Hide Forgot
++ This bug is a clone of bug 779523 ++ Affects: Release Notes Date of First Response: 2010-02-01 22:44:58 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/452333 project_key: SOA Platform issue for JBPM-2778.
Link: Added: This issue incorporates JBPM-2778
The issue is valid and resolving it should take a few hours.
Resolving, project issue JBPM-2778 is done.
Approved for SOA 4.3 CP03
verified fix with fisheye, it is in ER1
Draft Release Notes text states: https://jira.jboss.org/jira/browse/JBPM-2778 If accept-propagation-events="false" was set on both an action and a script, the script would, erroneously, be executed on the propagated event. This was contrary to the best practice documented in the jBPM Reference Manual. This happened because org.jbpm.graph.action.Script overrode the org.jbpm.graph.def.Action.read() method and did not recognise the accept-propagation-events attribute. To fix this problem, the JpdlXmlParser has been changed so that it will now apply accept- propagated-events and async attributes to any action. Also, the jPDL XML schema now permits the async and accept-propagated-events attributes to be used in the script and mail element, respectively. As a result, the software now conforms more closely to the standards in the document.
> If accept-propagation-events="false" was set on both an action and a script, Setting on "both an action and a script" is not a indispensable condition. This line would be > If accept-propagation-events="false" was set on a script, Sorry, my description in JBPM-2778 was not accurate.
That is okay. I have amended it now. Cheers.
Tests passing in CR2