[ 
https://issues.apache.org/jira/browse/CAMEL-12990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717815#comment-16717815
 ] 

Gerold Broser commented on CAMEL-12990:
---------------------------------------

I am using a route that has just {{from("ftp:...")}} / {{to("file:...")}}.

The {{from}} endpoint is:
{code}
ftp://${ftp.user.name}@${ftp.server.name}:${ftp.server.port}?password=${FTP_USER_PWD}&fileName=${in.file}&localWorkDirectory=${PATH}/${data.in}&noop=true
{code}

If I replace {{localWorkDirectory=...}} with {{streamDownload=true}} the 
exception mentioned above occurs.

> FTP endpoint with 'localWorkDirectory' considers File Consumer's 'noop' option
> ------------------------------------------------------------------------------
>
>                 Key: CAMEL-12990
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12990
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-ftp
>    Affects Versions: 2.22.1
>            Reporter: Gerold Broser
>            Priority: Minor
>              Labels: feature, ftp
>
> [https://camel.apache.org/ftp2.html] reads:
> {quote}See [File|https://camel.apache.org/file2.html] for more options as all 
> the options from [File|https://camel.apache.org/file2.html] is inherited.
> {quote}
>  and in *Using Local Work Directory*:
> {quote}And finally, when the Exchange is complete the local file is deleted.
> {quote}
>  [https://camel.apache.org/file2.html] reads:
> {quote}
> |{{noop}}|{{false}}|If *{{true}}*, the file is not moved or deleted in any 
> way.|
> {quote}
> I have a use case where I'd need the file transferred to 
> \{{localWorkDirectory}} to stay there. Otherwise I have to change 
> \{{localWorkDirectory}} to something else and add a Producer endpoint to my 
> route which copies the file to the intended directory (i.e. the former 
> \{{localWorkDirectory}}), which is inconvenient with GiB-size files.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to