OASIS Logo

OASIS SCA-BPEL TC

28 JAN 2010

Attendees

Present
Mike Edwards, (IBM)
Dieter Koenig, (IBM)
Martin Chapman, (Oracle Corporation)
Anish Karmarkar, (Oracle Corporation)
Sanjay Patil, (SAP AG)
Danny van der Rijn, (TIBCO Software Inc.)
Chair
Sanjay Patil
Scribe
Dieter Koenig
Agenda:
http://lists.oasis-open.org/archives/sca-bpel/201001/msg00026.html

Contents

Topics
[1]  Agenda bashing
[2]  Approval of 2010-01-21 minutes
[3]  Review of Action Items
[4]  New Issues
[5]  issue 62
[6]  Issue 58
[7]  TA document
Table of Resolutions
Table of Action Items

Action Items

New:
2010-01-28-1: Mike E. will create the updated proposal
2010-01-28-2: Anish to produce test assertions for SBPEL2023

Resolutions

Minutes

<Sanjay>
Agenda -
<Sanjay>
1. Roll Call
http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/roster.php
2. Appointment of scribe
Scribe list attached below
3. Agenda bashing
4. Approval of 2010-01-21 minutes
http://lists.oasis-open.org/archives/sca-bpel/201001/msg00023.html
5. Review of Action Items
#0109 Mike Edwards - Send instructions for running the Assembly tests
#0115 Anish Karmarkar - Prepare an updated version of the proposal for issue 58 (rewriting section 2.1.1 to remove the nested-if)
#0117 Danny - Create a new issue and a proposal for the 0..1 case (related to issue 53)
#0122
Dieter - update the spec to remove "." from assertion lables
DONE
#0123
Sanjay - update the TA doc to sync up with the new CD rev
6. New Issues
None
7. Testing
Planned schedule -
Jan 21 - Revised specification draft (DONE)
Feb 4 - Update Test Assertion Document
Mar 4 - Test Case Creation
Mar 25 - Review and finalization of Test Cases
Apr 1 - Go for 2nd PR
a> Planning/volunteers for updating the test assertions document (DONE)
b> MikeE to send instructions for running the tests
Here is a rough break up of work for creating the test cases. More volunteers are appreciated.
Sanjay - SBL-TA-1001 to SBL-TA-2018
Anish - SBL-TA-3001 to SBL-TA-3026
8. Issue Discussion
a) Issue 58 - Need to add Capability to indicate that a PartnerLink should be ignored when introspecting the ComponentType of a BPEL process
http://www.osoa.org/jira/browse/BPEL-58
Email discussion: http://lists.oasis-open.org/archives/sca-bpel/200909/msg00016.html
Awaiting a new proposal from Anish based on 2009-10-29 concall discussions
9. AOB
-----------------------------------------
Scribe list:
* Kand, Khanderao (Last scribed: 2009-07-23): 6
* Rowley, Mr Michael (Last scribed: 2009-08-06): 8
* Koenig, Mr Dieter (Last scribed: 2009-11-05): 13
* Malhotra, Mr Ashok (Last scribed: 2009-11-12): 14
* Andrabi, Mr. Najeeb (Last scribed: 2009-11-19): 13
* Chapman, Dr Martin (Last scribed: 2009-12-10): 11
* Patil, Sanjay (Last scribed: 2009-12-17): 1
* van der Rijn, Danny (Last scribed: 2010-01-07): 12
* Anish Karmarkar (Last scribed: 2010-01-14): 3
* Edwards, Mike (Last scribed: 2010-01-21): 2

Scribe: Dieter Koenig

Agenda bashing

 
Agenda approved

Approval of 2010-01-21 minutes

 
http://lists.oasis-open.org/archives/sca-bpel/201001/msg00023.html
 
Minutes approved
Resolution: Minutes of 2010-01-28 call located at http://lists.oasis-open.org/archives/sca-bpel/201001/msg00023.html approved

Review of Action Items

 
#0109 Mike Edwards - Send instructions for running the Assembly tests
#0115 Anish Karmarkar - Prepare an updated version of the proposal for issue 58 (rewriting section 2.1.1 to remove the nested-if)
#0117 Danny - Create a new issue and a proposal for the 0..1 case (related to issue 53)
#0122
Dieter - update the spec to remove "." from assertion lables
DONE
#0123
Sanjay - update the TA doc to sync up with the new CD rev
 
