[jboss-dev-forums] [Design of JBoss ESB] - Re: StartProcessInstanceCommand: Return token id/process ins

camunda do-not-reply at jboss.com
Wed Jan 7 11:14:47 EST 2009


Kevin wrote : 
  | It is the correlation functionality that is missing and not the signal command. 
  | 
Agreed. But in reality in your project, what do think the people do? Build a (complicated) correlation mechanism or hack an action which enables the SIgnalCommand again? ;-)

BTW: In pre-ESB projects we often used the token-id only for correlation, in some circumstances this doesn't cause problems. This is a project based decision. But to have the expected state is definitely best practice, I agree.

Kevin wrote : 
  | camunda wrote : 
  |   | I always work with the token id, because it is unambigous if multiple tokens exist for the ProcessInstance.
  |   | 
  | Except tokens come and go, loop etc. 
  | 

But you could have to process flows in parallel, both communicating with the ESB or maybe both flows even communicate with an external partner. Only the token id is unambiguous in this case. In the projects I know I always was fine with the token id.

BTW: Where is the problem with a loop? That doesn't change anything with the token id. Only Fork/Join does...

Kevin wrote : 
  | Thanks very much for the feedback, keep it coming :) 
  | 
Don't worry ;-)

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

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



More information about the jboss-dev-forums mailing list