Appointment of Scribe. List Attached Below
Mark Combellack: - Roll Call
- Appointment of scribe. List attached below
- Agenda bashing
- Approval of minutes for 5th June 2009
0. Administration
- Issue Status: Open: 31
1. Review action items:
Action Items that I believe are done:
2009-06-05-01: MikeE to raise issue in Assembly against wireFormat and operationSelector to make them abstract.
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-01-01: MikeE to raise issue regarding some Assembly tests that require Java
2009-06-01-02: Simon to contact Vamsi to discuss proposal for Issue 139
2009-06-05-02: Anish to raise an issue in Bindings TC against WS binding spec to address wireFormat and operationSelector pseudo-schema once the Assembly change is made to make these abstract.
2. Progress of the SCA-J specification to Public Review
Reminder: submitted for Public Review
Updated specification title:
3. New Issues
None
4. Open Issues
a. JAVA-161: @Service attributes "value" and "interfaces" should be combined
Latest proposal:
b. JAVA-125: Allow call semantics to be specified in interface.java
Latest proposal:
c. JAVA-153: Java CI should have corresponding changes in JAVA-125
Latest proposal:
d. JAVA-131: @Callback injection could be NULL (expanded to include refs, property and re-injection and callback
Proposed direction for resolution:
e. JAVA-143: Guidelines for dealing with cyclic references refers to an impossible situation
Proposal in Jira
f. JAVA-139: Default value for SCA property is not supported for java implementations
Outline of proposal in Jira
5. Issues waiting for updated proposals
a. JAVA-46: equals() method on ServiceReference and CallableReference
Waiting for updated proposal
b. JAVA-1: Accessing SCA Services from non-SCA component code
Latest discussions:
Updated Proposal:
Updated Proposal (PDF):
Waiting for updated proposal
c. JAVA-155: Inconsistent normative statements in Chapter 10
Discuss - What do we do next?
Waiting for updated proposal
d. JAVA-127: Long running request/response operations
Proposal:
Waiting for presentation slides
6. Issues without proposals
a. JAVA-13: ComponentContext.getProperty(...) ill defined
No proposal
b. JAVA-51: More examples on <interface.wsdl> mapping to Java
No proposal
c. JAVA-54: Section 7.1 of the Java CAA Specification is unclear
No proposal
d. JAVA-62: Clarify what a Component Implementation can do with threads
No proposal
e. JAVA-78: Need API to set EPR and for a reference invocation
No proposal
f. JAVA-156: Intent annotations are missing from Java CAA as compared to Policy FW spec
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)
Yang Lei (7)
Simon Nash Individual (8 )
Mike Edwards IBM (10)
Graham Charters IBM (3)
Anish Karmarkar Oracle Corporation (12)
Martin Chapman Oracle Corporation (10)
Ashok Malhotra Oracle Corporation (11)
Bryan Aupperle IBM (12)
Yang Lei: scribe: yang
Yang Lei: Topic: Agenda bashing. No comments
anonymous morphed into anish
Yang Lei: Topic: approval of minutes. No comments. Approved as posted.
Yang Lei: Topic: Review action items.
Yang Lei: Mike: done.
Yang Lei: Simon: done.
Yang Lei: Topic: Progress of the SCA-J specification to Public Review.
anish any ETA?</B< pre>
Yang Lei: Mark: waiting to hear from Mary's
Yang Lei: Topic: New Issues. None.
Yang Lei: Topic: Open Issues
Yang Lei: Topic: JAVA-161: @Service attributes "value" and "interfaces" should be combined
Latest proposal:
Yang Lei: Simon: describe the issue.
Yang Lei: Mike: names: contains an array of Strings which are used as the service names for each of the interfaces declared in the interfaces array
Yang Lei: Mike: interface array is the value array
Yang Lei: Discuss on :"A component implementation MUST NOT have two services with the same Java simple name."
Yang Lei: Simon: propose: the @service annotation can not specify services of the same name.
Yang Lei: Anish: suggest using computed service name. Simon thinks that is handled in the component type section not the @sevice section
Yang Lei: Dave: reference side does not have these statements. Simon: need to open new issue
anish perhaps we should not use 2119 keyword as the only trigger for tests</B< pre>
Yang Lei: Summary: name: 1) use value attribute array, 2) Use names attribute array 3) @Service annotations MUST not specify services of the same name.
Simon Nash: resolve JAVA-161 with document in email plus 3 changes:
Simon Nash: s/interfaces array/value attribute array/
Simon Nash: s/names attributes array/names attribute array/
Simon Nash: for JCA90045: The @Service annotation MUST NOT specify multiple services with the same name.
Yang Lei: Simon: motion to resolve JAVA-161 with the doc and the above changes.
Yang Lei: Anish: second it.
Yang Lei: No objections. Java-161 is resolved.
Yang Lei: Topic: JAVA-125: Allow call semantics to be specified in interface.java
Latest proposal:
Yang Lei: Simon: discuss the two changes
Yang Lei: Simon: move to resolve JAVA-125 with the document attached to the email.
Yang Lei: Second by Mike.
Yang Lei: No objections. Java-125 is resolved.
Yang Lei: Topic: JAVA-153: Java CI should have corresponding changes in JAVA-125
Latest proposal:
Yang Lei: Simon: discuss the proposal
Yang Lei: Dave: the first paragraph seems to suggest @Remotable is only way to specify remotable. Second paragraph, <interface.java> is referencing to an existing interface, it does not define it.
Yang Lei: Dave: the two paragraghs suggest there are two ways defining service interface. It should be one way with the additional metadata. So 158 apply to 161. 161 is additonal data on the same interface definition.
anish: i think the 2 paragraphs are correct, but it would be hard for someone new to figure the two ways of doing this. Regardless of the clarification we may make to the paragraphs, I think examples would help.
Yang Lei: Simon: by default applies to 158, while 161 specifies modifications..
Yang Lei: Dave: likes to merge the 2 paragraph together.
Simon Nash: By default, an SCA service interface defined by a Java interface or a Java implementation class and not annotated with a @Remotable annotation is inferred to be a local interface as defined by the SCA Assembly Model Specification [ASSEMBLY].
anish: There are four cases here, why don't we just enumerate them?
anish: would make it much simpler for the reader
Simon Nash: The <interface.java> XML element has an @remotable attribute which can be used to define such as interface as remotable, as defined by the SCA-J Common Annotations and APIs specification [JAVACAA].
anish: if we do it thru examples that would be ok
Simon Nash: The <interface.java> XML element has an @remotable attribute which can be used to define such an interface as remotable, as defined by the SCA-J Common Annotations and APIs specification [JAVACAA].
Yang Lei: Anish: the content is correct, what is missing is how 4 combinations work out.
Yang Lei: Anish: suggest to either adding a new paragraph or referencing an existing description on the 4 combinations.
Yang Lei: Simon: will follow 2.1 pattern...
Yang Lei: Dave/Mike: other issue: needs to change 123 according to Java-125 @Service changes.
Yang Lei: Mark: move on.
Yang Lei: Topic: JAVA-131: @Callback injection could be NULL (expanded to include refs, property and re-injection and callback
Proposed direction for resolution:
Yang Lei: Simon: discuss the proposal.
anonymous morphed into Pradeep
Yang Lei: Mike: agree on demanding injection of null to be consistent.
Yang Lei: Dave: +1
Yang Lei: Simon: reference always inject. Now discuss the 3 cases on callback.
Mark Combellack: Warning: We are almost out of time...
Yang Lei: Simon: always inject null even though callback is not in use for this invocation to be consistent.
Yang Lei: Mark: we will discuss the issue next time.
Yang Lei: Mark: call adjourns.