This tutorial aims to guide the reader through the stages of creating a project which uses Camel to facilitate the routing of messages from a JMS queue to a Spring service. The route works in a synchronous fashion returning a response to the client.

Writing the Server

Create the Spring Service

For this example the Spring service (= our business service) on the server will be a simple multiplier which trebles in the received value.

See Also

CXF Component

The cxf: component provides integration with Apache CXF for connecting to JAX-WS services hosted in CXF.

Where directoryname represents the underlying directory. The directory name is a relative path. Absolute paths are not supported. The relative path can contain nested folders, such as /inbox/us.

For Camel versions before Camel 2.16, the directoryName must exist already as this component does not support the autoCreate option (which the file component does). The reason is that its the FTP administrator (FTP server) task to properly setup user accounts, and home directories with the right file permissions etc.

For Camel 2.16, autoCreate option is supported. When consumer starts, before polling is scheduled, there's additional FTP operation performed to create the directory configured for endpoint. The default value for autoCreate is true.

If no username is provided, then anonymous login is attempted using no password.
If no port number is provided, Camel will provide default values according to the protocol (ftp = 21, sftp = 22, ftps = 2222).

You can append query options to the URI in the following format, ?option=value&option=value&...

This component uses two different libraries for the actual FTP work. FTP and FTPS uses Apache Commons Net while SFTP uses JCraft JSCH.

The FTPS component is only available in Camel 2.2 or newer.
FTPS (also known as FTP Secure) is an extension to FTP that adds support for the Transport Layer Security (TLS) and the Secure Sockets Layer (SSL) cryptographic protocols.

URI Options

