You can ftp to a temp directory and then do an atomic move/rename after it is finished. Or you can write it to the same directory with a special letter or character at the beginning which the consumer won't look for. For example, it might be t- for temporary files being FTP'd over and when it is done you rename to the final file name. But the rename/moves are done atomically on the system you so you don't get the corruption problem.
On Sat, Jul 30, 2016 at 7:43 AM, DariusX <[email protected]> wrote: > There's a readLock=changed option that might work for you. > Documentation here: http://camel.apache.org/ftp2.html > > > masalinas wrote > > Sometimes when the endpoint is fired, the client ftp didn't had finish to > > upload the file so, the endpoint get a file corrupted, and I have > problems > > with this. > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/FTP-Client-and-File-endpoint-in-camel-sharing-a-folder-tp5785620p5785706.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
