[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Raw chat log of 2009-05-22 telcon
Mark Combellack: - Roll Call http://www.oasis-open.org/committees/membership.php?wg_abbrev=sca-j - Appointment of scribe. List attached below - Agenda bashing - Approval of minutes for 18th May 2009 http://www.oasis-open.org/committees/download.php/32569/SCA%20Java%20Minutes%202009-05-18.doc 0. Administration - Issue Status: Open: 30 - LOA: Martin Chapman June 1st to June 7th - Reminder: No SCA-J call on Monday 25th May 1. Review action items: Action Items that I believe are done: Action Items that I believe are still to be done: 2008-11-11-22: Mark to draw up some wording for Direction 1 (as discussed at the November F2F) for JAVA-62 2008-11-11-23: Mark (and others prepared to help) to investigate the WorkManager JEE spec and determine its applicability to SCA for JAVA-62 2009-05-11-01: Editors: remove extra space on line 767 of CD01 (PDF) 2009-05-11-02: Simon: Write a full proposal for JAVA-125 with all the required metadata 3. New Issues a. JAVA-164: Spring C&I SCA extension element does not provide full functionality possible in an SCA CT http://www.osoa.org/jira/browse/JAVA-164 Outline proposal in Jira 4. Open Issues a. JAVA-58: SCA Spring C&I Specification does not have a normative definition of how to calculate the ComponentType of a Spring Application context http://www.osoa.org/jira/browse/JAVA-58 Latest proposal: http://lists.oasis-open.org/archives/sca-j/200905/msg00102.html PDF: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/32614/sca-springci-draft-20070926_Issue58c.pdf MS Word: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/32615/sca-springci-draft-20070926_Issue58c.doc b. JAVA-92: Spring C&I spec needs to define how effective CT is calculated http://www.osoa.org/jira/browse/JAVA-92 Latest proposal: http://lists.oasis-open.org/archives/sca-j/200905/msg00102.html c. JAVA-149: SCA Spring C & I specification need to specify the limitations of implicit references http://www.osoa.org/jira/browse/JAVA-149 Proposal in Jira d. JAVA-150: SCA Spring C & I specification need to mention how SCA runtime should load multiple application context files. http://www.osoa.org/jira/browse/JAVA-150 Proposal in Jira 5. Issues waiting for updated proposals a. JAVA-122: EJB Binding - Remove references to conversational function http://www.osoa.org/jira/browse/JAVA-122 Waiting for updated proposal b. JAVA-140: Schema for @ejb-link-name is incorrect http://www.osoa.org/jira/browse/JAVA-140 Waiting for updated proposal c. JAVA-59: SCA Spring C & I specification does not state what happens when a Bean exposed as a service implements mutliple interfaces http://www.osoa.org/jira/browse/JAVA-59 Waiting for updated proposal d. JAVA-114: Spring CI runtime behaviour when annotation rules are violated http://www.osoa.org/jira/browse/JAVA-114 Waiting for updated proposal 6. Issues with no proposals a. JAVA-118: EJB Binding: Need description for <wireFormat/> and <operationSelection/> http://www.osoa.org/jira/browse/JAVA-118 No proposal b. JAVA-163: Spring C&I sca-spring:reference element has a default attribute which is unexplained http://www.osoa.org/jira/browse/JAVA-163 No proposal c. JAVA-24: The EJB bindings specification should provide explicity statesupport or non-support for Callbacks http://www.osoa.org/jira/browse/JAVA-24 No proposal d. JAVA-107: RFC2119 Language is needed for the EJB Binding Specification http://www.osoa.org/jira/browse/JAVA-107 No proposal e. JAVA-106: RFC2119 Language is needed for Spring C&I Specification http://www.osoa.org/jira/browse/JAVA-106 No proposal f. JAVA-63: SCA Spring C & I specification does not state whether Constructor Injection should be supported http://www.osoa.org/jira/browse/JAVA-63 No proposal 7. AOB a. Straggler roll call --------------------------------------------------------------- Rotating scribe list: Ron Barack SAP AG (3) Michael Beisiegel IBM (3) Sanjay Patil SAP AG (3) Jim Marino Individual (4) Pradeep Simha TIBCO Software Inc. (5) Vamsavardhana Chillakuru IBM (3) Plamen Pavlov SAP AG (2) Meeraj Kunnumpurath Individual (3) Anish Karmarkar Oracle Corporation (11) Martin Chapman Oracle Corporation (9) Ashok Malhotra Oracle Corporation (10) Bryan Aupperle IBM (11) Yang Lei (7) Simon Nash Individual (8 ) Mike Edwards IBM (10) Graham Charters IBM (3) Mike Edwards: ahh, Bach Martin C: having trouble dialling in its engaged Martin C: bach again Martin C: or antiques roadshow anish: Scribe: anish anish: Topic: Agenda bashing anish: agenda approved anish: Topic: approval of minutes anish: - Approval of minutes for 18th May 2009 anish: http://www.oasis-open.org/committees/download.php/32569/SCA%20Java%20Minutes%202009-05-18.doc anish: minutes approved anish: topic: administrivia anish: - Issue Status: Open: 30 - LOA: Martin Chapman June 1st to June 7th - Reminder: No SCA-J call on Monday 25th May anish: topic: AI review anish: status as indicated in the agenda anish: topic: new issues anish: a. JAVA-164: Spring C&I SCA extension element does not provide full functionality possible in an SCA CT http://www.osoa.org/jira/browse/JAVA-164 Outline proposal in Jira anish: anish explains the issue anish: Motion: m:anish s:mikeE to open issue 164 anish: motion approved w/o anish: resolution: issue 164 is open anish: topic: issue 58 anish: a. JAVA-58: SCA Spring C&I Specification does not have a normative definition of how to calculate the ComponentType of a Spring Application context http://www.osoa.org/jira/browse/JAVA-58 Latest proposal: http://lists.oasis-open.org/archives/sca-j/200905/msg00102.html PDF: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/32614/sca-springci-draft-20070926_Issue58c.pdf MS Word: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/32615/sca-springci-draft-20070926_Issue58c.doc anish: Mike explains his proposal anish: minor cut-and-paste error in 1st sentence anish: s/java implementation class/spring app context/ Mark Combellack lowered your hand anish: anish: we can get specific about interface and say interface.java anish: anish: this assumes annotation support anish: ... there are more annotations that sca has and we need to figure out which annotations we want to support anish: s/wiredByImple/wiredByImpl/ anish: dave: it says default attribute is present, shouldn't it says @default with a specific value anish: mike: not properly described. the attribute needs to be defined anish: this is a separate issue already anish: another s/wiredByImple/wiredByImpl/ anish: dave: global question, for Java C&I if there are no @reference annotations then we do heavy introspection else we don't. What is the situation here? anish: mikeE: it is a hybrid appraoch anish: dave: don't know what the spring user community would want anish: ... in JCI there is one java class, whereas here the app context is more like a composite anish: ... what is the justification for this approach anish: mikeE: we could say that if you have one sca:reference then that is it anish: anish: in spring c&i we have essentially a componentType sidefile anish: dave: worried about mising java annotations with xml anish: anish: concerned that SpringSource is not participating anish: mikeE: are we ready to accept the proposal with few changes (to add interface.java and typos)? anish: dave: can't quantify my discomfort with the mixed/hybrid model anish: ... if there is a sca:service/sca:reference/scaroperty then it takes that into consideration but also pulls in dangling references anish: mikeE: so what you are saying is that if you include sca specific elements then those are the only ones that get pulled into the CT anish: mikeE: the trouble is that if you have a dependency then it has to be satisfied anish: ... if there is a dangling one then it must be satisfy Martin C is uncomfortable talking about dangly things anish: anish: we should look at usecases that we see for spring C&I. spring already provides a composition-in-the-small. but does not provide intent/policy support for other technologies. if that is the usecase, then we can structure the proposal to target that anish: mikeE urges folks to get an email discussion going anish: no call this monday anish: adjourned
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]