AGENDA anish: 1. Roll call 2. Scribe appointment Scribe list attached below 3. Agenda bashing 4. Meeting Minutes Minutes of 2011-03-28 telcon: http://lists.oasis-open.org/archives/sca-j/201103/msg00048.html 5. TC Administrivia a. Recording issue status - 7 open, 0 new 6. ACTION ITEMS 20110307-03 Mike - Respond to PR comment re resolution of issue 227. DONE 2011-03-28-1: Mike to produce proposal for issue 228 with alternative 1 (if bean implements >1 remotable interfaces that is an error. Use SCA extensions to fix that) DONE 2011-03-28-2: Mike to clean up spring C&I spec wrt fixing formating issues (eg: reference format) DONE 2011-03-28-3: Anish to provide Mike with list of names for the ACK section DONE 7. Planning for PR of various specs a) CAA spec: apply issue 233 b) CAA TA: apply issue 235, apply issue 232 c) CAA TC: apply issues 215? & 234 d) POJO spec: apply issue 231 e) POJO TA: apply issue 236 f) POJO TC: apply issue 222, ref udpate(?) g) Spring: resolve issues 228, 237, apply all resolved issues (228, 230, 237), ed. changes 8. New Issues (requires 2/3) NONE 9. Issues with proposals a. JAVA-228 Interface of a service when no element is present http://osoa.org/jira/browse/JAVA-228 Proposal: http://lists.oasis-open.org/archives/sca-j/201103/msg00057.html 10. CSD & PR for Spring C&I Two alternatives for PR: wait till TA/TCs are done OR get public feedback now. We decided last week to get an estimate for how much time would be needed for TA/TCs to be done before deciding. 11. Issues waiting for updated proposals (Spring/EJB/JEE) a. JAVA-109: Property and reference names computed from SCA annotations in web modules not specified explicitly http://www.osoa.org/jira/browse/JAVA-109 Proposal in Jira Waiting for updated proposal (Vamsi) b. JAVA-174: Consider portlets in the SCA JEE specification http://www.osoa.org/jira/browse/JAVA-174 c. JAVA-91: Java EE Spec: Need to define the derivation of the name of a component contributed to the Domain by an application.composite file http://www.osoa.org/jira/browse/JAVA-91 Waiting for updated proposal (Mike) d. JAVA-93: JEE Integration spec needs to define how effective CT is calculated http://www.osoa.org/jira/browse/JAVA-93 Waiting for updated proposal (Anish) e. JAVA-108: RFC2119 Language is needed for the SCA-JEE Specification http://www.osoa.org/jira/browse/JAVA-108 Waiting for updated proposal f. JAVA-88: Java EE Spec: The @archive attribute of the implementation.jee element needs fixing http://www.osoa.org/jira/browse/JAVA-88 No proposal Plamen to check whether on his informal JEE issues list 12. AOB a. straggler role 13. Spec status CAA (part of 1st batch of 1.1 specs): 2 new issue, 2nd PR ended 2010-12-08, CSD05 expected to be final CSD 1st impl: Tuscany (compliant), 2nd impl: ?? http://lists.oasis-open.org/archives/sca-j/201012/msg00000.htmlhttp://lists.oasis-open.org/archives/sca-j/201012/msg00000.htmlTA: CD01 PR ended 2010-10-24, 0 open issue, CSD02 expected to be final CSD TC: CD01 PR ended 2010-10-24, 0 open issue, CSD02 expected to be final CSD POJO (part of 1st batch of 1.1 specs): 0 open issues, 2st PR ended 2010-12-08, CSD03 expected to be final CSD 1st impl: Tuscany (compliant), 2nd impl: ?? TA: CSD01 PR ended 2010-12-23 TC: CDS01 PR ended 2010-12-23 EJB Binding (not part of 1st batch of 1.1 specs): 0 open issues, 1st PR done, CSD03 expected to be final CSD 1st impl: ??, 2nd impl: ?? TA: WD stage, no CSD yet, 60 day PR needed TC: WD stage, no CSD yet, 60 day PR needed Spring C&I (not part of 1st batch of 1.1 specs): 1 open issues, WD stage, no CSD yet, 60 day PR needed 1st impl: ??, 2nd impl: ?? TA: no work done TC: no work done JEE (not part of 1st batch of 1.1 specs): 6 open issues, WD stage (not actively worked on), no CSD yet, 60 day PR needed 1st impl: ??, 2nd impl: ?? TA: no work done TC: no work done ----------------------------------------- Scribe list: Plamen Pavlov: 3 Dave Booz: 3 (Last scribed: 2010-11-0) Ashok Malhotra: 22 (Last scribed: 2011-02-21) Bryan Aupperle: 31 (Last scribed: 2011-03-07) Mike Edwards: 27 (Last scribed: 2011-03-14) Martin Chapman: 23 (Last scribed: 2011-03-21) Anish Karmarkar: 20 (Last scribed: 2010-03-2
anish: Date: 2011-04-04
anish: Chair: Dave Booz & Anish Karmarkar
anish: Scribe: Ashok (Oracle)
anish: Scribe: Ashok Malhotra
anish: ScribeNick: Ashok (Oracle)
Ashok (Oracle): Topic: Agenda bashing
Ashok (Oracle): Anish: Let's wait for Assembly TC to come to a decision before we discuss exit criteria
Ashok (Oracle): Bryan: We can discuss the MAYs and the SHOULDs as we are doing in other TCs like Bindings
Ashok (Oracle): Anish: We can add a discussion of exit criteria
Ashok (Oracle): Topic: Meeting Minutes Minutes of 2011-03-28 telcon: http://lists.oasis-open.org/archives/sca-j/201103/msg00048.html
Ashok (Oracle): Minutes approved w/o objection
Ashok (Oracle): Topic: TC Administrivia a. Recording issue status - 7 open, 0 new
Ashok (Oracle): Topic: ACTION ITEM Review
Ashok (Oracle): All AIs are done
Ashok (Oracle): Topic: a. JAVA-228 Interface of a service when no element is present http://osoa.org/jira/browse/JAVA-228 Proposal: http://lists.oasis-open.org/archives/sca-j/201103/msg00057.html
Ashok (Oracle): Anish: MikeE not on the call
Ashok (Oracle): Anish: Explains issue
anish: - if the bean class implements zero Java interfaces annotated with @Remotable, the interface class is the Bean class itself - if the bean class implements one Java interface that is annotated with @Remotable, the interface class is the Java interface class which is annotated with @Remotable - where there are no explicit <sca:service/> elements in the application context, if a bean class implements two or more Java interfaces which are annotated with @Remotable, this is not allowed and the SCA runtime MUST raise an error. [SPR30005]
anish: Where there are no <sca:service/> elements, the bean is exposed as a single service with an interface that is the defined either by the bean class itself, or .is defined by a single @Remotable interface implemented by the bean class. It is not premitted for the bean class to implement two or more @Remotable interfaces in this case - this can only be done with the use of explicit <sca:service/> elements.
Ashok (Oracle): Anish: Typo re word "bean". Should be lower case.
Ashok (Oracle): Anish: Should say "exactly one Java interface" on line 516 second bullet
Ashok (Oracle): Bryan moves to resolves 228 in the file as modified above. DaveB seconds
Ashok (Oracle): RESOLVED unanimously
Ashok (Oracle): Topic: Progress to PR
Ashok (Oracle): Anish: Discusses timing
Ashok (Oracle): Anish: Let me check with Mike
Ashok (Oracle): s/PR/PR for Spring C&I/
Ashok (Oracle): Topic: Exit Criteria
Ashok (Oracle): Anish: Summarizes state of play ... teo impls required for all mandatory statements
Ashok (Oracle): s/teo/two/
Ashok (Oracle): Anish: I think out-of-band discussion is needed
Ashok (Oracle): Anish: SHOULDs and MAYs are being re-examined
Ashok (Oracle): ... we can do the same for our specs
Ashok (Oracle): ... we have very few optional statements. I have done some work on it. Happy to share with the TC.
MartinC : Q!
Ashok (Oracle): Discussion about Fabric3 and what it implments
Ashok (Oracle): ... and what it does not implement
Ashok (Oracle): Martin: The exercise in Assembly TC is about what has been testing, not about what is optional or
Ashok (Oracle): mandatory
MartinC : of course it turns out that most untested stuff is optional! bit removalk of optional is not the goal, rather it is removal of untested stuff
Ashok (Oracle): s/removalk/removal/
Ashok (Oracle): Anish: We will have a call on the 18th
Ashok (Oracle): Anish: Inclined to cancel call on the 11th
Ashok (Oracle): ... next week's call is cancelled
Ashok (Oracle): ADJOURNED
--
All the best, Ashok
All the best, Ashok