[
https://issues.apache.org/jira/browse/TUSCANY-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Kolb updated TUSCANY-3083:
---------------------------------
Attachment: Warehouse.zip
It seems like there's some problem with the invocation of partner links. The
code's working fine with only one partnerlink as a provider e.g. "warehouse".
But if there comes in the second link there are some strange exceptions with
the ODEScheduler after hanging for some time. It always fails when invoking two
partner links in the activity. I attached the Code so you
can take a look at it and hopefully reproduce it. In brief: the
activity.ActivityTestCase is the test case. The BPEl invokes "warehouse" checks
if isAvailable is true else it invokes the "wholesaler" and returns the result.
> BPEL can invoke only first Service used
> ---------------------------------------
>
> Key: TUSCANY-3083
> URL: https://issues.apache.org/jira/browse/TUSCANY-3083
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA BPEL Implementation Extension
> Affects Versions: Java-SCA-1.4
> Environment: WinXP SP2, JRE 1.6.0_12
> Reporter: Arne Schramm
> Attachments: Warehouse.zip
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> A BPEL Process containing several services to invoke, invokes always just the
> first service. the reason for that can be found in the class
> "ODEExternalService" of the "implementation-bpel-ode" module. the method
> "public void invoke(final PartnerRoleMessageExchange
> partnerRoleMessageExchange) " always uses the first element of the array
> containing all references to invoke a service.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
