Formatted minutes of 2009-07-23 telcon

[Anish Karmarkar <Anish.Karmarkar@oracle.com>]

Attached.
Thanks to Khanderao for scribing.

-Anish
--

Title: SCA-BPEL - 2009-07-23

Hide IRC

- DRAFT -

OASIS SCA-BPEL TC

23 JUL 2009

Attendees

Present

Dieter Koenig, (IBM)

Martin Chapman, (Oracle Corporation)

Khanderao Kand, (Oracle Corporation)

Anish Karmarkar, (Oracle Corporation)

Ashok Malhotra, (Oracle Corporation)

Sanjay Patil, (SAP AG)

Najeeb Andrabi, (TIBCO Software Inc.)

Danny van der Rijn, (TIBCO Software Inc.)

Chair

Anish Karmarkar

Scribe

Khanderao Kand

Agenda:

http://lists.oasis-open.org/archives/sca-bpel/200907/msg00033.html

---

Contents

Topics

[1]  Agenda bashing

[2]  Approval of 2009-07-16 minutes

[3]  AI reivew

[4]  issue 52

[5]  Issue 47

Table of Resolutions

Table of Action Items

---

Action Items

New:

2009-07-23-1: Michael to present a new modified proposal for issue 52

---

Resolutions

• 2009-07-23-1: Minutes of the 2009-07-16 telcon located at http://lists.oasis-open.org/archives/sca-bpel/200907/msg00026.html approved
• 2009-07-23-2: issue 47 is closed with proposal in the telcon chat
• 2009-07-23-3: 2009-07-30 telcon canceled.

---

Minutes

<anish>

Agenda --

<anish>

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 Jul 16, 2009 minutes
http://lists.oasis-open.org/archives/sca-bpel/200907/msg00026.html
5. Action Items review
#0096 Anish - Create proposal for issue 41
#0099 Dieter Create proposal for issue 49
6. New Issues
NONE
7. Issue Discussion
6 open issues
a) Issue 52
CT generation (section 2.1.1) does not take into consideration the multRefFrom attribute
http://osoa.org/jira/browse/BPEL-52
Proposal in JIRA
b) Issue 47
Section 2.1.2 (initializePartnerRole) needs an example
http://www.osoa.org/jira/browse/BPEL-47
Proposal -- http://lists.oasis-open.org/archives/sca-bpel/200907/msg00032.html
c) Issue 49
BPEL process QName is assumed to be unique
http://www.osoa.org/jira/browse/BPEL-49
Proposal: http://lists.oasis-open.org/archives/sca-bpel/200907/msg00029.html
d) Issue 46
SBPEL3006 isn't deterministic
http://osoa.org/jira/browse/BPEL-46
e) Issue 41
SBPEL2022 has an incorrect 'MAY' and is not applied recursively
http://www.osoa.org/jira/browse/BPEL-41
Email discussion -
http://lists.oasis-open.org/archives/sca-bpel/200905/msg00035.html
http://lists.oasis-open.org/archives/sca-bpel/200905/msg00041.html
http://lists.oasis-open.org/archives/sca-bpel/200905/msg00044.html
8. AOB

Scribe: Khanderao Kand

Agenda bashing

 

Agenda approved.

Approval of 2009-07-16 minutes

 

Meeting of Jul 16, 2009 minutes approved unanimously.

Resolution: Minutes of the 2009-07-16 telcon located at http://lists.oasis-open.org/archives/sca-bpel/200907/msg00026.html approved

AI reivew

 

Open action items #0096 Anish - Create proposal for issue 41: Open

 

#0099 Dieter Create proposal for issue 49 : CLOSED

 

No new Issues.

 

Discussion on open issues.

issue 52

 

Issue 52 - Proposal in Jira

 

About section 2.1.1

 

Anish presented the proposal as in Jira.

<Dieter Koenig>

[SBPEL3004] In a WS-BPEL process definition, a variable MAY include an sca-bpel:multiReference extension element that declares that the variable represents a multi-valued reference.

 

Michael question: variable is already being mapped to reference. Anish: where does it say it is mapped. It is not.

<Dieter Koenig>

Committee Draft 02 Revision 2 - 11 June 2009

Anish:

Proposal needs to be modified to account variable mapping

 

Anish to Michael: can you write a proposal

Action: Michael to present a new modified proposal for issue 52

<Dieter Koenig>

[SBPEL3006] The introspected component type MUST include a reference with a multiplicity of either "0..n" or "1..n" that corresponds to a variable with the sca-bpel:multiReference element.

Dieter:

Make sure not to create redundancy.

Anish:

Component type generation algorithm should be in one place.

 

Issue open for the next meeting.

Issue 47

 

Anish presented proposal as in : http://lists.oasis-open.org/archives/sca-bpel/200907/msg00032.html

 

<service name="inventory">
<interface.wsdl interface="..." callbackInterface="..."/>
<binding.ws/>
<callback>
<binding.ws uri="http://example.org/callbackService?inventory"; />
</callback>
</service>

<Dieter Koenig>

The ';' should be deleted

<anish>

yes, thx dieter

<anish>

http://docs.oasis-open.org/opencsa/sca-bpel/sca-bpel-1.1-spec-cd02.pdf

<anish>

cd02 rev2: http://www.oasis-open.org/apps/org/workgroup/sca-bpel/download.php/32890/sca-bpel-1.1-spec-cd02-rev2.zip

Anish:

JMS based example does make sense.

 

Section 2.1.2

 

2.1.2 Handling @initializePartnerRole
[SBPEL2014] If a partner link is marked with initializePartnerRole="yes" then any component that uses this business process as an implementation MUST configure the corresponding service or reference using binding, promotion and wiring configuration that guarantees that the partner link's partner role will be initialized as soon as the partner link becomes active. If the partner link is mapped to a service, the callback binding would be the relevant binding for this requirement.

 

Common case: Wired reference.

 

Michael: BPEL specs expects EPR to be set. Anish: binding.ws supports EPR.

<anish>

<service name="inventory">
<interface.wsdl interface="..." callbackInterface="..."/>
<binding.ws/>
<callback>
<binding.ws> <wsa:EndpointReference><wsa:Address>uri="http://example.org/callbackService?inventory"</wsa:Address></wsa:EndpointReference>
</callback>
</service>

Anish:

It may be better to specific EPR instead of URI

<anish>

One way this can be achieved is by specifying a callback binding that
includes endpoint information, on a bidirectional SCA service of a
component. For example:
<service name="inventory">
<interface.wsdl interface="..." callbackInterface="..."/>
<binding.ws/>
<callback>
<binding.ws> <wsa:EndpointReference><wsa:Address>uri="http://example.org/callbackService?inventory"</wsa:Address></wsa:EndpointReference>
</callback>
</service>

<anish>

One way this can be achieved is by specifying a callback binding that
includes endpoint information, on a bidirectional SCA service of a
component. For example:
<service name="inventory">
<interface.wsdl interface="..." callbackInterface="..."/>
<binding.ws/>
<callback>
<binding.ws> <wsa:EndpointReference><wsa:Address>http://example.org/callbackService?inventory</wsa:Address></wsa:EndpointReference>

<anish>

One way this can be achieved is by specifying a callback binding that
includes endpoint information, on a bidirectional SCA service of a
component. For example:
<service name="inventory">
<interface.wsdl interface="..." callbackInterface="..."/>
<binding.ws/>
<callback>
<binding.ws><endpointReference><wsa:Address>http://example.org/callbackService?inventory</wsa:Address></endpointReference></callback>

<Dieter Koenig>

</service>

 

Motion moved by Michael: To resolve the issue 47 as per updated example in <service name="inventory">
<interface.wsdl interface="..." callbackInterface="..."/>
<binding.ws/>
<callback>
<binding.ws><endpointReference><wsa:Address>http://example.org/callbackService?inventory</wsa:Address></endpointReference></callback>

<Dieter Koenig>

</service>

<Sanjay>

there should be a </binding.ws> too?

 

Second by: Khanderao.

<anish>

yes </binding.ws> too

 

Motion approved unanimously. Issue 47 Closed Resolved.

Resolution: issue 47 is closed with proposal in the telcon chat

 

Michael: Reg. Issue 52

 

Struggling with forward reference.

<Sanjay>

Anish, it seems that I can't attend the next week's call. I guess you can't make it either. Do we still want to have the call?
Martin C OnEvent(alarm) AOB

 

Michael: To do backward reference.

Anish:

Both Anish and Sanjay are not available.

 

Motion to cancel the next weeks call

 

Moved by Michael R and Second by: Danny

 

Motion accepted unanimously.

Resolution: 2009-07-30 telcon canceled.

[End of Minutes]
Formatted on 2009-07-24 at 16:48:24 GMT-7

---

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

---

Schreiber diagnostics output

[Delete this section before publishing the minutes]

final validation: Title not specified, default title 'OASIS SCA-BPEL TC...' was assumed

citation-detection-scribed: Line 90: Check for possible unrecognized nick 'Michael question'

citation-detection-scribed: Line 96: Check for possible unrecognized nick 'Anish to Michael'

citation-detection-scribed: Line 135: Check for possible unrecognized nick 'Common case'

citation-detection-scribed: Line 137: Check for possible unrecognized nick 'Michael'

citation-detection-scribed: Line 190: Check for possible unrecognized nick 'Second by'

citation-detection-scribed: Line 198: Check for possible unrecognized nick 'Michael'

citation-detection-scribed: Line 206: Check for possible unrecognized nick 'Michael'

statistics: Schreiber found 150 input lines

edits: Schreiber found no text-edit commands

citation-detection-irc1: Line 5: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 13: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 29: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 34: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 35: Check for possible unrecognized nick 'Proposal -- http'

citation-detection-irc1: Line 39: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 40: Check for possible unrecognized nick 'Proposal'

citation-detection-irc1: Line 44: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 48: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 50: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 51: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 52: Check for possible unrecognized nick 'http'

command-scribe: Line 56: Khanderao is a nick for Khanderao Kand who will be named as scribe

command-scribe: Schreiber detected that this section was scribed online

citation-detection-irc1: Line 143: Check for possible unrecognized nick '<binding.ws> <wsa'

citation-detection-irc1: Line 156: Check for possible unrecognized nick '<binding.ws> <wsa'

citation-detection-irc1: Line 167: Check for possible unrecognized nick '<binding.ws> <wsa'

system: Transformer: SAXON 9.0.0.2

[End of Schreiber diagnostic output]