[
https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55151#action_55151
]
Willem Jiang commented on CAMEL-2128:
-------------------------------------
@Christian
It is hard to let CamelTransport to know which kind of exception is defined by
User, and the CamelTransport should now nothing about the application level
thing. Let's put the ignoring the customer exception on the camel's error
handler framework.
I will commit my patch in a min :)
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message
> delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed
> which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
