Write two routes: one that writes to a JMS queue and one that picks up data
off the queue and processes it:
from("direct:input").to("activemq:queue:inbox");
from("activemq:queue:inbox"). <other processing here> .
to("activemq:queue:results");
This manner you can shove data in as fast as you want and even have
concurrent consumers of the inbox queue that will parallel process the
input data. At the same time you can have your results queue. You can then,
if you wish, process that queue for reporting and so on.
*Robert Simmons Jr. MSc. - Lead Java Architect @ EA*
*Author of: Hardcore Java (2003) and Maintainable Java (2012)*
*LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39
<http://www.linkedin.com/pub/robert-simmons/40/852/a39>*
On Tue, Jan 7, 2014 at 7:18 AM, jamalissimo <[email protected]> wrote:
> Hi hekonsek,
>
> I know that I will get the result when the request is solved in queue, but
> for example, when I am processing big amount of data, I don't want to wait
> 20 seconds. I can use "to("direct:foo")" for this purpose. I just want add
> the requests to the queue and return result right away(like processing data
> in progress), and all work would be done in background. Hope you know what
> I
> mean :-)
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/ActiveMQ-processing-tp5745652p5745676.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
