this is a tricky one. currently, the cancel method indeed includes the call to end() on purpose. the desired behaviour in case one fo the task instances is cancelled depends on the process. it cannot be defined in a general manner. in the current code, it would be the most logical to add the .cancel(Transition trans) and .cancel(String transName) methods apart from that i have been thinking about abstracting the state machine inside of a task instance. states being: created, started, cancelled, suspended, and others are thinkable. i'm in doubt wether this justifies it's own statemachine (could be implemented in jpdl:-) or wether this just be a hard coded state machine. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960949#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...