October 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBoss jBPM] - Re: Cancelling a task fires task-end event

by heiko.braun＠jboss.com

anonymous wrote : Let's make sure we address this in the jbpm team meeting. Sorry to intervene at this point, especially when it doesn't relate to this thread. But the team meeting should stay focused. Don't throw in stuff that can easily be discussed in the forums. IMO we need to make sure that conceptual things (bare bone) that relate to the API sand CTS have foremost priority when we meet. At least we should try to draw a line between implementation detail and concepts and leave the details to the person implementing it. Something else: If you come up with things that need to be considered, discussed or reviewed then raise an issue (JIRA) right away. Otherwise it get's easily lost. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180735#4180735 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180735

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Cancelling a task fires task-end event

by jbarrez

Ronald, If you are using this construction: | if (this.isCancelled) { | task.fireEvent(Event.EVENTTYPE_TASK_CANCEL, executionContext); | } else { | task.fireEvent(Event.EVENTTYPE_TASK_END, executionContext); | } | Then you are missing the TASK_END event if the task is cancelled. People for who see 'finishing a task ' (ie. cancelling or completing) as the end of a task (which is conceptually also correct) and now simply use an event handler for the TASK_END event are obliged to use 2 event handlers now. So it comes down to a matter of conceptual view: - Ending a task == the task is finished (removed by cancelling or successfully completed) - Ending a task == completing the task successfully, BUT cancelling means here that the task did not end but simply dissapeared for some reason. I have implemented both use cases in the past, so this is not some academic example. What we need here is a solid and clear definition ... anonymous wrote : | Otoh, I've not heard people complaining about taskmanagement regarding the 'states' of task management do you guys? Questions were more about declaring vars, typing them, giving default values etc | That's true ... but I did have a use case in which the states of a task were THE most import thing: cancelled, suspended, ended, assigned but not taken, working on it, etc. all those states were possible for a task. So you can imagine I would have been very happy at that moment if I had some more options ... we had to juggle a bit with task variables to get it all done. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180733#4180733 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180733

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Cancelling a task fires task-end event

by tom.baeyens＠jboss.com

"kukeltje" wrote : Questions were more about declaring vars, typing them, giving default values etc Those should be addressed as well in jBPM 4. Let's make sure we address this in the jbpm team meeting. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180731#4180731 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180731

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Cancelling a task fires task-end event

by kukeltje

"Tom B" wrote : | 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. | And we do provide a fully functional jbpm 3 compatable default I hope? Otoh, I've not heard people complaining about taskmanagement regarding the 'states' of task management do you guys? Questions were more about declaring vars, typing them, giving default values etc View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180727#4180727 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180727

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Cancelling a task fires task-end event

by kukeltje

"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#4180725 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180725

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Cancelling a task fires task-end event

by tom.baeyens＠jboss.com

"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#4180717 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180717

16 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Adding Ordering Group Features in JBM 1.4

by timfox

I have updated the docs and readme so they reference the correct jar versions and release numbers. I have also released the project in JIRA What remains to be done before releasing: 1) Make sure all the examples run through 2) Update remoting config in the docs with the version in the release Other things to do (maybe done already?) 1) Make sure eap 4.3 service binding manager config is updated with our new config. 2) Make sure any JBM config files in EAP 4.3 have been updated with our new config. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180716#4180716 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180716

16 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Adding Ordering Group Features in JBM 1.4

by timfox

I deleted the tag to prevent anyone taking it prematurely. Next time, I want to see a review process before tagging. This same mistake of not updating readme and documentation seems to happen regularly every single time.. :( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180710#4180710 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180710

16 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Adding Ordering Group Features in JBM 1.4

by timfox

Please don't use that branch. The release will need to be re-tagged since readme and docs weren't updated properly. The release notes still refer to 1.4.1.beta1 (!) and reference the incorrect project in JIRA, as does the documentation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180709#4180709 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180709

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - test

by thomas.diesler＠jboss.com

test View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180700#4180700 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180700

16 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2008