On Tue, Jul 6, 2010 at 10:49 PM, Christian Mueller <christian.muel...@gmail.com> wrote: > > Thanks for the fast answer Claus and pointing this out. This is certainly the > best solution for many requirements. But as you know, if you have to create > an aggregated XML file, only appending the content is not sufficient enough. > First, we have to provide something like this: > > <?xml version="1.0" encoding="ISO-8859-1"?> > <orders> > > than we could append all messages. > > <order>...</order> > > At the end, we have to provide something like this: > > </orders> > > To detect the first message and to write the "header" is easy. Bur I'm not > sure, how I could detect that all messages are processed (CamelBatchSize > header is not available because I use the splitter streaming mode) to write > the file "footer". >
Just after the splitter is done you can continue routing and add the last pieces from write header to file split sub route for splitter transform append entry to file end write footer to file > Regards, > Christian > -- > View this message in context: > http://camel.465427.n5.nabble.com/Splitting-big-files-and-aggregate-the-big-responses-tp858166p946350.html > Sent from the Camel Development mailing list archive at Nabble.com. > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
