camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: FTP endpoint markerFile
Date Tue, 01 Jun 2010 09:02:43 GMT
On Tue, Jun 1, 2010 at 10:57 AM, Onaluf <selim.arsever@gmail.com> wrote:
>
> Hi, thanks for your quick reply!
>
> Is there a reason for this ? Would you advise us against cutomizing the FTP
> endpoint, even at the cost of loosing the generality of the FTP access (for
> example by limiting to some FTP servers... or some settings of them)?
>

Feel free to create a JIRA ticket to have the markerFile supported by
FTP as well.
Of course this requires write access from the FTP user. And we can
then just document this in the wiki.



>
> Claus Ibsen-2 wrote:
>>
>> On Tue, Jun 1, 2010 at 9:03 AM, Onaluf <selim.arsever@gmail.com> wrote:
>>>
>>> Hi, I'm using camel 2.3 and I couldn't find a way to enable the
>>> "markerFile"
>>> lock strategy for a FTP endpoint. In the docs it's written that "changed"
>>> and "fileLock" are not available but nothing about "markerFile".
>>>
>>
>> MarkerFile is NOT supported for FTP. In fact the only option supported
>> is: rename and none.
>> I will improve the documentation.
>>
>>
>>> In the source code I found (in GenericFileProcessStrategyFactory, from
>>> line
>>> 79):
>>>
>>>      if (ObjectHelper.isNotEmpty(readLock)) {
>>>            if ("none".equals(readLock) || "false".equals(readLock)) {
>>>                return null;
>>>            } else if ("rename".equals(readLock)) {
>>>                GenericFileRenameExclusiveReadLockStrategy<T>
>>> readLockStrategy = new GenericFileRenameExclusiveReadLockStrategy<T>();
>>>                Long timeout = (Long) params.get("readLockTimeout");
>>>                if (timeout != null) {
>>>                    readLockStrategy.setTimeout(timeout);
>>>                }
>>>                return readLockStrategy;
>>>            }
>>>        }
>>>
>>> Which seams to imply that only "rename" is supported? (From what I
>>> understand "markerFile" only works when it's the default of the endpoint
>>> and
>>> cannot be set if it isn't.) Is this correct ? Is there a reason for this
>>> or
>>> can I patch this to use the strategy anyway?
>>>
>>>
>>> --
>>> View this message in context:
>>> http://old.nabble.com/FTP-endpoint-markerFile-tp28738325p28738325.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> 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
>>
>>
>
> --
> View this message in context: http://old.nabble.com/FTP-endpoint-markerFile-tp28738325p28739197.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>



-- 
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
View raw message