[
https://issues.apache.org/activemq/browse/CAMEL-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-585.
-------------------------------
Resolution: Fixed
trunk: 757395.
See new option *transferException* on the Camel JMS wiki page.
See also {{org.apache.camel.component.jms.JmsTransferExceptionTest}} for an
unit test.
> JMS Component - Look at Bruces investigations (message transfer using JMS and
> exceptions)
> -----------------------------------------------------------------------------------------
>
> Key: CAMEL-585
> URL: https://issues.apache.org/activemq/browse/CAMEL-585
> Project: Apache Camel
> Issue Type: Task
> Components: camel-jms
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
> Attachments: camel-fixes.zip
>
>
> Bruce Elmore have investigated and do think that Camel has a bug in the JMS
> compoenent regarding how exceptions is received from the JMS Producer (when
> receiving the reply).
> If the reply was a thrown exception from the other part, this is not
> currently set as an exception on the build Exchange but on the body as is.
> Pitfall: If an exception should be deserialized and set as an exception
> object on the created exception there could be problems with that the
> exception class does not exists on the receive side.
> Would be great to get James and other core comitters opinion on this matter,
> as it's maybe also a more general pattern for other components as well.
> This ticket is created to not forget about the postings on the user forum:
> nabble: (Handle Bean Exception)
> http://www.nabble.com/Handling-Bean-exceptions-td17671948s22882.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
