[jboss-user] [jBPM Users] - jBPM 4.1 - sub tasks

Thomas.Kriechbaum do-not-reply at jboss.com
Tue Sep 22 11:18:04 EDT 2009

We have been experimenting with sub tasks for a while (parent child relation is set up within a custom activity).

What is the planned/expected behavior of certain lifecycle events (e.g. complete parent task)?

Currently, the CompleteTaskCmd firstly calls task.complete (in this case, a history event for this task is fired too). Afterwards, the task is deleted using the DB session (according to the hibernate mapping, all sub tasks are deleted too;  cascade="all-delete-orphan").

What is the recommend way to extend this behavior (e.g. fire history events for all sub tasks)? One solution might be to implement a custom command (requires to implement a custom TaskServiceImpl as well). 


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256433#4256433

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256433

More information about the jboss-user mailing list