OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Raw text of Sep 22nd meeting minutes


Dave Booz: 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 from previous meeting(s) 
http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/29361/SCA%20Java%20Minutes%202008-09-15.doc 
 
 
1. Review action items: 
 
2008-07-15-2: Vladimir to produce a proposal for JAVA-2 
2008-07-15-9: MikeE to produce worked example of his proposal for JAVA-1, and to show the invocation model 
2008-07-24-2: Simon to revise proposal for issue 49 based on today's discussion 
2008-09-08-2: Everyone to review the SCA-J WD04 for ballot on the next call. 
2008-09-15-1: Simon to produce specific references to the resolutions for missing issues 20, 40, 42, 43 
http://lists.oasis-open.org/archives/sca-j/200809/msg00079.html 
 
2. Update from JEE Sub Committee Chair (Time boxed to maximum of 5 minutes) 
http://lists.oasis-open.org/archives/sca-j/200809/msg00077.html 
 
3. Ballot for CD 
 
During the last meeting of the sca-j TC on September 15th, a motion was passed to instruct the editors to prepare a new WD based on comments. 
 
4. Accepting new issues: 
 
JAVA-61: Describe the concurrency model for each scope 
http://www.osoa.org/jira/browse/JAVA-61 
http://lists.oasis-open.org/archives/sca-j/200809/msg00018.html 
 
JAVA-62: Clarify what a Component Implementation can do with threads 
http://www.osoa.org/jira/browse/JAVA-62 
http://lists.oasis-open.org/archives/sca-j/200809/msg00024.html 
 
JAVA-63: SCA Spring C & I specification does not state whether Constructor Injection should be supported 
http://www.osoa.org/jira/browse/JAVA-63 
http://lists.oasis-open.org/archives/sca-j/200809/msg00027.html 
 
JAVA-64: SCA Spring C & I specification does not state the purpose of sca:composite element 
http://www.osoa.org/jira/browse/JAVA-64 
http://lists.oasis-open.org/archives/sca-j/200809/msg00028.html 
 
JAVA-65: There is no lifecycle defined for SCA Components 
http://www.osoa.org/jira/browse/JAVA-65 
http://lists.oasis-open.org/archives/sca-j/200809/msg00032.html 
 
JAVA-66: Should the definitions of the various Scopes be pushed up to the SCA-Assembly specification? 
http://www.osoa.org/jira/browse/JAVA-66 
http://lists.oasis-open.org/archives/sca-j/200809/msg00033.html 
 
JAVA-67 Need normative rules for stateful callbacks 
http://www.osoa.org/jira/browse/JAVA-67 
 
JAVA-68 Uniqueness of conversation IDs 
http://www.osoa.org/jira/browse/JAVA-68 
 
JAVA-69 Misleading statement about lifetime of stateful callbacks 
http://www.osoa.org/jira/browse/JAVA-69 
 
JAVA-70 ConversationAttributes on class or interface? 
http://www.osoa.org/jira/browse/JAVA-70 
 
JAVA-71 Incorrect code in section 6.7.2 example 
http://www.osoa.org/jira/browse/JAVA-71 
 
JAVA-72 Should not say callback ID is passed in reference parameters 
http://www.osoa.org/jira/browse/JAVA-72 
 
JAVA-73 Incorrect reference to "original request" 
http://www.osoa.org/jira/browse/JAVA-73 
 
JAVA-74 Clarify meaning of "should implement" 
http://www.osoa.org/jira/browse/JAVA-74 
 
JAVA-75 Incorrect description of @Scope annotation default 
http://www.osoa.org/jira/browse/JAVA-75 
 
JAVA-76 Incorrect code in section 6.7.4 examples 
http://www.osoa.org/jira/browse/JAVA-76 
 
JAVA-77 A remotable service SHOULD be translatable into a generally accepted standard for a service, such as WSDL 1.1 or WSDL 2.0 
http://www.osoa.org/jira/browse/JAVA-77 
http://lists.oasis-open.org/archives/sca-j/200809/msg00059.html 
 
JAVA-78 Need API to set EPR and for a reference invocation 
http://www.osoa.org/jira/browse/JAVA-78 
 
JAVA-79 Missing word "type" for "return type" in CAA spec - sec 3.1 
http://www.osoa.org/jira/browse/JAVA-79 
 
JAVA-80 Ambiguous description of method for @OneWay annotation 
http://www.osoa.org/jira/browse/JAVA-80 
 
JAVA-81 Normative references to SCA Spec docs point to v1.00 docs 
http://www.osoa.org/jira/browse/JAVA-81 
 
 
6. Open issues discussion: 
 
JAVA-48 - @Callback annotation does not feature in section on Interfaces 
http://www.osoa.org/jira/browse/JAVA-48 
 
New Proposal 
http://lists.oasis-open.org/archives/sca-j/200808/msg00070.html 
 
Updated Proposals 
http://lists.oasis-open.org/archives/sca-j/200808/msg00086.html 
http://lists.oasis-open.org/archives/sca-j/200808/msg00079.html 
http://lists.oasis-open.org/archives/sca-j/200808/msg00083.html 
http://lists.oasis-open.org/archives/sca-j/200808/msg00087.html 
 
 
JAVA-42 - Incorrect examples of methods annotated @Init and @Destroy 
http://www.osoa.org/jira/browse/JAVA-42 
Close because of issue 37/44 changes that no longer restrict access modifiers 
 
http://lists.oasis-open.org/archives/sca-j/200808/msg00073.html 
http://lists.oasis-open.org/archives/sca-j/200808/msg00077.html 
http://lists.oasis-open.org/archives/sca-j/200808/msg00078.html 
http://lists.oasis-open.org/archives/sca-j/200808/msg00085.html 
 
 
JAVA-3 - Local services expose implementation classes as their type 
http://www.osoa.org/jira/browse/JAVA-3 
Should introduction of @Local annotation (JAVA-3) affect the Semantics of an Unannotated Implementation 
 
