[
https://jira.jboss.org/jira/browse/JBPM-1898?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-1898:
----------------------------------------
Brad, every event in jBPM is propagated up the graph element hierarchy to the process
definition. In your specific situation, the following events will be fired when the nested
superstate is left.
leave-superstate on nested superstate
leave-superstate on enclosing superstate
leave-superstate on process definition
If you want to know which graph element fired the event, call
ExecutionContext.getEventSource() from your action handler. Let me know if this clarifies
the observed behavior.
Leave-Superstate Event Executes Incorrectly
-------------------------------------------
Key: JBPM-1898
URL:
https://jira.jboss.org/jira/browse/JBPM-1898
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM 3.3.0 GA
Reporter: Brad Davis
Priority: Minor
Fix For: jBPM 3.3.2 GA
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
When there are nested superstates, events are processed incorrectly.
Example:
superstate w/ leave-superstate event {
nested superstate w/leave-superstate event { ... }
}
When the nested superstate is left, but the execution remains in the parent superstate,
both the parent and nested superstate's events for leave-superstate will execute.
The correct functionality would be that only the event for the superstate being left
should be fired.
--
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