[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Today's minutes
[10:13] 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 for 6th March 2009 http://www.oasis-open.org/committees/download.php/31568/SCA%20Java%20Minutes%202009-03-06.doc 0. Administration - Issue Status: Open: 28 - Daylight saving starts March 8 in the US - calls will be an hour earlier for those in Europe from 9th March for 3 weeks - LOA: Graham Charters is on LOA until 17th March 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-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-19-02: Mark to update proposal for JAVA-65 to remove @PostInit and @PreDestroy. 2009-02-23-01: Anish to write proposal for JAVA-119 2009-02-23-02: Mike to provide proposal for JAVA-54 2009-03-23-03: Editors to make sure org.osoa replaced with org.oasisopen 2009-02-23-05: Simon to try and create alternate example for JAVA-129 2009-02-23-06: Simon to write proposal for Java 131 2. Blocking issues The other 3 blocking issues are waiting for updated proposals. 3. Critical Issue discussion The other 2 critical issues are waiting for an updated proposal. 4. New Issues a. JAVA-139: Default value for SCA property is not supported for java implementations http://www.osoa.org/jira/browse/JAVA-139 Proposal in Jira 5. Other Open Issues discussion a. 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 Updated proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00166.html b. JAVA-133: Unannotated properties and references http://www.osoa.org/jira/browse/JAVA-133 Proposal: In Jira c. JAVA-135: Problems with definition of @Service annotation http://www.osoa.org/jira/browse/JAVA-135 Proposal: In Jira d. JAVA-102 - Need to have a Name parameter on the @Service annotation http://www.osoa.org/jira/browse/JAVA-102 Updated proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00222.html e. JAVA-137: Java C&I Constructor Examples are incorrect http://www.osoa.org/jira/browse/JAVA-137 Proposal in Jira f. JAVA-2: Determining the data binding to use (e.g. JAXB or SDO) http://www.osoa.org/jira/browse/JAVA-2 Updated proposal: http://lists.oasis-open.org/archives/sca-j/200903/msg00015.html 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 Proposal: http://lists.oasis-open.org/archives/sca-j/200903/msg00012.html b. JAVA-105: RFC2119 Language is needed for C&I Specification http://www.osoa.org/jira/browse/JAVA-105 Proposal (PDF): http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/31463/sca-javaci-1.1-spec-wd04_proposal.pdf Proposal (Word): http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/31464/sca-javaci-1.1-spec-wd04_proposal.doc Waiting for email feedback and resulting updates 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 b. 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 Updated code proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00225.html Waiting for updated code proposal 8. AOB --------------------------------------------------------------- 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) Graham Charters IBM (1) Yang Lei (4) Mike Edwards IBM (7) Meeraj Kunnumpurath Individual (3) Bryan Aupperle IBM (7) Ashok Malhotra Oracle Corporation (7) Simon Nash Individual (5) Anish Karmarkar Oracle Corporation (9) Martin Chapman Oracle Corporation (7)
[10:38] Bryan Aupperle: Scribe: Bryan
[10:38] Bryan Aupperle: Topic: Approval of Minutes
[10:40] Bryan Aupperle: Simon notes there is a missing AI for him for Java 98
[10:40] Bryan Aupperle: AI (Simon) produce an updated proposal for issue 98
[10:40] Bryan Aupperle: Minutes approved W/O
[10:41] Bryan Aupperle: Topic: Action Items
[10:41] Bryan Aupperle: No Updates
[10:43] Bryan Aupperle: Topic: Java 139
[10:43] Bryan Aupperle: http://www.osoa.org/jira/browse/JAVA-139
[10:46] Bryan Aupperle: Vamsi review issue
[10:47] Bryan Aupperle: Discussion about values and type conversion.
[10:48] Bryan Aupperle: We do not have sufficient voting members present to open the issue.
[10:48] Dave Booz Plamen, when you join the call, please let us know
[10:48] Bryan Aupperle: Topic: Java 77
[10:48] Bryan Aupperle: http://www.osoa.org/jira/browse/JAVA-77
[10:48] Bryan Aupperle: http://lists.oasis-open.org/archives/sca-j/200902/msg00166.html
[10:49] Bryan Aupperle: Mark reviews issue and proposal
[10:50] Plamen: I'm online
[10:51] Bryan Aupperle: Motion (Mark, second Bryan) Resolve issue Java 77 with the following:
[10:51] Mark Combellack: the reference to WSDL 2.0 should be removed from section 1.2 Normative References. Change from: 39 [WSDL] WSDL Specification, 40 WSDL 1.1: http://www.w3.org/TR/wsdl, 41 WSDL 2.0: http://www.w3.org/TR/wsdl20/ To: 39 [WSDL] WSDL Specification, 40 WSDL 1.1: http://www.w3.org/TR/wsdl,
[10:52] Bryan Aupperle: Resolution: Motion passes w/o
[10:53] Bryan Aupperle: Topic: Java 139 (resumed)
[10:54] Bryan Aupperle: Motion (Simon second Vamsi): Open issue 139
[10:54] Bryan Aupperle: Resolution: Motion passes w/o
[10:54] Bryan Aupperle: Topic: http://www.osoa.org/jira/browse/JAVA-133
[10:54] Bryan Aupperle: Proposal in JIRA
[10:54] Bryan Aupperle: Simon reviews proposal
[10:58] Bryan Aupperle: Motion (Simon, second Vamsi) Resolve issue 133 as proposed in JIRA
[10:59] Bryan Aupperle: Resolution: Motion passes w/o
[10:59] Bryan Aupperle: Topic: Java 135
[10:59] Bryan Aupperle: http://www.osoa.org/jira/browse/JAVA-135 Proposal: In JIRA
[11:06] Bryan Aupperle: Discussion on need for a Void.class value
[11:06] Bryan Aupperle: Motion (Simon, second Anish) resolve issue 135 as proposed in JIRA
[11:06] Bryan Aupperle: Resolution: Motion passes w/o
[11:07] Bryan Aupperle: Topic: Java 102
[11:07] Bryan Aupperle: http://www.osoa.org/jira/browse/JAVA-102
[11:07] Bryan Aupperle: Proposal: http://lists.oasis-open.org/archives/sca-j/200902/msg00222.html
[11:08] Bryan Aupperle: Simon reviews proposal
[11:10] Bryan Aupperle: Discussion on value of the added complexity of having multiple ways to specify a single name.
[11:12] Bryan Aupperle: Dave: Should there be a statement about the relative ordering of names and interfaces?
[11:13] Bryan Aupperle: Simon: Agrees there should be.
[11:13] Simon Nash: . If the names parameter is specified, the service names are the Strings declared in the names attribute array
[11:14] Simon Nash: If the names parameter is specified, the service name for each interface is the String declared in the corresponding position in the names attribute array
[11:15] Simon Nash: If the names parameter is specified, the service name for each interface in the interfaces attribute array is the String declared in the corresponding position in the names attribute array
[11:17] Simon Nash: proposal in email, with change: lines 1695/1696. replace "If the names parameter is specified, the service names are the Strings declared in the names attribute array" by "If the names parameter is specified, the service name for each interface in the interfaces attribute array is the String declared in the corresponding position in the names attribute array"
[11:18] Bryan Aupperle: Motion (Simon, second Dave) Resolve issue 102 as per line above.
[11:18] Bryan Aupperle: Resolution: Motion passes w/o
[11:19] Bryan Aupperle: Topic: Issue 137http://www.osoa.org/jira/browse/JAVA-137
[11:19] Bryan Aupperle: Proposal in JIRA
[11:19] Bryan Aupperle: Simon review proposal
[11:24] Mark Combellack: http://lists.oasis-open.org/archives/sca-j/200903/msg00028.html
[11:26] Bryan Aupperle: Simon Reviews his addition to Mike's proposal.
[11:27] Bryan Aupperle: Motion (Simon, second Dave) Resolve Issue 137 with proposal in JIRA and the addition in message 28.
[11:27] Bryan Aupperle: Resolution: Motion passes w/o
[11:27] Bryan Aupperle: Topic: Java 2
[11:28] Bryan Aupperle: http://www.osoa.org/jira/browse/JAVA-2
[11:28] Bryan Aupperle: Proposal: CNA
[11:29] Bryan Aupperle: Motion (Dave, second Plamen) Close issue 2 as No-Action
[11:29] Bryan Aupperle: Simon: Will this cause any interoperability problems?
[11:30] Bryan Aupperle: Dave: No, only portability. Wire format details will cover interoperability.
[11:33] Bryan Aupperle: Continued discussion on this aspect.
[11:35] Bryan Aupperle: Simon: What about wiring two java interfaces one which uses SDO and one which uses JAX-B? What are the compatibility rules?
[11:35] Bryan Aupperle: Dave: That is a separate issue.
[11:37] Bryan Aupperle: Ron has pointed out that it is always possible to determine if an interface is using SDO or JAX-B.
[11:38] Bryan Aupperle: Resolution: Motion passes w/o
[11:41] Bryan Aupperle: Topic: Issue 134
[11:42] Bryan Aupperle: http://www.osoa.org/jira/browse/JAVA-134
[11:43] Bryan Aupperle: Proposal in JIRA
[11:44] Bryan Aupperle: Simon notes the C&I spec contradicts itself on this topic.
[11:44] Bryan Aupperle: Simon: Is there any reason not to do this?
[11:45] Bryan Aupperle: Dave: This would allow a developer to not create an interface.
[11:46] Bryan Aupperle: Simon: Is it possible to map a Java class to WSDL?
[11:47] Bryan Aupperle: AI (Simon) Investigate if a class (as opposed to an interface) can be mapped to WSDL.
[11:47] Bryan Aupperle: No concern with the callback aspect of the proposal.
[11:48] Bryan Aupperle: Topic: Java 138
[11:49] Bryan Aupperle: http://www.osoa.org/jira/browse/JAVA-138
[11:49] Bryan Aupperle: Proposal in JIRA
[11:51] Bryan Aupperle: Dave reviews proposal
[11:52] Bryan Aupperle: Motion: (Dave, second Bryan) Resolve issue 138 as proposed in JIRA
[11:52] Bryan Aupperle: Resolution: Motion passes w/o
[11:53] Bryan Aupperle: Topic: AOB - Straggler role.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]