[
https://jira.jboss.org/browse/JBPM-2832?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu updated JBPM-2832:
------------------------------
Attachment: JBPM-2832.patch
Update the JBPM-2833 testcase to verify it could correct this issue, too.
using subprocess outcome-variable to choose transitions no longer
works
-----------------------------------------------------------------------
Key: JBPM-2832
URL:
https://jira.jboss.org/browse/JBPM-2832
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.x
Environment: JBPM 4.4-SNAPSHOT, revision 6232
Reporter: Per Christian Henden
Attachments: JBPM-2832.patch, Stacktrace-jbpm-2832.txt.txt
This worked in JBPM 4.3.
I use the outcome= construct of subprocess to choose transitions to take when the
subprocess has completed.
<sub-process name="mySubProc" sub-process-key="SubProc"
outcome="#{result}">
<transition name="to A" to="A"/>
<transition name="to B" to="B"/>
<transition name="to C" to="C"/>
</sub-process>
The subprocess uses execution.setVariable("result", value) in an event listener
that runs on start in the process end nodes to write the #{result} variable.
When the subprocess exits, this stack trace (the full stack trace attached as file) is
shown:
javax.el.PropertyNotFoundException: Cannot resolve identifier 'result'
The reason for using outcome= in the first place is to work around a bug, as reported in
https://community.jboss.org/message/526547 and
https://jira.jboss.org/jira/browse/JBPM-2833
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira