camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: File/Ftp endpoint consumer. prefix
Date Tue, 08 May 2012 09:43:53 GMT

Yeah as you have noticed the ftp component inherits 99% of the options
from the file component. There is a few which it doesn't, and we ought
to have notes on the file wiki page about that. For example the rename
read lock strategy used not to be supported on FTP. But I think we got
a patch from the community this year. And so on.

The producer is even more similar between file and ftp, as they use
the generic producer, and then its the file operations implementation
that is the difference.

On Mon, May 7, 2012 at 12:59 PM, Łukasz Dywicki <> wrote:
> Hey Claus,
> I checked out ScheduledPollConsumer and indeed, properties like initialDelay and so on
exists in this class. The problem is still documentation. File endpoint and consumer is not
really different than Ftp/Sftp consumer.
> File endpoint contains only following properties:
> - FileSeparator
> - File (which is delegated to configuration.setDirectory)
> - CopyAndDeleteOnRenameFail
> FTP endpoint do not have any specific properties but it extends same class like File
endpoint (GenericFileEndpoint) and have documented only few options. Should I assume that
these properties are not supported or they are missed in documentation?
> For example:
> - autoCreate
> - bufferSize
> - startingDirectoryMustExist
> - delete
> - flatten
> - charset
> and so on... If they are not supported in FTP/SFTP component they should not be present
in GenericFileEndpoint/Consumer/Producer (as they are specific for File component only). Please
clarify what is the status of documentation.
> Kind regards,
> Lukasz Dywicki
> --
> Code-House
> Wiadomość napisana przez Claus Ibsen w dniu 5 maj 2012, o godz. 07:37:
>> Hi
>> Any parameter with consumer. prefix will be configured as properties
>> on the created consumer.
>> Now the file and ftp consumers is scheduled based, and therefore these
>> options apply to their scheduling which is in an inherited class.
>> Now in terms of the consumer.delay option, then we got tired of having
>> to specify consumer.delay, instead of just delay. So we added support
>> for these shortcuts a long time ago.
>> The consumer. prefix is not so often used, as often a component
>> exposes all its options in the endpoint, and then uses these options
>> to configure its consumer/producers.
>> On Fri, May 4, 2012 at 9:38 PM, Łukasz Dywicki <> wrote:
>>> Hey,
>>> I have question about File and FTP endpoints documentation. Both pages on wiki
points to consumer. prefix for some parameters - for example initialDelay or delay, but they
are not used at all. Or at least they are set directly on endpoint (GenericFileEndpoint) instance.
If it is used somewhere else or I am blind? FTP documentation also points to FTPConsumer only
(deleteFile, userFixedDelay). I've walked through code and I've found no usage of these parameters
directly in FtpConsumer. Should these parameters be named delete, useFixedDelay and so on?
>>> Best regards,
>>> Lukasz Dywicki
>>> --
>>> Code-House
>> --
>> Claus Ibsen
>> -----------------
>> CamelOne 2012 Conference, May 15-16, 2012:
>> FuseSource
>> Email:
>> Web:
>> Twitter: davsclaus, fusenews
>> Blog:
>> Author of Camel in Action:

Claus Ibsen
CamelOne 2012 Conference, May 15-16, 2012:
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message