I could see the ProcessInstance.end() method was adjusted from 3.0 to 3.1alpha (so something wasn't likely right), and I didn't want to upgrade to 3.1 yet...
I needed persistance, so I just wrote my own ProcessState as a node extension. It was pretty easy. Essentially the two things needed done: 1. the parent must go into a wait state if execution returns (due to error or end) 2. the child's end must signal the parent token to continue. The additional benefit to this was that I can see it in the process designer. Sean View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912968#3912968 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912968 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
