That doesn't work, since by the time route completes, file is moved
elsewhere.
Do you think preMove-only could be useful extension? I know it is useful for
me, but not sure how typical such requirement is.
If so, I could e.g. add ${null} simple expressions, or "noMove=true" to file
component.
Thanks,
Pavel
On Fri, Jul 23, 2010 at 10:09 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> Hi
>
> Have you tried with move=. to indicate current folder?
>
> But no its, not a feature of camel to only pre move and then noop.
>
>
>
> On Fri, Jul 23, 2010 at 9:03 AM, Pavel <pag...@gmail.com> wrote:
> > Hi,
> >
> > Is it possible to pre-move files, but not move them once processing
> > complete? I use "preMove" to ensure camel from 2 different cluster nodes
> > don't process the same file twice - file is moved into different
> directory
> > and not scanned anymore.
> > "move" is not necessary, as custom components performs logic on file
> > archival, stores metadata in the database, etc.
> > Seems like setting "move" to null should do what I need, but I'm not
> quite
> > sure how to do that. The "&move=null" will create directory called
> "null",
> > not specifying anything will default to ".camel", and adding "&noop=true"
> > disables preMove.
> >
> > Is there something in file language that allows setting nulls? Or is
> there a
> > way to have preMove without move for file component?
> >
> >
> > --
> > Best regards,
> > Pavel
> >
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Author of Camel in Action: http://www.manning.com/ibsen/
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
