Alejandro Guizar [
http://community.jboss.org/people/alex.guizar%40jboss.com] created the
discussion
"Re: jBPM 3.2 Enterprise - Unhandled exception in async node?"
To view the discussion, visit:
http://community.jboss.org/message/565240#565240
--------------------------------------------------------------
Nodes with the "async" attribute set to "true" or
"exclusive" are +executed+ asynchronously, but they are still +entered+ in the
current transaction - see
http://fisheye.jboss.org/browse/jBPM/jbpm3/branches/jbpm-3.2-soa/core/src...
Node.enter(). The observed behavior is as expected. If the token remained in the
success-node after an exception thrown during +execution+ of the exception-node, it would
indicate the success-node is still in progress, yet it is not. The success-node has
completed successfully and the execution is stalled at the exception-node.
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/565240#565240]
Start a new discussion in jBPM at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]