Hello I'm trying to build a system where I consume files from a directory, perform transformations in several steps and finally deliver at an endpoint. In case the delivery of the transformed message succeeds, I want to route a copy of the original file as it was before consumation to a backup directory on disk. If the transformation fails, I want a copy of the original file copied to an error directory.
I have thought up a couple of solutions but I don't think they are best practice. One is somehow keeping a copy in a queue and then going back and identifying on an id and copy the. The other one is bundling the original file with the transforming message and then extracting the original file and write it to the according directory/queue. What kind of approach would be good? -- View this message in context: http://old.nabble.com/Keep-original-message-several-%22steps%22-back.-tp27626057p27626057.html Sent from the Camel - Users mailing list archive at Nabble.com.
