Hi
If you mean
http://camel.apache.org/idempotent-consumer.html
Then thats an EIP and its not 100% the same. As the file/ftp component
has idempotent out of the box. This allows those to know earlier if a
file has been consumed before or not, and then not even attempt to
consume the file.
The EIP is generic and works with any camel route. But then the
consumer would have picked up and create a message to route. So that
happens a bit later.
And since its an EIP then Camel setup and start it properly.
Your issue is that you create those endpoints manually using java
code, and therefore must wire and setup it correctly.
On Tue, Jul 15, 2014 at 12:57 PM, dermoritz <tantea...@hotmail.com> wrote:
> Thanks for this hint!
> This should be mentioned in docs. In my case i didn't saw this log entry but
> i saw a log entry for each file name being added to repository - so i didn't
> came to the idea that repository must be started.
> Now i am working with ".idempotentConsumer(header("CamelFileName"),
> fileRep)" This is working without ".start()" why?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-ftp-consumer-ignores-idempotent-file-repository-on-start-tp5753615p5753832.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
