Hi Rainer, It's Meltem :)
Thank you for your response. Since our processes are long running and complex processes, there may be several different outermost /initial token.signal() calls. For example in one process we assign an approval task to a user. And the user has several options to complete the task: approve / reject / send back... All of these resume the execution of the process (signals the process) with different transitions. So we should handle copying of the context in each. This will be repeated in some other steps of the process and this scenario will change for every process so each process needs special care. Each developer must be aware of this situation and implement accordingly. What I want to do is isolate the developers from such a detail and provide a generic solution. I want to use the objects by reference, but also persist them. It would be a great solution, if JBPM allowed this. Maybe they consider to provide this improvement in the next releases. I think they should. Meltem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911389#3911389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911389 ------------------------------------------------------- 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
