Hello camels! 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. 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. JS. P.S. Maybe a couple of wiki pages could be written explaining how to package applications using Camel and AMQ. Just of suggestion. -- View this message in context: http://www.nabble.com/Iona-Message-Broker---Architecture-Question-tf4828771s22882.html#a13815320 Sent from the Camel - Users mailing list archive at Nabble.com.
