You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by begorrah <be...@gmail.com> on 2015/04/05 18:04:30 UTC
Request reply route is returning the request
Hi,
I'm having some problems with my first ever Camel route.
First, some versions. I'm using Camel version 2.15.0 in a Spring Boot +
Groovy application and I'm currently running on OSX with a 1.8 JVM.
The route is defined as follows:
Most of the route is working correctly:
- the route gets started properly
- the splitting works fine
- the JMS queue works fine - I see the messages being handled and responded
to correctly in the JMS consumer (implemented in a different process)
- the aggregation seems to work fine also
I'm invoking the route as follows:
The problem is that the value returned from is the original request message
instead of the aggregated response.
If I add enhance the end of the route with a call to one of my own beans as
follows:
then I can see in the implementation of processBotReplies (which has this
signature: that the list being passed in really is the correct response.
But why is the return value from not also the response?
Any help, thoughts, advice, etc appreciated.
Cheers,
/BG
--
View this message in context: http://camel.465427.n5.nabble.com/Request-reply-route-is-returning-the-request-tp5765345.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Request reply route is returning the request
Posted by begorrah <be...@gmail.com>.
Works like a charm - you sir are a rock star! :-)
Many thanks,
/BG
--
View this message in context: http://camel.465427.n5.nabble.com/Request-reply-route-is-returning-the-request-tp5765345p5765354.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Request reply route is returning the request
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
You likely need to use this EIP
http://camel.apache.org/composed-message-processor.html
And then use _splitter only_ as the splitter has built-in aggregation,
that ensures eventually your response can be the aggregation from the
built-in splitter.
When you use aggregate explicit then you break up into 2 legs, where
each leg has their own threading model.
A bit short explain here, but some pointers to get started. The EIP
pages and Camel books explains this much more in depth too.
On Sun, Apr 5, 2015 at 6:04 PM, begorrah <be...@gmail.com> wrote:
> Hi,
> I'm having some problems with my first ever Camel route.
> First, some versions. I'm using Camel version 2.15.0 in a Spring Boot +
> Groovy application and I'm currently running on OSX with a 1.8 JVM.
>
> The route is defined as follows:
>
>
> Most of the route is working correctly:
> - the route gets started properly
> - the splitting works fine
> - the JMS queue works fine - I see the messages being handled and responded
> to correctly in the JMS consumer (implemented in a different process)
> - the aggregation seems to work fine also
>
> I'm invoking the route as follows:
>
>
> The problem is that the value returned from is the original request message
> instead of the aggregated response.
>
> If I add enhance the end of the route with a call to one of my own beans as
> follows:
>
> then I can see in the implementation of processBotReplies (which has this
> signature: that the list being passed in really is the correct response.
>
> But why is the return value from not also the response?
>
> Any help, thoughts, advice, etc appreciated.
>
> Cheers,
> /BG
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Request-reply-route-is-returning-the-request-tp5765345.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/