No, I want to send that last line without aggregating it, or aggregating it as the first and only exchange of that aggregation strategy. What I actually need is to have a final exchange, containing a line from the file and the FILE_COMPLETE header, that gets sent through a few service units, each processes its data, and the last service unit finds that it's the end of the file and resets a flag into the database so that the next file from the folder gets read. If I aggregate it with other exchanges, then split everything into the next service unit and so on I can't keep track of the end of the file, I risk having more than one exchange with this header.
If you need a better explanation please let me know. Thanks. -- View this message in context: http://camel.465427.n5.nabble.com/Aggregate-exchanges-until-before-EoF-tp5728680p5728686.html Sent from the Camel - Users mailing list archive at Nabble.com.
