Re: problem with camel:multicast

Hello Christian thanks for the reply. will try to write a small unittest for that and get back to you as soon as i can w/kindest regards marco On Sat, Jul 14, 2012 at 11:25 PM, Christian Müller < christian.muel...@gmail.com> wrote: > Hello Marco! > > You should start on this page [1]. We have

Accessing Number of Splits after the Splitter has done its job

Hello, I have a route which splits a large file into small chunks in a streaming mode based on number of lines. Hence, I wont know upfront as to how many splits shall be done. After the splitting is done, I use the .end() to continue processing in my route and want to know how many splits were done

Re: Welcome to my blog mainly about Apache Camel

Check out my new article about EIP and Camel: http://michalwarecki.blogspot.com/2012/07/eip-in-action.html It contains 4 practical example of how to use EIP's and Camel. Comments are very welcome (even criticizing). -- View this message in context: http://camel.465427.n5.nabble.com/Welcome-to-my

Re: Accessing Number of Splits after the Splitter has done its job

Yes, provide your own AggregationStrategy. Look for the section "What the Splitter returns" and "Specifying a custom aggregation strategy" in [1]. I would suggest something like this: Check the new exchange whether it has the exchange property "CamelSplitSize". If it has, set this exchange propert

Re: Usage of Scala DSL

Hi The multicast will send a copy to all the processors, so in your case, you have 4 processors - 2 transform - 2 logs I guess what you want is for the transform + log to be a pair. So you would need to use the pipes and filters eip inside the multicast. With Scala DSL you can possible do that by

Re: problem with camel:multicast

Hi This seems a bit odd. Have you tried with only 1 of the beans, to see that the volatiliy bean is invoked and you can see if it works? >From the multicast EIP point of view, its just all 3 processors in its output to process a copy of the same message. So it shouldn't matter if its a bean, seda

Preventing reading of a large XML file in memory

Hi, I am using Camel to transfer a file from my app server to an FTP server before converting it to a different format. The incoming file can be potentially huge (60 to 100 gbs) in size and I want to prevent Camel from reading the whole file in memory. I would like to call a bean which takes the in