[jboss-dev-forums] [Design of JBoss jBPM] - Re: Failure handling

[bill.burke@jboss.com]

"estaub" wrote : Bill,
  | 
  | In your original scenario, I'm picturing the rollback as originating in an actionhandler performing a non-JBPM-related action.  For these cases, I'm dealing with the transactional difficulties by isolating them in their own transaction.  Once this is done, exception handlers should be usable.

But, in this scenario, you wouldn't be able to do JBPM related actions is this isolated transaction, specifically the setting of variables, correct?  Kind of making things like Seam unusable.

anonymous wrote : 
  | You should probably also be aware that JBPM uses recursive execution of the graph.  I mean that, when a node actionhandler calls leaveNode() or, less properly, signal(), the downstream execution of subsequent nodes happens within that method call; the execution of later nodes happens within the execution scope of the first actionhandler.  This can lead to surprising behavior in error conditions, at least for me.  I have a fix for this, but I'm not sure that anyone else believes it's a problem!
  | 
  | -Ed Staub
  | 

Ed, can you elaborate why this is a problem?  I just want to learn something.  IMO, this seems like an advantage.  And, can't you just fix your issue with an asynchronous continuation?

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

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