Hi It's the JMS broker's duty to be complaint to the JMS spec and not Camel itself which is just a mediator of exchanges between endpoints, JMS broker being just one of them.
So for example in case you make use of Apache ActiveMQ then you're "lucky" as there's no restriction about the header values because the following ticket has not been fixed (mainly because of the backward compatibility): https://issues.apache.org/jira/browse/AMQ-2287 So just give your used broker a test to see how it behaves. Babak -- View this message in context: http://camel.465427.n5.nabble.com/Issue-with-JMS-endpoint-headers-that-do-not-conform-to-JMS-spec-tp5716665p5716666.html Sent from the Camel - Users mailing list archive at Nabble.com.
