[
https://issues.apache.org/activemq/browse/CAMEL-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-1195:
-------------------------------
Affects Version/s: 1.5.1
Fix Version/s: (was: 1.5.1)
I am changing target for this one to Camel 2.0 as the refactor is a bit bigger:
- New URI options
- Old URI options removed (consider them @deprecated in 1.x)
- New interface for pluggable readlock strategies
- etc.
> File component - exclusive read lock strategy using renaming
> ------------------------------------------------------------
>
> Key: CAMEL-1195
> URL: https://issues.apache.org/activemq/browse/CAMEL-1195
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.5.0, 1.5.1
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> See CAMEL-760
> But an end user has problem with this, the read lock can not be granted and a
> IOException is thrown.
> We should support the same strategy as the FTP consumer does with a try to
> rename the file.
> Also we should allow some nice URI options to select the strategy
> - nio locks
> - renaming
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
