[
https://issues.apache.org/jira/browse/TUSCANY-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731328#action_12731328
]
Mike Edwards commented on TUSCANY-3144:
---------------------------------------
Turns out that the name given to ODE engine as the name of the Service is
nothing to do with the SCA service name and is also nothing to do with the WSDL
service/portType name. It is simply a label used by the ODE engine to map to
invocation points in the deployed BPEL processes.
So, all that Tuscany has to do is to use a unique name for each service of each
process - unique also for each usage of each BPEL process, where 2 or more SCA
components use the same BPEL process as their implementation.
The simplest design for this is to use a concatenation of the SCA component URI
and the SCA service name. This combination is guaranteed to be unique.
> Multiple BPEL processes which offere the same service name, used as component
> implementations, all get invoked when one of them is the target of an
> invocation
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3144
> URL: https://issues.apache.org/jira/browse/TUSCANY-3144
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA BPEL Implementation Extension
> Affects Versions: Java-SCA-2.0
> Reporter: Mike Edwards
> Assignee: Mike Edwards
> Fix For: Java-SCA-2.0
>
>
> The ODE BPEL engine is designed so that if 2 or more deployed BPEL processes
> offer the same service BY NAME (!!), then an invocation of that service
> causes ALL the processes offering that service to get dispatched. Currently,
> the service name used for the BPEL process is the derived from the
> partnerLink name of the BPEL process. Reusing partnerLink names causes the
> same service names to turn up on multiple BPEL processes - with the effect of
> this being the dispatch of all the BPEL processes involved.
> Found using the OASIS Assembly Testcase ASM_5013_TestCase, running with BPEL
> as the implementation language.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
