[
https://jira.jboss.org/jira/browse/JBPM-2833?page=com.atlassian.jira.plug...
]
Huisheng Xu updated JBPM-2833:
------------------------------
Attachment: JBPM-2833.patch
If we use fork to create child execution for process instance and let any of child
executions end directly. Then the end activity name in ended process instance and history
process instance will miss.
attach patch and testcase to reproduce.
Null end activity after fork
----------------------------
Key: JBPM-2833
URL:
https://jira.jboss.org/jira/browse/JBPM-2833
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Reporter: Per Christian Henden
Assignee: Huisheng Xu
Attachments: ForkResultsInNullEndActivity.java, JBPM-2833.patch,
process.jpdl.xml, process.png
I'm experiencing that the end activity of a certain sub-process is always null,
resulting in the default transition being taken out from the sub-process. I expected that
the end activity of the sub-process would govern which transition is taken, like in the
documentation and the other sub-processes of my process. A minimal example unit test that
reproduces this problem is attached (reproduced with trunk/6208).
The problem is present in JBPM 4.3, as well.
--
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