[
https://jira.jboss.org/jira/browse/JBPM-2805?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2805:
----------------------------------------
Regarding the design it might seem odd, but from what I remember of the discussions, it
makes the PVM (Process Virtual Machine) way more easier to implement. Everything happens
on an execution and what parts are visible is limited by using different interfaces. For
this specific issue, it might be nothing more than adding the getEvent() method to the
EventListenerExecution with a return param of org.jbpm.api.Event
Add access to event type in EventListener interface
---------------------------------------------------
Key: JBPM-2805
URL:
https://jira.jboss.org/jira/browse/JBPM-2805
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.x
Reporter: Mike Martin
Add the ability to determine the event type ("start" or "end") from
within an EventListener implementation. There should also be the ability to easily
determine the name of the process definition step where the event occurred.
This makes it possible to write a single event listener that handles many different kinds
of events. As far as design, it seems odd that the notify() method has a *Execution
parameter, rather than an "event" parameter that contains all information about
the event that occurred; the latter would be more in line with the way event listener
interfaces are usually designed in Java.
--
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