Oh, that's in the web-demo code, not the actual ActiveMQ code. You might get away with a local copy of the same. Another option, that is likely more straight-forward and a safer approach, is to create a message with the necessary details all in the body, send to a separate queue which is consumed by a camel route, and have the camel route create a new message using the body and headers specified in the original.
With all that said, please do consider this path carefully. Most of the JMS guarantees will be lost using AJAX when all the possible timings of lost connection between the Ajax client and broker are considered. Cheers! -- View this message in context: http://activemq.2283324.n4.nabble.com/Send-headers-with-ActiveMQ-ajax-client-tp4680774p4680987.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
