This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch feature/CAMEL-23789-wave2-multi-dsl-docs in repository https://gitbox.apache.org/repos/asf/camel.git
commit 4d38d91923e2a0fc44cee8528104320dd29d36ba Author: Claus Ibsen <[email protected]> AuthorDate: Thu Jun 18 12:00:54 2026 +0200 CAMEL-23789: Add multi-DSL tabs to mina-sftp docs (Wave 2) Co-Authored-By: Claude <[email protected]> Signed-off-by: Claus Ibsen <[email protected]> --- .../src/main/docs/mina-sftp-component.adoc | 754 ++++++++++++++++++++- 1 file changed, 753 insertions(+), 1 deletion(-) diff --git a/components/camel-mina-sftp/src/main/docs/mina-sftp-component.adoc b/components/camel-mina-sftp/src/main/docs/mina-sftp-component.adoc index 33e4590c6dec..f55c813405a7 100644 --- a/components/camel-mina-sftp/src/main/docs/mina-sftp-component.adoc +++ b/components/camel-mina-sftp/src/main/docs/mina-sftp-component.adoc @@ -342,12 +342,43 @@ This behavior matches the JSch-based sftp component. You can customize the authentication order using the `preferredAuthentications` option: +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?password=secret&privateKeyFile=/path/to/key&preferredAuthentications=password,publickey";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?password=secret&privateKeyFile=/path/to/key&preferredAuthentications=password,publickey"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + privateKeyFile: /path/to/key + preferredAuthentications: "password,publickey" + steps: + - to: + uri: file:local +---- +==== + ==== Available Authentication Methods [cols="2,4"] @@ -370,12 +401,42 @@ If `preferredAuthentications` is not specified, the default order from Apache MI You can restrict which public key algorithms are accepted for authentication using the `publicKeyAcceptedAlgorithms` option: +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?privateKeyFile=/path/to/key&publicKeyAcceptedAlgorithms=ssh-ed25519,rsa-sha2-256,rsa-sha2-512";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?privateKeyFile=/path/to/key&publicKeyAcceptedAlgorithms=ssh-ed25519,rsa-sha2-256,rsa-sha2-512"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + privateKeyFile: /path/to/key + publicKeyAcceptedAlgorithms: "ssh-ed25519,rsa-sha2-256,rsa-sha2-512" + steps: + - to: + uri: file:local +---- +==== + ==== Available Public Key Algorithms [cols="2,4"] @@ -411,12 +472,42 @@ from("mina-sftp://user@host/path?privateKeyFile=/path/to/key&publicKeyAcceptedAl For security-conscious deployments, restrict to modern algorithms only: +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?privateKeyFile=/path/to/key&publicKeyAcceptedAlgorithms=ssh-ed25519,rsa-sha2-256,rsa-sha2-512,ecdsa-sha2-nistp256";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?privateKeyFile=/path/to/key&publicKeyAcceptedAlgorithms=ssh-ed25519,rsa-sha2-256,rsa-sha2-512,ecdsa-sha2-nistp256"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + privateKeyFile: /path/to/key + publicKeyAcceptedAlgorithms: "ssh-ed25519,rsa-sha2-256,rsa-sha2-512,ecdsa-sha2-nistp256" + steps: + - to: + uri: file:local +---- +==== + If `publicKeyAcceptedAlgorithms` is not specified, the default list from Apache MINA SSHD is used. === Supported Key Formats @@ -934,12 +1025,43 @@ When migrating from `sftp` to `mina-sftp`, verify the following: === Connection Retry +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?password=secret&maximumReconnectAttempts=5&reconnectDelay=2000";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?password=secret&maximumReconnectAttempts=5&reconnectDelay=2000"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + maximumReconnectAttempts: 5 + reconnectDelay: 2000 + steps: + - to: + uri: file:local +---- +==== + === Error Messages The component provides clear error messages for common failure scenarios: @@ -976,12 +1098,42 @@ The mina-sftp component supports SSH data compression to reduce bandwidth usage To enable compression, set the `compression` option to a value between 1 and 10: +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?password=secret&compression=5";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?password=secret&compression=5"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + compression: 5 + steps: + - to: + uri: file:local +---- +==== + The compression level is advisory; the actual compression behavior depends on the SSH library's implementation. When compression is enabled, the component configures the following algorithms in order of preference: 1. `[email protected]` (OpenSSH delayed compression - preferred for security) @@ -1035,12 +1187,42 @@ The mina-sftp component allows you to specify which SSH cipher algorithms to use To specify a custom list of ciphers, use the `ciphers` option with a comma-separated list of cipher names: +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?password=secret&ciphers=aes256-ctr,[email protected]";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?password=secret&ciphers=aes256-ctr,[email protected]"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + ciphers: "aes256-ctr,[email protected]" + steps: + - to: + uri: file:local +---- +==== + Ciphers are offered to the server in the order specified. The first mutually supported cipher will be used. === Available Ciphers @@ -1111,6 +1293,10 @@ The following ciphers are supported by Apache MINA SSHD: For security-hardened environments, use only modern authenticated encryption modes: +[tabs] +==== +Java:: ++ [source,java] ---- // Recommended secure configuration @@ -1118,6 +1304,34 @@ from("mina-sftp://user@host/path?password=secret&[email protected], .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<!-- Recommended secure configuration --> +<route> + <from uri="mina-sftp://user@host/path?password=secret&[email protected],[email protected],aes256-ctr"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +# Recommended secure configuration +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + ciphers: "[email protected],[email protected],aes256-ctr" + steps: + - to: + uri: file:local +---- +==== + === Default Cipher Behavior If `ciphers` is not specified, Apache MINA SSHD's default cipher list is used, which includes a secure selection of modern algorithms. @@ -1132,12 +1346,42 @@ The mina-sftp component allows you to specify which SSH key exchange algorithms To specify a custom list of key exchange protocols, use the `keyExchangeProtocols` option with a comma-separated list: +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?password=secret&keyExchangeProtocols=curve25519-sha256,ecdh-sha2-nistp256";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?password=secret&keyExchangeProtocols=curve25519-sha256,ecdh-sha2-nistp256"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + keyExchangeProtocols: "curve25519-sha256,ecdh-sha2-nistp256" + steps: + - to: + uri: file:local +---- +==== + Key exchange protocols are offered to the server in the order specified. The first mutually supported algorithm will be used. === Available Key Exchange Protocols @@ -1221,12 +1465,42 @@ The mina-sftp component allows you to specify which server host key algorithms a To specify a custom list of server host key algorithms, use the `serverHostKeys` option with a comma-separated list: +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?password=secret&serverHostKeys=ssh-ed25519,rsa-sha2-512";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?password=secret&serverHostKeys=ssh-ed25519,rsa-sha2-512"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + serverHostKeys: "ssh-ed25519,rsa-sha2-512" + steps: + - to: + uri: file:local +---- +==== + Server host key algorithms are offered to the server in the order specified. The first mutually supported algorithm will be used for server authentication. === Available Server Host Key Algorithms @@ -1391,6 +1665,10 @@ NOTE: Under the hood, these settings are mapped to Apache MINA SSHD's `CoreModul For routes with long idle periods between file transfers, configure keep-alive to prevent firewalls or servers from terminating the connection: +[tabs] +==== +Java:: ++ [source,java] ---- // Send keep-alive every 30 seconds @@ -1398,10 +1676,42 @@ from("mina-sftp://user@host/path?password=secret&serverAliveInterval=30000";) .to("file:local"); ---- -=== Detecting Unresponsive Servers +XML:: ++ +[source,xml] +---- +<!-- Send keep-alive every 30 seconds --> +<route> + <from uri="mina-sftp://user@host/path?password=secret&serverAliveInterval=30000"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +# Send keep-alive every 30 seconds +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + serverAliveInterval: 30000 + steps: + - to: + uri: file:local +---- +==== + +=== Detecting Unresponsive Servers Configure `serverAliveCountMax` to control how quickly the component detects an unresponsive server: +[tabs] +==== +Java:: ++ [source,java] ---- // Terminate connection after 3 unanswered keep-alives (90 seconds max) @@ -1409,6 +1719,35 @@ from("mina-sftp://user@host/path?password=secret&serverAliveInterval=30000&serve .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<!-- Terminate connection after 3 unanswered keep-alives (90 seconds max) --> +<route> + <from uri="mina-sftp://user@host/path?password=secret&serverAliveInterval=30000&serverAliveCountMax=3"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +# Terminate connection after 3 unanswered keep-alives (90 seconds max) +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + serverAliveInterval: 30000 + serverAliveCountMax: 3 + steps: + - to: + uri: file:local +---- +==== + With this configuration: * Keep-alive messages are sent every 30 seconds @@ -1462,12 +1801,42 @@ The MINA SFTP component supports comprehensive host key verification to protect When `strictHostKeyChecking=yes`, the server's host key must match an entry in the known hosts source. If the key is unknown or mismatches, the connection is rejected. +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?password=secret&strictHostKeyChecking=yes";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?password=secret&strictHostKeyChecking=yes"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + strictHostKeyChecking: "yes" + steps: + - to: + uri: file:local +---- +==== + === Known Hosts Sources (Priority Order) The component checks for known hosts in this priority order: @@ -1479,50 +1848,204 @@ The component checks for known hosts in this priority order: ==== Using Custom Known Hosts File +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?password=secret&strictHostKeyChecking=yes&knownHostsFile=/path/to/known_hosts";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?password=secret&strictHostKeyChecking=yes&knownHostsFile=/path/to/known_hosts"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + strictHostKeyChecking: "yes" + knownHostsFile: /path/to/known_hosts + steps: + - to: + uri: file:local +---- +==== + ==== Using Known Hosts from Classpath +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?password=secret&strictHostKeyChecking=yes&knownHostsUri=classpath:ssh/known_hosts";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?password=secret&strictHostKeyChecking=yes&knownHostsUri=classpath:ssh/known_hosts"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + strictHostKeyChecking: "yes" + knownHostsUri: "classpath:ssh/known_hosts" + steps: + - to: + uri: file:local +---- +==== + ==== Using User's Default Known Hosts By default, `useUserKnownHostsFile=true` which uses `~/.ssh/known_hosts`: +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?password=secret&strictHostKeyChecking=yes";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?password=secret&strictHostKeyChecking=yes"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + strictHostKeyChecking: "yes" + steps: + - to: + uri: file:local +---- +==== + === Auto-Create Known Hosts File (Development Only) For development environments, you can enable automatic trust-on-first-use: +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?password=secret&autoCreateKnownHostsFile=true&knownHostsFile=/tmp/dev_known_hosts";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?password=secret&autoCreateKnownHostsFile=true&knownHostsFile=/tmp/dev_known_hosts"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + autoCreateKnownHostsFile: true + knownHostsFile: /tmp/dev_known_hosts + steps: + - to: + uri: file:local +---- +==== + CAUTION: Auto-create is only recommended for development environments. It weakens security by automatically trusting new hosts. === Disable Host Key Checking (Testing Only) +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@localhost/test?password=secret&strictHostKeyChecking=no&useUserKnownHostsFile=false";) .to("mock:result"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@localhost/test?password=secret&strictHostKeyChecking=no&useUserKnownHostsFile=false"/> + <to uri="mock:result"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@localhost/test + parameters: + password: secret + strictHostKeyChecking: "no" + useUserKnownHostsFile: false + steps: + - to: + uri: mock:result +---- +==== + CAUTION: Disabling host key checking is insecure and should only be used for testing. === Certificate-Based Host Verification @@ -1544,12 +2067,43 @@ The standard OpenSSH known_hosts format supports `@cert-authority` entries that ==== Example Configuration +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://[email protected]/path?password=secret&strictHostKeyChecking=yes&knownHostsFile=/path/to/known_hosts";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://[email protected]/path?password=secret&strictHostKeyChecking=yes&knownHostsFile=/path/to/known_hosts"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://[email protected]/path + parameters: + password: secret + strictHostKeyChecking: "yes" + knownHostsFile: /path/to/known_hosts + steps: + - to: + uri: file:local +---- +==== + Where the known_hosts file contains: [source] ---- @@ -1666,12 +2220,42 @@ In multi-homed environments (servers with multiple network interfaces), you may Use the `bindAddress` option to specify the local IP address or hostname to bind the outgoing connection: +[tabs] +==== +Java:: ++ [source,java] ---- from("mina-sftp://user@host/path?password=secret&bindAddress=192.168.1.100";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<route> + <from uri="mina-sftp://user@host/path?password=secret&bindAddress=192.168.1.100"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + bindAddress: "192.168.1.100" + steps: + - to: + uri: file:local +---- +==== + === Bind Address Formats The mina-sftp component supports multiple formats for `bindAddress`: @@ -1771,6 +2355,7 @@ The mina-sftp component's `bindAddress` parameter has an enhanced format compare If you are migrating from the `sftp` component to `mina-sftp`, your existing `bindAddress` configurations will work without changes. The port specification is an optional enhancement. +._Java-only: bindAddress configuration values_ [source,java] ---- // Works in both sftp and mina-sftp @@ -1788,6 +2373,10 @@ The mina-sftp component allows you to configure buffer sizes for SFTP read and w Use `readBufferSize` and `writeBufferSize` to control the buffer allocation for SFTP transfers: +[tabs] +==== +Java:: ++ [source,java] ---- // Configure 64KB read buffer and 32KB write buffer @@ -1799,6 +2388,53 @@ from("mina-sftp://user@host/path?password=secret&readBufferSize=65536&writeBuffe .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<!-- Configure 64KB read buffer and 32KB write buffer --> +<route> + <from uri="mina-sftp://user@host/path?password=secret&readBufferSize=65536&writeBufferSize=32768"/> + <to uri="file:local"/> +</route> + +<!-- Configure symmetric buffer sizes for balanced transfers --> +<route> + <from uri="mina-sftp://user@host/path?password=secret&readBufferSize=65536&writeBufferSize=65536"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +# Configure 64KB read buffer and 32KB write buffer +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + readBufferSize: 65536 + writeBufferSize: 32768 + steps: + - to: + uri: file:local + +# Configure symmetric buffer sizes for balanced transfers +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + readBufferSize: 65536 + writeBufferSize: 65536 + steps: + - to: + uri: file:local +---- +==== + === Buffer Size Options [cols="2,1,3"] @@ -2070,6 +2706,10 @@ The mina-sftp component supports reading and writing through symbolic links on S When consuming files, the consumer follows symbolic links to their target files: +[tabs] +==== +Java:: ++ [source,java] ---- // Will consume files through symlinks @@ -2077,10 +2717,41 @@ from("mina-sftp://user@host/data?password=secret";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<!-- Will consume files through symlinks --> +<route> + <from uri="mina-sftp://user@host/data?password=secret"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +# Will consume files through symlinks +- route: + from: + uri: mina-sftp://user@host/data + parameters: + password: secret + steps: + - to: + uri: file:local +---- +==== + === Producer Behavior When producing files, you can write to paths that are symbolic links. The file will be written to the symlink's target: +[tabs] +==== +Java:: ++ [source,java] ---- // Can write to symlink targets @@ -2088,6 +2759,33 @@ from("file:local") .to("mina-sftp://user@host/upload-link?password=secret";); ---- +XML:: ++ +[source,xml] +---- +<!-- Can write to symlink targets --> +<route> + <from uri="file:local"/> + <to uri="mina-sftp://user@host/upload-link?password=secret"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +# Can write to symlink targets +- route: + from: + uri: file:local + steps: + - to: + uri: mina-sftp://user@host/upload-link + parameters: + password: secret +---- +==== + === Symlink Limitations NOTE: **Absolute symlinks in chroot environments**: If the SFTP server uses a chroot jail (common with OpenSSH `ChrootDirectory`), absolute symlinks may not resolve correctly because the absolute path gets prepended with the chroot directory. Use **relative symlinks** for maximum compatibility in chroot environments. @@ -2198,6 +2896,10 @@ By default, MINA SSHD uses UTF-8 encoding for filenames, which is the standard f Use the `filenameEncoding` option to specify the charset: +[tabs] +==== +Java:: ++ [source,java] ---- // Connect to a legacy server using GBK encoding for Chinese filenames @@ -2209,6 +2911,51 @@ from("mina-sftp://user@host/path?password=secret&filenameEncoding=Shift-JIS";) .to("file:local"); ---- +XML:: ++ +[source,xml] +---- +<!-- Connect to a legacy server using GBK encoding for Chinese filenames --> +<route> + <from uri="mina-sftp://user@host/path?password=secret&filenameEncoding=GBK"/> + <to uri="file:local"/> +</route> + +<!-- Connect to a Japanese server --> +<route> + <from uri="mina-sftp://user@host/path?password=secret&filenameEncoding=Shift-JIS"/> + <to uri="file:local"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +# Connect to a legacy server using GBK encoding for Chinese filenames +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + filenameEncoding: GBK + steps: + - to: + uri: file:local + +# Connect to a Japanese server +- route: + from: + uri: mina-sftp://user@host/path + parameters: + password: secret + filenameEncoding: Shift-JIS + steps: + - to: + uri: file:local +---- +==== + === Default Behavior When `filenameEncoding` is not specified, UTF-8 is used (the MINA SSHD default). This is correct for most modern SFTP servers. @@ -2253,6 +3000,7 @@ WARN The 'jschLoggingLevel' parameter is specific to the JSch-based sftp compon === Migration Example +._Java-only: before and after migration from JSch-specific parameters_ [source,java] ---- // Before (sftp component with JSch-specific parameters) @@ -2403,6 +3151,8 @@ If you are migrating from the `sftp` component and were using `loggingLevel` or 4. The standard SLF4J approach provides more flexibility and follows Java logging best practices .Before (JSch sftp component) + +._Java-only: JSch sftp component with logging parameters_ [source,java] ---- from("sftp://user@host/path?password=secret&loggingLevel=DEBUG&serverMessageLoggingLevel=INFO";) @@ -2410,6 +3160,8 @@ from("sftp://user@host/path?password=secret&loggingLevel=DEBUG&serverMessageLogg ---- .After (MINA SSHD mina-sftp component) + +._Java-only: mina-sftp component with logging parameters removed_ [source,java] ---- // Remove logging parameters from URI
