ISSUE 29: Ambigous Service Resolution

[Scott Vorthmann <scottv@tibco.com>]

http://www.osoa.org/jira/browse/ASSEMBLY-29

On Nov 26, 2007, at 10:08 AM, Dieter Koenig1 wrote:

>
> TARGET: SCA Assembly (although detected as a language implementation
> problem).
>
> 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:
>
>       <assign>
>          <copy>
>             <from partnerLink="NCName" endpointReference="myRole" />
>             <to variable="BPELVariableName" />
>          </copy>
>       </assign>
>
> 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) then it is not clear which of these service  
> endpoints
> should be used to create the EPR. A Java user of createSelfReference 
> () may
> specify a full URI in order to resolve the ambiguity, however, the  
> WS-BPEL
> runtime would not be able to make this decision.
>
> PROPOSAL: None so far.
>
> Kind Regards
> DK
>
>
> ---------------------------------------------------------------------
> 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
>
>