"jbarrez" wrote : Perhaps for jBPM4, something drastical should happen to cover this since it will never be good for everybody... perhaps working with inheritance for events, so that you could catch Task-end and Task-cancel but also Task-finished (parent of end and cancel) event that is a catch-all if it doens't matter ... ? That is what I was trying to indicate: In jBPM 4, the task lifecycle will be expresssed in a resource file that can be customized by the user. The different states a task can be in and the events that are fired are then specified in that configuration file. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180717#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...