[jboss-dev-forums] [jBPM Development] - Re: Close issue JBPM-2537

[sebastian.s]

Joram, can we try to agree on a concept for this issue? In the JIRA comments you wrote:

"Joram" wrote : 
  | The most logical is not necessarily what was in 3 ;-)
  | 
  | But you are right: in 3, the task is kept open, but it can't be completed anymore. The only option is than to delete the task. Imo, this makes sense.
  | 

https://jira.jboss.org/jira/browse/JBPM-2537

To me this solution makes sense. The task has to be deleted since the execution moved on because of the timer which fired. Since this isn't a fork the "old task" is not supposed to be active anymore (that's the reason it can't be completed) and as you stated it can only be deleted. 

I would highly appreciate a solution for this in jBPM 4.3 , personally but also because I think it's a very basic feature which is broken right now.

If the other dev's agree with us maybe you could take care of this issue? :)

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

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