On 18/11/2007, jsbournival <[EMAIL PROTECTED]> wrote: > Hello camels!
Hey! :) > I'm about to lay out an architecture involving Active MQ queueing server > (Iona FUSE MB), and we need something like the message router EIP. I > managed to get in touch with James on the IRC channel, and he told me Camel > was included (sort of) in the Active MQ distribution. Good. FWIW Apache ActiveMQ 5.x and later - and IONA's distribution of ActiveMQ both come with Camel integrated into the broker (there's an example EIP pattern inside the activemq.xml) as well as the JMS client - you can use CamelDestinations with the ActiveMQ client. http://activemq.apache.org/enterprise-integration-patterns.html > But then, one > question popped: is it recommended to deploy all of our « routing » code > (DSL routes, beans, etc.) and resources straight in AMQ? Or is it a better > practice to develop another application (Camel enabled) listening to AMQ and > performing the routing stuff? > > I'm leaning towards the second solution, but if you would be kind enough to > share your thoughts and experience on this, I would greatly appreciate. So its one of those 'it depends' kinda questions. There are pros and cons to both approaches. I've created a FAQ entry... http://cwiki.apache.org/ACTIVEMQ/should-i-deploy-enterprise-integration-patterns-in-the-broker-or-another-application.html any feedback welcome > P.S. Maybe a couple of wiki pages could be written explaining how to > package applications using Camel and AMQ. Just of suggestion. Great idea... http://cwiki.apache.org/ACTIVEMQ/how-should-i-package-applications-using-camel-and-activemq.html -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
