Re: scalable bus with multiple Camel instances

I see that Camel mainly makes sense with a broker like ActiveMQ, as a core for a scalable/decoupled system. Thanks for helping me understanding this! -- View this message in context: http://camel.465427.n5.nabble.com/scalable-bus-with-multiple-Camel-instances-tp5606593p5612599.html Sent from the

Re: scalable bus with multiple Camel instances

Thanks for your answer. I'd like to have a response as fast as possible and can afford loosing messages. Actually I would like to see if I can avoid activemq in the middle. -- View this message in context: http://camel.465427.n5.nabble.com/scalable-bus-with-multiple-Camel-instances-tp5606593p56

defaultEndpoint must be specified with seda request/reply

When running this program I get the message 'defaultEndpoint must be specified'. Could you help me understand why? Thank you! public static void main(String args[]) throws Exception { // create CamelContext CamelContext context = new DefaultCamelContext(); // add o

scalable bus with multiple Camel instances

My idea is to use camel to decouple modules. In order to support scalability and failover, I am wondering if the following architecture is adviced? I have two applications with Camel embedded AppCamel1 and AppCamel2. Then I have standalone camel nodes Camel1 and Camel2. AppCamel1 would have a rou

Using Camel as a Fast Back-end Bus with REST services?

I posted my question on stackoverflow: http://stackoverflow.com/questions/9704526/using-camel-as-a-fast-back-end-bus-with-rest-services http://stackoverflow.com/questions/9704526/using-camel-as-a-fast-back-end-bus-with-rest-services Please let me know if it's not ok to proceed this way. I beli