The point is that there is no reason to restart the process. It will be restarted (from the ht node) when the client UI completes the task. Try just reloading your ksession and completing the task from the UI.
Best Regards, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Esteban Aliverti - Developer @ http://www.plugtree.com - Blog @ http://ilesteban.wordpress.com On Wed, Apr 6, 2011 at 12:02 PM, gs76pl <[email protected]> wrote: > hi, > thanks for your prompt reply, > > OK, i've a custom screen that checks for a task assigned to a specific > user. > What i'm trying to do now is checking how to restart a process when for > instance the server crashes. In order to simulate this i'm killing my > process once a human task has been created. After that i'm trying to start > the process once again and what i expect is that: > - all steps prior to the human task will be skipped > - my process will be waiting for a human task to be completed before > continuing > > As you probably correctly pointed out i should be restarting a process > rather than starting a new one and trying to use previously stored > sessionId. The only problem i see here that i can't find any API that would > allow me to do someting like this: > > processService.restartProcess(processId, sesionId) > > > > > > -- > View this message in context: > http://drools-java-rules-engine.46999.n3.nabble.com/drools-flow-why-after-reloading-some-process-previously-completed-workItems-gets-executed-once-again-tp2784850p2785361.html > Sent from the Drools - User mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users >
_______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
