same file and one moves it before the other and hence the
other throws 'cannot rename' exception.
Any way to avoid this race condition?
--
View this message in context:
http://camel.465427.n5.nabble.com/File-component-language-preMove-only-tp1843111p5730477.html
Sent from the Camel -
nd of scenarios? If so how to
> do the same with FTP/SFTP?
>
> Thanks for your response and happy to provide more details. :)
>
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/File-component-language-preMove-only-tp1843111p5728629
enarios? If so how to
do the same with FTP/SFTP?
Thanks for your response and happy to provide more details. :)
--
View this message in context:
http://camel.465427.n5.nabble.com/File-component-language-preMove-only-tp1843111p5728629.html
Sent from the Camel - Users mailing list archive at Nabble.com.
portant to know what version you use.
> Thanks.
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/File-component-language-preMove-only-tp1843111p5728565.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
quot;processing
${file:name}").to("file://files/outbox?fileName=${file:name}+${exchangeId}")
Are we missing anything obvious in using Camel this way?
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/File-component-language-preMove-only-tp1843111p57
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 wrote:
> I created a ticket to track this
> https://i
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 wrote:
> Hi
>
> What if preMove is a bit special. So you can do
> preMove=moveMe&noop=true. Which then tells
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 wrote:
> That doesn't work, since by the time route completes, file is moved
> el
Hi
Yeah the file component is starting to be overloaded with
move/delete/noop options :)
Maybe the noop should have been an action option, so you could specify
what you want to do
action=preMove
action=preMove,move
action=preMove,delete
action=noop
action=delete
action=move (* default)
Let's t
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.
Th
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 wrote:
> Hi,
>
> Is it possible to pre-move files, but not move them once processing
> complete? I use "preMove" to ensure camel
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 perform
12 matches
Mail list logo
