[
https://issues.apache.org/jira/browse/TUSCANY-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731347#action_12731347
]
Mike Edwards commented on TUSCANY-3144:
---------------------------------------
Updated the name used for each BPEL Process service to use the combination
ComponentURI+ServiceName in BPELInvoker and TuscanyProcessConfImpl classes:
794181 + 794188
> 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.
