Sounds like a pretty specialized use case. You could always write your own component or a processor that handles the output of the file2 consumer (which will be a stream) . However when I hear of such specialized use cases I always wonder if the person is not going about it the wrong way. What is the business requirement you are trying to obtain and why do you need to read the metadata first before consuming the file?
*Robert Simmons Jr. MSc. - Lead Java Architect @ EA* *Author of: Maintainable Java (Kindle <http://www.amazon.com/Maintainable-Java-Robert-Simmons-Jr-ebook/dp/B00AKHI69K>)(iTunes <https://itunes.apple.com/us/book/maintainable-java/id585666097?mt=11>)* *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39 <http://www.linkedin.com/pub/robert-simmons/40/852/a39>* On Thu, Jun 19, 2014 at 4:28 PM, vishveshmulay <[email protected]> wrote: > I have to setup camel to process data files where the first line of the > file > is the metadata and then it follows with millions of lines of actual data. > The metadata dictates how the data is to be processed. What I am looking > for > is something like this: > > Read first line (metadata) and populate a bean (with metadata) --> 2. then > send data 1000 lines at a time to the data processor which will refer to > the > bean in step # 1 > Is it possible in Apache Camel ? > > I've posted same question in stackoverflow at > > http://stackoverflow.com/questions/24315861/processing-data-based-on-the-metadata-in-the-file-using-apache-camel > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/processing-data-based-on-the-metadata-in-the-file-using-apache-camel-tp5752593.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
