[JBoss JIRA] Created: (JBPM-2832) using subprocess outcome-variable to choose transitions no longer works
9:42 a.m.
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
9:46 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2832) using subprocess outcome-variable to choose transitions no longer works
[
https://jira.jboss.org/jira/browse/JBPM-2832?page=com.atlassian.jira.plug...
]
Per Christian Henden updated JBPM-2832:
---------------------------------------
Description:
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, as reported in
https://community.jboss.org/message/526547
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.
was:
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.
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, as reported in
https://community.jboss.org/message/526547
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
10:12 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2832) using subprocess outcome-variable to choose transitions no longer works
[
https://jira.jboss.org/jira/browse/JBPM-2832?page=com.atlassian.jira.plug...
]
Per Christian Henden updated JBPM-2832:
---------------------------------------
Environment: JBPM 4.4-SNAPSHOT, revision 6232 (was: JBPM 4.4-SNAPSHOT, revision
6205)
Description:
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
was:
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, as reported in
https://community.jboss.org/message/526547
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.
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 6232
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.
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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:14 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2832) using subprocess outcome-variable to choose transitions no longer works
[
https://jira.jboss.org/jira/browse/JBPM-2832?page=com.atlassian.jira.plug...
]
Per Christian Henden updated JBPM-2832:
---------------------------------------
Attachment: Stacktrace-jbpm-2832.txt.txt
The complete stack trace.
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 6232
Reporter: Per Christian Henden
Attachments: 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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:43 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2832) using subprocess outcome-variable to choose transitions no longer works
[
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
2:45 a.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2832) using subprocess outcome-variable to choose transitions no longer works
[
https://jira.jboss.org/browse/JBPM-2832?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu reassigned JBPM-2832:
---------------------------------
Assignee: Huisheng Xu
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
Assignee: Huisheng Xu
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
1 a.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2832) using subprocess outcome-variable to choose transitions no longer works
[
https://jira.jboss.org/browse/JBPM-2832?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu resolved JBPM-2832.
-------------------------------
Fix Version/s: jBPM 4.4
Resolution: Done
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
Assignee: Huisheng Xu
Fix For: jBPM 4.4
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
5325
days inactive
5391
days old
6 comments
2 participants
participants (2)
-
Huisheng Xu (JIRA) -
Per Christian Henden (JIRA)