You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2018/10/19 11:02:28 UTC
[camel] branch master updated: CAMEL-11497: Migrate FAQ - general
questions (#2571)
This is an automated email from the ASF dual-hosted git repository.
acosentino 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 3b7a469 CAMEL-11497: Migrate FAQ - general questions (#2571)
3b7a469 is described below
commit 3b7a469e1046f1c4632e0b138e2f8697959a2603
Author: Tadayoshi Sato <sa...@gmail.com>
AuthorDate: Fri Oct 19 20:02:22 2018 +0900
CAMEL-11497: Migrate FAQ - general questions (#2571)
---
camel-core/src/main/docs/eips/bean-eip.adoc | 2 +-
.../main/docs/eips/content-based-router-eip.adoc | 8 +-
.../src/main/docs/eips/content-filter-eip.adoc | 65 +
.../src/main/docs/eips/dead-letter-channel.adoc | 10 +-
camel-core/src/main/docs/eips/event-message.adoc | 4 +-
.../main/docs/eips/eventDrivenConsumer-eip.adoc | 58 +
camel-core/src/main/docs/eips/message-channel.adoc | 2 +-
.../src/main/docs/eips/message-endpoint.adoc | 4 +-
.../src/main/docs/eips/message-translator.adoc | 4 +-
camel-core/src/main/docs/eips/message.adoc | 2 +-
camel-core/src/main/docs/eips/process-eip.adoc | 2 +-
camel-core/src/main/docs/eips/toD-eip.adoc | 2 +-
.../src/main/docs/eips/transactional-client.adoc | 2 +-
camel-core/src/main/docs/eips/wireTap-eip.adoc | 8 +-
docs/user-manual/en/SUMMARY.md | 24 +-
.../en/annotation-based-expression-language.adoc | 154 +++
docs/user-manual/en/architecture.adoc | 4 +-
.../en/asynchronous-routing-engine.adoc | 2 +-
docs/user-manual/en/bam-example.adoc | 2 +-
docs/user-manual/en/bean-integration.adoc | 2 +-
docs/user-manual/en/book-getting-started.adoc | 2 +-
docs/user-manual/en/camel-jar-dependencies.adoc | 2 +-
.../user-manual/en/commercial-camel-offerings.adoc | 126 ++
docs/user-manual/en/component.adoc | 6 +-
...add-a-component.adoc => configuring-camel.adoc} | 11 +-
docs/user-manual/en/data-format.adoc | 177 +++
docs/user-manual/en/defaulterrorhandler.adoc | 4 +-
docs/user-manual/en/dsl.adoc | 2 +-
docs/user-manual/en/error-handling-in-camel.adoc | 8 +-
docs/user-manual/en/examples.adoc | 2 +-
docs/user-manual/en/exception-clause.adoc | 2 +-
docs/user-manual/en/exchange-pattern.adoc | 2 +-
docs/user-manual/en/expression.adoc | 2 +-
docs/user-manual/en/faq.adoc | 261 ++++
.../en/faq/can-i-get-commercial-support.adoc | 4 +
.../en/faq/can-i-use-camel-on-java-14.adoc | 9 +
.../en/faq/does-camel-work-on-ibms-jdk.adoc | 32 +
.../en/faq/how-can-i-get-the-source-code.adoc | 50 +
.../en/faq/how-do-i-become-a-committer.adoc | 61 +
.../en/faq/how-do-i-change-the-logging.adoc | 20 +
.../en/faq/how-do-i-compile-the-code.adoc | 4 +
.../en/{ => faq}/how-do-i-configure-endpoints.adoc | 2 +-
.../en/faq/how-do-i-edit-the-website.adoc | 18 +
.../how-do-i-run-camel-using-java-webstart.adoc | 83 ++
...spring-property-placeholder-with-camel-xml.adoc | 2 +-
.../en/faq/how-does-camel-compare-to-mule.adoc | 29 +
.../how-does-camel-compare-to-servicemix-eip.adoc | 61 +
.../faq/how-does-camel-compare-to-servicemix.adoc | 43 +
.../en/faq/how-does-camel-compare-to-synapse.adoc | 32 +
.../en/faq/how-does-camel-work-with-activemq.adoc | 21 +
.../faq/how-does-camel-work-with-servicemix.adoc | 25 +
docs/user-manual/en/faq/how-does-camel-work.adoc | 5 +
.../en/faq/how-does-the-camel-api-compare-to.adoc | 43 +
.../en/faq/how-does-the-website-work.adoc | 8 +
...f-i-use-servicemix-when-should-i-use-camel.adoc | 22 +
docs/user-manual/en/faq/is-camel-an-esb.adoc | 17 +
docs/user-manual/en/faq/is-camel-ioc-friendly.adoc | 61 +
.../en/faq/running-camel-standalone.adoc | 29 +
.../en/faq/what-are-the-dependencies.adoc | 67 +
docs/user-manual/en/faq/what-is-a-router.adoc | 23 +
docs/user-manual/en/faq/what-is-camel.adoc | 60 +
docs/user-manual/en/faq/what-is-the-license.adoc | 6 +
docs/user-manual/en/faq/what-jars-do-i-need.adoc | 34 +
.../en/faq/what-platforms-are-supported.adoc | 8 +
docs/user-manual/en/faq/why-the-name-camel.adoc | 30 +
docs/user-manual/en/fluent-builders.adoc | 11 +
docs/user-manual/en/getting-started.adoc | 4 +-
docs/user-manual/en/guice-jms-example.adoc | 2 +-
docs/user-manual/en/injector.adoc | 2 +-
docs/user-manual/en/irc-room.adoc | 24 +
docs/user-manual/en/languages.adoc | 52 +
docs/user-manual/en/mailing-lists.adoc | 72 +
docs/user-manual/en/processor.adoc | 99 ++
.../en/release-notes/camel-2170-release.adoc | 20 +-
.../en/release-notes/camel-2180-release.adoc | 18 +-
.../en/release-notes/camel-2190-release.adoc | 10 +-
.../en/release-notes/camel-2200-release.adoc | 6 +-
.../en/release-notes/camel-2210-release.adoc | 8 +-
docs/user-manual/en/spring-testing.adoc | 2 +-
docs/user-manual/en/spring-xml-extensions.adoc | 33 +
docs/user-manual/en/spring.adoc | 5 +-
docs/user-manual/en/support.adoc | 134 ++
docs/user-manual/en/team.adoc | 174 +++
docs/user-manual/en/transactionerrorhandler.adoc | 2 +-
.../en/{component.adoc => transport.adoc} | 23 +-
docs/user-manual/en/type-converter.adoc | 403 ++++++
docs/user-manual/en/uris.adoc | 2 +-
docs/user-manual/en/using-propertyplaceholder.adoc | 2 +-
docs/user-manual/en/vtd-xml.adoc | 51 +
docs/user-manual/en/xml-configuration.adoc | 25 +
docs/user-manual/en/xml-reference.adoc | 1436 ++++++++++++++++++++
91 files changed, 4379 insertions(+), 118 deletions(-)
diff --git a/camel-core/src/main/docs/eips/bean-eip.adoc b/camel-core/src/main/docs/eips/bean-eip.adoc
index d3c3917..7d822a5 100644
--- a/camel-core/src/main/docs/eips/bean-eip.adoc
+++ b/camel-core/src/main/docs/eips/bean-eip.adoc
@@ -11,7 +11,7 @@ bean:beanID[?options]
----
Where *beanID* can be any string which is used to look up the bean in
-the link:registry.html[Registry]
+the <<Registry-Registry,Registry>>
=== EIP options
diff --git a/camel-core/src/main/docs/eips/content-based-router-eip.adoc b/camel-core/src/main/docs/eips/content-based-router-eip.adoc
index 1c52c63..193c27c 100644
--- a/camel-core/src/main/docs/eips/content-based-router-eip.adoc
+++ b/camel-core/src/main/docs/eips/content-based-router-eip.adoc
@@ -13,7 +13,7 @@ The following example shows how to route a request from an input
*seda:a* endpoint to either *seda:b*, *seda:c* or *seda:d* depending on
the evaluation of various link:predicate.html[Predicate] expressions
-=== Using the link:fluent-builders.html[Fluent Builders]
+=== Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>
[source,java]
----
@@ -41,7 +41,7 @@ can I not use when or otherwise in a Java Camel route] if you have
problems with the Java DSL, accepting using `when` or `otherwise`.
====
-=== Using the link:spring-xml-extensions.html[Spring XML Extensions]
+=== Using the <<SpringXMLExtensions-SpringXMLExtensions,Spring XML Extensions>>
[source,java]
----
@@ -74,6 +74,6 @@ https://github.com/apache/camel/blob/master/camel-core/src/test/java/org/apache/
If you would like to use this EIP Pattern then please read the
<<GettingStarted-GettingStarted,Getting Started>>. You may also find the
<<Architecture-Architecture,Architecture>> useful particularly the description
-of link:endpoint.html[Endpoint] and link:uris.html[URIs]. Then you could
-try out some of the link:examples.html[Examples] first before trying
+of <<Endpoint-Endpoints,Endpoint>> and link:uris.html[URIs]. Then you could
+try out some of the <<Examples-Examples,Examples>> first before trying
this pattern out.
diff --git a/camel-core/src/main/docs/eips/content-filter-eip.adoc b/camel-core/src/main/docs/eips/content-filter-eip.adoc
new file mode 100644
index 0000000..f66fd7e
--- /dev/null
+++ b/camel-core/src/main/docs/eips/content-filter-eip.adoc
@@ -0,0 +1,65 @@
+[[ContentFilter-eip]]
+== Content Filter
+
+Camel supports the
+http://www.enterpriseintegrationpatterns.com/ContentFilter.html[Content
+Filter] from the
+<<EnterpriseIntegrationPatterns-EnterpriseIntegrationPatterns,EIP patterns>>
+using one of the following mechanisms in the routing logic to transform
+content from the inbound message.
+
+* <<MessageTranslator-MessageTranslator,Message Translator>>
+* invoking a <<BeanIntegration-BeanIntegration,Java bean>>
+* <<Processor-Processor,Processor>> object
+
+image:http://www.enterpriseintegrationpatterns.com/img/ContentFilter.gif[image]
+
+A common way to filter messages is to use an
+<<Expression-Expressions,Expression>> in the <<DSL-DSL,DSL>> like
+<<xquery-language,XQuery>>, <<sql-language,SQL>> or one of the supported
+<<ScriptingLanguages-ScriptingLanguages,Scripting Languages>>.
+
+=== Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>
+
+Here is a simple example using the <<DSL-DSL,DSL>> directly
+
+In this example we add our own <<Processor-Processor,Processor>>
+
+For further examples of this pattern in use you could look at one of the
+JUnit tests
+
+* link:../../../test/java/org/apache/camel/processor/TransformTest.java?[TransformTest]
+* link:../../../test/java/org/apache/camel/processor/TransformViaDSLTest.java[TransformViaDSLTest]
+
+=== Using Spring XML
+
+[source,xml]
+----
+<route>
+ <from uri="activemq:Input"/>
+ <bean ref="myBeanName" method="doTransform"/>
+ <to uri="activemq:Output"/>
+</route>
+----
+
+You can also use XPath to filter out part of the message you are
+interested in:
+
+[source,xml]
+----
+<route>
+ <from uri="activemq:Input"/>
+ <setBody><xpath resultType="org.w3c.dom.Document">//foo:bar</xpath></setBody>
+ <to uri="activemq:Output"/>
+</route>
+----
+
+[[ContentFilter-UsingThisPattern]]
+=== Using This Pattern
+
+If you would like to use this EIP Pattern then please read the
+<<GettingStarted-GettingStarted,Getting Started>>, you may also find the
+<<Architecture-Architecture,Architecture>> useful particularly the description
+of <<Endpoint-Endpoints,Endpoint>> and <<URIs-URIs,URIs>>. Then you could
+try out some of the <<Examples-Examples,Examples>> first before trying
+this pattern out.
diff --git a/camel-core/src/main/docs/eips/dead-letter-channel.adoc b/camel-core/src/main/docs/eips/dead-letter-channel.adoc
index 1f44700..8aab98b 100644
--- a/camel-core/src/main/docs/eips/dead-letter-channel.adoc
+++ b/camel-core/src/main/docs/eips/dead-letter-channel.adoc
@@ -303,7 +303,7 @@ So if it exists its the *last* endpoint which Camel send the Exchange
to.
When for example processing the link:exchange.html[Exchange] at a given
-link:endpoint.html[Endpoint] and the message is to be moved into the
+<<Endpoint-Endpoints,Endpoint>> and the message is to be moved into the
dead letter queue, then Camel also decorates the Exchange with another
property that contains that *last* endpoint:
@@ -472,10 +472,10 @@ also http://stackoverflow.com/questions/13711462/logging-camel-exceptions-and-s
==== Using This Pattern
If you would like to use this EIP Pattern then please read the
-link:getting-started.html[Getting Started], you may also find the
-link:architecture.html[Architecture] useful particularly the description
-of link:endpoint.html[Endpoint] and link:uris.html[URIs]. Then you could
-try out some of the link:examples.html[Examples] first before trying
+<<GettingStarted-GettingStarted,Getting Started>>, you may also find the
+<<Architecture-Architecture,Architecture>> useful particularly the description
+of <<Endpoint-Endpoints,Endpoint>> and link:uris.html[URIs]. Then you could
+try out some of the <<Examples-Examples,Examples>> first before trying
this pattern out.
* link:error-handler.html[Error Handler]
diff --git a/camel-core/src/main/docs/eips/event-message.adoc b/camel-core/src/main/docs/eips/event-message.adoc
index 3575b30..199bb31 100644
--- a/camel-core/src/main/docs/eips/event-message.adoc
+++ b/camel-core/src/main/docs/eips/event-message.adoc
@@ -1,4 +1,4 @@
-[[EventMessage-EventMessage]]
+[[eventMessage-eip]]
== Event Message
Camel supports the
@@ -17,7 +17,7 @@ such as for <<jms-component,JMS>>, <<jms-component,File>> or
TIP: See the related link:request-reply.html[Request Reply] message.
-[[EventMessage-ExplicitlyspecifyingInOnly]]
+[[eventMessage-ExplicitlyspecifyingInOnly]]
=== Explicitly specifying InOnly
If you are using a component which defaults to InOut you can override
diff --git a/camel-core/src/main/docs/eips/eventDrivenConsumer-eip.adoc b/camel-core/src/main/docs/eips/eventDrivenConsumer-eip.adoc
new file mode 100644
index 0000000..a3082aa
--- /dev/null
+++ b/camel-core/src/main/docs/eips/eventDrivenConsumer-eip.adoc
@@ -0,0 +1,58 @@
+[[eventDrivenConsumer-eip]]
+== Event Driven Consumer
+
+Camel supports the
+http://www.enterpriseintegrationpatterns.com/EventDrivenConsumer.html[Event Driven Consumer]
+from the
+<<EnterpriseIntegrationPatterns-EnterpriseIntegrationPatterns,EIP patterns>>.
+The default consumer model is event based (i.e. asynchronous)
+as this means that the Camel container can then manage pooling,
+threading and concurrency for you in a declarative manner.
+
+image:http://www.enterpriseintegrationpatterns.com/img/EventDrivenConsumerSolution.gif[image]
+
+The Event Driven Consumer is implemented by consumers implementing the
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html[Processor]
+interface which is invoked by the <<messageEndpoint-eip,Message Endpoint>>
+when a <<message-eip,Message>> is available for processing.
+
+[[eventDrivenConsumer-Example]]
+=== Example
+
+The following demonstrates a
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html[Processor]
+defined in the Camel <<Registry-Registry,Registry>> which is
+invoked when an event occurs from a <<jms-component,JMS>> queue.
+
+*Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>*
+
+[source,java]
+----
+from("jms:queue:foo")
+ .processRef("processor");
+----
+
+**Using the <<SpringXMLExtensions-SpringXMLExtensions,Spring XML Extensions>>**
+
+[source,xml]
+----
+<route>
+ <from uri="jms:queue:foo"/>
+ <to uri="processor"/>
+</route>
+----
+
+For more details see:
+
+* <<message-eip,Message>>
+* <<messageEndpoint-eip,Message Endpoint>>
+
+[[eventDrivenConsumer-UsingThisPattern]]
+=== Using This Pattern
+
+If you would like to use this EIP Pattern then please read the
+<<GettingStarted-GettingStarted,Getting Started>>, you may also find the
+<<Architecture-Architecture,Architecture>> useful particularly the description
+of <<Endpoint-Endpoints,Endpoint>> and <<URIs-URIs,URIs>>. Then you could
+try out some of the <<Examples-Examples,Examples>> first before trying
+this pattern out.
diff --git a/camel-core/src/main/docs/eips/message-channel.adoc b/camel-core/src/main/docs/eips/message-channel.adoc
index 57f8e76..b7d3b64 100644
--- a/camel-core/src/main/docs/eips/message-channel.adoc
+++ b/camel-core/src/main/docs/eips/message-channel.adoc
@@ -48,4 +48,4 @@ And in XML:
For more details see
* link:message.html[Message]
-* link:message-endpoint.html[Message Endpoint]
+* <<messageEndpoint-eip,Message Endpoint>>
diff --git a/camel-core/src/main/docs/eips/message-endpoint.adoc b/camel-core/src/main/docs/eips/message-endpoint.adoc
index 17bc4ed..486a692 100644
--- a/camel-core/src/main/docs/eips/message-endpoint.adoc
+++ b/camel-core/src/main/docs/eips/message-endpoint.adoc
@@ -1,4 +1,4 @@
-[[MessageEndpoint-MessageEndpoint]]
+[[messageEndpoint-eip]]
== Message Endpoint
Camel supports the
@@ -21,7 +21,7 @@ available
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Component.html[Component]
implementations.
-[[MessageEndpoint-Example]]
+[[messageEndpoint-Example]]
=== Samples
See first example in link:https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/to-eip.adoc[To EIP]
diff --git a/camel-core/src/main/docs/eips/message-translator.adoc b/camel-core/src/main/docs/eips/message-translator.adoc
index d2137d3..797e96e 100644
--- a/camel-core/src/main/docs/eips/message-translator.adoc
+++ b/camel-core/src/main/docs/eips/message-translator.adoc
@@ -16,7 +16,7 @@ image:http://www.enterpriseintegrationpatterns.com/img/MessageTranslator.gif[ima
You can transform a message using Camel's
link:bean-integration.html[Bean Integration] to call any method on a
-bean in your link:registry.html[Registry] such as your
+bean in your <<Registry-Registry,Registry>> such as your
link:spring.html[Spring] XML configuration file as follows
[source,java]
@@ -36,7 +36,7 @@ the transformation
or you can use the DSL to explicitly configure the transformation
-You can also use link:spring-xml-extensions.html[Spring XML Extensions]
+You can also use <<SpringXMLExtensions-SpringXMLExtensions,Spring XML Extensions>>
to do a transformation. Basically any link:expression.html[Expression]
language can be substituted inside the transform element as shown below
diff --git a/camel-core/src/main/docs/eips/message.adoc b/camel-core/src/main/docs/eips/message.adoc
index 1c89282..ccee101 100644
--- a/camel-core/src/main/docs/eips/message.adoc
+++ b/camel-core/src/main/docs/eips/message.adoc
@@ -1,4 +1,4 @@
-[[Message-Message]]
+[[message-eip]]
== Message
Camel supports the
diff --git a/camel-core/src/main/docs/eips/process-eip.adoc b/camel-core/src/main/docs/eips/process-eip.adoc
index aaca6dd..04cdd48 100644
--- a/camel-core/src/main/docs/eips/process-eip.adoc
+++ b/camel-core/src/main/docs/eips/process-eip.adoc
@@ -88,7 +88,7 @@ refactor it into a separate class.
There is a base class called
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/ProcessorEndpoint.html[ProcessorEndpoint]
-which supports the full link:endpoint.html[Endpoint] semantics given a
+which supports the full <<Endpoint-Endpoints,Endpoint>> semantics given a
Processor instance.
So you just need to create a link:https://github.com/apache/camel/tree/master/components[Component] class by
diff --git a/camel-core/src/main/docs/eips/toD-eip.adoc b/camel-core/src/main/docs/eips/toD-eip.adoc
index f788864..ad6d557 100644
--- a/camel-core/src/main/docs/eips/toD-eip.adoc
+++ b/camel-core/src/main/docs/eips/toD-eip.adoc
@@ -2,7 +2,7 @@
== To D EIP
There is a new `.toD` / `<toD>` that allows to send a message to a dynamic
-computed link:endpoint.html[Endpoint] using one or
+computed <<Endpoint-Endpoints,Endpoint>> using one or
more link:expression.html[Expression] that are concat together. By
default the <<simple-language,Simple>> language is used to compute
the endpoint.
diff --git a/camel-core/src/main/docs/eips/transactional-client.adoc b/camel-core/src/main/docs/eips/transactional-client.adoc
index f460ed2..4b6360f 100644
--- a/camel-core/src/main/docs/eips/transactional-client.adoc
+++ b/camel-core/src/main/docs/eips/transactional-client.adoc
@@ -1,4 +1,4 @@
-[[TransactionalClient-TransactionalClient]]
+[[transactionalClient-eip]]
== Transactional Client
Camel recommends supporting the
diff --git a/camel-core/src/main/docs/eips/wireTap-eip.adoc b/camel-core/src/main/docs/eips/wireTap-eip.adoc
index 275d930..33d1b35 100644
--- a/camel-core/src/main/docs/eips/wireTap-eip.adoc
+++ b/camel-core/src/main/docs/eips/wireTap-eip.adoc
@@ -68,8 +68,7 @@ values.
=== Sending a Copy (traditional wiretap)
-* Using the link:fluent-builders.html[Fluent
-Builders]
+* Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>
[source,java]
----
@@ -96,8 +95,9 @@ Builders]
=== Sending a New link:exchange.html[Exchange]
-*Using the link:fluent-builders.html[Fluent Builders]*
- Camel supports either a processor or an
+*Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>*
+
+Camel supports either a processor or an
link:expression.html[Expression] to populate the new
link:exchange.html[Exchange]. Using a processor gives you full power
over how the link:exchange.html[Exchange] is populated as you can set
diff --git a/docs/user-manual/en/SUMMARY.md b/docs/user-manual/en/SUMMARY.md
index 1ecb27b..55d9643 100644
--- a/docs/user-manual/en/SUMMARY.md
+++ b/docs/user-manual/en/SUMMARY.md
@@ -11,7 +11,7 @@
* Download
* [Getting Started](getting-started.adoc)
* [Longer Getting Started Guide](book-getting-started.adoc)
-* FAQ
+* [FAQ](faq.adoc)
* [Legal Notice](notice.md)
## Documentation
@@ -41,9 +41,9 @@
* [Working with Camel and Spring](spring.adoc)
* [Working with Camel and Guice](guice.adoc)
* [Working with Camel and Karaf](karaf.adoc)
-* [How do I configure endpoints?](how-do-i-configure-endpoints.adoc)
+* [How do I configure endpoints?](faq/how-do-i-configure-endpoints.adoc)
* [Bean Integration](bean-integration.adoc)
-* [Configuring Camel](how-do-i-add-a-component.adoc)
+* [Configuring Camel](configuring-camel.adoc)
* [Configuring route startup ordering and autostartup]
* [Graceful Shutdown]
* [AsyncProcessorAwaitManager] for insight into the routing engine when it has been forced to block threads while exchanges are being processed asynchronous
@@ -52,7 +52,7 @@
* [Tutorials]
* [Examples](examples.adoc)
* [Testing](testing.adoc)
-* [Xml Configuration]
+* [XML Configuration](xml-configuration.adoc)
* [Using CamelProxy] for how to use proxies for clients to easily invoke camel routes without them knowing
* [Camel Maven Plugin] for running Camel from a Maven goal
* [Guice Maven Plugin] for working with [Guice](guice.adoc)
@@ -86,7 +86,7 @@
* Clustering and loadbalancing
* [Component](component.adoc)
* ComponentConfiguration
-* Data Format
+* [Data Format](data-format.adoc)
* [Debugger](debugger.adoc)
* [Delay Interceptor](delay-interceptor.adoc)
* [Dependency Injection](dependency-injection.adoc)
@@ -108,7 +108,7 @@
* [OnCompletion](oncompletion.adoc)
* Pluggable Class Resolvers
* [Predicate](predicate.adoc)
-* Processor
+* [Processor](processor.adoc)
* [Registry](registry.adoc)
* [RouteBuilder](route-builder.adoc)
* RoutePolicy
@@ -118,8 +118,8 @@
* Threading Model
* ToAsync
* Tracer
-* Transport
-* Type Converter
+* [Transport](transport.adoc)
+* [Type Converter](type-converter.adoc)
* URIs
* UuidGenerator
* Xml Configuration
@@ -555,7 +555,7 @@
* [Zip File](zipfile-dataformat.adoc)
<!-- dataformats: END -->
-### Languages
+### [Languages](languages.adoc)
<!-- languages: START -->
* Expression Languages
@@ -587,9 +587,9 @@
## Community
-* Support
-* Contributing
-* Mailing Lists
+* [Support](support.adoc)
+* [Contributing](../../../CONTRIBUTING.md)
+* [Mailing Lists](mailing-lists.adoc)
* Gitter / IRC Chat
* User Stories
* News
diff --git a/docs/user-manual/en/annotation-based-expression-language.adoc b/docs/user-manual/en/annotation-based-expression-language.adoc
new file mode 100644
index 0000000..fdea7fe
--- /dev/null
+++ b/docs/user-manual/en/annotation-based-expression-language.adoc
@@ -0,0 +1,154 @@
+[[AnnotationBasedExpressionLanguage-AnnotationBasedExpressionLanguage]]
+=== Annotation Based Expression Language
+
+You can also use any of the link:languages.adoc[Languages] supported in
+Camel to bind expressions to method parameters when using
+link:bean-integration.adoc[Bean Integration]. For example you can use
+any of these annotations:
+
+[width="100%",cols="50%,50%",options="header",]
+|=======================================================================
+|Annotation |Description
+|http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/language/Bean.html[@Bean]
+|Inject a <<bean-language,Bean>> expression
+
+|http://camel.apache.org/maven/current/camel-script/apidocs/org/apache/camel/builder/script/BeanShell.html[@BeanShell]
+|Inject a <<beanshell-language,BeanShell>> expression
+
+|http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/language/Constant.html[@Constant]
+|Inject a <<constant-language,Constant>> expression
+
+|http://camel.apache.org/maven/current/camel-juel/apidocs/org/apache/camel/language/juel/EL.html[@EL]
+|Inject an <<el-language,EL>> expression
+
+|http://camel.apache.org/maven/current/camel-script/apidocs/org/apache/camel/builder/script/Groovy.html[@Groovy]
+|Inject a <<groovy-language,Groovy>> expression
+
+|http://camel.apache.org/maven/current/maven/camel-core/apidocs/org/apache/camel/Header.html[@Header]
+|Inject a <<header-language,Header>> expression
+
+|http://camel.apache.org/maven/current/camel-script/apidocs/org/apache/camel/builder/script/JavaScript.html[@JavaScript]
+|Inject a <<javascript-language,JavaScript>> expression
+
+|http://camel.apache.org/maven/current/camel-mvel/apidocs/org/apache/camel/language/mvel/MVEL.html[@MVEL]
+|Inject a <<mvel-language,MVEL>> expression
+
+|http://camel.apache.org/maven/current/camel-ognl/apidocs/org/apache/camel/language/ognl/OGNL.html[@OGNL]
+|Inject an <<ognl-language,OGNL>> expression
+
+|http://camel.apache.org/maven/current/camel-script/apidocs/org/apache/camel/builder/script/PHP.html[@PHP]
+|Inject a <<php-language,PHP>> expression
+
+|http://camel.apache.org/maven/current/camel-script/apidocs/org/apache/camel/builder/script/Python.html[@Python]
+|Inject a <<python-language,Python>> expression
+
+|http://camel.apache.org/maven/current/camel-script/apidocs/org/apache/camel/builder/script/Ruby.html[@Ruby]
+|Inject a <<ruby-language,Ruby>> expression
+
+|http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/language/Simple.html[@Simple]
+|Inject an <<simple-language,Simple>> expression
+
+|http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/language/XPath.html[@XPath]
+|Inject an <<xpath-language,XPath>> expression
+
+|http://camel.apache.org/maven/current/camel-saxon/apidocs/org/apache/camel/component/xquery/XQuery.html[@XQuery]
+|Inject an <<xquery-language,XQuery>> expression
+|=======================================================================
+
+[[AnnotationBasedExpressionLanguage-Example]]
+===== Example
+
+[source,java]
+----
+public class Foo {
+
+ @MessageDriven(uri = "activemq:my.queue")
+ public void doSomething(@XPath("/foo/bar/text()") String correlationID, @Body String body) {
+ // process the inbound message here
+ }
+}
+----
+
+[[AnnotationBasedExpressionLanguage-AdvancedexampleusingBean]]
+===== Advanced example using @Bean
+
+And an example of using the the
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/language/Bean.html[@Bean]
+binding annotation, where you can use a <<bean-component,POJO>> where you
+can do whatever java code you like:
+
+[source,java]
+----
+public class Foo {
+
+ @MessageDriven(uri = "activemq:my.queue")
+ public void doSomething(@Bean("myCorrelationIdGenerator") String correlationID, @Body String body) {
+ // process the inbound message here
+ }
+}
+----
+
+And then we can have a spring bean with the id
+`myCorrelationIdGenerator` where we can compute the id.
+
+[source,java]
+----
+public class MyIdGenerator {
+
+ private UserManager userManager;
+
+ public String generate(@Header(name = "user") String user, @Body String payload) throws Exception {
+ User user = userManager.lookupUser(user);
+ String userId = user.getPrimaryId();
+ String id = userId + generateHashCodeForPayload(payload);
+ return id;
+ }
+}
+----
+
+The <<bean-component,POJO>> `MyIdGenerator` has one public method that
+accepts two parameters. However we have also annotated this one with the
+`@Header` and `@Body` annotation to help Camel know what to bind here from
+the Message from the Exchange being processed.
+
+Of course this could be simplified a lot if you for instance just have a
+simple id generator. But we wanted to demonstrate that you can use the
+link:bean-binding.adoc[Bean Binding] annotations anywhere.
+
+[source,java]
+----
+public class MySimpleIdGenerator {
+
+ public static int generate() {
+ // generate a unique id
+ return 123;
+ }
+}
+----
+
+And finally we just need to remember to have our bean registered in the
+Spring link:registry.adoc[Registry]:
+
+[source,xml]
+----
+ <bean id="myCorrelationIdGenerator" class="com.mycompany.MySimpleIdGenerator"/>
+----
+
+[[AnnotationBasedExpressionLanguage-ExampleusingGroovy]]
+===== Example using <<groovy-language,Groovy>>
+
+In this example we have an Exchange that has a User object stored in the
+in header. This User object has methods to get some user information. We
+want to use <<groovy.adoc[Groovy] to inject an expression that
+extracts and concats the fullname of the user into the fullName
+parameter.
+
+[source,java]
+----
+ public void doSomething(@Groovy("$request.header['user'].firstName $request.header['user'].familyName) String fullName, @Body String body) {
+ // process the inbound message here
+ }
+----
+
+Groovy supports GStrings that is like a template where we can insert $
+placeholders that will be evaluated by Groovy.
diff --git a/docs/user-manual/en/architecture.adoc b/docs/user-manual/en/architecture.adoc
index 6313b4a..4e9c80c 100644
--- a/docs/user-manual/en/architecture.adoc
+++ b/docs/user-manual/en/architecture.adoc
@@ -2,12 +2,12 @@
Architecture
~~~~~~~~~~~~
-Camel uses a Java based link:dsl.html[Routing Domain Specific Language
+Camel uses a Java based link:dsl.adoc[Routing Domain Specific Language
(DSL)] or an Xml Configuration to configure
routing and mediation rules which are added to a
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html[CamelContext]
to implement the various
-link:enterprise-integration-patterns.html[Enterprise Integration
+link:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns].
At a high level Camel consists of a
diff --git a/docs/user-manual/en/asynchronous-routing-engine.adoc b/docs/user-manual/en/asynchronous-routing-engine.adoc
index 7932776..aaadf8c 100644
--- a/docs/user-manual/en/asynchronous-routing-engine.adoc
+++ b/docs/user-manual/en/asynchronous-routing-engine.adoc
@@ -5,7 +5,7 @@ Asynchronous Routing Engine
*Available as of Camel 2.4*
As of Camel 2.4 the asynchronous routing engine is back and kicking. +
-All the link:enterprise-integration-patterns.html[Enterprise
+All the link:enterprise-integration-patterns.adoc[Enterprise
Integration Patterns] are supported as well a selected number of
Components:
diff --git a/docs/user-manual/en/bam-example.adoc b/docs/user-manual/en/bam-example.adoc
index d244e5a..c235b02 100644
--- a/docs/user-manual/en/bam-example.adoc
+++ b/docs/user-manual/en/bam-example.adoc
@@ -95,7 +95,7 @@ Components such as ActiveMQ,
Running the example
^^^^^^^^^^^^^^^^^^^
-To run the example we use the link:camel-maven-plugin.html[Camel Maven
+To run the example we use the link:camel-maven-plugin.adoc[Camel Maven
Plugin]. For example from the source or binary distribution the
following should work
diff --git a/docs/user-manual/en/bean-integration.adoc b/docs/user-manual/en/bean-integration.adoc
index bdea094..a83d323 100644
--- a/docs/user-manual/en/bean-integration.adoc
+++ b/docs/user-manual/en/bean-integration.adoc
@@ -85,7 +85,7 @@ uses Camel as the underlying transport mechanism. The nice thing about
this approach is we can use any of the Camel transport
Components to communicate between beans. It also
means we can use Content Based Router
-and the other link:enterprise-integration-patterns.html[Enterprise
+and the other link:enterprise-integration-patterns.adoc[Enterprise
Integration Patterns] in between the beans; in particular we can use
Message Translator to be able to convert
what the on-the-wire messages look like in addition to adding various
diff --git a/docs/user-manual/en/book-getting-started.adoc b/docs/user-manual/en/book-getting-started.adoc
index 36b4d96..48e2b86 100644
--- a/docs/user-manual/en/book-getting-started.adoc
+++ b/docs/user-manual/en/book-getting-started.adoc
@@ -63,7 +63,7 @@ you navigate between parent and child subsections. +
For example, If you are on the "Languages" documentation page then the
left-hand side of the reddish bar contains the following links.
-[source,brush:,java;,gutter:,false;,theme:,Default]
+[source,java]
----
Apache Camel > Documentation > Architecture > Languages
----
diff --git a/docs/user-manual/en/camel-jar-dependencies.adoc b/docs/user-manual/en/camel-jar-dependencies.adoc
index 9670e51..b63090c 100644
--- a/docs/user-manual/en/camel-jar-dependencies.adoc
+++ b/docs/user-manual/en/camel-jar-dependencies.adoc
@@ -50,6 +50,6 @@ From *Camel 2.9*: the Spring JARs are no longer required for using JMX.
Other Components
~~~~~~~~~~~~~~~~
-All the other link:components.html[Components] have a range of 3rd party
+All the other link:component.adoc[Components] have a range of 3rd party
.jars they depend on. They are listed in the maven pom files which files
they require.
diff --git a/docs/user-manual/en/commercial-camel-offerings.adoc b/docs/user-manual/en/commercial-camel-offerings.adoc
new file mode 100644
index 0000000..1b5fe9f
--- /dev/null
+++ b/docs/user-manual/en/commercial-camel-offerings.adoc
@@ -0,0 +1,126 @@
+[[CommercialCamelOfferings-CommercialCamelOfferings]]
+=== Commercial Camel Offerings
+
+Apache Camel is a widely used project. As such, several companies have
+built products and services around Camel. This page is dedicated to
+providing descriptions of those offerings and links to more information.
+Companies are definitely encouraged to update this page directly or
+link:mailing-lists.adoc[send a mail] to the Camel PMC with a description
+of your offerings and we can update the page. The products and services
+listed on this page are provided for information use only to our users.
+The Camel PMC does not endorse or recommend any of the products or
+services on this page. See below for information about what is
+appropriate to add to the page.
+
+[[CommercialCamelOfferings-Code-House]]
+==== http://code-house.org[Code-House]
+
+http://code-house.org[Code-House] is european service provider with own
+training programs covering Apache middleware projects (Camel,
+ServiceMix, ActiveMQ) on development and system operations level. We
+also offer dedicated management tool.
+
+[[CommercialCamelOfferings-CyberlogicConsulting]]
+==== http://www.cyberlogic.ch[Cyberlogic Consulting]
+
+http://www.cyberlogic.ch[Cyberlogic Consulting] is a Swiss based
+consultancy. We pride ourselves in providing Swiss quality services
+including enterprise consulting, coding, systems integration, training
+and support for Apache Camel and the related Apache Open Source
+Software. We specialize in helping our clients to realize new projects
+and support the delivery of the project from end to end.
+
+[[CommercialCamelOfferings-Evosent]]
+==== http://evosent.com/?utm_source=apache&utm_medium=web&utm_campaign=commercial_support[Evosent]
+
+http://evosent.com/?utm_source=apache&utm_medium=web&utm_campaign=commercial_support[Evosent]�is
+a boutique consultancy based in Europe. It specialises in open source
+integration middleware, messaging and big data: Apache Camel,
+ServiceMix, Karaf, ActiveMQ, Elasticsearch (+ Kibana + Logstash), Docker
+and Kubernetes. Evosent is managed by a committer and PMC member at the
+Apache Camel and Apache Ignite projects. Amongst it services are: ninja
+consulting and support; workshops, mentoring and training; proof of
+concept development; and sophisticated engineering services.
+
+[[CommercialCamelOfferings-GOAPPO]]
+==== https://www.goappo.com[GOAPPO]
+
+https://www.goappo.com[GOAPPO] embeds Apache Camel at design, testing
+and runtime. You start by composing ETLs using the application builder.
+You test ETLs instantly on your machine. You bundle ETLs with your
+application.
+
+[[CommercialCamelOfferings-MediaDriver]]
+==== http://mediadriver.com[Media Driver]
+
+Media Driver provides consulting services and management tools for
+Apache Camel, Red Hat JBoss Fuse and the Apache Integration stack
+(ActiveMQ, CXF, Karaf, ServiceMix, etc) for both the commercial and
+public sector. We bring a full suite of project delivery services
+including business and technical analysis, proof of concepts,
+architectural guidance, best practice integration, and project
+management. Media Driver offers training classes for developers and
+administrators, as well as middleware management software.
+
+[[CommercialCamelOfferings-Middleware360]]
+==== http://www.middleware360.com/[Middleware360]
+
+http://www.middleware360.com/[Middleware360] Enterprise Integration
+consulting services.
+
+[[CommercialCamelOfferings-OpenLogic]]
+==== http://www.openlogic.com/[OpenLogic]
+
+http://www.openlogic.com/[OpenLogic] provide support.
+
+[[CommercialCamelOfferings-RedHat]]
+==== https://www.redhat.com/en/technologies/jboss-middleware/fuse[Red Hat]
+
+https://www.redhat.com/en/technologies/jboss-middleware/fuse[Red Hat] offers
+http://www.redhat.com/en/technologies/jboss-middleware/fuse[Fuse],
+an enterprise integration platform based on Apache Camel and other
+open source integration projects, with developer and production support.
+In addition to enterprise support, Red Hat provides
+https://www.redhat.com/en/services/training/courses-by-curriculum#Red-Hat-JBoss-Fuse-BRMS-and-more[training],
+https://www.redhat.com/en/services/consulting[consulting], and
+https://developers.redhat.com/products/fuse/overview/[a developer community].
+
+[[CommercialCamelOfferings-SavoirTechnologiesInc]]
+==== http://www.savoirtech.com[Savoir Technologies, Inc]
+
+http://www.savoirtech.com[Savoir Technologies, Inc] provides enterprise
+consulting, training and support for Camel and a host of other Apache
+service containers. Savoir can provide best practice mentoring for
+developing with Camel, as well as architectural/design reviews,
+troubleshooting and SOA infrastructure implementations.
+
+[[CommercialCamelOfferings-TalendInc]]
+==== http://www.talend.com[Talend, Inc]
+
+http://www.talend.com[Talend, Inc] provides enterprise level services,
+training and support for Apache Camel and their
+http://www.talend.com/products/esb-standard-edition.php[Talend ESB]
+product which is a repackaging of Apache Camel including a full,
+pre-configured OSGi runtime container.
+
+[[CommercialCamelOfferings-TouK]]
+==== http://touk.pl[TouK]
+
+http://touk.pl[TouK] provides enterprise integration consulting and
+system integration services as well as support for Apache Camel and
+Apache Servicemix. Their developers were involved in camel-activiti
+development.
+
+[[CommercialCamelOfferings-Policyforadditionstothispage]]
+==== Policy for additions to this page
+
+Companies are free to add information about their products and services
+to this page (please keep entries in alphabetical order). The
+information must be factual and informational in nature and not be a
+marketing statement. Statements that promote your products and services
+over other offerings on the page will not be tolerated and will be
+removed. Such marketing statements can be added to your own pages on
+your own site, but not here.
+
+When in doubt, email the Camel dev list (see
+link:mailing-lists.adoc[Mailing Lists]) and ask. We'd be happy to help.
diff --git a/docs/user-manual/en/component.adoc b/docs/user-manual/en/component.adoc
index fa801b3..9a7781f 100644
--- a/docs/user-manual/en/component.adoc
+++ b/docs/user-manual/en/component.adoc
@@ -15,7 +15,7 @@ Camel includes the following Component implementations via link:uris.adoc[URIs].
[IMPORTANT]
====
-Make sure to read link:how-do-i-configure-endpoints.adoc[How do I configure endpoints?]
+Make sure to read link:faq/how-do-i-configure-endpoints.adoc[How do I configure endpoints?]
to learn more about configuring endpoints. For
example how to refer to beans in the link:registry.adoc[Registry] or how
to use raw values for password options, and using
@@ -37,6 +37,6 @@ include::../../../components/readme.adoc[]
* link:endpoint.adoc[Endpoint]
* link:uris.adoc[URIs]
* link:writing-components.adoc[Writing Components]
-* link:how-do-i-add-a-component.adoc[How do I add a component]
-* link:how-do-i-configure-endpoints.adoc[How do I configure endpoints?]
+* link:configuring-camel.adoc[How do I add a component?]
+* link:faq/how-do-i-configure-endpoints.adoc[How do I configure endpoints?]
* link:using-propertyplaceholder.adoc[Using `PropertyPlaceholder`]
diff --git a/docs/user-manual/en/how-do-i-add-a-component.adoc b/docs/user-manual/en/configuring-camel.adoc
similarity index 92%
rename from docs/user-manual/en/how-do-i-add-a-component.adoc
rename to docs/user-manual/en/configuring-camel.adoc
index 9541e2d..2716672 100644
--- a/docs/user-manual/en/how-do-i-add-a-component.adoc
+++ b/docs/user-manual/en/configuring-camel.adoc
@@ -1,5 +1,8 @@
-[[HowdoIaddacomponent-HowdoIaddacomponent]]
-=== How do I add a component
+[[ConfiguringCamel-ConfiguringCamel]]
+=== Configuring Camel
+
+[[ConfiguringCamel-HowdoIaddacomponent]]
+==== How do I add a component?
You might first want to read link:writing-components.adoc[Writing
Components] for a background in how to implement a new component.
@@ -43,7 +46,7 @@ support `@Resource` (EJB3 style) injection or Guice style `@Inject`
injection.
-[[HowdoIaddacomponent-WorkingwithSpringXML]]
+[[ConfiguringCamel-WorkingwithSpringXML]]
==== Working with Spring XML
You can configure a component via Spring using the following mechanism:
@@ -65,7 +68,7 @@ link:contributing.adoc[contribute a patch] to the camel XSD. Otherwise
you could write your own namespace & schema if you prefer.
-[[HowdoIaddacomponent-SeeAlso]]
+[[ConfiguringCamel-SeeAlso]]
==== See Also
* link:writing-components.adoc[Writing Components]
diff --git a/docs/user-manual/en/data-format.adoc b/docs/user-manual/en/data-format.adoc
new file mode 100644
index 0000000..8ee1f26
--- /dev/null
+++ b/docs/user-manual/en/data-format.adoc
@@ -0,0 +1,177 @@
+[[DataFormat-DataFormat]]
+=== Data Format
+
+Camel supports a pluggable DataFormat to allow messages to be marshalled
+to and from binary or text formats to support a kind of
+<<MessageTranslator-MessageTranslator,Message Translator>>.
+
+The following data formats are currently supported:
+
+* Standard JVM object marshalling
+** <<serialization-dataformat,Serialization>>
+** <<string-dataformat,String>>
+
+* Object marshalling
+** <<avro-dataformat,Avro>>
+** <<boon-dataformat,Boon>>
+** <<hessian-dataformat,Hessian>>
+** link:json.adoc[JSON]
+** <<protobuf-dataformat,Protobuf>>
+** <<yaml-snakeyaml-dataformat,YAML>>
+
+* Object/XML marshalling
+** <<castor-dataformat,Castor>>
+** <<jaxb-dataformat,JAXB>>
+** <<xmlBeans-dataformat,XmlBeans>>
+** <<xstream-dataformat,XStream>>
+** <<jibx-dataformat,JiBX>>
+** <<jacksonxml-dataformat,Jackson XML>>
+
+* Object/XML/Webservice marshalling
+** <<soap-dataformat,SOAP>>
+
+* Direct JSON / XML marshalling
+** <<xmljson-dataformat,XmlJson>>
+
+* Flat data structure marshalling
+** <<beanio-dataformat,BeanIO>>
+** <<bindy-dataformat,Bindy>>
+** <<csv-dataformat,CSV>>
+** <<edi-dataformat,EDI>>
+** <<flatpack-dataformat,Flatpack DataFormat>>
+** uniVocity DataFormats <<univocity-csv-dataformat,CSV>> / <<univocity-tsv-dataformat,TSV>> / <<univocity-fixed-dataformat,Fixed Length>>
+
+* Domain specific marshalling
+** <<hl7-dataformat,HL7 DataFormat>>
+
+* Compression
+** <<gzip-dataformat,GZip DataFormat>>
+** <<zip-dataformat,Zip DataFormat>>
+** <<zipfile-dataformat,Zip File DataFormat>>
+** <<lzf-dataformat,LZF Data Format>>
+** <<tar-dataformat,Tar DataFormat>>
+
+* Security
+** <<crypto-component,Crypto>>
+** <<crypto-component,PGP>>
+** <<secureXML-dataformat,XMLSecurity DataFormat>>
+
+* Misc.
+** <<base64-dataformat,Base64>>
+** <<custom-dataformat,Custom DataFormat>> -- to use your own
+custom implementation
+** <<mime-multipart-dataformat,MIME-Multipart>>
+** <<rss-dataformat,RSS>>
+** <<tidymarkup-dataformat,TidyMarkup>>
+** <<syslog-dataformat,Syslog>>
+** <<ical-dataformat,ICal>>
+** <<barcode-dataformat,Barcode>> -- to read and generate barcodes
+(QR-Code, PDF417, ...)
+
+And related is the following:
+
+* <<dataformat-component,DataFormat Component>> for working with
+ Data Formats as if it was a regular link:component.adoc[Component]
+ supporting link:endpoint.adoc[Endpoints] and link:uris.adoc[URIs].
+* link:dozer-type-conversion.adoc[Dozer Type Conversion] using Dozer for
+ type converting POJOs
+
+[[DataFormat-Unmarshalling]]
+==== Unmarshalling
+
+If you receive a message from one of the Camel
+link:component.adoc[Components] such as <<file-component,File>>,
+<<http-component,HTTP>> or <<jms-component,JMS>> you often want to unmarshal
+the payload into some bean so that you can process it using some
+link:bean-integration.adoc[Bean Integration] or perform
+link:predicate.adoc[Predicate] evaluation and so forth. To do this use
+the `unmarshal` word in the link:dsl.adoc[DSL] in Java or the
+link:xml-configuration.adoc[XML Configuration].
+
+For example:
+
+[source,java]
+----
+DataFormat jaxb = new JaxbDataFormat("com.acme.model");
+
+from("activemq:My.Queue").
+ unmarshal(jaxb).
+ to("mqseries:Another.Queue");
+----
+
+The above uses a named DataFormat of `jaxb` which is configured with a
+number of Java package names. You can if you prefer use a named
+reference to a data format which can then be defined in your
+link:registry.adoc[Registry] such as via your link:spring.adoc[Spring]
+XML file.
+
+You can also use the DSL itself to define the data format as you use it.
+For example the following uses Java serialization to unmarshal a binary
+file then send it as an ObjectMessage to link:activemq.adoc[ActiveMQ]
+
+[source,java]
+----
+from("file://foo/bar").
+ unmarshal().serialization().
+ to("activemq:Some.Queue");
+----
+
+[[DataFormat-Marshalling]]
+==== Marshalling
+
+Marshalling is the opposite of unmarshalling, where a bean is marshalled
+into some binary or textual format for transmission over some transport
+via a Camel link:component.adoc[Component]. Marshalling is used in the
+same way as unmarshalling above; in the link:dsl.adoc[DSL] you can use a
+DataFormat instance, you can configure the DataFormat dynamically using
+the DSL or you can refer to a named instance of the format in the
+link:registry.adoc[Registry].
+
+The following example unmarshals via serialization then marshals using a
+named JAXB data format to perform a kind of
+<<MessageTranslator-MessageTranslator,Message Translator>>:
+
+[source,java]
+----
+from("file://foo/bar").
+ unmarshal().serialization().
+ marshal("jaxb").
+ to("activemq:Some.Queue");
+----
+
+[[DataFormat-UsingSpringXML]]
+==== Using Spring XML
+
+This example shows how to configure the data type just once and reuse it
+on multiple routes:
+
+[source,xml]
+----
+<camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
+ <dataFormats>
+ <jaxb id="myJaxb" prettyPrint="true" contextPath="org.apache.camel.example"/>
+ </dataFormats>
+
+ <route>
+ <from uri="direct:start"/>
+ <marshal ref="myJaxb"/>
+ <to uri="direct:marshalled"/>
+ </route>
+ <route>
+ <from uri="direct:marshalled"/>
+ <unmarshal ref="myJaxb"/>
+ <to uri="mock:result"/>
+ </route>
+
+</camelContext>
+----
+
+You can also define reusable data formats as Spring beans:
+
+[source,xml]
+----
+<bean id="myJaxb" class="org.apache.camel.model.dataformat.JaxbDataFormat">
+ <property name="prettyPrint" value="true"/>
+ <property name="contextPath" value="org.apache.camel.example"/>
+</bean>
+----
diff --git a/docs/user-manual/en/defaulterrorhandler.adoc b/docs/user-manual/en/defaulterrorhandler.adoc
index 52a27e1..08d0ad4 100644
--- a/docs/user-manual/en/defaulterrorhandler.adoc
+++ b/docs/user-manual/en/defaulterrorhandler.adoc
@@ -29,7 +29,7 @@ In this route below, any exception thrown in, eg the `validateOrder`
bean, will be propagated back to the caller via the jetty endpoint. It
will return an HTTP error message back to the client.
-[source,brush:,java;,gutter:,false;,theme:,Default]
+[source,java]
----
from("jetty:http://localhost/myservice/order")
.to("bean:validateOrder")
@@ -40,7 +40,7 @@ We can add an *onException* in case we want to catch certain exceptions
and route them differently, for instance to catch a
*ValidationException* and return a fixed response to the caller.
-[source,brush:,java;,gutter:,false;,theme:,Default]
+[source,java]
----
onException(ValidationException.class)
.handled(true)
diff --git a/docs/user-manual/en/dsl.adoc b/docs/user-manual/en/dsl.adoc
index 91b4b80..b5e4482 100644
--- a/docs/user-manual/en/dsl.adoc
+++ b/docs/user-manual/en/dsl.adoc
@@ -3,7 +3,7 @@ DSL
~~~
Camel uses a Java _Domain Specific Language_ or DSL for creating
-link:enterprise-integration-patterns.html[Enterprise Integration
+link:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] or Routes in a variety of domain-specific
languages (DSL) as listed below.
diff --git a/docs/user-manual/en/error-handling-in-camel.adoc b/docs/user-manual/en/error-handling-in-camel.adoc
index ede8d92..3b4c436 100644
--- a/docs/user-manual/en/error-handling-in-camel.adoc
+++ b/docs/user-manual/en/error-handling-in-camel.adoc
@@ -141,7 +141,7 @@ kicks in and decides what to do.
An example illustrating this:
-[source,brush:,java;,gutter:,false;,theme:,Default]
+[source,java]
----
errorHandler(deadLetterChannel("jms:queue:dead"));
@@ -174,7 +174,7 @@ just a ERROR logger.
[NOTE]
====
-This applies to all kind of link:components.html[Components] in Camel.
+This applies to all kind of link:component.adoc[Components] in Camel.
The sample above only uses <<bean-component,Bean>> but it's the same for
<<file-component,File>>, <<mail-component,Mail>>,
<<velocity-component,Velocity>> or whatever component you use.
@@ -219,7 +219,7 @@ link:transactionerrorhandler.adoc[TransactionErrorHandler] does *not*
attempt any local redeliveries. You have to configure it to do so, for
instance to set a maximum redelivers to a number > 0.
-See <<TransactionalClient-TransactionalClient,Transactional Client>>
+See <<transactionalClient-eip,Transactional Client>>
for more.
[[ErrorhandlinginCamel-Seealso]]
@@ -228,7 +228,7 @@ for more.
* link:error-handler.adoc[Error Handler]
* <<DeadLetterChannel-DeadLetterChannel,Dead Letter Channel>>
* link:exception-clause.adoc[Exception Clause]
-* <<TransactionalClient-TransactionalClient,Transactional Client>>
+* <<transactionalClient-eip,Transactional Client>>
* link:transactionerrorhandler.adoc[TransactionErrorHandler]
* link:defaulterrorhandler.adoc[DefaultErrorHandler]
* link:try-catch-finally.adoc[Try Catch Finally]
diff --git a/docs/user-manual/en/examples.adoc b/docs/user-manual/en/examples.adoc
index e9939bb..926db38 100644
--- a/docs/user-manual/en/examples.adoc
+++ b/docs/user-manual/en/examples.adoc
@@ -6,7 +6,7 @@ looked at the link:enterprise-integration-patterns.adoc[Enterprise
Integration Patterns], you might want to try out some examples.
Before starting to work on example you may want to
-link:what-are-the-dependencies.adoc[check the requirements for working
+link:faq/what-are-the-dependencies.adoc[check the requirements for working
with Camel]. Then link:running-examples.adoc[Running Examples] describes
how to get the examples to run
diff --git a/docs/user-manual/en/exception-clause.adoc b/docs/user-manual/en/exception-clause.adoc
index e35fcc7..84b86c8 100644
--- a/docs/user-manual/en/exception-clause.adoc
+++ b/docs/user-manual/en/exception-clause.adoc
@@ -763,4 +763,4 @@ Spring DSL as well. Here are a few examples:
* The link:error-handler.adoc[Error Handler] for the general error handling documentation
* The <<DeadLetterChannel-DeadLetterChannel,Dead Letter Channel>> for further details
-* The <<TransactionalClient-TransactionalClient,Transactional Client>> for transactional behavior
+* The <<transactionalClient-eip,Transactional Client>> for transactional behavior
diff --git a/docs/user-manual/en/exchange-pattern.adoc b/docs/user-manual/en/exchange-pattern.adoc
index ef62cd6..ef467ba 100644
--- a/docs/user-manual/en/exchange-pattern.adoc
+++ b/docs/user-manual/en/exchange-pattern.adoc
@@ -5,7 +5,7 @@ Exchange Pattern
There are many different _Message Exchange Patterns_ you can use in
messaging. This concept is also demonstrated in WSDL and JBI's MEPs.
-From there link:enterprise-integration-patterns.html[Enterprise
+From there link:enterprise-integration-patterns.adoc[Enterprise
Integration Patterns] the common examples are
* Request Reply
diff --git a/docs/user-manual/en/expression.adoc b/docs/user-manual/en/expression.adoc
index e71ac4e..172e75a 100644
--- a/docs/user-manual/en/expression.adoc
+++ b/docs/user-manual/en/expression.adoc
@@ -3,7 +3,7 @@ Expressions
~~~~~~~~~~~
Expressions and Predicates can then be used to
-create the various link:enterprise-integration-patterns.html[Enterprise
+create the various link:enterprise-integration-patterns.adoc[Enterprise
Integration Patterns] in the DSL or
Xml Configuration like the
Recipient List. +
diff --git a/docs/user-manual/en/faq.adoc b/docs/user-manual/en/faq.adoc
new file mode 100644
index 0000000..7e3e93f
--- /dev/null
+++ b/docs/user-manual/en/faq.adoc
@@ -0,0 +1,261 @@
+[[FAQ-FAQ]]
+=== FAQ
+
+Here are a list of commonly asked questions and answers. If you have any
+questions which are not on this list, please talk to us on the
+link:mailing-lists.adoc[Mailing Lists].
+
+We link:../../../CONTRIBUTING.md[welcome contributions] and
+this entire website is in
+link:faq/how-does-the-website-work.adoc[the GitHub repository you can send a pull request],
+so please join in and help us make the documentation better!
+
+[[FAQ-GeneralQuestions]]
+==== General Questions
+
+General questions about Camel
+
+* link:faq/can-i-get-commercial-support.adoc[Can I get commercial support?]
+* link:faq/can-i-use-camel-on-java-14.adoc[Can I use Camel on Java 1.4?]
+* link:faq/does-camel-work-on-ibms-jdk.adoc[Does Camel work on IBM's JDK?]
+* link:support.adoc[How can I get help?]
+* link:faq/how-can-i-get-the-source-code.adoc[How can I get the source code?]
+* link:faq/how-does-camel-compare-to-mule.adoc[How does Camel compare to
+Mule?]
+* link:faq/how-does-camel-compare-to-servicemix.adoc[How does Camel compare
+to ServiceMix?]
+* link:faq/how-does-camel-compare-to-servicemix-eip.adoc[How does Camel
+compare to ServiceMix EIP?]
+* link:faq/how-does-camel-compare-to-synapse.adoc[How does Camel compare to
+Synapse?]
+* link:faq/how-does-camel-work.adoc[How does Camel work?]
+* link:faq/how-does-camel-work-with-activemq.adoc[How does Camel work with
+ActiveMQ?]
+* link:faq/how-does-camel-work-with-servicemix.adoc[How does Camel work with
+ServiceMix?]
+* link:faq/how-does-the-camel-api-compare-to.adoc[How does the Camel API
+compare to?]
+* link:faq/how-does-the-website-work.adoc[How does the website work?]
+* link:faq/how-do-i-become-a-committer.adoc[How do I become a committer?]
+* link:faq/how-do-i-compile-the-code.adoc[How do I compile the code?]
+* link:faq/how-do-i-edit-the-website.adoc[How do I edit the website?]
+* link:faq/how-do-i-run-camel-using-java-webstart.adoc[How do I run Camel
+using Java WebStart?]
+* link:faq/if-i-use-servicemix-when-should-i-use-camel.adoc[If I use
+ServiceMix when should I use Camel?]
+* link:faq/is-camel-an-esb.adoc[Is Camel an ESB?]
+* link:faq/is-camel-ioc-friendly.adoc[Is Camel IoC friendly?]
+* link:faq/running-camel-standalone.adoc[Running Camel standalone]
+* link:faq/what-are-the-dependencies.adoc[What are the dependencies?]
+* link:faq/what-is-a-router.adoc[What is a router?]
+* link:faq/what-is-camel.adoc[What is Camel?]
+* link:faq/what-is-the-license.adoc[What is the license?]
+* link:faq/what-jars-do-i-need.adoc[What jars do I need?]
+* link:languages.adoc[What languages are supported?]
+* link:faq/what-platforms-are-supported.adoc[What platforms are supported?]
+* link:faq/why-the-name-camel.adoc[Why the name Camel?]
+
+[[FAQ-UsingCamelQuestions]]
+==== Using Camel Questions
+
+Questions on using Apache Camel
+
+* link:faq/classloader-issue-of-servicemix-camel-component.adoc[Classloader
+issue of servicemix-camel component]
+* link:faq/ho-do-i-specify-which-method-to-use-when-using-beans-in-routes.adoc[Ho
+do I specify which method to use when using beans in routes?]
+* link:faq/how-can-i-create-a-custom-component-or-endpoint.adoc[How can I
+create a custom component or endpoint?]
+* link:faq/how-can-i-get-the-remote-connection-ip-address-from-the-camel-cxf-consumer-.adoc[How
+can I get the remote connection IP address from the camel-cxf consumer
+?]
+* link:faq/how-can-i-stop-a-route-from-a-route.adoc[How can I stop a route
+from a route?]
+* link:faq/how-can-webservice-clients-see-remote-faults-with-stacktraces-when-using-camel-cxf.adoc[How
+can webservice clients see remote faults with stacktraces when using
+camel-cxf?]
+* link:faq/how-does-camel-look-up-beans-and-endpoints.adoc[How does Camel
+look up beans and endpoints?]
+* link:configuring-camel.adoc[How do I add a component?]
+* link:faq/how-do-i-change-the-logging.adoc[How do I change the logging?]
+* link:faq/how-do-i-configure-endpoints.adoc[How Do I Configure Endpoints?]
+* link:faq/how-do-i-configure-password-options-on-camel-endpoints-without-the-value-being-encoded.adoc[How
+do I configure password options on Camel endpoints without the value
+being encoded?]
+* link:faq/how-do-i-configure-the-default-maximum-cache-size-for-producercache-or-producertemplate.adoc[How
+do I configure the default maximum cache size for ProducerCache or
+ProducerTemplate?]
+* link:faq/how-do-i-configure-the-maximum-endpoint-cache-size-for-camelcontext.adoc[How
+do I configure the maximum endpoint cache size for CamelContext?]
+* link:faq/how-do-i-debug-my-route.adoc[How do I debug my route?]
+* link:faq/how-do-i-disable-jmx.adoc[How do I disable JMX?]
+* link:faq/how-do-i-enable-streams-when-debug-logging-messages-in-camel.adoc[How
+do I enable streams when debug logging messages in Camel?]
+* link:faq/how-do-i-handle-failures-when-consuming-for-example-from-a-ftp-server.adoc[How
+do I handle failures when consuming for example from a FTP server?]
+* link:faq/how-do-i-import-rests-from-other-xml-files.adoc[How do I import
+rests from other XML files?]
+* link:faq/how-do-i-import-routes-from-other-xml-files.adoc[How Do I Import
+Routes From Other XML Files?]
+* link:faq/how-do-i-let-jetty-match-wildcards.adoc[How do I let Jetty match
+wildcards?]
+* link:faq/how-do-i-name-my-routes.adoc[How do I name my routes?]
+* link:faq/how-do-i-restart-camelcontext.adoc[How do I restart CamelContext?]
+* link:faq/how-do-i-retrieve-the-thrown-exception-during-processing-an-exchange.adoc[How
+do I retrieve the thrown Exception during processing an Exchange?]
+* link:faq/how-do-i-retry-failed-messages-forever.adoc[How do I retry failed
+messages forever?]
+* link:faq/how-do-i-retry-processing-a-message-from-a-certain-point-back-or-an-entire-route.adoc[How
+do I retry processing a message from a certain point back or an entire
+route?]
+* link:faq/how-do-i-reuse-the-contexttestsupport-class-in-my-unit-tests.adoc[How
+do I reuse the ContextTestSupport class in my unit tests?]
+* link:faq/how-do-i-run-activemq-and-camel-in-jboss.adoc[How do I run
+ActiveMQ and Camel in JBoss?]
+* link:faq/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[How
+do I set the max chars when debug logging messages in Camel?]
+* link:faq/how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc[How
+do I specify time period in a human friendly syntax?]
+* link:faq/how-do-i-use-a-big-uber-jar.adoc[How do I use a big (uber) JAR?]
+* link:faq/how-do-i-use-camel-inside-servicemix.adoc[How do I use Camel
+inside ServiceMix?]
+* link:faq/how-do-i-use-spring-property-placeholder-with-camel-xml.adoc[How
+do I use Spring Property Placeholder with Camel XML?]
+* link:faq/how-do-i-use-uris-with-parameters-in-xml.adoc[How do I use URIs
+with parameters in XML?]
+* link:faq/how-do-i-write-a-custom-processor-which-sends-multiple-messages.adoc[How
+do I write a custom Processor which sends multiple messages?]
+* link:faq/how-should-i-invoke-my-pojos-or-spring-services.adoc[How should I
+invoke my POJOs or Spring Services?]
+* link:faq/how-should-i-package-applications-using-camel-and-activemq.adoc[How
+should I package applications using Camel and ActiveMQ?]
+* link:faq/how-to-avoid-importing-bunch-of-cxf-packages-when-start-up-the-camel-cxf-endpoint-from-osgi-platform-.adoc[How
+to avoid importing bunch of cxf packages when start up the camel-cxf
+endpoint from OSGi platform ?]
+* link:faq/how-to-avoid-sending-some-or-all-message-headers.adoc[How to
+avoid sending some or all message headers?]
+* link:faq/how-to-define-a-static-camel-converter-method-in-scala.adoc[How
+to define a static camel converter method in Scala?]
+* link:faq/how-to-remove-the-http-protocol-headers-in-the-camel-message.adoc[How
+to remove the http protocol headers in the camel message?]
+* link:faq/how-to-send-the-same-message-to-multiple-endpoints.adoc[How to
+send the same message to multiple endpoints?]
+* link:faq/how-to-switch-the-cxf-consumer-between-http-and-https-without-touching-the-spring-configuration.adoc[How
+to switch the CXF consumer between HTTP and HTTPS without touching the
+Spring configuration?]
+* link:faq/how-to-use-a-dynamic-uri-in-to.adoc[How to use a dynamic URI in
+to()?]
+* link:faq/how-to-use-extra-camel-componets-in-servicemix-camel.adoc[How to
+use extra camel componets in servicemix-camel?]
+* link:faq/how-to-validate-the-camel-1x-context-xml-from-apache-camel-web-site.adoc[How
+to validate the camel-1.x context xml from Apache Camel web site?]
+* link:faq/is-there-an-ide.adoc[Is there an IDE?]
+* link:faq/should-i-deploy-camel-inside-the-activemq-broker-or-in-another-application.adoc[Should
+I deploy Camel inside the ActiveMQ broker or in another application?]
+* link:faq/using-camel-core-testsjar.adoc[Using camel-core-tests.jar]
+* link:faq/using-getin-or-getout-methods-on-exchange.adoc[Using getIn or
+getOut methods on Exchange]
+* link:faq/why-cant-i-use-sign-in-my-password.adoc[Why can't I use + sign in
+my password?]
+* link:faq/why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc[Why
+can I not use when or otherwise in a Java Camel route?]
+* link:faq/why-does-ftp-component-not-download-any-files.adoc[Why does FTP
+component not download any files?]
+* link:faq/why-does-my-file-consumer-not-pick-up-the-file-and-how-do-i-let-the-file-consumer-use-the-camel-error-handler.adoc[Why
+does my file consumer not pick up the file, and how do I let the file
+consumer use the Camel error handler?]
+* link:faq/why-does-useoriginalmessage-with-error-handler-not-work-as-expected.adoc[Why
+does useOriginalMessage with error handler not work as expected?]
+* link:faq/why-do-my-message-lose-its-headers-during-routing.adoc[Why do my
+message lose its headers during routing?]
+* link:faq/why-is-my-message-body-empty.adoc[Why is my message body empty?]
+* link:faq/why-is-my-processor-not-showing-up-in-jconsole.adoc[Why is my
+processor not showing up in JConsole?]
+* link:faq/why-is-the-exception-null-when-i-use-onexception.adoc[Why is the
+exception null when I use onException?]
+* link:faq/why-use-multiple-camelcontext.adoc[Why use multiple CamelContext?]
+
+[[FAQ-LoggingQuestions]]
+==== Logging Questions
+
+Questions on logging output from Camel to a console, using the
+link:log.adoc[Log] endpoint or JDK 1.4 logging or Log4j etc
+
+* link:faq/how-do-i-enable-debug-logging.adoc[How do I enable debug logging?]
+* link:faq/how-do-i-use-java-14-logging.adoc[How do I use Java 1.4 logging?]
+* link:faq/how-do-i-use-log4j.adoc[How do I use log4j?]
+
+[[FAQ-CamelEndpointQuestions]]
+==== Camel Endpoint Questions
+
+Questions on using the various Camel link:components.adoc[Components]
+and link:endpoint.adoc[Endpoint] implementations
+
+* link:faq/how-do-i-invoke-camel-routes-from-jbi.adoc[How do I invoke Camel
+routes from JBI?]
+* link:faq/how-do-i-make-my-jms-endpoint-transactional.adoc[How Do I Make My
+JMS Endpoint Transactional?]
+* link:faq/how-do-i-set-the-mep-when-interacting-with-jbi.adoc[How do I set
+the MEP when interacting with JBI?]
+* link:faq/how-do-the-direct-event-seda-and-vm-endpoints-compare.adoc[How do
+the direct, event, seda and vm endpoints compare?]
+* link:faq/how-do-the-timer-and-quartz-endpoints-compare.adoc[How do the
+Timer and Quartz endpoints compare?]
+
+[[FAQ-ComponentQuestions]]
+==== Component Questions
+
+Questions on using specific components
+
+[[FAQ-JMSQuestions]]
+===== JMS Questions
+
+Questions on using the <<jms-component,JMS>> endpoints in Camel
+
+* link:faq/why-does-my-jms-route-only-consume-one-message-at-once.adoc[Why
+does my JMS route only consume one message at once?]
+
+[[FAQ-CommonProblems]]
+==== Common Problems
+
+Common Problems that people have when riding the Camel
+
+* link:faq/exception-beandefinitionstoreexception.adoc[Exception -
+BeanDefinitionStoreException]
+* link:faq/exception-javaxnamingnoinitialcontextexception.adoc[Exception -
+javax.naming.NoInitialContextException]
+* link:faq/exception-orgapachecamelnosuchendpointexception.adoc[Exception -
+org.apache.camel.NoSuchEndpointException]
+* link:faq/exception-orgxmlsaxsaxparseexception.adoc[Exception -
+org.xml.sax.SAXParseException]
+* link:faq/memory-leak-when-adding-and-removing-routes-at-runtime.adoc[Memory
+leak when adding and removing routes at runtime]
+* link:faq/why-do-camel-throw-so-many-noclassdeffoundexception-on-startup.adoc[Why
+do Camel throw so many NoClassDefFoundException on startup?]
+* link:faq/why-does-camel-use-too-many-threads-with-producertemplate.adoc[Why
+does Camel use too many threads with ProducerTemplate?]
+* link:faq/why-does-maven-not-download-dependencies.adoc[Why does maven not
+download dependencies?]
+
+[[FAQ-Acknowledgment]]
+==== Acknowledgment
+
+Many thanks to the following organizations for helping the Camel
+project.
+
+[width="100%",cols="50%,50%",]
+|=======================================================================
+|image:http://www.structure101.com/structure101-java/images/webapp.gif[image]
+|http://www.headwaysoftware.com/[Headway Software] provided free
+licenses of
+http://www.headwaysoftware.com/products/structure101/index.php[Structure101]
+for analyzing and managing the
+http://www.structure101.com/structure101-java/tracker/camel/1.2.0/summary.html[architecture
+of Camel] Java code.
+
+|image:https://www.yourkit.com/images/yk_logo.png[image]
+|https://www.yourkit.com/[YourKit], LLC kindly provide free licenses for
+the YourKit Java Profiler to open source projects. YourKit Java Profiler
+is primarily used to investigate performance and memory leak issues
+reported in Apache Camel.
+|=======================================================================
diff --git a/docs/user-manual/en/faq/can-i-get-commercial-support.adoc b/docs/user-manual/en/faq/can-i-get-commercial-support.adoc
new file mode 100644
index 0000000..ee0f1b4
--- /dev/null
+++ b/docs/user-manual/en/faq/can-i-get-commercial-support.adoc
@@ -0,0 +1,4 @@
+[[CanIgetcommercialsupport-CanIgetcommercialsupport]]
+=== Can I get commercial support?
+
+Absolutely, see our link:../support.adoc[Support] page for more details.
diff --git a/docs/user-manual/en/faq/can-i-use-camel-on-java-14.adoc b/docs/user-manual/en/faq/can-i-use-camel-on-java-14.adoc
new file mode 100644
index 0000000..2b465d7
--- /dev/null
+++ b/docs/user-manual/en/faq/can-i-use-camel-on-java-14.adoc
@@ -0,0 +1,9 @@
+[[CanIuseCamelonJava1.4-CanIuseCamelonJava1.4]]
+=== Can I use Camel on Java 1.4?
+
+Apache Camel was developed to run on Java 1.5 or later to take advantage
+of the new language features like generics and annotations together with
+using the Java 5 concurrency code. Starting with version 2.7.0, only
+Java 1.6 is supported.
+
+Starting with version 2.10.0, Java 1.7 is supported, but not required.
diff --git a/docs/user-manual/en/faq/does-camel-work-on-ibms-jdk.adoc b/docs/user-manual/en/faq/does-camel-work-on-ibms-jdk.adoc
new file mode 100644
index 0000000..1b5df2c
--- /dev/null
+++ b/docs/user-manual/en/faq/does-camel-work-on-ibms-jdk.adoc
@@ -0,0 +1,32 @@
+[[DoesCamelworkonIBMsJDK-DoesCamelworkonIBMsJDK]]
+=== Does Camel work on IBM's JDK?
+
+Yes, we've tested Camel with IBM's JDK on the AIX and Linux platforms.
+There are a few things to look out for though.
+
+[[DoesCamelworkonIBMsJDK-Exceptionusingcamel-http]]
+==== Exception using camel-http
+
+You may get a `sun.io.MalformedInputException` when using camel-http on
+IBM's JDK.
+http://www-128.ibm.com/developerworks/java/jdk/linux/142/runtimeguide.lnx.en.html
+lists a possible solution: if `LANG=en_US.UTF-8`, just set it to
+`LANG=en_US`.
+
+[[DoesCamelworkonIBMsJDK-Buildingcamel-springcomponent]]
+==== Building camel-spring component
+
+The schema generation portion of camel-spring uses Sun specific tools
+and thus cannot run on IBM's JDK. It will currently try to download an
+XSD generated from a previous build and then run the tests against that.
+So, if you need to change Camel's model, you will need to rebuild
+camel-spring on another JDK (preferably a Sun JDK).
+
+[[DoesCamelworkonIBMsJDK-Rubyscriptingsupport]]
+==== Ruby scripting support
+
+Ruby scripting on IBM's JDK works for Camel 2.0 and onward. For earlier
+versions you'll need to use one of the other
+link:../scripting-languages.adoc[Scripting Languages]. See
+https://issues.apache.org/activemq/browse/CAMEL-1030[CAMEL-1030] for
+more details.
diff --git a/docs/user-manual/en/faq/how-can-i-get-the-source-code.adoc b/docs/user-manual/en/faq/how-can-i-get-the-source-code.adoc
new file mode 100644
index 0000000..c488cb9
--- /dev/null
+++ b/docs/user-manual/en/faq/how-can-i-get-the-source-code.adoc
@@ -0,0 +1,50 @@
+[[HowcanIgetthesourcecode-HowcanIgetthesourcecode]]
+=== How can I get the source code?
+
+[WARNING]
+====
+Apache Camel code repository was moved to git. The old svn repo will not
+be updated.
+====
+
+[[HowcanIgetthesourcecode-WebBrowsingofgit]]
+==== Web Browsing of git
+
+To browse via the web:
+
+https://git-wip-us.apache.org/repos/asf?p=camel.git
+
+[[HowcanIgetthesourcecode-WebBrowingUsingFishEye]]
+==== Web Browing Using FishEye
+
+A hearty thanks to http://atlassian.com/[Atlassian] for providing
+http://cenqua.com/fisheye/[FishEye] hosting for Camel. Below is the URL
+to browse the Subversion repo via FishEye:
+
+https://fisheye6.atlassian.com/browse/camel-git
+
+[[HowcanIgetthesourcecode-Checkingoutfromgit]]
+==== Checking out from git
+
+----
+git clone https://git-wip-us.apache.org/repos/asf/camel.git
+----
+
+Only project developers can commit to the git via this method. SSH must
+be installed on your client machine. Enter your site password when
+prompted.
+
+[[HowcanIgetthesourcecode-UsingGitHub]]
+==== Using GitHub
+
+The source code is https://github.com/apache/camel/[mirrored to GitHub],
+so you can also checkout the source code from GitHub, if you are
+familiar with using GitHub. By using GitHub you can submit pull requests
+to the project using the standard GitHub way.
+
+https://github.com/apache/camel/
+
+[[HowcanIgetthesourcecode-Buildingthecode]]
+==== Building the code
+
+To then build the code see link:../building.adoc[Building].
diff --git a/docs/user-manual/en/faq/how-do-i-become-a-committer.adoc b/docs/user-manual/en/faq/how-do-i-become-a-committer.adoc
new file mode 100644
index 0000000..25c6db2
--- /dev/null
+++ b/docs/user-manual/en/faq/how-do-i-become-a-committer.adoc
@@ -0,0 +1,61 @@
+[[HowdoIbecomeacommitter-HowcanIbecomeacommitter]]
+=== How can I become a committer
+
+First of all you need to get involved and
+link:../../../../CONTRIBUTING.md[Contribute] via the mail list, forums, edit the
+documentation, work on the issue tracker and submit patches.
+
+Once you're contributing and your work is good, one of our
+link:../team.adoc[Team] may invite you to be a committer (after we've
+called a vote). When that happens, if you accept, the following process
+kicks into place...
+
+Note that becoming a committer is not just about submitting some
+patches; its also about helping out on the development and user
+link:../mailing-lists.adoc[Discussion Forums],
+helping with documentation and the issue tracker.
+
+[[HowdoIbecomeacommitter-Becomingacommittersteps]]
+==== Becoming a committer steps
+
+* Download and print the Apache Contributor License Agreement from
+http://www.apache.org/dev/new-committers-guide.html[here]. You need to
+sign it and fax it to Apache. In the past I've found its often faster to
+also post it via snail mail :smile:
+* wait for your name to appear on the list of
+http://people.apache.org/~jim/committers.html#unlistedclas[received
+CLAs]
+* once thats done let us know and we can apply to Apache Infrastructure
+to have your account created; we'll also need to know
+** your full name
+** your preferred email address
+** your preferred unix account name
+
+[[HowdoIbecomeacommitter-GettingstartedatApache]]
+==== Getting started at Apache
+
+Firstly add yourself to the link:../team.adoc[Team] page
+
+Now go read the instructions on the
+http://www.apache.org/dev/new-committers-guide.html[new committers guide].
+Its also worth viewing http://www.apache.org/dev.
+
+[[HowdoIbecomeacommitter-Moreinformation]]
+==== More information
+
+You can find more information about being a
+http://www.apache.org/dev/committers.html[committer at Apache here].
+
+[[HowdoIbecomeacommitter-GettingKarmainJIRAandConfluence]]
+==== Getting Karma in JIRA and Confluence
+
+Mail the dev list and ask for karma for JIRA / Confluence giving them
+details of your username you used to register with them both. We can
+then grant the necessary karma so you can start grabbing JIRA issues or
+editing the wiki
+
+[[HowdoIbecomeacommitter-GettingKarmainJenkinsHudson]]
+==== Getting Karma in Jenkins / Hudson
+
+Mail the PMC chair and ask for karma for Jenkins / Hudson as described
+http://wiki.apache.org/general/Hudson[here].
diff --git a/docs/user-manual/en/faq/how-do-i-change-the-logging.adoc b/docs/user-manual/en/faq/how-do-i-change-the-logging.adoc
new file mode 100644
index 0000000..fe48a44
--- /dev/null
+++ b/docs/user-manual/en/faq/how-do-i-change-the-logging.adoc
@@ -0,0 +1,20 @@
+[[HowdoIchangethelogging-HowdoIchangethelogging]]
+=== How do I change the logging?
+
+We use https://commons.apache.org/proper/commons-logging/[commons-logging] to
+log information in the broker client and the broker itself so you can
+fully configure the logging levels desired, whether to log to files or
+the console, as well as the underlying logging implementation (Log4J,
+Java SE logger, etc.) you wish to use. For Log4J, full instructions are
+in its https://logging.apache.org/log4j/2.x/manual/index.html[manual], but in
+a nutshell:
+
+* Add `log4j.jar` to your classpath
+* Create a `log4j.properties` file specifying desired logging
+configuration (The Camel distribution has example `log4j.properties` files
+you can use -- see for example in the
+link:../../../../examples/camel-example-bam/src/main/resources[/examples/camel-example-bam/src/main/resources] folder.)
+* Place the `log4j.properties` file in the folder where the compiled
+`.class` files are located (typically the `classes` folder) -- this will
+place the properties file on the classpath, where it needs to be at
+runtime.
diff --git a/docs/user-manual/en/faq/how-do-i-compile-the-code.adoc b/docs/user-manual/en/faq/how-do-i-compile-the-code.adoc
new file mode 100644
index 0000000..cfd54be
--- /dev/null
+++ b/docs/user-manual/en/faq/how-do-i-compile-the-code.adoc
@@ -0,0 +1,4 @@
+[[HowdoIcompilethecode-HowdoIcompilefromthesourcecode]]
+=== How do I compile from the source code?
+
+See the link:../building.adoc[Building] page.
diff --git a/docs/user-manual/en/how-do-i-configure-endpoints.adoc b/docs/user-manual/en/faq/how-do-i-configure-endpoints.adoc
similarity index 99%
rename from docs/user-manual/en/how-do-i-configure-endpoints.adoc
rename to docs/user-manual/en/faq/how-do-i-configure-endpoints.adoc
index 780de47..9b48d24 100644
--- a/docs/user-manual/en/how-do-i-configure-endpoints.adoc
+++ b/docs/user-manual/en/faq/how-do-i-configure-endpoints.adoc
@@ -83,7 +83,7 @@ Using Guice
^^^^^^^^^^^
You can also use Guice as the dependency injection
-framework. For example see the link:guice-jms-example.html[Guice JMS
+framework. For example see the link:../guice-jms-example.adoc[Guice JMS
Example].
[[HowdoIconfigureendpoints-UsingSpringXML]]
diff --git a/docs/user-manual/en/faq/how-do-i-edit-the-website.adoc b/docs/user-manual/en/faq/how-do-i-edit-the-website.adoc
new file mode 100644
index 0000000..863755f
--- /dev/null
+++ b/docs/user-manual/en/faq/how-do-i-edit-the-website.adoc
@@ -0,0 +1,18 @@
+[[HowdoIeditthewebsite-HowdoIeditthewebsite]]
+=== How do I edit the website?
+
+The website is all contained in
+https://github.com/apache/camel/[the GitHub repository] so that you can
+link:../../../../CONTRIBUTING.md[contribute] providing you are happy to license
+all your contributions under the
+http://www.apache.org/licenses/LICENSE-2.0[Apache Software License version 2.0]
+
+[[HowdoIeditthewebsite-Howtoedit]]
+==== How to edit
+
+TODO: Write how it works and how to contribute to the web site.
+
+[[HowdoIeditthewebsite-Howthesiteworks]]
+==== How the site works
+
+TODO: Write how it works and how to contribute to the web site.
diff --git a/docs/user-manual/en/faq/how-do-i-run-camel-using-java-webstart.adoc b/docs/user-manual/en/faq/how-do-i-run-camel-using-java-webstart.adoc
new file mode 100644
index 0000000..c6418ce
--- /dev/null
+++ b/docs/user-manual/en/faq/how-do-i-run-camel-using-java-webstart.adoc
@@ -0,0 +1,83 @@
+[[HowdoIrunCamelusingJavaWebStart-HowdoIrunCamelusingJavaWebStart]]
+=== How do I run Camel using Java WebStart?
+
+Camel 1.5 has support for starting using Java WebStart.
+
+[WARNING]
+====
+**Be Careful**
+
+However there is a restriction to *not* use the version attribute for
+*camel* jars.
+====
+
+What you need to have in mind is that Camel will scan for resources in
+.jar files on-the-fly and therefore the .jars is loaded using http.
+Therefore the http URLs in the .jnlp file must be complete in the *href*
+tag.
+
+[[HowdoIrunCamelusingJavaWebStart-Mavenconfiguration]]
+==== Maven configuration
+
+If you use Maven to generate your *.jnlp* file then check out these
+links: http://mojo.codehaus.org/webstart/webstart-maven-plugin/
+
+You need to configure your maven to not output the jar version attribute
+(`outputJarVersion=false`) as started in this snippet:
+
+[source,xml]
+----
+<plugin>
+ <groupId>org.codehaus.mojo.webstart</groupId>
+ <artifactId>webstart-maven-plugin</artifactId>
+ .....
+ <configuration>
+ .....
+ <jnlpFiles>
+ <jnlpFile>
+ <templateFilename>jnlpTemplate.vm</templateFilename>
+ <outputFilename>appl.jnlp</outputFilename>
+ <jarResources>
+ <jarResource>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-core</artifactId>
+ <version>${camel-version}</version>
+ <!-- set the outputJarVersion to false appends the version to the jar filename in the href -->
+ <outputJarVersion>false</outputJarVersion>
+ </jarResource>
+ <jarResource>
+ <groupId>org.apache.activemq</groupId>
+ <artifactId>activemq-core</artifactId>
+ <version>${activemq-version}</version>
+ <outputJarVersion>false</outputJarVersion>
+ </jarResource>
+ .....
+ </jarResources>
+ <jnlpFile>
+ <jnlpFiles>
+ .....
+ <configuration>
+<plugin>
+----
+
+And a sample of the generated *appl.jnlp* file:
+
+[source,xml]
+----
+<jnlp .....>
+ .......
+ <resources>
+ .......
+ <jar href="camel-core-1.4.jar"/>
+ <jar href="activemq-core-5.1.jar"/>
+ .......
+ <jar href="spring-core.jar" version="2.5.5"/>
+ </resources>
+</jnlp>
+----
+
+*What to notice:*
+
+To let Camel run using Java WebStart the `<jar href>` tag must *not* use
+the version attribute for the *camel-xxx.jars*. See the difference
+between Camel and the spring jar.
diff --git a/docs/user-manual/en/how-do-i-use-spring-property-placeholder-with-camel-xml.adoc b/docs/user-manual/en/faq/how-do-i-use-spring-property-placeholder-with-camel-xml.adoc
similarity index 97%
rename from docs/user-manual/en/how-do-i-use-spring-property-placeholder-with-camel-xml.adoc
rename to docs/user-manual/en/faq/how-do-i-use-spring-property-placeholder-with-camel-xml.adoc
index 7b9283c..6442268 100644
--- a/docs/user-manual/en/how-do-i-use-spring-property-placeholder-with-camel-xml.adoc
+++ b/docs/user-manual/en/faq/how-do-i-use-spring-property-placeholder-with-camel-xml.adoc
@@ -65,7 +65,7 @@ http://jira.springframework.org/browse/SPR-4466[SPR-4466]
===== Bridge Spring and Camel property placeholders
From Camel 2.10 onwards you can bridge Spring and Camel property
-placeholders, see link:using-propertyplaceholder.adoc[Using
+placeholders, see link:../using-propertyplaceholder.adoc[Using
PropertyPlaceholder] for more details.
Here is a trick that you can use to define the uri in a property file
diff --git a/docs/user-manual/en/faq/how-does-camel-compare-to-mule.adoc b/docs/user-manual/en/faq/how-does-camel-compare-to-mule.adoc
new file mode 100644
index 0000000..cdf99fc
--- /dev/null
+++ b/docs/user-manual/en/faq/how-does-camel-compare-to-mule.adoc
@@ -0,0 +1,29 @@
+[[HowdoesCamelcomparetoMule-HowdoesCamelcomparetoMule]]
+=== How does Camel compare to Mule?
+
+This FAQ entry was written when Mule 1.x and 2.x existed. It doesn't
+cater for how Mule may go in Mule 3.x.
+
+I guess from 30,000 feet they're kinda
+link:why-the-name-camel.adoc[similar beasts]; they're both kinds of
+routing/mediation engines. The main differences are as follows:
+
+* Camel uses a Java link:../dsl.adoc[Domain Specific Language] in addition
+ to Spring XML for configuring the routing rules and providing
+ link:../enterprise-integration-patterns.adoc[Enterprise Integration
+ Patterns]
+* Camel's API is smaller & cleaner (IMHO) and is closely aligned with
+ the APIs of JBI, <<cxf-component,CXF>> and
+ <<jms-component,JMS>>; based around message exchanges (with in and optional
+ out messages) which more closely maps to REST, WS, WSDL & JBI than the
+ UMO model Mule is based on
+* Camel allows the underlying transport details to be easily exposed
+ (e.g. the `JmsExchange`, `JbiExchange`, `HttpExchange` objects expose all the
+ underlying transport information & behaviour if its required). See
+ link:how-does-the-camel-api-compare-to.adoc[How does the Camel API
+ compare to]
+* Camel supports an implicit link:../type-converter.adoc[Type Converter] in
+ the core API to make it simpler to connect components together requiring
+ different types of payload & headers
+* Camel uses the link:../notice.md[Apache 2 License] rather than Mule's more restrictive
+ commercial license
diff --git a/docs/user-manual/en/faq/how-does-camel-compare-to-servicemix-eip.adoc b/docs/user-manual/en/faq/how-does-camel-compare-to-servicemix-eip.adoc
new file mode 100644
index 0000000..515c1d1
--- /dev/null
+++ b/docs/user-manual/en/faq/how-does-camel-compare-to-servicemix-eip.adoc
@@ -0,0 +1,61 @@
+[[HowdoesCamelcomparetoServiceMixEIP-HowdoesCamelcomparetoServiceMixEIP]]
+=== How does Camel compare to ServiceMix EIP
+
+http://servicemix.apache.org/servicemix-eip.html[ServiceMix EIP] was the
+ancestor though they both do similar things.
+
+The main difference with ServiceMix EIP is its integrated into the
+existing ServiceMix XBean XML configuration whereas Camel has more
+link:../enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns] and can be used outside of JBI (e.g. just with pure
+<<jms-component,JMS>> or <<mina-component,MINA>>). Also Camel supports a
+link:../dsl.adoc[Java DSL] or link:../spring.adoc[XML configuration].
+
+[[HowdoesCamelcomparetoServiceMixEIP-ConvertingfromServiceMixEIPtoCamel]]
+==== Converting from ServiceMix EIP to Camel
+
+Here's an example of a servicemix-eip route:
+
+[source,xml]
+----
+<eip:message-filter service="test:messageFilter" endpoint="endpoint">
+ <eip:target>
+ <eip:exchange-target service="test:trace3" />
+ </eip:target>
+ <eip:filter>
+ <eip:xpath-predicate xpath="count(/test:world) = 1" namespaceContext="#nsContext"/>
+ </eip:filter>
+</eip:message-filter>
+----
+
+Here's the equivalent Camel code in XML:
+
+[source,xml]
+----
+<route>
+ <from uri="jbi:endpoint:test:messageFilter:endpoint">
+ <filter>
+ <xpath>count(/test:world) = 1</xpath>
+ <to uri="jbi:service:test:trace3"/>
+ </filter>
+</route>
+----
+
+Or Java:
+
+[source,java]
+----
+from("jbi:endpoint:test:messageFilter:endpoint").
+ filter(ns.xpath("count(/test:world) = 1")).
+ to("jbi:service:test:trace3");
+----
+
+[[HowdoesCamelcomparetoServiceMixEIP-SeeAlso]]
+==== See Also
+
+* link:how-does-camel-work-with-servicemix.adoc[How does Camel work with
+ServiceMix]
+* link:how-does-camel-compare-to-servicemix.adoc[How does Camel compare
+to ServiceMix]
+* http://incubator.apache.org/servicemix/servicemix-camel.html[ServiceMix
+Camel plugin]
diff --git a/docs/user-manual/en/faq/how-does-camel-compare-to-servicemix.adoc b/docs/user-manual/en/faq/how-does-camel-compare-to-servicemix.adoc
new file mode 100644
index 0000000..89a4d0b
--- /dev/null
+++ b/docs/user-manual/en/faq/how-does-camel-compare-to-servicemix.adoc
@@ -0,0 +1,43 @@
+[[HowdoesCamelcomparetoServiceMix-HowdoesCamelcomparetoServiceMix]]
+=== How does Camel compare to ServiceMix?
+
+Camel is smart routing and mediation engine which implements the
+link:../enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns] and is designed to be used either inside an ESB like
+ServiceMix, in a Message Broker like ActiveMQ or in a smart endpoint or
+web services framework like CXF. ServiceMix is an ESB, a JBI container
+and an integration platform. So they both address different needs though
+they are both designed to work great together.
+
+Camel can be deployed as a component within ServiceMix to provide
+link:../enterprise-integration-patterns.adoc[EIP routing and mediation]
+between existing JBI components together with communicating with any of
+the other Camel link:../component.adoc[Components] along with defining new
+JBI components on the NMR. So Camel is similar to the
+link:how-does-camel-compare-to-servicemix-eip.adoc[ServiceMix EIP
+component].
+
+To work with Camel and ServiceMix you take your Camel
+link:../spring.adoc[Spring] configuration and turn it into a JBI Service
+Unit using the maven plugin or archetype. For more details see
+http://incubator.apache.org/servicemix/servicemix-camel.html[ServiceMix
+Camel plugin].
+
+So you could start out using Camel routing inside your application via
+link:../dsl.adoc[Java] or link:../spring.adoc[Spring]; then later on if you
+choose to you could wrap up your routing and mediation rules as a JBI
+deployment unit and drop it into your ServiceMix ESB. This provides a
+nice agile approach to integration; start small & simple on an endpoint
+then as and when you need to migrate your integration components into
+your ESB for more centralised management, governance and operational
+monitoring etc.
+
+[[HowdoesCamelcomparetoServiceMix-SeeAlso]]
+==== See Also
+
+* link:how-does-camel-work-with-servicemix.adoc[How does Camel work with
+ServiceMix]
+* link:how-does-camel-compare-to-servicemix-eip.adoc[How does Camel
+compare to ServiceMix EIP]
+* http://incubator.apache.org/servicemix/servicemix-camel.html[ServiceMix
+Camel plugin]
diff --git a/docs/user-manual/en/faq/how-does-camel-compare-to-synapse.adoc b/docs/user-manual/en/faq/how-does-camel-compare-to-synapse.adoc
new file mode 100644
index 0000000..9502e02
--- /dev/null
+++ b/docs/user-manual/en/faq/how-does-camel-compare-to-synapse.adoc
@@ -0,0 +1,32 @@
+[[HowdoesCamelcomparetoSynapse-HowdoesCamelcomparetoSynapse]]
+=== How does Camel compare to Synapse?
+
+We are Camel developers so take what you read here with a pinch of salt.
+If you want to read a less biased comparison
+http://rajith.2rlabs.com/2008/02/11/synapse-vs-camel/[try reading this
+review which has a slight Synapse bias since the author mostly uses
+Synapse] :smile:
+
+However we think the main differences are:
+
+* the Camel community is way more active according to the
+http://www.nabble.com/Camel-f22882.html[nabble statistics] (Synapse is
+inside the Apache Web Services bar) or by comparing
+http://apache.markmail.org/search/?q=camel[Camel] and
+http://apache.markmail.org/search/?q=synapse[Synapse] on markmail.
+* Camel is the default routing engine included in
+http://activemq.apache.org/[Apache ActiveMQ] for Message Orientated
+middleware with EIP and http://servicemix.apache.org/[Apache ServiceMix]
+the ESB based around OSGi and JBI at Apache - both of which are
+http://www.nabble.com/Apache-f90.html[very popular too].
+* Camel is designed from the ground up around
+link:../enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns] -- having an EIP pattern language implemented in
+link:../dsl.adoc[Java], link:../spring.adoc[Spring XML],
+link:../scala-dsl.adoc[Scala] and link:../groovy-dsl.adoc[Groovy] as well as
+link:../visualisation.adoc[EIP Visualisations].
+* Camel is designed to work with pretty much all kinds of
+link:../transport.adoc[transport] as well as working with any
+link:../data-format.adoc[Data Format]. When we first looked at Synapse it
+was based around Axis 2 and WS-* though apparently thats no longer the
+case.
diff --git a/docs/user-manual/en/faq/how-does-camel-work-with-activemq.adoc b/docs/user-manual/en/faq/how-does-camel-work-with-activemq.adoc
new file mode 100644
index 0000000..715aa0a
--- /dev/null
+++ b/docs/user-manual/en/faq/how-does-camel-work-with-activemq.adoc
@@ -0,0 +1,21 @@
+[[HowdoesCamelworkwithActiveMQ-HowdoesCamelworkwithActiveMQ]]
+=== How does Camel work with ActiveMQ?
+
+You can use Camel to do smart routing and implement the
+link:../enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns] inside:
+
+* the ActiveMQ message broker
+* the ActiveMQ JMS client
+
+So Camel can route messages to and from <<mail-component,Mail>>,
+<<file-component,File>>, <<ftp-component,FTP>>, <<jpa-component,JPA>>,
+<<xmpp-component,XMPP>> other <<jms-component,JMS>> providers and any of the
+other Camel link:../component.adoc[Components] as well as implementating
+all of the link:../enterprise-integration-patterns.adoc[Enterprise
+Integration Patterns] such as link:content-based-router.html[Content
+Based Router] or <<MessageTranslator-MessageTranslator,Message Translator>>.
+
+For more details see
+http://activemq.apache.org/enterprise-integration-patterns.html[ActiveMQ
+EIP].
diff --git a/docs/user-manual/en/faq/how-does-camel-work-with-servicemix.adoc b/docs/user-manual/en/faq/how-does-camel-work-with-servicemix.adoc
new file mode 100644
index 0000000..f3e0717
--- /dev/null
+++ b/docs/user-manual/en/faq/how-does-camel-work-with-servicemix.adoc
@@ -0,0 +1,25 @@
+[[HowdoesCamelworkwithServiceMix-HowdoesCamelworkwithServiceMix]]
+=== How does Camel work with ServiceMix?
+
+You can use Camel to do smart routing and implement the
+link:../enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns] inside of the JBI container, routing between existing JBI
+components together with communicating with any of the other Camel
+link:../component.adoc[Components].
+
+To do this you take your Camel link:../spring.adoc[Spring] configuration
+and turn it into a JBI Service Unit using the maven plugin or archetype.
+
+For more details see
+http://incubator.apache.org/servicemix/servicemix-camel.html[ServiceMix
+Camel plugin].
+
+[[HowdoesCamelworkwithServiceMix-SeeAlso]]
+==== See Also
+
+* link:how-does-camel-work-with-servicemix.adoc[How does Camel work with
+ServiceMix]
+* link:how-does-camel-compare-to-servicemix.adoc[How does Camel compare
+to ServiceMix]
+* http://incubator.apache.org/servicemix/servicemix-camel.html[ServiceMix
+Camel plugin]
diff --git a/docs/user-manual/en/faq/how-does-camel-work.adoc b/docs/user-manual/en/faq/how-does-camel-work.adoc
new file mode 100644
index 0000000..907913a
--- /dev/null
+++ b/docs/user-manual/en/faq/how-does-camel-work.adoc
@@ -0,0 +1,5 @@
+[[HowdoesCamelwork-HowdoesCamelwork]]
+=== How does Camel work?
+
+Please see the link:../architecture.adoc[Architecture] for details of how
+things work.
diff --git a/docs/user-manual/en/faq/how-does-the-camel-api-compare-to.adoc b/docs/user-manual/en/faq/how-does-the-camel-api-compare-to.adoc
new file mode 100644
index 0000000..bce28a6
--- /dev/null
+++ b/docs/user-manual/en/faq/how-does-the-camel-api-compare-to.adoc
@@ -0,0 +1,43 @@
+[[HowdoestheCamelAPIcompareto-HowdoestheCamelAPIcomparetofromCXFHTTPJBIJMSJavaMailetc]]
+=== How does the Camel API compare to from CXF, HTTP, JBI, JMS, JavaMail, etc.
+
+We have tried to make the Camel
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html[Exchange]
+and
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Message.html[Message]
+map very closely to JBI in particular but also
+<<cxf-component,CXF>>, <<http-component,HTTP>>, <<jms-component,JMS>>,
+<<mail-component,Mail>>, <<xmpp-component,XMPP>> and most other integration
+abstractions. We want to prevent leaky abstractions, so the Camel API
+exposes the underlying APIs so that a link:../processor.adoc[Processor] can
+make use of the underlying abstractions if they make sense.
+
+For example:
+
+[width="100%",cols="50%,50%",options="header",]
+|=======================================================================
+|Component |Inbound exchange exposes
+|<<cxf-component,CXF>> |Each Inbound
+http://camel.apache.org/maven/current/camel-cxf/apidocs/org/apache/camel/component/cxf/CxfExchange.html[CxfExchange]
+has access to the underlying Exchange and Message from CXF
+
+|<<http-component,HTTP>> |Each inbound
+http://camel.apache.org/maven/current/camel-http/apidocs/org/apache/camel/component/http/HttpExchange.html[HttpExchange]
+has access to the underlying HttpServletRequest and HttpServletResponse
+
+|JBI |Each inbound
+http://camel.apache.org/maven/current/camel-jbi/apidocs/org/apache/camel/component/jbi/JbiExchange.html[JbiExchange]
+has access to the underlying JBI MessageExchange and NormalizedMessage
+objects
+
+|<<jms-component,JMS>> |Each inbound
+http://camel.apache.org/maven/current/camel-jms/apidocs/org/apache/camel/component/jms/JmsExchange.html[JmsExchange]
+has access to the underlying JMS Message objects
+|=======================================================================
+
+You can probably see a pattern forming now :smile:
+
+For many routing and mediation components and
+link:../processor.adoc[Processor] objects, you maybe don't care about the
+underlying transport and can instead stick to the abstract Camel API.
+But if you need to, the real transport APIs are there for you.
diff --git a/docs/user-manual/en/faq/how-does-the-website-work.adoc b/docs/user-manual/en/faq/how-does-the-website-work.adoc
new file mode 100644
index 0000000..4304b3f
--- /dev/null
+++ b/docs/user-manual/en/faq/how-does-the-website-work.adoc
@@ -0,0 +1,8 @@
+[[Howdoesthewebsitework-Howdoesthewebsitework]]
+=== How does the website work?
+
+This entire website is hosted in
+https://github.com/apache/camel/[the GitHub repository],
+and you can send a pull request to help us make the documentation better.
+
+TODO: Write how it works and how to contribute to the web site.
diff --git a/docs/user-manual/en/faq/if-i-use-servicemix-when-should-i-use-camel.adoc b/docs/user-manual/en/faq/if-i-use-servicemix-when-should-i-use-camel.adoc
new file mode 100644
index 0000000..4fee4a2
--- /dev/null
+++ b/docs/user-manual/en/faq/if-i-use-servicemix-when-should-i-use-camel.adoc
@@ -0,0 +1,22 @@
+[[IfIuseServiceMixwhenshouldIuseCamel-IfIuseServiceMixwhenshouldIuseCamel]]
+=== If I use ServiceMix when should I use Camel?
+
+Camel is a routing and mediation engine which works great inside JBI.
+
+So if you are already using http://servicemix.apache.org/[ServiceMix]
+then you can use Camel implement the
+link:../enterprise-integration-patterns.adoc[Enterprise Integration Patterns]
+inside JBI such as
+<<contentBasedRouter-eip,Content Based Router>>, routing messages
+between your existing JBI endpoints.
+
+You can also reuse any of the Camel link:../component.adoc[Components]
+within JBI or expose Camel endpoints as JBI endpoints.
+
+[[IfIuseServiceMixwhenshouldIuseCamel-SeeAlso]]
+==== See Also
+
+* link:how-does-camel-compare-to-servicemix.adoc[How does Camel compare
+to ServiceMix]
+* link:how-does-camel-compare-to-servicemix-eip.adoc[How does Camel
+compare to ServiceMix EIP]
diff --git a/docs/user-manual/en/faq/is-camel-an-esb.adoc b/docs/user-manual/en/faq/is-camel-an-esb.adoc
new file mode 100644
index 0000000..b2f2da8
--- /dev/null
+++ b/docs/user-manual/en/faq/is-camel-an-esb.adoc
@@ -0,0 +1,17 @@
+[[IsCamelanESB-IsCamelanESB]]
+=== Is Camel an ESB?
+
+Typically vendors claim practically everything is an ESB these days, so
+the answer is probably yes :smile:
+
+However our view is that an ESB is more of a container of integration
+components, so we view http://servicemix.apache.org[Apache ServiceMix]
+to be a true ESB based around OSGi (and optionally JBI) to provide a
+standards based integration platform of components.
+
+We view Camel as being a rule based routing & mediation engine which can
+be used inside a full blown ESB, a message broker or a web services
+smart client. Though if you want to, you could consider that Camel is a
+small, lightweight embeddable ESB since it can provide many of the
+common ESB services like smart routing, transformation, mediation,
+monitoring, orchestration, etc.
diff --git a/docs/user-manual/en/faq/is-camel-ioc-friendly.adoc b/docs/user-manual/en/faq/is-camel-ioc-friendly.adoc
new file mode 100644
index 0000000..e7cc295
--- /dev/null
+++ b/docs/user-manual/en/faq/is-camel-ioc-friendly.adoc
@@ -0,0 +1,61 @@
+[[IsCamelIoCfriendly-IsCamelIoCfriendly]]
+=== Is Camel IoC friendly?
+
+The quick answer is, yes absolutely! :smile:
+Now for the longer answer...
+
+[[IsCamelIoCfriendly-Spring]]
+==== Spring
+
+In particular we've gone out of our way to make Camel work great with
+link:../spring.adoc[Spring] and to reuse all of Spring 2.x's power. For
+example:
+
+* the CamelContext, Components and Endpoints and their dependent beans
+can be configured in Spring using Spring custom XML namespaces or
+traditional bean/property elements
+* we implement a spring BeanPostProcessor to allow POJOs to be injected
+with Camel resources along with powerful
+link:../bean-integration.adoc[Bean Integration] which allows any
+spring-injected POJO to be used inside Camel along with full support
+for Spring Remoting.
+
+What we've tried to do is implement the
+link:../inversion-of-control-with-smart-defaults.adoc[Inversion Of Control With Smart Defaults]
+pattern; namely that you can configure Camel in a
+single XML element (or very small amont of XML) to get going, then you
+can overload default configurations to add more explicit configuration
+as and when you need it.
+
+[[IsCamelIoCfriendly-OtherIoCcontainers]]
+==== Other IoC containers
+
+Spring is clearly the leading IoC container; though there are some
+others such as Guice, OSGi, Pico, HiveMind & Plexus so we have made the
+IoC pluggable in Camel.
+For example camel-core has no dependencies on anything other than
+commons-logging; camel-spring contains all the link:../spring.adoc[Spring]
+integration, etc.
+
+We hope to have closer integration to other IoC containers, particularly
+with Guice. The current mechanism for hooking into other IoC containers
+are:
+
+* link:../injector.adoc[Injector] is used to perform dependency injection
+on a type when sing the
+link:../inversion-of-control-with-smart-defaults.adoc[Inversion Of Control
+With Smart Defaults] pattern
+* link:../registry.adoc[Registry] this strategy is used to abstract away
+the ApplicationContext such as to use JNDI or OSGi to lookup services on
+demand
+
+[[IsCamelIoCfriendly-UsingnoIoCcontainer]]
+==== Using no IoC container
+
+Some folks don't even use an IoC container and thats fine too :smile:
+For example you can just use camel-core with pure Java and then wire
+things together using just Java code (or some scripting language, etc.).
+
+By default when referring to components, endpoints or beans by name,
+it'll try look them up in the JNDI context and we've got a POJO based
+JNDI provier if you need one of those too.
diff --git a/docs/user-manual/en/faq/running-camel-standalone.adoc b/docs/user-manual/en/faq/running-camel-standalone.adoc
new file mode 100644
index 0000000..e125d41
--- /dev/null
+++ b/docs/user-manual/en/faq/running-camel-standalone.adoc
@@ -0,0 +1,29 @@
+[[RunningCamelstandalone-IsitpossibletostartCamelasastandaloneapplication,withoutembeddingitinanotherapplication]]
+=== Is it possible to start Camel as a standalone application, without embedding it in another application?
+
+Yes, Camel can run standalone or in any container. Running Standalone is
+as simple just to create a link:../camelcontext.adoc[CamelContext], add
+routes and start it. If you don't want to write your own Java main, you
+could use the one from link:../spring.adoc[camel-spring]
+(http://camel.apache.org/maven/current/camel-spring/apidocs/) also used
+by the link:../camel-maven-plugin.adoc[Camel Maven Plugin].
+
+The starting guide is a good place to start: +
+link:../getting-started.adoc[Getting Started]
+
+And the concrete walk through a plain old java main example: +
+link:walk-through-an-example.adoc[Walk through an Example]
+
+The FAQ have some more details: +
+link:../faq.adoc[FAQ]
+
+And if you use Maven for your projects Camel has maven tools to boot up
+in standalone mode and quickly run you Camel application: +
+link:../camel-maven-plugin.adoc[Camel Maven Plugin]
+
+And check this link:../cookbook.adoc[Cookbook] example: +
+link:running-camel-standalone-and-have-it-keep-running.adoc[Running
+Camel standalone and have it keep running]
+
+This is how you can run the link:../examples.adoc[Examples] that is
+included in the Camel distribution.
diff --git a/docs/user-manual/en/faq/what-are-the-dependencies.adoc b/docs/user-manual/en/faq/what-are-the-dependencies.adoc
new file mode 100644
index 0000000..fa36cb6
--- /dev/null
+++ b/docs/user-manual/en/faq/what-are-the-dependencies.adoc
@@ -0,0 +1,67 @@
+[[Whatarethedependencies-Whatarethedependencies]]
+=== What are the dependencies?
+
+* Camel 2.6 or older can run on JDK 1.5 or better.
+* Camel 2.7 onwards requires JDK 1.6 or JDK 1.7.
+* Camel 2.14 onwards requires JDK 1.7 or better.
+* Camel 2.18 onwards requires JDK 1.8.
+
+[[Whatarethedependencies-Whataretheruntimejardependencies]]
+==== What are the runtime jar dependencies?
+
+Apache Camel is designed to require a minimum number of dependencies for
+us so it is ideal for embedding into smart clients, message brokers, SOA
+frameworks and ESBs.
+
+[[Whatarethedependencies-CamelJARDependencies]]
+==== Camel JAR Dependencies
+
+Camel core itself is lightweight and can run with a few .jars.
+
+[[Whatarethedependencies-camel-coredependenciesforCamel2.0orlower]]
+===== `camel-core` dependencies for Camel 2.0 or lower
+
+* `commons-logging-api.jar` -- API for commons logging
+* JAXB 2.1.x -- XML stuff -- Is provided in the JDK core from Java 1.6
+* `activation.jar` -- For Attachments support -- Is provided in the JDK
+core from Java 1.6
+
+[[Whatarethedependencies-camel-coredependenciesforCamel2.1-2.6]]
+===== `camel-core` dependencies for Camel 2.1 - 2.6
+
+* `commons-logging-api-1.1.jar` -- API for commons logging
+* `commons-management-1.0.jar` -- API for JMX
+* JAXB 2.1.x -- XML stuff -- Is provided in the JDK core from Java 1.6
+* `activation-1.1.jar` -- For Attachments support -- Is provided in the
+JDK core from Java 1.6
+
+[[Whatarethedependencies-camel-coredependenciesforCamel2.7-2.8]]
+===== `camel-core` dependencies for Camel 2.7 - 2.8
+
+* `slf4j-api-1.5.11.jar` -- API for slf4j logging
+* `commons-management-1.0.jar` -- API for JMX
+
+[[Whatarethedependencies-camel-coredependenciesforCamel2.9]]
+===== `camel-core` dependencies for Camel 2.9
+
+* `slf4j-api-1.6.1.jar` -- API for slf4j logging
+
+[[Whatarethedependencies-OptionalDependenciesforJMXforCamel1.x-2.8]]
+===== Optional Dependencies for JMX for Camel 1.x - 2.8
+
+* `spring-core.jar`, `spring-beans.jar`,
+`spring-context.jar`, `spring-aop.jar` -- All 4 jars needed to use JMX
+with Camel (subject to change in the future).
+
+From *Camel 2.9*: the Spring JARs are no longer required for using JMX.
+
+[[Whatarethedependencies-OtherComponents]]
+==== Other Components
+
+All the other link:../component.adoc[Components] have a range of 3rd party
+.jars they depend on. They are listed in the maven pom files which files
+they require.
+
+Other modules require other dependencies; such as camel-jms requires a
+JMS provider. To see the exact dependencies of the other modules see the
+http://activemq.apache.org/camel/maven/[Maven reports].
diff --git a/docs/user-manual/en/faq/what-is-a-router.adoc b/docs/user-manual/en/faq/what-is-a-router.adoc
new file mode 100644
index 0000000..fdfca7a
--- /dev/null
+++ b/docs/user-manual/en/faq/what-is-a-router.adoc
@@ -0,0 +1,23 @@
+[[Whatisarouter-Whatisarouter]]
+=== What is a router?
+
+We often talk about that Camel is a mediation and routing framework; so
+what exactly is a router and what does it do?
+
+Basically a router just consumes <<message-eip,Message>> exchanges
+from some link:../endpoint.adoc[Endpoint], then sends them on to some other
+link:../endpoint.adoc[Endpoint] using some kind of
+link:../enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns].
+
+For example a router could implement the
+<<contentBasedRouter-eip,Content Based Router>> pattern, to route
+from an endpoint to one or more destination endpoints using a
+link:../predicate.adoc[Predicate] based on the message content.
+
+Typically a route or router consists of one or more consumers; either an
+<<eventDrivenConsumer-eip,Event Driven Consumer>> or a
+<<pollingConsumer-eip,Polling Consumer>> or possibly a
+<<transactionalClient-eip,Transactional Client>>. Then there are one
+or more link:../processor.adoc[Processor] instances which could send the
+message to one or more endpoints.
diff --git a/docs/user-manual/en/faq/what-is-camel.adoc b/docs/user-manual/en/faq/what-is-camel.adoc
new file mode 100644
index 0000000..6036be0
--- /dev/null
+++ b/docs/user-manual/en/faq/what-is-camel.adoc
@@ -0,0 +1,60 @@
+[[WhatisCamel-WhatisCamel]]
+=== What is Camel?
+Apache Camel (TM) is a versatile open-source integration framework based on
+known link:../enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns].
+
+Camel empowers you to define routing and mediation rules in a variety of
+domain-specific languages, including a Java-based link:../dsl.adoc[Fluent
+API], link:../spring.adoc[Spring] or
+link:../using-osgi-blueprint-with-camel.adoc[Blueprint]
+link:../xml-configuration.adoc[XML Configuration] files, and a
+link:../scala-dsl.adoc[Scala DSL]. This means you get smart completion of
+routing rules in your IDE, whether in a Java, Scala or XML editor.
+
+Apache Camel uses link:../uris.adoc[URIs] to work directly with any kind of
+link:../transport.adoc[Transport] or messaging model such as
+<http-component,HTTP>>, link:activemq.adoc[ActiveMQ], <<jms-component,JMS>>,
+JBI, SCA, <<mina-component,MINA>> or <<cxf-component,CXF>>, as
+well as pluggable link:../component.adoc[Components] and
+link:../data-format.adoc[Data Format] options. Apache Camel is a small
+library with minimal link:what-are-the-dependencies.adoc[dependencies]
+for easy embedding in any Java application. Apache Camel lets you work
+with the same link:../exchange.adoc[API] regardless which kind of
+link:../transport.adoc[Transport] is used -- so learn the API once and you
+can interact with all the link:components.adoc[Components] provided
+out-of-box.
+
+Apache Camel provides support for link:bean-binding.adoc[Bean Binding]
+and seamless integration with popular frameworks such as
+<<cdi-component,CDI>>, link:../spring.adoc[Spring],
+link:../using-osgi-blueprint-with-camel.adoc[Blueprint] and
+link:../guice.adoc[Guice]. Camel also has extensive support for
+link:../testing.adoc[unit testing] your routes.
+
+The following projects can leverage Apache Camel as a routing and
+mediation engine:
+
+* http://servicemix.apache.org/[Apache ServiceMix] -- a popular
+distributed open source ESB and JBI container
+* http://activemq.apache.org/[Apache ActiveMQ] -- a mature, widely used
+open source message broker
+* http://cxf.apache.org/[Apache CXF] -- a smart web services suite
+(JAX-WS and JAX-RS)
+* http://karaf.apache.org/[Apache Karaf] -- a small OSGi based runtime in
+which applications can be deployed
+* http://mina.apache.org/[Apache MINA] -- a high-performance
+http://en.wikipedia.org/wiki/New_I/O[NIO]-driven networking framework
+
+So don't get the hump -- try Camel today! :smile:
+
+[NOTE]
+====
+*Too many buzzwords -- what exactly is Camel?*
+
+Okay, so the description above is technology focused.
+There's a great discussion about Camel at
+http://stackoverflow.com/questions/8845186/what-exactly-is-apache-camel[Stack
+Overflow]. We suggest you view the post, read the comments, and browse
+the suggested links for more details.
+====
diff --git a/docs/user-manual/en/faq/what-is-the-license.adoc b/docs/user-manual/en/faq/what-is-the-license.adoc
new file mode 100644
index 0000000..c033be6
--- /dev/null
+++ b/docs/user-manual/en/faq/what-is-the-license.adoc
@@ -0,0 +1,6 @@
+[[Whatisthelicense-Whatisthelicense]]
+=== What is the license?
+
+This software is open source using the
+http://www.apache.org/licenses/LICENSE-2.0.html[Apache 2.0 licence] (a
+liberal BSD style license which is very commercial friendly).
diff --git a/docs/user-manual/en/faq/what-jars-do-i-need.adoc b/docs/user-manual/en/faq/what-jars-do-i-need.adoc
new file mode 100644
index 0000000..d687da7
--- /dev/null
+++ b/docs/user-manual/en/faq/what-jars-do-i-need.adoc
@@ -0,0 +1,34 @@
+[[WhatjarsdoIneed-WhatjarsdoIneed]]
+=== What jars do I need?
+
+Camel is designed to be small lightweight and extremely modular so that
+you only pay for what you use. The core of camel, *camel-core.jar* is
+small and has minimal dependencies.
+
+On Java 6 camel-core.jar only depends on
+
+* *commons-management.jar* (for Camel 2.8 or older)
+* *commons-logging.jar* (for Camel 2.6 or older)
+* *slf4j-api.jar* (from Camel 2.7 onwards)
+
+On Java 5 camel-core.jar depends also on *activation.jar* and a JAXB2
+implementation which typically involves *jaxb-api.jar*, *jaxb-impl.jar*
+and a StAX API which may be *stax-api.jar* and *woodstox.jar*.
+
+[[WhatjarsdoIneed-UsingSpring]]
+==== Using Spring
+
+If you wish to work with Spring, you will also need *camel-spring.jar*
+along with the *spring.jar* or the individual spring jars if you prefer.
+
+[[WhatjarsdoIneed-Othercomponents]]
+==== Other components
+
+For other components you may want to look at the
+http://activemq.apache.org/camel/maven/[Maven reports] to see the exact
+dependencies of individual modules.
+
+For example to work with JMS you will require the JMS API jar together
+with *camel-jms.jar* and your JMS provider of choice such as the
+http://activemq.apache.org/[ActiveMQ]
+http://activemq.apache.org/initial-configuration.html[required jars].
diff --git a/docs/user-manual/en/faq/what-platforms-are-supported.adoc b/docs/user-manual/en/faq/what-platforms-are-supported.adoc
new file mode 100644
index 0000000..5b5a697
--- /dev/null
+++ b/docs/user-manual/en/faq/what-platforms-are-supported.adoc
@@ -0,0 +1,8 @@
+[[Whatplatformsaresupported-Whatplatformsaresupported]]
+=== What platforms are supported?
+
+Any platform supporting JDK 6.
+
+We regularly test Camel on Linux, Windows and OS X. If you have a
+platform that is not listed contact one of the companies that provide
+link:../support.adoc[commercial support].
diff --git a/docs/user-manual/en/faq/why-the-name-camel.adoc b/docs/user-manual/en/faq/why-the-name-camel.adoc
new file mode 100644
index 0000000..e8b03c8
--- /dev/null
+++ b/docs/user-manual/en/faq/why-the-name-camel.adoc
@@ -0,0 +1,30 @@
+[[WhythenameCamel-WhydidyouchoosethenameCamel]]
+=== Why did you choose the name Camel?
+
+* it stands for Concise Application Message Exchange Language (i.e. the
+Java link:../dsl.adoc[DSL] for routing)
+* a Camel can carry http://www.fao.org/sd/EGdirect/EGan0006.htm[4 times
+the load] of other beasts of burden
+* a Camel can travel for great distances without water; similarly a
+Camel does not require bucket loads of XML as you can use a pure Java
+link:../dsl.adoc[DSL]
+* some members of the team used to love Camel cigarettes!
+* it's short, simple and easy to remember name
+* very fast, even when the going gets tough!
+* a Camel will never spit on those it loves!
+* a Camel is not an
+http://en.wikipedia.org/wiki/Hybrid_animals#Equid_Hybrids[evolutionary
+dead end]
+* a Camel looks really funny when it's running, like most of the team :smile:
+* a Camel is a horse designed by committee :smile:
+* a http://www.groapacuprosti.com/2010/09/camel-in-action.html[Camel in
+Action] is really funny
+
+We generated some really cheesy tag lines like:
+
+* You can go a long way with Camel!
+* Don't get the hump get Camel!
+* No where to evolve to? Get Camel!
+* One hump or two?
+* Don't get lost in a desert of XML config files, get Camel!
+* It's not a mirage, it's a Camel!
diff --git a/docs/user-manual/en/fluent-builders.adoc b/docs/user-manual/en/fluent-builders.adoc
new file mode 100644
index 0000000..c6e64c0
--- /dev/null
+++ b/docs/user-manual/en/fluent-builders.adoc
@@ -0,0 +1,11 @@
+[[FluentBuilders-FluentBuilders]]
+=== Fluent Builders
+
+Camel provides _fluent builders_ for creating routing and mediation
+rules using a type-safe IDE friendly way which provides smart completion
+and is refactoring safe.
+
+For more information see:
+
+* link:dsl.adoc[Java Domain Specific Language]
+* link:xml-configuration.adoc[XML Configuration]
diff --git a/docs/user-manual/en/getting-started.adoc b/docs/user-manual/en/getting-started.adoc
index a0e5b53..7fca182 100644
--- a/docs/user-manual/en/getting-started.adoc
+++ b/docs/user-manual/en/getting-started.adoc
@@ -10,7 +10,7 @@ Then come back here and you might want to read the following
documentation before continuing:
* Longer Getting Started Guide
-* Find out about link:enterprise-integration-patterns.html[Enterprise
+* Find out about link:enterprise-integration-patterns.adoc[Enterprise
Integration Patterns] and how to implement them with Camel
* Review the Architecture guide to see how to
build Routes using the Java DSL or
@@ -34,7 +34,7 @@ Xml Configuration.
When your application is closing you may wish to
stop the context
-When you are ready, why not link:walk-through-an-example.html[Walk
+When you are ready, why not link:walk-through-an-example.adoc[Walk
through an Example]? +
And then continue the walk link:walk-through-another-example.html[Walk
through another example] +
diff --git a/docs/user-manual/en/guice-jms-example.adoc b/docs/user-manual/en/guice-jms-example.adoc
index beeb78f..bef4ebc 100644
--- a/docs/user-manual/en/guice-jms-example.adoc
+++ b/docs/user-manual/en/guice-jms-example.adoc
@@ -19,7 +19,7 @@ file to bootstrap Guice and Camel.
To run the example we currently use the maven exec plugin. For example
from the source or binary distribution the following should work
-[source,brush:,java;,gutter:,false;,theme:,Default]
+[source,java]
----
cd examples/camel-example-guice-jms
mvn compile exec:java
diff --git a/docs/user-manual/en/injector.adoc b/docs/user-manual/en/injector.adoc
index 4f2d877..59078b8 100644
--- a/docs/user-manual/en/injector.adoc
+++ b/docs/user-manual/en/injector.adoc
@@ -9,7 +9,7 @@ Spring or Guice to be able to create and
dependency-inject objects of a certain type.
For example if you are using the
-link:inversion-of-control-with-smart-defaults.html[Inversion Of Control
+link:inversion-of-control-with-smart-defaults.adoc[Inversion Of Control
With Smart Defaults] pattern to minimize your XML dependency; Camel will
automatically discover and use new endpoints when they are referenced
via their URIs by using the META-INF/services settings.
diff --git a/docs/user-manual/en/irc-room.adoc b/docs/user-manual/en/irc-room.adoc
new file mode 100644
index 0000000..02c3b3a
--- /dev/null
+++ b/docs/user-manual/en/irc-room.adoc
@@ -0,0 +1,24 @@
+[[IRCRoom-IRC]]
+=== IRC
+
+You can hang out on IRC in the `#apache-camel` room at freenode with other
+Apache Camel developers and users.
+
+[[IRCRoom-UsinganIRCclient]]
+==== Using an IRC client
+
+Here are the connection details.
+
+[width="100%",cols="50%,50%",]
+|========================
+|server |irc.freenode.net
+|port |6667
+|room |#apache-camel
+|========================
+
+[[IRCRoom-GitterRoom]]
+==== Gitter Room
+
+Apache Camel is also on Gitter in the
+https://gitter.im/apache/apache-camel[apache/apache-camel] room which
+you can access from a web browser.
diff --git a/docs/user-manual/en/languages.adoc b/docs/user-manual/en/languages.adoc
new file mode 100644
index 0000000..bfd351c
--- /dev/null
+++ b/docs/user-manual/en/languages.adoc
@@ -0,0 +1,52 @@
+[[Languages-Languages]]
+=== Languages
+
+To support flexible and powerful
+link:enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns], Camel supports various Languages to create an
+link:expression.adoc[Expression] or link:predicate.adoc[Predicate]
+within either the link:dsl.adoc[Routing Domain Specific Language] or the
+link:xml-configuration.adoc[XML Configuration].
+
+[NOTE]
+====
+**Combining Predicates**
+
+When creating predicates (expressions that evaluate to `true` or
+`false`), you can combine several predicates -- regardless of the
+language they are built with -- by using the `PredicateBuilder` class.
+For more information, see link:predicate.adoc[Compound Predicates].
+====
+
+The following is the list of currently supported languages:
+
+* <<bean-language,Bean Language>> for using Java for expressions
+* <<constant-language,Constant>>
+* the unified <<el-language,EL>> from JSP and JSF
+* <<header-language,Header>>
+* <<jsonpath-language,JSonPath>>
+* <<jxpath-language,JXPath>>
+* <<mvel-language,Mvel>>
+* <<ognl-language,OGNL>>
+* <<ref-language,Ref Language>>
+* <<exchangeproperty-language,ExchangeProperty>> /
+ �<<property-language,Property>>
+* <<scripting-languages-language,Scripting Languages>> such as:
+** <<beanshell-language,BeanShell>>
+** <<javascript-language,JavaScript>>
+** <<groovy-language,Groovy>>
+** <<python-language,Python>>
+** <<php-language,PHP>>
+** <<ruby-language,Ruby>>
+* <<simple-language,Simple>>
+** <<file-language,File Language>>
+* <<spel-language,Spring Expression Language>>
+* <<sql-language,SQL>>
+* <<tokenizer-language,Tokenizer>>
+* <<xpath-language,XPath>>
+* <<xquery-language,XQuery>>
+* link:vtd-xml.adoc[VTD-XML]
+
+Most of these languages are also supported used as
+link:annotation-based-expression-language.html[Annotation Based
+Expression Language].
diff --git a/docs/user-manual/en/mailing-lists.adoc b/docs/user-manual/en/mailing-lists.adoc
new file mode 100644
index 0000000..d4981ec
--- /dev/null
+++ b/docs/user-manual/en/mailing-lists.adoc
@@ -0,0 +1,72 @@
+[[MailingLists-MailingLists]]
+=== Mailing Lists
+
+The following mailing lists are available. Before posting you might want
+to read the link:support.adoc[Support] page before posting to the
+mailing list.
+
+[IMPORTANT]
+====
+**Use Camel User List**
+
+You should post and subscriber to the *Camel User List* for all your
+questions on using Camel, or how to do X with Camel, etc. If in doubt use
+this list.
+The other list Camel Developer List, is for the Camel team to discuss
+development of the actual Camel project; do *not* use this list for
+question on using Camel.
+Again to re-iterate, use the *Camel User List*, for you Camel questions.
+This is the correct mailing list, and have the most people there ready
+for helping you.
+====
+
+[WARNING]
+====
+**Post plain text mails**
+
+When posting to the mailing lists, use plain text mails. Do *not* use
+HTML mails. HTML mails is more likely to be targeted as spam mails and
+will be rejected; as well it's not easily readable by others.
+====
+
+[width="99%",cols="16%,14%,14%,14%,14%,14%,14%",options="header",]
+|=======================================================================
+|List Name |Address |Subscribe |Unsubscribe |Archive |Nabble footnote:[Online
+Forums] |Comment
+|Camel User List |users@camel.apache.org
+|mailto:users-subscribe@camel.apache.org[Subscribe]
+|mailto:users-unsubscribe@camel.apache.org[Unsubscribe]
+|http://mail-archives.apache.org/mod_mbox/camel-users/[Archive]
+|http://camel.465427.n5.nabble.com/Camel-Users-f465428.html[Nabble] |Use
+this list for your Camel questions.
+
+|Camel Developer List |dev@camel.apache.org
+|mailto:dev-subscribe@camel.apache.org[Subscribe]
+|mailto:dev-unsubscribe@camel.apache.org[Unsubscribe]
+|http://mail-archives.apache.org/mod_mbox/camel-dev/[Archive]
+|http://camel.465427.n5.nabble.com/Camel-Development-f479097.html[Nabble] |
+
+|Camel Commits List |commits@camel.apache.org
+|mailto:commits-subscribe@camel.apache.org[Subscribe]
+|mailto:commits-unsubscribe@camel.apache.org[Unsubscribe]
+|http://mail-archives.apache.org/mod_mbox/camel-commits/[Archive]
+|http://camel.465427.n5.nabble.com/Camel-Commits-f498405.html[Nabble] |
+
+|Camel Issues List |issues@camel.apache.org
+|mailto:issues-subscribe@camel.apache.org[Subscribe]
+|mailto:issues-unsubscribe@camel.apache.org[Unsubscribe]
+|http://mail-archives.apache.org/mod_mbox/camel-issues/[Archive] |� |
+|=======================================================================
+
+There were various discussions before these mailing lists were setup on
+the http://camel.apache.org/mailing-lists.html[ActiveMQ Mailing Lists]
+such as
+http://www.nabble.com/forum/Search.jtp?forum=2354&local=y&query=%5Bcamel%5D[these
+threads].
+
+[[MailingLists-DiscussionForums]]
+==== Discussion Forums
+
+If you prefer you could use our
+http://camel.465427.n5.nabble.com/[Discussion Forums]
+which are sync'd with the above mailing lists.
diff --git a/docs/user-manual/en/processor.adoc b/docs/user-manual/en/processor.adoc
new file mode 100644
index 0000000..deee573
--- /dev/null
+++ b/docs/user-manual/en/processor.adoc
@@ -0,0 +1,99 @@
+[[Processor-Processor]]
+=== Processor
+
+The
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html[Processor]
+interface is used to implement consumers of message exchanges or to
+implement a <<MessageTranslator-MessageTranslator,Message Translator>>.
+
+[[Processor-Usingaprocessorinaroute]]
+==== Using a processor in a route
+
+Once you have written a class which implements processor like this...
+
+[source,java]
+----
+public class MyProcessor implements Processor {
+ public void process(Exchange exchange) throws Exception {
+ // do something...
+ }
+}
+----
+
+You can then easily use this inside a route by declaring the bean in
+Spring, say via the XML (or registering it in JNDI if that is your
+link:registry.adoc[Registry]):
+
+[source,xml]
+----
+<bean id="myProcessor" class="com.acme.MyProcessor"/>
+----
+
+Then in Camel you can do:
+
+[source,java]
+----
+from("activemq:myQueue").to("myProcessor");
+----
+
+[[Processor-UsingtheprocessDSL]]
+===== Using the process DSL
+
+In your route you can also use the `process` DSL syntax for invoking a
+processor.
+
+[source,java]
+----
+Processor myProcessor = new MyProcessor();
+...
+from("activemq:myQueue").process(myProcessor);
+----
+
+If you need to lookup the processor in the link:registry.adoc[Registry]
+then you should use the `processRef` DSL:
+
+[source,java]
+----
+from("activemq:myQueue").processRef("myProcessor");
+----
+
+[[Processor-Whyuseprocesswhenyoucanusetoinstead]]
+==== Why use process when you can use to instead?
+
+The process can be used in routes as an anonymous inner class such:
+
+[source,java]
+----
+ from("activemq:myQueue").process(new Processor() {
+ public void process(Exchange exchange) throws Exception {
+ String payload = exchange.getIn().getBody(String.class);
+ // do something with the payload and/or exchange here
+ exchange.getIn().setBody("Changed body");
+ }
+ }).to("activemq:myOtherQueue");
+----
+
+This is usable for quickly whirling up some code. If the code in the
+inner class gets a bit more complicated it is of course advised to
+refactor it into a separate class.
+
+[[Processor-TurningyourprocessorintoafullComponent]]
+==== Turning your processor into a full Component
+
+There is a base class called
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/ProcessorEndpoint.html[ProcessorEndpoint]
+which supports the full link:endpoint.adoc[Endpoint] semantics given a
+Processor instance.
+
+So you just need to create a link:component.adoc[Component] class by
+deriving from
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/DefaultComponent.html[DefaultComponent]
+which returns instances of ProcessorEndpoint. For more details see
+link:writing-components.adoc[Writing Components]
+
+[[Processor-SeeAlso]]
+==== See Also
+
+* <<MessageTranslator-MessageTranslator,Message Translator>>
+* <<enrich-eip,Content Enricher>>
+* <<ContentFilter-eip,Content Filter>>
diff --git a/docs/user-manual/en/release-notes/camel-2170-release.adoc b/docs/user-manual/en/release-notes/camel-2170-release.adoc
index 5aa545f..dc48c7e 100644
--- a/docs/user-manual/en/release-notes/camel-2170-release.adoc
+++ b/docs/user-manual/en/release-notes/camel-2170-release.adoc
@@ -28,7 +28,7 @@ and link:ftp.html[FTP] endpoints is now case in-sensitive out of the
box.
* Resource based component such
as link:xslt.html[XSLT], link:velocity.html[Velocity] etc can load the
-resource file from the link:registry.html[Registry] by using `ref:` as
+resource file from the link:registry.adoc[Registry] by using `ref:` as
prefix.
* Upgraded camel-amqp to the latest qpid-jms-client (also AMQP < 1.0 is
not supported anymore).
@@ -78,20 +78,20 @@ custom `Processor` to be invoked right after an exception was thrown
using the new *onExceptionOccurred* option.
* link:rabbitmq.html[RabbitMQ] consumer more resilient to auto
re-connect in case of connection failures
-* The link:json.html[JSON] `camel-jackson` can be used as a type
+* The link:../json.adoc[JSON] `camel-jackson` can be used as a type
converter to convert json to/from POJO and String/byte[] types, if
enabled.
* The link:sql-component.html[SQL Component] now supports loading the
SQL queries from external files on the classpath or file system, where
you can format the queries using newlines and indenting.
-* The link:mail.html[Mail] consumer allows to use an idempotent
+* The <<mail-component,Mail>> consumer allows to use an idempotent
repository which allows to cluster consuming from the same mailbox, and
let the repository coordinate whether a mail message is valid for the
consumer to process.
* Added support for completion interval on the link:sjms-batch.html[SJMS
Batch] component, which allows to trigger batch completion in a fixed
scheduled interval.
-* The link:http.html[HTTP] and link:http4.html[HTTP4] producers now
+* The <<http-component,HTTP>> and link:http4.html[HTTP4] producers now
support the `disableStreamCache` option to allow to use the raw response
stream as the message body instead of wrapping
using link:stream-caching.html[Stream caching]
@@ -137,7 +137,7 @@ from an OGNL method chain (eg invoke the following 3 methods
"doFoo.doSomething.getBar") and a method returned null which prevent
further method invocation as that would cause a NullPointerException.
Now you have a more detailed exception message to better explain this.
-* link:jaxb.html[JAXB] data format and type converter now supports
+* <<jaxb-dataformat,JAXB>> data format and type converter now supports
converting from XML to POJO for classes that are using ObjectFactory
classes instead of XmlRootElement annotations.
* The link:kafka.html[Kafka] component has been migrated to use the Java
@@ -183,7 +183,7 @@ api-docs could lead to api-doc route being added multiple times
using link:swagger-java.html[Swagger Java]
* Fixed using `statement.xxx` options on the link:jdbc.html[JDBC]
consumer would only be used in first poll.
-* Fixed link:http.html[HTTP] and link:http4.html[HTTP4] to keep
+* Fixed <<http-component,HTTP>> and link:http4.html[HTTP4] to keep
trailing slash if provided in uri when calling remote HTTP service.
* Fixed link:oncompletion.html[OnCompletion] to keep any caught
exception stored as property on the `Exchange` which allows to access
@@ -244,8 +244,8 @@ link:sql-stored-procedure.html[sql-stored component].
### New Data Formats
-* link:mime-multipart.html[MIME-Multipart] - mime based data format.
-* link:lzf-data-format.html[LZF Data Format] - LZF based data format.
+* <<mime-multipart-dataformat,MIME-Multipart>> - mime based data format.
+* <<lzf-dataformat,LZF Data Format>> - LZF based data format.
* link:yaml-data-format.html[YAML Data Format] - YAML based data format.
* Hessian - Caucho Hessian based data format.
@@ -372,10 +372,10 @@ from the Camel Parent BOM to the tooling BOM (to have them separated).
* camel-amqp do not support 0.9 anymore.
* camel-spring-integration feature has been removed from the Camel
karaf.
-* The link:mail.html[Mail] component now requires to configure to, cc,
+* The <<mail-component,Mail>> component now requires to configure to, cc,
and bcc using lower case keys, eg to=foo@bar.com, instead
of mailto:To=foo@bar.com[To=foo@bar.com] as previously.
-* The link:file2.html[File] consumer no longer probe the file content by
+* The <<file-component,File>> consumer no longer probe the file content by
default. See the option `probeContentType` for more details.
* If using link:bean.html[Bean] or link:class.html[Class] component and
specifying additional parameters in the endpoint uri to configure on the
diff --git a/docs/user-manual/en/release-notes/camel-2180-release.adoc b/docs/user-manual/en/release-notes/camel-2180-release.adoc
index 8c5e57d..e0a6fb4 100644
--- a/docs/user-manual/en/release-notes/camel-2180-release.adoc
+++ b/docs/user-manual/en/release-notes/camel-2180-release.adoc
@@ -18,7 +18,7 @@ are now also documented (before it was only <routes> and <rests>). The
XSD schema now also documents the default values of all the options.
* Introduced `FluentProducerTemplate` using fluent builder style as a
alternative to link:producertemplate.html[ProducerTemplate]
-* All Camel link:components.html[Components] that has options to be
+* All Camel link:component.adoc[Components] that has options to be
configured now supports and include link:spring-boot.html[Spring
Boot] auto configuration for those options, so they can easily be
configured in your application.yaml file when using Spring Boot with
@@ -53,12 +53,12 @@ camel-spring-dm module. +
parameter types when using link:simple.html[Simple] language as
parameter values.
* Added `BindyConverter` that allows to implement custom data converters
-for link:bindy.html[Bindy]
+for <<bindy-dataformat,Bindy>>
* The access in the link:rest-dsl.html[Rest DSL] has been deprecated and
no longer in use - its not part of swagger specification anymore.
* link:nats.html[Camel-NATS] now uses JNATS client instead of the
deprecated Java_nats one.
-* During startup of link:camelcontext.html[CamelContext] the services
+* During startup of link:camelcontext.adoc[CamelContext] the services
that are used as part of routes are now deferred being started to the
end of the startup process. Some IoC frameworks like Spring can
otherwise causes a circular dependency issue if services are started too
@@ -73,7 +73,7 @@ issues.
* Added PATCH to link:rest-dsl.html[Rest DSL]
* Added "starts with" and "ends with" operator to the
link:simple.html[Simple] language.
-* Added `BeanIOSplitter` to link:beanio.html[BeanIO] that can be used
+* Added `BeanIOSplitter` to <<beanio-dataformat,BeanIO>> that can be used
with the link:splitter.html[Splitter] EIP to split big payloads in
streaming mode without reading the entire content into memory.
* Some of the link:aws.html[AWS] components allows to specify ARN in the
@@ -102,7 +102,7 @@ iterator for the output of the SQL query that allows to process the data
in a streaming fashion such as with the link:splitter.html[Splitter] EIP
to process the data row by row, and load data from the database as
needed.
-* link:jpa.html[JPA] now includes a `JpaPollingConsumer` implementation
+* <<jpa-component,JPA>> now includes a `JpaPollingConsumer` implementation
that better supports link:content-enricher.html[Content Enricher]
using `pollEnrich` to do a on-demand poll that returns either none, one
or a list of entities as the result.
@@ -137,7 +137,7 @@ configure AllowUseOriginalMessage=true.
link:http.html[Camel-HTTP] link:http4.html[Camel-HTTP4] link:jetty.html[Camel-Jetty] now
support a connectionClose parameter to allow explicitly adding a
Connection Close header to HTTP request
-* link:bindy.html[Bindy] allows to plugin custom formatters for mapping
+* <<bindy-dataformat,Bindy>> allows to plugin custom formatters for mapping
to custom types.
* link:content-enricher.html[Content Enricher] using `pollEnrich` now
supports consumers configured with `consumer.bridgeErrorHandler=true` to
@@ -161,7 +161,7 @@ used when querying the catalog. There is a `camel-catalog-maven` module
that is able to download catalog JARs from Maven central.
* A new Camel Attachment interface was added that allows propagating
headers for attachments. link:cxf.html[Camel CXF], link:mail.html[Camel
-Mail] (including the link:mime-multipart.html[MIME-Multipart]data
+Mail] (including the <<mime-multipart-dataformat,MIME-Multipart>>data
format), and link:jetty.html[Camel-Jetty] set and consume attachment
headers.
* Improved link:bean.html[bean method call] to validate if method name
@@ -223,8 +223,8 @@ be gargage collected.
* Fixed link:dozer.html[Dozer] not able to use variables in mapping
files when using OSGi.
* Fixed a potential dead-lock when doing request/reply
-over link:jms.html[JMS] and requests are timing out concurrently and
-continued routing the exchanges are calling another link:jms.html[JMS]
+over <<jms-component,JMS>> and requests are timing out concurrently and
+continued routing the exchanges are calling another <<jms-component,JMS>>
endpoint that is also doing request/reply which also timeout.
* Fixed link:load-balancer.html[Load Balancer] EIPs to support
using _any_ link:using-propertyplaceholder.html[property placeholder]
diff --git a/docs/user-manual/en/release-notes/camel-2190-release.adoc b/docs/user-manual/en/release-notes/camel-2190-release.adoc
index 21b0cd0..003af5b 100644
--- a/docs/user-manual/en/release-notes/camel-2190-release.adoc
+++ b/docs/user-manual/en/release-notes/camel-2190-release.adoc
@@ -11,12 +11,12 @@ https://github.com/apache/camel/blob/master/connectors/camel-connector/src/main/
Connector]'s which is a simplified version of a Camel component that has
been pre-configured for a specific use-case.
* Upgraded to Spring Boot 1.5.x.
-* The link:camel-maven-plugin.html[Camel Maven Plugin] now provides the
+* The link:camel-maven-plugin.adoc[Camel Maven Plugin] now provides the
`camel:validate` goal to parse your Java and XML source code for any
Camel routes and report invalid Camel endpoint uri and simple expression
errors. You can run this at code time (not runtime).
* Camel `Main` and link:spring-boot.html[Spring Boot]
-and link:camel-maven-plugin.html[Camel Maven Plugin] can now auto
+and link:camel-maven-plugin.adoc[Camel Maven Plugin] can now auto
terminate the JVM after Camel has been running for maximum duration of
seconds, processed messages or been idle for a period.
* Camel source code can build with Java 9 in preparation for official
@@ -28,7 +28,7 @@ tooling to display such information
Camel 3.0 or sometime in the future
* Introduced `ReloadStrategy` as SPI which allows custom providers to
implement logic for triggering live reloads of Camel routes.
-* The link:camel-maven-plugin.html[Camel Maven Plugin] now allows to
+* The link:camel-maven-plugin.adoc[Camel Maven Plugin] now allows to
live reload route changes from XML files when running Camel. This can
also be enabled from the `Main` class.
* Introduced a new `camel-catalog-rest` artifact which is a tiny
@@ -88,7 +88,7 @@ been added
* The link:jsonpath.html[JSonPath] language now supports Map and List
types and POJOs as well. For POJOs you need to have Jackson on the
classpath.
-* link:data-format.html[Data Format] which marshal to JSon or XML now
+* link:../data-format.adoc[Data Format] which marshal to JSon or XML now
set the content-type header to application/json or application/xml
appropriately. +
* The link:kafka.html[Kafka] component can now store offset state
@@ -128,7 +128,7 @@ https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/
There're a few examples demonstrates this feature:
https://github.com/apache/camel/tree/master/examples/camel-example-transformer-blueprint[camel-example-transformer-blueprint], https://github.com/apache/camel/tree/master/examples/camel-example-transformer-cdi[camel-example-transformer-cdi], https://github.com/apache/camel/tree/master/examples/camel-example-transformer-demo[camel-example-transformer-demo],
and https://github.com/apache/camel/tree/master/examples/camel-example-validator-spring-boot[camel-example-validator-spring-boot]
-* Added query support for link:jpa.html[JPA] Producer
+* Added query support for <<jpa-component,JPA>> Producer
Fixed these issues
diff --git a/docs/user-manual/en/release-notes/camel-2200-release.adoc b/docs/user-manual/en/release-notes/camel-2200-release.adoc
index d82e8cc..1818d66 100644
--- a/docs/user-manual/en/release-notes/camel-2200-release.adoc
+++ b/docs/user-manual/en/release-notes/camel-2200-release.adoc
@@ -23,7 +23,7 @@ XML files with <camelContext>.
* Worked to make Apache Camel more ready and compatible with the
upcoming Spring Boot 2 and Spring Framework 5. Officially support for
these is expected in Camel 2.21 release.
-* The link:jms.html[JMS] component now includes JMS 2.0 functionality to
+* The <<jms-component,JMS>> component now includes JMS 2.0 functionality to
use shared (durable and non-durable) topic.
* The
https://github.com/apache/camel/blob/master/tooling/maven/camel-maven-plugin/src/main/docs/camel-maven-plugin.adoc[Camel
@@ -50,7 +50,7 @@ started last - when all resources should be available, and stopped first
- while all resources are still available
* The link:sql-stored-procedure.html[SQL Stored Procedure] now supports
specifying custom types as FQN classnames and scale in numeric values.
-* Using Camel with link:spring.html[Spring] now supports calling
+* Using Camel with link:spring.adoc[Spring] now supports calling
link:bean.html[Bean] by their FQN name and let Spring instantiate the
bean using auto-wired constructor's as opposed to only supporting a
no-arg constructor.
@@ -140,7 +140,7 @@ to complete or timeout.
* Fixed an issue with copying streams could block forever due IBM
application server would mistakenly return 0 instead of -1 to indicate
EOL for an empty stream.
-* Fixed an issue with making link:jms.html[JMS] and link:sjms.html[SJMS]
+* Fixed an issue with making <<jms-component,JMS>> and link:sjms.html[SJMS]
components work with ActiveMQ Artemis that would otherwise causes a
ClassCastException
* Fixed link:rabbitmq.html[RabbitMQ] to better recover connection if
diff --git a/docs/user-manual/en/release-notes/camel-2210-release.adoc b/docs/user-manual/en/release-notes/camel-2210-release.adoc
index e0b866f..2ec1c6c 100644
--- a/docs/user-manual/en/release-notes/camel-2210-release.adoc
+++ b/docs/user-manual/en/release-notes/camel-2210-release.adoc
@@ -15,8 +15,8 @@ This release supports only Spring Boot 1.5.x. Support for Spring Boot
* Upgraded to JAXB 2.3.0 which is more JDK9 compliant.
* Added better support for `javax.jms.StreamMessage` types
-in link:jms.html[JMS] component.
-* Optimised link:jms.html[JMS] to support ActiveMQ Artemis
+in <<jms-component,JMS>> component.
+* Optimised <<jms-component,JMS>> to support ActiveMQ Artemis
http://activemq.apache.org/artemis/docs/latest/large-messages.html[large
messages] so you can send and receive big messages such as GB's in size.
There is an example demonstrating this in
@@ -36,9 +36,9 @@ back-on via the apiVendorExtension option.
used to download a single known file without use LIST operation on the
FTP server (which can be slow if the FTP server has many files in the
LIST results)
-* Camel link:json.html[JSON] with camel-jackson will now automatic use
+* Camel link:../json.adoc[JSON] with camel-jackson will now automatic use
shared ObjectMapper instance if there is only one instance in
-the link:registry.html[Registry]. For example users with Spring Boot
+the link:registry.adoc[Registry]. For example users with Spring Boot
then allows Camel to easily use the default mapper from Spring Boot.
* Added `ExtendedStartupListener` that allows a callback just after the
CamelContext has been fully started.
diff --git a/docs/user-manual/en/spring-testing.adoc b/docs/user-manual/en/spring-testing.adoc
index 87ce708..a38278b 100644
--- a/docs/user-manual/en/spring-testing.adoc
+++ b/docs/user-manual/en/spring-testing.adoc
@@ -400,7 +400,7 @@ Sending and receiving messages
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It might be that the
-link:enterprise-integration-patterns.html[Enterprise Integration
+link:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] you have defined in either Spring XML or
using the Java DSL do all of the sending and receiving
and you might just work with the <<mock-component,Mock>> endpoints as
diff --git a/docs/user-manual/en/spring-xml-extensions.adoc b/docs/user-manual/en/spring-xml-extensions.adoc
new file mode 100644
index 0000000..2627d97
--- /dev/null
+++ b/docs/user-manual/en/spring-xml-extensions.adoc
@@ -0,0 +1,33 @@
+[[SpringXMLExtensions-SpringXMLExtensions]]
+=== Spring XML Extensions
+
+The Camel Spring XML Extensions allow you use a very concise XML syntax
+to describe your Camel configuration when you are using spring to wire
+together your application.
+
+The following is an example of what it looks like:
+
+[source,xml]
+----
+<camelContext errorHandlerRef="errorHandler" xmlns="http://camel.apache.org/schema/spring">
+ <route>
+ <from uri="direct:a"/>
+ <choice>
+ <when>
+ <xpath>$foo = 'bar'</xpath>
+ <to uri="direct:b"/>
+ </when>
+ <when>
+ <xpath>$foo = 'cheese'</xpath>
+ <to uri="direct:c"/>
+ </when>
+ <otherwise>
+ <to uri="direct:d"/>
+ </otherwise>
+ </choice>
+ </route>
+</camelContext>
+----
+
+For more usage examples see the
+link:enterprise-integration-patterns.adoc[Enterprise Integration Patterns].
diff --git a/docs/user-manual/en/spring.adoc b/docs/user-manual/en/spring.adoc
index 6fa7f04..df99537 100644
--- a/docs/user-manual/en/spring.adoc
+++ b/docs/user-manual/en/spring.adoc
@@ -1,5 +1,6 @@
-Spring Support
-~~~~~~~~~~~~~~
+[[SpringSupport-SpringSupport]]
+=== Spring Support
+
Apache Camel is designed to work nicely with the Spring Framework in a number of ways.
* Camel uses Spring Transactions as the default transaction handling in components like JMS and JPA
diff --git a/docs/user-manual/en/support.adoc b/docs/user-manual/en/support.adoc
new file mode 100644
index 0000000..e0607cc
--- /dev/null
+++ b/docs/user-manual/en/support.adoc
@@ -0,0 +1,134 @@
+[[Support-GettingHelp]]
+=== Getting Help
+
+If you are experiencing problems using Camel then please report your
+problem to our mailing list. This allows the entire community to help
+with your problem. If indeed a bug has been identified in the Camel
+software, then document the problem in our
+http://issues.apache.org/jira/browse/CAMEL[Issue Tracker]. Please
+refrain from immediately opening a ticket in the issue tracker unless
+you are certain it's a problem in the Camel software. If you are in
+doubt, we appreciate asking the
+link:mailing-lists.adoc[mailing list],
+link:irc-room.adoc[IRC chat], or
+https://gitter.im/apache/apache-camel[Gitter chat] first.
+
+[TIP]
+====
+Please read the section below (_How to get help_), and follow the
+bullets advised there first.
+====
+
+[NOTE]
+====
+*Reporting bugs - Please read this first*
+
+We prefer people to get in touch first using the
+link:mailing-lists.adoc[mailing list],
+link:irc-room.adoc[IRC chat] or
+https://gitter.im/apache/apache-camel[Gitter chat]. Or take time to read
+link:faq.adoc[FAQs], or search in the mailing list archives to find answers.
+Unfortunately some people create a JIRA ticket as first thing. *Please
+don't do that!* Only if you are sure it really is a bug, etc. JIRA tickets
+create noise for the Camel team to react on issues that are not bugs
+but already covered in FAQs, in the mailing lists, etc., or in the existing
+documentation.
+Also on the mailing lists there are more people active to help you better.
+====
+
+* http://issues.apache.org/jira/browse/CAMEL[Issue Tracker]
+* link:faq.adoc[FAQ]
+
+[[Support-Alternativediscussionforums]]
+==== Alternative discussion forums
+
+There are a number of sites outside Apache that offer discussion forums on
+Camel. For example, http://stackoverflow.com/[Stack Overflow] is a
+popular Q & A site with a
+http://stackoverflow.com/questions/tagged/apache-camel[dedicated Apache
+Camel forum]. You are also likely to find helpful discussions on
+technical blogs, on
+https://www.google.com/search?q=apache+camel[Google], or even on
+https://twitter.com/search?q=apache%20camel[Twitter].
+
+[[Support-Usingdeprecatedcomponents]]
+==== Using deprecated components
+
+Deprecated components are *not* supported and issues such as bugs may
+not be fixed. We encourage users to migrate away from using any
+deprecated component. A list of deprecated components is on the
+github page at:
+https://github.com/apache/camel/tree/master/components#components
+
+[[Support-Howtogethelp]]
+==== How to get help
+
+Before you report a problem, you may wish to read the
+link:faq.adoc[FAQ].
+When you report an issue, please be sure to include as much information
+as possible. The more we know, the easier it is to reach an effective
+solution quickly.
+
+[IMPORTANT]
+====
+*What version do you use?*
+
+What version of Camel do you use!? Remember to include this information.
+====
+
+* *what are the version numbers of involved software components?* (this
+is very important to detail)
+* what platform and JDK?
+* any particular container being used? and if so, what version?
+* stack traces generally really help! (*Remember to post which version
+of Camel you use, this is important to know when posting stacktraces*)
+If in doubt, include the whole thing; often exceptions get wrapped in
+other exceptions and the exception right near the bottom explains the
+actual error, not the first few lines at the top. It's very easy for us
+to skim-read past unnecessary parts of a stack trace.
+* log output can be useful too; sometimes
+link:faq/how-do-i-change-the-logging.adoc[enabling DEBUG logging] can help
+* your code & configuration files are often useful
+* did it work before? what have you changed to break it?
+* try upgrading to the latest release and see if it's fixed there
+* try the latest SNAPSHOT to see if it's fixed in the pre-release
+* search the user forum to see if has been discussed before
+* see the "known issues" section in the release notes
+* and check the http://issues.apache.org/jira/browse/CAMEL[issue
+tracker] to see if the issue has already been reported
+* do *not* send private emails to Camel link:team.adoc[Team] members to
+ask them to help you faster, or in the private only. Help on Apache
+Camel is volunteer based and *must* happen in the *open* on the public
+link:mailing-lists.adoc[Mailing Lists]. If you want to get help faster
+or in private, then see further below.
+
+[[Support-Howtogethelpfaster]]
+==== How to get help faster
+
+We can help you much quicker if you try the following:
+
+* provide us with a JUnit test case that demonstrates your issue. e.g.
+if you think you've found a bug, can you create a test case to
+demonstrate the bug?
+* link:../../../CONTRIBUTING.md[submit a patch] fixing the
+bug! (We also buy you beer when we meet you if you submit bug fixes
+:smile:)
+* for memory leak or performance related issues, if you can run a
+profiler on your test case and attach the output as a file (or zipped
+file if it's huge) to the JIRA we can normally fix things much faster.
+e.g. you could run
+http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html[jmap] /
+http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html[jhat],
+JProfiler or YourKit on your code and send us the output. To find memory
+leaks it's quicker to resolve if you can tell us what classes are taking
+up all of the RAM; we can normally figure out what's wrong from that.
+
+[[Support-CommercialSupport]]
+==== Commercial Support
+
+This is an open source project, so the amount of time we have available
+to help resolve your issue is often limited as all help is provided on a
+volunteer basis. If you want to get priority help, need to get up to
+speed quickly, require some training or mentoring, or need full 24 x 7
+production support you could contact one of the following companies with
+link:commercial-camel-offerings.adoc[Commercial Camel Offerings].
diff --git a/docs/user-manual/en/team.adoc b/docs/user-manual/en/team.adoc
new file mode 100644
index 0000000..3bb63f8
--- /dev/null
+++ b/docs/user-manual/en/team.adoc
@@ -0,0 +1,174 @@
+[[Team-Committers]]
+=== Committers
+
+This page lists who we are. By all means add yourself to the list -- let's
+sort it in alphabetical order.
+
+[width="100%",cols="34%,33%,33%",options="header",]
+|=================================================
+|Name |ID |Organisation
+|Aaron Mulder |ammulder |Chariot Solutions
+|Akitoshi Yoshida |ay |SAP
+|Andrea Cosentino |acosentino |Red Hat
+|Antonin Stefanutti |astefanutti |Red Hat
+|Babak Vahdat |bvahdat |Cyberlogic Consulting GmbH
+|Ben O'Day |boday |Initek Consulting
+|Bilgin Ibryam |bibryam |Red Hat
+|Bruce Snyder |bsnyder |
+|Charles Moulliard |cmoulliard |Red Hat
+|Christian Mueller |cmueller |Amazon Web Services
+|Christian Posta |ceposta |Red Hat
+|Christian Schneider |cschneider |
+|Claus Ibsen |davsclaus |Red Hat
+|Colm O hEigeartaigh |coheigea |Talend
+|David Jencks |djencks |IBM
+|Daniel Kulp |dkulp |Talend
+|Franz Forsthofer |forsthofer |SAP
+|Freeman Fang |ffang |Red Hat
+|Gary Tully |gtully |Red Hat
+|Gert Vanthienen |gertv |
+|Gregor Zurowski |gzurowski |Sotheby's
+|Guillaume Nodet |gnodet |Red Hat
+|Hadrian Zbarcea |hadrian |
+|Henryk Konsek |hekonsek |Red Hat
+|Hiram Chirino |chirino |Red Hat
+|Ioannis Canellos |iocanel |Red Hat
+|Jacek Laskowski |jlaskowski |
+|James Carman |jcarman |Savoir Technologies
+|Jean-Baptiste Onofré |jbonofre |Talend
+|Jeff Genender |jgenender |Savoir Technologies
+|Johan Edstrom |joed |Savoir Technologies
+|John Poth | |Red Hat
+|Jonathan Anstey |janstey |Red Hat
+|James Netherton | |Red Hat
+|James Strachan |jstrachan |
+|Luca Burgazzoli |lburgazzoli |Red Hat
+|Martin Krasser |krasserm |
+|Nicky Sandhu |nsandhu |
+|Onder Sezgin |onders |
+|Quinn Stevenson |quinn |
+|Raul Kripalani |raulk |
+|Rich Newcomb |rnewcomb |
+|Richard Kettelerij |rickette |Avisi BV
+|Rob Davies |rajdavies |
+|Roman Kalukiewicz |romkal |
+|Scott England-Sullivan |sully6768 |Red Hat
+|Stan Lewis |slewis |Red Hat
+|Tomohisa Igarashi |igarashitm |Red Hat
+|Tracy Snell |tjsnell |Juice Labs
+|Willem Jiang |ningjiang |
+|William Tam |wtam |Progress Software
+|Zoran Regvart |zregvart |Red Hat
+|=================================================
+
+[[Team-Contributors]]
+Contributors
+^^^^^^^^^^^^
+
+[NOTE]
+====
+*Adding your name to the list below*
+
+If you have been contributing to the Apache Camel project, and you want
+your name added to the list below. Then you can get in touch with the
+Camel team from the link:mailing-lists.adoc[Mailing Lists] and ask to be
+added.
+====
+
+[width="100%",cols="50%,50%",options="header",]
+|===========================================
+|Name |Organisation
+|Aaron Crickenberger |
+|Al Maw |
+|Aleksi Kallio |
+|Andrew Deason |
+|Andy Depue |
+|Axel Hohaus |
+|Arjan Moraal |
+|Arno Noordover |het CAK
+|Barry Kaplan |
+|Brett Meyer |3RiverDev, Savoir Technologies
+|Brian Diesenhaus |
+|Brian Guan |
+|Brian Madigan |
+|Bruno Barin |
+|Bruno Borges |
+|Bryan Schmidt |
+|Chris Kingsbury |TradingScreen
+|Christoph Emmersberger |
+|Christopher G. Stach II |
+|Charles Anthony |
+|Christian Posta |Red Hat
+|Christopher Köster |
+|Claus Straube |
+|Dan Checkoway |
+|Dennis Byrne |Thoughtworks
+|Erik Onnen |
+|Fabrizio Spataro |Bizmate
+|Fernando Ribeiro |
+|Gert Vanthienen |
+|Glen Klyuzner |Tullib
+|Hakan Guleryuz |ASPone
+|James Chamberlain |
+|James Zhang |
+|Jamie McCrindle |
+|Jason Anderson |
+|Jason Carreira |
+|Jason Sherman |
+|Jérôme Delagnes |
+|Jeff Sparkes |
+|Jeff Lansing |SYS Technologies
+|Jeremy Volkman |
+|Joe Fernandez |TTM
+|John Heitmann |
+|Jonathan Cook |BBC
+|Juraj Tomasov |
+|Kevin Ross |
+|Kranti Parisa |
+|Leo Pechersky |
+|Li Ma |
+|Lars Heinemann |Red Hat
+|Lauri Lehmijoki |
+|Lauri Kimmel |
+|Marco Buss |product + concept
+|Marco Luebcke |
+|Mark Bucayan |
+|Mark Timmings |
+|Mario Siegenthaler |
+|Mathieu Lalonde |
+|Mats Henricson |
+|Matt Hoffman |
+|Matthew Vincent |
+|Mathew Kuppe |360 Treasury Systems
+|Mike Perham |
+|Mitko Kolev |InterComponentWare AG
+|Neil Clayton |Royal Bank of Scotland
+|Neil Thorne |
+|Nick Reid |Evolution
+|Niklas Gustavsson |
+|Ning Li |
+|Noah Nordrum |
+|Oliver Belikan |
+|Ozgur Cetinturk |
+|Paul Smith |
+|Paul Wai |
+|Pawel Tucholski |
+|Peter Henning |
+|Przemyslaw Budzik |
+|Radek Sedmak |
+|Reuben Garrett |
+|Robert Liguori |Solentus
+|Robin Roos |Dresdner Kleinwort Wasserstein
+|Ross Mason |
+|Sachin Handiekar |
+|Sami Dalouche |
+|Sanjiv Jivan |
+|Steven Marcus |
+|Taariq Levack |
+|Tadayoshi Sato |Red Hat
+|Taylor Gautier |
+|Thomas Heller |
+|Trevor Pounds |
+|Viral Gohel |Red Hat
+|Xueqiang Mi |
+|===========================================
diff --git a/docs/user-manual/en/transactionerrorhandler.adoc b/docs/user-manual/en/transactionerrorhandler.adoc
index 8288511..3f5bccf 100644
--- a/docs/user-manual/en/transactionerrorhandler.adoc
+++ b/docs/user-manual/en/transactionerrorhandler.adoc
@@ -175,4 +175,4 @@ from("direct:fail")
* link:error-handler.adoc[Error Handler]
* link:error-handling-in-camel.adoc[Error handling in Camel]
-* <<TransactionalClient-TransactionalClient,Transactional Client>>
+* <<transactionalClient-eip,Transactional Client>>
diff --git a/docs/user-manual/en/component.adoc b/docs/user-manual/en/transport.adoc
similarity index 53%
copy from docs/user-manual/en/component.adoc
copy to docs/user-manual/en/transport.adoc
index fa801b3..d13f1e2 100644
--- a/docs/user-manual/en/component.adoc
+++ b/docs/user-manual/en/transport.adoc
@@ -1,21 +1,18 @@
-[[Component-Components]]
-=== Components
+[[Transport-Transports]]
+=== Transports
-A Component is essentially a factory of link:endpoint.adoc[Endpoint] instances.
+Apache Camel supports a number of different plugable componets for
+talking to different transports. The transports is implement as Camel
+components.
-You can explicitly configure Component instances
-and add them to a link:camelcontext.adoc[CamelContext] in an IoC
-container like Spring or Guice, or they can be auto-discovered using
-link:uris.adoc[URIs].
-
-[[Component-ComponentsIncluded]]
+[[Transport-ComponentsIncluded]]
==== Components Included
Camel includes the following Component implementations via link:uris.adoc[URIs].
[IMPORTANT]
====
-Make sure to read link:how-do-i-configure-endpoints.adoc[How do I configure endpoints?]
+Make sure to read link:faq/how-do-i-configure-endpoints.adoc[How do I configure endpoints?]
to learn more about configuring endpoints. For
example how to refer to beans in the link:registry.adoc[Registry] or how
to use raw values for password options, and using
@@ -31,12 +28,12 @@ include::../../../camel-core/readme.adoc[]
include::../../../components/readme.adoc[]
-[[Component-SeeAlso]]
+[[Transport-SeeAlso]]
==== See Also
* link:endpoint.adoc[Endpoint]
* link:uris.adoc[URIs]
* link:writing-components.adoc[Writing Components]
-* link:how-do-i-add-a-component.adoc[How do I add a component]
-* link:how-do-i-configure-endpoints.adoc[How do I configure endpoints?]
+* link:configuring-camel.adoc[How do I add a component?]
+* link:faq/how-do-i-configure-endpoints.adoc[How do I configure endpoints?]
* link:using-propertyplaceholder.adoc[Using `PropertyPlaceholder`]
diff --git a/docs/user-manual/en/type-converter.adoc b/docs/user-manual/en/type-converter.adoc
new file mode 100644
index 0000000..7ce937b
--- /dev/null
+++ b/docs/user-manual/en/type-converter.adoc
@@ -0,0 +1,403 @@
+[[TypeConverter-TypeConverter]]
+=== Type Converter
+
+It is very common when routing messages from one endpoint to another to
+need to convert the body payloads from one type to another such as to
+convert to and from the following common types:
+
+* File
+* String
+* byte[] and ByteBuffer
+* InputStream and OutputStream
+* Reader and Writer
+* Document and Source
+* ...
+
+The
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Message.html[Message
+interface] defines a helper method to allow conversions to be done via
+the
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Message.html#getBody(java.lang.Class)[getBody(Class)]
+method.
+
+So in an endpoint you can convert a body to another type via:
+
+[source,java]
+----
+Message message = exchange.getIn();
+Document document = message.getBody(Document.class);
+----
+
+[[TypeConverter-HowTypeConversionworks]]
+==== How Type Conversion works
+
+The type conversion strategy is defined by the
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/TypeConverter.html[TypeConverter]
+interface that can be customized on a
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html[CamelContext].
+
+The default implementation,
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/DefaultTypeConverter.html[DefaultTypeConverter],
+uses pluggable strategies to load type converters via
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/TypeConverterLoader.html[TypeConverterLoader].
+The default strategy,
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/AnnotationTypeConverterLoader.html[AnnotationTypeConverterLoader],
+uses a discovery mechanism to find converters.
+
+*New in Camel 1.5*
+
+The default implementation,
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/DefaultTypeConverter.html[DefaultTypeConverter],
+now throws a
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/NoTypeConversionAvailableException.html[NoTypeConversionAvailableException]
+if a suitable conversion cannot be found
+(https://issues.apache.org/jira/browse/CAMEL-84[CAMEL-84]).
+The semantical ambiguity of `null` (both valid result and indication
+of no conversion found) is now resolved, but this may impact existing
+code in that it should now catch the exception instead of checking
+for `null`.
+
+[[TypeConverter-TypeConverterRegistry]]
+==== TypeConverterRegistry
+
+*New in Camel 2.0*
+
+Exposed the
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/TypeConverterRegistry.html[TypeConverterRegistry]
+from link:camelcontext.adoc[CamelContext] so end users more easily will
+be able to add type converters at runtime. This is also usable in
+situations where the default discovering of type converters fails on
+platforms with classloading issues.
+
+To access the registry, you get it from the `CamelContext`:
+
+[source,java]
+----
+CamelContext context = ...
+context.getTypeConverterRegistry()
+----
+
+[[TypeConverter-TypeConverterRegistryutilizationstatistics]]
+===== TypeConverterRegistry utilization statistics
+
+Camel can gather utilization statistics of the runtime usage of type
+converters. These stats are available in JMX, and as well as from the
+`getStatistics()` method from `TypeConverterRegistry`.
+
+From *Camel 2.11.0/2.10.5* onwards these statistics are turned off by
+default as there is some performance overhead under very high concurrent
+load. To enable the statistics in Java, do the following:
+
+[source,java]
+----
+CamelContext context = ...
+context.setTypeConverterStatisticsEnabled(true);
+----
+
+Or in the XML DSL with:
+
+[source,xml]
+----
+<camelContext xmlns="http://camel.apache.org/schema/spring" typeConverterStatisticsEnabled="true">
+ ...
+</camelContext>
+----
+
+[[TypeConverter-Addtypeconverteratruntime]]
+===== Add type converter at runtime
+
+The following sample demonstrates how to add a type converter at
+runtime: +
+link:../../../camel-core/src/test/java/org/apache/camel/impl/TypeConverterRegistryTest.java[/camel-core/src/test/java/org/apache/camel/impl/TypeConverterRegistryTest.java]
+
+And our type converter is implemented as: +
+link:../../../camel-core/src/test/java/org/apache/camel/impl/TypeConverterRegistryTest.java[/camel-core/src/test/java/org/apache/camel/impl/TypeConverterRegistryTest.java]
+
+And then we can convert from String to MyOrder as we are used to with the
+type converter: +
+link:../../../camel-core/src/test/java/org/apache/camel/impl/TypeConverterRegistryTest.java[/camel-core/src/test/java/org/apache/camel/impl/TypeConverterRegistryTest.java]
+
+[[TypeConverter-Addtypeconverterclassesatruntime]]
+===== Add type converter classes at runtime
+
+*Available as of Camel 2.16*
+
+From Camel 2.16 onwards you type converter classes can
+implement `org.apache.camel.TypeConverters` which is an marker
+interface. Then for each type converter you want use
+the `@Converter` annotation.
+
+[source,java]
+----
+private class MyOrderTypeConverters implements TypeConverters {
+ @Converter
+ public MyOrder toMyOrder(String orderId) {
+ MyOrder order = new MyOrder();
+ order.setId(Integer.parseInt(orderId));
+ return order;
+ }
+}
+----
+
+Then you can add these converters to the registry using:
+
+[source,xml]
+----
+MyOrderTypeConverters myClass = ...
+context.getTypeConverterRegistry().addTypeConverters(myClass);
+----
+
+If you are using Spring or Blueprint, then you can just declare a `<bean>`
+then `CamelContext` will automatic discover and add the converters.
+
+[source,xml]
+----
+<bean id="myOrderTypeConverters" class="..."/>
+ <camelContext ...>
+ ...
+ </camelContext>
+----
+
+You can declare multiple `<bean>`s if you have more clases.
+
+Using this technique do not require to scan the classpath and using the
+file `META-INF/services/org/apache/camel/TypeConverter` as discussed in
+the <<TypeConverter-DiscoveringTypeConverters,Discovering Type Converters>>
+section. However the latter is highly
+recommended when developing Camel components or data formats as then the
+type converters is automatic included out of the box. The functionality
+from this section requires the end users to explicit add the converters
+to their Camel applications.
+
+[[TypeConverter-DiscoveringTypeConverters]]
+==== Discovering Type Converters
+
+The
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/AnnotationTypeConverterLoader.html[AnnotationTypeConverterLoader]
+will search the classpath for a file called
+`META-INF/services/org/apache/camel/TypeConverter`. The contents are
+expected to be comma separated package names. These packages are then
+recursively searched for any objects with the
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Converter[@Converter]
+annotation. Then any method marked with @Converter is assumed to be a
+conversion method; where the parameter is the from value and the return
+is the to value.
+
+E.g. the following shows how to register a converter from `File` to
+`InputStream`:
+
+[source,java]
+----
+@Converter
+public class IOConverter {
+ @Converter
+ public static InputStream toInputStream(File file) throws FileNotFoundException {
+ return new BufferedInputStream(new FileInputStream(file));
+ }
+}
+----
+
+Static methods are invoked; non-static methods require an instance of
+the converter object to be created (which is then cached). If a
+converter requires configuration you can plug in an Injector interface
+to the `DefaultTypeConverter` which can construct and inject converter
+objects via Spring or Guice.
+
+We have most of the common converters for common Java types in the
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/converter/package-summary.html[org.apache.camel.converter]
+package and its children.
+
+[[TypeConverter-Returningnullvalues]]
+===== Returning null values
+
+By default when using a method in a POJO annotation with @Converter
+returning null is not a valid response. If null is returned, then Camel
+will regard that type converter as a _miss_, and prevent from using it
+in the future. If null should be allowed as a valid response, then from
+*Camel 2.11.2/2.12* onwards you can specify this in the annotation as
+shown:
+
+[source,java]
+----
+@Converter(allowNull = true)
+public static InputStream toInputStream(File file) throws IOException {
+ if (file.exist()) {
+ return new BufferedInputStream(new FileInputStream(file));
+ } else {
+ return null;
+ }
+}
+----
+
+[[TypeConverter-DiscoveringFallbackTypeConverters]]
+==== Discovering Fallback Type Converters
+
+*Available in Camel 2.0*
+
+The
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/AnnotationTypeConverterLoader.html[AnnotationTypeConverterLoader]
+has been enhanced to also look for methods defined with a
+`@FallbackConverter` annotation, and register it as a fallback type
+converter.
+
+Fallback type converters are used as a last resort for converting a
+given value to another type. Its used when the regular type converters
+give up.
+The fallback converters is also meant for a broader scope, so its method
+signature is a bit different:
+
+[source,java]
+----
+@FallbackConverter
+public static <T> T convertTo(Class<T> type, Exchange exchange, Object value, TypeConverterRegistry registry)
+----
+
+Or you can use the non generic signature.
+
+[source,java]
+----
+@FallbackConverter
+public static Object convertTo(Class type, Exchange exchange, Object value, TypeConverterRegistry registry)
+----
+
+And the method name can be anything (`convertTo` is not required as a
+name), so it can be named `convertMySpecialTypes` if you like. +
+The `Exchange` parameter is optional, just as its with the regular
+`@Converter` methods.
+
+The purpose with this broad scope method signature is allowing you to
+control if you can convert the given type or not. The `type` parameter
+holds the type we want the `value` converted to. Its used internally in
+Camel for wrapper objects so we can delegate the type convertions to the
+body that is wrapped.
+
+For instance in the method below we will handle all type conversions
+that is based on the wrapper class `GenericFile` and we let Camel do the
+type conversions on its body instead.
+
+[source,java]
+----
+@FallbackConverter
+public static <T> T convertTo(Class<T> type, Exchange exchange, Object value, TypeConverterRegistry registry) {
+ // use a fallback type converter so we can convert the embedded body
+ // if the value is GenericFile
+ if (GenericFile.class.isAssignableFrom(value.getClass())) {
+ GenericFile file = (GenericFile) value;
+ Class from = file.getBody().getClass();
+ TypeConverter tc = registry.lookup(type, from);
+ if (tc != null) {
+ Object body = file.getBody();
+ return tc.convertTo(type, exchange, body);
+ }
+ }
+ return null;
+}
+----
+
+[[TypeConverter-WritingyourownTypeConverters]]
+==== Writing your own Type Converters
+
+[NOTE]
+====
+*Use FQN*
+
+In Camel 2.8 the TypeConverter file now supports specifying the FQN
+class name. This is recommended to be used. See below for more details.
+Using FQN must be used. The older way with just package name is
+deprecated and should not be used, and it may also not work in some
+application servers due to classpath scanning issues.
+====
+
+
+You are welcome to write your own converters. Remember to use the
+`@Converter` annotations on the classes and methods you wish to use. Then
+add the packages to a file called
+`META-INF/services/org/apache/camel/TypeConverter` in your jar. Remember
+to make sure that :
+
+* static methods are encouraged to reduce caching, but instance methods
+are fine, particularly if you want to allow optional dependency
+injection to customize the converter
+* converter methods should be thread safe and reentrant
+
+[[TypeConverter-ExamplesofTypeConverterfile]]
+===== Examples of TypeConverter file
+
+The file in the JAR: `META-INF/services/org/apache/camel/TypeConverter`
+contains the following line(s):
+
+----
+com.foo com.bar
+----
+
+Each line in the file is a package name. This tells Camel to go scan
+those packages for any classes that has been annotated with the
+`@Converter`.
+
+[[TypeConverter-ImprovedTypeConverterbyusingFQNclassnames]]
+===== Improved TypeConverter by using FQN class names
+
+*Available as of Camel 2.8*
+
+In Camel 2.8 we improved the type converter loader to support specifying
+the FQN class name of the converter classes. This has the advantage of
+avoiding having to scan packages for `@Converter` classes. Instead it
+loads the `@Converter` class directly. This is a *highly* recommend
+approach to use going forward.
+
+[[TypeConverter-ExamplesofTypeConverterfile.1]]
+===== Examples of TypeConverter file
+
+The file in the JAR: `META-INF/services/org/apache/camel/TypeConverter`
+contains the following line(s) for FQN class names:
+
+----
+com.foo.MyConverter
+com.bar.MyOtherConverter
+com.bar.YetOtherConverter
+----
+
+As you can see each line in the file now contains a FQN class name. This
+is the recommended approach.
+
+[[TypeConverter-Encodingsupportforbyte[]andStringConversion]]
+==== Encoding support for byte[] and String Conversion
+
+*Available in Camel 1.5*
+
+Since Java provides converting the `byte[]` to `String` and `String` to `byte[]`
+with the
+http://java.sun.com/j2se/1.5.0/docs/api/java/nio/charset/Charset.html[charset
+name] parameter. You can define the charset name by setting the exchange
+property name `Exchange.CHARSET_NAME` with the charset name, such as
+`"UTF-8"` or `"iso-8859-1"`.
+
+[[TypeConverter-Exchangeparameter]]
+==== Exchange parameter
+
+*Available in Camel 1.5*
+
+The type converter accepts the `Exchange` as an optional 2nd parameter.
+This is usable if the type converter for instance needs information from
+the current exchange. For instance combined with the encoding support
+its possible for type converters to convert with the configured
+encoding. An example from camel-core for the `byte[]` -> `String`
+converter:
+
+[source,java]
+----
+@Converter
+public static String toString(byte[] data, Exchange exchange) {
+ if (exchange != null) {
+ String charsetName = exchange.getProperty(Exchange.CHARSET_NAME, String.class);
+ if (charsetName != null) {
+ try {
+ return new String(data, charsetName);
+ } catch (UnsupportedEncodingException e) {
+ LOG.warn("Can't convert the byte to String with the charset " + charsetName, e);
+ }
+ }
+ }
+ return new String(data);
+}
+----
diff --git a/docs/user-manual/en/uris.adoc b/docs/user-manual/en/uris.adoc
index 54a6c45..c3f7de5 100644
--- a/docs/user-manual/en/uris.adoc
+++ b/docs/user-manual/en/uris.adoc
@@ -8,7 +8,7 @@ refer to them within link:routes.adoc[Routes].
[IMPORTANT]
====
Make sure to read
-link:how-do-i-configure-endpoints.adoc[How do I configure endpoints]
+link:faq/how-do-i-configure-endpoints.adoc[How do I configure endpoints]
to learn more about configuring endpoints. For
example how to refer to beans in the link:registry.adoc[Registry] or how
to use raw values for password options, and using
diff --git a/docs/user-manual/en/using-propertyplaceholder.adoc b/docs/user-manual/en/using-propertyplaceholder.adoc
index 4f016b1..6dc99a9 100644
--- a/docs/user-manual/en/using-propertyplaceholder.adoc
+++ b/docs/user-manual/en/using-propertyplaceholder.adoc
@@ -11,7 +11,7 @@ limitation that prevents third-party frameworks from fully leveraging
Spring property placeholders.
For more details see:
-link:how-do-i-use-spring-property-placeholder-with-camel-xml.adoc[How do
+link:faq/how-do-i-use-spring-property-placeholder-with-camel-xml.adoc[How do
I use Spring Property Placeholder with Camel XML].
[[UsingPropertyPlaceholder-BridgingSpringandCamelPropertyPlaceholders]]
diff --git a/docs/user-manual/en/vtd-xml.adoc b/docs/user-manual/en/vtd-xml.adoc
new file mode 100644
index 0000000..aae8e50
--- /dev/null
+++ b/docs/user-manual/en/vtd-xml.adoc
@@ -0,0 +1,51 @@
+[[VTD-XML-VTD-XML]]
+=== VTD-XML
+
+*Available as of Camel 2.10*
+
+The VTD-XML component supports the
+http://vtd-xml.sourceforge.net/[VTD-XML Library] for very fast and
+efficient <<xpath-language,XPath>> processing. The *camel-vtdxml* library
+is provided by the https://github.com/camel-extra/camel-extra[Camel Extra]
+project which hosts all *GPL* related components for Camel.
+
+[[VTD-XML-Using]]
+==== Using
+
+The VTD-XML is implemented as a Camel <<language-component,Language>> which
+allows you to easily use it in the Camel routes. This component is particular efficient for splitting files or other big
+payloads.
+
+For example to split a big file containing many persons, you could do:
+
+[source,java]
+----
+from("file:inbox")
+ .split().vtdxml("/persons/person").streaming()
+ .to("activemq:queue:person")
+ .end()
+----
+
+And in XML DSL:
+
+[source,xml]
+----
+<route>
+ <from uri="file:inbox"/>
+ <split streaming="true">
+ <vtdxml>/persons/person</vtdxml>
+ <to uri="activemq:queue:person"/>
+ </split>
+</route>
+----
+
+This will run the <<split-eip,Splitter>> in streaming mode using
+the *vtdxml* language.
+
+[[VTD-XML-SeeAlso]]
+==== See Also
+
+* link:configuring-camel.adoc[Configuring Camel]
+* link:component.adoc[Component]
+* link:endpoint.adoc[Endpoint]
+* link:getting-started.adoc[Getting Started]
diff --git a/docs/user-manual/en/xml-configuration.adoc b/docs/user-manual/en/xml-configuration.adoc
new file mode 100644
index 0000000..6754ffa
--- /dev/null
+++ b/docs/user-manual/en/xml-configuration.adoc
@@ -0,0 +1,25 @@
+[[XMLConfiguration-XMLConfiguration]]
+=== XML Configuration
+
+We recommend developers use the Java link:dsl.adoc[Domain Specific
+Language] when writing routing rules as this provides maximum IDE
+completion and functionality while being the most expressive. However if
+you wish to put your routing rules in XML you can via the Camel XML
+language.
+
+Camel XML uses link:spring.adoc[Spring] 2 namespaces; so that you can
+configure your routing rules within your link:spring.adoc[Spring XML
+configuration file]; you can also use
+link:faq/how-do-i-configure-endpoints.adoc[Java code to configure components
+and endpoints].
+
+For examples on how to use Camel XML, see the
+link:enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns] or refer to the link:spring.adoc[Spring Support].
+
+[[XMLConfiguration-SeeAlso]]
+=== See Also
+
+* link:xml-reference.adoc[XML Reference]
+* link:faq/how-do-i-use-spring-property-placeholder-with-camel-xml.adoc[How
+do I use Spring Property Placeholder with Camel XML]
diff --git a/docs/user-manual/en/xml-reference.adoc b/docs/user-manual/en/xml-reference.adoc
new file mode 100644
index 0000000..c67d028
--- /dev/null
+++ b/docs/user-manual/en/xml-reference.adoc
@@ -0,0 +1,1436 @@
+[[XMLReference-CamelXMLReference]]
+=== Camel XML Reference
+
+This page contains a link to the XML schema documents for
+link:xml-configuration.adoc[XML Configuration] with Camel releases. You
+can refer to http://camel.apache.org/schema/ to see the individual XSDs
+available.
+
+[[XMLReference-ReleasedSchemas-Spring]]
+==== Released Schemas - Spring
+
+[width="100%",cols="50%,50%",options="header",]
+|=======================================================================
+|Version |XML Schema
+|2.20.2 |http://camel.apache.org/schema/spring/camel-spring-2.20.2.xsd
+
+|2.20.1 |http://camel.apache.org/schema/spring/camel-spring-2.20.1.xsd
+
+|2.20.0 |http://camel.apache.org/schema/spring/camel-spring-2.20.0.xsd
+
+|2.19.4 |http://camel.apache.org/schema/spring/camel-spring-2.19.4.xsd
+
+|2.19.3 |http://camel.apache.org/schema/spring/camel-spring-2.19.3.xsd
+
+|2.19.2 |http://camel.apache.org/schema/spring/camel-spring-2.19.2.xsd
+
+|2.19.1 |http://camel.apache.org/schema/spring/camel-spring-2.19.1.xsd
+
+|2.19.0 |http://camel.apache.org/schema/spring/camel-spring-2.19.0.xsd
+
+|2.18.5 |http://camel.apache.org/schema/spring/camel-spring-2.18.5.xsd
+
+|2.18.4 |http://camel.apache.org/schema/spring/camel-spring-2.18.4.xsd
+
+|2.18.3 |http://camel.apache.org/schema/spring/camel-spring-2.18.3.xsd
+
+|2.18.2 |http://camel.apache.org/schema/spring/camel-spring-2.18.2.xsd
+
+|2.18.1 |http://camel.apache.org/schema/spring/camel-spring-2.18.1.xsd
+
+|2.18.0 |http://camel.apache.org/schema/spring/camel-spring-2.18.0.xsd
+
+|2.17.7 |http://camel.apache.org/schema/spring/camel-spring-2.17.7.xsd
+
+|2.17.6 |http://camel.apache.org/schema/spring/camel-spring-2.17.6.xsd
+
+|2.17.5 |http://camel.apache.org/schema/spring/camel-spring-2.17.5.xsd
+
+|2.17.4 |http://camel.apache.org/schema/spring/camel-spring-2.17.4.xsd
+
+|2.17.3 |http://camel.apache.org/schema/spring/camel-spring-2.17.3.xsd
+
+|2.17.2 |http://camel.apache.org/schema/spring/camel-spring-2.17.2.xsd
+
+|2.17.1 |http://camel.apache.org/schema/spring/camel-spring-2.17.1.xsd
+
+|2.17.0 |http://camel.apache.org/schema/spring/camel-spring-2.17.0.xsd
+
+|2.16.4 |http://camel.apache.org/schema/spring/camel-spring-2.16.4.xsd
+
+|2.16.3 |http://camel.apache.org/schema/spring/camel-spring-2.16.3.xsd
+
+|2.16.2 |http://camel.apache.org/schema/spring/camel-spring-2.16.2.xsd
+
+|2.16.1 |http://camel.apache.org/schema/spring/camel-spring-2.16.1.xsd
+
+|2.16.0 |http://camel.apache.org/schema/spring/camel-spring-2.16.0.xsd
+
+|2.15.6 |http://camel.apache.org/schema/spring/camel-spring-2.15.6.xsd
+
+|2.15.5 |http://camel.apache.org/schema/spring/camel-spring-2.15.5.xsd
+
+|2.15.4 |http://camel.apache.org/schema/spring/camel-spring-2.15.4.xsd
+
+|2.15.3 |http://camel.apache.org/schema/spring/camel-spring-2.15.3.xsd
+
+|2.15.2 |http://camel.apache.org/schema/spring/camel-spring-2.15.2.xsd
+
+|2.15.1 |http://camel.apache.org/schema/spring/camel-spring-2.15.1.xsd
+
+|2.15.0 |http://camel.apache.org/schema/spring/camel-spring-2.15.0.xsd
+
+|2.14.4 |http://camel.apache.org/schema/spring/camel-spring-2.14.4.xsd
+
+|2.14.3 |http://camel.apache.org/schema/spring/camel-spring-2.14.3.xsd
+
+|2.14.2 |http://camel.apache.org/schema/spring/camel-spring-2.14.2.xsd
+
+|2.14.1 |http://camel.apache.org/schema/spring/camel-spring-2.14.1.xsd
+
+|2.14.0 |http://camel.apache.org/schema/spring/camel-spring-2.14.0.xsd
+
+|2.13.4 |http://camel.apache.org/schema/spring/camel-spring-2.13.4.xsd
+
+|2.13.3 |http://camel.apache.org/schema/spring/camel-spring-2.13.3.xsd
+
+|2.13.2 |http://camel.apache.org/schema/spring/camel-spring-2.13.2.xsd
+
+|2.13.1 |http://camel.apache.org/schema/spring/camel-spring-2.13.1.xsd
+
+|2.13.0 |http://camel.apache.org/schema/spring/camel-spring-2.12.3.xsd
+
+|2.12.5 |http://camel.apache.org/schema/spring/camel-spring-2.12.5.xsd
+
+|2.12.4 |http://camel.apache.org/schema/spring/camel-spring-2.12.4.xsd
+
+|2.12.3 |http://camel.apache.org/schema/spring/camel-spring-2.12.3.xsd
+
+|2.12.2 |http://camel.apache.org/schema/spring/camel-spring-2.12.2.xsd
+
+|2.12.1 |http://camel.apache.org/schema/spring/camel-spring-2.12.1.xsd
+
+|2.12.0 |http://camel.apache.org/schema/spring/camel-spring-2.12.0.xsd
+
+|2.11.4 |http://camel.apache.org/schema/spring/camel-spring-2.11.4.xsd
+
+|2.11.3 |http://camel.apache.org/schema/spring/camel-spring-2.11.3.xsd
+
+|2.11.2 |http://camel.apache.org/schema/spring/camel-spring-2.11.2.xsd
+
+|2.11.1 |http://camel.apache.org/schema/spring/camel-spring-2.11.1.xsd
+
+|2.11.0 |http://camel.apache.org/schema/spring/camel-spring-2.11.0.xsd
+
+|2.10.7 |http://camel.apache.org/schema/spring/camel-spring-2.10.7.xsd
+
+|2.10.6 |http://camel.apache.org/schema/spring/camel-spring-2.10.6.xsd
+
+|2.10.5 |http://camel.apache.org/schema/spring/camel-spring-2.10.5.xsd
+
+|2.10.4 |http://camel.apache.org/schema/spring/camel-spring-2.10.4.xsd
+
+|2.10.3 |http://camel.apache.org/schema/spring/camel-spring-2.10.3.xsd
+
+|2.10.2 |http://camel.apache.org/schema/spring/camel-spring-2.10.2.xsd
+
+|2.10.1 |http://camel.apache.org/schema/spring/camel-spring-2.10.1.xsd
+
+|2.10.0 |http://camel.apache.org/schema/spring/camel-spring-2.10.0.xsd
+
+|2.9.8 |http://camel.apache.org/schema/spring/camel-spring-2.9.8.xsd
+
+|2.9.7 |http://camel.apache.org/schema/spring/camel-spring-2.9.7.xsd
+
+|2.9.6 |http://camel.apache.org/schema/spring/camel-spring-2.9.6.xsd
+
+|2.9.5 |http://camel.apache.org/schema/spring/camel-spring-2.9.5.xsd
+
+|2.9.4 |http://camel.apache.org/schema/spring/camel-spring-2.9.4.xsd
+
+|2.9.3 |http://camel.apache.org/schema/spring/camel-spring-2.9.3.xsd
+
+|2.9.2 |http://camel.apache.org/schema/spring/camel-spring-2.9.2.xsd
+
+|2.9.1 |http://camel.apache.org/schema/spring/camel-spring-2.9.1.xsd
+
+|2.9.0 |http://camel.apache.org/schema/spring/camel-spring-2.9.0.xsd
+
+|2.8.6 |http://camel.apache.org/schema/spring/camel-spring-2.8.6.xsd
+
+|2.8.5 |http://camel.apache.org/schema/spring/camel-spring-2.8.5.xsd
+
+|2.8.4 |http://camel.apache.org/schema/spring/camel-spring-2.8.4.xsd
+
+|2.8.3 |http://camel.apache.org/schema/spring/camel-spring-2.8.3.xsd
+
+|2.8.2 |http://camel.apache.org/schema/spring/camel-spring-2.8.2.xsd
+
+|2.8.1 |http://camel.apache.org/schema/spring/camel-spring-2.8.1.xsd
+
+|2.8.0 |http://camel.apache.org/schema/spring/camel-spring-2.8.0.xsd
+
+|2.7.5 |http://camel.apache.org/schema/spring/camel-spring-2.7.5.xsd
+
+|2.7.4 |http://camel.apache.org/schema/spring/camel-spring-2.7.4.xsd
+
+|2.7.3 |http://camel.apache.org/schema/spring/camel-spring-2.7.3.xsd
+
+|2.7.2 |http://camel.apache.org/schema/spring/camel-spring-2.7.2.xsd
+
+|2.7.1 |http://camel.apache.org/schema/spring/camel-spring-2.7.1.xsd
+
+|2.7.0 |http://camel.apache.org/schema/spring/camel-spring-2.7.0.xsd
+
+|2.6.0 |http://camel.apache.org/schema/spring/camel-spring-2.6.0.xsd
+
+|2.5.0 |http://camel.apache.org/schema/spring/camel-spring-2.5.0.xsd
+
+|2.4.0 |http://camel.apache.org/schema/spring/camel-spring-2.4.0.xsd
+
+|2.3.0 |http://camel.apache.org/schema/spring/camel-spring-2.3.0.xsd
+
+|2.2.0 |http://camel.apache.org/schema/spring/camel-spring-2.2.0.xsd
+
+|2.1.0 |http://camel.apache.org/schema/spring/camel-spring-2.1.0.xsd
+
+|2.0.0 |http://camel.apache.org/schema/spring/camel-spring-2.0.0.xsd
+
+|1.6.4 |http://camel.apache.org/schema/spring/camel-spring-1.6.4.xsd
+
+|1.6.3 |http://camel.apache.org/schema/spring/camel-spring-1.6.3.xsd
+
+|1.6.2 |http://camel.apache.org/schema/spring/camel-spring-1.6.2.xsd
+
+|1.6.1 |http://camel.apache.org/schema/spring/camel-spring-1.6.1.xsd
+
+|1.6.0 |http://camel.apache.org/schema/spring/camel-spring-1.6.0.xsd
+
+|1.5.0
+|http://activemq.apache.org/camel/schema/spring/camel-spring-1.5.0.xsd
+
+|1.4.0
+|http://activemq.apache.org/camel/schema/spring/camel-spring-1.4.0.xsd
+
+|1.3.0
+|http://activemq.apache.org/camel/schema/spring/camel-spring-1.3.0.xsd
+
+|1.2.0
+|http://activemq.apache.org/camel/schema/spring/camel-spring-1.2.0.xsd
+
+|1.1.0
+|http://activemq.apache.org/camel/schema/spring/camel-spring-1.1.0.xsd
+
+|1.0.0
+|http://activemq.apache.org/camel/schema/spring/camel-spring-1.0.0.xsd
+|=======================================================================
+
+[[XMLReference-ReleasedSchemas-Blueprint]]
+==== Released Schemas - Blueprint
+
+[width="100%",cols="50%,50%",options="header",]
+|=======================================================================
+|Version |XML Schema
+|2.20.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.20.2.xsd
+
+|2.20.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.20.1.xsd
+
+|2.20.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.20.0.xsd
+
+|2.19.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.19.4.xsd
+
+|2.19.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.19.3.xsd
+
+|2.19.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.19.2.xsd
+
+|2.19.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.19.1.xsd
+
+|2.19.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.19.0.xsd
+
+|2.18.5
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.18.5.xsd
+
+|2.18.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.18.4.xsd
+
+|2.18.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.18.3.xsd
+
+|2.18.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.18.2.xsd
+
+|2.18.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.18.1.xsd
+
+|2.18.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.18.0.xsd
+
+|2.17.7
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.17.7.xsd
+
+|2.17.6
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.17.6.xsd
+
+|2.17.5
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.17.5.xsd
+
+|2.17.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.17.4.xsd
+
+|2.17.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.17.3.xsd
+
+|2.17.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.17.2.xsd
+
+|2.17.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.17.1.xsd
+
+|2.17.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.17.0.xsd
+
+|2.16.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.16.4.xsd
+
+|2.16.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.16.3.xsd
+
+|2.16.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.16.2.xsd
+
+|2.16.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.16.1.xsd
+
+|2.16.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.16.0.xsd
+
+|2.15.6
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.15.6.xsd
+
+|2.15.5
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.15.5.xsd
+
+|2.15.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.15.4.xsd
+
+|2.15.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.15.3.xsd
+
+|2.15.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.15.2.xsd
+
+|2.15.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.15.1.xsd
+
+|2.15.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.15.0.xsd
+
+|2.14.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.14.4.xsd
+
+|2.14.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.14.3.xsd
+
+|2.14.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.14.2.xsd
+
+|2.14.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.14.1.xsd
+
+|2.14.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.14.0.xsd
+
+|2.13.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.13.4.xsd
+
+|2.13.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.13.3.xsd
+
+|2.13.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.13.3.xsd
+
+|2.13.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.13.1.xsd
+
+|2.13.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.13.0.xsd
+
+|2.12.5
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.12.5.xsd
+
+|2.12.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.12.4.xsd
+
+|2.12.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.12.3.xsd
+
+|2.12.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.12.2.xsd
+
+|2.12.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.12.1.xsd
+
+|2.12.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.12.0.xsd
+
+|2.11.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.11.4.xsd
+
+|2.11.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.11.3.xsd
+
+|2.11.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.11.2.xsd
+
+|2.11.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.11.1.xsd
+
+|2.11.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.11.0.xsd
+
+|2.10.7
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.10.7.xsd
+
+|2.10.6
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.10.6.xsd
+
+|2.10.5
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.10.5.xsd
+
+|2.10.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.10.4.xsd
+
+|2.10.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.10.3.xsd
+
+|2.10.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.10.2.xsd
+
+|2.10.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.10.1.xsd
+
+|2.10.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.10.0.xsd
+
+|2.9.8
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.9.8.xsd
+
+|2.9.7
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.9.7.xsd
+
+|2.9.6
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.9.6.xsd
+
+|2.9.5
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.9.5.xsd
+
+|2.9.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.9.4.xsd
+
+|2.9.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.9.3.xsd
+
+|2.9.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.9.2.xsd
+
+|2.9.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.9.1.xsd
+
+|2.9.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.9.0.xsd
+
+|2.8.6
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.8.6.xsd
+
+|2.8.5
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.8.5.xsd
+
+|2.8.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.8.4.xsd
+
+|2.8.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.8.3.xsd
+
+|2.8.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.8.2.xsd
+
+|2.8.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.8.1.xsd
+
+|2.8.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.8.0.xsd
+
+|2.7.5
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.7.5.xsd
+
+|2.7.4
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.7.4.xsd
+
+|2.7.3
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.7.3.xsd
+
+|2.7.2
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.7.2.xsd
+
+|2.7.1
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.7.1.xsd
+
+|2.7.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.7.0.xsd
+
+|2.6.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.6.0.xsd
+
+|2.5.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.5.0.xsd
+
+|2.4.0
+|http://camel.apache.org/schema/blueprint/camel-blueprint-2.4.0.xsd
+|=======================================================================
+
+[[XMLReference-ReleasedSchemas-CXFSpring]]
+==== Released Schemas - CXF Spring
+
+[width="100%",cols="50%,50%",options="header",]
+|======================================================================
+|Version |XML Schema
+|2.20.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.20.1-spring.xsd
+|2.20.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.20.0-spring.xsd
+|2.19.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.19.4-spring.xsd
+|2.19.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.19.3-spring.xsd
+|2.19.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.19.2-spring.xsd
+|2.19.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.19.1-spring.xsd
+|2.19.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.19.0-spring.xsd
+|2.18.5 |http://camel.apache.org/schema/cxf/camel-cxf-2.18.5-spring.xsd
+|2.18.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.18.4-spring.xsd
+|2.18.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.18.3-spring.xsd
+|2.18.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.18.2-spring.xsd
+|2.18.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.18.1-spring.xsd
+|2.18.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.18.0-spring.xsd
+|2.17.7 |http://camel.apache.org/schema/cxf/camel-cxf-2.17.7-spring.xsd
+|2.17.6 |http://camel.apache.org/schema/cxf/camel-cxf-2.17.6-spring.xsd
+|2.17.5 |http://camel.apache.org/schema/cxf/camel-cxf-2.17.5-spring.xsd
+|2.17.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.17.4-spring.xsd
+|2.17.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.17.3-spring.xsd
+|2.17.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.17.2-spring.xsd
+|2.17.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.17.1-spring.xsd
+|2.17.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.17.0-spring.xsd
+|2.16.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.16.4-spring.xsd
+|2.16.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.16.3-spring.xsd
+|2.16.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.16.2-spring.xsd
+|2.16.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.16.1-spring.xsd
+|2.16.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.16.0-spring.xsd
+|2.15.6 |http://camel.apache.org/schema/cxf/camel-cxf-2.15.6-spring.xsd
+|2.15.5 |http://camel.apache.org/schema/cxf/camel-cxf-2.15.5-spring.xsd
+|2.15.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.15.4-spring.xsd
+|2.15.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.15.3-spring.xsd
+|2.15.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.15.2-spring.xsd
+|2.15.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.15.1-spring.xsd
+|2.15.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.15.0-spring.xsd
+|2.14.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.14.4-spring.xsd
+|2.14.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.14.3-spring.xsd
+|2.14.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.14.2-spring.xsd
+|2.14.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.14.1-spring.xsd
+|2.14.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.14.0-spring.xsd
+|2.13.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.13.4-spring.xsd
+|2.13.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.13.3-spring.xsd
+|2.13.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.13.2-spring.xsd
+|2.13.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.13.1-spring.xsd
+|2.13.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.13.0-spring.xsd
+|2.12.5 |http://camel.apache.org/schema/cxf/camel-cxf-2.12.5-spring.xsd
+|2.12.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.12.4-spring.xsd
+|2.12.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.12.3-spring.xsd
+|2.12.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.12.2-spring.xsd
+|2.12.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.12.1-spring.xsd
+|2.12.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.12.0-spring.xsd
+|2.11.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.11.4-spring.xsd
+|2.11.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.11.3-spring.xsd
+|2.11.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.11.2-spring.xsd
+|2.11.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.11.1-spring.xsd
+|2.11.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.11.0-spring.xsd
+|2.10.7 |http://camel.apache.org/schema/cxf/camel-cxf-2.10.7-spring.xsd
+|2.10.6 |http://camel.apache.org/schema/cxf/camel-cxf-2.10.6-spring.xsd
+|2.10.5 |http://camel.apache.org/schema/cxf/camel-cxf-2.10.5-spring.xsd
+|2.10.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.10.4-spring.xsd
+|2.10.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.10.3-spring.xsd
+|2.10.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.10.2-spring.xsd
+|2.10.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.10.1-spring.xsd
+|2.10.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.10.0-spring.xsd
+|2.9.8 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.8-spring.xsd
+|2.9.7 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.7-spring.xsd
+|2.9.6 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.6-spring.xsd
+|2.9.5 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.5-spring.xsd
+|2.9.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.4-spring.xsd
+|2.9.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.3-spring.xsd
+|2.9.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.2-spring.xsd
+|2.9.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.1-spring.xsd
+|2.9.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.0.xsd
+|2.8.6 |http://camel.apache.org/schema/cxf/camel-cxf-2.8.6-spring.xsd
+|2.8.5 |http://camel.apache.org/schema/cxf/camel-cxf-2.8.5-spring.xsd
+|2.8.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.8.4-spring.xsd
+|2.8.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.8.3.xsd
+|2.8.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.8.2.xsd
+|2.8.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.8.1.xsd
+|2.8.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.8.0.xsd
+|2.7.5 |http://camel.apache.org/schema/cxf/camel-cxf-2.7.5.xsd
+|2.7.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.7.4.xsd
+|2.7.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.7.3.xsd
+|2.7.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.7.2.xsd
+|2.7.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.7.1.xsd
+|2.7.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.7.0.xsd
+|2.6.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.6.0.xsd
+|2.5.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.5.0.xsd
+|2.4.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.4.0.xsd
+|2.3.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.3.0.xsd
+|2.2.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.2.0.xsd
+|2.1.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.1.0.xsd
+|2.0.0 |http://camel.apache.org/schema/cxf/camel-cxf-2.0.0.xsd
+|1.6.4 |http://camel.apache.org/schema/cxf/camel-cxf-1.6.4.xsd
+|1.6.3 |http://camel.apache.org/schema/cxf/camel-cxf-1.6.3.xsd
+|1.6.2 |http://camel.apache.org/schema/cxf/camel-cxf-1.6.2.xsd
+|1.6.1 |http://camel.apache.org/schema/cxf/camel-cxf-1.6.1.xsd
+|1.6.0 |http://camel.apache.org/schema/cxf/camel-cxf-1.6.0.xsd
+|1.5.0 |http://activemq.apache.org/camel/schema/cxf/camel-cxf-1.5.0.xsd
+|1.4.0 |http://activemq.apache.org/camel/schema/cxf/camel-cxf-1.4.0.xsd
+|1.3.0 |http://activemq.apache.org/camel/schema/cxf/camel-cxf-1.3.0.xsd
+|======================================================================
+
+[[XMLReference-ReleasedSchemas-CXFblueprint]]
+==== Released Schemas - CXF blueprint
+
+[width="100%",cols="50%,50%",options="header",]
+|=======================================================================
+|Version |XML Schema
+|2.20.2
+|http://camel.apache.org/schema/cxf/camel-cxf-2.20.2-blueprint.xsd
+
+|2.20.1
+|http://camel.apache.org/schema/cxf/camel-cxf-2.20.1-blueprint.xsd
+
+|2.20.0
+|http://camel.apache.org/schema/cxf/camel-cxf-2.20.0-blueprint.xsd
+
+|2.19.4
+|http://camel.apache.org/schema/cxf/camel-cxf-2.19.4-blueprint.xsd
+
+|2.19.3
+|http://camel.apache.org/schema/cxf/camel-cxf-2.19.3-blueprint.xsd
+
+|2.19.2
+|http://camel.apache.org/schema/cxf/camel-cxf-2.19.2-blueprint.xsd
+
+|2.19.1
+|http://camel.apache.org/schema/cxf/camel-cxf-2.19.1-blueprint.xsd
+
+|2.19.0
+|http://camel.apache.org/schema/cxf/camel-cxf-2.19.0-blueprint.xsd
+
+|2.18.5
+|http://camel.apache.org/schema/cxf/camel-cxf-2.18.5-blueprint.xsd
+
+|2.18.4
+|http://camel.apache.org/schema/cxf/camel-cxf-2.18.4-blueprint.xsd
+
+|2.18.3
+|http://camel.apache.org/schema/cxf/camel-cxf-2.18.3-blueprint.xsd
+
+|2.18.2
+|http://camel.apache.org/schema/cxf/camel-cxf-2.18.2-blueprint.xsd
+
+|2.18.1
+|http://camel.apache.org/schema/cxf/camel-cxf-2.18.1-blueprint.xsd
+
+|2.18.0
+|http://camel.apache.org/schema/cxf/camel-cxf-2.18.0-blueprint.xsd
+
+|2.17.7
+|http://camel.apache.org/schema/cxf/camel-cxf-2.17.7-blueprint.xsd
+
+|2.17.6
+|http://camel.apache.org/schema/cxf/camel-cxf-2.17.6-blueprint.xsd
+
+|2.17.5
+|http://camel.apache.org/schema/cxf/camel-cxf-2.17.5-blueprint.xsd
+
+|2.17.4
+|http://camel.apache.org/schema/cxf/camel-cxf-2.17.4-blueprint.xsd
+
+|2.17.3
+|http://camel.apache.org/schema/cxf/camel-cxf-2.17.3-blueprint.xsd
+
+|2.17.2
+|http://camel.apache.org/schema/cxf/camel-cxf-2.17.2-blueprint.xsd
+
+|2.17.1
+|http://camel.apache.org/schema/cxf/camel-cxf-2.17.1-blueprint.xsd
+
+|2.17.0
+|http://camel.apache.org/schema/cxf/camel-cxf-2.17.0-blueprint.xsd
+
+|2.16.4
+|http://camel.apache.org/schema/cxf/camel-cxf-2.16.4-blueprint.xsd
+
+|2.16.3
+|http://camel.apache.org/schema/cxf/camel-cxf-2.16.3-blueprint.xsd
+
+|2.16.2
+|http://camel.apache.org/schema/cxf/camel-cxf-2.16.2-blueprint.xsd
+
+|2.16.1
+|http://camel.apache.org/schema/cxf/camel-cxf-2.16.1-blueprint.xsd
+
+|2.16.0
+|http://camel.apache.org/schema/cxf/camel-cxf-2.16.0-blueprint.xsd
+
+|2.15.6
+|http://camel.apache.org/schema/cxf/camel-cxf-2.15.6-blueprint.xsd
+
+|2.15.5
+|http://camel.apache.org/schema/cxf/camel-cxf-2.15.5-blueprint.xsd
+
+|2.15.4
+|http://camel.apache.org/schema/cxf/camel-cxf-2.15.4-blueprint.xsd
+
+|2.15.3
+|http://camel.apache.org/schema/cxf/camel-cxf-2.15.3-blueprint.xsd
+
+|2.15.2
+|http://camel.apache.org/schema/cxf/camel-cxf-2.15.2-blueprint.xsd
+
+|2.15.1
+|http://camel.apache.org/schema/cxf/camel-cxf-2.15.1-blueprint.xsd
+
+|2.15.0
+|http://camel.apache.org/schema/cxf/camel-cxf-2.15.0-blueprint.xsd
+
+|2.14.4
+|http://camel.apache.org/schema/cxf/camel-cxf-2.14.4-blueprint.xsd
+
+|2.14.3
+|http://camel.apache.org/schema/cxf/camel-cxf-2.14.3-blueprint.xsd
+
+|2.14.2
+|http://camel.apache.org/schema/cxf/camel-cxf-2.14.2-blueprint.xsd
+
+|2.14.1
+|http://camel.apache.org/schema/cxf/camel-cxf-2.14.1-blueprint.xsd
+
+|2.14.0
+|http://camel.apache.org/schema/cxf/camel-cxf-2.14.0-blueprint.xsd
+
+|2.13.4
+|http://camel.apache.org/schema/cxf/camel-cxf-2.13.4-blueprint.xsd
+
+|2.13.3
+|http://camel.apache.org/schema/cxf/camel-cxf-2.13.3-blueprint.xsd
+
+|2.13.2
+|http://camel.apache.org/schema/cxf/camel-cxf-2.13.2-blueprint.xsd
+
+|2.13.1
+|http://camel.apache.org/schema/cxf/camel-cxf-2.13.1-blueprint.xsd
+
+|2.13.0
+|http://camel.apache.org/schema/cxf/camel-cxf-2.13.0-blueprint.xsd
+
+|2.12.5
+|http://camel.apache.org/schema/cxf/camel-cxf-2.12.5-blueprint.xsd
+
+|2.12.4
+|http://camel.apache.org/schema/cxf/camel-cxf-2.12.4-blueprint.xsd
+
+|2.12.3
+|http://camel.apache.org/schema/cxf/camel-cxf-2.12.3-blueprint.xsd
+
+|2.12.2
+|http://camel.apache.org/schema/cxf/camel-cxf-2.12.2-blueprint.xsd
+
+|2.12.1
+|http://camel.apache.org/schema/cxf/camel-cxf-2.12.1-blueprint.xsd
+
+|2.12.0
+|http://camel.apache.org/schema/cxf/camel-cxf-2.12.0-blueprint.xsd
+
+|2.11.4
+|http://camel.apache.org/schema/cxf/camel-cxf-2.11.4-blueprint.xsd
+
+|2.11.3
+|http://camel.apache.org/schema/cxf/camel-cxf-2.11.3-blueprint.xsd
+
+|2.11.2
+|http://camel.apache.org/schema/cxf/camel-cxf-2.11.2-blueprint.xsd
+
+|2.11.1
+|http://camel.apache.org/schema/cxf/camel-cxf-2.11.1-blueprint.xsd
+
+|2.11.0
+|http://camel.apache.org/schema/cxf/camel-cxf-2.11.0-blueprint.xsd
+
+|2.10.7
+|http://camel.apache.org/schema/cxf/camel-cxf-2.10.7-blueprint.xsd
+
+|2.10.6
+|http://camel.apache.org/schema/cxf/camel-cxf-2.10.6-blueprint.xsd
+
+|2.10.5
+|http://camel.apache.org/schema/cxf/camel-cxf-2.10.5-blueprint.xsd
+
+|2.10.4
+|http://camel.apache.org/schema/cxf/camel-cxf-2.10.4-blueprint.xsd
+
+|2.10.3
+|http://camel.apache.org/schema/cxf/camel-cxf-2.10.3-blueprint.xsd
+
+|2.10.2
+|http://camel.apache.org/schema/cxf/camel-cxf-2.10.2-blueprint.xsd
+
+|2.10.1
+|http://camel.apache.org/schema/cxf/camel-cxf-2.10.1-blueprint.xsd
+
+|2.10.0
+|http://camel.apache.org/schema/cxf/camel-cxf-2.10.0-blueprint.xsd
+
+|2.9.8 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.8-blueprint.xsd
+
+|2.9.7 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.7-blueprint.xsd
+
+|2.9.6 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.6-blueprint.xsd
+
+|2.9.5 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.5-blueprint.xsd
+
+|2.9.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.4-blueprint.xsd
+
+|2.9.3 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.3-blueprint.xsd
+
+|2.9.2 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.2-blueprint.xsd
+
+|2.9.1 |http://camel.apache.org/schema/cxf/camel-cxf-2.9.1-blueprint.xsd
+
+|2.8.6 |http://camel.apache.org/schema/cxf/camel-cxf-2.8.6-blueprint.xsd
+
+|2.8.5 |http://camel.apache.org/schema/cxf/camel-cxf-2.8.5-blueprint.xsd
+
+|2.8.4 |http://camel.apache.org/schema/cxf/camel-cxf-2.8.4-blueprint.xsd
+|=======================================================================
+
+[[XMLReference-ReleasedSchemas-SpringIntegration]]
+==== Released Schemas - Spring Integration
+
+[width="100%",cols="50%,50%",options="header",]
+|=======================================================================
+|Version |XML Schema
+|2.20.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.20.2.xsd
+
+|2.20.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.20.1.xsd
+
+|2.20.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.20.0.xsd
+
+|2.19.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.19.4.xsd
+
+|2.19.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.19.3.xsd
+
+|2.19.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.19.2.xsd
+
+|2.19.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.19.1.xsd
+
+|2.19.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.19.0.xsd
+
+|2.18.5
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.18.5.xsd
+
+|2.18.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.18.4.xsd
+
+|2.18.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.18.3.xsd
+
+|2.18.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.18.2.xsd
+
+|2.18.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.18.1.xsd
+
+|2.18.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.18.0.xsd
+
+|2.17.7
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.17.7.xsd
+
+|2.17.6
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.17.6.xsd
+
+|2.17.5
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.17.5.xsd
+
+|2.17.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.17.4.xsd
+
+|2.17.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.17.3.xsd
+
+|2.17.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.17.2.xsd
+
+|2.17.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.17.1.xsd
+
+|2.17.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.17.0.xsd
+
+|2.16.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.16.4.xsd
+
+|2.16.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.16.3.xsd
+
+|2.16.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.16.2.xsd
+
+|2.16.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.16.1.xsd
+
+|2.16.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.16.0.xsd
+
+|2.15.6
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.15.6.xsd
+
+|2.15.5
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.15.5.xsd
+
+|2.15.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.15.4.xsd
+
+|2.15.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.15.3.xsd
+
+|2.15.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.15.2.xsd
+
+|2.15.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.15.1.xsd
+
+|2.15.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.15.0.xsd
+
+|2.14.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.14.4.xsd
+
+|2.14.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.14.3.xsd
+
+|2.14.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.14.2.xsd
+
+|2.14.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.14.1.xsd
+
+|2.14.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.14.0.xsd
+
+|2.13.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.13.4.xsd
+
+|2.13.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.13.3.xsd
+
+|2.13.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.13.2.xsd
+
+|2.13.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.13.1.xsd
+
+|2.13.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.13.0.xsd
+
+|2.12.5
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.12.5.xsd
+
+|2.12.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.12.4.xsd
+
+|2.12.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.12.3.xsd
+
+|2.12.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.12.2.xsd
+
+|2.12.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.12.1.xsd
+
+|2.12.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.12.0.xsd
+
+|2.11.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.11.4.xsd
+
+|2.11.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.11.3.xsd
+
+|2.11.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.11.2.xsd
+
+|2.11.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.11.1.xsd
+
+|2.11.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.11.0.xsd
+
+|2.10.6
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.10.6.xsd
+
+|2.10.6
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.10.6.xsd
+
+|2.10.5
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.10.5.xsd
+
+|2.10.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.10.4.xsd
+
+|2.10.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.10.3.xsd
+
+|2.10.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.10.2.xsd
+
+|2.10.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.10.1.xsd
+
+|2.10.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.10.0.xsd
+
+|2.9.8
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.9.8.xsd
+
+|2.9.7
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.9.7.xsd
+
+|2.9.6
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.9.6.xsd
+
+|2.9.5
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.9.5.xsd
+
+|2.9.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.9.4.xsd
+
+|2.9.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.9.3.xsd
+
+|2.9.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.9.2.xsd
+
+|2.9.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.9.1.xsd
+
+|2.9.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.9.0.xsd
+
+|2.8.6
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.8.6.xsd
+
+|2.8.5
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.8.5.xsd
+
+|2.8.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.8.4.xsd
+
+|2.8.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.8.3.xsd
+
+|2.8.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.8.2.xsd
+
+|2.8.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.8.1.xsd
+
+|2.8.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.8.0.xsd
+
+|2.7.5
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.7.5.xsd
+
+|2.7.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.7.4.xsd
+
+|2.7.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.7.3.xsd
+
+|2.7.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.7.2.xsd
+
+|2.7.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.7.1.xsd
+
+|2.7.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.7.0.xsd
+
+|2.6.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.6.0.xsd
+
+|2.5.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.5.0.xsd
+
+|2.4.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.4.0.xsd
+
+|2.3.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.3.0.xsd
+
+|2.2.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.2.0.xsd
+
+|2.1.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.1.0.xsd
+
+|2.0.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-2.0.0.xsd
+
+|1.6.4
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-1.6.4.xsd
+
+|1.6.3
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-1.6.3.xsd
+
+|1.6.2
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-1.6.2.xsd
+
+|1.6.1
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-1.6.1.xsd
+
+|1.6.0
+|http://camel.apache.org/schema/spring/integration/camel-spring-integration-1.6.0.xsd
+
+|1.5.0
+|http://activemq.apache.org/camel/schema/spring/integration/camel-spring-integration-1.5.0.xsd
+
+|1.4.0
+|http://activemq.apache.org/camel/schema/spring/integration/camel-spring-integration-1.4.0.xsd
+|=======================================================================
+
+[[XMLReference-ReleasedSchemas-SpringSecurity]]
+==== Released Schemas - Spring Security
+
+[width="100%",cols="50%,50%",options="header",]
+|=======================================================================
+|Version |XML Schema
+|2.20.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.20.2.xsd
+
+|2.20.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.20.1.xsd
+
+|2.20.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.20.0.xsd
+
+|2.19.4
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.19.4.xsd
+
+|2.19.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.19.3.xsd
+
+|2.19.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.19.2.xsd
+
+|2.19.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.19.1.xsd
+
+|2.19.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.19.0.xsd
+
+|2.18.5
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.18.5.xsd
+
+|2.18.4
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.18.4.xsd
+
+|2.18.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.18.3.xsd
+
+|2.18.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.18.2.xsd
+
+|2.18.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.18.1.xsd
+
+|2.18.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.18.0.xsd
+
+|2.17.7
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.17.7.xsd
+
+|2.17.6
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.17.6.xsd
+
+|2.17.5
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.17.5.xsd
+
+|2.17.4
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.17.4.xsd
+
+|2.17.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.17.3.xsd
+
+|2.17.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.17.2.xsd
+
+|2.17.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.17.1.xsd
+
+|2.17.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.17.0.xsd
+
+|2.16.4
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.16.4.xsd
+
+|2.16.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.16.3.xsd
+
+|2.16.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.16.2.xsd
+
+|2.16.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.16.1.xsd
+
+|2.16.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.16.0.xsd
+
+|2.15.6
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.15.6.xsd
+
+|2.15.5
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.15.5.xsd
+
+|2.15.4
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.15.4.xsd
+
+|2.15.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.15.3.xsd
+
+|2.15.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.15.2.xsd
+
+|2.15.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.15.1.xsd
+
+|2.15.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.15.0.xsd
+
+|2.14.4
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.14.4.xsd
+
+|2.14.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.14.3.xsd
+
+|2.14.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.14.2.xsd
+
+|2.14.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.14.1.xsd
+
+|2.14.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.14.0.xsd
+
+|2.13.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.13.4.xsd
+
+|2.13.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.13.3.xsd
+
+|2.13.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.13.2.xsd
+
+|2.13.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.13.1.xsd
+
+|2.13.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.13.0.xsd
+
+|2.12.5
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.12.5.xsd
+
+|2.12.4
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.12.4.xsd
+
+|2.12.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.12.3.xsd
+
+|2.12.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.12.2.xsd
+
+|2.12.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.12.1.xsd
+
+|2.12.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.12.0.xsd
+
+|2.11.4
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.11.4.xsd
+
+|2.11.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.11.3.xsd
+
+|2.11.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.11.2.xsd
+
+|2.11.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.11.1.xsd
+
+|2.11.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.11.0.xsd
+
+|2.10.7
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.10.7.xsd
+
+|2.10.6
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.10.6.xsd
+
+|2.10.5
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.10.5.xsd
+
+|2.10.4
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.10.4.xsd
+
+|2.10.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.10.3.xsd
+
+|2.10.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.10.2.xsd
+
+|2.10.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.10.1.xsd
+
+|2.10.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.10.0.xsd
+
+|2.9.8
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.9.8.xsd
+
+|2.9.7
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.9.7.xsd
+
+|2.9.6
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.9.6.xsd
+
+|2.9.5
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.9.5.xsd
+
+|2.9.4
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.9.4.xsd
+
+|2.9.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.9.3.xsd
+
+|2.9.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.9.2.xsd
+
+|2.9.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.9.1.xsd
+
+|2.9.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.9.0.xsd
+
+|2.8.6
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.8.6.xsd
+
+|2.8.5
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.8.5.xsd
+
+|2.8.4
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.8.4.xsd
+
+|2.8.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.8.3.xsd
+
+|2.8.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.8.2.xsd
+
+|2.8.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.8.1.xsd
+
+|2.8.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.8.0.xsd
+
+|2.7.5
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.7.5.xsd
+
+|2.7.4
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.7.4.xsd
+
+|2.7.3
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.7.3.xsd
+
+|2.7.2
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.7.2.xsd
+
+|2.7.1
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.7.1.xsd
+
+|2.7.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.7.0.xsd
+
+|2.6.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.6.0.xsd
+
+|2.5.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.5.0.xsd
+
+|2.4.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.4.0.xsd
+
+|2.3.0
+|http://camel.apache.org/schema/spring-security/camel-spring-security-2.3.0.xsd
+|=======================================================================
+
+[[XMLReference-UsingtheXSDsinconfigurationfiles]]
+==== Using the XSDs in configuration files
+
+When you are using link:spring.adoc[Spring]'s 2.5 XML handling to parse
+the XML then you need to refer to the XSD locations in your XML
+document.
+
+You can refer to a specific version of the XSD in your XML as follows:
+
+[source,xml]
+----
+<beans
+ xmlns="http://www.springframework.org/schema/beans"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="
+ http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
+ http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring-2.13.1.xsd">
+----
+
+Or if you prefer you can use a generic XSD without the version number:
+
+[source,xml]
+----
+<beans
+ xmlns="http://www.springframework.org/schema/beans"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="
+ http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
+ http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd">
+----
+
+Your IDE won't be able to fetch this XSD, you'll have to manually
+associate a specific release; however it does mean that you won't have
+to upgrade your XML config file with each Camel release; as it will
+resolve this XSD using the bundled XSD inside the `camel-spring.jar`.