← Prev in month
← Prev in thread
Next in thread →
Next in month →
Java TC raw minutes July 13th 2009
Dave Booz: - 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 10th July 2009 http://www.oasis-open.org/committees/download.php/33337/SCA%20Java%20Minutes%202009-07-10.doc 0. Administration - Issue Status: Open: 24 - 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-10-01: Mike E to make sure Ram attends calls to discuss his issues (JAVA-150, JAVA-167 and possibly others) 2. SCA-J Test Suite Discussion on the Test Assertions and Test Cases documents http://lists.oasis-open.org/archives/sca-j/200906/msg00078.html PDF: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/32929/SCA_J_CAA_Test_Assertions_5.pdf ODT: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/32928/SCA_J_CAA_Test_Assertions_5.odt 3. New Issues (Excluding EJB/Spring new issues) None 4. Open Issues a. JAVA-139: Default value for SCA property is not supported for java implementations http://www.osoa.org/jira/browse/JAVA-139 Updated proposal: http://lists.oasis-open.org/archives/sca-j/200907/msg00012.html Continued from last Monday's call b. JAVA-118: EJB Binding: Need description for and http://www.osoa.org/jira/browse/JAVA-118 Latest proposal: http://lists.oasis-open.org/archives/sca-j/200907/msg00000.html c. JAVA-166: Spring C&I does not say anything about SCA annotations http://www.osoa.org/jira/browse/JAVA-166 Outline proposal in Jira d. 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 Ram to be on the call e. 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 Ram to be on the call 5. Issues waiting for updated proposals a. JAVA-46: equals() method on ServiceReference and CallableReference http://www.osoa.org/jira/browse/JAVA-46 Waiting for updated proposal b. JAVA-155: Inconsistent normative statements in Chapter 10 http://www.osoa.org/jira/browse/JAVA-155 Discuss - What do we do next? Waiting for updated proposal c. JAVA-127: Long running request/response operations http://www.osoa.org/jira/browse/JAVA-127 Proposal: http://lists.oasis-open.org/archives/sca-j/200812/msg00089.html Waiting for presentation slides d. JAVA-168: Conversion rules for property values are not specified http://www.osoa.org/jira/browse/JAVA-168 Proposed direction: http://lists.oasis-open.org/archives/sca-j/200907/msg00004.html Waiting for full proposal 6. Issues without proposals a. JAVA-13: ComponentContext.getProperty(...) ill defined http://www.osoa.org/jira/browse/JAVA-13 No proposal b. JAVA-51: More examples on mapping to Java http://www.osoa.org/jira/browse/JAVA-51 No proposal c. JAVA-54: Section 7.1 of the Java CAA Specification is unclear http://www.osoa.org/jira/browse/JAVA-154 No proposal d. JAVA-62: Clarify what a Component Implementation can do with threads http://www.osoa.org/jira/browse/JAVA-62 No proposal e. JAVA-78: Need API to set EPR and for a reference invocation http://www.osoa.org/jira/browse/JAVA-78 No proposal f. JAVA-156: Intent annotations are missing from Java CAA as compared to Policy FW spec http://www.osoa.org/jira/browse/JAVA-156 No proposal 7. AOB a. Straggler roll call --------------------------------------------------------------- Rotating scribe list: Anish Karmarkar Oracle Corporation (12) Yang Lei (8 ) Simon Nash Individual (9) Mike Edwards IBM (11) Graham Charters IBM (4) Ashok Malhotra Oracle Corporation (12) Martin Chapman Oracle Corporation (11) Bryan Aupperle IBM (13) Graham Charters: Scribe: Graham Charters Graham Charters: Agenda updates: None Graham Charters: Quorate (6/11) Graham Charters: Approval of minutes: no updates. Minutes accepted. Graham Charters: 24 open issues. Still in public review. Graham Charters: Action Item Review: Graham Charters: 2009-07-10-01 - Done Graham Charters: Test Suite: Graham Charters: No comments. Graham Charters: New Issues: Graham Charters: None Graham Charters: Open Issues: Graham Charters: Java-139 Graham Charters: JAVA-139: Default value for SCA property is not supported for java implementations Graham Charters: Mike would like to propose "close no action" because he feels it is an unnecessary complexity. Graham Charters: Main advocates are Simon and Anish, but neither are on the call. Holding off to give Anish chance to join. Graham Charters: Skipping to "JAVA-167: SCA Spring C & I specification should make type attribute as optional for element " to take advantage of Ram on the call. Graham Charters: Implicit services take interface from the Spring bean, or the bean type itself (if it does not implement an interface). We should not need to specify the type on sca:service because we can determine it from the bean. Suggestion is to make the type optional and the default would be the interface of the bean it's pointing to (consistent with implementation.java). Graham Charters: Mike motions to resolved Java-167 with the direction laid out in the Jira. Graham Charters: Bryan A seconds. Graham Charters: Accepted with unanimous consent. Graham Charters: Action: Mike E to produce text for Java-167 Graham Charters: JAVA-150: SCA Spring C & I specification need to mention how SCA runtime should load multiple application context files. anonymous morphed into anish Graham Charters: Issue concerns handling of multiple application context files. Ram took the group through the issue. Mike E was concerned the proposal impact was not clear. Would like to see the proposal written into the spec with change tracking on. Graham Charters: Action: Ram to write up the proposal in the spec with change tracking on. Mike Edwards: I'll dial in Mike Edwards: again Mike Edwards: my line dropped too Mike Edwards: back again Mike Edwards: Graham is sounding chopped now Graham Charters: I have to go for 1 mins. And I'm scribe. Mike Edwards: graham - suggest that you use the US dial in Graham Charters: Back Graham Charters: JAVA-139: Default value for SCA property is not supported for java implementations Graham Charters: Anish: would be nice to provide simple support for the most common use cases. Anish could live without this. Graham Charters: Mike thinks closing is the right answer. Current proposal does not handle all the cases. Graham Charters: Mike E moved to "close no action". Graham Charters: Bryan A seconds Graham Charters: No discussion Graham Charters: Anish abstains Graham Charters: No objections. Motions passes. Java-139 closed. Graham Charters: JAVA-118: EJB Binding: Need description for and Graham Charters: In v4, Dave has attempted to align this with the Web services binding spec. anish: +1 to the proposal anish: http://lists.oasis-open.org/archives/sca-j/200907/msg00000.html Graham Charters: Mike moves to resolve Java-118 with the proposal in the referenced email (http://lists.oasis-open.org/archives/sca-j/200907/msg00000.html) Graham Charters: Anish seconds Graham Charters: No discussion. Graham Charters: Motion passed with unanimous consent. Graham Charters: JAVA-166: Spring C&I does not say anything about SCA annotations Graham Charters: Need to reconcile annotations in the classes and the SCA elements in the application contexts. Both contribute to the component type. Graham Charters: It would be hard to justify not supporting SCA annotations. Also hard to justify taking out the SCA elements and therefore have to work out how to handle this combination. Graham Charters: Bryan: if we don't support annotations, do we need mechanisms for attaching policy. Anish: we modified the schema to include interfaces policies. Bryan: we have not covered implementation policies. Graham Charters: Some question about whether a user would use SCA annotation in POJOs and then assemble using Spring and them assemble in SCA. Seems strange to interpose Spring in between two slices of SCA. Graham Charters: Anish: it does not seem to make sense to allow every annotation (e.g. Scope). Graham Charters: Action: Anish to create a proposal for the list of annotations which make sense. Martin C stooopid bridge cut me off Graham Charters: Java-164 - Mike sent write-up to list. Mike Edwards: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/33353/sca-springci-1.1-spec-WD01%2BIssue164b.pdf Mike Edwards: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/33352/sca-springci-1.1-spec-WD01%20Issue164b.doc anonymous morphed into Mark Combellack Graham Charters: Mike to merge into a new working draft. Graham Charters: Changes are additive so do not require a schema namespace change. Graham Charters: Anish, minor issue. Schema uses a type from a schema which is not imported. Thinks it requires an xsd:import. Mike to check. Mike Edwards: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/33357/sca-springci-draft-20070926_Issue58e.pdf Graham Charters: Java-58 Graham Charters: Algorithm for determining the component type. See section 3. Graham Charters: Second change is you either reflect to determine all or spell everything out (once you meet an scaroperty or sca:reference element). Graham Charters: Anish, in this case, unlike Java, we are specifying Spring things in XML, which contributed to the component type, which is also XML. These elements are very similar to the ones present in a component type. We have extensibility in both. So if you specify something in extensibility in Spring, should it be surface in the SCA extensibility? Graham Charters: Mike thinks the spec should not need to say anything. Anish thinks we could state that they are copied through, but do not need to be understood. Graham Charters: Example: imagine the Spring and C C&Is sharing an extensibility. Could just understand at the CT level if we stated it must be copied through. Graham Charters: Mike not sure of the value of this given it is valid to just throw it away. Graham Charters: Discussion ended - ran out of time. Graham Charters: AOB: Graham Charters: Call closed. Regards, Graham. Graham Charters PhD CEng MBCS CITP STSM, AIM Technical Lead OSGi Expert Groups, Master Inventor, UKI Technical Staff Member IBM United Kingdom Limited, MP 146, Hursley Park, Winchester, SO21 2JN, UK Tel: (Ext) +44-1962-816527 (Int) 7-246527 (Fax) +44-1962-818999 Internet: 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
← Prev in month
← Prev in thread
Next in thread →
Next in month →