[
https://issues.jboss.org/browse/JBESB-3609?page=com.atlassian.jira.plugin...
]
Michael Burman commented on JBESB-3609:
---------------------------------------
To correct this somewhat, this isn't actually always true. It's nearly impossible
to solve the issue when there is splitting action with further routing done inside the
Smooks. In this case, not throwing a RuntimeException will cause already routed messages
to go through, even if the whole message wasn't well-formed XML.
SmooksException handling
------------------------
Key: JBESB-3609
URL:
https://issues.jboss.org/browse/JBESB-3609
Project: JBoss ESB
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Transformation Service
Affects Versions: 4.9 CP1
Reporter: Michael Burman
Executing SmooksAction might lead to throwing SmooksException in the process. If the
environment is transacted (JCA is used), the service is always rollbacked and message
returned to the queue. This is not correct behaviour often, since Smooks throws
SmooksException for example in case of SAXParseException. That processed file is broken
and will not work in the subsequent phases either. Writing any database log for example of
happening is impossible since that would be rollbacked as well.
All SmooksException should be checked whether they should be rollbacked or not (or just
never rollback them, throw them as checked exceptions).
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira