camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Erker (JIRA)" <>
Subject [jira] [Commented] (CAMEL-6137) Send siteCommand(s) without uploading files
Date Thu, 21 Mar 2013 18:09:18 GMT


Carsten Erker commented on CAMEL-6137:

Just sent a pull request on Github:


Part 1
- Added a new option "upload" to the producer which works according to option "download" in
the FTP consumer: If false, no file will be uploaded, no temporary file will be created, no
done file will be created, but the Exchange.FILE_NAME_PRODUCED header will be set. Defaults
to true.
- Since I wanted the "upload" option to work similar as the "download" option, I added an
isUploadFile() method to the GenericFileProducer in camel-core. This is the only change in

Part 2
- Added a new option "siteCommandCapture" to the RemoteFileConfiguration: if true, the output
of the site commands will be returned in the exchange's body as a List<String> with
the output of each executed site command as a list element in order of execution. If false,
the body remains untouched. Defaults to false.

The default behaviour remains as before.
> Send siteCommand(s) without uploading files
> -------------------------------------------
>                 Key: CAMEL-6137
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-ftp
>    Affects Versions: 2.10.4
>            Reporter: Carsten Erker
>             Fix For: Future
> Currently, Camel sends FTP SITE commands only after log-in and before uploading a file.

> In general, SITE commands can be virtually anything: We now got a use case where we need
to communicate with an FTP server in terms of SITE commands, most of the time without the
need to upload anything. I.e., send a SITE command, capture the reply and hand it back to
the application.
> In camel-ftp, this could be done with a new property which tells the component to not
upload a file and get the server response, e.g. in the body or as a header attribute. This
is only needed for the producer side.
> We'd like to provide the code for this.

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:

View raw message