Hi Bernd, I can't resist...
anonymous wrote : cancel ProcessInstances and start complete new processes is often impossible (because of triggering external systems, sending mails t ocustomers, ...) What I suggested was ending the old processInstance and starting the new one in the same or matching state so you wouldn't be triggering anything twice. (Resending mails is a problem that has to be solved differently anyway as it isn't transactable.) The problem I have with directly changing the database is 'revision-safe' data. Especially in long running or archieved processes you would have no chance of reproducing workflow execution as you have no way of knowing what definition was used for what processInstance. (If customer internal security forbids direct write access to production databases this would probably be forbidden as well.) Think: Customers calls and claims you sent a mail 2 months ago. You changed the processDefinition. What chance do you have of being sure (unless you map / log all actions somewhere else). But of course I am totally aware that hardly anybody cares about these things except for internal revision departments :-) Greetings Rainer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916453#3916453 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916453 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
