[jboss-user] [jBPM Users] - Re: workflow design about wait states

mmusaji do-not-reply at jboss.com
Fri Sep 11 09:50:03 EDT 2009

Would love to write a blog entry about this, get more involved with jboss and jbpm is my ultimate aim. I need to know what I'm talking about first! ;) Unfortunately... with work pressures etc its not always possible. We'll see... 

Taking the "async" out it works fine, I can see the nodes and assert which one they should be in. When the custom nodes run in async, the unit test runs to completion quicker than the actual workflow completes (or vice versa not sure). So when I do:

  | Execution execution = processInstance.findActiveExecutionIn("validate one request");
  |     assertNotNull(execution ); //FAILS
  |     String executionId = execution .getId();
  |     executionService.signalExecutionById(executionId);

The assertion fails. In my custom class I have the following line 
  | public void execute(ActivityExecution execution {
  |  //my code....
  |   execution.waitForSignal(); 
  | }
  | public void signal(ActivityExecution execution, 
  |             String signalName, 
  |             Map<String, ?> parameters) {
  |         execution.take(signalName);
  |     }

and they all implement ExternalActivityBehaviour. I have no idea what state these are in now.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254772#4254772

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254772

More information about the jboss-user mailing list