[
https://jira.jboss.org/browse/JBPM-2644?page=com.atlassian.jira.plugin.sy...
]
Ed Willis commented on JBPM-2644:
---------------------------------
We have recently run into this exact problem.
The current behaviour seems counter-intuitive and unhelpful since it makes processing
based on the properties of the started task impossible in the start handler. In our case,
we want to get hold of the task participants and take action based in them when it
starts.
I understand the technical reason for this but it seems to be a restriction imposed by the
current design.
We can work around it by storing state in process variables, but we are then throwing away
the benifit of using the jBPM API to query this information in a first-class type-safe
way.
Investigate problem with EventListeners and missing tasks for user
activities
-----------------------------------------------------------------------------
Key: JBPM-2644
URL:
https://jira.jboss.org/browse/JBPM-2644
Project: jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.2, jBPM 4.3
Reporter: Sebastian Schneider
Assignee: Koen Aers
Priority: Critical
Attachments: process.jpdl.xml, TaskEventListener.java,
TaskEventListenerTest.java
When you put an EventListener on the start-event of a user task in your process
definition and you use a TaskQuery to retrieve the matching task in the user's task
list you don't find the task in the list although the execution is already active.
Investigate if this behaviour is intended and if it can be changed.
--
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