camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-6669) doneFileName=${file:name} don't work with ftp component
Date Mon, 26 Aug 2013 15:01:58 GMT

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

Claus Ibsen commented on CAMEL-6669:
------------------------------------

Can you double check on your end, as we have unit test that test this use-cases
org.apache.camel.component.file.remote.FtpProducerDoneFileNameTest
                
> doneFileName=${file:name} don't work with ftp component
> -------------------------------------------------------
>
>                 Key: CAMEL-6669
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6669
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-ftp
>    Affects Versions: 2.11.1
>            Reporter: Steffen Bollweber
>
> I tried to write a file on a ftp server using a done file to signal the end of the file
transmission. I guess the file/ftp component preserves the doneFileName option. But the ftp
component doesn't replace the doneFileName=${file:name} correctly. 
> My fpt endpoint looks like this: 
> {code:java}
> .to(ftp:myuser@myserver/mypath?doneFileName=${file:name}.done&charset=utf-8&password={{ftp.passwd}})
> {code}
> But the route generates only a file with name {{name.done}}
> I also tried the option stepwise=false as described here [http://camel.465427.n5.nabble.com/doneFileName-doesn-t-seem-to-work-td4704701.html].
With the same result.
> I also test this option with the file component and it works. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message