We are in the process of using the Aggregator component in our integration,
and I need some clarification of whether my understanding of its persistence
is correct.
We are reading files from a folder structure like this:
user1/inv1/..
user1/inv2/..
where all files found in e.g. user1/inv1 has to be grouped and handled
together - which is why we use the aggregator to perform the grouping of the
files.
We are reading the folder structure from a ftp-server, and originally I had
expected, that if something went wrong in the aggregator or later in the
route, the files would still present in the folder structure (like it would
in a non-aggregator route).
But I can see that this is not the case, and after reading chapter 8 of
Camel in Action, I assume that what I need to do is to use the HawtDb as a
recoverable aggregation repository and this way add persistence/recovery to
the route.
Is this the correct approach or can the route, by other means, be made to
work so it leaves the files in the folder structure in case it is unable to
complete the route?
/Mikael
--
View this message in context: http://camel.465427.n5.nabble.com/Aggregator-clarification-tp5119201p5119201.html
Sent from the Camel - Users mailing list archive at Nabble.com.
