[jira] Updated: (CAMEL-1928) FileConsumer should allow files to be processed more than once when "noop" setting is used.

["Alexander Lee (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/CAMEL-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Lee updated CAMEL-1928:
---------------------------------

    Attachment: GenericFileEndpoint.java
                FileEndpoint.java

This a minimal patch to allow use of the "noop" setting without an inprogress repository.  This allows files to be picked up and processed everytime polling occurs.  This is useful where the files are basically templates or config that kicks off a regular process.

> FileConsumer should allow files to be processed more than once when "noop" setting is used.
> -------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1928
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1928
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.0-M3
>            Reporter: Alexander Lee
>            Priority: Minor
>         Attachments: FileEndpoint.java, GenericFileEndpoint.java
>
>
> If the "noop" setting is used with the FileConsumer, then this forces use of the idempotent repository.  This means that files are only ever picked up once.  While this is probably the desired behaviour for most users, it makes it difficult to use the files to generate events on a timed basis.   For instance, a file could be used to store query configuration which was read every hour and used to query a database, the data from which would be added to an exchange and sent to the next step.  In this case we don't want to delete or move the original file and we want to read it again.
> At the moment this behaviour can be simulated by using "preMove" to move the file to a new extension, and then "move" to move it back.  It would be better if there was a way to default use of the idempotent repository as is the case now, but also provide a way to explicitly turn it off if required.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.