On 20 July 2010 16:38, Ron Smith <ron.sm...@valkyresoftware.com> wrote: > Unfortunately, all those cool features (especially pooling and reconnect) > are exactly why I was wanting to use something like camel. This isn't the > first time that this companies unreasonable biases have limited my choices > of tools. I'm not a fan of spring or maven but I understand their value. > > I might actually take a stab at a non-spring jms component for camel because > I am really liking the way camel works.
Yay - go Ron! :) FWIW the Camel Component is designed as a natural place to lazily create & own the JMS connection; the Endpoint as a natural place to hold the Destination. Then each Camel Producer/Consumer would just create & own a JMS Session and MessageProducer / MessageConsumer. So it shouldn't be too hard to get something reasonable going fairly quickly. Though camel-jms has ended up being quite complex code due to lots of complex requirements (e.g. supporting InOut with a ton of different configuration options). Dealing with transactions and reconnection is going to be the hardest and most complex bit though. -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