#0109: work in progress
 
#0115: done: proposal sent - still needs an update: deferred to issue 58 discussion
 
#0117: done
 
#0122: done
 
#0123: work in progress

New Issues

 
issue 62
<anish>
http://lists.oasis-open.org/archives/sca-bpel/201001/msg00029.html
 
Motion (Danny) second (Anish): open BPEL-62 - passed unanimously
Resolution: issue 62 is now open
<anish>
proposal for 62 - http://lists.oasis-open.org/archives/sca-bpel/201001/doc00000.doc
 
New agenda topic - discussion of issue 62

issue 62

<DannyvanderRijn>
current proposed: [SBPELXXXX] If the domain composite includes a wire for an optional reference, then the SCA-BPEL Runtime MUST configure the reference.
<DannyvanderRijn>
new proposed: [SBPELXXXX] If the domain composite includes a wire for *any* reference, then the SCA-BPEL Runtime MUST configure the reference.
Mike E:
editorial issue: the word "required", e.g., in "required reference" in 2.1.1, must be replaced as "required" is an RFC term
Mike E:
if SCA provides a wire then it *must* be made available to BPEL
 
Are there rules SCA-Assembly requires *every* C&I spec to follow?
 
(no general agreement in SCA-Assembly TC about such "meta-spec" rules)
Danny:
need rewording for resolution part (a)
Anish:
should distinguish 0..1 and 0..N cases
<Mike Edwards>
Proposal1: [SBPELXXXX] If the component configuration includes a wire for a 0..1 or 1..1 multiplicity reference, then the SCA-BPEL Runtime MUST configure the partner role of the partnerLink for that reference.
<Mike Edwards>
Proposal1: [SBPELXXXX] If the component configuration includes a wire for a 0..1 or 1..1 multiplicity reference, then the SCA-BPEL Runtime MUST configure the partner role of the partnerLink for that reference.
<Mike Edwards>
Proposal1: [SBPELXXXX] If the component configuration includes a wire for a 0..1 or 1..1 multiplicity reference, then the SCA-BPEL Runtime MUST configure the partner role of the partnerLink associated with that reference.
<DannyvanderRijn>
where would you put this text?
Mike E:
this text should appear at the end of 2.1.1 after #4. as a separate paragraph
<Mike Edwards>
Proposal1: [SBPELXXXX] If the component configuration includes a wire for a 0..n or 1..n multiplicity reference, then the SCA-BPEL Runtime MUST configure the sca-bpel:multiRefFrom variable associated with the partnerLink associated with that reference.
<anish>
wire(s)
 
serviceReferenceList:
<xsd:element name="serviceReferenceList">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="sref:service-ref"
minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<Mike Edwards>
[SBPELXXXX] For a 0..n or 1..n multiplicity reference, then the SCA-BPEL Runtime MUST configure the sca-bpel:multiRefFrom variable associated with the partnerLink associated with that reference, using a serviceReferenceList which contains 1 service-ref element for each configured target for the reference.
 
Resolution part (b) is in new section 3.5
 
Discussion continued on mailing list, using a proposal updated with the two statements above for section 2.1.1
Action: Mike E. will create the updated proposal

Issue 58

<anish>
http://lists.oasis-open.org/archives/sca-bpel/201001/msg00032.html
 
See proposal submitted by Anish (link above)
<Sanjay>
is that violin in the background?
<Martin C>
maybe we can include a summary in an appendix
<Martin C>
it would be nice to have it all in one place
DannyvanderRijn apologies. have to drop for another meeting
<Martin C>
I have to drop for two meetings in parallel
Martin C only one call now as bindings was cancelled
 
Discussion on 58 continued on mailing list and the next call

TA document

Sanjay:
test assertions document ready for review
 
9. AOB
Action: Anish to produce test assertions for SBPEL2023
 
Meeting adjourned

[End of Minutes]
Formatted on 2010-01-28 at 09:31:18 GMT-8

Minutes formatted by Schreiber, a collection of XSLT stylesheets by Bob Freund modeled after David Booth's scribe