[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [sca-assembly] ISSUE 29: Ambigous Service Resolution
FYI, I sent a request to the SCA-BPEL TC in order to let this issue be
discussed there first - as discussed and decided in today's SCA-Assembly TC
call.
Kind Regards
DK
----- Forwarded by Dieter Koenig1/Germany/IBM on 04.12.2007 18:32 -----
From: Dieter Koenig1/Germany/IBM@IBMDE
To: sca-bpel@lists.oasis-open.org
Date: 04.12.2007 18:30
Subject: [sca-bpel] NEW ISSUE: Ambigous Service Resolution
(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: <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 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]