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/11/18 12:16:54 UTC
[camel] branch master updated: Doc update to use Since instead of
Available as of
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
The following commit(s) were added to refs/heads/master by this push:
new c851dd0 Doc update to use Since instead of Available as of
c851dd0 is described below
commit c851dd0405cd9d99d2a119464a86cd49e23f5524
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Mon Nov 18 13:16:29 2019 +0100
Doc update to use Since instead of Available as of
---
.../camel-aws-xray/src/main/docs/aws-xray.adoc | 2 +-
.../src/main/docs/cometd-component.adoc | 2 +-
.../src/main/docs/controlbus-component.adoc | 2 +-
.../camel-csv/src/main/docs/csv-dataformat.adoc | 6 ++---
.../camel-cxf/src/main/docs/cxfrs-component.adoc | 2 +-
.../camel-elsql/src/main/docs/elsql-component.adoc | 2 +-
.../camel-file/src/main/docs/file-component.adoc | 6 ++---
.../src/main/docs/groovy-language.adoc | 8 +++----
.../camel-irc/src/main/docs/irc-component.adoc | 2 +-
components/camel-jasypt/src/main/docs/jasypt.adoc | 2 +-
.../camel-jaxb/src/main/docs/jaxb-dataformat.adoc | 8 +++----
.../camel-jdbc/src/main/docs/jdbc-component.adoc | 4 ++--
.../camel-jms/src/main/docs/jms-component.adoc | 4 ++--
.../src/main/docs/jsonpath-language.adoc | 8 +++----
.../camel-jt400/src/main/docs/jt400-component.adoc | 2 +-
.../camel-kafka/src/main/docs/kafka-component.adoc | 4 ++--
components/camel-kura/src/main/docs/kura.adoc | 2 +-
.../src/main/docs/language-component.adoc | 2 +-
.../camel-leveldb/src/main/docs/leveldb.adoc | 2 +-
.../camel-log/src/main/docs/log-component.adoc | 4 ++--
.../camel-mail/src/main/docs/mail-component.adoc | 2 +-
.../src/main/docs/metrics-component.adoc | 4 ++--
.../src/main/docs/microprofile-config.adoc | 2 +-
.../src/main/docs/microprofile-health.adoc | 2 +-
.../src/main/docs/mongodb-component.adoc | 2 +-
.../camel-mvel/src/main/docs/mvel-language.adoc | 2 +-
.../src/main/docs/mybatis-component.adoc | 6 ++---
.../camel-ognl/src/main/docs/ognl-language.adoc | 2 +-
.../camel-openstack/src/main/docs/openstack.adoc | 2 +-
.../src/main/docs/opentracing.adoc | 2 +-
.../src/main/docs/reactive-executor-vertx.adoc | 2 +-
.../camel-seda/src/main/docs/seda-component.adoc | 4 ++--
components/camel-shiro/src/main/docs/shiro.adoc | 2 +-
.../src/main/docs/soapjaxb-dataformat.adoc | 4 ++--
.../src/main/docs/spring-boot.adoc | 4 ++--
.../src/main/docs/spring-cloud-consul.adoc | 2 +-
.../src/main/docs/spring-cloud-netflix.adoc | 4 ++--
.../src/main/docs/spring-cloud-zookeeper.adoc | 2 +-
.../src/main/docs/spring-cloud.adoc | 4 ++--
.../src/main/docs/spring-security.adoc | 2 +-
.../src/main/docs/spring-ws-component.adoc | 2 +-
.../camel-spring/src/main/docs/spel-language.adoc | 2 +-
.../camel-sql/src/main/docs/sql-component.adoc | 16 ++++++-------
.../src/main/docs/swagger-java.adoc | 6 ++---
.../src/main/docs/syslog-dataformat.adoc | 2 +-
.../src/main/docs/test-blueprint.adoc | 2 +-
.../camel-timer/src/main/docs/timer-component.adoc | 4 ++--
.../src/main/docs/velocity-component.adoc | 2 +-
.../src/main/docs/secureXML-dataformat.adoc | 2 +-
.../src/main/docs/xmlsecurity-component.adoc | 2 +-
.../camel-xpath/src/main/docs/xpath-language.adoc | 16 ++++++-------
components/camel-zipkin/src/main/docs/zipkin.adoc | 2 +-
docs/components/modules/ROOT/pages/aws-xray.adoc | 2 +-
.../modules/ROOT/pages/cometd-component.adoc | 2 +-
.../modules/ROOT/pages/controlbus-component.adoc | 2 +-
.../modules/ROOT/pages/csv-dataformat.adoc | 6 ++---
.../modules/ROOT/pages/cxfrs-component.adoc | 2 +-
.../modules/ROOT/pages/elsql-component.adoc | 2 +-
.../modules/ROOT/pages/file-component.adoc | 6 ++---
.../modules/ROOT/pages/groovy-language.adoc | 8 +++----
.../modules/ROOT/pages/irc-component.adoc | 2 +-
docs/components/modules/ROOT/pages/jasypt.adoc | 2 +-
.../modules/ROOT/pages/jaxb-dataformat.adoc | 8 +++----
.../modules/ROOT/pages/jdbc-component.adoc | 4 ++--
.../modules/ROOT/pages/jms-component.adoc | 4 ++--
.../modules/ROOT/pages/jsonpath-language.adoc | 8 +++----
.../modules/ROOT/pages/jt400-component.adoc | 2 +-
.../modules/ROOT/pages/kafka-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/kura.adoc | 2 +-
.../modules/ROOT/pages/language-component.adoc | 2 +-
docs/components/modules/ROOT/pages/leveldb.adoc | 2 +-
.../modules/ROOT/pages/log-component.adoc | 4 ++--
.../modules/ROOT/pages/mail-component.adoc | 2 +-
.../modules/ROOT/pages/metrics-component.adoc | 4 ++--
.../modules/ROOT/pages/microprofile-config.adoc | 2 +-
.../modules/ROOT/pages/microprofile-health.adoc | 2 +-
.../modules/ROOT/pages/mongodb-component.adoc | 2 +-
.../modules/ROOT/pages/mvel-language.adoc | 2 +-
.../modules/ROOT/pages/mybatis-component.adoc | 6 ++---
.../modules/ROOT/pages/ognl-language.adoc | 2 +-
docs/components/modules/ROOT/pages/openstack.adoc | 2 +-
.../components/modules/ROOT/pages/opentracing.adoc | 2 +-
.../ROOT/pages/reactive-executor-vertx.adoc | 2 +-
.../modules/ROOT/pages/secureXML-dataformat.adoc | 2 +-
.../modules/ROOT/pages/seda-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/shiro.adoc | 2 +-
.../modules/ROOT/pages/soapjaxb-dataformat.adoc | 4 ++--
.../modules/ROOT/pages/spel-language.adoc | 2 +-
.../components/modules/ROOT/pages/spring-boot.adoc | 4 ++--
.../modules/ROOT/pages/spring-cloud-consul.adoc | 2 +-
.../modules/ROOT/pages/spring-cloud-netflix.adoc | 4 ++--
.../modules/ROOT/pages/spring-cloud-zookeeper.adoc | 2 +-
.../modules/ROOT/pages/spring-cloud.adoc | 4 ++--
.../modules/ROOT/pages/spring-security.adoc | 2 +-
.../modules/ROOT/pages/spring-ws-component.adoc | 2 +-
.../modules/ROOT/pages/sql-component.adoc | 16 ++++++-------
.../modules/ROOT/pages/swagger-java.adoc | 6 ++---
.../modules/ROOT/pages/syslog-dataformat.adoc | 2 +-
.../modules/ROOT/pages/test-blueprint.adoc | 2 +-
.../modules/ROOT/pages/timer-component.adoc | 4 ++--
.../modules/ROOT/pages/velocity-component.adoc | 2 +-
.../modules/ROOT/pages/xmlsecurity-component.adoc | 2 +-
.../modules/ROOT/pages/xpath-language.adoc | 16 ++++++-------
docs/components/modules/ROOT/pages/zipkin.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/async.adoc | 2 +-
.../ROOT/pages/asynchronous-routing-engine.adoc | 2 +-
.../modules/ROOT/pages/backlog-tracer.adoc | 2 +-
.../modules/ROOT/pages/backlogdebugger.adoc | 2 +-
.../modules/ROOT/pages/batch-consumer.adoc | 2 +-
.../modules/ROOT/pages/bean-binding.adoc | 4 ++--
.../user-manual/modules/ROOT/pages/clustering.adoc | 2 +-
...ing-route-startup-ordering-and-autostartup.adoc | 4 ++--
.../modules/ROOT/pages/content-enricher.adoc | 4 ++--
.../modules/ROOT/pages/dead-letter-channel.adoc | 8 +++----
docs/user-manual/modules/ROOT/pages/debugger.adoc | 2 +-
.../modules/ROOT/pages/exception-clause.adoc | 18 +++++++--------
.../pages/faq/how-do-i-configure-endpoints.adoc | 8 +++----
...size-for-producercache-or-producertemplate.adoc | 2 +-
...ximum-endpoint-cache-size-for-camelcontext.adoc | 2 +-
...reams-when-debug-logging-messages-in-camel.adoc | 2 +-
...how-do-i-import-rests-from-other-xml-files.adoc | 2 +-
...ow-do-i-import-routes-from-other-xml-files.adoc | 2 +-
.../how-do-i-run-activemq-and-camel-in-jboss.adoc | 2 +-
...chars-when-debug-logging-messages-in-camel.adoc | 2 +-
...ify-time-period-in-a-human-friendly-syntax.adoc | 2 +-
...se-when-or-otherwise-in-a-java-camel-route.adoc | 2 +-
.../modules/ROOT/pages/graceful-shutdown.adoc | 8 +++----
.../modules/ROOT/pages/health-check.adoc | 2 +-
.../modules/ROOT/pages/http-session-handling.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/java-dsl.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/jmx.adoc | 16 ++++++-------
docs/user-manual/modules/ROOT/pages/json.adoc | 20 ++++++++---------
.../modules/ROOT/pages/oncompletion.adoc | 4 ++--
.../modules/ROOT/pages/pojo-consuming.adoc | 2 +-
.../modules/ROOT/pages/polling-consumer.adoc | 4 ++--
.../modules/ROOT/pages/producertemplate.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/rest-dsl.adoc | 6 ++---
.../modules/ROOT/pages/route-policy.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/routes.adoc | 2 +-
.../modules/ROOT/pages/scripting-languages.adoc | 8 +++----
docs/user-manual/modules/ROOT/pages/security.adoc | 4 ++--
.../modules/ROOT/pages/service-registry.adoc | 2 +-
.../modules/ROOT/pages/servicepool.adoc | 2 +-
.../modules/ROOT/pages/servlet-tomcat-example.adoc | 2 +-
.../modules/ROOT/pages/spring-remoting.adoc | 4 ++--
docs/user-manual/modules/ROOT/pages/spring.adoc | 2 +-
.../modules/ROOT/pages/stream-caching.adoc | 2 +-
.../modules/ROOT/pages/threading-model.adoc | 6 ++---
.../modules/ROOT/pages/transactional-client.adoc | 2 +-
.../ROOT/pages/transactionerrorhandler.adoc | 2 +-
.../modules/ROOT/pages/transformer.adoc | 2 +-
.../pages/using-osgi-blueprint-with-camel.adoc | 2 +-
.../ROOT/pages/using-propertyplaceholder.adoc | 26 +++++++++++-----------
docs/user-manual/modules/ROOT/pages/validator.adoc | 2 +-
154 files changed, 297 insertions(+), 297 deletions(-)
diff --git a/components/camel-aws-xray/src/main/docs/aws-xray.adoc b/components/camel-aws-xray/src/main/docs/aws-xray.adoc
index cda67cb..3977b8d 100644
--- a/components/camel-aws-xray/src/main/docs/aws-xray.adoc
+++ b/components/camel-aws-xray/src/main/docs/aws-xray.adoc
@@ -1,7 +1,7 @@
[[AWSXRay-AWSXRayComponent]]
= AWS XRay Component
-*Available as of Camel 2.21*
+*Since Camel 2.21*
The camel-aws-xray component is used for tracing and timing incoming and outgoing Camel messages using https://aws.amazon.com/xray/[AWS XRay].
diff --git a/components/camel-cometd/src/main/docs/cometd-component.adoc b/components/camel-cometd/src/main/docs/cometd-component.adoc
index c311b56..9c94004 100644
--- a/components/camel-cometd/src/main/docs/cometd-component.adoc
+++ b/components/camel-cometd/src/main/docs/cometd-component.adoc
@@ -178,7 +178,7 @@ cometd://localhost:8080?resourceBase=classpath:webapp
== Authentication
-*Available as of Camel 2.8*
+*Since Camel 2.8*
You can configure custom `SecurityPolicy` and `Extension`'s to the
`CometdComponent` which allows you to use authentication as
diff --git a/components/camel-controlbus/src/main/docs/controlbus-component.adoc b/components/camel-controlbus/src/main/docs/controlbus-component.adoc
index 120fd33..7a58eb4 100644
--- a/components/camel-controlbus/src/main/docs/controlbus-component.adoc
+++ b/components/camel-controlbus/src/main/docs/controlbus-component.adoc
@@ -165,7 +165,7 @@ String status = template.requestBody("controlbus:route?routeId=foo&action=status
[[ControlBus-Gettingperformancestatistics]]
== Getting performance statistics
-*Available as of Camel 2.11.1*
+*Since Camel 2.11.1*
This requires JMX to be enabled (is by default) then you can get the
performance statics per route, or for the
diff --git a/components/camel-csv/src/main/docs/csv-dataformat.adoc b/components/camel-csv/src/main/docs/csv-dataformat.adoc
index 73d8bfd..9e808c6 100644
--- a/components/camel-csv/src/main/docs/csv-dataformat.adoc
+++ b/components/camel-csv/src/main/docs/csv-dataformat.adoc
@@ -191,7 +191,7 @@ for (List<String> line : data) {
== Marshalling a List<Map> to CSV
-*Available as of Camel 2.1*
+*Since Camel 2.1*
If you have multiple rows of data you want to be marshalled into CSV
format you can now store the message payload as a
@@ -268,7 +268,7 @@ abc|123
Using autogenColumns, configRef and strategyRef attributes inside XML
== DSL
-*Available as of Camel 2.9.2 / 2.10 and deleted for Camel 2.15*
+*Since Camel 2.9.2 / 2.10 and deleted for Camel 2.15*
You can customize the CSV Data Format to make use
of your own `CSVConfig` and/or `CSVStrategy`. Also note that the default
@@ -307,7 +307,7 @@ should illustrate this customization.
== Using skipFirstLine option while unmarshaling
-*Available as of Camel 2.10 and deleted for Camel 2.15*
+*Since Camel 2.10 and deleted for Camel 2.15*
You can instruct the CSV Data Format to skip the
first line which contains the CSV headers. Using the Spring/XML DSL:
diff --git a/components/camel-cxf/src/main/docs/cxfrs-component.adoc b/components/camel-cxf/src/main/docs/cxfrs-component.adoc
index 3e84385..3e7813f 100644
--- a/components/camel-cxf/src/main/docs/cxfrs-component.adoc
+++ b/components/camel-cxf/src/main/docs/cxfrs-component.adoc
@@ -193,7 +193,7 @@ setting the message with the key of "CamelDestinationOverrideUrl".
== Consuming a REST Request - Simple Binding Style
-*Available as of Camel 2.11*
+*Since Camel 2.11*
The `Default` binding style is rather low-level, requiring the user to
manually process the `MessageContentsList` object coming into the route.
diff --git a/components/camel-elsql/src/main/docs/elsql-component.adoc b/components/camel-elsql/src/main/docs/elsql-component.adoc
index 6f26a04..6438cf6 100644
--- a/components/camel-elsql/src/main/docs/elsql-component.adoc
+++ b/components/camel-elsql/src/main/docs/elsql-component.adoc
@@ -272,7 +272,7 @@ assumes to have `getLicense` and `getMinimum` methods:
=== Using expression parameters in consumers
-*Available as of Camel 2.23*
+*Since Camel 2.23*
When using the ElSql component as consumer, you can now also use expression parameters (simple language)
to build dynamic query parameters, such as calling a method on a bean to retrieve an id, date or something.
diff --git a/components/camel-file/src/main/docs/file-component.adoc b/components/camel-file/src/main/docs/file-component.adoc
index 3787539..8bd708d 100644
--- a/components/camel-file/src/main/docs/file-component.adoc
+++ b/components/camel-file/src/main/docs/file-component.adoc
@@ -426,7 +426,7 @@ this number of files.
== Using charset
-*Available as of Camel 2.9.3* +
+*Since Camel 2.9.3* +
The charset option allows for configuring an encoding of the files on
both the consumer and producer endpoints. For example if you read utf-8
files, and want to convert the files to iso-8859-1, you can do:
@@ -577,7 +577,7 @@ done and ready to be consumed.
== Using done files
-*Available as of Camel 2.6*
+*Since Camel 2.6*
See also section _writing done files_ below.
@@ -625,7 +625,7 @@ from("file:bar?doneFileName=ready-${file:name}");
== Writing done files
-*Available as of Camel 2.6*
+*Since Camel 2.6*
After you have written a file you may want to write an additional _done_
_file_ as a kind of marker, to indicate to others that the file is
diff --git a/components/camel-groovy/src/main/docs/groovy-language.adoc b/components/camel-groovy/src/main/docs/groovy-language.adoc
index 489d7fe..bf801cb 100644
--- a/components/camel-groovy/src/main/docs/groovy-language.adoc
+++ b/components/camel-groovy/src/main/docs/groovy-language.adoc
@@ -143,7 +143,7 @@ languages with explicit DSL support.
== Additional arguments to ScriptingEngine
-*Available as of Camel 2.8*
+*Since Camel 2.8*
You can provide additional arguments to the `ScriptingEngine` using a
header on the Camel message with the key `CamelScriptArguments`. +
@@ -151,7 +151,7 @@ header on the Camel message with the key `CamelScriptArguments`. +
== Using properties function
-*Available as of Camel 2.9*
+*Since Camel 2.9*
If you need to use the xref:properties-component.adoc[Properties] component from a
script to lookup property placeholders, then its a bit cumbersome to do
@@ -173,7 +173,7 @@ You can use the properties function and the same example is simpler:
== Loading script from external resource
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can externalize the script and have Camel load it from a resource
such as `"classpath:"`, `"file:"`, or `"http:"`. +
@@ -187,7 +187,7 @@ eg to refer to a file on the classpath you can do:
== How to get the result from multiple statements script
-*Available as of Camel 2.14*
+*Since Camel 2.14*
As the scripteengine evale method just return a Null if it runs a
multiple statments script. Camel now look up the value of script result
diff --git a/components/camel-irc/src/main/docs/irc-component.adoc b/components/camel-irc/src/main/docs/irc-component.adoc
index c42c23c..9ce2baa 100644
--- a/components/camel-irc/src/main/docs/irc-component.adoc
+++ b/components/camel-irc/src/main/docs/irc-component.adoc
@@ -225,7 +225,7 @@ ircs:host[:port]/#room?username=user&password=pass&trustManager=#referenceToMyTr
== Using keys
-*Available as of Camel 2.2*
+*Since Camel 2.2*
Some irc rooms requires you to provide a key to be able to join that
channel. The key is just a secret word.
diff --git a/components/camel-jasypt/src/main/docs/jasypt.adoc b/components/camel-jasypt/src/main/docs/jasypt.adoc
index 0fb1044..3cc57e8 100644
--- a/components/camel-jasypt/src/main/docs/jasypt.adoc
+++ b/components/camel-jasypt/src/main/docs/jasypt.adoc
@@ -1,6 +1,6 @@
= Jasypt component
-*Available as of Camel 2.5*
+*Since Camel 2.5*
http://www.jasypt.org/[Jasypt] is a simplified encryption library which
makes encryption and decryption easy. Camel integrates with Jasypt to
diff --git a/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc b/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
index dc8dc8b..9f83322 100644
--- a/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
+++ b/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
@@ -230,7 +230,7 @@ In this Spring DSL we have defined to use `iso-8859-1` as the encoding:
== Controlling namespace prefix mapping
-*Available as of Camel 2.11*
+*Since Camel 2.11*
When marshalling using xref:jaxb-dataformat.adoc[JAXB] or xref:jaxb-dataformat.adoc[SOAP] then
the JAXB implementation will automatic assign namespace prefixes, such
@@ -268,7 +268,7 @@ with the id "myMap", which was what we defined above.
== Schema validation
-*Available as of Camel 2.11*
+*Since Camel 2.11*
The JAXB Data Format supports validation by
marshalling and unmarshalling from/to XML. Your can use the prefix
@@ -308,7 +308,7 @@ jaxbDataFormat.setSchemaFactory(thradSafeSchemaFactory);
== Schema Location
-*Available as of Camel 2.14*
+*Since Camel 2.14*
The JAXB Data Format supports to specify the
SchemaLocation when marshaling the XML.
@@ -333,7 +333,7 @@ You can do the same using the XML DSL:
== Marshal data that is already XML
-*Available as of Camel 2.14.1*
+*Since Camel 2.14.1*
The JAXB marshaller requires that the message body is JAXB compatible,
eg its a JAXBElement, eg a java instance that has JAXB annotations, or
diff --git a/components/camel-jdbc/src/main/docs/jdbc-component.adoc b/components/camel-jdbc/src/main/docs/jdbc-component.adoc
index 551d621..6209b85 100644
--- a/components/camel-jdbc/src/main/docs/jdbc-component.adoc
+++ b/components/camel-jdbc/src/main/docs/jdbc-component.adoc
@@ -174,7 +174,7 @@ type.
== Generated keys
-*Available as of Camel 2.10*
+*Since Camel 2.10*
If you insert data using SQL INSERT, then the RDBMS may support auto
generated keys. You can instruct the xref:jdbc-component.adoc[JDBC] producer to
@@ -187,7 +187,7 @@ Using generated keys does not work with together with named parameters.
== Using named parameters
-*Available as of Camel 2.12*
+*Since Camel 2.12*
In the given route below, we want to get all the projects from the
projects table. Notice the SQL query has 2 named parameters, :?lic and
diff --git a/components/camel-jms/src/main/docs/jms-component.adoc b/components/camel-jms/src/main/docs/jms-component.adoc
index 1b5a1dd..d8a29be 100644
--- a/components/camel-jms/src/main/docs/jms-component.adoc
+++ b/components/camel-jms/src/main/docs/jms-component.adoc
@@ -1252,7 +1252,7 @@ broker more frequent, and thus require more network traffic. +
=== Request-reply over JMS and using an exclusive fixed reply queue
-*Available as of Camel 2.9*
+*Since Camel 2.9*
In the previous example, Camel would anticipate the fixed reply queue
named "bar" was shared, and thus it uses a `JMSSelector` to only consume
@@ -1403,7 +1403,7 @@ messaging:
The `transacted` property applies *only* to the InOnly message
Exchange Pattern (MEP).
-*Available as of Camel 2.10*
+*Since Camel 2.10*
You can leverage the
http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/jms/listener/AbstractPollingMessageListenerContainer.html#setSessionTransacted(boolean)[DMLC
diff --git a/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc b/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
index 807f23a..bb003d1 100644
--- a/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
+++ b/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
@@ -110,7 +110,7 @@ further examples.
== Easy Syntax
-*Available as of Camel 2.19*
+*Since Camel 2.19*
When you just want to define a basic predicate using jsonpath syntax it can be a bit hard to remember the syntax.
So for example to find out all the cheap books you have to do
@@ -169,7 +169,7 @@ can configure JSonPath to suppress exceptions (see below)
== Suppress exceptions
-*Available as of Camel 2.16*
+*Since Camel 2.16*
By default jsonpath will throw an exception if the json payload does not
have a valid path accordingly to the configured jsonpath expression. In
@@ -210,7 +210,7 @@ This option is also available on the `@JsonPath` annotation.
== Inline Simple exceptions
-*Available as of Camel 2.18*
+*Since Camel 2.18*
Its now possible to inlined Simple language expressions in the JSonPath expression using the simple syntax $\{xxx\}.
An example is shown below:
@@ -319,7 +319,7 @@ would need to use camel-jackson dataformat and marshal the message body to make
convert the message body from `Map` to a `String` type.
== Using header as input
-*Available as of Camel 2.20*
+*Since Camel 2.20*
By default jsonpath uses the message body as the input source. However you can also use a header as input
by specifying the `headerName` option.
diff --git a/components/camel-jt400/src/main/docs/jt400-component.adoc b/components/camel-jt400/src/main/docs/jt400-component.adoc
index 6efce42..a91b450 100644
--- a/components/camel-jt400/src/main/docs/jt400-component.adoc
+++ b/components/camel-jt400/src/main/docs/jt400-component.adoc
@@ -166,7 +166,7 @@ the data queue as either raw bytes or text.
== Connection pool
-*Available as of Camel 2.10*
+*Since Camel 2.10*
You can explicit configure a connection pool on the Jt400Component, or as an uri option
on the endpoint.
diff --git a/components/camel-kafka/src/main/docs/kafka-component.adoc b/components/camel-kafka/src/main/docs/kafka-component.adoc
index ba46db7..0c37538 100644
--- a/components/camel-kafka/src/main/docs/kafka-component.adoc
+++ b/components/camel-kafka/src/main/docs/kafka-component.adoc
@@ -552,7 +552,7 @@ In XML:
----
== Using manual commit with Kafka consumer
-*Available as of Camel 2.21*
+*Since Camel 2.21*
By default the Kafka consumer will use auto commit, where the offset will be committed automatically in the background using a given interval.
@@ -584,7 +584,7 @@ If you want to use a custom implementation of `KafkaManualCommit` then you can c
on the `KafkaComponent` that creates instances of your custom implementation.
== Kafka Headers propagation
-*Available as of Camel 2.22*
+*Since Camel 2.22*
When consuming messages from Kafka, headers will be propagated to camel exchange headers automatically.
Producing flow backed by same behaviour - camel headers of particular exchange will be propagated to kafka message headers.
diff --git a/components/camel-kura/src/main/docs/kura.adoc b/components/camel-kura/src/main/docs/kura.adoc
index 2acc7a0..43945d5 100644
--- a/components/camel-kura/src/main/docs/kura.adoc
+++ b/components/camel-kura/src/main/docs/kura.adoc
@@ -1,7 +1,7 @@
[[Kura-EclipseKuracomponent]]
= Eclipse Kura component
-*Available as of Camel 2.15*
+*Since Camel 2.15*
This documentation page covers the integration options of Camel with the
https://eclipse.org/kura/[Eclipse Kura] M2M gateway. The common reason
diff --git a/components/camel-language/src/main/docs/language-component.adoc b/components/camel-language/src/main/docs/language-component.adoc
index bfdbd01..4355e54 100644
--- a/components/camel-language/src/main/docs/language-component.adoc
+++ b/components/camel-language/src/main/docs/language-component.adoc
@@ -159,7 +159,7 @@ assertEquals("Hello World", out);
== Loading scripts from resources
-*Available as of Camel 2.9*
+*Since Camel 2.9*
You can specify a resource uri for a script to load in either the
endpoint uri, or in the `Exchange.LANGUAGE_SCRIPT` header. +
diff --git a/components/camel-leveldb/src/main/docs/leveldb.adoc b/components/camel-leveldb/src/main/docs/leveldb.adoc
index b9cfad7..c5fa8ad 100644
--- a/components/camel-leveldb/src/main/docs/leveldb.adoc
+++ b/components/camel-leveldb/src/main/docs/leveldb.adoc
@@ -1,7 +1,7 @@
[[LevelDB-LevelDB]]
= LevelDB
-*Available as of Camel 2.10*
+*Since Camel 2.10*
https://code.google.com/p/leveldb/[Leveldb] is a very lightweight and
embedable key value database. It allows together with Camel to provide
diff --git a/components/camel-log/src/main/docs/log-component.adoc b/components/camel-log/src/main/docs/log-component.adoc
index dfd4875..37919e8 100644
--- a/components/camel-log/src/main/docs/log-component.adoc
+++ b/components/camel-log/src/main/docs/log-component.adoc
@@ -230,7 +230,7 @@ The following will be logged:
----
== Masking sensitive information like password
-*Available as of Camel 2.19*
+*Since Camel 2.19*
You can enable security masking for logging by setting `logMask` flag to `true`.
Note that this option also affects Log EIP.
@@ -270,7 +270,7 @@ Note that the masking formatter must implement `org.apache.camel.spi.MaskingForm
== Full customization of the logging output
-*Available as of Camel 2.11*
+*Since Camel 2.11*
With the options outlined in the xref:log-component.adoc[#Formatting] section, you
can control much of the output of the logger. However, log lines will
diff --git a/components/camel-mail/src/main/docs/mail-component.adoc b/components/camel-mail/src/main/docs/mail-component.adoc
index 9b291dc..0b6b4f6 100644
--- a/components/camel-mail/src/main/docs/mail-component.adoc
+++ b/components/camel-mail/src/main/docs/mail-component.adoc
@@ -656,7 +656,7 @@ And then use the expression with the splitter eip.
== Using custom SearchTerm
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can configure a `searchTerm` on the `MailEndpoint` which allows you
to filter out unwanted mails.
diff --git a/components/camel-metrics/src/main/docs/metrics-component.adoc b/components/camel-metrics/src/main/docs/metrics-component.adoc
index 749b74b..c8790a1 100644
--- a/components/camel-metrics/src/main/docs/metrics-component.adoc
+++ b/components/camel-metrics/src/main/docs/metrics-component.adoc
@@ -576,7 +576,7 @@ if (registryService != null) {
== MetricsMessageHistoryFactory
-*Available as of Camel 2.17*
+*Since Camel 2.17*
This factory allows to use metrics to
capture Message History performance
@@ -652,7 +652,7 @@ with `name=MetricsMessageHistoryService`.
== InstrumentedThreadPoolFactory
-*Available as of Camel 2.18*
+*Since Camel 2.18*
This factory allows you to gather performance information about Camel Thread Pools by injecting a InstrumentedThreadPoolFactory
which collects information from inside of Camel.
diff --git a/components/camel-microprofile-config/src/main/docs/microprofile-config.adoc b/components/camel-microprofile-config/src/main/docs/microprofile-config.adoc
index d0acd08..37013d317 100644
--- a/components/camel-microprofile-config/src/main/docs/microprofile-config.adoc
+++ b/components/camel-microprofile-config/src/main/docs/microprofile-config.adoc
@@ -1,7 +1,7 @@
[[MicroProfileConfig]]
= MicroProfile Config
-*Available as of Camel 3.0*
+*Since Camel 3.0*
The microprofile-config component is used for bridging the Eclipse MicroProfile Config with Camels
properties component. This allows to use configuration management from Eclipse MicroProfile with Camel.
diff --git a/components/camel-microprofile-health/src/main/docs/microprofile-health.adoc b/components/camel-microprofile-health/src/main/docs/microprofile-health.adoc
index 6f9f17f..57d4a3a 100644
--- a/components/camel-microprofile-health/src/main/docs/microprofile-health.adoc
+++ b/components/camel-microprofile-health/src/main/docs/microprofile-health.adoc
@@ -1,7 +1,7 @@
[[MicroProfileHealth-MicroProfileHealthComponent]]
= MicroProfile Health
-*Available as of Camel 3.0*
+*Since Camel 3.0*
The microprofile-health component is used for bridging https://microprofile.io/project/eclipse/microprofile-health[Eclipse MicroProfile Health] checks with Camel's own Health Check API.
diff --git a/components/camel-mongodb/src/main/docs/mongodb-component.adoc b/components/camel-mongodb/src/main/docs/mongodb-component.adoc
index c85ad03..937614b 100644
--- a/components/camel-mongodb/src/main/docs/mongodb-component.adoc
+++ b/components/camel-mongodb/src/main/docs/mongodb-component.adoc
@@ -622,7 +622,7 @@ containing the number of records deleted (copied from
==== bulkWrite
-*Available as of Camel 2.21*
+*Since Camel 2.21*
Performs write operations in bulk with controls for order of execution.
Requires a `List<WriteModel<Document>>` as the IN message body containing commands for insert, update, and delete operations.
diff --git a/components/camel-mvel/src/main/docs/mvel-language.adoc b/components/camel-mvel/src/main/docs/mvel-language.adoc
index d44c137..6c3b2a9 100644
--- a/components/camel-mvel/src/main/docs/mvel-language.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-language.adoc
@@ -121,7 +121,7 @@ And the sample using Java DSL:
== Loading script from external resource
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can externalize the script and have Camel load it from a resource
such as `"classpath:"`, `"file:"`, or `"http:"`. +
diff --git a/components/camel-mybatis/src/main/docs/mybatis-component.adoc b/components/camel-mybatis/src/main/docs/mybatis-component.adoc
index c926e5b..d4af05f 100644
--- a/components/camel-mybatis/src/main/docs/mybatis-component.adoc
+++ b/components/camel-mybatis/src/main/docs/mybatis-component.adoc
@@ -232,7 +232,7 @@ IN body to MyBatis:
=== Using InsertList StatementType
-*Available as of Camel 2.10*
+*Since Camel 2.10*
MyBatis allows you to insert multiple rows using its for-each batch
driver. To use this, you need to use the <foreach> in the mapper XML
@@ -244,7 +244,7 @@ below:
=== Using UpdateList StatementType
-*Available as of Camel 2.11*
+*Since Camel 2.11*
MyBatis allows you to update multiple rows using its for-each batch
driver. To use this, you need to use the <foreach> in the mapper XML
@@ -276,7 +276,7 @@ from("direct:start")
=== Using DeleteList StatementType
-*Available as of Camel 2.11*
+*Since Camel 2.11*
MyBatis allows you to delete multiple rows using its for-each batch
driver. To use this, you need to use the <foreach> in the mapper XML
diff --git a/components/camel-ognl/src/main/docs/ognl-language.adoc b/components/camel-ognl/src/main/docs/ognl-language.adoc
index 678c26c..0194981 100644
--- a/components/camel-ognl/src/main/docs/ognl-language.adoc
+++ b/components/camel-ognl/src/main/docs/ognl-language.adoc
@@ -121,7 +121,7 @@ And the sample using Java DSL:
== Loading script from external resource
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can externalize the script and have Camel load it from a resource
such as `"classpath:"`, `"file:"`, or `"http:"`. +
diff --git a/components/camel-openstack/src/main/docs/openstack.adoc b/components/camel-openstack/src/main/docs/openstack.adoc
index 3a5a70a..ca411ec 100644
--- a/components/camel-openstack/src/main/docs/openstack.adoc
+++ b/components/camel-openstack/src/main/docs/openstack.adoc
@@ -1,7 +1,7 @@
[[Openstack-OpenstackComponent]]
= Openstack Component
-*Available as of Camel 2.19*
+*Since Camel 2.19*
The Openstack component is a component for managing your
https://www.openstack.org//[OpenStack] applications.
diff --git a/components/camel-opentracing/src/main/docs/opentracing.adoc b/components/camel-opentracing/src/main/docs/opentracing.adoc
index c630d81..4199c36 100644
--- a/components/camel-opentracing/src/main/docs/opentracing.adoc
+++ b/components/camel-opentracing/src/main/docs/opentracing.adoc
@@ -1,7 +1,7 @@
[[OpenTracing-OpenTracingComponent]]
= OpenTracing Component
-*Available as of Camel 2.19*
+*Since Camel 2.19*
The OpenTracing component is used for tracing and timing incoming and
outgoing Camel messages using http://opentracing.io/[OpenTracing].
diff --git a/components/camel-reactive-executor-vertx/src/main/docs/reactive-executor-vertx.adoc b/components/camel-reactive-executor-vertx/src/main/docs/reactive-executor-vertx.adoc
index f224023..94723f2 100644
--- a/components/camel-reactive-executor-vertx/src/main/docs/reactive-executor-vertx.adoc
+++ b/components/camel-reactive-executor-vertx/src/main/docs/reactive-executor-vertx.adoc
@@ -1,6 +1,6 @@
= ReactiveExecutor VertX
-*Available as of Camel 3.0*
+*Since Camel 3.0*
The camel-reactive-executor-vertx is a VertX based implementation of the `ReactiveExecutor` SPI.
diff --git a/components/camel-seda/src/main/docs/seda-component.adoc b/components/camel-seda/src/main/docs/seda-component.adoc
index 0abcd65..7ee0723 100644
--- a/components/camel-seda/src/main/docs/seda-component.adoc
+++ b/components/camel-seda/src/main/docs/seda-component.adoc
@@ -146,7 +146,7 @@ The component supports 9 options, which are listed below.
== Choosing BlockingQueue implementation
-*Available as of Camel 2.12*
+*Since Camel 2.12*
By default, the SEDA component always intantiates LinkedBlockingQueue,
but you can use different implementation, you can reference your own
@@ -320,7 +320,7 @@ unit test.
== Using multipleConsumers
-*Available as of Camel 2.2*
+*Since Camel 2.2*
In this example we have defined two consumers and registered them as
spring beans.
diff --git a/components/camel-shiro/src/main/docs/shiro.adoc b/components/camel-shiro/src/main/docs/shiro.adoc
index a3e6a77..b8b6e47 100644
--- a/components/camel-shiro/src/main/docs/shiro.adoc
+++ b/components/camel-shiro/src/main/docs/shiro.adoc
@@ -1,7 +1,7 @@
[[ShiroSecurity-ShiroSecurityComponent]]
= Shiro Security Component
-*Available as of Camel 2.5*
+*Since Camel 2.5*
The Shiro Security component in Camel is a security focused component,
based on the Apache Shiro security project.
diff --git a/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc b/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc
index f6a917c..69c9d78 100644
--- a/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc
+++ b/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc
@@ -124,7 +124,7 @@ most settings apply here as well
=== Using SOAP 1.2
-*Available as of Camel 2.11*
+*Since Camel 2.11*
[source,java]
-------------------------------------------------------------------------------------------------------------------------------------
@@ -162,7 +162,7 @@ And in the Camel route
== Multi-part Messages
-*Available as of Camel 2.8.1*
+*Since Camel 2.8.1*
Multi-part SOAP messages are supported by the ServiceInterfaceStrategy.
The ServiceInterfaceStrategy must be initialized with a service
diff --git a/components/camel-spring-boot/src/main/docs/spring-boot.adoc b/components/camel-spring-boot/src/main/docs/spring-boot.adoc
index 8cf1e08..3083b78 100644
--- a/components/camel-spring-boot/src/main/docs/spring-boot.adoc
+++ b/components/camel-spring-boot/src/main/docs/spring-boot.adoc
@@ -1,7 +1,7 @@
[[SpringBoot-SpringBoot]]
= Spring Boot
-*Available as of Camel 2.15*
+*Since Camel 2.15*
Spring Boot component provides auto-configuration for Apache Camel. Our
opinionated auto-configuration of the Camel context auto-detects Camel
@@ -28,7 +28,7 @@ automatically auto-configure Camel for you.
[[SpringBoot-CamelSpringBootStarter]]
== Camel Spring Boot Starter
-*Available as of Camel 2.17*
+*Since Camel 2.17*
Apache Camel ships
a https://github.com/spring-projects/spring-boot/tree/master/spring-boot-project/spring-boot-starters[Spring
diff --git a/components/camel-spring-cloud-consul/src/main/docs/spring-cloud-consul.adoc b/components/camel-spring-cloud-consul/src/main/docs/spring-cloud-consul.adoc
index 9552961..23d6896 100644
--- a/components/camel-spring-cloud-consul/src/main/docs/spring-cloud-consul.adoc
+++ b/components/camel-spring-cloud-consul/src/main/docs/spring-cloud-consul.adoc
@@ -1,3 +1,3 @@
= Spring Cloud Consul
-*Available as of Camel 2.22*
+*Since Camel 2.22*
diff --git a/components/camel-spring-cloud-netflix/src/main/docs/spring-cloud-netflix.adoc b/components/camel-spring-cloud-netflix/src/main/docs/spring-cloud-netflix.adoc
index d8e4e75..f77f984 100644
--- a/components/camel-spring-cloud-netflix/src/main/docs/spring-cloud-netflix.adoc
+++ b/components/camel-spring-cloud-netflix/src/main/docs/spring-cloud-netflix.adoc
@@ -1,6 +1,6 @@
= Spring Cloud Netflix
-*Available as of Camel 2.19*
+*Since Camel 2.19*
The Spring Cloud Netflix component bridges Camel Cloud and Spring Cloud Netflix so you can leverage Spring Cloud Netflix service discovery and load balance features in Camel and/or you can use Camel Service Discovery implementations as ServerList source for Spring Cloud Netflix's Ribbon load balabncer.
@@ -31,7 +31,7 @@ camel.cloud.netflix.ribbon = true
== Spring Cloud Netflix Starter
-*Available as of Camel 2.19*
+*Since Camel 2.19*
To use the starter, add the following to your spring boot pom.xml file:
diff --git a/components/camel-spring-cloud-zookeeper/src/main/docs/spring-cloud-zookeeper.adoc b/components/camel-spring-cloud-zookeeper/src/main/docs/spring-cloud-zookeeper.adoc
index 1073ee3..cd8efbf 100644
--- a/components/camel-spring-cloud-zookeeper/src/main/docs/spring-cloud-zookeeper.adoc
+++ b/components/camel-spring-cloud-zookeeper/src/main/docs/spring-cloud-zookeeper.adoc
@@ -1,3 +1,3 @@
= Spring Cloud Zookeeper
-*Available as of Camel 2.22*
+*Since Camel 2.22*
diff --git a/components/camel-spring-cloud/src/main/docs/spring-cloud.adoc b/components/camel-spring-cloud/src/main/docs/spring-cloud.adoc
index c9044e4..d4b8f4d 100644
--- a/components/camel-spring-cloud/src/main/docs/spring-cloud.adoc
+++ b/components/camel-spring-cloud/src/main/docs/spring-cloud.adoc
@@ -1,7 +1,7 @@
[[SpringCloud-SpringCloud]]
= Spring Cloud
-*Available as of Camel 2.19*
+*Since Camel 2.19*
Spring Cloud component
@@ -24,7 +24,7 @@ automatically auto-configure Camel for you.
[[SpringCloud-CamelSpringCloudStarter]]
== Camel Spring Cloud Starter
-*Available as of Camel 2.19*
+*Since Camel 2.19*
To use the starter, add the following to your spring boot pom.xml file:
diff --git a/components/camel-spring-security/src/main/docs/spring-security.adoc b/components/camel-spring-security/src/main/docs/spring-security.adoc
index c213062..2c5cbbc 100644
--- a/components/camel-spring-security/src/main/docs/spring-security.adoc
+++ b/components/camel-spring-security/src/main/docs/spring-security.adoc
@@ -1,7 +1,7 @@
[[SpringSecurity-SpringSecurity]]
= Spring Security
-*Available as of Camel 2.3*
+*Since Camel 2.3*
The Camel Spring Security component provides role-based authorization
for Camel routes. It leverages the authentication and user services
diff --git a/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc b/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc
index 287febe..6166c98 100644
--- a/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc
+++ b/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc
@@ -262,7 +262,7 @@ SpringWebserviceConstants.SPRING_WS_SOAP_ACTION, "http://baz.com");
== Using SOAP headers
-*Available as of Camel 2.11.1*
+*Since Camel 2.11.1*
You can provide the SOAP header(s) as a Camel Message header when
sending a message to a spring-ws endpoint, for example given the
diff --git a/components/camel-spring/src/main/docs/spel-language.adoc b/components/camel-spring/src/main/docs/spel-language.adoc
index f112d61..3e6ef59 100644
--- a/components/camel-spring/src/main/docs/spel-language.adoc
+++ b/components/camel-spring/src/main/docs/spel-language.adoc
@@ -141,7 +141,7 @@ from("direct:foo")
== Loading script from external resource
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can externalize the script and have Camel load it from a resource
such as `"classpath:"`, `"file:"`, or `"http:"`. +
diff --git a/components/camel-sql/src/main/docs/sql-component.adoc b/components/camel-sql/src/main/docs/sql-component.adoc
index 68409c6..e1d40bf 100644
--- a/components/camel-sql/src/main/docs/sql-component.adoc
+++ b/components/camel-sql/src/main/docs/sql-component.adoc
@@ -341,7 +341,7 @@ message headers:
== Generated keys
-*Available as of Camel 2.12.4, 2.13.1 and 2.14*
+*Since Camel 2.12.4, 2.13.1 and 2.14*
If you insert data using SQL INSERT, then the RDBMS may support auto
generated keys. You can instruct the SQL producer to return the
@@ -364,7 +364,7 @@ sql:select * from table where id=# order by name?dataSource=myDS
== Using named parameters
-*Available as of Camel 2.11*
+*Since Camel 2.11*
In the given route below, we want to get all the projects from the
projects table. Notice the SQL query has 2 named parameters, :#lic and
@@ -393,7 +393,7 @@ parameters will be taken from the body.
== Using expression parameters in producers
-*Available as of Camel 2.14*
+*Since Camel 2.14*
In the given route below, we want to get all the project from the
database. It uses the body of the exchange for defining the license and
@@ -409,7 +409,7 @@ from("direct:projects")
=== Using expression parameters in consumers
-*Available as of Camel 2.23*
+*Since Camel 2.23*
When using the SQL component as consumer, you can now also use expression parameters (simple language)
to build dynamic query parameters, such as calling a method on a bean to retrieve an id, date or something.
@@ -441,7 +441,7 @@ bean methods as in this example.
== Using IN queries with dynamic values
-*Available as of Camel 2.17*
+*Since Camel 2.17*
The SQL producer allows to use SQL queries with
IN statements where the IN values is dynamic computed. For example from
@@ -507,7 +507,7 @@ from("direct:query")
== Using the JDBC based idempotent repository
-*Available as of Camel 2.7*
+*Since Camel 2.7*
In this section we will use the JDBC based
idempotent repository.
@@ -585,7 +585,7 @@ the second one is the message id (`String`).
== Using the JDBC based aggregation repository
-*Available as of Camel 2.6*
+*Since Camel 2.6*
`JdbcAggregationRepository` is an `AggregationRepository` which on the
fly persists the aggregated messages. This ensures that you will not
@@ -646,7 +646,7 @@ CREATE TABLE aggregation_completed (
== Storing body and headers as text
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can configure the `JdbcAggregationRepository` to store message body
and select(ed) headers as String in separate columns. For example to
diff --git a/components/camel-swagger-java/src/main/docs/swagger-java.adoc b/components/camel-swagger-java/src/main/docs/swagger-java.adoc
index 72ad366..953aef3 100644
--- a/components/camel-swagger-java/src/main/docs/swagger-java.adoc
+++ b/components/camel-swagger-java/src/main/docs/swagger-java.adoc
@@ -1,6 +1,6 @@
= Swagger Java Component
-*Available as of Camel 2.16*
+*Since Camel 2.16*
The Rest DSL can be integrated with
the `camel-swagger-java` module which is used for exposing the REST
@@ -127,7 +127,7 @@ Intercept
== Adding Security Definitions in API doc
-*Available as of Camel 2.22.0*
+*Since Camel 2.22.0*
The Rest DSL now supports declaring Swagger `securityDefinitions` in the generated API document.
For example as shown below:
@@ -178,7 +178,7 @@ option apiContextIdPattern can be used to filter the names in this list.
== JSon or Yaml
-*Available as of Camel 2.17*
+*Since Camel 2.17*
The camel-swagger-java module supports both JSon and Yaml out of the
box. You can specify in the request url what you want returned by using
diff --git a/components/camel-syslog/src/main/docs/syslog-dataformat.adoc b/components/camel-syslog/src/main/docs/syslog-dataformat.adoc
index 4b61688..cd830c0 100644
--- a/components/camel-syslog/src/main/docs/syslog-dataformat.adoc
+++ b/components/camel-syslog/src/main/docs/syslog-dataformat.adoc
@@ -88,7 +88,7 @@ ND
== RFC5424 Syslog protocol
-*Available as of Camel 2.14*
+*Since Camel 2.14*
To expose a Syslog listener service we reuse the
existing xref:mina-component.adoc[Mina Component] component
diff --git a/components/camel-test-blueprint/src/main/docs/test-blueprint.adoc b/components/camel-test-blueprint/src/main/docs/test-blueprint.adoc
index 36221af..2aff5c1 100644
--- a/components/camel-test-blueprint/src/main/docs/test-blueprint.adoc
+++ b/components/camel-test-blueprint/src/main/docs/test-blueprint.adoc
@@ -1,6 +1,6 @@
= Blueprint Testing
-*Available as of Camel 2.10*
+*Since Camel 2.10*
camel-test-blueprint does only support testing _one_ CamelContext. So
if you have two or more CamelContexts in your blueprint XML files, then
diff --git a/components/camel-timer/src/main/docs/timer-component.adoc b/components/camel-timer/src/main/docs/timer-component.adoc
index 9b50d63..091df27 100644
--- a/components/camel-timer/src/main/docs/timer-component.adoc
+++ b/components/camel-timer/src/main/docs/timer-component.adoc
@@ -172,7 +172,7 @@ And the route in Spring DSL:
== Firing as soon as possible
-*Available as of Camel 2.17*
+*Since Camel 2.17*
You may want to fire messages in a Camel route as soon as possible you
can use a negative delay:
@@ -196,7 +196,7 @@ messages until the route will be stopped.
== Firing only once
-*Available as of Camel 2.8*
+*Since Camel 2.8*
You may want to fire a message in a Camel route only once, such as when
starting the route. To do that you use the repeatCount option as shown:
diff --git a/components/camel-velocity/src/main/docs/velocity-component.adoc b/components/camel-velocity/src/main/docs/velocity-component.adoc
index 71a6ef3..349dcb5 100644
--- a/components/camel-velocity/src/main/docs/velocity-component.adoc
+++ b/components/camel-velocity/src/main/docs/velocity-component.adoc
@@ -208,7 +208,7 @@ when the resource never changes.
== Dynamic templates
-*Available as of Camel 2.1* +
+*Since Camel 2.1* +
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these
headers is set then Camel uses this over the endpoint configured
diff --git a/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc b/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc
index 5198b11..496165c 100644
--- a/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc
+++ b/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc
@@ -16,7 +16,7 @@ encryption formats. Additional formats can be easily added later as
needed. This capability allows Camel users to encrypt/decrypt payloads
while being dispatched or received along a route.
-*Available as of Camel 2.9* +
+*Since Camel 2.9* +
The XMLSecurity Data Format supports asymmetric key encryption. In this
encryption model a symmetric key is generated and used to perform XML
content encryption or decryption. This "content encryption key" is then
diff --git a/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc b/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
index 9b235ec..e07d666 100644
--- a/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
+++ b/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
@@ -583,7 +583,7 @@ from("direct:detached")
== XAdES-BES/EPES for the Signer Endpoint
-*Available as of Camel 2.15.0*
+*Since Camel 2.15.0*
http://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf[XML
Advanced Electronic Signatures (XAdES)] defines extensions to XML
diff --git a/components/camel-xpath/src/main/docs/xpath-language.adoc b/components/camel-xpath/src/main/docs/xpath-language.adoc
index ec792dc..604c96c 100644
--- a/components/camel-xpath/src/main/docs/xpath-language.adoc
+++ b/components/camel-xpath/src/main/docs/xpath-language.adoc
@@ -225,7 +225,7 @@ qualified classname:
----
In @XPath: +
- *Available as of Camel 2.1*
+ *Since Camel 2.1*
[source,java]
----
@@ -238,7 +238,7 @@ type so the concat function works.
== Using XPath on Headers
-*Available as of Camel 2.11*
+*Since Camel 2.11*
Some users may have XML stored in a header. To apply an XPath to a
header's value you can do this by defining the 'headerName' attribute.
@@ -305,7 +305,7 @@ public class Foo {
== Using XPathBuilder without an Exchange
-*Available as of Camel 2.3*
+*Since Camel 2.3*
You can now use the `org.apache.camel.builder.XPathBuilder` without the
need for an Exchange. This comes handy if you want
@@ -345,7 +345,7 @@ String name = XPathBuilder.xpath("foo/bar").evaluate(context, "<foo><bar>cheese<
== Using Saxon with XPathBuilder
-*Available as of Camel 2.3*
+*Since Camel 2.3*
You need to add *camel-saxon* as dependency to your project.
@@ -360,7 +360,7 @@ The easy one
== Setting a custom XPathFactory using System Property
-*Available as of Camel 2.3*
+*Since Camel 2.3*
Camel now supports reading the
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/XPathFactory.html#newInstance(java.lang.String)[JVM
@@ -387,7 +387,7 @@ To use Apache Xerces you can configure the system property
== Enabling Saxon from Spring DSL
-*Available as of Camel 2.10*
+*Since Camel 2.10*
Similarly to Java DSL, to enable Saxon from Spring DSL you have three
options:
@@ -415,7 +415,7 @@ Shortcut
== Namespace auditing to aid debugging
-*Available as of Camel 2.10*
+*Since Camel 2.10*
A large number of XPath-related issues that users frequently face are
linked to the usage of namespaces. You may have some misalignment
@@ -509,7 +509,7 @@ xmlns:b=[http://apache.org/camelA, http://apache.org/camelB]}
== Loading script from external resource
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can externalize the script and have Camel load it from a resource
such as `"classpath:"`, `"file:"`, or `"http:"`. +
diff --git a/components/camel-zipkin/src/main/docs/zipkin.adoc b/components/camel-zipkin/src/main/docs/zipkin.adoc
index ee7b2df..535e311 100644
--- a/components/camel-zipkin/src/main/docs/zipkin.adoc
+++ b/components/camel-zipkin/src/main/docs/zipkin.adoc
@@ -1,7 +1,7 @@
[[Zipkin-ZipkinComponent]]
= Zipkin Component
-*Available as of Camel 2.18*
+*Since Camel 2.18*
The Camel Zipkin component is used for tracing and timing incoming and outgoing Camel messages using http://zipkin.io/[zipkin].
diff --git a/docs/components/modules/ROOT/pages/aws-xray.adoc b/docs/components/modules/ROOT/pages/aws-xray.adoc
index 606eaec..0c8067d 100644
--- a/docs/components/modules/ROOT/pages/aws-xray.adoc
+++ b/docs/components/modules/ROOT/pages/aws-xray.adoc
@@ -2,7 +2,7 @@
= AWS XRay Component
:page-source: components/camel-aws-xray/src/main/docs/aws-xray.adoc
-*Available as of Camel 2.21*
+*Since Camel 2.21*
The camel-aws-xray component is used for tracing and timing incoming and outgoing Camel messages using https://aws.amazon.com/xray/[AWS XRay].
diff --git a/docs/components/modules/ROOT/pages/cometd-component.adoc b/docs/components/modules/ROOT/pages/cometd-component.adoc
index c2437cd..075cd4b 100644
--- a/docs/components/modules/ROOT/pages/cometd-component.adoc
+++ b/docs/components/modules/ROOT/pages/cometd-component.adoc
@@ -179,7 +179,7 @@ cometd://localhost:8080?resourceBase=classpath:webapp
== Authentication
-*Available as of Camel 2.8*
+*Since Camel 2.8*
You can configure custom `SecurityPolicy` and `Extension`'s to the
`CometdComponent` which allows you to use authentication as
diff --git a/docs/components/modules/ROOT/pages/controlbus-component.adoc b/docs/components/modules/ROOT/pages/controlbus-component.adoc
index d2ada39..a56be2a 100644
--- a/docs/components/modules/ROOT/pages/controlbus-component.adoc
+++ b/docs/components/modules/ROOT/pages/controlbus-component.adoc
@@ -166,7 +166,7 @@ String status = template.requestBody("controlbus:route?routeId=foo&action=status
[[ControlBus-Gettingperformancestatistics]]
== Getting performance statistics
-*Available as of Camel 2.11.1*
+*Since Camel 2.11.1*
This requires JMX to be enabled (is by default) then you can get the
performance statics per route, or for the
diff --git a/docs/components/modules/ROOT/pages/csv-dataformat.adoc b/docs/components/modules/ROOT/pages/csv-dataformat.adoc
index 698c22b..1cee8ee 100644
--- a/docs/components/modules/ROOT/pages/csv-dataformat.adoc
+++ b/docs/components/modules/ROOT/pages/csv-dataformat.adoc
@@ -192,7 +192,7 @@ for (List<String> line : data) {
== Marshalling a List<Map> to CSV
-*Available as of Camel 2.1*
+*Since Camel 2.1*
If you have multiple rows of data you want to be marshalled into CSV
format you can now store the message payload as a
@@ -269,7 +269,7 @@ abc|123
Using autogenColumns, configRef and strategyRef attributes inside XML
== DSL
-*Available as of Camel 2.9.2 / 2.10 and deleted for Camel 2.15*
+*Since Camel 2.9.2 / 2.10 and deleted for Camel 2.15*
You can customize the CSV Data Format to make use
of your own `CSVConfig` and/or `CSVStrategy`. Also note that the default
@@ -308,7 +308,7 @@ should illustrate this customization.
== Using skipFirstLine option while unmarshaling
-*Available as of Camel 2.10 and deleted for Camel 2.15*
+*Since Camel 2.10 and deleted for Camel 2.15*
You can instruct the CSV Data Format to skip the
first line which contains the CSV headers. Using the Spring/XML DSL:
diff --git a/docs/components/modules/ROOT/pages/cxfrs-component.adoc b/docs/components/modules/ROOT/pages/cxfrs-component.adoc
index 720e630..4a13cb7 100644
--- a/docs/components/modules/ROOT/pages/cxfrs-component.adoc
+++ b/docs/components/modules/ROOT/pages/cxfrs-component.adoc
@@ -194,7 +194,7 @@ setting the message with the key of "CamelDestinationOverrideUrl".
== Consuming a REST Request - Simple Binding Style
-*Available as of Camel 2.11*
+*Since Camel 2.11*
The `Default` binding style is rather low-level, requiring the user to
manually process the `MessageContentsList` object coming into the route.
diff --git a/docs/components/modules/ROOT/pages/elsql-component.adoc b/docs/components/modules/ROOT/pages/elsql-component.adoc
index 8214baf..96ed62e 100644
--- a/docs/components/modules/ROOT/pages/elsql-component.adoc
+++ b/docs/components/modules/ROOT/pages/elsql-component.adoc
@@ -273,7 +273,7 @@ assumes to have `getLicense` and `getMinimum` methods:
=== Using expression parameters in consumers
-*Available as of Camel 2.23*
+*Since Camel 2.23*
When using the ElSql component as consumer, you can now also use expression parameters (simple language)
to build dynamic query parameters, such as calling a method on a bean to retrieve an id, date or something.
diff --git a/docs/components/modules/ROOT/pages/file-component.adoc b/docs/components/modules/ROOT/pages/file-component.adoc
index f55af8b..0b1d096 100644
--- a/docs/components/modules/ROOT/pages/file-component.adoc
+++ b/docs/components/modules/ROOT/pages/file-component.adoc
@@ -427,7 +427,7 @@ this number of files.
== Using charset
-*Available as of Camel 2.9.3* +
+*Since Camel 2.9.3* +
The charset option allows for configuring an encoding of the files on
both the consumer and producer endpoints. For example if you read utf-8
files, and want to convert the files to iso-8859-1, you can do:
@@ -578,7 +578,7 @@ done and ready to be consumed.
== Using done files
-*Available as of Camel 2.6*
+*Since Camel 2.6*
See also section _writing done files_ below.
@@ -626,7 +626,7 @@ from("file:bar?doneFileName=ready-${file:name}");
== Writing done files
-*Available as of Camel 2.6*
+*Since Camel 2.6*
After you have written a file you may want to write an additional _done_
_file_ as a kind of marker, to indicate to others that the file is
diff --git a/docs/components/modules/ROOT/pages/groovy-language.adoc b/docs/components/modules/ROOT/pages/groovy-language.adoc
index 233783e..c875b88 100644
--- a/docs/components/modules/ROOT/pages/groovy-language.adoc
+++ b/docs/components/modules/ROOT/pages/groovy-language.adoc
@@ -144,7 +144,7 @@ languages with explicit DSL support.
== Additional arguments to ScriptingEngine
-*Available as of Camel 2.8*
+*Since Camel 2.8*
You can provide additional arguments to the `ScriptingEngine` using a
header on the Camel message with the key `CamelScriptArguments`. +
@@ -152,7 +152,7 @@ header on the Camel message with the key `CamelScriptArguments`. +
== Using properties function
-*Available as of Camel 2.9*
+*Since Camel 2.9*
If you need to use the xref:properties-component.adoc[Properties] component from a
script to lookup property placeholders, then its a bit cumbersome to do
@@ -174,7 +174,7 @@ You can use the properties function and the same example is simpler:
== Loading script from external resource
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can externalize the script and have Camel load it from a resource
such as `"classpath:"`, `"file:"`, or `"http:"`. +
@@ -188,7 +188,7 @@ eg to refer to a file on the classpath you can do:
== How to get the result from multiple statements script
-*Available as of Camel 2.14*
+*Since Camel 2.14*
As the scripteengine evale method just return a Null if it runs a
multiple statments script. Camel now look up the value of script result
diff --git a/docs/components/modules/ROOT/pages/irc-component.adoc b/docs/components/modules/ROOT/pages/irc-component.adoc
index f081052..dc45fb6 100644
--- a/docs/components/modules/ROOT/pages/irc-component.adoc
+++ b/docs/components/modules/ROOT/pages/irc-component.adoc
@@ -226,7 +226,7 @@ ircs:host[:port]/#room?username=user&password=pass&trustManager=#referenceToMyTr
== Using keys
-*Available as of Camel 2.2*
+*Since Camel 2.2*
Some irc rooms requires you to provide a key to be able to join that
channel. The key is just a secret word.
diff --git a/docs/components/modules/ROOT/pages/jasypt.adoc b/docs/components/modules/ROOT/pages/jasypt.adoc
index a005d83..b7a4df7 100644
--- a/docs/components/modules/ROOT/pages/jasypt.adoc
+++ b/docs/components/modules/ROOT/pages/jasypt.adoc
@@ -1,7 +1,7 @@
= Jasypt component
:page-source: components/camel-jasypt/src/main/docs/jasypt.adoc
-*Available as of Camel 2.5*
+*Since Camel 2.5*
http://www.jasypt.org/[Jasypt] is a simplified encryption library which
makes encryption and decryption easy. Camel integrates with Jasypt to
diff --git a/docs/components/modules/ROOT/pages/jaxb-dataformat.adoc b/docs/components/modules/ROOT/pages/jaxb-dataformat.adoc
index a1ddd31..f689bc1 100644
--- a/docs/components/modules/ROOT/pages/jaxb-dataformat.adoc
+++ b/docs/components/modules/ROOT/pages/jaxb-dataformat.adoc
@@ -231,7 +231,7 @@ In this Spring DSL we have defined to use `iso-8859-1` as the encoding:
== Controlling namespace prefix mapping
-*Available as of Camel 2.11*
+*Since Camel 2.11*
When marshalling using xref:jaxb-dataformat.adoc[JAXB] or xref:jaxb-dataformat.adoc[SOAP] then
the JAXB implementation will automatic assign namespace prefixes, such
@@ -269,7 +269,7 @@ with the id "myMap", which was what we defined above.
== Schema validation
-*Available as of Camel 2.11*
+*Since Camel 2.11*
The JAXB Data Format supports validation by
marshalling and unmarshalling from/to XML. Your can use the prefix
@@ -309,7 +309,7 @@ jaxbDataFormat.setSchemaFactory(thradSafeSchemaFactory);
== Schema Location
-*Available as of Camel 2.14*
+*Since Camel 2.14*
The JAXB Data Format supports to specify the
SchemaLocation when marshaling the XML.
@@ -334,7 +334,7 @@ You can do the same using the XML DSL:
== Marshal data that is already XML
-*Available as of Camel 2.14.1*
+*Since Camel 2.14.1*
The JAXB marshaller requires that the message body is JAXB compatible,
eg its a JAXBElement, eg a java instance that has JAXB annotations, or
diff --git a/docs/components/modules/ROOT/pages/jdbc-component.adoc b/docs/components/modules/ROOT/pages/jdbc-component.adoc
index 4b0de30..7552230 100644
--- a/docs/components/modules/ROOT/pages/jdbc-component.adoc
+++ b/docs/components/modules/ROOT/pages/jdbc-component.adoc
@@ -175,7 +175,7 @@ type.
== Generated keys
-*Available as of Camel 2.10*
+*Since Camel 2.10*
If you insert data using SQL INSERT, then the RDBMS may support auto
generated keys. You can instruct the xref:jdbc-component.adoc[JDBC] producer to
@@ -188,7 +188,7 @@ Using generated keys does not work with together with named parameters.
== Using named parameters
-*Available as of Camel 2.12*
+*Since Camel 2.12*
In the given route below, we want to get all the projects from the
projects table. Notice the SQL query has 2 named parameters, :?lic and
diff --git a/docs/components/modules/ROOT/pages/jms-component.adoc b/docs/components/modules/ROOT/pages/jms-component.adoc
index 1b958f5..adf6125 100644
--- a/docs/components/modules/ROOT/pages/jms-component.adoc
+++ b/docs/components/modules/ROOT/pages/jms-component.adoc
@@ -1253,7 +1253,7 @@ broker more frequent, and thus require more network traffic. +
=== Request-reply over JMS and using an exclusive fixed reply queue
-*Available as of Camel 2.9*
+*Since Camel 2.9*
In the previous example, Camel would anticipate the fixed reply queue
named "bar" was shared, and thus it uses a `JMSSelector` to only consume
@@ -1404,7 +1404,7 @@ messaging:
The `transacted` property applies *only* to the InOnly message
Exchange Pattern (MEP).
-*Available as of Camel 2.10*
+*Since Camel 2.10*
You can leverage the
http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/jms/listener/AbstractPollingMessageListenerContainer.html#setSessionTransacted(boolean)[DMLC
diff --git a/docs/components/modules/ROOT/pages/jsonpath-language.adoc b/docs/components/modules/ROOT/pages/jsonpath-language.adoc
index e0ffdc6..3959787 100644
--- a/docs/components/modules/ROOT/pages/jsonpath-language.adoc
+++ b/docs/components/modules/ROOT/pages/jsonpath-language.adoc
@@ -111,7 +111,7 @@ further examples.
== Easy Syntax
-*Available as of Camel 2.19*
+*Since Camel 2.19*
When you just want to define a basic predicate using jsonpath syntax it can be a bit hard to remember the syntax.
So for example to find out all the cheap books you have to do
@@ -170,7 +170,7 @@ can configure JSonPath to suppress exceptions (see below)
== Suppress exceptions
-*Available as of Camel 2.16*
+*Since Camel 2.16*
By default jsonpath will throw an exception if the json payload does not
have a valid path accordingly to the configured jsonpath expression. In
@@ -211,7 +211,7 @@ This option is also available on the `@JsonPath` annotation.
== Inline Simple exceptions
-*Available as of Camel 2.18*
+*Since Camel 2.18*
Its now possible to inlined Simple language expressions in the JSonPath expression using the simple syntax $\{xxx\}.
An example is shown below:
@@ -320,7 +320,7 @@ would need to use camel-jackson dataformat and marshal the message body to make
convert the message body from `Map` to a `String` type.
== Using header as input
-*Available as of Camel 2.20*
+*Since Camel 2.20*
By default jsonpath uses the message body as the input source. However you can also use a header as input
by specifying the `headerName` option.
diff --git a/docs/components/modules/ROOT/pages/jt400-component.adoc b/docs/components/modules/ROOT/pages/jt400-component.adoc
index 5a9bea1..197053a 100644
--- a/docs/components/modules/ROOT/pages/jt400-component.adoc
+++ b/docs/components/modules/ROOT/pages/jt400-component.adoc
@@ -167,7 +167,7 @@ the data queue as either raw bytes or text.
== Connection pool
-*Available as of Camel 2.10*
+*Since Camel 2.10*
You can explicit configure a connection pool on the Jt400Component, or as an uri option
on the endpoint.
diff --git a/docs/components/modules/ROOT/pages/kafka-component.adoc b/docs/components/modules/ROOT/pages/kafka-component.adoc
index b143a6c..ede1932 100644
--- a/docs/components/modules/ROOT/pages/kafka-component.adoc
+++ b/docs/components/modules/ROOT/pages/kafka-component.adoc
@@ -553,7 +553,7 @@ In XML:
----
== Using manual commit with Kafka consumer
-*Available as of Camel 2.21*
+*Since Camel 2.21*
By default the Kafka consumer will use auto commit, where the offset will be committed automatically in the background using a given interval.
@@ -585,7 +585,7 @@ If you want to use a custom implementation of `KafkaManualCommit` then you can c
on the `KafkaComponent` that creates instances of your custom implementation.
== Kafka Headers propagation
-*Available as of Camel 2.22*
+*Since Camel 2.22*
When consuming messages from Kafka, headers will be propagated to camel exchange headers automatically.
Producing flow backed by same behaviour - camel headers of particular exchange will be propagated to kafka message headers.
diff --git a/docs/components/modules/ROOT/pages/kura.adoc b/docs/components/modules/ROOT/pages/kura.adoc
index 0a70e59..6fb6246 100644
--- a/docs/components/modules/ROOT/pages/kura.adoc
+++ b/docs/components/modules/ROOT/pages/kura.adoc
@@ -2,7 +2,7 @@
= Eclipse Kura component
:page-source: components/camel-kura/src/main/docs/kura.adoc
-*Available as of Camel 2.15*
+*Since Camel 2.15*
This documentation page covers the integration options of Camel with the
https://eclipse.org/kura/[Eclipse Kura] M2M gateway. The common reason
diff --git a/docs/components/modules/ROOT/pages/language-component.adoc b/docs/components/modules/ROOT/pages/language-component.adoc
index 4055d8d..c674bcd 100644
--- a/docs/components/modules/ROOT/pages/language-component.adoc
+++ b/docs/components/modules/ROOT/pages/language-component.adoc
@@ -160,7 +160,7 @@ assertEquals("Hello World", out);
== Loading scripts from resources
-*Available as of Camel 2.9*
+*Since Camel 2.9*
You can specify a resource uri for a script to load in either the
endpoint uri, or in the `Exchange.LANGUAGE_SCRIPT` header. +
diff --git a/docs/components/modules/ROOT/pages/leveldb.adoc b/docs/components/modules/ROOT/pages/leveldb.adoc
index 166fbd6..77e10f5 100644
--- a/docs/components/modules/ROOT/pages/leveldb.adoc
+++ b/docs/components/modules/ROOT/pages/leveldb.adoc
@@ -2,7 +2,7 @@
= LevelDB
:page-source: components/camel-leveldb/src/main/docs/leveldb.adoc
-*Available as of Camel 2.10*
+*Since Camel 2.10*
https://code.google.com/p/leveldb/[Leveldb] is a very lightweight and
embedable key value database. It allows together with Camel to provide
diff --git a/docs/components/modules/ROOT/pages/log-component.adoc b/docs/components/modules/ROOT/pages/log-component.adoc
index aa2e6b8..23cf7e2 100644
--- a/docs/components/modules/ROOT/pages/log-component.adoc
+++ b/docs/components/modules/ROOT/pages/log-component.adoc
@@ -231,7 +231,7 @@ The following will be logged:
----
== Masking sensitive information like password
-*Available as of Camel 2.19*
+*Since Camel 2.19*
You can enable security masking for logging by setting `logMask` flag to `true`.
Note that this option also affects Log EIP.
@@ -271,7 +271,7 @@ Note that the masking formatter must implement `org.apache.camel.spi.MaskingForm
== Full customization of the logging output
-*Available as of Camel 2.11*
+*Since Camel 2.11*
With the options outlined in the xref:log-component.adoc[#Formatting] section, you
can control much of the output of the logger. However, log lines will
diff --git a/docs/components/modules/ROOT/pages/mail-component.adoc b/docs/components/modules/ROOT/pages/mail-component.adoc
index b872903..0862bfa 100644
--- a/docs/components/modules/ROOT/pages/mail-component.adoc
+++ b/docs/components/modules/ROOT/pages/mail-component.adoc
@@ -657,7 +657,7 @@ And then use the expression with the splitter eip.
== Using custom SearchTerm
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can configure a `searchTerm` on the `MailEndpoint` which allows you
to filter out unwanted mails.
diff --git a/docs/components/modules/ROOT/pages/metrics-component.adoc b/docs/components/modules/ROOT/pages/metrics-component.adoc
index cb49faa..1cb1c99 100644
--- a/docs/components/modules/ROOT/pages/metrics-component.adoc
+++ b/docs/components/modules/ROOT/pages/metrics-component.adoc
@@ -577,7 +577,7 @@ if (registryService != null) {
== MetricsMessageHistoryFactory
-*Available as of Camel 2.17*
+*Since Camel 2.17*
This factory allows to use metrics to
capture Message History performance
@@ -653,7 +653,7 @@ with `name=MetricsMessageHistoryService`.
== InstrumentedThreadPoolFactory
-*Available as of Camel 2.18*
+*Since Camel 2.18*
This factory allows you to gather performance information about Camel Thread Pools by injecting a InstrumentedThreadPoolFactory
which collects information from inside of Camel.
diff --git a/docs/components/modules/ROOT/pages/microprofile-config.adoc b/docs/components/modules/ROOT/pages/microprofile-config.adoc
index 926aeac..50f5565 100644
--- a/docs/components/modules/ROOT/pages/microprofile-config.adoc
+++ b/docs/components/modules/ROOT/pages/microprofile-config.adoc
@@ -2,7 +2,7 @@
= MicroProfile Config
:page-source: components/camel-microprofile-config/src/main/docs/microprofile-config.adoc
-*Available as of Camel 3.0*
+*Since Camel 3.0*
The microprofile-config component is used for bridging the Eclipse MicroProfile Config with Camels
properties component. This allows to use configuration management from Eclipse MicroProfile with Camel.
diff --git a/docs/components/modules/ROOT/pages/microprofile-health.adoc b/docs/components/modules/ROOT/pages/microprofile-health.adoc
index 7e98c52..0fed98a8 100644
--- a/docs/components/modules/ROOT/pages/microprofile-health.adoc
+++ b/docs/components/modules/ROOT/pages/microprofile-health.adoc
@@ -2,7 +2,7 @@
= MicroProfile Health
:page-source: components/camel-microprofile-health/src/main/docs/microprofile-health.adoc
-*Available as of Camel 3.0*
+*Since Camel 3.0*
The microprofile-health component is used for bridging https://microprofile.io/project/eclipse/microprofile-health[Eclipse MicroProfile Health] checks with Camel's own Health Check API.
diff --git a/docs/components/modules/ROOT/pages/mongodb-component.adoc b/docs/components/modules/ROOT/pages/mongodb-component.adoc
index 34e35b9..390cf4f 100644
--- a/docs/components/modules/ROOT/pages/mongodb-component.adoc
+++ b/docs/components/modules/ROOT/pages/mongodb-component.adoc
@@ -623,7 +623,7 @@ containing the number of records deleted (copied from
==== bulkWrite
-*Available as of Camel 2.21*
+*Since Camel 2.21*
Performs write operations in bulk with controls for order of execution.
Requires a `List<WriteModel<Document>>` as the IN message body containing commands for insert, update, and delete operations.
diff --git a/docs/components/modules/ROOT/pages/mvel-language.adoc b/docs/components/modules/ROOT/pages/mvel-language.adoc
index e32c6f1..dc72a70 100644
--- a/docs/components/modules/ROOT/pages/mvel-language.adoc
+++ b/docs/components/modules/ROOT/pages/mvel-language.adoc
@@ -122,7 +122,7 @@ And the sample using Java DSL:
== Loading script from external resource
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can externalize the script and have Camel load it from a resource
such as `"classpath:"`, `"file:"`, or `"http:"`. +
diff --git a/docs/components/modules/ROOT/pages/mybatis-component.adoc b/docs/components/modules/ROOT/pages/mybatis-component.adoc
index 3411966..ddb8a75 100644
--- a/docs/components/modules/ROOT/pages/mybatis-component.adoc
+++ b/docs/components/modules/ROOT/pages/mybatis-component.adoc
@@ -233,7 +233,7 @@ IN body to MyBatis:
=== Using InsertList StatementType
-*Available as of Camel 2.10*
+*Since Camel 2.10*
MyBatis allows you to insert multiple rows using its for-each batch
driver. To use this, you need to use the <foreach> in the mapper XML
@@ -245,7 +245,7 @@ below:
=== Using UpdateList StatementType
-*Available as of Camel 2.11*
+*Since Camel 2.11*
MyBatis allows you to update multiple rows using its for-each batch
driver. To use this, you need to use the <foreach> in the mapper XML
@@ -277,7 +277,7 @@ from("direct:start")
=== Using DeleteList StatementType
-*Available as of Camel 2.11*
+*Since Camel 2.11*
MyBatis allows you to delete multiple rows using its for-each batch
driver. To use this, you need to use the <foreach> in the mapper XML
diff --git a/docs/components/modules/ROOT/pages/ognl-language.adoc b/docs/components/modules/ROOT/pages/ognl-language.adoc
index e9ece0a..b754dc0 100644
--- a/docs/components/modules/ROOT/pages/ognl-language.adoc
+++ b/docs/components/modules/ROOT/pages/ognl-language.adoc
@@ -122,7 +122,7 @@ And the sample using Java DSL:
== Loading script from external resource
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can externalize the script and have Camel load it from a resource
such as `"classpath:"`, `"file:"`, or `"http:"`. +
diff --git a/docs/components/modules/ROOT/pages/openstack.adoc b/docs/components/modules/ROOT/pages/openstack.adoc
index cda896e..e8240b5 100644
--- a/docs/components/modules/ROOT/pages/openstack.adoc
+++ b/docs/components/modules/ROOT/pages/openstack.adoc
@@ -2,7 +2,7 @@
= Openstack Component
:page-source: components/camel-openstack/src/main/docs/openstack.adoc
-*Available as of Camel 2.19*
+*Since Camel 2.19*
The Openstack component is a component for managing your
https://www.openstack.org//[OpenStack] applications.
diff --git a/docs/components/modules/ROOT/pages/opentracing.adoc b/docs/components/modules/ROOT/pages/opentracing.adoc
index 1304e25d..06e2966 100644
--- a/docs/components/modules/ROOT/pages/opentracing.adoc
+++ b/docs/components/modules/ROOT/pages/opentracing.adoc
@@ -2,7 +2,7 @@
= OpenTracing Component
:page-source: components/camel-opentracing/src/main/docs/opentracing.adoc
-*Available as of Camel 2.19*
+*Since Camel 2.19*
The OpenTracing component is used for tracing and timing incoming and
outgoing Camel messages using http://opentracing.io/[OpenTracing].
diff --git a/docs/components/modules/ROOT/pages/reactive-executor-vertx.adoc b/docs/components/modules/ROOT/pages/reactive-executor-vertx.adoc
index 610241b..91bed36 100644
--- a/docs/components/modules/ROOT/pages/reactive-executor-vertx.adoc
+++ b/docs/components/modules/ROOT/pages/reactive-executor-vertx.adoc
@@ -1,7 +1,7 @@
= ReactiveExecutor VertX
:page-source: components/camel-reactive-executor-vertx/src/main/docs/reactive-executor-vertx.adoc
-*Available as of Camel 3.0*
+*Since Camel 3.0*
The camel-reactive-executor-vertx is a VertX based implementation of the `ReactiveExecutor` SPI.
diff --git a/docs/components/modules/ROOT/pages/secureXML-dataformat.adoc b/docs/components/modules/ROOT/pages/secureXML-dataformat.adoc
index 662cc1c..00bc1b9 100644
--- a/docs/components/modules/ROOT/pages/secureXML-dataformat.adoc
+++ b/docs/components/modules/ROOT/pages/secureXML-dataformat.adoc
@@ -17,7 +17,7 @@ encryption formats. Additional formats can be easily added later as
needed. This capability allows Camel users to encrypt/decrypt payloads
while being dispatched or received along a route.
-*Available as of Camel 2.9* +
+*Since Camel 2.9* +
The XMLSecurity Data Format supports asymmetric key encryption. In this
encryption model a symmetric key is generated and used to perform XML
content encryption or decryption. This "content encryption key" is then
diff --git a/docs/components/modules/ROOT/pages/seda-component.adoc b/docs/components/modules/ROOT/pages/seda-component.adoc
index 0db8d0b..f806ea4 100644
--- a/docs/components/modules/ROOT/pages/seda-component.adoc
+++ b/docs/components/modules/ROOT/pages/seda-component.adoc
@@ -147,7 +147,7 @@ The component supports 9 options, which are listed below.
== Choosing BlockingQueue implementation
-*Available as of Camel 2.12*
+*Since Camel 2.12*
By default, the SEDA component always intantiates LinkedBlockingQueue,
but you can use different implementation, you can reference your own
@@ -321,7 +321,7 @@ unit test.
== Using multipleConsumers
-*Available as of Camel 2.2*
+*Since Camel 2.2*
In this example we have defined two consumers and registered them as
spring beans.
diff --git a/docs/components/modules/ROOT/pages/shiro.adoc b/docs/components/modules/ROOT/pages/shiro.adoc
index 9127b18..000f9b6 100644
--- a/docs/components/modules/ROOT/pages/shiro.adoc
+++ b/docs/components/modules/ROOT/pages/shiro.adoc
@@ -2,7 +2,7 @@
= Shiro Security Component
:page-source: components/camel-shiro/src/main/docs/shiro.adoc
-*Available as of Camel 2.5*
+*Since Camel 2.5*
The Shiro Security component in Camel is a security focused component,
based on the Apache Shiro security project.
diff --git a/docs/components/modules/ROOT/pages/soapjaxb-dataformat.adoc b/docs/components/modules/ROOT/pages/soapjaxb-dataformat.adoc
index 1006f8a..9bf96cc 100644
--- a/docs/components/modules/ROOT/pages/soapjaxb-dataformat.adoc
+++ b/docs/components/modules/ROOT/pages/soapjaxb-dataformat.adoc
@@ -125,7 +125,7 @@ most settings apply here as well
=== Using SOAP 1.2
-*Available as of Camel 2.11*
+*Since Camel 2.11*
[source,java]
-------------------------------------------------------------------------------------------------------------------------------------
@@ -163,7 +163,7 @@ And in the Camel route
== Multi-part Messages
-*Available as of Camel 2.8.1*
+*Since Camel 2.8.1*
Multi-part SOAP messages are supported by the ServiceInterfaceStrategy.
The ServiceInterfaceStrategy must be initialized with a service
diff --git a/docs/components/modules/ROOT/pages/spel-language.adoc b/docs/components/modules/ROOT/pages/spel-language.adoc
index d197da6..f9003ea 100644
--- a/docs/components/modules/ROOT/pages/spel-language.adoc
+++ b/docs/components/modules/ROOT/pages/spel-language.adoc
@@ -142,7 +142,7 @@ from("direct:foo")
== Loading script from external resource
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can externalize the script and have Camel load it from a resource
such as `"classpath:"`, `"file:"`, or `"http:"`. +
diff --git a/docs/components/modules/ROOT/pages/spring-boot.adoc b/docs/components/modules/ROOT/pages/spring-boot.adoc
index 0cb64d3..e87352a 100644
--- a/docs/components/modules/ROOT/pages/spring-boot.adoc
+++ b/docs/components/modules/ROOT/pages/spring-boot.adoc
@@ -2,7 +2,7 @@
= Spring Boot
:page-source: components/camel-spring-boot/src/main/docs/spring-boot.adoc
-*Available as of Camel 2.15*
+*Since Camel 2.15*
Spring Boot component provides auto-configuration for Apache Camel. Our
opinionated auto-configuration of the Camel context auto-detects Camel
@@ -29,7 +29,7 @@ automatically auto-configure Camel for you.
[[SpringBoot-CamelSpringBootStarter]]
== Camel Spring Boot Starter
-*Available as of Camel 2.17*
+*Since Camel 2.17*
Apache Camel ships
a https://github.com/spring-projects/spring-boot/tree/master/spring-boot-project/spring-boot-starters[Spring
diff --git a/docs/components/modules/ROOT/pages/spring-cloud-consul.adoc b/docs/components/modules/ROOT/pages/spring-cloud-consul.adoc
index 02997cb..bf2e878 100644
--- a/docs/components/modules/ROOT/pages/spring-cloud-consul.adoc
+++ b/docs/components/modules/ROOT/pages/spring-cloud-consul.adoc
@@ -1,4 +1,4 @@
= Spring Cloud Consul
:page-source: components/camel-spring-cloud-consul/src/main/docs/spring-cloud-consul.adoc
-*Available as of Camel 2.22*
+*Since Camel 2.22*
diff --git a/docs/components/modules/ROOT/pages/spring-cloud-netflix.adoc b/docs/components/modules/ROOT/pages/spring-cloud-netflix.adoc
index 2392a07..68cb302 100644
--- a/docs/components/modules/ROOT/pages/spring-cloud-netflix.adoc
+++ b/docs/components/modules/ROOT/pages/spring-cloud-netflix.adoc
@@ -1,7 +1,7 @@
= Spring Cloud Netflix
:page-source: components/camel-spring-cloud-netflix/src/main/docs/spring-cloud-netflix.adoc
-*Available as of Camel 2.19*
+*Since Camel 2.19*
The Spring Cloud Netflix component bridges Camel Cloud and Spring Cloud Netflix so you can leverage Spring Cloud Netflix service discovery and load balance features in Camel and/or you can use Camel Service Discovery implementations as ServerList source for Spring Cloud Netflix's Ribbon load balabncer.
@@ -32,7 +32,7 @@ camel.cloud.netflix.ribbon = true
== Spring Cloud Netflix Starter
-*Available as of Camel 2.19*
+*Since Camel 2.19*
To use the starter, add the following to your spring boot pom.xml file:
diff --git a/docs/components/modules/ROOT/pages/spring-cloud-zookeeper.adoc b/docs/components/modules/ROOT/pages/spring-cloud-zookeeper.adoc
index 7d090b4..129679b 100644
--- a/docs/components/modules/ROOT/pages/spring-cloud-zookeeper.adoc
+++ b/docs/components/modules/ROOT/pages/spring-cloud-zookeeper.adoc
@@ -1,4 +1,4 @@
= Spring Cloud Zookeeper
:page-source: components/camel-spring-cloud-zookeeper/src/main/docs/spring-cloud-zookeeper.adoc
-*Available as of Camel 2.22*
+*Since Camel 2.22*
diff --git a/docs/components/modules/ROOT/pages/spring-cloud.adoc b/docs/components/modules/ROOT/pages/spring-cloud.adoc
index 735da9e..91bf117 100644
--- a/docs/components/modules/ROOT/pages/spring-cloud.adoc
+++ b/docs/components/modules/ROOT/pages/spring-cloud.adoc
@@ -2,7 +2,7 @@
= Spring Cloud
:page-source: components/camel-spring-cloud/src/main/docs/spring-cloud.adoc
-*Available as of Camel 2.19*
+*Since Camel 2.19*
Spring Cloud component
@@ -25,7 +25,7 @@ automatically auto-configure Camel for you.
[[SpringCloud-CamelSpringCloudStarter]]
== Camel Spring Cloud Starter
-*Available as of Camel 2.19*
+*Since Camel 2.19*
To use the starter, add the following to your spring boot pom.xml file:
diff --git a/docs/components/modules/ROOT/pages/spring-security.adoc b/docs/components/modules/ROOT/pages/spring-security.adoc
index d55a5f9..4542a04 100644
--- a/docs/components/modules/ROOT/pages/spring-security.adoc
+++ b/docs/components/modules/ROOT/pages/spring-security.adoc
@@ -2,7 +2,7 @@
= Spring Security
:page-source: components/camel-spring-security/src/main/docs/spring-security.adoc
-*Available as of Camel 2.3*
+*Since Camel 2.3*
The Camel Spring Security component provides role-based authorization
for Camel routes. It leverages the authentication and user services
diff --git a/docs/components/modules/ROOT/pages/spring-ws-component.adoc b/docs/components/modules/ROOT/pages/spring-ws-component.adoc
index 17b300a..025e9b5 100644
--- a/docs/components/modules/ROOT/pages/spring-ws-component.adoc
+++ b/docs/components/modules/ROOT/pages/spring-ws-component.adoc
@@ -263,7 +263,7 @@ SpringWebserviceConstants.SPRING_WS_SOAP_ACTION, "http://baz.com");
== Using SOAP headers
-*Available as of Camel 2.11.1*
+*Since Camel 2.11.1*
You can provide the SOAP header(s) as a Camel Message header when
sending a message to a spring-ws endpoint, for example given the
diff --git a/docs/components/modules/ROOT/pages/sql-component.adoc b/docs/components/modules/ROOT/pages/sql-component.adoc
index d247abf..e648744 100644
--- a/docs/components/modules/ROOT/pages/sql-component.adoc
+++ b/docs/components/modules/ROOT/pages/sql-component.adoc
@@ -342,7 +342,7 @@ message headers:
== Generated keys
-*Available as of Camel 2.12.4, 2.13.1 and 2.14*
+*Since Camel 2.12.4, 2.13.1 and 2.14*
If you insert data using SQL INSERT, then the RDBMS may support auto
generated keys. You can instruct the SQL producer to return the
@@ -365,7 +365,7 @@ sql:select * from table where id=# order by name?dataSource=myDS
== Using named parameters
-*Available as of Camel 2.11*
+*Since Camel 2.11*
In the given route below, we want to get all the projects from the
projects table. Notice the SQL query has 2 named parameters, :#lic and
@@ -394,7 +394,7 @@ parameters will be taken from the body.
== Using expression parameters in producers
-*Available as of Camel 2.14*
+*Since Camel 2.14*
In the given route below, we want to get all the project from the
database. It uses the body of the exchange for defining the license and
@@ -410,7 +410,7 @@ from("direct:projects")
=== Using expression parameters in consumers
-*Available as of Camel 2.23*
+*Since Camel 2.23*
When using the SQL component as consumer, you can now also use expression parameters (simple language)
to build dynamic query parameters, such as calling a method on a bean to retrieve an id, date or something.
@@ -442,7 +442,7 @@ bean methods as in this example.
== Using IN queries with dynamic values
-*Available as of Camel 2.17*
+*Since Camel 2.17*
The SQL producer allows to use SQL queries with
IN statements where the IN values is dynamic computed. For example from
@@ -508,7 +508,7 @@ from("direct:query")
== Using the JDBC based idempotent repository
-*Available as of Camel 2.7*
+*Since Camel 2.7*
In this section we will use the JDBC based
idempotent repository.
@@ -586,7 +586,7 @@ the second one is the message id (`String`).
== Using the JDBC based aggregation repository
-*Available as of Camel 2.6*
+*Since Camel 2.6*
`JdbcAggregationRepository` is an `AggregationRepository` which on the
fly persists the aggregated messages. This ensures that you will not
@@ -647,7 +647,7 @@ CREATE TABLE aggregation_completed (
== Storing body and headers as text
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can configure the `JdbcAggregationRepository` to store message body
and select(ed) headers as String in separate columns. For example to
diff --git a/docs/components/modules/ROOT/pages/swagger-java.adoc b/docs/components/modules/ROOT/pages/swagger-java.adoc
index ffe3c6a..64d3de3 100644
--- a/docs/components/modules/ROOT/pages/swagger-java.adoc
+++ b/docs/components/modules/ROOT/pages/swagger-java.adoc
@@ -1,7 +1,7 @@
= Swagger Java Component
:page-source: components/camel-swagger-java/src/main/docs/swagger-java.adoc
-*Available as of Camel 2.16*
+*Since Camel 2.16*
The Rest DSL can be integrated with
the `camel-swagger-java` module which is used for exposing the REST
@@ -128,7 +128,7 @@ Intercept
== Adding Security Definitions in API doc
-*Available as of Camel 2.22.0*
+*Since Camel 2.22.0*
The Rest DSL now supports declaring Swagger `securityDefinitions` in the generated API document.
For example as shown below:
@@ -179,7 +179,7 @@ option apiContextIdPattern can be used to filter the names in this list.
== JSon or Yaml
-*Available as of Camel 2.17*
+*Since Camel 2.17*
The camel-swagger-java module supports both JSon and Yaml out of the
box. You can specify in the request url what you want returned by using
diff --git a/docs/components/modules/ROOT/pages/syslog-dataformat.adoc b/docs/components/modules/ROOT/pages/syslog-dataformat.adoc
index 243e828..51639ef 100644
--- a/docs/components/modules/ROOT/pages/syslog-dataformat.adoc
+++ b/docs/components/modules/ROOT/pages/syslog-dataformat.adoc
@@ -89,7 +89,7 @@ ND
== RFC5424 Syslog protocol
-*Available as of Camel 2.14*
+*Since Camel 2.14*
To expose a Syslog listener service we reuse the
existing xref:mina-component.adoc[Mina Component] component
diff --git a/docs/components/modules/ROOT/pages/test-blueprint.adoc b/docs/components/modules/ROOT/pages/test-blueprint.adoc
index 4fff03b..ae2342a 100644
--- a/docs/components/modules/ROOT/pages/test-blueprint.adoc
+++ b/docs/components/modules/ROOT/pages/test-blueprint.adoc
@@ -1,7 +1,7 @@
= Blueprint Testing
:page-source: components/camel-test-blueprint/src/main/docs/test-blueprint.adoc
-*Available as of Camel 2.10*
+*Since Camel 2.10*
camel-test-blueprint does only support testing _one_ CamelContext. So
if you have two or more CamelContexts in your blueprint XML files, then
diff --git a/docs/components/modules/ROOT/pages/timer-component.adoc b/docs/components/modules/ROOT/pages/timer-component.adoc
index 3e654be..f4bc766 100644
--- a/docs/components/modules/ROOT/pages/timer-component.adoc
+++ b/docs/components/modules/ROOT/pages/timer-component.adoc
@@ -173,7 +173,7 @@ And the route in Spring DSL:
== Firing as soon as possible
-*Available as of Camel 2.17*
+*Since Camel 2.17*
You may want to fire messages in a Camel route as soon as possible you
can use a negative delay:
@@ -197,7 +197,7 @@ messages until the route will be stopped.
== Firing only once
-*Available as of Camel 2.8*
+*Since Camel 2.8*
You may want to fire a message in a Camel route only once, such as when
starting the route. To do that you use the repeatCount option as shown:
diff --git a/docs/components/modules/ROOT/pages/velocity-component.adoc b/docs/components/modules/ROOT/pages/velocity-component.adoc
index 2d4c6e7..dd7d91f 100644
--- a/docs/components/modules/ROOT/pages/velocity-component.adoc
+++ b/docs/components/modules/ROOT/pages/velocity-component.adoc
@@ -209,7 +209,7 @@ when the resource never changes.
== Dynamic templates
-*Available as of Camel 2.1* +
+*Since Camel 2.1* +
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these
headers is set then Camel uses this over the endpoint configured
diff --git a/docs/components/modules/ROOT/pages/xmlsecurity-component.adoc b/docs/components/modules/ROOT/pages/xmlsecurity-component.adoc
index 34ff665..e1771fa 100644
--- a/docs/components/modules/ROOT/pages/xmlsecurity-component.adoc
+++ b/docs/components/modules/ROOT/pages/xmlsecurity-component.adoc
@@ -584,7 +584,7 @@ from("direct:detached")
== XAdES-BES/EPES for the Signer Endpoint
-*Available as of Camel 2.15.0*
+*Since Camel 2.15.0*
http://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf[XML
Advanced Electronic Signatures (XAdES)] defines extensions to XML
diff --git a/docs/components/modules/ROOT/pages/xpath-language.adoc b/docs/components/modules/ROOT/pages/xpath-language.adoc
index 7058013..ac26f9e 100644
--- a/docs/components/modules/ROOT/pages/xpath-language.adoc
+++ b/docs/components/modules/ROOT/pages/xpath-language.adoc
@@ -226,7 +226,7 @@ qualified classname:
----
In @XPath: +
- *Available as of Camel 2.1*
+ *Since Camel 2.1*
[source,java]
----
@@ -239,7 +239,7 @@ type so the concat function works.
== Using XPath on Headers
-*Available as of Camel 2.11*
+*Since Camel 2.11*
Some users may have XML stored in a header. To apply an XPath to a
header's value you can do this by defining the 'headerName' attribute.
@@ -306,7 +306,7 @@ public class Foo {
== Using XPathBuilder without an Exchange
-*Available as of Camel 2.3*
+*Since Camel 2.3*
You can now use the `org.apache.camel.builder.XPathBuilder` without the
need for an Exchange. This comes handy if you want
@@ -346,7 +346,7 @@ String name = XPathBuilder.xpath("foo/bar").evaluate(context, "<foo><bar>cheese<
== Using Saxon with XPathBuilder
-*Available as of Camel 2.3*
+*Since Camel 2.3*
You need to add *camel-saxon* as dependency to your project.
@@ -361,7 +361,7 @@ The easy one
== Setting a custom XPathFactory using System Property
-*Available as of Camel 2.3*
+*Since Camel 2.3*
Camel now supports reading the
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/XPathFactory.html#newInstance(java.lang.String)[JVM
@@ -388,7 +388,7 @@ To use Apache Xerces you can configure the system property
== Enabling Saxon from Spring DSL
-*Available as of Camel 2.10*
+*Since Camel 2.10*
Similarly to Java DSL, to enable Saxon from Spring DSL you have three
options:
@@ -416,7 +416,7 @@ Shortcut
== Namespace auditing to aid debugging
-*Available as of Camel 2.10*
+*Since Camel 2.10*
A large number of XPath-related issues that users frequently face are
linked to the usage of namespaces. You may have some misalignment
@@ -510,7 +510,7 @@ xmlns:b=[http://apache.org/camelA, http://apache.org/camelB]}
== Loading script from external resource
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can externalize the script and have Camel load it from a resource
such as `"classpath:"`, `"file:"`, or `"http:"`. +
diff --git a/docs/components/modules/ROOT/pages/zipkin.adoc b/docs/components/modules/ROOT/pages/zipkin.adoc
index 929b791..05de410 100644
--- a/docs/components/modules/ROOT/pages/zipkin.adoc
+++ b/docs/components/modules/ROOT/pages/zipkin.adoc
@@ -2,7 +2,7 @@
= Zipkin Component
:page-source: components/camel-zipkin/src/main/docs/zipkin.adoc
-*Available as of Camel 2.18*
+*Since Camel 2.18*
The Camel Zipkin component is used for tracing and timing incoming and outgoing Camel messages using http://zipkin.io/[zipkin].
diff --git a/docs/user-manual/modules/ROOT/pages/async.adoc b/docs/user-manual/modules/ROOT/pages/async.adoc
index 9b87a32..d354ead 100644
--- a/docs/user-manual/modules/ROOT/pages/async.adoc
+++ b/docs/user-manual/modules/ROOT/pages/async.adoc
@@ -1,7 +1,7 @@
[[Async-Async]]
= Async
-*Available as of Camel 2.0*
+*Since Camel 2.0*
The asynchronous API in Camel has been rewritten for Camel 2.0, and the
information on this page applies for Camel 2.0 and later.
diff --git a/docs/user-manual/modules/ROOT/pages/asynchronous-routing-engine.adoc b/docs/user-manual/modules/ROOT/pages/asynchronous-routing-engine.adoc
index cced8eb..566df03 100644
--- a/docs/user-manual/modules/ROOT/pages/asynchronous-routing-engine.adoc
+++ b/docs/user-manual/modules/ROOT/pages/asynchronous-routing-engine.adoc
@@ -1,7 +1,7 @@
[[AsynchronousRoutingEngine-AsynchronousRoutingEngine]]
= Asynchronous Routing Engine
-*Available as of Camel 2.4*
+*Since Camel 2.4*
As of Camel 2.4 the asynchronous routing engine is back and kicking. +
All the xref:enterprise-integration-patterns.adoc[Enterprise Integration Patterns]
diff --git a/docs/user-manual/modules/ROOT/pages/backlog-tracer.adoc b/docs/user-manual/modules/ROOT/pages/backlog-tracer.adoc
index 4e6afd8..f0bc92c 100644
--- a/docs/user-manual/modules/ROOT/pages/backlog-tracer.adoc
+++ b/docs/user-manual/modules/ROOT/pages/backlog-tracer.adoc
@@ -1,7 +1,7 @@
[[BacklogTracer-BacklogTracerInterceptor]]
= BacklogTracer Interceptor
-*Available as of Camel 2.11*
+*Since Camel 2.11*
Camel supports a backlog tracer interceptor that is used for capturing a
trace message of each message as they are routed in Camel. +
diff --git a/docs/user-manual/modules/ROOT/pages/backlogdebugger.adoc b/docs/user-manual/modules/ROOT/pages/backlogdebugger.adoc
index 22be6e2..dea53b0 100644
--- a/docs/user-manual/modules/ROOT/pages/backlogdebugger.adoc
+++ b/docs/user-manual/modules/ROOT/pages/backlogdebugger.adoc
@@ -1,7 +1,7 @@
[[BacklogDebugger-BacklogDebugger]]
= BacklogDebugger
-*Available as of Camel 2.12*
+*Since Camel 2.12*
Camel supports a backlog debugger that is used for live debugging of
messages that are routed in Camel.
diff --git a/docs/user-manual/modules/ROOT/pages/batch-consumer.adoc b/docs/user-manual/modules/ROOT/pages/batch-consumer.adoc
index 5a4ba83..9596fb0 100644
--- a/docs/user-manual/modules/ROOT/pages/batch-consumer.adoc
+++ b/docs/user-manual/modules/ROOT/pages/batch-consumer.adoc
@@ -1,7 +1,7 @@
[[BatchConsumer-BatchConsumer]]
= Batch Consumer
-*Available as of Camel 2.0*
+*Since Camel 2.0*
Batch Consumer is basically a xref:polling-consumer.adoc[Polling
Consumer] that is capable of polling multiple
diff --git a/docs/user-manual/modules/ROOT/pages/bean-binding.adoc b/docs/user-manual/modules/ROOT/pages/bean-binding.adoc
index 9d0ed94..643b856 100644
--- a/docs/user-manual/modules/ROOT/pages/bean-binding.adoc
+++ b/docs/user-manual/modules/ROOT/pages/bean-binding.adoc
@@ -222,7 +222,7 @@ public class Bar {
[[BeanBinding-Parameterbindingusingmethodoption]]
== Parameter binding using method option
-*Available as of Camel 2.9*
+*Since Camel 2.9*
Camel uses the following rules to determine if it's a parameter value in
the method option
@@ -341,7 +341,7 @@ use `.to` instead as shown:
[[BeanBinding-Usingtypequalifierstoselectamongoverloadedmethods]]
== Using type qualifiers to select among overloaded methods
-*Available as of Camel 2.8*
+*Since Camel 2.8*
If you have a xref:bean-eip.adoc[Bean] with overloaded methods, you can now
specify parameter types in the method name so Camel can match the method
diff --git a/docs/user-manual/modules/ROOT/pages/clustering.adoc b/docs/user-manual/modules/ROOT/pages/clustering.adoc
index 888334e..fe286f2 100644
--- a/docs/user-manual/modules/ROOT/pages/clustering.adoc
+++ b/docs/user-manual/modules/ROOT/pages/clustering.adoc
@@ -1,7 +1,7 @@
[[Clustering-Clustering]]
= Clustering
-*Available as of Camel 2.20*
+*Since Camel 2.20*
[WARNING]
====
diff --git a/docs/user-manual/modules/ROOT/pages/configuring-route-startup-ordering-and-autostartup.adoc b/docs/user-manual/modules/ROOT/pages/configuring-route-startup-ordering-and-autostartup.adoc
index 6a2d820..a291184 100644
--- a/docs/user-manual/modules/ROOT/pages/configuring-route-startup-ordering-and-autostartup.adoc
+++ b/docs/user-manual/modules/ROOT/pages/configuring-route-startup-ordering-and-autostartup.adoc
@@ -1,7 +1,7 @@
[[Configuringroutestartuporderingandautostartup-Configuringroutesstartuporderingandautostartup]]
= Configuring routes startup ordering and autostartup
-*Available as of Camel 2.1*
+*Since Camel 2.1*
Camel now supports configuring two aspects:
@@ -87,7 +87,7 @@ from("activemq:queue:special").noAutoStartup().to("file://backup");
[[Configuringroutestartuporderingandautostartup-ConfiguringwhetherarouteshouldbestartedornotusingabooleanorStringinJavaDSL]]
== Configuring whether a route should be started or not, using a boolean or String, in Java DSL
-*Available as of Camel 2.9*
+*Since Camel 2.9*
To startup based on a boolean, String or
xref:components::properties-component.adoc[Property], do one of the following:
diff --git a/docs/user-manual/modules/ROOT/pages/content-enricher.adoc b/docs/user-manual/modules/ROOT/pages/content-enricher.adoc
index 6743b60..ac602a0 100644
--- a/docs/user-manual/modules/ROOT/pages/content-enricher.adoc
+++ b/docs/user-manual/modules/ROOT/pages/content-enricher.adoc
@@ -300,7 +300,7 @@ And for Spring DSL:
[[ContentEnricher-Usingdynamicuris]]
=== Using dynamic uris
-*Available as of Camel 2.16*
+*Since Camel 2.16*
From Camel 2.16 onwards enrich and pollEnrich supports using dynamic
uris computed based on information from the
@@ -487,7 +487,7 @@ For example to wait up to 5 seconds you can do:
[[ContentEnricher-Usingdynamicuris.1]]
==== Using dynamic uris
-*Available as of Camel 2.16*
+*Since Camel 2.16*
From Camel 2.16 onwards enrich and pollEnrich supports using dynamic
uris computed based on information from the
diff --git a/docs/user-manual/modules/ROOT/pages/dead-letter-channel.adoc b/docs/user-manual/modules/ROOT/pages/dead-letter-channel.adoc
index 0b61e3d..c61fcfd 100644
--- a/docs/user-manual/modules/ROOT/pages/dead-letter-channel.adoc
+++ b/docs/user-manual/modules/ROOT/pages/dead-letter-channel.adoc
@@ -296,7 +296,7 @@ Is this header is absent, normal redelivery rules apply.
[[deadLetterChannel-Whichendpointfailed]]
== Which endpoint failed
-*Available as of Camel 2.1*
+*Since Camel 2.1*
When Camel routes messages it will decorate the
xref:exchange.adoc[Exchange] with a property that contains the *last*
@@ -351,7 +351,7 @@ still contain the value of `\http://someserver/somepath`.
[[deadLetterChannel-OnPrepareFailure]]
== OnPrepareFailure
-*Available as of Camel 2.16*
+*Since Camel 2.16*
Before the exchange is sent to the dead letter queue, you can use
onPrepare to allow a custom `Processor` to prepare the exchange, such as
@@ -392,7 +392,7 @@ The onPrepare is also available using the default error handler.
[[deadLetterChannel-Whichroutefailed]]
== Which route failed
-*Available as of Camel 2.10.4/2.11*
+*Since Camel 2.10.4/2.11*
When Camel error handler handles an error such as
xref:dead-letter-channel.adoc[Dead Letter Channel] or using
@@ -415,7 +415,7 @@ letter queue and use that for error reporting.
[[deadLetterChannel-Controlifredeliveryisallowedduringstoppingshutdown]]
== Control if redelivery is allowed during stopping/shutdown
-*Available as of Camel 2.11*
+*Since Camel 2.11*
Prior to Camel 2.10, Camel will perform redelivery while stopping a
route, or shutting down Camel. This has improved a bit in Camel 2.10
diff --git a/docs/user-manual/modules/ROOT/pages/debugger.adoc b/docs/user-manual/modules/ROOT/pages/debugger.adoc
index 6f64c4b..191a9b6 100644
--- a/docs/user-manual/modules/ROOT/pages/debugger.adoc
+++ b/docs/user-manual/modules/ROOT/pages/debugger.adoc
@@ -1,7 +1,7 @@
[[Debugger-Debugger]]
= Debugger
-*Available as of Camel 2.6*
+*Since Camel 2.6*
Camel Debugger is much related to
Tracer, in fact they are sisters. Debugger is a
diff --git a/docs/user-manual/modules/ROOT/pages/exception-clause.adoc b/docs/user-manual/modules/ROOT/pages/exception-clause.adoc
index e434be0..6f32dcf 100644
--- a/docs/user-manual/modules/ROOT/pages/exception-clause.adoc
+++ b/docs/user-manual/modules/ROOT/pages/exception-clause.adoc
@@ -233,7 +233,7 @@ Will retry from *`processor2`* - not the complete route.
[[ExceptionClause-ReusingRedeliveryPolicy]]
== Reusing RedeliveryPolicy
-*Available as of Camel 1.5.1 or later*
+*Since Camel 1.5.1 or later*
You can reference a *`RedeliveryPolicy`* so you can reuse existing
configurations and use standard spring bean style configuration that
@@ -256,7 +256,7 @@ supports property placeholders.
[[ExceptionClause-AsynchronousDelayedRedelivery]]
== Asynchronous Delayed Redelivery
-*Available as of Camel 2.4*
+*Since Camel 2.4*
From *Camel 2.4*: Camel has a feature to *not block* while waiting for a
delayed redelivery to occur. However if you use transacted routes then
@@ -276,7 +276,7 @@ control pool settings.
[[ExceptionClause-CatchingMultipleExceptions]]
== Catching Multiple Exceptions
-*Available as of Camel 1.5*
+*Since Camel 1.5*
In Camel 1.5 the *exception* clauses has been renamed to *`onException`*
and it also supports multiple exception classes:
@@ -330,7 +330,7 @@ using a producer template from Exchange.
[[ExceptionClause-MarkingExceptionsasHandled]]
== Marking Exceptions as Handled
-*Available as of Camel 1.5*
+*Since Camel 1.5*
== Continued
@@ -425,7 +425,7 @@ message with the caused exception message:
[[ExceptionClause-HandleandContinueExceptions]]
== Handle and Continue Exceptions
-*Available as of Camel 2.3*
+*Since Camel 2.3*
In Camel 2.3 we introduced a new option `continued` which allows you to
both *`handle`* and *`continue`* routing in the original route as if the
@@ -622,7 +622,7 @@ that is selected.
[[ExceptionClause-UsingFineGrainedSelectionUsingonWhenPredicate]]
== Using Fine Grained Selection Using `onWhen` Predicate
-*Available as of Camel 1.5.1 or later*
+*Since Camel 1.5.1 or later*
You can attach an xref:expression.adoc[Expression] to the exception
clause to have fine grained control when a clause should be selected or
@@ -644,7 +644,7 @@ default error handler will kick in.
[[ExceptionClause-UsingonRedeliveryProcessor]]
== Using `onRedelivery` Processor
-*Available as of Camel 2.0*
+*Since Camel 2.0*
xref:dead-letter-channel.adoc[Dead Letter Channel] has support
for *`onRedelivery`* to allow custom processing of a Message before its
@@ -685,7 +685,7 @@ class as this code is based on unit testing):
[[ExceptionClause-UsingonExceptionOccurredProcessor]]
== Using `onExceptionOccurred` Processor
-*Available as of Camel 2.17*
+*Since Camel 2.17*
xref:dead-letter-channel.adoc[Dead Letter Channel] has support
for *`onExceptionOccurred`* to allow custom processing of a Message just
@@ -737,7 +737,7 @@ to refer to a spring bean id that is your custom processor:
[[ExceptionClause-UsingFineGrainedRetryUsingretryWhilePredicate]]
== Using Fine Grained Retry Using `retryWhile` Predicate
-*Available as of Camel 2.0*
+*Since Camel 2.0*
=== RetryUntil
diff --git a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-configure-endpoints.adoc b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-configure-endpoints.adoc
index e357e38..f630049 100644
--- a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-configure-endpoints.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-configure-endpoints.adoc
@@ -118,7 +118,7 @@ pop3://host:port?password=foo
[[HowdoIconfigureendpoints-ReferringbeansfromEndpointURIs]]
=== Referring beans from Endpoint URIs
-*Available as of Camel 2.0*
+*Since Camel 2.0*
When configuring endpoints using URI syntax you can now refer to beans
in the Registry using the `#` notation.
@@ -138,7 +138,7 @@ Registry.
[[HowdoIconfigureendpoints-Configuringparametervaluesusingrawvalues,egsuchaspasswords]]
=== Configuring parameter values using raw values, eg such as passwords
-*Available as of Camel 2.11*
+*Since Camel 2.11*
When configuring endpoint options using URI syntax, then the values is
by default URI encoded. This can be a problem if you want to configure
@@ -216,7 +216,7 @@ documentation.
[[HowdoIconfigureendpoints-Configuringurisusingendpointwithbeanpropertystyle]]
== Configuring URIs using endpoint with bean property style
-*Available as of Camel 2.15*
+*Since Camel 2.15*
Sometimes configuring endpoint URIs may have many options, and therefore
the URI can become long. In Java DSL you can break the URIs into new
@@ -266,7 +266,7 @@ as:
[[HowdoIconfigureendpoints-Configuringlongurisusingnewlines]]
== Configuring long URIs using new lines
-*Available as of Camel 2.15*
+*Since Camel 2.15*
Sometimes configuring endpoint URIs may have many options, and therefore
the URI can become long. In Java DSL you can break the URIs into new
diff --git a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-configure-the-default-maximum-cache-size-for-producercache-or-producertemplate.adoc b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-configure-the-default-maximum-cache-size-for-producercache-or-producertemplate.adoc
index 4fd5f29..79d05ea 100644
--- a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-configure-the-default-maximum-cache-size-for-producercache-or-producertemplate.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-configure-the-default-maximum-cache-size-for-producercache-or-producertemplate.adoc
@@ -1,7 +1,7 @@
[[HowdoIconfigurethedefaultmaximumcachesizeforProducerCacheorProducerTemplate-HowdoIconfigurethedefaultmaximumcachesizeforProducerCacheorProducerTemplate]]
= How do I configure the default maximum cache size for ProducerCache or ProducerTemplate?
-*Available as of Camel 2.3*
+*Since Camel 2.3*
This applies to ConsumerCache and ConsumerTemplate as well.
diff --git a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-configure-the-maximum-endpoint-cache-size-for-camelcontext.adoc b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-configure-the-maximum-endpoint-cache-size-for-camelcontext.adoc
index cae163c..fe93983 100644
--- a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-configure-the-maximum-endpoint-cache-size-for-camelcontext.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-configure-the-maximum-endpoint-cache-size-for-camelcontext.adoc
@@ -7,7 +7,7 @@ used endpoints (based on a LRUCache).
[[HowdoIconfigurethemaximumendpointcachesizeforCamelContext-Configuringcachesize]]
== Configuring cache size
-*Available as of Camel 2.8*
+*Since Camel 2.8*
You can configure the default maximum cache size by setting the
`Exchange.MAXIMUM_ENDPOINT_CACHE_SIZE` property on
diff --git a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-enable-streams-when-debug-logging-messages-in-camel.adoc b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-enable-streams-when-debug-logging-messages-in-camel.adoc
index b41fcb9..fee776d 100644
--- a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-enable-streams-when-debug-logging-messages-in-camel.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-enable-streams-when-debug-logging-messages-in-camel.adoc
@@ -1,7 +1,7 @@
[[HowdoIenablestreamswhendebugloggingmessagesinCamel-HowdoIenablestreamswhendebugloggingmessagesinCamel]]
= How do I enable streams when debug logging messages in Camel
-*Available as of Camel 2.1*
+*Since Camel 2.1*
When you run Camel with `DEBUG` level as logging, it will log the
messages and its content from time to time.
diff --git a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-import-rests-from-other-xml-files.adoc b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-import-rests-from-other-xml-files.adoc
index d75db6f..b22ce8a 100644
--- a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-import-rests-from-other-xml-files.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-import-rests-from-other-xml-files.adoc
@@ -1,7 +1,7 @@
[[HowdoIimportrestsfromotherXMLfiles-HowdoIimportrestsfromotherXMLfiles]]
= How do I import rests from other XML files?
-*Available as of Camel 2.14*
+*Since Camel 2.14*
When defining rests in Camel using xref:xml-configuration.adoc[Xml
Configuration] you may want to define some rests in other XML files. For
diff --git a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-import-routes-from-other-xml-files.adoc b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-import-routes-from-other-xml-files.adoc
index 2a0205d..8c82dd2 100644
--- a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-import-routes-from-other-xml-files.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-import-routes-from-other-xml-files.adoc
@@ -1,7 +1,7 @@
[[HowDoIImportRoutesFromOtherXMLFiles-HowDoIImportRoutesFromOtherXMLFiles]]
= How Do I Import Routes From Other XML Files?
-*Available as of Camel 2.3*
+*Since Camel 2.3*
When defining routes in Camel using xref:xml-configuration.adoc[XML Configuration]
you may want to define some routes in other XML files.
diff --git a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-run-activemq-and-camel-in-jboss.adoc b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-run-activemq-and-camel-in-jboss.adoc
index c261992..1629992 100644
--- a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-run-activemq-and-camel-in-jboss.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-run-activemq-and-camel-in-jboss.adoc
@@ -9,7 +9,7 @@ solution here].
[[HowdoIrunActiveMQandCamelinJBoss-UsingCamelinJBoss]]
== Using Camel in JBoss
-*Available as of Camel 2.1*
+*Since Camel 2.1*
We have now created a https://github.com/camel-extra/camel-extra/blob/master/components/camel-jboss/src/main/docs/jboss-component.adoc[camel-jboss] component which
allows you to run Camel inside JBoss. Unfortunately JBoss uses LGPL
diff --git a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc
index 92ad4f5..9afa828 100644
--- a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc
@@ -1,7 +1,7 @@
[[HowdoIsetthemaxcharswhendebugloggingmessagesinCamel-HowdoIsetthemaxcharswhendebugloggingmessagesinCamel]]
= How do I set the max chars when debug logging messages in Camel?
-*Available as of Camel 2.0*
+*Since Camel 2.0*
When you run Camel with logging, it will log the messages and its
content from time to time.
diff --git a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc
index aaea13b..44f7afa 100644
--- a/docs/user-manual/modules/ROOT/pages/faq/how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq/how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc
@@ -1,7 +1,7 @@
[[HowdoIspecifytimeperiodinahumanfriendlysyntax-HowdoIspecifytimeperiodinahumanfriendlysyntax]]
= How do I specify time period in a human friendly syntax?
-*Available as of Camel 2.3*
+*Since Camel 2.3*
Some of the Camel xref:component.adoc[components] offers options to
specify a time period, which must be entered in milli second as unit.
diff --git a/docs/user-manual/modules/ROOT/pages/faq/why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc b/docs/user-manual/modules/ROOT/pages/faq/why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc
index 6cdbc6d..7c22202 100644
--- a/docs/user-manual/modules/ROOT/pages/faq/why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq/why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc
@@ -85,7 +85,7 @@ xref:split-eip.adoc[Splitter] EIP has a sub-route which denotes the
routing of each splitted message. You would also have to use
`.endChoice()` to indicate the end of the sub-route and to return back
to the xref:content-based-router-eip.adoc[Content Based Router]. Note
-`.endChoice()` is *available as of Camel 2.7*.
+`.endChoice()` is *Since Camel 2.7*.
[[WhycanInotusewhenorotherwiseinaJavaCamelroute-Stillproblems]]
== Still problems
diff --git a/docs/user-manual/modules/ROOT/pages/graceful-shutdown.adoc b/docs/user-manual/modules/ROOT/pages/graceful-shutdown.adoc
index 31e7564..270cb8c 100644
--- a/docs/user-manual/modules/ROOT/pages/graceful-shutdown.adoc
+++ b/docs/user-manual/modules/ROOT/pages/graceful-shutdown.adoc
@@ -1,7 +1,7 @@
[[GracefulShutdown-GracefulShutdown]]
= Graceful Shutdown
-*Available as of Camel 2.2*
+*Since Camel 2.2*
Camel now supports a pluggable shutdown strategy using
`org.apache.camel.spi.ShutdownStrategy`. Its responsible for shutting
@@ -64,7 +64,7 @@ processed before it can shutdown.
== Suppressing logging due to timeout not allowing all inflight messages to complete
-*Available as of Camel 2.12*
+*Since Camel 2.12*
If a graceful shutdown could not shutdown cleanly within the given
timeout period, then Camel performs a more aggressive shutdown by
@@ -88,7 +88,7 @@ control.
[[GracefulShutdown-Logginginflightexchangeinformationontimeout]]
== Logging inflight exchange information on timeout
-*Available as of Camel 2.15*
+*Since Camel 2.15*
If a graceful shutdown could not shutdown cleanly within the given
timeout period, then Camel performs a more aggressive shutdown by
@@ -378,7 +378,7 @@ JMX console. For example you can change the timeout value.
[[GracefulShutdown-Shuttingdownindividualroutes]]
== Shutting down individual routes
-*Available as of Camel 2.3*
+*Since Camel 2.3*
Its now possible to gracefully shutdown an individual route using
`shutdownRoute(routeId)` method on `CamelContext`. Its also possible to
provide a specific timeout to use instead of the default timeout
diff --git a/docs/user-manual/modules/ROOT/pages/health-check.adoc b/docs/user-manual/modules/ROOT/pages/health-check.adoc
index aa7e003..84a160d 100644
--- a/docs/user-manual/modules/ROOT/pages/health-check.adoc
+++ b/docs/user-manual/modules/ROOT/pages/health-check.adoc
@@ -1,7 +1,7 @@
[[HealthCheck-HealthCheck]]
= Health Checks
-*Available as of Camel 2.20*
+*Since Camel 2.20*
Camel provides support to probe the state of an integration via a pluggable Health Check strategy based on the following concepts:
diff --git a/docs/user-manual/modules/ROOT/pages/http-session-handling.adoc b/docs/user-manual/modules/ROOT/pages/http-session-handling.adoc
index a63bbd8..afe1312 100644
--- a/docs/user-manual/modules/ROOT/pages/http-session-handling.adoc
+++ b/docs/user-manual/modules/ROOT/pages/http-session-handling.adoc
@@ -1,7 +1,7 @@
[[HTTP-SessionHandling]]
= HTTP Session Handling
-*Available as of Camel 2.19*
+*Since Camel 2.19*
Several Camel components can use HTTP as the underlying transport
protocol. In general HTTP calls are stateless in nature, however some
diff --git a/docs/user-manual/modules/ROOT/pages/java-dsl.adoc b/docs/user-manual/modules/ROOT/pages/java-dsl.adoc
index 47fd261..e2a28aa 100644
--- a/docs/user-manual/modules/ROOT/pages/java-dsl.adoc
+++ b/docs/user-manual/modules/ROOT/pages/java-dsl.adoc
@@ -87,7 +87,7 @@ endpoints together.
[[JavaDSL-URIStringformatting]]
== URI String formatting
-*Available as of Camel 2.0*
+*Since Camel 2.0*
If you have endpoint URIs that accept options and you want to be able to
substitute the value, e.g. build the URI by concat the strings together,
diff --git a/docs/user-manual/modules/ROOT/pages/jmx.adoc b/docs/user-manual/modules/ROOT/pages/jmx.adoc
index 34c854c..fa3e6e4 100644
--- a/docs/user-manual/modules/ROOT/pages/jmx.adoc
+++ b/docs/user-manual/modules/ROOT/pages/jmx.adoc
@@ -455,7 +455,7 @@ usage of each incoming and outgoing endpoints).
== Configuring whether to register MBeans always, for new routes or just by default
-*Available as of Camel 2.7*
+*Since Camel 2.7*
Camel now offers 2 settings to control whether or not to register mbeans
@@ -578,7 +578,7 @@ image::jconsole_trace_notifications.png[image]
== Registering your own Managed Endpoints
-*Available as of Camel 2.0* +
+*Since Camel 2.0* +
You can decorate your own endpoints with Spring managed annotations
`@ManagedResource` to allow to register them in the Camel `MBeanServer`
and thus access your custom MBeans using JMX.
@@ -633,7 +633,7 @@ code to not depend on Spring JARs.
== Programming your own Managed Services
-*Available as of Camel 2.1*
+*Since Camel 2.1*
Camel now offers to use your own MBeans when registering services for
management. What that means is for example you can develop a custom
@@ -687,7 +687,7 @@ And in the future we will add additional wrappers for more EIP patterns.
== ManagementObjectNameStrategy
-*Available as of Camel 2.1*
+*Since Camel 2.1*
Camel provides a pluggable API for naming strategy by
`org.apache.camel.spi.ManagementObjectNameStrategy`. A default
@@ -696,7 +696,7 @@ registered with.
== Management naming pattern
-*Available as of Camel 2.10*
+*Since Camel 2.10*
From *Camel 2.10* onwards we made it easier to configure a naming
pattern for the MBeans. The pattern is used as part of the `ObjectName`
@@ -838,7 +838,7 @@ MBean already exists exception.
== ManagementStrategy
-*Available as of Camel 2.1*
+*Since Camel 2.1*
Camel now provides a totally pluggable management strategy that allows
you to be 100% in control of management. It is a rich interface with
@@ -851,7 +851,7 @@ details and features that are provided out of the box at Apache.
== Configuring level of granularity for performance statistics
-*Available as of Camel 2.1*
+*Since Camel 2.1*
You can now set a pre set level whether performance statistics is
enabled or not when Camel start ups. The levels are
@@ -912,7 +912,7 @@ And from Spring DSL you do:
== Hiding sensitive information
-*Available as of Camel 2.12*
+*Since Camel 2.12*
By default, Camel enlists MBeans in JMX such as endpoints configured
using URIs. In this configuration, there may be
diff --git a/docs/user-manual/modules/ROOT/pages/json.adoc b/docs/user-manual/modules/ROOT/pages/json.adoc
index 0aaa46c..90d29c7 100644
--- a/docs/user-manual/modules/ROOT/pages/json.adoc
+++ b/docs/user-manual/modules/ROOT/pages/json.adoc
@@ -121,7 +121,7 @@ marshalling to JSON.
[[JSON-Configuringfieldnamingpolicy]]
== Configuring field naming policy
-*Available as of Camel 2.11*
+*Since Camel 2.11*
The GSON library supports specifying policies and strategies for mapping
from json to POJO fields. A common naming convention is to map json
@@ -222,7 +222,7 @@ And use it in Camel routes by referring to its bean id as shown:
[[JSON-IncludeExcludefieldsusingthejsonViewattributewithJacksonDataFormat]]
== Include/Exclude fields using the `jsonView` attribute with `JacksonDataFormat`
-*Available as of Camel 2.12*
+*Since Camel 2.12*
As an example of using this attribute you can instead of:
@@ -255,7 +255,7 @@ And the same in XML DSL:
[[JSON-SettingserializationincludeoptionforJacksonmarshal]]
== Setting serialization include option for Jackson marshal
-*Available as of Camel 2.13.3/2.14*
+*Since Camel 2.13.3/2.14*
If you want to marshal a pojo to JSON, and the pojo has some fields with
null values. And you want to skip these null values, then you need to
@@ -291,7 +291,7 @@ Or from XML DSL you configure this as
[[JSON-UnmarshallingfromjsontoPOJOwithdynamicclassname]]
== Unmarshalling from json to POJO with dynamic class name
-*Available as of Camel 2.14*
+*Since Camel 2.14*
If you use jackson to unmarshal json to POJO, then you can now specify a
header in the message that indicate which class name to unmarshal to. +
@@ -322,7 +322,7 @@ Or from XML DSL you configure this as
[[JSON-UnmarshallingfromjsontoListMaporListpojo]]
== Unmarshalling from json to List<Map> or List<pojo>
-*Available as of Camel 2.14*
+*Since Camel 2.14*
If you are using Jackson to unmarshal json to a list of map/pojo, you
can now specify this by setting `useList="true"` or use
@@ -361,7 +361,7 @@ And you can specify the pojo type also
[[JSON-UsingcustomJacksonObjectMapper]]
== Using custom Jackson ObjectMapper
-*Available as of Camel 2.17*
+*Since Camel 2.17*
You can use custom Jackson ObjectMapper instance, can be configured as
shown below.
@@ -379,7 +379,7 @@ in the Registry
[[JSON-UsingcustomJacksonmodules]]
== Using custom Jackson modules
-*Available as of Camel 2.15*
+*Since Camel 2.15*
You can use custom Jackson modules by specifying the class names of
those using the moduleClassNames option as shown below.
@@ -414,7 +414,7 @@ moduleRefs="myJacksonModule,myOtherModule"
[[JSON-EnablingordisablefeaturesusingJackson]]
== Enabling or disable features using Jackson
-*Available as of Camel 2.15*
+*Since Camel 2.15*
Jackson has a number of features you can enable or disable, which its
ObjectMapper uses. For example to disable failing on unknown properties
@@ -472,7 +472,7 @@ Otherwise the default mapper will be used.
[[JSON-FormattedJSONmarshalling-pretty-printing]]
== Formatted JSON marshalling (pretty-printing)
-*Available as of Camel 2.16*
+*Since Camel 2.16*
Using the `prettyPrint` option one can output a well formatted JSON
while marshalling:
@@ -509,7 +509,7 @@ combination with other settings for `JsonLibrary`, `unmarshalType`,
[[JSON.1]]
-*Available as of Camel 2.17*
+*Since Camel 2.17*
The `camel-jackson` module allows to integrate Jackson as
a Type Converter in the Camel registry. This
diff --git a/docs/user-manual/modules/ROOT/pages/oncompletion.adoc b/docs/user-manual/modules/ROOT/pages/oncompletion.adoc
index 2347014..6f6638d 100644
--- a/docs/user-manual/modules/ROOT/pages/oncompletion.adoc
+++ b/docs/user-manual/modules/ROOT/pages/oncompletion.adoc
@@ -231,7 +231,7 @@ from("direct:start")
[[OnCompletion-UsingonCompletionwithorwithoutthreadpool]]
== Using onCompletion with or without thread pool
-*Available as of Camel 2.14*
+*Since Camel 2.14*
OnCompletion will from Camel 2.14 onwards not use thread pool by
default. To use thread pool then either set a `executorService` or set
@@ -275,7 +275,7 @@ to be used, using the executorServiceRef option
[[OnCompletion-UsingonCompletiontorunbeforerouteconsumersendsbackresponsetocallee]]
== Using onCompletion to run before route consumer sends back response to callee
-*Available as of Camel 2.14*
+*Since Camel 2.14*
OnCompletion supports two modes
diff --git a/docs/user-manual/modules/ROOT/pages/pojo-consuming.adoc b/docs/user-manual/modules/ROOT/pages/pojo-consuming.adoc
index af75ae1..346dafb 100644
--- a/docs/user-manual/modules/ROOT/pages/pojo-consuming.adoc
+++ b/docs/user-manual/modules/ROOT/pages/pojo-consuming.adoc
@@ -99,7 +99,7 @@ from(uri).to("bean:myBean?method=methodName");
[[POJOConsuming-Usingapropertytodefinetheendpoint]]
== Using a property to define the endpoint
-*Available as of Camel 2.11*
+*Since Camel 2.11*
The following annotations @Consume, @Produce, @EndpointInject, now
offers a `property` attribute you can use to define the endpoint as a
diff --git a/docs/user-manual/modules/ROOT/pages/polling-consumer.adoc b/docs/user-manual/modules/ROOT/pages/polling-consumer.adoc
index eb85f56..fd28244 100644
--- a/docs/user-manual/modules/ROOT/pages/polling-consumer.adoc
+++ b/docs/user-manual/modules/ROOT/pages/polling-consumer.adoc
@@ -280,7 +280,7 @@ From *Camel 2.8*: the default value is *`true`*.
[[PollingConsumer-UsingbackofftoLettheSchedulerbeLessAggressive]]
=== Using `backoff` to Let the Scheduler be Less Aggressive
-*Available as of Camel 2.12*
+*Since Camel 2.12*
The scheduled xref:polling-consumer.adoc[Polling Consumer] is by default
static by using the same poll frequency whether or not there is messages
@@ -332,7 +332,7 @@ the endpoint successfully.
[[PollingConsumer-UsingaCustomScheduler]]
=== Using a Custom Scheduler
-*Available as of Camel 2.12:*
+*Since Camel 2.12:*
The SPI interface
*`org.apache.camel.spi.ScheduledPollConsumerScheduler`* allows to
diff --git a/docs/user-manual/modules/ROOT/pages/producertemplate.adoc b/docs/user-manual/modules/ROOT/pages/producertemplate.adoc
index 778dd4e..8de11d0 100644
--- a/docs/user-manual/modules/ROOT/pages/producertemplate.adoc
+++ b/docs/user-manual/modules/ROOT/pages/producertemplate.adoc
@@ -56,7 +56,7 @@ String ret = template.requestBody("cxf:bean:HelloWorldService", "<hello/>", Stri
[[ProducerTemplate-Fluentinterface]]
== Fluent interface
-*Available as of Camel 2.18.0*
+*Since Camel 2.18.0*
The FluentProducerTemplate provides a fluent syntax to
ProducerTemplate.
diff --git a/docs/user-manual/modules/ROOT/pages/rest-dsl.adoc b/docs/user-manual/modules/ROOT/pages/rest-dsl.adoc
index 5f6ac01..e3117b4 100644
--- a/docs/user-manual/modules/ROOT/pages/rest-dsl.adoc
+++ b/docs/user-manual/modules/ROOT/pages/rest-dsl.adoc
@@ -182,7 +182,7 @@ For example:
== Using Dynamic To in Rest DSL
-*Available as of Camel 2.16*
+*Since Camel 2.16*
The Rest DSL supports the new .toD <toD> as dynamic
to in the rest-dsl. For example to do a request/reply
@@ -638,7 +638,7 @@ example configure 2 component options, and 3 endpoint options etc.
== Enabling or disabling Jackson JSON features
-*Available as of Camel 2.15*
+*Since Camel 2.15*
When using JSON binding you may want to turn specific Jackson features
on or off. For example to disable failing on unknown properties (eg json
@@ -688,7 +688,7 @@ The rest configuration is of course also possible using XML DSL
== Default CORS headers
-*Available as of Camel 2.14.1*
+*Since Camel 2.14.1*
If CORS is enabled then the follow headers is in use by default. You can
configure custom CORS headers which takes precedence over the default
diff --git a/docs/user-manual/modules/ROOT/pages/route-policy.adoc b/docs/user-manual/modules/ROOT/pages/route-policy.adoc
index f64ba37..3c77f40 100644
--- a/docs/user-manual/modules/ROOT/pages/route-policy.adoc
+++ b/docs/user-manual/modules/ROOT/pages/route-policy.adoc
@@ -1,6 +1,6 @@
= RoutePolicy
-*Available as of Camel 2.1*
+*Since Camel 2.1*
A route policy *`org.apache.camel.spi.RoutePolicy`* is used to control
route(s) at runtime. For example you can use it to determine whether a
diff --git a/docs/user-manual/modules/ROOT/pages/routes.adoc b/docs/user-manual/modules/ROOT/pages/routes.adoc
index 392ea15..fd36c68 100644
--- a/docs/user-manual/modules/ROOT/pages/routes.adoc
+++ b/docs/user-manual/modules/ROOT/pages/routes.adoc
@@ -19,7 +19,7 @@ As you can see from the above Camel uses URIs to wire endpoints together.
[[Routes-URI-String-Formatting]]
== URI String formatting
-Available as of Camel 2.0
+Since Camel 2.0
If you have endpoint URIs that accept options and you want to be able to substitute the value, e.g. build the URI by concat the strings together, then you can use the java.lang.String.format method. But in Camel 2.0 we have added two convenient methods in the Java DSL so you can do fromF and toF that uses String formatting to build the URI.
diff --git a/docs/user-manual/modules/ROOT/pages/scripting-languages.adoc b/docs/user-manual/modules/ROOT/pages/scripting-languages.adoc
index 08375fd..dc631d3 100644
--- a/docs/user-manual/modules/ROOT/pages/scripting-languages.adoc
+++ b/docs/user-manual/modules/ROOT/pages/scripting-languages.adoc
@@ -73,7 +73,7 @@ languages with explicit DSL support.
[[ScriptingLanguages-AdditionalargumentstoScriptingEngine]]
== Additional arguments to ScriptingEngine
-*Available as of Camel 2.8*
+*Since Camel 2.8*
You can provide additional arguments to the `ScriptingEngine` using a
header on the Camel message with the key `CamelScriptArguments`.
@@ -82,7 +82,7 @@ See this example:
[[ScriptingLanguages-Usingpropertiesfunction]]
== Using properties function
-*Available as of Camel 2.9*
+*Since Camel 2.9*
If you need to use the xref:components::properties-component.adoc[Properties] component from a
script to lookup property placeholders, then its a bit cumbersome to do
@@ -105,7 +105,7 @@ same example is simpler:
[[ScriptingLanguages-Loadingscriptfromexternalresource]]
== Loading script from external resource
-*Available as of Camel 2.11*
+*Since Camel 2.11*
You can externalize the script and have Camel load it from a resource
such as `"classpath:"`, `"file:"`, or `"http:"`. +
@@ -120,7 +120,7 @@ eg to refer to a file on the classpath you can do:
[[ScriptingLanguages-Howtogettheresultfrommultiplestatementsscript]]
== How to get the result from multiple statements script
-*Available as of Camel 2.14*
+*Since Camel 2.14*
As the scripteengine evale method just return a Null if it runs a
multiple statments script. Camel now look up the value of script result
diff --git a/docs/user-manual/modules/ROOT/pages/security.adoc b/docs/user-manual/modules/ROOT/pages/security.adoc
index d08946e..40b84dd 100644
--- a/docs/user-manual/modules/ROOT/pages/security.adoc
+++ b/docs/user-manual/modules/ROOT/pages/security.adoc
@@ -74,7 +74,7 @@ broker communication
[[Security-ConfigurationSecurity]]
== Configuration Security
-*Available as of Camel 2.5*
+*Since Camel 2.5*
Camel offers the xref:components::properties-component.adoc[Properties] component to
externalize configuration values to properties files. Those values could
@@ -83,7 +83,7 @@ values can be encrypted and automatic decrypted by Camel.
* xref:components::jasypt.adoc[Jasypt]
-*Available as of Camel 2.8*
+*Since Camel 2.8*
Camel offers the xref:camel-configuration-utilities.adoc[JSSE Utility]
for configuring SSL/TLS related aspects of a number of Camel components.
diff --git a/docs/user-manual/modules/ROOT/pages/service-registry.adoc b/docs/user-manual/modules/ROOT/pages/service-registry.adoc
index a0781a2..62cacbd 100644
--- a/docs/user-manual/modules/ROOT/pages/service-registry.adoc
+++ b/docs/user-manual/modules/ROOT/pages/service-registry.adoc
@@ -1,7 +1,7 @@
[[ServiceRegistry-ServiceRegistry]]
= Service Registry
-*Available as of Camel 2.22*
+*Since Camel 2.22*
[WARNING]
====
diff --git a/docs/user-manual/modules/ROOT/pages/servicepool.adoc b/docs/user-manual/modules/ROOT/pages/servicepool.adoc
index eaf8627..5fbb9aa 100644
--- a/docs/user-manual/modules/ROOT/pages/servicepool.adoc
+++ b/docs/user-manual/modules/ROOT/pages/servicepool.adoc
@@ -1,7 +1,7 @@
[[ServicePool-ServicePool]]
= Service Pool
-*Available as of Camel 2.0*
+*Since Camel 2.0*
Camel supports pluggable pools for services. At this time of write we
have pools for:
diff --git a/docs/user-manual/modules/ROOT/pages/servlet-tomcat-example.adoc b/docs/user-manual/modules/ROOT/pages/servlet-tomcat-example.adoc
index 4f429aa..db3241c 100644
--- a/docs/user-manual/modules/ROOT/pages/servlet-tomcat-example.adoc
+++ b/docs/user-manual/modules/ROOT/pages/servlet-tomcat-example.adoc
@@ -1,7 +1,7 @@
[[ServletTomcatExample-ServletTomcatExample]]
= Servlet Tomcat Example
-*Available as of Camel 2.7*
+*Since Camel 2.7*
This example is located in the
https://github.com/apache/camel/blob/master/examples/camel-example-servlet-tomcat[examples/camel-example-servlet-tomcat]
diff --git a/docs/user-manual/modules/ROOT/pages/spring-remoting.adoc b/docs/user-manual/modules/ROOT/pages/spring-remoting.adoc
index 54ab8cb..6b6962e 100644
--- a/docs/user-manual/modules/ROOT/pages/spring-remoting.adoc
+++ b/docs/user-manual/modules/ROOT/pages/spring-remoting.adoc
@@ -342,7 +342,7 @@ public class Bar {
[[SpringRemoting-Parameterbindingusingmethodoption]]
=== Parameter binding using method option
-*Available as of Camel 2.9*
+*Since Camel 2.9*
Camel uses the following rules to determine if it's a parameter value in
the method option
@@ -463,7 +463,7 @@ use `.to` instead as shown:
[[SpringRemoting-Usingtypequalifierstoselectamongoverloadedmethods]]
=== Using type qualifiers to select among overloaded methods
-*Available as of Camel 2.8*
+*Since Camel 2.8*
If you have a xref:bean-eip.adoc[Bean] with overloaded methods, you can now
specify parameter types in the method name so Camel can match the method
diff --git a/docs/user-manual/modules/ROOT/pages/spring.adoc b/docs/user-manual/modules/ROOT/pages/spring.adoc
index 59252c1..81cdbca 100644
--- a/docs/user-manual/modules/ROOT/pages/spring.adoc
+++ b/docs/user-manual/modules/ROOT/pages/spring.adoc
@@ -148,7 +148,7 @@ For example:
== Using `contextScan`
-*Available as of Camel 2.4*
+*Since Camel 2.4*
You can allow Camel to scan the container context, e.g. the Spring ApplicationContext for route builder instances. This allow you to use the Spring *<component-scan>* feature and have Camel pickup any *`RouteBuilder`* instances which was created by Spring in its scan process.
diff --git a/docs/user-manual/modules/ROOT/pages/stream-caching.adoc b/docs/user-manual/modules/ROOT/pages/stream-caching.adoc
index 28e3897..721c3ba 100644
--- a/docs/user-manual/modules/ROOT/pages/stream-caching.adoc
+++ b/docs/user-manual/modules/ROOT/pages/stream-caching.adoc
@@ -194,7 +194,7 @@ And in XML you do:
[[Streamcaching-UsingStreamCachingStrategy]]
== Using StreamCachingStrategy
-*Available as of Camel 2.12*
+*Since Camel 2.12*
Stream caching is from Camel 2.12 onwards intended to be configured using `org.apache.camel.spi.StreamCachingStrategy`.
The old kind of configuration using properties on the xref:camelcontext.adoc[CamelContext] has been marked as deprecated.
diff --git a/docs/user-manual/modules/ROOT/pages/threading-model.adoc b/docs/user-manual/modules/ROOT/pages/threading-model.adoc
index 4db3c69..8c2d1ce 100644
--- a/docs/user-manual/modules/ROOT/pages/threading-model.adoc
+++ b/docs/user-manual/modules/ROOT/pages/threading-model.adoc
@@ -1,7 +1,7 @@
[[ThreadingModel-ThreadingModel]]
= Threading Model
-*Available as of Camel 2.3*
+*Since Camel 2.3*
The threading model in Camel is based on leveraging the JDK concurrency
API which provides thread pools, named `ExecutorService`.
@@ -102,7 +102,7 @@ them in JConsole under the `threadpools` category.
[[ThreadingModel-ExecutorServiceStrategy]]
== ExecutorServiceStrategy
-*Available as of Camel 2.3 to 2.8.x* +
+*Since Camel 2.3 to 2.8.x* +
Camel provides a pluggable strategy to hook in your own thread pool
provider, for example from a WorkManager in a J2EE server etc. +
See the `org.apache.camel.spi.ExecutorServiceStrategy` interface which
@@ -118,7 +118,7 @@ getter/setter.
[[ThreadingModel-ExecutorServiceManager]]
== ExecutorServiceManager
-*Available as of Camel 2.9*
+*Since Camel 2.9*
In camel 2.9.0 the `ExecutorServiceManager` replaces the
`ExecutorServiceStrategy`. It is renamed to manager as is not only
diff --git a/docs/user-manual/modules/ROOT/pages/transactional-client.adoc b/docs/user-manual/modules/ROOT/pages/transactional-client.adoc
index a654702..d299d2f 100644
--- a/docs/user-manual/modules/ROOT/pages/transactional-client.adoc
+++ b/docs/user-manual/modules/ROOT/pages/transactional-client.adoc
@@ -328,7 +328,7 @@ parts that cause separate threads to avoid this issue.
[[TransactionalClient-Usingmultiplerouteswithdifferentpropagationbehaviors]]
== Using multiple routes with different propagation behaviors
-*Available as of Camel 2.2*
+*Since Camel 2.2*
Suppose you want to route a message through two routes and by which the
2nd route should run in its own transaction. How do you do that? You use
diff --git a/docs/user-manual/modules/ROOT/pages/transactionerrorhandler.adoc b/docs/user-manual/modules/ROOT/pages/transactionerrorhandler.adoc
index 976bde7..2b1f276 100644
--- a/docs/user-manual/modules/ROOT/pages/transactionerrorhandler.adoc
+++ b/docs/user-manual/modules/ROOT/pages/transactionerrorhandler.adoc
@@ -1,7 +1,7 @@
[[TransactionErrorHandler-TransactionErrorHandler]]
= TransactionErrorHandler
-*Available as of Camel 2.0*
+*Since Camel 2.0*
This is the new default transaction error handler in Camel 2.0 onwards,
used for transacted routes.
diff --git a/docs/user-manual/modules/ROOT/pages/transformer.adoc b/docs/user-manual/modules/ROOT/pages/transformer.adoc
index cc981de..f3e5f5d 100644
--- a/docs/user-manual/modules/ROOT/pages/transformer.adoc
+++ b/docs/user-manual/modules/ROOT/pages/transformer.adoc
@@ -1,7 +1,7 @@
[[Transformer-Transformer]]
= Transformer
-*Available as of Camel 2.19*
+*Since Camel 2.19*
Transformer performs declarative transformation of the message according
to the declared `Input Type` and/or `Output Type` on a route definition which declares
diff --git a/docs/user-manual/modules/ROOT/pages/using-osgi-blueprint-with-camel.adoc b/docs/user-manual/modules/ROOT/pages/using-osgi-blueprint-with-camel.adoc
index 8b58b8f..5ee5a5b 100644
--- a/docs/user-manual/modules/ROOT/pages/using-osgi-blueprint-with-camel.adoc
+++ b/docs/user-manual/modules/ROOT/pages/using-osgi-blueprint-with-camel.adoc
@@ -1,7 +1,7 @@
[[UsingOSGiblueprintwithCamel-UsingOSGiblueprintwithCamel]]
= Using OSGi blueprint with Camel
-*Available as of Camel 2.4*
+*Since Camel 2.4*
A custom XML namespace for Blueprint has been created to let you
leverage the nice XML dialect. Given Blueprint custom namespaces are not
diff --git a/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc b/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
index a4cd784..cc8fabe 100644
--- a/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
+++ b/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
@@ -1,7 +1,7 @@
[[UsingPropertyPlaceholder-UsingPropertyPlaceholder]]
= Using `PropertyPlaceholder`
-*Available as of Camel 2.3*
+*Since Camel 2.3*
Camel now provides a new `PropertiesComponent` in `camel-core` which
allows you to use property placeholders when defining Camel
@@ -116,7 +116,7 @@ pc.setLocations("com/mycompany/override.properties;optional=true,com/mycompany/d
[[UsingPropertyPlaceholder-UsingSystemandEnvironmentVariablesinLocations]]
== Using System and Environment Variables in Locations
-*Available as of Camel 2.7*
+*Since Camel 2.7*
The location now supports using placeholders for JVM system properties
and OS environments variables.
@@ -202,7 +202,7 @@ option both inside the Spring as well as the Blueprint XML.
[[UsingPropertyPlaceholder-UsingaPropertiesfromthe]]
== Using a Properties from the xref:registry.adoc[Registry]
-*Available as of Camel 2.4*
+*Since Camel 2.4*
For example in OSGi you may want to expose a service which returns the
properties as a `java.util.Properties` object.
@@ -370,7 +370,7 @@ Example using property placeholders in the attributes of `<camelContext>`:
[[UsingPropertyPlaceholder-UsingPropertyPlaceholdersforAnyKindofAttributeintheXMLDSL]]
== Using Property Placeholders for Any Kind of Attribute in the XML DSL
-*Available as of Camel 2.7*
+*Since Camel 2.7*
If you use OSGi Blueprint then this only works from *2.11.1* or *2.10.5*
on.
@@ -424,7 +424,7 @@ stop=true
[[UsingPropertyPlaceholder-UsingPropertyPlaceholderintheJavaDSL]]
== Using Property Placeholder in the Java DSL
-*Available as of Camel 2.7*
+*Since Camel 2.7*
Likewise we have added support for defining placeholders in the Java DSL
using the new `placeholder` DSL as shown in the following equivalent
@@ -446,7 +446,7 @@ from("direct:start")
[[UsingPropertyPlaceholder-UsingBlueprintPropertyPlaceholderwithCamelRoutes]]
== Using Blueprint Property Placeholder with Camel Routes
-*Available as of Camel 2.7*
+*Since Camel 2.7*
Camel supports xref:using-osgi-blueprint-with-camel.adoc[Blueprint]
which also offers a property placeholder service. Camel supports
@@ -539,7 +539,7 @@ Each location is separated by comma.
[[UsingPropertyPlaceholder-OverridingBlueprintPropertyPlaceholdersOutsideCamelContext]]
== Overriding Blueprint Property Placeholders Outside CamelContext
-*Available as of Camel 2.10.4*
+*Since Camel 2.10.4*
When using Blueprint property placeholder in the Blueprint XML file, you
can declare the properties directly in the XML file as shown below:
@@ -597,7 +597,7 @@ XML file.
[[UsingPropertyPlaceholder-Usinga.cfgor.propertiesFileForBlueprintPropertyPlaceholders]]
== Using a `.cfg` or `.properties` File For Blueprint Property Placeholders
-*Available as of Camel 2.10.4*
+*Since Camel 2.10.4*
When using Blueprint property placeholder in the Blueprint XML file, you
can declare the properties in a .properties or `.cfg` file. If you use
@@ -770,7 +770,7 @@ destination=mock:result
[[UsingPropertyPlaceholder-BridgingSpringandCamelPropertyPlaceholders-1]]
== Bridging Spring and Camel Property Placeholders
-*Available as of Camel 2.10*
+*Since Camel 2.10*
The Spring Framework does not allow third-party frameworks such as
Apache Camel to seamless hook into the Spring property placeholder
@@ -855,7 +855,7 @@ with `ignoreUnresolvablePlaceholders` option to `true`.
[[UsingPropertyPlaceholder-OverridingPropertiesfromCamelTestKit]]
== Overriding Properties from Camel Test Kit
-*Available as of Camel 2.10*
+*Since Camel 2.10*
When xref:testing.adoc[Testing] with Camel and using the
xref:components::properties-component.adoc[Properties] component, you may want to be able to
@@ -894,7 +894,7 @@ access to the location of the properties.
[[UsingPropertyPlaceholder-UsingPropertyInject]]
== Using `@PropertyInject`
-*Available as of Camel 2.12*
+*Since Camel 2.12*
Camel allows to inject property placeholders in POJOs using
the `@PropertyInject` annotation which can be set on fields and setter
@@ -944,7 +944,7 @@ private int timeout;
[[UsingPropertyPlaceholder-UsingOutoftheBoxFunctions]]
== Using Out of the Box Functions
-*Available as of Camel 2.14.1*
+*Since Camel 2.14.1*
The xref:components::properties-component.adoc[Properties] component includes the following
functions out of the box
@@ -1036,7 +1036,7 @@ example to call a service on localhost, maybe for unit testing etc:
[[UsingPropertyPlaceholder-UsingCustomFunctions]]
== Using Custom Functions (advanced)
-*Available as of Camel 2.14.1*
+*Since Camel 2.14.1*
The xref:components::properties-component.adoc[Properties] component allow to plugin 3rd party
functions which can be used during parsing of the property placeholders.
diff --git a/docs/user-manual/modules/ROOT/pages/validator.adoc b/docs/user-manual/modules/ROOT/pages/validator.adoc
index d683d18..2aff00c 100644
--- a/docs/user-manual/modules/ROOT/pages/validator.adoc
+++ b/docs/user-manual/modules/ROOT/pages/validator.adoc
@@ -1,7 +1,7 @@
[[Validator-Validator]]
= Validator
-*Available as of Camel 2.19*
+*Since Camel 2.19*
Validator performs declarative validation of the message according to the declared
`Input Type` and/or `Output Type` on a route definition which declares the expected