On Fri, May 29, 2009 at 3:56 PM, Simpor <[email protected]> wrote: > > Hi, thanks for the fast reply! > > I just realized that I forgot to mention what version I was using and you > had already responded then. :-) > > My version is: apache-camel-2.0-M1 > > Ok.. I don't really follow you with the inOnly or outOnly. Haven't I Okay lets try the EIP patterns language then :)
*inOnly* http://camel.apache.org/event-message.html *inOut* http://camel.apache.org/request-reply.html >From what I read in your route description its an *inOnly*. > specified: > SideA: ActiveMQ-1, queue1->send with mina/tcp-port1 > SideB listen on mina/tcp-port1->ActiveMQ-2, queue2 > > And then > SideB: ActiveMQ-2, queue3->send with mina/tcp-port2 > SideA listen on mina/tcp-port2->ActiveMQ-1, queue4 > > > That is what I want to do. You can start to build the skeleton with some simpler components to make sure overall route is okay. So instead of mina and amq you can use seda and mock for testing. This allows you to easily get started from("seda:queue1").to("seda:tcp1"); from("seda:tcp1").to("seda:queue2"); from("seda:queue2").to("seda:tcp2"); from("seda:tcp2").to("seda:queue3"); But that only works within the same camel context as they are of course not remote protocols. How do you send the first message to the JMS queue1 that starts it? Could it be that this one have a JMSReplyTo set so Camel thinks its a request/reply message? Try adding .inOnly() after the first from in your route to force inOnly from("amq:queue1").inOnly().to("mina://...." > > > > > > -- > View this message in context: > http://www.nabble.com/Sending-a-message-between-two-ActiveMQ-using-mina-tp23780161p23780511.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
