[
https://issues.apache.org/activemq/browse/CAMEL-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53731#action_53731
]
Claus Ibsen commented on CAMEL-1928:
------------------------------------
Thanks, we need an unit test as well. So if you have the time and energy please
write one if possible.
> 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.
