Re: Unit of Work Scope and direct/SEDA/vm components

2013-08-07 Thread Christian Posta
Could you also do the following? from(...)..to("vm:name").process(new Processor() { public void process(Exchange exchange) { exchange.getUnitOfWork().done(); } }); On Tue, Aug 6, 2013 at 7:11 AM, Scott Parkerson wrote: > Bilgin, > > Thank you -- that's what I expected, so I'll

Re: Unit of Work Scope and direct/SEDA/vm components

2013-08-06 Thread Scott Parkerson
Bilgin, Thank you -- that's what I expected, so I'll give using a JMS queue a try. --sgp On Mon, Aug 5, 2013 at 2:45 PM, Bilgin Ibryam wrote: > Hi, > The file component uses onCompletion for moving files after the exchange > has completed. As long as the completions are passed with the exchan

Re: Unit of Work Scope and direct/SEDA/vm components

2013-08-05 Thread Bilgin Ibryam
Hi, The file component uses onCompletion for moving files after the exchange has completed. As long as the completions are passed with the exchange the files wont move. The VM component passes the completions to the next camel context so the files are not moved... You have to use a queue or somethi

Unit of Work Scope and direct/SEDA/vm components

2013-08-05 Thread Scott Parkerson
Hi, fellow Camel riders. I was wondering where Camel's notion of UnitOfWork begins and ends with respect to processing a route or set of routes. For example, I have a route that starts with a SFTP poller that consumes files off of a server. The contents of these files are then handed to another r