using subprocess outcome-variable to choose transitions no longer works
-----------------------------------------------------------------------
Key: JBPM-2832
URL:
https://jira.jboss.org/jira/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 6205
Reporter: Per Christian Henden
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.
The reason for using outcome= in the first place is to work around a bug. Will update
this ticket when
community.jboss.org becomes available so that I can link to that issue.
I'm not able to give more detail at the moment, as the jbpm 4.4 snapshots are not
available from the jboss maven repo.
From what I can remember, there are two problems here, first: the
variable set on the execution is not persisted/stored, then, when I force the variable to
be set (using createVariable instead of setVariable), the variable is not read/not found
when subprocess exits.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira