[jboss-user] [jBPM] New message: "Re: Problem Signaling a Waiting Execution"

Santanu Saraswati do-not-reply at jboss.com
Tue Jan 19 00:36:37 EST 2010

User development,

A new message was posted in the thread "Problem Signaling a Waiting Execution":


Author  : Santanu Saraswati
Profile : http://community.jboss.org/people/saraswati.santanu

These are the two points I understood about your requirement:
1. You have to perform some activity at every node of the flow.
2. You call executionService.signalExecutionById(executionId); from somewhere outside to invoke the flow for the first time. This call takes you to the end even listener of activity1. There you try to invoke executionService.signalExecutionById(executionId); to ensure that you move to activity2.
Lets take the second point first. Hope this understanding of mine is correct. And if it is correct then you do not need executionService.signalExecutionById(executionId); call in your event listener. If you have reached end event listener you will anyway move to the next activity (activity2). Just execute your business logic there. Flow will be taken care of.
About the first point - my question is do you need to wait for some external operation (which is not a part of the flow) to happen and then trigger the flow at each activity? If you need to do this then state node is the correct choice. If you do not need to wait at the node and just need to execute some business logic at the node you should consider using java node.


To reply to this message visit the message page: http://community.jboss.org/message/520721#520721

More information about the jboss-user mailing list