-
1. Re: SyncTaskServiceWrapper registerForEvent
salaboy21 Sep 28, 2012 10:33 AM (in response to supritchaudhary)I think that you miss this: https://github.com/droolsjbpm/jbpm/blob/master/jbpm-human-task/jbpm-human-task-core/src/main/java/org/jbpm/task/event/TaskEventKey.java
But, what are you trying to achieve?
-
2. Re: SyncTaskServiceWrapper registerForEvent
supritchaudhary Sep 28, 2012 10:37 AM (in response to salaboy21)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?
-
3. Re: SyncTaskServiceWrapper registerForEvent
salaboy21 Sep 28, 2012 11:02 AM (in response to supritchaudhary)Is a marker interface like Serializable, but once again, why do you want to use that method?
-
4. Re: SyncTaskServiceWrapper registerForEvent
supritchaudhary Sep 28, 2012 12:24 PM (in response to salaboy21)I am trying to find out appropriate and realiable event notification for task transitions for Human/User task.
For example:
On task claim/start/complete, I want a notification to a registered handler; rather then a thread loop to query task status.
-
5. Re: SyncTaskServiceWrapper registerForEvent
salaboy21 Sep 28, 2012 1:36 PM (in response to supritchaudhary)1 of 1 people found this helpfulI'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.
Cheers
-
6. Re: SyncTaskServiceWrapper registerForEvent
supritchaudhary Oct 1, 2012 5:51 AM (in response to salaboy21)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.
Thanks.
-
7. Re: SyncTaskServiceWrapper registerForEvent
salaboy21 Oct 1, 2012 8:00 AM (in response to supritchaudhary)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
Cheers