It isn't clear how you want to use Camel in this picture. if it is simply to
poll for files, and if the file is not huge, a simple/naive approach would
be to read in the whole file and do all the steps you need. All as a single
Processor following the "from:file" consumer.
The the Data/Task sections always follow one another, as in your example,
you could attempt to split the file into sections that way, and handle each
split task differently, based on the "operation". It will be more complex to
code. So the question is: what would you gain by this?
View this message in context:
Sent from the Camel - Users mailing list archive at Nabble.com.