That is expected, noop=true means do not copy the file ever again. You
need to use an idempotent repository where you store the key with the
file name and timestamp so the repo can know if its the same file or a
changed file.
btw its often much better to either delete or move the files after you
have processed the file, instead of leaving them as-is.
On Sun, Aug 9, 2015 at 11:18 PM, hayden74 <hdr...@gmail.com> wrote:
> Hi Camel experts.
> The issue I am facing is that Camel doesn't seem to copy a modified file
> after being copied the first time to its destination. The route used is:
>
> from("smb://networkDriveOne?noop=true&fileName=inputFile.csv")
> .to("smb://networkDriveTwo?fileExist=Override")
>
> When Camel is restarted, the inputFile.csv file is copied to its destination
> as expected. When inputFile.csv modified and saved in the input directory,
> however, Camel doesn't pick it up and override the one in the destination.
>
> Versions:
>
> Camel: 2.14.0
>
> ActiveMQ: 5.11.0
>
> Spring MVC: 4.1.6.RELEASE
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/smb-endpoint-modified-files-not-copied-to-destination-tp5770499.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2nd edition: http://www.manning.com/ibsen2
