I was too rash. The exception stated in my first message is raised due to the body of the exchange in-message, which is of type Map<String,String[]>. I worked around the problem by marshalling the map to JSON.
Irrespective of whether I use "transferExchange" or not I am loosing a header of type Set<String>. No exception or warning gets logged. -- View this message in context: http://camel.465427.n5.nabble.com/Sending-Receiving-active-mq-with-transferExchange-silently-removes-Exchange-headers-tp5794278p5794292.html Sent from the Camel - Users mailing list archive at Nabble.com.
