[ 
https://issues.apache.org/activemq/browse/CAMEL-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53721#action_53721
 ] 

Claus Ibsen commented on CAMEL-1928:
------------------------------------

Alexander

Good point. However we must make sure the current behavior is preserved.

I think changing the idempotentRepository option to a java.lang.Boolean type 
instead of boolean and let it be null by default.
Then we have 3 states: null, TRUE, FALSE and thus can determine if null = 
current behavior.
If TRUE or FALSE then use it or not.

Patches is mostly welcome with unit tests :)

> 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
>
> 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.

Reply via email to