Camel exchange - Multiple File output from processor

Hello, Is it possible to handle multiple file output in Exchange? Here is my scenario from(routes.getString("inbound")).to(routes.getString("shared.inbound")).process(new Processor() { public void process(Exchange exchange) throws Exception { MYProcessor asdaProcess

Re: Camel exchange - Multiple File output from processor

Thanks very much Willem. 1. Input file - Order1.xml 2. Output after the Processor component - File1.xml, File2.xml, File3.xml. Output files are generated after XSLT transformation. 3. All the output file is routed to the same endpoint I looked through the splitter documentation and think that is

Re: Camel exchange - Multiple File output from processor

Thanks Willem, this worked perfectly for my scenario. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-exchange-Multiple-File-output-from-processor-tp5717035p5717465.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Read a file from network location

Gnanaguru: As long as you have appropriate access to your endpoint, this should work. [file://\\10.200.208.223\\share\\input] Thanks, Murari -- View this message in context: http://camel.465427.n5.nabble.com/Read-a-file-from-network-location-tp5667150p5717667.html Sent from the Camel - Users

Passing arguments to a customer splitter

Hello: Is there a way to pass arguments to a custom splitter? For eg - Route Builder calls a custom splitter - DDSResponseSplitService.splitStatusResponse() from(routesprops.getString(Constants.INBOUND)) .split().method(DDSResponseSplitService.class, "splitStatusResponse") .process(new

Cannot invoke Otherwise method due to the splitter

ter .to(archive); Thanks, Murari Raghavan -- View this message in context: http://camel.465427.n5.nabble.com/Cannot-invoke-Otherwise-method-due-to-the-splitter-tp5717811.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: onException invoked even when there is no exception

Thanks Claus. I would like the OnException to be route specific. When I define the onException right after .from, the .process call after the .split() cannot be resolved. That was the reason I moved it after the .split() call. Any suggestions? from("file://statusresponseinbound"