Yes, you're right. After I removed signal* from EventListener everything works.
But I read about it in documentation:
http://docs.jboss.com/jbpm/v4/userguide/html_single/#singallingawaitingexecution
From there:
"
The preferred way to capture the right execution is by associating an event listener to the state activity like this:<state name="wait"> <on event="start"> <event-listener /> </on> ... </state>In event listener StartExternalWork you can kick off what needs to be done externally. In that event listener you can also obtain the exact execution id with execution.getId(). It's that executionId that you'll need to provide with the signal later on when the external work is done: executionService.signalExecutionById(executionId);
The preferred way to capture the right execution is by associating an event listener to the state activity like this:
<state name="wait"> <on event="start"> <event-listener /> </on> ... </state>
In event listener StartExternalWork you can kick off what needs to be done externally. In that event listener you can also obtain the exact execution id with execution.getId(). It's that executionId that you'll need to provide with the signal later on when the external work is done:
StartExternalWork
execution.getId()
executionService.signalExecutionById(executionId);
So by real life if I want java code to decide where to go next I can't use State and should use Java, right?
Reply to this message by going to Community
Start a new discussion in jBPM at Community