[
http://jira.jboss.com/jira/browse/JBESB-1374?page=comments#action_12389927 ]
Jiri Pechanec commented on JBESB-1374:
--------------------------------------
See record of discussion with Tom B.
tombstone kevin says: The responsibility for deciding whether a RuntimeException should be
wrapped/unwrapped lies within the jBPM and integration code.
tombstone that is right
09:35 tombstone within the jBPM *and* integration code
09:36 tombstone so it should be in the integration code
tombstone meaning that jBPM will throw runtime exceptions out of execution of commands
09:37 tombstone it's up to the caller to call setRollbackOnly in case such an
exception occurs
tombstone (or alternatively use the command service SLSB)
Exception handling problem when used integrated jBPM/ESB with JTA
-----------------------------------------------------------------
Key: JBESB-1374
URL:
http://jira.jboss.com/jira/browse/JBESB-1374
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Process flow
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Assigned To: Kevin Conner
When used distributed tranasctions the transaction is rolled back when runtime exception
is thrown. Unfortunately the jBPM encapsulates RuntimeExceptions into JBPMExceptions that
are checked. Thus the rollback is not executed.
Also it needs to be checked there there is no other way in ESB that will cause
RuntimException to be changed to checked Exception.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira