AGENDA: - 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 13th July 2009 http://www.oasis-open.org/committees/download.php/33411/SCA%20Java%20Minutes%202009-07-13.doc

0. Administration - Issue Status: Open: 22 - SCA-J Public Review Started: 8th June 2009 Ends: 7th August 2009

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-06-19-01: Mike E to prepare a detailed proposal for Issue 149 2009-07-06-01: Dave B to raise to liaison (so that other C&Is can consider and possibly assembly) that non-XML based C&Is should state how the conversion of property values happens 2009-07-13-01: Mike E to produce text for JAVA-167 2009-07-13-02: Ram to write up proposal in spec with change tracking on for JAVA-150 2009-07-13-03: Anish to create a proposal for the list of annotations which make sense for JAVA-166

2. New Issues

None

3. 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/200907/msg00027.html PDF: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/33357/sca-springci-draft-20070926_Issue58e.pdf

MS Word: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/33358/sca-springci-draft-20070926_Issue58e.doc

b. 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 Latest proposal: http://lists.oasis-open.org/archives/sca-j/200907/msg00041.html

4. Issues waiting for updated proposals

a. 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 Waiting for JAVA-58 to be resolved.

b. 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 Waiting for updated proposal

c. JAVA-114: Spring CI runtime behaviour when annotation rules are violated http://www.osoa.org/jira/browse/JAVA-114 Proposal in Jira Blocked by JAVA-166

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 Waiting for full proposal (Ram Action Item)

e. JAVA-166: Spring C&I does not say anything about SCA annotations http://www.osoa.org/jira/browse/JAVA-166 Waiting for list of Annotations (Anish Action Item)

f. JAVA-167: SCA Spring C & I specification should make type attribute as optional for element http://www.osoa.org/jira/browse/JAVA-167 Outline proposal in Jira Waiting for full proposal (Mike E Action Item)

5. Issues with no proposals

a. 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

b. JAVA-107: RFC2119 Language is needed for the EJB Binding Specification http://www.osoa.org/jira/browse/JAVA-107 No proposal

c. JAVA-106: RFC2119 Language is needed for Spring C&I Specification http://www.osoa.org/jira/browse/JAVA-106 No proposal

d. 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

6. AOB

a. Straggler roll call

Item 0 Agenda Bashing No changes

Item 0 Administrivia Public Review is in progress Ends Aug 7

Item 1 Minutes from Previous Meeting Minutes from 13th July are accepted without change

Item 2 Action Items. 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-06-19-01: Mike E to prepare a detailed proposal for Issue 149 2009-07-06-01: Dave B to raise to liaison (so that other C&Is can consider and possibly assembly) that non-XML based C&Is should state how the conversion of property values happens 2009-07-13-01: Mike E to produce text for JAVA-167 2009-07-13-02: Ram to write up proposal in spec with change tracking on for JAVA-150 2009-07-13-03: Anish to create a proposal for the list of annotations which make sense for JAVA-166 All remain outstanding

Item 3 Open Issues 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/200907/msg00027.html PDF: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/33357/sca-springci-draft-20070926_Issue58e.pdf

MS Word: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/33358/sca-springci-draft-20070926_Issue58e.doc anonymous morphed into anish Mike describes the proposal Anish: Could you add an example. Mike: Happy to do this, but I'd like to do that outside the resolution of this issue Dave: Give Mike an action item to create an example

ACTION 20090717-01: Mike to create an example of the componentType introspection

Mike moves to resolve Issue 58 using the proposal in the email http://lists.oasis-open.org/archives/sca-j/200907/msg00027.html Bryan seconds Motion passes unanimously Issue 58 is resolved.

JAVA 98 Spring C&I spec needs to define how effective CT is calculated http://www.osoa.org/jira/browse/JAVA-92 anish: we should say that sides files are not used in effective CT anish: a similar issue was filed in BPEL anish: this is what mike's proposal in BPEL says:"The SCA WS-BPEL Client and Implementation Specification does not support the use of component type side files (as described in the SCA Assembly Model specification [SCA-Assembly]). The component type of a WS-BPEL process used an an implementation is determined completely by introspection of the process."

Mike moves to resolve Issue 92 by adding the following text at the end of Section 3, as defined in the resolution of Issue 58: "The Spring Component Implementation type does not support the use of Component Type side files, as defined in the SCA Assembly Model specification [SCA-ASSEMBLY], so that the effective componentType of a Spring Application Context is determined completely by introspection of the Spring Application Context" Bryan seconds Motion passes unanimously Issue 92 is resolved with the proposal text above.

JAVA-59: SCA Spring C & I specification does not state what happens when a Bean exposed as a service implements multiple interfaces http://www.osoa.org/jira/browse/JAVA-59 Latest proposal: http://lists.oasis-open.org/archives/sca-j/200907/msg00041.html Mike presents the proposal in the email above Mike moves to resolve Issue 59 using the proposal in the email http://lists.oasis-open.org/archives/sca-j/200907/msg00041.html Bryan seconds Anish queries the comment about Issue 167 in the email Mike indicates that there is a text change required from issue 167 Motion is accepted unanimously Issue 59 is resolved using the proposal in the email

<Discussion of possibilities for resolving Issue 166> Thinking at the moment is in the direction of disallowing the SCA annotations in Spring beans

Yours, Mike.

Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU