Minutes
Agenda bashing
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
Discussion on open issues.
issue 52
Issue 52 - Proposal in Jira
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
<Dieter Koenig>
The ';' should be deleted
Anish:
JMS based example does make sense.
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?
<anish>
yes </binding.ws> too
Motion approved unanimously. Issue 47 Closed Resolved.
Resolution: issue 47 is closed with proposal in the telcon chat
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.
