Hide Forgot
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000006kYtv project_key: SOA See jbpm-3151 for details When incorporating this into SOA it is important that the SOA configuration has the asynchronous behaviour, i.e. the following must be configured <boolean name="jbpm.sub.process.async" value="true"/>
Link: Added: This issue Cloned from SOA-2991
Link: Added: This issue depends JBPM-3151
Link: Added: This issue relates to SOA-2990
Writer: Added: dlesage
This has been sorted in 4.3 CP05 ER1
Verified on 4.3 CP05 ER1. Both sync/async invocation.
The issue was tested on 3.2.10.SP1 tag. But after the tag there was created a new revision that applies similar patch to jbpm3-jbpm-3.2-soa branch. As the situation is confusion please verify that repository versions are in sync. We will close the issue after that.
Release Notes Docs Status: Added: Documented as Known Issue Release Notes Text: Added: https://issues.jboss.org/browse/JBPM-3151 The way in which a sub-process is signalled was changed by a patch which altered behaviour so that super processes would resume execution in separate transactions. This change resulted in the system contradicting the synchronous signaling behavior of jBPM as described in Section 6.11 of the jBPM Reference Guide and also lead to a different result in the case of a roll-back.To resolve this problem, a configuration switch has been added to allow both the new asynchronous sub-process signalling, and revert the default signaling mode to be synchronous as before.
The code was first committed as a one-off patch in .../tags/jbpm-3.2.10_SOA-2990. It was then pulled across to the 3.2.10.SP branch (r6906, r6907), and later to the jbpm-3.2-soa branch (r6911). The 3.2.10.SP1 tag was created from the 3.2.10.SP branch (r6910). The code differnces between the 3.2.10.SP1 tag and the jbpm-3.2-soa branch at this time can be verified with: svn diff http://anonsvn.jboss.org/repos/jbpm/jbpm3/branches/jbpm-3.2-soa@6911 \ http://anonsvn.jboss.org/repos/jbpm/jbpm3/tags/3.2.10.SP1@6910 The only differences are in the version information, and not in the code.
Verified. See comment from Julian: added on - 09/May/11 1:00 PM
Temporarily reopening to update release note status.
Release Notes Docs Status: Removed: Documented as Known Issue Added: Documented as Resolved Issue