Name	Default Value	Description
`username`	`null`	Specifies the u sername to use to log in to the remote file systen.
`password`	`null`	Specifies the password to use to log in to the remote file system.
`account`	`null`	Camel 2.15.2: Specified the account to use to login to the remote FTP server (only for FTP and FTP Secure)
`binary`	`false`	Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (`false).`
`disconnect`	`false`	Camel 2.2: Whether or not to disconnect from remote FTP server right after use. Can be used for both consumer and producer. Disconnect will only disconnect the current connection to the FTP server. If you have a consumer which you want to stop, then you need to stop the consumer/route instead.
`localWorkDirectory`	`null`	When consuming, a local work directory can be used to store the remote file content directly in local files, to avoid loading the content into memory. This is beneficial, if you consume a very big remote fil e and thus can conserve memory. See below for more details.
`passiveMode`	`false`	FTP and FTPS only: Specifies whether to use passive mode connections. Default is active mode (`false`).
`securityProtocol`	`TLS`	FTPS only: Sets the underlying security protocol. The following values are defined: `TLS`: Transport Layer Security `SSL`: Secure Sockets Layer
`disableSecureDataChannelDefaults`	`false`	Camel 2.4: FTPS only: Whether or not to disable using default values for `execPbsz` and `execProt` when using secure data transfer. You can set this option to `true` if you want to be in full control what the options `execPbsz` and `execProt` should be used.
`download`	`true`	Camel 2.11: Whether the FTP consumer should download the file. If this option is set to `false`, then the message body will be `null`, but the consumer will still trigger a Camel Exchange that has details about the file such as file name, file size, etc. It's just that the file will not be downloaded.
streamDownload	false	Camel 2.11: Whether the consumer should download the entire file up front, the default behavior, or if it should pass an InputStream read from the remote resource rather than an in-memory array as the in body of the Camel Exchange. This option is ignored if download is false or is localWorkDirectory is provided. This option is useful for working with large remote files.
`execProt`	`null`	Camel 2.4: FTPS only: Will by default use option `P` if secure data channel defaults hasn't been disabled. Possible values are: `C`: Clear `S`: Safe (SSL protocol only) `E`: Confidential (SSL protocol only) `P`: Private
`execPbsz`	`null`	Camel 2.4: FTPS only: This option specifies the buffer size of the secure data channel. If option `useSecureDataChannel` has been enabled and this option has not been explicit set, then value `0` is used.< /p>
`isImplicit`	`false`	FTPS only: Sets the security mode(implicit/explicit). Default is explicit (`false`).
`knownHostsFile`	`null`	SFTP only: Sets the `known_hosts` file, so that the SFTP endpoint can do host key verification.
`knownHostsUri`	`null`	SFTP only: Camel 2.11.1: Sets the `known_hosts` file (loaded from classpath by default), so that the SFTP endpoint can do host key verification.
`keyPair`	`null`	SFTP only: Camel 2.12.0: Sets the Java KeyPair for SSH public key authentication, it supports DSA or RSA keys.
`privateKeyFile`	`null`	SFTP only: Set the private key file to that the SFTP endpoint can do private key verification.
`privateKeyUri`	`null`	SFTP only: Camel 2.11.1: Set the private key file (loaded from classpath by default) to that the SFTP endpoint can do private key verification.
`privateKey`	`null`	SFTP only: Camel 2.11.1: Set the private key as byte[] to that the SFTP endpoint can do private key verification.
`privateKeyFilePassphrase`	`null`	SFTP only: Deprecated: use `privateKeyPassphrase` instead. Set the private key file passphrase to that the SFTP endpoint can do private key verification.
`privateKeyPassphrase`	`null`	SFTP only: Camel 2.11.1: Set the private key file passphrase to that the SFTP endpoint can do private key verification.
`preferredAuthentications`	`null`	SFTP only: Camel 2.10.7, 2.11.2,2.12.0: set the preferred authentications which SFTP endpoint will used. Some example include:password,publickey. If not specified the default list from JSCH will be used.
`ciphers`	`null`	Camel 2.8.2, 2.9: SFTP only Set a comma separated list of ciphers that will be used in order of preference. Possible cipher names are defined by JCraft JSCH. Some examples include: aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc. If not specified the default list from JSCH will be used.
`fastExistsCheck`	`false`	Camel 2.8.2, 2.9: If set this option to be true, camel-ftp will use the list file directly to check if the file exists . Since some FTP server may not support to list the file directly, if the option is false, camel-ftp will use the old way to list the directory and check if the file exists. Note from Camel 2.10.1 onwards this option also influences `readLock=changed` to control whether it performs a fast check to update file information or not. This can be used to speed up the process if the FTP server has a lot of files.
`strictHostKeyChecking`	`no`	SFTP only: Camel 2.2: Sets whether to use strict host key checking. Possible values are: `no`, `yes` and `ask`. `ask` does not make sense to use as Camel cannot answer the question for you as its meant for human intervention. Note: The default in Camel 2.1 and below was `ask`.
`maximumReconnectAttempts`	`3`	Specifies the maximum reconnect attempts Camel performs when it tries to connect to the remote FTP server. Use 0 to disable this behavior.
`reconnectDelay`	`1000`	Delay in millis Camel will wait before performing a reconnect attempt.
`connectTimeout`	`10000`	C amel 2.4: Is the connect timeout in millis. This corresponds to using `ftpClient.connectTimeout` for the FTP/FTPS. For SFTP this option is also used when attempting to connect.
`soTimeout`	`null / 30000`	FTP and FTPS Only: Camel 2.4: Is the `SocketOptions.SO_TIMEOUT` value in millis. A good idea is to configure this to a value such as 300000 (5 minutes) to not hang a connection. On SFTP this option is set as timeout on the JSCH Session instance. Also SFTP from Camel 2.14.3/2.15.3/2.16 onwards. From Camel 2.16 onwards the default is 30000 (30 sec).
`timeout`	`30000`	FTP and FTPS Only: Camel 2.4: Is the data timeout in millis. This corresponds to using `ftpClient.dataTimeout` for the FTP/FTPS. For SFTP there is no data timeout.
`throwExceptionOnConnectFailed`	`false`	Camel 2.5: Whether or not to thrown an exception if a successful connection and login could not be establish. This allows a custom `pollStrategy` to deal with the exception, for example to stop the consumer or the likes.
`siteCommand`	`null`	FTP and FTPS Only: Camel 2.5: To execute site commands after successful login. Multiple site commands can be separated using a new line character (\n). Use `help site` to see which site commands your FTP server supports.
`stepwise`	`true`	Camel 2.6: Whether or not stepwise traversing directories should be used or not. Stepwise means that it will CD one directory at a time. See more details below. You can disable this in case you can't use this approach.
`separator`	`UNIX`	Camel 2.6: Dictates what path separator char to use when uploading files. `Auto` = Use the path provided without altering it. `UNIX` = Use unix style path separators. `Windows` = Use Windows style path separators. Since Camel 2.15.2: The default value is changed to UNIX style path, before Camel 2.15.2: The default value is `Auto.`
`chmod`	`null`	SFTP Producer Only: Camel 2.9: Allows you to set chmod on the stored file. For example `chmod=640`.
`compression`	0	SFTP Only: Camel 2.8.3/2.9: To use compression. Specify a level from 1 to 10. Important: You must manually add the needed JSCH zlib JAR to the classpath for compression support.
`receiveBufferSize`	`32768`	FTP/FTPS Only: Camel 2.15.1: The buffer size for downloading files. The default size is 32kb.
`ftpClient`	`null`	FTP and FTPS Only: Camel 2.1: Allows you to use a custom `org.apache.commons.net.ftp .FTPClient` instance.
`ftpClientConfig`	`null`	FTP and FTPS Only: Camel 2.1: Allows you to use a custom `org.apache.commons.net.ftp.FTPClientConfig` instance.
`ftpClientConfig.XXX`		FTP and FTPS Only: To configure various options on the FTPClient instance from the uri. For example: `ftpClientConfig.receiveDataSocketBufferSize=8192&ftpClientConfig.sendDataSocketBufferSize=8192`
`serverAliveInterval`	`0`	SFTP Only: Camel 2.8 Allows you to set the serverAliveInterval of the sftp session
`serverAliveCountMax`	`1`	SFTP Only: Camel 2.8 Allows you to set the serverAliveCountMax of the sftp session
`ftpClient.trustStore.file`	`null`	FTPS Only: Sets the trust store file, so that the FTPS client can look up for trusted certificates.
`ftpClient.trustStore.type`	`JKS`	FTPS Only: Sets the trust store type.
`ftpClient.trustStore.algorithm`	`SunX509`	FTPS Only: Sets the trust store algorithm.
`ftpClient.trustStore.password`	`null`	FTPS Only: Sets the trust store password.
`ftpClient.keyStore.file`	`null`	FTPS Only: Sets the key store file, so that the FTPS client can look up for the private certificate.
`ftpClient.keyStore.type`	`JKS`	FTPS Only: Sets the key store type.
`ftpClient.keyStore.algorithm`	`SunX509`	FTPS Only: Sets the key store algorithm.
`ftpClient.keyStore.password`	`null`	FTPS Only: Sets the key store password.
`ftpClient.keyStore.keyPassword`	`null`	FTPS Only: Sets the private key password.
`sslContextParameters`	`null`	FTPS Only: Camel 2.9: Reference to a `org.apache.camel.util.jsse.SSLContextParameters` in the Registry. This reference overrides any configured SSL related o ptions on ftpClient as well as the securityProtocol (SSL, TLS, etc.) set on FtpsConfiguration. See Using the JSSE Configuration Utility.
`proxy`	`null`	SFTP Only: Camel 2.10.7, 2.11.1: Reference to a `com.jcraft.jsch.Proxy` in the Registry. This proxy is used to consume/send messages from the target SFTP host.
`useList`	`true`	FTP/FTPS Only: Camel 2.12.1: Whether the consumer should use FTP LIST command to retrieve directory listing to see which files exists. If this option is set to `false`, then `stepwise=false` must be configured, and also `fileName` must be configured to a fixed name, so the consumer knows the name of the file to retrieve. When doing this only that single file can be retrieved. See further below for more details.
`ignoreFileNotFoundOrPermissionError`	`false`	Camel 2.12.1: Whether the consumer should ignore when a file was attempted to be retrieved but did not exist (for some reason), or failure due insufficient file permission error. Camel 2.14.2: This option now applies to directories as well.
`sendNoop`	`true`	Camel 2.16: Producer only. Whether to send a noop command as a pre-write check before uploading files to the FTP server. This is enabled by default as a validation of the connection is still valid, which allows to silently re-connect to be able to upload the file. However if this causes problems, you can turn this option off.
`jschLoggingLevel`	`WARN`	SFTP Only: Camel 2.15.3/2.16: The logging level to use for JSCH activity logging. As JSCH is verbose at by default at INFO level the threshold is WARN by default.

You can configure additional options on the ftpClient and ftpClientConfig from the URI directly by using the ftpClient. or ftpClientConfig. prefix.

For example to set the setDataTimeout on the FTPClient to 30 seconds you can do:

Where directoryname represents the underlying directory. The directory name is a relative path. Absolute paths are not supported. The relative path can contain nested folders, such as /inbox/us.

For Camel versions before Camel 2.16, the directoryName must exist already as this component does not support the autoCreate option (which the file component does). The reason is that its the FTP administrator (FTP server) task to properly setup user accounts, and home directories with the right file permissions etc.

For Camel 2.16, autoCreate option is supported. When consumer starts, before polling is scheduled, there's additional FTP operation performed to create the directory configured for endpoint. The default value for autoCreate is true.

If no username is provided, then anonymous login is attempted using no password.
 If no port number is provided, Camel will provide default values according to the protocol (ftp = 21, sftp = 22, ftps = 2222).

You can append query options to the URI in the following format, ?option=value&option=value&...

This component uses two different libraries for the actual FTP work. FTP and FTPS uses Apache Commons Net while SFTP uses JCraft JSCH.

The FTPS component is only available in Camel 2.2 or newer.
 FTPS (also known as FTP Secure) is an extension to FTP that adds support for the Transport Layer Security (TLS) and the Secure Sockets Layer (SSL) cryptographic protocols.

URI Options

Name	Default Value	Description
`username`	`null`	Specifies the u sername to use to log in to the remote file systen.
`password`	`null`	Specifies the password to use to log in to the remote file system.
`account`	`null`	Camel 2.15.2: Specified the account to use to login to the remote FTP server (only for FTP and FTP Secure)
`binary`	`false`	Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (`false).`
`disconnect`	`false`	Camel 2.2: Whether or not to disconnect from remote FTP server right after use. Can be used for both consumer and producer. Disconnect will only disconnect the current connection to the FTP server. If you have a consumer which you want to stop, then you need to stop the consumer/route instead.
`localWorkDirectory`	`null`	When consuming, a local work directory can be used to store the remote file content directly in local files, to avoid loading the content into memory. This is beneficial, if you consume a very big remote fil e and thus can conserve memory. See below for more details.
`passiveMode`	`false`	FTP and FTPS only: Specifies whether to use passive mode connections. Default is active mode (`false`).
`securityProtocol`	`TLS`	FTPS only: Sets the underlying security protocol. The following values are defined: `TLS`: Transport Layer Security `SSL`: Secure Sockets Layer
`disableSecureDataChannelDefaults`	`false`	Camel 2.4: FTPS only: Whether or not to disable using default values for `execPbsz` and `execProt` when using secure data transfer. You can set this option to `true` if you want to be in full control what the options `execPbsz` and `execProt` should be used.
`download`	`true`	Camel 2.11: Whether the FTP consumer should download the file. If this option is set to `false`, then the message body will be `null`, but the consumer will still trigger a Camel Exchange that has details about the file such as file name, file size, etc. It's just that the file will not be downloaded.
streamDownload	false	Camel 2.11: Whether the consumer should download the entire file up front, the default behavior, or if it should pass an InputStream read from the remote resource rather than an in-memory array as the in body of the Camel Exchange. This option is ignored if download is false or is localWorkDirectory is provided. This option is useful for working with large remote files.
`execProt`	`null`	Camel 2.4: FTPS only: Will by default use option `P` if secure data channel defaults hasn't been disabled. Possible values are: `C`: Clear `S`: Safe (SSL protocol only) `E`: Confidential (SSL protocol only) `P`: Private
`execPbsz`	`null`	Camel 2.4: FTPS only: This option specifies the buffer size of the secure data channel. If option `useSecureDataChannel` has been enabled and this option has not been explicit set, then value `0` is used.< /p>
`isImplicit`	`false`	FTPS only: Sets the security mode(implicit/explicit). Default is explicit (`false`).
`knownHostsFile`	`null`	SFTP only: Sets the `known_hosts` file, so that the SFTP endpoint can do host key verification.
`knownHostsUri`	`null`	SFTP only: Camel 2.11.1: Sets the `known_hosts` file (loaded from classpath by default), so that the SFTP endpoint can do host key verification.
`keyPair`	`null`	SFTP only: Camel 2.12.0: Sets the Java KeyPair for SSH public key authentication, it supports DSA or RSA keys.
`privateKeyFile`	`null`	SFTP only: Set the private key file to that the SFTP endpoint can do private key verification.
`privateKeyUri`	`null`	SFTP only: Camel 2.11.1: Set the private key file (loaded from classpath by default) to that the SFTP endpoint can do private key verification.
`privateKey`	`null`	SFTP only: Camel 2.11.1: Set the private key as byte[] to that the SFTP endpoint can do private key verification.
`privateKeyFilePassphrase`	`null`	SFTP only: Deprecated: use `privateKeyPassphrase` instead. Set the private key file passphrase to that the SFTP endpoint can do private key verification.
`privateKeyPassphrase`	`null`	SFTP only: Camel 2.11.1: Set the private key file passphrase to that the SFTP endpoint can do private key verification.
`preferredAuthentications`	`null`	SFTP only: Camel 2.10.7, 2.11.2,2.12.0: set the preferred authentications which SFTP endpoint will used. Some example include:password,publickey. If not specified the default list from JSCH will be used.
`ciphers`	`null`	Camel 2.8.2, 2.9: SFTP only Set a comma separated list of ciphers that will be used in order of preference. Possible cipher names are defined by JCraft JSCH. Some examples include: aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc. If not specified the default list from JSCH will be used.
`fastExistsCheck`	`false`	Camel 2.8.2, 2.9: If set this option to be true, camel-ftp will use the list file directly to check if the file exists . Since some FTP server may not support to list the file directly, if the option is false, camel-ftp will use the old way to list the directory and check if the file exists. Note from Camel 2.10.1 onwards this option also influences `readLock=changed` to control whether it performs a fast check to update file information or not. This can be used to speed up the process if the FTP server has a lot of files.
`strictHostKeyChecking`	`no`	SFTP only: Camel 2.2: Sets whether to use strict host key checking. Possible values are: `no`, `yes` and `ask`. `ask` does not make sense to use as Camel cannot answer the question for you as its meant for human intervention. Note: The default in Camel 2.1 and below was `ask`.
`maximumReconnectAttempts`	`3`	Specifies the maximum reconnect attempts Camel performs when it tries to connect to the remote FTP server. Use 0 to disable this behavior.
`reconnectDelay`	`1000`	Delay in millis Camel will wait before performing a reconnect attempt.
`connectTimeout`	`10000`	C amel 2.4: Is the connect timeout in millis. This corresponds to using `ftpClient.connectTimeout` for the FTP/FTPS. For SFTP this option is also used when attempting to connect.
`soTimeout`	`null / 30000`	FTP and FTPS Only: Camel 2.4: Is the `SocketOptions.SO_TIMEOUT` value in millis. A good idea is to configure this to a value such as 300000 (5 minutes) to not hang a connection. On SFTP this option is set as timeout on the JSCH Session instance. Also SFTP from Camel 2.14.3/2.15.3/2.16 onwards. From Camel 2.16 onwards the default is 30000 (30 sec).
`timeout`	`30000`	FTP and FTPS Only: Camel 2.4: Is the data timeout in millis. This corresponds to using `ftpClient.dataTimeout` for the FTP/FTPS. For SFTP there is no data timeout.
`throwExceptionOnConnectFailed`	`false`	Camel 2.5: Whether or not to thrown an exception if a successful connection and login could not be establish. This allows a custom `pollStrategy` to deal with the exception, for example to stop the consumer or the likes.
`siteCommand`	`null`	FTP and FTPS Only: Camel 2.5: To execute site commands after successful login. Multiple site commands can be separated using a new line character (\n). Use `help site` to see which site commands your FTP server supports.
`stepwise`	`true`	Camel 2.6: Whether or not stepwise traversing directories should be used or not. Stepwise means that it will CD one directory at a time. See more details below. You can disable this in case you can't use this approach.
`separator`	`UNIX`	Camel 2.6: Dictates what path separator char to use when uploading files. `Auto` = Use the path provided without altering it. `UNIX` = Use unix style path separators. `Windows` = Use Windows style path separators. Since Camel 2.15.2: The default value is changed to UNIX style path, before Camel 2.15.2: The default value is `Auto.`
`chmod`	`null`	SFTP Producer Only: Camel 2.9: Allows you to set chmod on the stored file. For example `chmod=640`.
`compression`	0	SFTP Only: Camel 2.8.3/2.9: To use compression. Specify a level from 1 to 10. Important: You must manually add the needed JSCH zlib JAR to the classpath for compression support.
`receiveBufferSize`	`32768`	FTP/FTPS Only: Camel 2.15.1: The buffer size for downloading files. The default size is 32kb.
`ftpClient`	`null`	FTP and FTPS Only: Camel 2.1: Allows you to use a custom `org.apache.commons.net.ftp .FTPClient` instance.
`ftpClientConfig`	`null`	FTP and FTPS Only: Camel 2.1: Allows you to use a custom `org.apache.commons.net.ftp.FTPClientConfig` instance.
`ftpClientConfig.XXX`		FTP and FTPS Only: To configure various options on the FTPClient instance from the uri. For example: `ftpClientConfig.receiveDataSocketBufferSize=8192&ftpClientConfig.sendDataSocketBufferSize=8192`
`serverAliveInterval`	`0`	SFTP Only: Camel 2.8 Allows you to set the serverAliveInterval of the sftp session
`serverAliveCountMax`	`1`	SFTP Only: Camel 2.8 Allows you to set the serverAliveCountMax of the sftp session
`ftpClient.trustStore.file`	`null`	FTPS Only: Sets the trust store file, so that the FTPS client can look up for trusted certificates.
`ftpClient.trustStore.type`	`JKS`	FTPS Only: Sets the trust store type.
`ftpClient.trustStore.algorithm`	`SunX509`	FTPS Only: Sets the trust store algorithm.
`ftpClient.trustStore.password`	`null`	FTPS Only: Sets the trust store password.
`ftpClient.keyStore.file`	`null`	FTPS Only: Sets the key store file, so that the FTPS client can look up for the private certificate.
`ftpClient.keyStore.type`	`JKS`	FTPS Only: Sets the key store type.
`ftpClient.keyStore.algorithm`	`SunX509`	FTPS Only: Sets the key store algorithm.
`ftpClient.keyStore.password`	`null`	FTPS Only: Sets the key store password.
`ftpClient.keyStore.keyPassword`	`null`	FTPS Only: Sets the private key password.
`sslContextParameters`	`null`	FTPS Only: Camel 2.9: Reference to a `org.apache.camel.util.jsse.SSLContextParameters` in the Registry. This reference overrides any configured SSL related o ptions on ftpClient as well as the securityProtocol (SSL, TLS, etc.) set on FtpsConfiguration. See Using the JSSE Configuration Utility.
`proxy`	`null`	SFTP Only: Camel 2.10.7, 2.11.1: Reference to a `com.jcraft.jsch.Proxy` in the Registry. This proxy is used to consume/send messages from the target SFTP host.
`useList`	`true`	FTP/FTPS Only: Camel 2.12.1: Whether the consumer should use FTP LIST command to retrieve directory listing to see which files exists. If this option is set to `false`, then `stepwise=false` must be configured, and also `fileName` must be configured to a fixed name, so the consumer knows the name of the file to retrieve. When doing this only that single file can be retrieved. See further below for more details.
`ignoreFileNotFoundOrPermissionError`	`false`	Camel 2.12.1: Whether the consumer should ignore when a file was attempted to be retrieved but did not exist (for some reason), or failure due insufficient file permission error. Camel 2.14.2: This option now applies to directories as well.
`sendNoop`	`true`	Camel 2.16: Producer only. Whether to send a noop command as a pre-write check before uploading files to the FTP server. This is enabled by default as a validation of the connection is still valid, which allows to silently re-connect to be able to upload the file. However if this causes problems, you can turn this option off.
`jschLoggingLevel`	`WARN`	SFTP Only: Camel 2.15.3/2.16: The logging level to use for JSCH activity logging. As JSCH is verbose at by default at INFO level the threshold is WARN by default.
`bulkRequest`		SFTP Only: Camel 2.17.1: Specifies how many requests may be outstanding at any one time. Increasing this value may slightly improve file transfer speed but will increase memory usage.

You can configure additional options on the ftpClient and ftpClientConfig from the URI directly by using the ftpClient. or ftpClientConfig. prefix.

For example to set the setDataTimeout on the FTPClient to 30 seconds you can do:

You can mix and match and have use both prefixes, for example to configure date format or timezones.

Tutorial on Spring Remoting with JMS

Preface

Writing the Server

Create the Spring Service

See Also

CXF Component

URI Options

`URI Options`