Today's minutes

[9:48] Mark Combellack: - 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 16th February 2009
http://www.oasis-open.org/committees/download.php/31257/SCA%20Java%20Minutes%202009-02-16.doc


0. Administration 
- Issue Status: Open: 29


1. Review action items:

Action Items that I believe are done:
2008-11-11-21: Mark, Jim and Mike to describe their use cases for JAVA-30
2009-02-09-02: SimonN and Mark to work up a better proposal for the function proposed by Mark for Issue 1
2009-02-13-03: Mark to raise a new issue for the JDK version of the SCA J spec
2009-02-16-02: Mark to create code to contrast the two options for direction for issue Java-1

Action Items that I believe are still to be done:
2008-07-15-02: Plamen to produce a proposal for JAVA-2
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
2008-11-11-27: Simon to raise issue on brain-damaged definition of @Service annotation (see comments in Nov F2F raw chat log)
2009-02-13-01: Mike to upload artifacts for JAVA-121 into OASIS Open SVN
2009-02-13-02: Chairs to look at how the files for JAVA-121 should be licensed
2009-02-16-01: Mike to fix the usage of "class loader" through out the spec
2009-02-16-03: Editors to make an editorial change when applying resolution of issue 117 (in section 8.3) to make a comment about the case difference in "someProperty/SomeProperty"


2. Blocking issues

All 3 blocking issues are waiting for updated proposals


3. Critical Issue discussion

a. JAVA-1: Accessing SCA Services from non-SCA component code
http://www.osoa.org/jira/browse/JAVA-1
Proposal: http://lists.oasis-open.org/archives/sca-j/200901/msg00094.html
Comparison of approaches: http://lists.oasis-open.org/archives/sca-j/200902/msg00161.html

The other critical issue is waiting for updated proposals.


4. New Issues

None


5. Other Open Issues discussion

a. JAVA-65: There is no lifecycle defined for SCA Components
http://www.osoa.org/jira/browse/JAVA-65
proposal: http://lists.oasis-open.org/archives/sca-j/200811/msg00095.html
Discussion at: http://lists.oasis-open.org/archives/sca-j/200811/msg00098.html

b. JAVA-102: Need to have a Name parameter on the @Service annotation
proposal: http://www.osoa.org/jira/browse/JAVA-102

c. 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-30
Updated proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00166.html

d. JAVA-76: Incorrect code in section 6.7.4 examples
http://www.osoa.org/jira/browse/JAVA-76
Proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00098.html

e. JAVA-129: Problems with Example 2b in chapter 7
http://www.osoa.org/jira/browse/JAVA-129
Outline proposal in Jira

f. JAVA-130: CAA - Problems with Example 3 in chapter 7
http://www.osoa.org/jira/browse/JAVA-130
Proposal PDF: http://lists.oasis-open.org/archives/sca-j/200902/msg00119.html
Proposal MS Word: http://lists.oasis-open.org/archives/sca-j/200902/msg00118.html
Comments on proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00123.html

g. JAVA-131: @Callback injection could be NULL
http://www.osoa.org/jira/browse/JAVA-131
Latest Proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00102.html

h. JAVA-132: Specification should require JDK 1.5 or above
http://www.osoa.org/jira/browse/JAVA-132
Proposal in Jira


6. Blocking issues waiting for updates/proposals

a. JAVA-104: RFC2119 Language is needed for CAA Specification
http://www.osoa.org/jira/browse/JAVA-104
No proposal

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

c. JAVA-119: JAA Conformance Section
http://www.osoa.org/jira/browse/JAVA-119
Updated proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00021.html
Alternative proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00049.html
Waiting for email discussion and new proposal


7. Critical issues waiting for updates/proposals

a. JAVA-54: Section 7.1 of the Java CAA Specification is unclear
http://www.osoa.org/jira/browse/JAVA-54
No proposal


8. AOB


---------------------------------------------------------------
Rotating scribe list:

