In this case, chances are that adding .to("file:kind-of-failed-directory")
at some point in the dead letter channel logic helps.
useOriginalMessage() may be of interest too.Alex On Sat, May 18, 2019 at 10:14 AM Jonathan Cook <jonathan.c...@erars.plus.com> wrote: > Thanks for the replies > > The moveFailed does do what I want but only when I remove the configured > errorHandler from my routes. In my error handler I have other logic such > as sending an email notification. So I don't think I can sue the > moveFailed unless there is a way to be able to use both? > > Thanks > > On 17/05/2019 19:03, Jonathan Cook wrote: > > Hello, > > > > I am using the file endpoint with delete=true. My routes pick up files > > from a directory and then pass through a number of steps, so are > > reasonably complex. I have a dead letter route where in the event of > > an error I want to move the original file to a kind of failed > > directory area. > > > > But the problem is that when an error occurs, by the time the code > > runs inside the dead letter route, the original file has already been > > deleted by the FileComponent because of delete=true. If I set this to > > false it works OK but the file stays at the original folder which I > > don't want. > > > > Do I have to manage this myself, i.e not use delete=true and have > > another step in my route (bean or processor) which would delete or > > move the file from the original directory at the end of all the > > processing rather than rely on the file component? > > > > Thanks for any suggestions! > > > > Paul > > > >
