Raj, sorry if this sounds too intrusive, but what are you trying to accomplish?
Your approach seems extremely complicated to me and I have the impression that you are actually redundantly reimplementing behaviour jBPM already takes care of. token.signal() will traverse the processDefinition until it reaches a wait-state and only then return, which seems to be very similar to what you are trying to achieve. I don't have the time right now to trace it in detail, this is just a first impression. Concerning your concurrency question: you will have to lock on the processInstance. Greetings View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922254#3922254 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922254 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
