Unexpected TaskListener behavior

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2013 12:28 PM
I have a task listener which listeners for each of the three types of task events (create, assign, complete). However, I saw some unexpected behavior when I created a new task with an initial assignee:
In this case, both the 'create' and 'assign' events are triggered as expected, but they happen in reverse order. My listener always received the 'assign' event before it receives the 'create' event.
Is there a reason for this ordering? I would have expected to get them in the opposite order. As it currently stands, my listener is receiving 'create' events for tasks that it already knows about and 'assign' events for tasks that it has never seen before.
<userTask id="myTask" name="My Task" activiti:dueDate="${dueDate}" activiti:assignee="${initialAssignee}" activiti:priority="${priority}">
In this case, both the 'create' and 'assign' events are triggered as expected, but they happen in reverse order. My listener always received the 'assign' event before it receives the 'create' event.
Is there a reason for this ordering? I would have expected to get them in the opposite order. As it currently stands, my listener is receiving 'create' events for tasks that it already knows about and 'assign' events for tasks that it has never seen before.
Labels:
- Labels:
-
Archive
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2013 08:21 AM
No, that does sound like a bug. Can you reproduce it as easily as you say (just add a task listener for both events)? If so, please create a Jira issue and link to this post.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2013 10:55 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2013 11:02 AM
Ok, thanks! We will look into it.
