[TUSCANY-3144] 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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Java-SCA-2.x
• Fix Version/s: Java-SCA-2.x
• Component/s: Java SCA BPEL Implementation Extension
• Assignee: Mike Edwards
• Reporter: Mike Edwards
• Due: 24/Jul/09
• Created: 15/Jul/09 07:44
• Updated: 18/Sep/10 10:48
• Resolved: 17/Jul/09 12:49

Description

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.