http://lists.oasis-open.org/archives/sca-j/200808/msg00098.html 
 
 
JAVA-47: Missing description of what the @EagerInit annotation does 
http://www.osoa.org/jira/browse/JAVA-47 
Proposal in JIRA 
 
 
7. AOB 
 
Straggler roll call 
 
 
8. Adjourn 
 
--------------------------------------------------------------- 
Rotating scribe list: 
 
Plamen Pavlov SAP AG (0) 
Peter Walker Sun Microsystems (1) 
Roberto Chinnici Sun Microsystems (2) 
Peter Peshev SAP AG (2) 
Ron Barack SAP AG (3) 
Michael Beisiegel IBM (3) 
Anish Karmarkar Oracle Corporation (4) 
Mike Edwards IBM (3) 
Sanjay Patil SAP AG (3) 
Ashok Malhotra Oracle Corporation (3) 
Pradeep Simha TIBCO Software Inc. (3) 
Martin Chapman Oracle Corporation (3) 
Bryan Aupperle IBM (3) 
Vladimir Savchenko SAP AG (1) 
Jim Marino Individual (4) 
Meeraj Kunnumpurath Individual (1) 
Vamsavardhana Chillakuru IBM (2) 
Simon Nash (1)
Mike Edwards: VERY posh music on hold
Vamsi: The India toll free number is not working for me 
anonymous morphed into Pradeep
Pradeep: Scribe: Pradeep
Pradeep: Agenda Bashing: No changes
Pradeep: Can't approve meeting as we are not quorate.
Pradeep: On to action items
Pradeep: 2008-07-24-2 - Done
Pradeep: 2008-09-15-1 - Done
Vamsi: upto section 6.1.2
Pradeep: Update from JEE SC - Reviewing WD Specification. Just started section 6.
Vamsi: reviewed up to section 6.1.2
Pradeep: On to new issues.
Pradeep: Can't open new issues as we are not quorate.
Vamsi: http://lists.oasis-open.org/archives/sca-j/200809/msg00041.html
Pradeep: Dave to make JIRA entry for the new issue above
Pradeep: On to topic 6 of agenda - open issues discussion
Pradeep: Action item for Simon to writeup latest proposal for JAVA-25
Pradeep: Simon presenting his proposal to JAVA-48
Vamsi: http://lists.oasis-open.org/archives/sca-j/200808/msg00086.html
Pradeep: Mike Edwards - Let's us go with Simon's proposal in http://lists.oasis-open.org/archives/sca-j/200808/msg00086.html
Pradeep: Action item for Simon to send updated proposal for JAVA-48.
Pradeep: Issue JAVA-42 has been resolved.
Pradeep: Discussion on JAVA-3
Pradeep: Action item for Simon to send updated proposal for JAVA-3.
Pradeep: Michael Beisiegel Joins. Meeting is quorate.
Vamsi: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/29361/SCA%20Java%20Minutes%202008-09-15.doc
Pradeep: Minutes of meeting on Sept 15th accepted without objections.
Martin C reports that the cat has found the velcro strip for my power supply and keeps getting stuck</B< pre>
Please change your name from 'anonymous' using the Settings button
Dave Booz: section 2.3.s: A composite scoped implementation may also specify eager initialization using the @EagerInit annotation. When marked for eager initialization, the composite scoped instance is created when its containing component is started. If a method is marked with the @Init annotation, it is called when the instance is created.
Pradeep1: Discussion on JAVA-47
Mike Edwards: The @EagerInit annotation is used to annotate the Java class of a Composite scoped implementation for eager initialization. When marked for eager initialization, the composite scoped instance is created when its containing component is started.
Pradeep: Mike Edwards moves to resolve issue JAVA-47 with above text
Pradeep: Simon Nash seconds.
Mike Edwards: COMPOSITE
Pradeep: Simon prose to ammend to change first occurrence of Composite to COMPOSITE.
Pradeep: Mike Edwards seconds.
Pradeep: s/prose/proposes
Pradeep: Ammendment accepted without objections.
Mike Edwards: The @EagerInit annotation is used to annotate the Java class of a COMPOSITE scoped implementation for eager initialization. When marked for eager initialization, the COMPOSITE scoped instance is created when its containing component is started.
Mike Edwards: Update the specification to add the following text at after line 1208 of the @EagerInit section in Working Draft 03
Mike Edwards: The @EagerInit annotation is used to annotate the Java class of a COMPOSITE scoped implementation for eager initialization. When marked for eager initialization, the composite scoped instance is created when its containing component is started.
Vamsi: The description goes at line 1222
Vamsi: of WD 04.
Pradeep: Ammended motion accepted without objections. Issue JAVA-47 resolved.
Vamsi: http://lists.oasis-open.org/archives/sca-j/200809/msg00082.html
Pradeep: Back to issue JAVA-48
Pradeep: Simon makes motion to resolve issue JAVA-48 with text in http://lists.oasis-open.org/archives/sca-j/200809/msg00082.html to be inserted after line 202
Pradeep: in WD-04
Simon Nash: 3.4 @Callback
A callback interface is declared by using a @Callback annotation on a Java
service interface, with the Java Class object of the callback interface as a
parameter. There is another form of the @Callback annotation, without any
parameters, that specifies callback injection for a setter method or
a field of an implementation.
Pradeep: Vamsi seconds
Pradeep: Motion accepted unanimously without objection.
Pradeep: Meeting adjourned.

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]