You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2019/06/26 03:33:45 UTC
[camel] 01/07: Components "d..." and "f...".
https://issues.apache.org/jira/browse/CAMEL-13480
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 4f4ba02119d794904858a5252e8f86cd20a44273
Author: Alexandros Koufoudakis <ak...@gmail.com>
AuthorDate: Wed Jun 12 18:51:31 2019 +0200
Components "d..." and "f...". https://issues.apache.org/jira/browse/CAMEL-13480
---
.../src/main/docs/dataformat-component.adoc | 2 +-
.../src/main/docs/dataset-test-component.adoc | 19 ++--------------
.../src/main/docs/digitalocean-component.adoc | 2 +-
.../src/main/docs/direct-component.adoc | 2 +-
.../src/main/docs/direct-vm-component.adoc | 2 +-
.../src/main/docs/disruptor-component.adoc | 2 +-
.../camel-dozer/src/main/docs/dozer-component.adoc | 4 ++--
.../camel-drill/src/main/docs/drill-component.adoc | 2 +-
.../src/main/docs/dropbox-component.adoc | 2 +-
.../src/main/docs/ehcache-component.adoc | 2 +-
.../camel-ejb/src/main/docs/ejb-component.adoc | 2 +-
.../camel-elsql/src/main/docs/elsql-component.adoc | 8 ++++---
.../camel-etcd/src/main/docs/etcd-component.adoc | 2 +-
.../src/main/docs/eventadmin-component.adoc | 5 ++---
.../camel-exec/src/main/docs/exec-component.adoc | 7 +++---
.../src/main/docs/fhirJson-dataformat.adoc | 4 +---
.../src/main/docs/fhirXml-dataformat.adoc | 3 +--
.../camel-file/src/main/docs/file-component.adoc | 20 ++++++++---------
.../src/main/docs/flatpack-component.adoc | 4 ++--
.../camel-fop/src/main/docs/fop-component.adoc | 2 +-
.../src/main/docs/freemarker-component.adoc | 14 ++++++------
.../camel-ftp/src/main/docs/ftp-component.adoc | 26 +++++-----------------
22 files changed, 51 insertions(+), 85 deletions(-)
diff --git a/components/camel-dataformat/src/main/docs/dataformat-component.adoc b/components/camel-dataformat/src/main/docs/dataformat-component.adoc
index b02a2c4..7a2546a 100644
--- a/components/camel-dataformat/src/main/docs/dataformat-component.adoc
+++ b/components/camel-dataformat/src/main/docs/dataformat-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.12*
-The *dataformat:* component allows to use xref:data-format.adoc[Data
+The Dataformat component allows to use link:data-format.html[Data
Format] as a Camel Component.
=== URI format
diff --git a/components/camel-dataset/src/main/docs/dataset-test-component.adoc b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
index f4f66a6..e26f957 100644
--- a/components/camel-dataset/src/main/docs/dataset-test-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
@@ -1,9 +1,7 @@
[[dataset-test-component]]
== DataSet Test Component
-*Available as of Camel version 1.3*
-*Available as of Camel version 1.3*
-
+*Available as of Camel version 1.3*
Testing of distributed and asynchronous processing is
notoriously difficult. The <<mock-component,Mock>>, <<mock-component,Test>>
@@ -26,20 +24,7 @@ This will then set up a properly configured <<mock-component,Mock>>
endpoint, which is only valid if the received messages match the number
of expected messages and their message payloads are equal.
-Maven users will need to add the following dependency to their `pom.xml`
-for this component when using *Camel 2.8* or older:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-spring</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-From Camel 2.9 onwards the <<test-component,Test>> component is provided
+The <<test-component,Test>> component is provided
directly in the camel-core.
=== URI format
diff --git a/components/camel-digitalocean/src/main/docs/digitalocean-component.adoc b/components/camel-digitalocean/src/main/docs/digitalocean-component.adoc
index d04be37..74e3476 100644
--- a/components/camel-digitalocean/src/main/docs/digitalocean-component.adoc
+++ b/components/camel-digitalocean/src/main/docs/digitalocean-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.19*
-The **DigitalOcean** component allows you to manage Droplets and resources within the DigitalOcean cloud with **Camel** by encapsulating https://www.digitalocean.com/community/projects/api-client-in-java[digitalocean-api-java]. All of the functionality that you are familiar with in the DigitalOcean control panel is also available through this Camel component.
+The DigitalOcean component allows you to manage Droplets and resources within the DigitalOcean cloud with **Camel** by encapsulating https://www.digitalocean.com/community/projects/api-client-in-java[digitalocean-api-java]. All of the functionality that you are familiar with in the DigitalOcean control panel is also available through this Camel component.
=== Prerequisites
diff --git a/components/camel-direct/src/main/docs/direct-component.adoc b/components/camel-direct/src/main/docs/direct-component.adoc
index f90cc18..61e4c5d 100644
--- a/components/camel-direct/src/main/docs/direct-component.adoc
+++ b/components/camel-direct/src/main/docs/direct-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 1.0*
-The *direct:* component provides direct, synchronous invocation of any
+The Direct component provides direct, synchronous invocation of any
consumers when a producer sends a message exchange. +
This endpoint can be used to connect existing routes in the *same*
camel context.
diff --git a/components/camel-directvm/src/main/docs/direct-vm-component.adoc b/components/camel-directvm/src/main/docs/direct-vm-component.adoc
index 35e9f1d..37d7838 100644
--- a/components/camel-directvm/src/main/docs/direct-vm-component.adoc
+++ b/components/camel-directvm/src/main/docs/direct-vm-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.10*
-The *direct-vm:* component provides direct, synchronous invocation of
+The Direct-Vm component provides direct, synchronous invocation of
any consumers in the JVM when a producer sends a message exchange. +
This endpoint can be used to connect existing routes in the same camel
context, as well from other camel contexts in the *same* JVM.
diff --git a/components/camel-disruptor/src/main/docs/disruptor-component.adoc b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
index d5cfaba..77fe80f 100644
--- a/components/camel-disruptor/src/main/docs/disruptor-component.adoc
+++ b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.12*
-The *disruptor:* component provides asynchronous
+The Disruptor component provides asynchronous
http://www.eecs.harvard.edu/~mdw/proj/seda/[SEDA] behavior much as the
standard SEDA Component, but utilizes a
https://github.com/LMAX-Exchange/disruptor[Disruptor] instead of a
diff --git a/components/camel-dozer/src/main/docs/dozer-component.adoc b/components/camel-dozer/src/main/docs/dozer-component.adoc
index 136a9cb..b94f5cb 100644
--- a/components/camel-dozer/src/main/docs/dozer-component.adoc
+++ b/components/camel-dozer/src/main/docs/dozer-component.adoc
@@ -3,9 +3,9 @@
*Available as of Camel version 2.15*
-The *dozer:* component provides the ability to map between Java beans
+The Dozer component provides the ability to map between Java beans
using the http://camel.apache.org/dozer-type-conversion.html[Dozer]
-mapping framework since *Camel 2.15.0*. Camel also supports the ability
+mapping framework. Camel also supports the ability
to trigger Dozer mappings
http://camel.apache.org/dozer-type-conversion.html[as a type converter].
The primary differences between using a Dozer endpoint and a Dozer
diff --git a/components/camel-drill/src/main/docs/drill-component.adoc b/components/camel-drill/src/main/docs/drill-component.adoc
index 7f010e4..b684bb2 100644
--- a/components/camel-drill/src/main/docs/drill-component.adoc
+++ b/components/camel-drill/src/main/docs/drill-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.19*
-The *drill:* component gives you the ability to query an https://drill.apache.org/[Apache Drill Cluster]
+The Drill component gives you the ability to querying to https://drill.apache.org/[Apache Drill Cluster]
Drill is an Apache open-source SQL query engine for Big Data exploration. Drill is designed from the ground up to support high-performance analysis on the semi-structured and rapidly evolving data coming from modern Big Data applications, while still providing the familiarity and ecosystem of ANSI SQL, the industry-standard query language
diff --git a/components/camel-dropbox/src/main/docs/dropbox-component.adoc b/components/camel-dropbox/src/main/docs/dropbox-component.adoc
index 08d86e3..eddc5cc 100644
--- a/components/camel-dropbox/src/main/docs/dropbox-component.adoc
+++ b/components/camel-dropbox/src/main/docs/dropbox-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.14*
-The *dropbox:* component allows you to treat
+The Dropbox component allows you to treat
https://www.dropbox.com[Dropbox] remote folders as a producer or
consumer of messages. Using the
http://dropbox.github.io/dropbox-sdk-java/api-docs/v1.7.x/[Dropbox Java
diff --git a/components/camel-ehcache/src/main/docs/ehcache-component.adoc b/components/camel-ehcache/src/main/docs/ehcache-component.adoc
index a2ee17d..f1843e4 100644
--- a/components/camel-ehcache/src/main/docs/ehcache-component.adoc
+++ b/components/camel-ehcache/src/main/docs/ehcache-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.18*
-The *ehcache* component enables you to perform caching operations using
+The Ehcache component enables you to perform caching operations using
Ehcache 3 as the Cache Implementation.
This component supports producer and event based consumer endpoints.
diff --git a/components/camel-ejb/src/main/docs/ejb-component.adoc b/components/camel-ejb/src/main/docs/ejb-component.adoc
index 2990d3b..e04cb90 100644
--- a/components/camel-ejb/src/main/docs/ejb-component.adoc
+++ b/components/camel-ejb/src/main/docs/ejb-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.4*
-The *ejb:* component binds EJBs to Camel message exchanges.
+The EJB component binds EJBs to Camel message exchanges.
Maven users will need to add the following dependency to their `pom.xml`
for this component:
diff --git a/components/camel-elsql/src/main/docs/elsql-component.adoc b/components/camel-elsql/src/main/docs/elsql-component.adoc
index 965c781..22f69fe 100644
--- a/components/camel-elsql/src/main/docs/elsql-component.adoc
+++ b/components/camel-elsql/src/main/docs/elsql-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.16*
-The *elsql:* component is an extension to the existing
+The ELSQL component is an extension to the existing
<<sql-component,SQL Component>> that uses
https://github.com/OpenGamma/ElSql[ElSql] to define the SQL queries.
@@ -40,10 +40,12 @@ The parameters to the SQL queries are named parameters in the elsql
mapping files, and maps to corresponding keys from the Camel message, in
the given precedence:
-1. *Camel 2.16.1:* from message body if <<simple-language,Simple>>
+1. from message body if <<simple-language,Simple>>
expression.
-2. from message body if its a `java.util.Map`3. from message headers
+2. from message body if its a `java.util.Map`
+
+3. from message headers
If a named parameter cannot be resolved, then an exception is thrown.
diff --git a/components/camel-etcd/src/main/docs/etcd-component.adoc b/components/camel-etcd/src/main/docs/etcd-component.adoc
index bece04a..0eded03 100644
--- a/components/camel-etcd/src/main/docs/etcd-component.adoc
+++ b/components/camel-etcd/src/main/docs/etcd-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.18*
-The camel etcd component allows you to work with Etcd, a distributed reliable key-value store.
+The camel Etcd component allows you to work with Etcd, a distributed reliable key-value store.
### URI Format
diff --git a/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc b/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc
index 3f45b07..5dc1ecb 100644
--- a/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc
+++ b/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.6*
-The `eventadmin` component can be used in an OSGi environment to receive
+The Eventadmin component can be used in an OSGi environment to receive
OSGi EventAdmin events and process them.
### Dependencies
@@ -19,8 +19,7 @@ Maven users need to add the following dependency to their `pom.xml`
</dependency>
-------------------------------------------
-where `${camel-version`} must be replaced by the actual version of Camel
-(2.6.0 or higher).
+where `${camel-version`} must be replaced by the actual version of Camel.
### URI format
diff --git a/components/camel-exec/src/main/docs/exec-component.adoc b/components/camel-exec/src/main/docs/exec-component.adoc
index fb7841a..4b4da69 100644
--- a/components/camel-exec/src/main/docs/exec-component.adoc
+++ b/components/camel-exec/src/main/docs/exec-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.3*
-The `exec` component can be used to execute system commands.
+The Exec component can be used to execute system commands.
### Dependencies
@@ -18,8 +18,7 @@ Maven users need to add the following dependency to their `pom.xml`
</dependency>
-------------------------------------
-where `${camel-version`} must be replaced by the actual version of Camel
-(2.3.0 or higher).
+where `${camel-version`} must be replaced by the actual version of Camel.
### URI format
@@ -130,7 +129,7 @@ The supported headers are defined in
are used literally - no quoting is applied. Overrides any existing
`args` in the URI.
-|`ExecBinding.EXEC_COMMAND_ARGS` |`String`| `in` |*Camel 2.5:* The arguments of the executable as a Single string where
+|`ExecBinding.EXEC_COMMAND_ARGS` |`String`| `in` |The arguments of the executable as a Single string where
each argument is whitespace separated (see `args` in URI option). The
arguments are used literally, no quoting is applied. Overrides any
existing `args` in the URI.
diff --git a/components/camel-fhir/camel-fhir-component/src/main/docs/fhirJson-dataformat.adoc b/components/camel-fhir/camel-fhir-component/src/main/docs/fhirJson-dataformat.adoc
index fe8d099..7dc3019 100644
--- a/components/camel-fhir/camel-fhir-component/src/main/docs/fhirJson-dataformat.adoc
+++ b/components/camel-fhir/camel-fhir-component/src/main/docs/fhirJson-dataformat.adoc
@@ -1,9 +1,7 @@
[[fhirJson-dataformat]]
== FHIR JSon DataFormat
-*Available as of Camel version 2.21*
-*Available as of Camel version 2.21*
-
+*Available as of Camel version 2.21*
The FHIR-JSON Data Format leverages
link:https://github.com/jamesagnew/hapi-fhir/blob/master/hapi-fhir-base/src/main/java/ca/uhn/fhir/parser/JsonParser.java[HAPI-FHIR's]
diff --git a/components/camel-fhir/camel-fhir-component/src/main/docs/fhirXml-dataformat.adoc b/components/camel-fhir/camel-fhir-component/src/main/docs/fhirXml-dataformat.adoc
index f54a874..ff182ce 100644
--- a/components/camel-fhir/camel-fhir-component/src/main/docs/fhirXml-dataformat.adoc
+++ b/components/camel-fhir/camel-fhir-component/src/main/docs/fhirXml-dataformat.adoc
@@ -1,8 +1,7 @@
[[fhirXml-dataformat]]
== FHIR XML DataFormat
-*Available as of Camel version 2.21*
-*Available as of Camel version 2.21*
+*Available as of Camel version 2.21*
The FHIR-XML Data Format leverages
link:https://github.com/jamesagnew/hapi-fhir/blob/master/hapi-fhir-base/src/main/java/ca/uhn/fhir/parser/XmlParser.java[HAPI-FHIR's]
diff --git a/components/camel-file/src/main/docs/file-component.adoc b/components/camel-file/src/main/docs/file-component.adoc
index a314efd..b6406bb 100644
--- a/components/camel-file/src/main/docs/file-component.adoc
+++ b/components/camel-file/src/main/docs/file-component.adoc
@@ -332,7 +332,7 @@ unique ID.
written. This header is set by Camel and its purpose is providing
end-users with the name of the file that was written.
-|`CamelOverruleFileName` |*Camel 2.11:* Is used for overruling `CamelFileName` header and use the
+|`CamelOverruleFileName` |Is used for overruling `CamelFileName` header and use the
value instead (but only once, as the producer will remove this header
after writing the file). The value can be only be a String. Notice that
if the option `fileName` has been configured, then this is still being
@@ -368,8 +368,7 @@ relative filename. For absolute files this is the absolute path.
|`CamelFileLength` |A `long` value containing the file size.
-|`CamelFileLastModified` |A `Long` value containing the last modified timestamp of the file. In
-*Camel 2.10.3 and older* the type is `Date`.
+|`CamelFileLastModified` |A `Long` value containing the last modified timestamp of the file.
|===
=== Batch Consumer
@@ -567,8 +566,8 @@ from("file:bar?doneFileName=done");
Will only consume files from the bar folder, if a done _file_ exists in
the same directory as the target files. Camel will automatically delete
-the _done file_ when it's done consuming the files. From Camel *2.9.3*
-onwards Camel will not automatically delete the _done file_ if
+the _done file_ when it's done consuming the files.
+Camel does not delete automatically the _done file_ if
`noop=true` is configured.
However it is more common to have one _done file_ per target file. This
@@ -829,7 +828,7 @@ from("file://inbox?idempotent=true").to("...");
----
Camel uses the absolute file name as the idempotent key, to detect
-duplicate files. From *Camel 2.11* onwards you can customize this key by
+duplicate files. You can customize this key by
using an expression in the idempotentKey option. For example to use both
the name and the file size as the key
@@ -972,8 +971,7 @@ The file paths is matched with the following rules:
* `*` matches zero or more characters
* `**` matches zero or more directories in a path
-TIP: *New options from Camel 2.10 onwards*
-There are now `antInclude` and `antExclude` options to make it easy to
+The `antInclude` and `antExclude` options make it easy to
specify ANT style include/exclude without having to define the filter.
See the URI options above for more information.
@@ -1112,7 +1110,7 @@ this as:
* In the `begin()` method we can test whether the special _ready_ file
exists. The begin method returns a `boolean` to indicate if we can
consume the file or not.
-* In the `abort()` method (Camel 2.10) special logic can be executed in
+* In the `abort()` method special logic can be executed in
case the `begin` operation returned `false`, for example to cleanup
resources etc.
* in the `commit()` method we can move the actual file and also delete
@@ -1123,8 +1121,8 @@ the _ready_ file.
The `filter` option allows you to implement a custom filter in Java code
by implementing the `org.apache.camel.component.file.GenericFileFilter`
interface. This interface has an `accept` method that returns a boolean.
-Return `true` to include the file, and `false` to skip the file. From
-Camel 2.10 onwards, there is a `isDirectory` method on `GenericFile`
+Return `true` to include the file, and `false` to skip the file.
+There is a `isDirectory` method on `GenericFile`
whether the file is a directory. This allows you to filter unwanted
directories, to avoid traversing down unwanted directories.
diff --git a/components/camel-flatpack/src/main/docs/flatpack-component.adoc b/components/camel-flatpack/src/main/docs/flatpack-component.adoc
index 0aac34d..b7cb0d8 100644
--- a/components/camel-flatpack/src/main/docs/flatpack-component.adoc
+++ b/components/camel-flatpack/src/main/docs/flatpack-component.adoc
@@ -293,10 +293,10 @@ headers).
|`parserFactory` |`null` |Uses the default Flatpack parser factory.
-|`allowShortLines` |`false` |*Camel 2.9.7 and 2.10.5 onwards*: Allows for lines to be shorter than
+|`allowShortLines` |`false` |Allows for lines to be shorter than
expected and ignores the extra characters.
-|`ignoreExtraColumns` |`false` |*Camel 2.9.7 and 2.10.5 onwards*: Allows for lines to be longer than
+|`ignoreExtraColumns` |`false` |Allows for lines to be longer than
expected and ignores the extra characters.
|=======================================================================
diff --git a/components/camel-fop/src/main/docs/fop-component.adoc b/components/camel-fop/src/main/docs/fop-component.adoc
index 8528853..7cdf9b2 100644
--- a/components/camel-fop/src/main/docs/fop-component.adoc
+++ b/components/camel-fop/src/main/docs/fop-component.adoc
@@ -142,7 +142,7 @@ The component supports 3 options, which are listed below.
The location of a configuration file with the following
http://xmlgraphics.apache.org/fop/1.0/configuration.html[structure].
-From *Camel 2.12* onwards the file is loaded from the classpath by
+The file is loaded from the classpath by
default. You can use `file:`, or `classpath:` as prefix to load the
resource from file or classpath. In previous releases the file is always
loaded from file system.
diff --git a/components/camel-freemarker/src/main/docs/freemarker-component.adoc b/components/camel-freemarker/src/main/docs/freemarker-component.adoc
index 90c8dc4..63437a5 100644
--- a/components/camel-freemarker/src/main/docs/freemarker-component.adoc
+++ b/components/camel-freemarker/src/main/docs/freemarker-component.adoc
@@ -163,7 +163,7 @@ a `Map`). The `Exchange` is transferred as:
|`response` |The Out message (only for InOut message exchange pattern).
|=======================================================================
-From Camel 2.14, you can setup your custom FreeMarker context in the
+You can setup your custom FreeMarker context in the
message header with the key "*CamelFreemarkerDataModel*" just like this
[source,java]
@@ -189,16 +189,16 @@ location for a template or the template content itself. If any of these
headers is set then Camel uses this over the endpoint configured
resource. This allows you to provide a dynamic template at runtime.
-[width="100%",cols="10%,10%,10%,70%",options="header",]
+[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
-|Header |Type |Description |Support Version
+|Header |Type |Description
-|FreemarkerConstants.FREEMARKER_RESOURCE |org.springframework.core.io.Resource |The template resource | <= 2.1
+|FreemarkerConstants.FREEMARKER_RESOURCE |org.springframework.core.io.Resource |The template resource.
|FreemarkerConstants.FREEMARKER_RESOURCE_URI |String |A URI for the template resource to use instead of the endpoint
-configured. | >= 2.1
+configured.
-|FreemarkerConstants.FREEMARKER_TEMPLATE |String |The template to use instead of the endpoint configured. | >= 2.1
+|FreemarkerConstants.FREEMARKER_TEMPLATE |String |The template to use instead of the endpoint configured.
|=======================================================================
### Samples
@@ -243,7 +243,7 @@ from("activemq:My.Queue").
to("activemq:Another.Queue");
---------------------------------------------------------------------
-In *Camel 2.1* it's possible to specify what template the component
+It's possible to specify what template the component
should use dynamically via a header, so for example:
[source,java]
diff --git a/components/camel-ftp/src/main/docs/ftp-component.adoc b/components/camel-ftp/src/main/docs/ftp-component.adoc
index 97a8253..ccc1aff 100644
--- a/components/camel-ftp/src/main/docs/ftp-component.adoc
+++ b/components/camel-ftp/src/main/docs/ftp-component.adoc
@@ -9,7 +9,7 @@ SFTP protocols.
When consuming from remote FTP server make sure you read the section titled _Default when consuming files_
further below for details related to consuming files.
-Absolute path is *not* supported. *Camel 2.16* will translate absolute path to relative by trimming all
+Absolute path is *not* supported. Camel translates absolute path to relative by trimming all
leading slashes from `directoryname`. There'll be WARN message printed
in the logs.
@@ -40,13 +40,7 @@ Where *directoryname* represents the underlying directory. The directory
name is a relative path. Absolute path's is *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
+The `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`.
@@ -63,7 +57,6 @@ This component uses two different libraries for the actual FTP work. FTP
and FTPS uses http://commons.apache.org/net/[Apache Commons Net] while
SFTP uses http://www.jcraft.com/jsch/[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.
@@ -409,9 +402,9 @@ In addition the FTP/FTPS consumer and producer will enrich the Camel
|=======================================================================
|Header |Description
-|`CamelFtpReplyCode` |*Camel 2.11.1:* The FTP client reply code (the type is a integer)
+|`CamelFtpReplyCode` |The FTP client reply code (the type is a integer)
-|`CamelFtpReplyString` | *Camel 2.11.1:* The FTP client reply string
+|`CamelFtpReplyString` |The FTP client reply string
|=======================================================================
=== About timeouts
@@ -465,16 +458,9 @@ producing files (eg uploading)
You may want to pick either one depending on your situation and security
issues. Some Camel end users can only download files if they use
-stepwise, while others can only download if they do not. At least you
-have the choice to pick (from Camel 2.6 onwards).
-
-In Camel 2.0 - 2.5 there is only one mode and it is:
-
-* before 2.5 not stepwise
-* 2.5 stepwise
+stepwise, while others can only download if they do not.
-From Camel 2.6 onwards there is now an option `stepwise` you can use to
-control the behavior.
+You can use the `stepwise` option to control the behavior.
Note that stepwise changing of directory will in most cases only work
when the user is confined to it's home directory and when the home