Hi Maybe just implement a new Camel component instead of reusing JMS. Then you can still use producer template to send message to endpoints of this component.
On Wed, Nov 23, 2011 at 5:21 PM, saiya-jin <martin.franci...@barclayswealth.com> wrote: > Hello, > I have been given a task to integrate Camel to rather unstandard JMS > implementation that is coming with one of core banking packages. It > basically serves as a bridge that transforms JMS messages to SQL so queues > are in fact tables underneath. I tried simple approach with setting up their > internal ConnectionFactory, adding it via JMSComponent to context, and > sending simple message via ProducerTemplate. It fails because several > aspects of JMS standard are not implemented in this bridge (ie temporary > queues, headers on messages etc). I don't have source code of this connector > so it is rather hard to debug it correctly, exceptions are internal saying > "not implemented". > I have an old standalone code that is working, but very ugly and Camel seems > like a right step. But I am little bit lost, went through tutorial and > examples, been looking into ActiveMQ connector sources, but for somebody who > is starting with this product it is not easy to not make a step in wrong > direction. > Could You please help me and provide some initial advice , point to similar > implementation, or give any other advice? > Thank You > > -- > View this message in context: > http://camel.465427.n5.nabble.com/connecting-to-new-jms-implementation-tp5017200p5017200.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
