Issue 16 - Ambigous Service Resolution

Issue entered:
http://www.osoa.org/jira/browse/BPEL-16

Regards,
Alex Yiu


Dieter Koenig1 wrote:
> (The SCA-Assembly TC has decided to let this issue be discussed in the
> SCA-BPEL TC first.)
>
> -------------------------------------------------------
>
> Reference:
> Original issue ASSEMBLY-29: http://www.osoa.org/jira/browse/ASSEMBLY-29
>
> -------------------------------------------------------
>
> TARGET: SCA-BPEL (at least as a starting point).
>
> DESCRIPTION: WS-BPEL processes may assign an EPR (pointing to themselves)
> to a variable in order to e.g. pass it as a callback EPR to another service
> partner: partnerLink="NCName" endpointReference="myRole" /> variable="BPELVariableName" /> 
> If the component's interface (the WSDL port type referenced by the WS-BPEL
> partner link type) is exposed as a service multiple times (e.g. with
> different bindings or with different policies) then it is not clear which
> of these service endpoints should be used to create the EPR. The WS-BPEL
> runtime is not able to make this decision.
>
> PROPOSAL: None so far.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>
>