AFAIK, there is only one default destination for all async nodes (see 
org.jbpm.graph.def.Node and org.jbpm.command.ExecuteNodeCommand).
Since I'd like to use multiple CommandExecutorThread instances on different 
machines, I can configure them so that every CommandExecutorThread has its own 
destination:

  | CommandExecutorThread cet = new 
CommandExecutorThread(JbpmConfiguration.getInstance());
  | cet.setDestination("myDest");
  | cet.start();
  | 
But at the current state, this CommandExecutorThread will never receive a 
message because all generated async messages have the destination 
"CMD_EXECUTOR" (see org.jbpm.command.Command.DEFAULT_CMD_DESTINATION).
Is it planned to add an additional "destination" attribute to the "node" class 
which can be set for async nodes?
I would find this very useful.

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

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961051
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to