Peter Walker Sun Microsystems (1)
Roberto Chinnici Sun Microsystems (2)
Peter Peshev SAP AG (2)
Ron Barack SAP AG (3)
Michael Beisiegel IBM (3)
Sanjay Patil SAP AG (3)
Vladimir Savchenko SAP AG (1)
Jim Marino Individual (4)
Pradeep Simha TIBCO Software Inc. (5)
Vamsavardhana Chillakuru IBM (3)
Bryan Aupperle IBM (6)
Plamen Pavlov SAP AG (2)
Ashok Malhotra Oracle Corporation (6)
Simon Nash Individual (4)
Graham Charters IBM (1)
Martin Chapman Oracle Corporation (6) 
Yang Lei (4)
Mike Edwards IBM (7)
Meeraj Kunnumpurath Individual (3)
Anish Karmarkar Oracle Corporation (

[10:04] Bryan Aupperle: Scribe: Bryan Aupperle

[10:08] Bryan Aupperle: Topic: Agenda Bashing

[10:08] Bryan Aupperle: Accepted as posted;

[10:08] Bryan Aupperle: Topic Approval of minutes

[10:09] Bryan Aupperle: Resolution: Minutes accepted w/o

[10:09] Bryan Aupperle: Topic: Action Items

[10:09] Bryan Aupperle: 2008-11-11-21 - Done

[10:10] Bryan Aupperle: 2009-02-09-02 - Done

[10:10] Bryan Aupperle: 2009-02-13-03 - Done

[10:10] Bryan Aupperle: 2009-02-16-02 - Done

[10:11] Bryan Aupperle: 2008-07-15-02 - Plamen proposes CNA, Dave does not aggree - Reasigned to Dave.

[10:11] Bryan Aupperle: All others pending.

[10:11] Bryan Aupperle: Topic: JAVA-1

[10:12] Bryan Aupperle: http://www.osoa.org/jira/browse/JAVA-1

[10:12] Bryan Aupperle: Mark reviews proposal

[10:17] Bryan Aupperle: Simon notes that it needs to be possible to specify a class loader.  Mark agrees.

[10:18] Bryan Aupperle: Mark wonders if we also need to be able to passi a properties object.

[10:19] Bryan Aupperle: s/passi/pass in/

[10:20] Bryan Aupperle: Dave points out we would need to stanardize property names.

[10:20] Bryan Aupperle: Mark points out the proposal proposes one standard name.

[10:21] Bryan Aupperle: Conclusion is that the ability to pass in a property object is needed.

[10:22] Bryan Aupperle: Discussion of Raymond's note: http://lists.oasis-open.org/archives/sca-j/200902/msg00163.html

[10:23] Bryan Aupperle: AI: (Mark) Update proposal based on today's discussion.

[10:24] Bryan Aupperle: Specific points: Class loader, properties and look at reference injection.

[10:25] Bryan Aupperle: Topic: JAVA-65

[10:28] anish you mean doc00002.doc

[10:29] Bryan Aupperle: Mark reviews the proposal

[10:31] Bryan Aupperle: Anish: Remind us why we need postInit and preDestroy.

[10:31] Bryan Aupperle: Mark: There can be dependency issues with using references during Init and Destroy.

[10:35] Bryan Aupperle: Discussion of these dependencies.

[10:42] Bryan Aupperle: Simon: This can lead to s significant number of unnecessary postInit and preDestroy calls.

[10:43] Bryan Aupperle: Mark: Would have to use catch blocks to guard against exceptions.

[10:44] Bryan Aupperle: Anish: If there circular references, we could get into an infinite loop.

[10:46] Bryan Aupperle: Dave: Reference to a stateless component is always valid.  postInit and preDestroy are not needed for stateless components.

[10:47] Bryan Aupperle: Simon: How does client component know if a service implementation it references is stateless or not?

[10:48] Bryan Aupperle: Mike Edwards has observed that this is all too complex; especially since we have removed request and conversation scopes.

[10:49] Bryan Aupperle: This suggests we do not need postInit and preDestroy.

[10:51] Bryan Aupperle: Simon: Still useful for composite scope.

[10:55] Bryan Aupperle: Dave: It may be possible to use EagerInit to break the circular case.

[10:57] Bryan Aupperle: AI (Mark): Update proposal for JAVA-65 to remove postInit and preDestroy.

[10:57] Bryan Aupperle: Topic: JAVA-77

[10:58] Bryan Aupperle: http://www.osoa.org/jira/browse/JAVA-77

[10:59] Bryan Aupperle: Mark: Since this issue was raised,  the assembly removed WSDL 2.0 support.

[11:00] Bryan Aupperle: Mark reviews the current proposal which reflects this change.

[11:00] Bryan Aupperle: Anish: Why do we need this, since we already reference JAX-WS for mapping to/from WSDL.

[11:04] Mark Combellack: Sorry - was not such a quick issue as I thought

[11:05] Bryan Aupperle: Topic: AOB

sca-j message