Hi I do think we should pick this issue up when Camel 1.4 has been released hopefully in next week. Then we have time to discus and find a solution to this for the next release.
Could you create a JIRA ticket with this issue with a layout of the problem and some links to the user forum (from nabble etc.) to your requests etc. When the ticket is in JIRA it is not forgotten (maybe there is at ticket for this already, please check). When an exception is sent over the wire with JMS then the consumer/producer can have different jar libraries and thus the exception on the remote site can not be marshaled. At least I see a point in adding a header (if not already there) with a string property of the original exception name - eg. originalExceptionClassName=com.mycompany.business.CustomerDoesNotExistsException Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: jaco.uys [mailto:[EMAIL PROTECTED] Sent: 23. juni 2008 22:12 To: [email protected] Subject: Re: exception trace in message Hi, Is there any resolution to this issue? I am using the deadletterchannel to handle any exceptions, but so far unable to set the original exception on the resulting message that is send to a queue. Regards Jaco -- View this message in context: http://www.nabble.com/exception-trace-in-message-tp15740418s22882p18077402.html Sent from the Camel - Users mailing list archive at Nabble.com.
