[CAMEL-585] JMS Component - Look at Bruces investigations (message transfer using JMS and exceptions)

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.0, 1.4.0
• Fix Version/s: 2.0-M2
• Component/s: camel-jms
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 07/Jun/08 13:43
• Updated: 21/Nov/09 11:57
• Resolved: 23/Mar/09 13:03

Description

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