Is this for an application that will run in production? If so, I recommend avoiding the ajax interface into ActiveMQ and consider a REST service, or something similar in its place. With Camel, setting up a rest endpoint is fairly simple.
With that said, you may be able to find a solution here. Just keep in mind that this feature may not get much usage (please correct me if I'm wrong), which means it will be hard to get help with it. -- View this message in context: http://activemq.2283324.n4.nabble.com/Send-headers-with-ActiveMQ-ajax-client-tp4680774p4680785.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
