[
https://issues.jboss.org/browse/JBESB-3823?page=com.atlassian.jira.plugin...
]
Sato Tadayoshi commented on JBESB-3823:
---------------------------------------
Hi Kevin,
As an input, the original request was for the inVM transport to be aligned with the
behaviour of the jms-jca-provider (JCA inflow). We think the JCA inflow's
transactional behaviour is preferable because it is the same as that of the JEE
standards.
As described as a comment (see below) in the MessageAwareListener source code, providing a
option to change the inVM transport's behaviour would be fine, considering the impact
to existing applications which will be caused by this change.
{code}
// TODO consider adding a RollbackOnFalse option to allow override.
{code}
Standardise exception behaviour
-------------------------------
Key: JBESB-3823
URL:
https://issues.jboss.org/browse/JBESB-3823
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.11
Reporter: Kevin Conner
The JCA inflow handles exception behaviour differently from MessageAwareListener, rolling
back transactions *iff* a runtime exception was thrown.
MessageAwareListener also allows application exceptions to cause rollbacks.
We need to check the JCA inflow, and other uses of the pipeline, to make sure that this
behaviour is common.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira