"jbarrez" wrote : | It is a difficult topic :p | I tend to disagree, see below "jbarrez" wrote : | I have a use case in which having a cancel event would be great. In that use case is cancelling a task conceptually different from ending a task: ie. a cancelled task is a task which has not been ended (= finished correctly) by someone. | | But, Tom is right: for another customer the story could be different ... | If they are the same for this user, They will just use one or the other (most likely end() ). But for others, they can put any logic they want on 2 'event-handlers' so.. "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 ... ? Could be, but that makes it more difficult to implement. You can get that functionality by declaring 2 event-handlers as mentioned above.... I would not make it overly complicate. But if kind of hierarchical events are introduced, that would be fine to. In that case we agree and is it less complex/difficult than we thought. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180725#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...