Thanks James. I did read through the email and have it working with 1.3-SNAPSHOT. It just seemed strange that the suggested method did not work with 1.2.
I am trying to compare using the spring remoting proxies with using CamelTemplate with ExchangePattern.InOut. Do you think this is a good idea? I have it working this way as well, but being a Camel newbie I am very confused about what is on the client/server/both. For example if I was using CamelTemplate to synchronously call a remote queue managed by Camel, what would be in my client's camel context that I give to the CamelTemplate? Would it just be the JMS component with no routes defined and the AcitveMQ connection factory? Thanks, Martin. ----- Original message ----- From: "James Strachan" <[EMAIL PROTECTED]> To: [email protected] Date: Thu, 27 Mar 2008 12:31:29 +0000 Subject: Re: Request Reponse with Camel On 27/03/2008, Martin Gilday <[EMAIL PROTECTED]> wrote: > Hi, > I am currently trying to find the best way to implement request response > with ActiveMQ. I am considering Lingo as well as Camel. Camel offers much more flexibility for things like smart routing, transformation & encoding of the messages, setting of headers and so forth - plus it can work with any Camel transport... http://activemq.apache.org/camel/components.html The big downside of Camel right now is it doesn't support Lingo's asynchronous options yet. We need to enhance the Spring Remoting implementation in Camel to support this. e.g. marking methods in an interface as being @Oneway or @Async or something so that the spring remoting can send an InOnly exchange rather than an InOut. > This page on > the ActiveMQ site [1] suggests that using Camel as a Spring Remoting > provider is the best solution. However the page it links to [2] is > seemingly only a partial listing of the test case from camel-spring. I > have attempted to follow the test case, however this resulted in errors > once I changed the example from direct to JMS. There's been a JMS remoting test case in svn for a while - I just created a simpler one to follow in trunk... https://svn.apache.org/repos/asf/activemq/camel/trunk/components/camel-jms/src/test/java/org/apache/camel/component/jms/remoting/RemotingTest.java using this Spring XML https://svn.apache.org/repos/asf/activemq/camel/trunk/components/camel-jms/src/test/resources/org/apache/camel/component/jms/remoting/RemotingTest-context.xml > This lead me to finding > this posting [3] on the mailing list describing the same fault. Reading to the end of that thread it seems Carsten got it working in the end - it turned out to be a configuration issue with ActiveMQ right? -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
