public class TaskEventKey implements EventKey.
What is acheived by TaskEventKey implementing EventKey when EventKey is a empty interface.
What is a use of empty interface passed to SyncTaskServiceWrapper registerForEvent function?
Is a marker interface like Serializable, but once again, why do you want to use that method?
I am trying to find out appropriate and realiable event notification for task transitions for Human/User task.
On task claim/start/complete, I want a notification to a registered handler; rather then a thread loop to query task status.
1 of 1 people found this helpful
I'm working on an updated version of the Human Task Component based on CDI, if you are not using the spring integration, you can easily try out the new module, where all the hooks for getting those events are already created. If you are using the latest snapshot from master there is a new module called jbpm-human-task-services that you can try.
Can you provide a test case for the events that you are implementing.
I looked into the source of jbpm-human-task-services, but unable to find a test for the human task events.
The jbpm-human-task-services is emiting CDI events:
All the events are hidden from the regular user that is not interested in them but, because the Human Task WorkItems rely on these events to work you can find an example usage of them here:
That's the listener which is Observing events that are being emitted by the HT services.
All the tests inside the jbpm-human-task-workItems are using these events to notify the session about a task completion/abortion ->
If you debug those tests you will see where the events are being emitted and observed