Hello Claus,
Well of course, I didn't remove the "noop" option for testing.
Thanks for your feedback.
Ryadh.
Claus Ibsen-2 wrote:
>
> On Fri, Dec 19, 2008 at 10:29 AM, Ryadh Amar <magnetic.gan...@gmail.com>
> wrote:
>>
>> Thanks Claus and Ramon,
>> I managed to combine both routes and used an aggregate, which helped a
>> lot
>> my use case.
>> I've seen a couple of threads where proposals were made to find a way to
>> persist messages, something like BAM, since this is a requirement, I am
>> going down this route (no pun intended ;) )
>>
>> from("file:src/data/recieved?noop=true").to("ibatis:setMessageReceived");
>> from("file:src/data/processed?noop=true").to("ibatis:setMessageProcessed");
>> from("file:src/data/error?noop=true").to("ibatis:setMessageFailure");
>> from("file:src/data/done?noop=true").to("ibatis:setMessageSuccess");
>>
>> And then have another route, which will simply poll the table where the
>> messages are stored and show the status of each one, something like:
>>
>> from("jetty:http://localhost:8080/myapp/myservice";).process(new
>> MessagesStatusService());
>> where MessagesStatusService() pulls the list of messages from the table
>> and
>> displays the status of each one.
>>
>> Thoughts?
> Thats a good solution. Storing the status in a DB then its persistent.
>
> Note that noop=true on the file consumer will not delete/move the
> file, so the folder will just grow larger and larger.
> But I guess that is for unit testing?
>
> We use noop=true as an essential part of unit testing Camel itself.
> Then we can have file messages we can route, where we can store the
> files in SVN.
>
>
>>
>> Thanks in advance for you efforts, Camel has now become an essential part
>> of
>> my toolset.
>>
>>
>>
>
>
>
--
View this message in context:
http://www.nabble.com/Using-the-correlation-id-in-regular-routes-tp20978464s22882p21088620.html
Sent from the Camel - Users mailing list archive at Nabble.com.
