JIRA [email protected] wrote:
>
>
> [
> https://issues.apache.org/activemq/browse/CAMEL-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51973#action_51973
> ]
>
> Claus Ibsen commented on CAMEL-1653:
> ------------------------------------
>
> Good idea. I think I will give this option an overhaul and introduce an
> enum to choose what you want
>
> What we have now:
> - override
> - append
>
> And these additional options (if existing file exists):
> - fail
> - ignore
> - rename original file
> - write with a new filename (postfixed with _camel or something, leaving
> original file)
>
The rename original and write with a new filename options should be
repeatable, in case they result in a name collision as well. So maybe when
we write to new filename, if foo.txt fails we try foo2.txt, then foo3.txt,
etc. Similarly, if we need to move an original foo.txt, we move it to
foo2.txt, and if there is already a foo2.txt we move that to foo3.txt. In
either case we would probably want to have a plugable strategy so users can
decide on there own renaming policy.
--
View this message in context:
http://www.nabble.com/-jira--Created%3A-%28CAMEL-1653%29-clobber-option-for-FileComponent-tp23754402p23778035.html
Sent from the Camel Development mailing list archive at Nabble.com.
