camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel <pag...@gmail.com>
Subject Re: File component/language: preMove only
Date Fri, 30 Jul 2010 18:34:43 GMT
Cool - thanks a lot. Yes, seems like preMove is a bit special indeed - it
addresses technical issue of concurrency as opposed to functional
requirements of file placement after processing...

Pavel
On Wed, Jul 28, 2010 at 12:31 PM, Claus Ibsen <claus.ibsen@gmail.com> wrote:

> I created a ticket to track this
> https://issues.apache.org/activemq/browse/CAMEL-3003
>
> And you can now use preMove together with noop|delete.
>
>
> On Tue, Jul 27, 2010 at 2:50 PM, Claus Ibsen <claus.ibsen@gmail.com>
> wrote:
> > Hi
> >
> > What if preMove is a bit special. So you can do
> > preMove=moveMe&noop=true. Which then tells Camel to pre move the file.
> > But on commit it should just leave the file as is.
> >
> >
> >
> > On Fri, Jul 23, 2010 at 12:05 PM, Pavel <pagrus@gmail.com> wrote:
> >> 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.ibsen@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 <pagrus@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
> >>>
> >>
> >
> >
> >
> > --
> > 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
> >
>
>
>
> --
> 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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message