This is an automated email from the ASF dual-hosted git repository.
djencks pushed a commit to branch camel-3.11.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-3.11.x by this push:
new 1cce173 latest to next
1cce173 is described below
commit 1cce173b91a2efa454c4a3ea02748e9141255f07
Author: David Jencks <[email protected]>
AuthorDate: Sun Oct 24 12:30:52 2021 -0700
latest to next
---
.../apache/camel/catalog/docs/aggregate-eip.adoc | 14 +++---
.../org/apache/camel/catalog/docs/bean-eip.adoc | 10 ++--
.../apache/camel/catalog/docs/channel-adapter.adoc | 2 +-
.../org/apache/camel/catalog/docs/choice-eip.adoc | 4 +-
.../catalog/docs/content-based-router-eip.adoc | 14 +++---
.../camel/catalog/docs/content-enricher.adoc | 52 ++++++++++----------
.../camel/catalog/docs/content-filter-eip.adoc | 18 +++----
.../camel/catalog/docs/correlation-identifier.adoc | 4 +-
.../camel/catalog/docs/dead-letter-channel.adoc | 56 +++++++++++-----------
.../docs/enterprise-integration-patterns.adoc | 2 +-
.../apache/camel/catalog/docs/event-message.adoc | 6 +--
.../catalog/docs/eventDrivenConsumer-eip.adoc | 12 ++---
.../org/apache/camel/catalog/docs/filter-eip.adoc | 10 ++--
.../camel/catalog/docs/idempotentConsumer-eip.adoc | 2 +-
.../org/apache/camel/catalog/docs/log-eip.adoc | 4 +-
.../org/apache/camel/catalog/docs/marshal-eip.adoc | 2 +-
.../camel/catalog/docs/message-endpoint.adoc | 4 +-
.../apache/camel/catalog/docs/message-router.adoc | 6 +--
.../camel/catalog/docs/message-translator.adoc | 22 ++++-----
.../org/apache/camel/catalog/docs/message.adoc | 4 +-
.../camel/catalog/docs/messaging-gateway.adoc | 2 +-
.../camel/catalog/docs/messaging-mapper.adoc | 2 +-
.../apache/camel/catalog/docs/multicast-eip.adoc | 2 +-
.../apache/camel/catalog/docs/otherwise-eip.adoc | 2 +-
.../apache/camel/catalog/docs/pipeline-eip.adoc | 4 +-
.../camel/catalog/docs/polling-consumer.adoc | 28 +++++------
.../org/apache/camel/catalog/docs/process-eip.adoc | 8 ++--
.../camel/catalog/docs/properties-component.adoc | 2 +-
.../catalog/docs/publish-subscribe-channel.adoc | 4 +-
.../camel/catalog/docs/service-activator.adoc | 2 +-
.../org/apache/camel/catalog/docs/toD-eip.adoc | 4 +-
.../camel/catalog/docs/transactional-client.adoc | 6 +--
.../apache/camel/catalog/docs/unmarshal-eip.adoc | 4 +-
.../org/apache/camel/catalog/docs/when-eip.adoc | 2 +-
.../org/apache/camel/catalog/docs/wireTap-eip.adoc | 42 ++++++++--------
.../src/main/docs/properties-component.adoc | 2 +-
.../modules/ROOT/pages/properties-component.adoc | 2 +-
docs/components/modules/others/pages/yaml-dsl.adoc | 2 +-
.../ROOT/pages/error-handling-in-camel.adoc | 2 +-
docs/user-manual/modules/ROOT/references.adoc | 6 +--
.../camel-yaml-dsl/src/main/docs/yaml-dsl.adoc | 2 +-
41 files changed, 189 insertions(+), 189 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aggregate-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aggregate-eip.adoc
index 5f70fa9..6db99dc 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aggregate-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aggregate-eip.adoc
@@ -12,7 +12,7 @@ you to combine a number of messages together into a single
message.
image::eip/Aggregator.gif[image]
-A correlation xref:latest@manual:ROOT:expression.adoc[Expression] is used to
determine the
+A correlation xref:manual:ROOT:expression.adoc[Expression] is used to
determine the
messages which should be aggregated together. If you want to aggregate
all messages into a single message, just use a constant expression. An
AggregationStrategy is used to combine all the message exchanges for a
@@ -125,7 +125,7 @@ class ArrayListAggregationStrategy implements
AggregationStrategy {
== About completion
-When aggregation xref:latest@manual:ROOT:exchange.adoc[Exchange]s at some
point you need to
+When aggregation xref:manual:ROOT:exchange.adoc[Exchange]s at some point you
need to
indicate that the aggregated exchanges is complete, so they can be send
out of the aggregator. Camel allows you to indicate completion in
various ways as follows:
@@ -137,7 +137,7 @@ key within the period.
exchanges are completed.
* completionSize - Is a number indicating that after X aggregated
exchanges it's complete.
-* completionPredicate - Runs a
xref:latest@manual:ROOT:predicate.adoc[Predicate] when a new
+* completionPredicate - Runs a xref:manual:ROOT:predicate.adoc[Predicate] when
a new
exchange is aggregated to determine if we are complete or not.
The configured aggregationStrategy can implement the
Predicate interface and will be used as the completionPredicate if no
@@ -146,7 +146,7 @@ override the `preComplete` method and will be used as
the completionPredicate in pre-complete check mode. See further below
for more details.
* completionFromBatchConsumer - Special option for
-xref:latest@manual:ROOT:batch-consumer.adoc[Batch Consumer] which allows you
to complete
+xref:manual:ROOT:batch-consumer.adoc[Batch Consumer] which allows you to
complete
when all the messages from the batch has been aggregated.
* forceCompletionOnStop - Indicates to complete all current
aggregated exchanges when the context is stopped
@@ -166,9 +166,9 @@ aggregator. If not provided Camel will thrown an Exception
on startup.
== Pre-completion mode
There can be use-cases where you want the incoming
-xref:latest@manual:ROOT:exchange.adoc[Exchange] to determine if the
correlation group
+xref:manual:ROOT:exchange.adoc[Exchange] to determine if the correlation group
should pre-complete, and then the incoming
-xref:latest@manual:ROOT:exchange.adoc[Exchange] is starting a new group from
scratch. o
+xref:manual:ROOT:exchange.adoc[Exchange] is starting a new group from scratch.
o
determine this the `AggregationStrategy` must override the `canPreComplete`
method
which has to return `true`.
@@ -568,7 +568,7 @@ without using POJOs then you may have `null` as
`oldExchange` or
Aggregate EIP will invoke the
`AggregationStrategy` with `oldExchange` as null, for the first
Exchange incoming to the aggregator. And then for
-subsequent xref:latest@manual:ROOT:exchange.adoc[Exchange]s then `oldExchange`
and
+subsequent xref:manual:ROOT:exchange.adoc[Exchange]s then `oldExchange` and
`newExchange` parameters are both not null.
Example with Content Enricher EIP and no data
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/bean-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/bean-eip.adoc
index e37f30c..9f770077 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/bean-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/bean-eip.adoc
@@ -15,7 +15,7 @@ bean:beanID[?options]
----
Where *beanID* can be any string which is used to look up the bean in
-the xref:latest@manual:ROOT:registry.adoc[Registry]
+the xref:manual:ROOT:registry.adoc[Registry]
== EIP options
@@ -50,10 +50,10 @@ Camel also supports invoking
xref:components::bean-component.adoc[Bean] as an En
route below:
What happens is that when the exchange is routed to the `myBean` Camel
-will use the xref:latest@manual:ROOT:bean-binding.adoc[Bean Binding] to invoke
the bean. +
+will use the xref:manual:ROOT:bean-binding.adoc[Bean Binding] to invoke the
bean. +
The source for the bean is just a plain POJO:
-Camel will use xref:latest@manual:ROOT:bean-binding.adoc[Bean Binding] to
invoke the
+Camel will use xref:manual:ROOT:bean-binding.adoc[Bean Binding] to invoke the
`sayHello` method, by converting the Exchange's In body to the `String`
type and storing the output of the method on the Exchange Out body.
@@ -94,6 +94,6 @@ from("direct:start").bean(ExampleBean.class);
How bean methods to be invoked are chosen (if they are not specified
explicitly through the *method* parameter) and how parameter values are
constructed from the xref:message.adoc[Message] are all defined by the
-xref:latest@manual:ROOT:bean-binding.adoc[Bean Binding] mechanism which is
used throughout
-all of the various xref:latest@manual:ROOT:bean-integration.adoc[Bean
Integration]
+xref:manual:ROOT:bean-binding.adoc[Bean Binding] mechanism which is used
throughout
+all of the various xref:manual:ROOT:bean-integration.adoc[Bean Integration]
mechanisms in Camel.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/channel-adapter.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/channel-adapter.adoc
index 03c0d05..95769b0 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/channel-adapter.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/channel-adapter.adoc
@@ -41,7 +41,7 @@ public class CheeseBean {
}
----
-You can also use xref:latest@manual:ROOT:pojo-consuming.adoc[POJO consuming]
with `@Consume` annotation.
+You can also use xref:manual:ROOT:pojo-consuming.adoc[POJO consuming] with
`@Consume` annotation.
[source,java]
----
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/choice-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/choice-eip.adoc
index a431005..5287056 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/choice-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/choice-eip.adoc
@@ -30,7 +30,7 @@ The Choice EIP supports 2 options which are listed below:
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 xref:latest@manual:ROOT:predicate.adoc[Predicate]
expressions
+the evaluation of various xref:manual:ROOT:predicate.adoc[Predicate]
expressions
[source,java]
----
@@ -107,7 +107,7 @@ Another example is explained in the TIP below.
[TIP]
====
-See
xref:latest@manual:faq:why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc[Why
+See
xref:manual: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] if you have
problems with the Java DSL, accepting using `when` or `otherwise`.
====
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/content-based-router-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/content-based-router-eip.adoc
index 820bf2c..bf4549a 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/content-based-router-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/content-based-router-eip.adoc
@@ -11,7 +11,7 @@ image::eip/ContentBasedRouter.gif[image]
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 xref:latest@manual:ROOT:predicate.adoc[Predicate]
expressions
+the evaluation of various xref:manual:ROOT:predicate.adoc[Predicate]
expressions
[source,java]
----
@@ -34,12 +34,12 @@ RouteBuilder builder = new RouteBuilder() {
[TIP]
====
See
-xref:latest@manual:faq:why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc[Why
+xref:manual: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] if you have
problems with the Java DSL, accepting using `when` or `otherwise`.
====
-== Using the xref:latest@manual:ROOT:spring-xml-extensions.adoc[Spring XML
Extensions]
+== Using the xref:manual:ROOT:spring-xml-extensions.adoc[Spring XML Extensions]
[source,java]
----
@@ -70,8 +70,8 @@
https://github.com/apache/camel/blob/main/core/camel-core/src/test/java/org/apac
== Using This Pattern
If you would like to use this EIP Pattern then please read the
-xref:latest@manual:ROOT:getting-started.adoc[Getting Started]. You may also
find the
-xref:latest@manual:ROOT:architecture.adoc[Architecture] useful particularly
the description
-of xref:latest@manual:ROOT:endpoint.adoc[Endpoint] and
xref:latest@manual:ROOT:uris.adoc[URIs]. Then you could
-try out some of the xref:latest@manual:ROOT:examples.adoc[Examples] first
before trying
+xref:manual:ROOT:getting-started.adoc[Getting Started]. You may also find the
+xref:manual:ROOT:architecture.adoc[Architecture] useful particularly the
description
+of xref:manual:ROOT:endpoint.adoc[Endpoint] and
xref:manual:ROOT:uris.adoc[URIs]. Then you could
+try out some of the xref:manual:ROOT:examples.adoc[Examples] first before
trying
this pattern out.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/content-enricher.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/content-enricher.adoc
index a257f19..2b31b2b 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/content-enricher.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/content-enricher.adoc
@@ -5,7 +5,7 @@ Camel supports the
http://www.enterpriseintegrationpatterns.com/DataEnricher.html[Content
Enricher] from the xref:enterprise-integration-patterns.adoc[EIP
patterns] using a xref:message-translator.adoc[Message Translator], an
-arbitrary xref:latest@manual:ROOT:processor.adoc[Processor] in the routing
logic, or using
+arbitrary xref:manual:ROOT:processor.adoc[Processor] in the routing logic, or
using
the xref:content-enricher.adoc[enrich] DSL element to enrich the
message.
@@ -38,7 +38,7 @@ from("activemq:My.Queue")
.to("velocity:com/acme/MyResponse.vm");
----
-Here is a simple example using the xref:latest@manual:ROOT:dsl.adoc[DSL]
directly to
+Here is a simple example using the xref:manual:ROOT:dsl.adoc[DSL] directly to
transform the message
[source,java]
@@ -48,7 +48,7 @@ from("direct:start")
.to("mock:result");
----
-In this example we add our own
xref:latest@manual:ROOT:processor.adoc[Processor] using
+In this example we add our own xref:manual:ROOT:processor.adoc[Processor] using
explicit Java
[source,java]
@@ -63,7 +63,7 @@ from("direct:start")
.to("mock:result");
----
-we can use xref:latest@manual:ROOT:bean-integration.adoc[Bean Integration] to
use any Java
+we can use xref:manual:ROOT:bean-integration.adoc[Bean Integration] to use any
Java
method on any bean to act as the transformer
[source,java]
@@ -109,9 +109,9 @@ file or download a xref:components::ftp-component.adoc[FTP]
file.
Camel 2.15 or older - Data from current Exchange not used
`pollEnrich` or `enrich` does *not* access any data from the current
-xref:latest@manual:ROOT:exchange.adoc[Exchange] which means when polling it
cannot use any
+xref:manual:ROOT:exchange.adoc[Exchange] which means when polling it cannot
use any
of the existing headers you may have set on the
-xref:latest@manual:ROOT:exchange.adoc[Exchange]. For example you cannot set a
filename in
+xref:manual:ROOT:exchange.adoc[Exchange]. For example you cannot set a
filename in
the `Exchange.FILE_NAME` header and use `pollEnrich` to consume only
that file. For that you *must* set the filename in the endpoint URI.
@@ -126,9 +126,9 @@ messages from a seda, ... components using an aggregation
strategy. Only
one response message will be aggregated with the original message.
From *Camel 2.16* onwards both enrich and pollEnrich supports dynamic
-endpoints that uses an xref:latest@manual:ROOT:expression.adoc[Expression] to
compute the
+endpoints that uses an xref:manual:ROOT:expression.adoc[Expression] to compute
the
uri, which allows to use data from the current
-xref:latest@manual:ROOT:exchange.adoc[Exchange]. In other words all what is
told above no
+xref:manual:ROOT:exchange.adoc[Exchange]. In other words all what is told
above no
longer apply and it just works.
[[ContentEnricher-EnrichOptions]]
@@ -139,25 +139,25 @@ longer apply and it just works.
|Name |Default Value |Description
|`uri` | |The endpoint uri for the external service to enrich from. You
must use either `uri` or `ref`. *Important:* From Camel 2.16 onwards,
-this option is removed, and you use an
xref:latest@manual:ROOT:expression.adoc[Expression]
+this option is removed, and you use an
xref:manual:ROOT:expression.adoc[Expression]
to configure the uri, such as
xref:components:languages:simple-language.adoc[Simple] or
xref:components:languages:constant-language.adoc[Constant] or any other
dynamic language that can
compute the uri dynamically using values from the current
-xref:latest@manual:ROOT:exchange.adoc[Exchange].
+xref:manual:ROOT:exchange.adoc[Exchange].
|`ref` | |Refers to the endpoint for the external service to enrich
from. You must use either `uri` or `ref`. **Important:** From Camel
2.16 onwards, this option is removed, and you use an
-xref:latest@manual:ROOT:expression.adoc[Expression] to configure the uri, such
as
+xref:manual:ROOT:expression.adoc[Expression] to configure the uri, such as
xref:components:languages:simple-language.adoc[Simple] or
xref:components:languages:constant-language.adoc[Constant] or any other
dynamic language that can compute the uri dynamically using values from
-the current xref:latest@manual:ROOT:exchange.adoc[Exchange].
+the current xref:manual:ROOT:exchange.adoc[Exchange].
|expression | |*Camel 2.16:* Mandatory.
-The xref:latest@manual:ROOT:expression.adoc[Expression] to configure the uri,
such as
+The xref:manual:ROOT:expression.adoc[Expression] to configure the uri, such as
xref:components:languages:simple-language.adoc[Simple] or
xref:components:languages:constant-language.adoc[Constant] or any other
dynamic language that can compute the uri dynamically using values from
-the current xref:latest@manual:ROOT:exchange.adoc[Exchange].
+the current xref:manual:ROOT:exchange.adoc[Exchange].
|`strategyRef` | |Refers to an
https://github.com/apache/camel/blob/main/core/camel-api/src/main/java/org/apache/camel/AggregationStrategy.java[AggregationStrategy]
@@ -306,7 +306,7 @@ And for Spring DSL:
From Camel 2.16 onwards enrich and pollEnrich supports using dynamic
uris computed based on information from the
-current xref:latest@manual:ROOT:exchange.adoc[Exchange]. For example to enrich
from
+current xref:manual:ROOT:exchange.adoc[Exchange]. For example to enrich from
a xref:components::http-component.adoc[HTTP] endpoint where the header with
key orderId is
used as part of the content-path of the HTTP url:
@@ -349,25 +349,25 @@ polling
|Name |Default Value |Description
|`uri` | |The endpoint uri for the external service to enrich from. You
must use either `uri` or `ref`. **Important:** From Camel 2.16 onwards,
-this option is removed, and you use an
xref:latest@manual:ROOT:expression.adoc[Expression]
+this option is removed, and you use an
xref:manual:ROOT:expression.adoc[Expression]
to configure the uri, such as
xref:components:languages:simple-language.adoc[Simple] or
xref:components:languages:constant-language.adoc[Constant] or any other
dynamic language that can
compute the uri dynamically using values from the current
- xref:latest@manual:ROOT:exchange.adoc[Exchange].
+ xref:manual:ROOT:exchange.adoc[Exchange].
|`ref` | |Refers to the endpoint for the external service to enrich
from. You must use either `uri` or `ref`. **Important:** From Camel 2.16
onwards, this option is removed, and you use an
-xref:latest@manual:ROOT:expression.adoc[Expression] to configure the uri, such
as
+xref:manual:ROOT:expression.adoc[Expression] to configure the uri, such as
xref:components:languages:simple-language.adoc[Simple] or
xref:components:languages:constant-language.adoc[Constant] or any other
dynamic language that can compute the uri dynamically using values from
-the current xref:latest@manual:ROOT:exchange.adoc[Exchange].
+the current xref:manual:ROOT:exchange.adoc[Exchange].
|`expression` | |**Camel 2.16:** Mandatory.
-The xref:latest@manual:ROOT:expression.adoc[Expression] to configure the uri,
such as
+The xref:manual:ROOT:expression.adoc[Expression] to configure the uri, such as
xref:components:languages:simple-language.adoc[Simple] or
xref:components:languages:constant-language.adoc[Constant] or any other
dynamic language that can compute the uri dynamically using values from
-the current xref:latest@manual:ROOT:exchange.adoc[Exchange].
+the current xref:manual:ROOT:exchange.adoc[Exchange].
|`strategyRef` | |Refers to an
https://github.com/apache/camel/blob/main/core/camel-api/src/main/java/org/apache/camel/AggregationStrategy.java[AggregationStrategy]
@@ -431,16 +431,16 @@ The timeout values is in millis.
Camel 2.15 or older - Data from current Exchange not used
`pollEnrich` does *not* access any data from the current
-xref:latest@manual:ROOT:exchange.adoc[Exchange] which means when polling it
cannot use any
+xref:manual:ROOT:exchange.adoc[Exchange] which means when polling it cannot
use any
of the existing headers you may have set on the
-xref:latest@manual:ROOT:exchange.adoc[Exchange]. For example you cannot set a
filename in
+xref:manual:ROOT:exchange.adoc[Exchange]. For example you cannot set a
filename in
the `Exchange.FILE_NAME` header and use `pollEnrich` to consume only
that file. For that you *must* set the filename in the endpoint URI.
From **Camel 2.16** onwards both enrich and pollEnrich supports dynamic
-endpoints that uses an xref:latest@manual:ROOT:expression.adoc[Expression] to
compute the
+endpoints that uses an xref:manual:ROOT:expression.adoc[Expression] to compute
the
uri, which allows to use data from the current
-xref:latest@manual:ROOT:exchange.adoc[Exchange]. In other words all what is
told above no
+xref:manual:ROOT:exchange.adoc[Exchange]. In other words all what is told
above no
longer apply and it just works.
[[ContentEnricher-Example]]
@@ -493,7 +493,7 @@ For example to wait up to 5 seconds you can do:
From Camel 2.16 onwards enrich and pollEnrich supports using dynamic
uris computed based on information from the
-current xref:latest@manual:ROOT:exchange.adoc[Exchange]. For example to
pollEnrich from an
+current xref:manual:ROOT:exchange.adoc[Exchange]. For example to pollEnrich
from an
endpoint that uses a header to indicate a
xref:components::seda-component.adoc[SEDA] queue
name:
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/content-filter-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/content-filter-eip.adoc
index f437ef0..726c9a5 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/content-filter-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/content-filter-eip.adoc
@@ -9,18 +9,18 @@ using one of the following mechanisms in the routing logic to
transform
content from the inbound message.
* xref:message-translator.adoc[Message Translator]
-* invoking a xref:latest@manual:ROOT:bean-integration.adoc[Java bean]
-* xref:latest@manual:ROOT:processor.adoc[Processor] object
+* invoking a xref:manual:ROOT:bean-integration.adoc[Java bean]
+* xref:manual:ROOT:processor.adoc[Processor] object
image::eip/ContentFilter.gif[image]
A common way to filter messages is to use an
-xref:latest@manual:ROOT:expression.adoc[Expression] in the
xref:latest@manual:ROOT:dsl.adoc[DSL] like
+xref:manual:ROOT:expression.adoc[Expression] in the
xref:manual:ROOT:dsl.adoc[DSL] like
xref:components:languages:xquery-language.adoc[XQuery].
-Here is a simple example using the xref:latest@manual:ROOT:dsl.adoc[DSL]
directly
+Here is a simple example using the xref:manual:ROOT:dsl.adoc[DSL] directly
-In this example we add our own
xref:latest@manual:ROOT:processor.adoc[Processor]
+In this example we add our own xref:manual:ROOT:processor.adoc[Processor]
For further examples of this pattern in use you could look at one of the
JUnit tests
@@ -55,8 +55,8 @@ interested in:
== Using This Pattern
If you would like to use this EIP Pattern then please read the
-xref:latest@manual:ROOT:getting-started.adoc[Getting Started], you may also
find the
-xref:latest@manual:ROOT:architecture.adoc[Architecture] useful particularly
the description
-of xref:latest@manual:ROOT:endpoint.adoc[Endpoint] and
xref:latest@manual:ROOT:uris.adoc[URIs]. Then you could
-try out some of the xref:latest@manual:ROOT:examples.adoc[Examples] first
before trying
+xref:manual:ROOT:getting-started.adoc[Getting Started], you may also find the
+xref:manual:ROOT:architecture.adoc[Architecture] useful particularly the
description
+of xref:manual:ROOT:endpoint.adoc[Endpoint] and
xref:manual:ROOT:uris.adoc[URIs]. Then you could
+try out some of the xref:manual:ROOT:examples.adoc[Examples] first before
trying
this pattern out.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/correlation-identifier.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/correlation-identifier.adoc
index f214f77..dd83840 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/correlation-identifier.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/correlation-identifier.adoc
@@ -21,9 +21,9 @@ with the xref:components::mock-component.adoc[Mock testing
framework]
Some xref:enterprise-integration-patterns.adoc[EIP] patterns will spin off a
sub message, and in
those cases, Camel will add a correlation id on the
-xref:latest@manual:ROOT:exchange.adoc[Exchange] as a property with they key
+xref:manual:ROOT:exchange.adoc[Exchange] as a property with they key
`Exchange.CORRELATION_ID`, which links back to the source
-xref:latest@manual:ROOT:exchange.adoc[Exchange]. For example the
+xref:manual:ROOT:exchange.adoc[Exchange]. For example the
xref:split-eip.adoc[Splitter], xref:multicast-eip.adoc[Multicast],
xref:recipientList-eip.adoc[Recipient List], and xref:wireTap-eip.adoc[Wire
Tap] EIP does this.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dead-letter-channel.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dead-letter-channel.adoc
index 4c615cc..4ddb5b4 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dead-letter-channel.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dead-letter-channel.adoc
@@ -6,7 +6,7 @@
http://www.enterpriseintegrationpatterns.com/DeadLetterChannel.html[Dead
Letter Channel] from the xref:enterprise-integration-patterns.adoc[EIP
patterns] using the
https://www.javadoc.io/doc/org.apache.camel/camel-base/current/org/apache/camel/processor/errorhandler/DeadLetterChannel.html[DeadLetterChannel]
-processor which is an xref:latest@manual:ROOT:error-handler.adoc[Error
Handler].
+processor which is an xref:manual:ROOT:error-handler.adoc[Error Handler].
image::eip/DeadLetterChannelSolution.gif[image]
@@ -68,11 +68,11 @@ forwarded to the dead letter queue.
== About moving Exchange to dead letter queue and using handled
When all attempts of redelivery have failed the
-xref:latest@manual:ROOT:exchange.adoc[Exchange] is moved to the dead letter
queue (the dead
+xref:manual:ROOT:exchange.adoc[Exchange] is moved to the dead letter queue
(the dead
letter endpoint). The exchange is then complete and from the client
point of view it was processed. As such the
xref:dead-letter-channel.adoc[Dead Letter Channel] have handled the
-xref:latest@manual:ROOT:exchange.adoc[Exchange].
+xref:manual:ROOT:exchange.adoc[Exchange].
For instance configuring the dead letter channel as:
@@ -103,8 +103,8 @@ And in XML:
The xref:dead-letter-channel.adoc[Dead Letter Channel] above will clear
the caused exception (`setException(null)`), by moving the caused
-exception to a property on the
xref:latest@manual:ROOT:exchange.adoc[Exchange], with the
-key `Exchange.EXCEPTION_CAUGHT`. Then the
xref:latest@manual:ROOT:exchange.adoc[Exchange]
+exception to a property on the xref:manual:ROOT:exchange.adoc[Exchange], with
the
+key `Exchange.EXCEPTION_CAUGHT`. Then the
xref:manual:ROOT:exchange.adoc[Exchange]
is moved to the `"jms:queue:dead"` destination and the client will not
notice the failure.
@@ -126,12 +126,12 @@ from("jms:queue:order:input")
-----
The route listen for JMS messages and validates, transforms and handle
-it. During this the xref:latest@manual:ROOT:exchange.adoc[Exchange] payload is
+it. During this the xref:manual:ROOT:exchange.adoc[Exchange] payload is
transformed/modified. So in case something goes wrong and we want to
move the message to another JMS destination, then we can configure our
xref:dead-letter-channel.adoc[Dead Letter Channel] with the
*useOriginalMessage* option. But when we move the
-xref:latest@manual:ROOT:exchange.adoc[Exchange] to this destination we do not
know in which
+xref:manual:ROOT:exchange.adoc[Exchange] to this destination we do not know in
which
state the message is in. Did the error happen in before the
transformOrder or after? So to be sure we want to move the original
input message we received from `jms:queue:order:input`. So we can do
@@ -169,13 +169,13 @@ the parent original message.
== OnRedelivery
When xref:dead-letter-channel.adoc[Dead Letter Channel] is doing
-redeliver its possible to configure a
xref:latest@manual:ROOT:processor.adoc[Processor]
+redeliver its possible to configure a
xref:manual:ROOT:processor.adoc[Processor]
that is executed just *before* every redelivery attempt. This can be
used for the situations where you need to alter the message before its
redelivered. See below for sample.
TIP: *onException and onRedeliver*
-We also support for per
xref:latest@manual:ROOT:exception-clause.adoc[*onException*] to set
+We also support for per xref:manual:ROOT:exception-clause.adoc[*onException*]
to set
a *onRedeliver*. That means you can do special on redelivery for
different exceptions, as opposed to onRedelivery set on
xref:dead-letter-channel.adoc[Dead Letter Channel] can be viewed as a
@@ -302,8 +302,8 @@ Is this header is absent, normal redelivery rules apply.
*Since Camel 2.1*
When Camel routes messages it will decorate the
-xref:latest@manual:ROOT:exchange.adoc[Exchange] with a property that contains
the *last*
-endpoint Camel send the xref:latest@manual:ROOT:exchange.adoc[Exchange] to:
+xref:manual:ROOT:exchange.adoc[Exchange] with a property that contains the
*last*
+endpoint Camel send the xref:manual:ROOT:exchange.adoc[Exchange] to:
[source,java]
----
@@ -316,8 +316,8 @@ This information is updated when Camel sends a message to
any endpoint.
So if it exists its the *last* endpoint which Camel send the Exchange
to.
-When for example processing the
xref:latest@manual:ROOT:exchange.adoc[Exchange] at a given
-xref:latest@manual:ROOT:endpoint.adoc[Endpoint] and the message is to be moved
into the
+When for example processing the xref:manual:ROOT:exchange.adoc[Exchange] at a
given
+xref:manual:ROOT:endpoint.adoc[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:
@@ -399,9 +399,9 @@ The onPrepare is also available using the default error
handler.
When Camel error handler handles an error such as
xref:dead-letter-channel.adoc[Dead Letter Channel] or using
-xref:latest@manual:ROOT:exception-clause.adoc[Exception Clause] with
handled=true, then
+xref:manual:ROOT:exception-clause.adoc[Exception Clause] with handled=true,
then
Camel will decorate +
- the xref:latest@manual:ROOT:exchange.adoc[Exchange] with the route id where
the error
+ the xref:manual:ROOT:exchange.adoc[Exchange] with the route id where the error
occurred.
[source,java]
@@ -423,16 +423,16 @@ letter queue and use that for error reporting.
Prior to Camel 2.10, Camel will perform redelivery while stopping a
route, or shutting down Camel. This has improved a bit in Camel 2.10
onwards, as Camel will not perform redelivery attempts when shutting
-down aggressively (eg during
xref:latest@manual:ROOT:graceful-shutdown.adoc[Graceful
+down aggressively (eg during xref:manual:ROOT:graceful-shutdown.adoc[Graceful
Shutdown] and timeout hit). From Camel 2.11 onwards there is a new
option `allowRedeliveryWhileStopping` which you can use to control if
redelivery is allowed or not; notice that any in progress redelivery
will still be executed. This option can only disallow any redelivery to
be executed *after* the stopping of a route/shutdown of Camel has been
triggered. If a redelivery is disallowed then a
-`RejectedExecutionException` is set on the
xref:latest@manual:ROOT:exchange.adoc[Exchange]
-and the processing of the xref:latest@manual:ROOT:exchange.adoc[Exchange]
stops. This means
-any consumer will see the xref:latest@manual:ROOT:exchange.adoc[Exchange] as
failed due the
+`RejectedExecutionException` is set on the
xref:manual:ROOT:exchange.adoc[Exchange]
+and the processing of the xref:manual:ROOT:exchange.adoc[Exchange] stops. This
means
+any consumer will see the xref:manual:ROOT:exchange.adoc[Exchange] as failed
due the
`RejectedExecutionException`.
The default value is `true` to be backwards compatible as before. For
@@ -445,7 +445,7 @@ And the sample with XML DSL
== Samples
The following example shows how to configure the Dead Letter Channel
-configuration using the xref:latest@manual:ROOT:dsl.adoc[DSL]
+configuration using the xref:manual:ROOT:dsl.adoc[DSL]
You can also configure the
https://www.javadoc.io/doc/org.apache.camel/camel-base/current/org/apache/camel/processor/errorhandler/RedeliveryPolicy.html[RedeliveryPolicy]
@@ -455,11 +455,11 @@ as this example shows
== How can I modify the Exchange before redelivery?
We support directly in xref:dead-letter-channel.adoc[Dead Letter
-Channel] to set a xref:latest@manual:ROOT:processor.adoc[Processor] that is
executed
+Channel] to set a xref:manual:ROOT:processor.adoc[Processor] that is executed
*before* each redelivery attempt.
When xref:dead-letter-channel.adoc[Dead Letter Channel] is doing
-redeliver its possible to configure a
xref:latest@manual:ROOT:processor.adoc[Processor]
+redeliver its possible to configure a
xref:manual:ROOT:processor.adoc[Processor]
that is executed just *before* every redelivery attempt. This can be
used for the situations where you need to alter the message before its
redelivered.
@@ -486,12 +486,12 @@ also
http://stackoverflow.com/questions/13711462/logging-camel-exceptions-and-se
=== Using This Pattern
If you would like to use this EIP Pattern then please read the
-xref:latest@manual:ROOT:getting-started.adoc[Getting Started], you may also
find the
-xref:latest@manual:ROOT:architecture.adoc[Architecture] useful particularly
the description
-of xref:latest@manual:ROOT:endpoint.adoc[Endpoint] and
xref:latest@manual:ROOT:uris.adoc[URIs]. Then you could
-try out some of the xref:latest@manual:ROOT:examples.adoc[Examples] first
before trying
+xref:manual:ROOT:getting-started.adoc[Getting Started], you may also find the
+xref:manual:ROOT:architecture.adoc[Architecture] useful particularly the
description
+of xref:manual:ROOT:endpoint.adoc[Endpoint] and
xref:manual:ROOT:uris.adoc[URIs]. Then you could
+try out some of the xref:manual:ROOT:examples.adoc[Examples] first before
trying
this pattern out.
-* xref:latest@manual:ROOT:error-handler.adoc[Error Handler]
-* xref:latest@manual:ROOT:exception-clause.adoc[Exception Clause]
+* xref:manual:ROOT:error-handler.adoc[Error Handler]
+* xref:manual:ROOT:exception-clause.adoc[Exception Clause]
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/enterprise-integration-patterns.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/enterprise-integration-patterns.adoc
index d01175b..5145d56 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/enterprise-integration-patterns.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/enterprise-integration-patterns.adoc
@@ -5,7 +5,7 @@ Camel supports most of the
http://www.eaipatterns.com/toc.html[Enterprise Integration Patterns]
from the excellent book by Gregor Hohpe and Bobby Woolf.
-If you are new to Camel you might want to try the
xref:latest@manual:ROOT:getting-started.adoc[Getting Started] in the
+If you are new to Camel you might want to try the
xref:manual:ROOT:getting-started.adoc[Getting Started] in the
User Guide before attempting to implement these patterns.
[[EnterpriseIntegrationPatterns-MessagingSystems]]
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/event-message.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/event-message.adoc
index bdbb468..38cf230 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/event-message.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/event-message.adoc
@@ -4,7 +4,7 @@
Camel supports the
http://www.enterpriseintegrationpatterns.com/EventMessage.html[Event
Message] from the xref:enterprise-integration-patterns.adoc[EIP
-patterns] by supporting the
xref:latest@manual:ROOT:exchange-pattern.adoc[Exchange Pattern]
+patterns] by supporting the xref:manual:ROOT:exchange-pattern.adoc[Exchange
Pattern]
on a xref:message.adoc[Message] which can be set to *InOnly* to indicate
a oneway event message. Camel xref:components::index.adoc[Components] then
implement this pattern using the underlying transport or protocols.
@@ -21,7 +21,7 @@ TIP: See the related xref:requestReply-eip.adoc[Request
Reply] message.
== Explicitly specifying InOnly
If you are using a component which defaults to InOut you can override
-the xref:latest@manual:ROOT:exchange-pattern.adoc[Exchange Pattern] for an
endpoint using
+the xref:manual:ROOT:exchange-pattern.adoc[Exchange Pattern] for an endpoint
using
the pattern property.
[source]
@@ -33,7 +33,7 @@ foo:bar?exchangePattern=InOnly
== Samples
From 2.0 onwards on Camel you can specify the
-xref:latest@manual:ROOT:exchange-pattern.adoc[Exchange Pattern] using the DSL.
+xref:manual:ROOT:exchange-pattern.adoc[Exchange Pattern] using the DSL.
[source,java]
----
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/eventDrivenConsumer-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/eventDrivenConsumer-eip.adoc
index aa3e086..cadef13 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/eventDrivenConsumer-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/eventDrivenConsumer-eip.adoc
@@ -21,7 +21,7 @@ when a xref:message.adoc[Message] is available for processing.
The following demonstrates a
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html[Processor]
-defined in the Camel xref:latest@manual:ROOT:registry.adoc[Registry] which is
+defined in the Camel xref:manual:ROOT:registry.adoc[Registry] which is
invoked when an event occurs from a xref:components::jms-component.adoc[JMS]
queue.
[source,java]
@@ -30,7 +30,7 @@ from("jms:queue:foo")
.processRef("processor");
----
-**Using the xref:latest@manual:ROOT:spring-xml-extensions.adoc[Spring XML
Extensions]**
+**Using the xref:manual:ROOT:spring-xml-extensions.adoc[Spring XML
Extensions]**
[source,xml]
----
@@ -49,8 +49,8 @@ For more details see:
== Using This Pattern
If you would like to use this EIP Pattern then please read the
-xref:latest@manual:ROOT:getting-started.adoc[Getting Started], you may also
find the
-xref:latest@manual:ROOT:architecture.adoc[Architecture] useful particularly
the description
-of xref:latest@manual:ROOT:endpoint.adoc[Endpoint] and
xref:latest@manual:ROOT:uris.adoc[URIs]. Then you could
-try out some of the xref:latest@manual:ROOT:examples.adoc[Examples] first
before trying
+xref:manual:ROOT:getting-started.adoc[Getting Started], you may also find the
+xref:manual:ROOT:architecture.adoc[Architecture] useful particularly the
description
+of xref:manual:ROOT:endpoint.adoc[Endpoint] and
xref:manual:ROOT:uris.adoc[URIs]. Then you could
+try out some of the xref:manual:ROOT:examples.adoc[Examples] first before
trying
this pattern out.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/filter-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/filter-eip.adoc
index ad43501..7b1dfea 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/filter-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/filter-eip.adoc
@@ -13,7 +13,7 @@ image::eip/MessageFilter.gif[image]
The following example shows how to create a Message Filter route
consuming messages from an endpoint called *queue:a*, which if the
-xref:latest@manual:ROOT:predicate.adoc[Predicate] is true will be dispatched
to *queue:b*
+xref:manual:ROOT:predicate.adoc[Predicate] is true will be dispatched to
*queue:b*
== EIP options
@@ -90,15 +90,15 @@ the when predicate by using the `.stop()`.
== Knowing if Exchange was filtered or not
The xref:filter-eip.adoc[Message Filter] EIP will add a property on
-the xref:latest@manual:ROOT:exchange.adoc[Exchange] that states if it was
filtered or not.
+the xref:manual:ROOT:exchange.adoc[Exchange] that states if it was filtered or
not.
The property has the key `Exchange.FILTER_MATCHED`, which has the String
value of `CamelFilterMatched`. Its value is a boolean indicating `true`
-or `false`. If the value is `true` then the
xref:latest@manual:ROOT:exchange.adoc[Exchange]
+or `false`. If the value is `true` then the
xref:manual:ROOT:exchange.adoc[Exchange]
was routed in the filter block. This property will be visible within the
xref:filter-eip.adoc[Message Filter] block who's
-xref:latest@manual:ROOT:predicate.adoc[Predicate] matches (value set to
`true`), and to the
+xref:manual:ROOT:predicate.adoc[Predicate] matches (value set to `true`), and
to the
steps immediately following the xref:filter-eip.adoc[Message Filter]
with the value set based on the results of the last
-xref:filter-eip.adoc[Message Filter]
xref:latest@manual:ROOT:predicate.adoc[Predicate]
+xref:filter-eip.adoc[Message Filter] xref:manual:ROOT:predicate.adoc[Predicate]
evaluated.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/idempotentConsumer-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/idempotentConsumer-eip.adoc
index 23c2c9c..d672145 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/idempotentConsumer-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/idempotentConsumer-eip.adoc
@@ -27,7 +27,7 @@ Camel provides the following Idempotent Consumer
implementations:
* xref:components::jpa-component.adoc[JpaMessageIdRepository]
* xref:components::infinispan-component.adoc[InfinispanIdempotentRepository]
* xref:components::jcache-component.adoc[JCacheIdempotentRepository]
-* xref:latest@manual:ROOT:spring.adoc[SpringCacheIdempotentRepository]
+* xref:manual:ROOT:spring.adoc[SpringCacheIdempotentRepository]
* xref:components::ehcache-component.adoc[EhcacheIdempotentRepository]
* xref:components::kafka-component.adoc[KafkaIdempotentRepository]
* xref:components::hbase-component.adoc[HbaseIdempotentRepository]
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/log-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/log-eip.adoc
index 7fde239..a8811a4 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/log-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/log-eip.adoc
@@ -9,8 +9,8 @@ How can I log the processing of a xref:message.adoc[Message]?
Camel provides many ways to log the fact that you are processing a message.
Here are just a few examples:
* You can use the xref:components::log-component.adoc[Log] component which
logs the Message content.
-* You can use the xref:latest@manual:ROOT:tracer.adoc[Tracer] which trace logs
message flow.
-* You can also use a xref:latest@manual:ROOT:processor.adoc[Processor] or
xref:latest@manual:ROOT:bean-binding.adoc[Bean] and log from Java code.
+* You can use the xref:manual:ROOT:tracer.adoc[Tracer] which trace logs
message flow.
+* You can also use a xref:manual:ROOT:processor.adoc[Processor] or
xref:manual:ROOT:bean-binding.adoc[Bean] and log from Java code.
* You can use the log DSL.
== Options
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/marshal-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/marshal-eip.adoc
index 9c2fb7f..ec9431f 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/marshal-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/marshal-eip.adoc
@@ -1,7 +1,7 @@
[[marshal-eip]]
= Marshal EIP
-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
xref:components::index.adoc[Components]. Marshalling is used in the same way as
unmarshalling above; in the xref:latest@manual:ROOT: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
xref:latest@manual:ROOT:registry.adoc [...]
+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
xref:components::index.adoc[Components]. Marshalling is used in the same way as
unmarshalling above; in the xref:manual:ROOT: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
xref:manual:ROOT:registry.adoc[Registry].
== Options
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-endpoint.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-endpoint.adoc
index 4351a23..417443b 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-endpoint.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-endpoint.adoc
@@ -10,8 +10,8 @@ interface.
image::eip/MessageEndpointSolution.gif[image]
-When using the xref:latest@manual:ROOT:dsl.adoc[DSL] to create
xref:latest@manual:ROOT:routes.adoc[Routes] you
-typically refer to Message Endpoints by their
xref:latest@manual:ROOT:uris.adoc[URIs]
+When using the xref:manual:ROOT:dsl.adoc[DSL] to create
xref:manual:ROOT:routes.adoc[Routes] you
+typically refer to Message Endpoints by their xref:manual:ROOT:uris.adoc[URIs]
rather than directly using the
https://www.javadoc.io/doc/org.apache.camel/camel-api/current/org/apache/camel/Endpoint.html[Endpoint]
interface. Its then a responsibility of the
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-router.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-router.adoc
index aa8204a..6cd275e 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-router.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-router.adoc
@@ -11,13 +11,13 @@ image::eip/MessageRouter.gif[image]
The following example shows how to route a request from an input
*queue:a* endpoint to either *queue:b*, *queue:c* or *queue:d* depending
-on the evaluation of various xref:latest@manual:ROOT:predicate.adoc[Predicate]
expressions
+on the evaluation of various xref:manual:ROOT:predicate.adoc[Predicate]
expressions
== Examples
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 xref:latest@manual:ROOT:predicate.adoc[Predicate]
expressions
+the evaluation of various xref:manual:ROOT:predicate.adoc[Predicate]
expressions
[source,java]
----
@@ -35,7 +35,7 @@ RouteBuilder builder = new RouteBuilder() {
};
----
-TIP: See
xref:latest@manual:faq:why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc[Why
+TIP: See
xref:manual: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] if you have
problems with the Java DSL, accepting using `when` or `otherwise`.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-translator.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-translator.adoc
index aef4c99..67a4e91 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-translator.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message-translator.adoc
@@ -4,10 +4,10 @@
Camel supports the
http://www.enterpriseintegrationpatterns.com/MessageTranslator.html[Message
Translator] from the xref:enterprise-integration-patterns.adoc[EIP
-patterns] by using an arbitrary
xref:latest@manual:ROOT:processor.adoc[Processor] in the
-routing logic, by using a xref:latest@manual:ROOT:bean-integration.adoc[bean]
to perform
+patterns] by using an arbitrary xref:manual:ROOT:processor.adoc[Processor] in
the
+routing logic, by using a xref:manual:ROOT:bean-integration.adoc[bean] to
perform
the transformation, or by using transform() in the DSL. You can also use
-a xref:latest@manual:ROOT:data-format.adoc[Data Format] to marshal and
unmarshal messages
+a xref:manual:ROOT:data-format.adoc[Data Format] to marshal and unmarshal
messages
in different encodings.
image::eip/MessageTranslator.gif[image]
@@ -15,9 +15,9 @@ image::eip/MessageTranslator.gif[image]
== Samples
You can transform a message using Camel's
-xref:latest@manual:ROOT:bean-integration.adoc[Bean Integration] to call any
method on a
-bean in your xref:latest@manual:ROOT:registry.adoc[Registry] such as your
-xref:latest@manual:ROOT:spring.adoc[Spring] XML configuration file as follows
+xref:manual:ROOT:bean-integration.adoc[Bean Integration] to call any method on
a
+bean in your xref:manual:ROOT:registry.adoc[Registry] such as your
+xref:manual:ROOT:spring.adoc[Spring] XML configuration file as follows
[source,java]
----
@@ -28,19 +28,19 @@ from("activemq:SomeQueue")
Where the "myTransformerBean" would be defined in a Spring XML file or
defined in JNDI etc. You can omit the method name parameter from
-beanRef() and the xref:latest@manual:ROOT:bean-integration.adoc[Bean
Integration] will try
+beanRef() and the xref:manual:ROOT:bean-integration.adoc[Bean Integration]
will try
to deduce the method to invoke from the message exchange.
-or you can add your own explicit
xref:latest@manual:ROOT:processor.adoc[Processor] to do
+or you can add your own explicit xref:manual:ROOT:processor.adoc[Processor] to
do
the transformation
or you can use the DSL to explicitly configure the transformation
-You can also use xref:latest@manual:ROOT:spring-xml-extensions.adoc[Spring XML
Extensions]
-to do a transformation. Basically any
xref:latest@manual:ROOT:expression.adoc[Expression]
+You can also use xref:manual:ROOT:spring-xml-extensions.adoc[Spring XML
Extensions]
+to do a transformation. Basically any
xref:manual:ROOT:expression.adoc[Expression]
language can be substituted inside the transform element as shown below
-Or you can use the xref:latest@manual:ROOT:bean-integration.adoc[Bean
Integration] to
+Or you can use the xref:manual:ROOT:bean-integration.adoc[Bean Integration] to
invoke a bean
[source,xml]
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message.adoc
index 737ec05..d576004 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/message.adoc
@@ -9,10 +9,10 @@ interface.
image::eip/MessageSolution.gif[image]
-To support various message
xref:latest@manual:ROOT:exchange-pattern.adoc[exchange patterns]
+To support various message xref:manual:ROOT:exchange-pattern.adoc[exchange
patterns]
like one way xref:event-message.adoc[Event Message] and
xref:requestReply-eip.adoc[Request Reply] messages Camel uses an
-xref:latest@manual:ROOT:exchange.adoc[Exchange] interface which has a
*pattern* property
+xref:manual:ROOT:exchange.adoc[Exchange] interface which has a *pattern*
property
which can be set to *InOnly* for an xref:event-message.adoc[Event
Message] which has a single inbound Message, or *InOut* for a
xref:requestReply-eip.adoc[Request Reply] where there is an inbound and
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/messaging-gateway.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/messaging-gateway.adoc
index e535588..c967871 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/messaging-gateway.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/messaging-gateway.adoc
@@ -15,5 +15,5 @@ Camel has several endpoint components that support the
Messaging Gateway from th
Components like xref:components::bean-component.adoc[Bean] and
xref:components::bean-component.adoc[CXF] provide a way
to bind a Java interface to the message exchange.
-Another approach is to use `@Produce` annotations which you can read about in
xref:latest@manual:ROOT:pojo-producing.adoc[POJO Producing]
+Another approach is to use `@Produce` annotations which you can read about in
xref:manual:ROOT:pojo-producing.adoc[POJO Producing]
which also can be used as a Messaging Gateway EIP solution.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/messaging-mapper.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/messaging-mapper.adoc
index 88abd34..e25bcb6 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/messaging-mapper.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/messaging-mapper.adoc
@@ -18,7 +18,7 @@ Since the Messaging Mapper is implemented as a separate class
that references th
and the messaging layer, neither layer is aware of the other. The layers don't
even know about the Messaging Mapper.
With Camel this pattern is often implemented directly via Camel components
that provides
-xref:latest@manual:ROOT:type-converter.adoc[Type Converter]'s from the
messaging infrastructure to common Java types or
+xref:manual:ROOT:type-converter.adoc[Type Converter]'s from the messaging
infrastructure to common Java types or
Java Objects representing the data model of the component in question.
Combining this with the
xref:message-translator.adoc[Message Translator] to have the Messaging Mapper
EIP pattern.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/multicast-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/multicast-eip.adoc
index bc5ae8a..a7bfc5a 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/multicast-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/multicast-eip.adoc
@@ -144,5 +144,5 @@ allows you to do this using the processor
interface.
Notice the `onPrepare` can be used for any kind of custom logic which
-you would like to execute before the
xref:latest@manual:ROOT:exchange.adoc[Exchange] is
+you would like to execute before the xref:manual:ROOT:exchange.adoc[Exchange]
is
being multicasted.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/otherwise-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/otherwise-eip.adoc
index 87d22a5..8bf661f 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/otherwise-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/otherwise-eip.adoc
@@ -21,7 +21,7 @@ The Otherwise EIP has no options.
The following example shows how to route a request from an input
*direct:a* endpoint to either *direct:b*, *direct:c* or *direct:d* depending on
-the evaluation of various xref:latest@manual:ROOT:predicate.adoc[Predicate]
expressions
+the evaluation of various xref:manual:ROOT:predicate.adoc[Predicate]
expressions
[source,java]
----
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/pipeline-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/pipeline-eip.adoc
index 0414588..8ec1db4 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/pipeline-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/pipeline-eip.adoc
@@ -10,7 +10,7 @@ Camel supports the
http://www.enterpriseintegrationpatterns.com/PipesAndFilters.
image::eip/PipesAndFilters.gif[image]
With Camel you can split your processing across multiple independent
-xref:latest@manual:ROOT:endpoint.adoc[Endpoint] instances which can then be
chained
+xref:manual:ROOT:endpoint.adoc[Endpoint] instances which can then be chained
together.
== Options
@@ -23,7 +23,7 @@ The Pipeline EIP has no options.
== Examples
You can create pipelines of logic using multiple
-xref:latest@manual:ROOT:endpoint.adoc[Endpoint] or
xref:message-translator.adoc[Message
+xref:manual:ROOT:endpoint.adoc[Endpoint] or
xref:message-translator.adoc[Message
Translator] instances as follows
Though pipeline is the default mode of operation when you specify
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/polling-consumer.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/polling-consumer.adoc
index 9966fe5..035bc4c 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/polling-consumer.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/polling-consumer.adoc
@@ -69,7 +69,7 @@ Notice that some Camel
xref:components::index.adoc[Components] has their own
implementation of *`PollingConsumer`* and therefore do not support the
options above.
-You can configure these options in endpoints
xref:latest@manual:ROOT:uris.adoc[URIs], such
+You can configure these options in endpoints xref:manual:ROOT:uris.adoc[URIs],
such
as shown below:
[source,java]
@@ -86,8 +86,8 @@ Exchange exchange = consumer.receive(5000);
The *`ConsumerTemplate`* is a template much like
Spring's *`JmsTemplate`* or *`JdbcTemplate`* supporting the
xref:polling-consumer.adoc[Polling Consumer] EIP. With the template you
-can consume xref:latest@manual:ROOT:exchange.adoc[Exchange]s from an
-xref:latest@manual:ROOT:endpoint.adoc[Endpoint]. The template supports the
three operations
+can consume xref:manual:ROOT:exchange.adoc[Exchange]s from an
+xref:manual:ROOT:endpoint.adoc[Endpoint]. The template supports the three
operations
listed above. However, it also includes convenient methods for returning
the body, etc *`consumeBody`*.
@@ -220,7 +220,7 @@ previous run polled 1 or more messages.
A pluggable *`org.apache.camel.PollingConsumerPollingStrategy`* allowing
you to provide your custom implementation to control error handling
usually occurred during the *`poll`* operation _*before*_ an
-xref:latest@manual:ROOT:exchange.adoc[Exchange] has been created and routed in
Camel. In
+xref:manual:ROOT:exchange.adoc[Exchange] has been created and routed in Camel.
In
other words the error occurred while the polling was gathering
information, for instance access to a file network failed so Camel
cannot access it to scan for files.
@@ -242,20 +242,20 @@ option allows you to share a thread pool among multiple
consumers.
*`org.apache.camel.spi.ScheduledPollConsumerScheduler`* to use as the
scheduler for firing when the polling consumer runs. The default
implementation uses the *`ScheduledExecutorService`* and there is a
-xref:components::quartz-component.adoc[Quartz], and
xref:latest@manual:ROOT:spring.adoc[Spring] based which
+xref:components::quartz-component.adoc[Quartz], and
xref:manual:ROOT:spring.adoc[Spring] based which
supports CRON expressions. *Notice:* If using a custom scheduler then
the options for *`initialDelay`, `useFixedDelay`*, *`timeUnit`* and
*`scheduledExecutorService`* may not be in use. Use the text *`quartz`*
to refer to use the xref:components::quartz-component.adoc[Quartz] scheduler;
and use the
-text `spring` to use the xref:latest@manual:ROOT:spring.adoc[Spring] based;
and use the
+text `spring` to use the xref:manual:ROOT:spring.adoc[Spring] based; and use
the
text *`#myScheduler`* to refer to a custom scheduler by its id in the
-xref:latest@manual:ROOT:registry.adoc[Registry].
+xref:manual:ROOT:registry.adoc[Registry].
See xref:components::quartz-component.adoc[Quartz] page for an example.
|`scheduler.xxx` |`null` |*Camel 2.12:* To configure additional
properties when using a custom *`scheduler`* or any of the
-xref:components::quartz-component.adoc[Quartz],
xref:latest@manual:ROOT:spring.adoc[Spring] based scheduler.
+xref:components::quartz-component.adoc[Quartz],
xref:manual:ROOT:spring.adoc[Spring] based scheduler.
|`sendEmptyMessageWhenIdle` |`false` |*Camel 2.9:* If the polling
consumer did not poll any files, you can enable this option to send an
@@ -319,9 +319,9 @@ is scheduled based and its *`run`* method is invoked
periodically based
on schedule settings. But errors can also occur when a poll is being
executed. For instance if Camel should poll a file network, and this
network resource is not available then a *`java.io.IOException`* could
-occur. As this error happens *before* any
xref:latest@manual:ROOT:exchange.adoc[Exchange]
+occur. As this error happens *before* any
xref:manual:ROOT:exchange.adoc[Exchange]
has been created and prepared for routing, then the regular
-xref:latest@manual:ROOT:error-handler.adoc[Error handler] does not
+xref:manual:ROOT:error-handler.adoc[Error handler] does not
apply. So what does the consumer do then? Well the exception is
propagated back to the *`run`* method where its handled. Camel will by
default log the exception at *`WARN`* level and then ignore it. At next
@@ -339,7 +339,7 @@ implement a custom scheduler to control when the
xref:polling-consumer.adoc[Polling Consumer] runs. The default
implementation is based on the JDKs *`ScheduledExecutorService`* with a
single thread in the thread pool. There is a CRON based implementation
-in the xref:components::quartz-component.adoc[Quartz], and
xref:latest@manual:ROOT:spring.adoc[Spring]
+in the xref:components::quartz-component.adoc[Quartz], and
xref:manual:ROOT:spring.adoc[Spring]
components.
For an example of developing and using a custom scheduler, see the unit
@@ -412,12 +412,12 @@ throwing exceptions as in such a case the *`poll`*
operation is not
invoked and Camel will invoke the *`rollback`* directly.
[[PollingConsumer-ConfiguringantoUsePollingConsumerPollStrategy]]
-=== Configuring an xref:latest@manual:ROOT:endpoint.adoc[Endpoint] to Use
`PollingConsumerPollStrategy`
+=== Configuring an xref:manual:ROOT:endpoint.adoc[Endpoint] to Use
`PollingConsumerPollStrategy`
-To configure an xref:latest@manual:ROOT:endpoint.adoc[Endpoint] to use a custom
+To configure an xref:manual:ROOT:endpoint.adoc[Endpoint] to use a custom
*`PollingConsumerPollStrategy`* you use the option *`pollStrategy`*. For
example in the file consumer below we want to use our custom strategy
-defined in the xref:latest@manual:ROOT:registry.adoc[Registry] with the bean
id *`myPoll`*:
+defined in the xref:manual:ROOT:registry.adoc[Registry] with the bean id
*`myPoll`*:
[source,java]
----
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/process-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/process-eip.adoc
index 2db2f6a..ade011a 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/process-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/process-eip.adoc
@@ -36,7 +36,7 @@ public class MyProcessor implements Processor {
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
-xref:latest@manual:ROOT:registry.adoc[Registry])
+xref:manual:ROOT:registry.adoc[Registry])
[source,xml]
--------------------------------------------------------
@@ -62,7 +62,7 @@ Processor myProcessor = new MyProcessor();
from("activemq:myQueue").process(myProcessor);
----
-If you need to lookup the processor in the
xref:latest@manual:ROOT:registry.adoc[Registry]
+If you need to lookup the processor in the
xref:manual:ROOT:registry.adoc[Registry]
then you should use the *processRef* DSL:
[source,java]
@@ -93,11 +93,11 @@ 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 xref:latest@manual:ROOT:endpoint.adoc[Endpoint]
semantics given a
+which supports the full xref:manual:ROOT:endpoint.adoc[Endpoint] semantics
given a
Processor instance.
So you just need to create a
https://github.com/apache/camel/tree/main/components[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
-xref:latest@manual:ROOT:writing-components.adoc[Writing Components]
+xref:manual:ROOT:writing-components.adoc[Writing Components]
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/properties-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/properties-component.adoc
index c3c2e91..f82847b 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/properties-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/properties-component.adoc
@@ -13,7 +13,7 @@ The properties component is used for property placeholders in
your Camel applica
It is *not* a regular Camel component with producer and consumer for routing
messages.
However, for historical reasons it was named `PropertiesComponent` and this
name is commonly known so we keep using it.
-IMPORTANT: See the
xref:latest@manual:ROOT:using-propertyplaceholder.adoc[Property Placeholder]
documentation for general information on using property placeholders in Camel.
+IMPORTANT: See the xref:manual:ROOT:using-propertyplaceholder.adoc[Property
Placeholder] documentation for general information on using property
placeholders in Camel.
The properties component requires to load the properties (key=value pairs)
from an external source such as `.properties` files.
The component is pluggable and you can configure to use other sources or write
a custom implementation (for example to load from a database).
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/publish-subscribe-channel.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/publish-subscribe-channel.adoc
index 55f2fe4..43fa12e 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/publish-subscribe-channel.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/publish-subscribe-channel.adoc
@@ -11,7 +11,7 @@ example the following components:
clustering and load balancing
* xref:components::xmpp-component.adoc[XMPP] when using rooms for group
communication
* xref:components::seda-component.adoc[SEDA] for working with SEDA in the same
-xref:latest@manual:ROOT:camelcontext.adoc[CamelContext] which can work in
pub-sub, but
+xref:manual:ROOT:camelcontext.adoc[CamelContext] which can work in pub-sub, but
allowing multiple consumers.
* xref:components::vm-component.adoc[VM] as SEDA but for intra-JVM.
@@ -23,7 +23,7 @@ image::eip/PublishSubscribeSolution.gif[image]
Another option is to explicitly list the publish-subscribe relationship
in your routing logic; this keeps the producer and consumer decoupled
but lets you control the fine grained routing configuration using the
-xref:latest@manual:ROOT:dsl.adoc[DSL].
+xref:manual:ROOT:dsl.adoc[DSL].
In Java code:
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/service-activator.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/service-activator.adoc
index f21cca3..3f2cb32 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/service-activator.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/service-activator.adoc
@@ -17,7 +17,7 @@ Components like xref:components::bean-component.adoc[Bean]
and xref:components:
provide a way to bind the message exchange to a Java interface/service where
the route defines the
endpoints and wires it up to the bean.
-In addition you can use the xref:latest@manual:ROOT:bean-integration.adoc[Bean
Integration] to wire messages
+In addition you can use the xref:manual:ROOT:bean-integration.adoc[Bean
Integration] to wire messages
to a bean using annotation.
== Sample
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/toD-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/toD-eip.adoc
index 1589429..93417b7 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/toD-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/toD-eip.adoc
@@ -6,8 +6,8 @@
:supportLevel: Stable
There is a new `.toD` / `<toD>` that allows to send a message to a dynamic
-computed xref:latest@manual:ROOT:endpoint.adoc[Endpoint] using one or
-more xref:latest@manual:ROOT:expression.adoc[Expression] that are concat
together. By
+computed xref:manual:ROOT:endpoint.adoc[Endpoint] using one or
+more xref:manual:ROOT:expression.adoc[Expression] that are concat together. By
default the xref:components:languages:simple-language.adoc[Simple] language is
used to compute
the endpoint.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/transactional-client.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/transactional-client.adoc
index c96ede9..970aff2 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/transactional-client.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/transactional-client.adoc
@@ -288,9 +288,9 @@ route as transacted using the *transacted* tag.
When a route is marked as transacted using *transacted* Camel will
automatic use `TransactionErrorHandler` as the
-xref:latest@manual:ROOT:error-handler.adoc[Error Handler]. This error handler
supports basically the same
-feature set as the
xref:latest@manual:ROOT:defaulterrorhandler.adoc[DefaultErrorHandler],
-so you can for instance use
xref:latest@manual:ROOT:exception-clause.adoc[Exception Clause]
+xref:manual:ROOT:error-handler.adoc[Error Handler]. This error handler
supports basically the same
+feature set as the
xref:manual:ROOT:defaulterrorhandler.adoc[DefaultErrorHandler],
+so you can for instance use xref:manual:ROOT:exception-clause.adoc[Exception
Clause]
as well.
[[TransactionalClient-IntegrationTestingwithSpring]]
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/unmarshal-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/unmarshal-eip.adoc
index d998681..aac126b 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/unmarshal-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/unmarshal-eip.adoc
@@ -1,7 +1,7 @@
[[unmarshal-eip]]
= Unmarshal EIP
-If you receive a message from one of the Camel
xref:components::index.adoc[Components] such as
xref:components::file-component.adoc[File],
xref:components::http-component.adoc[HTTP] or
xref:components::jms-component.adoc[JMS] you often want to unmarshal the
payload into some bean so that you can process it using some
xref:latest@manual:ROOT:bean-integration.adoc[Bean Integration] or perform
xref:latest@manual:ROOT:predicate.adoc[Predicate] evaluation and so forth.
+If you receive a message from one of the Camel
xref:components::index.adoc[Components] such as
xref:components::file-component.adoc[File],
xref:components::http-component.adoc[HTTP] or
xref:components::jms-component.adoc[JMS] you often want to unmarshal the
payload into some bean so that you can process it using some
xref:manual:ROOT:bean-integration.adoc[Bean Integration] or perform
xref:manual:ROOT:predicate.adoc[Predicate] evaluation and so forth.
== Options
@@ -29,7 +29,7 @@ from("activemq:My.Queue").
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
xref:latest@manual:ROOT:registry.adoc[Registry] such as via your
xref:components::spring-summary.adoc[Spring] XML file.
+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
xref:manual:ROOT:registry.adoc[Registry] such as via your
xref:components::spring-summary.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
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/when-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/when-eip.adoc
index b4cf993..23590d7 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/when-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/when-eip.adoc
@@ -21,7 +21,7 @@ The When EIP has no options.
The following example shows how to route a request from an input
*direct:a* endpoint to either *direct:b*, *direct:c* or *direct:d* depending on
-the evaluation of various xref:latest@manual:ROOT:predicate.adoc[Predicate]
expressions
+the evaluation of various xref:manual:ROOT:predicate.adoc[Predicate]
expressions
[source,java]
----
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/wireTap-eip.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/wireTap-eip.adoc
index a7c8c54..9b3681c 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/wireTap-eip.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/wireTap-eip.adoc
@@ -15,9 +15,9 @@ image::eip/WireTap.gif[image]
== Streams
If you xref:wireTap-eip.adoc[Wire Tap] a stream message body then you
-should consider enabling xref:latest@manual:ROOT:stream-caching.adoc[Stream
caching] to
+should consider enabling xref:manual:ROOT:stream-caching.adoc[Stream caching]
to
ensure the message body can be read at each endpoint. See more details
-at xref:latest@manual:ROOT:stream-caching.adoc[Stream caching].
+at xref:manual:ROOT:stream-caching.adoc[Stream caching].
TIP: See the `cacheSize` option for more details on _how much cache_ to use
depending on how many or few unique endpoints are used.
@@ -48,7 +48,7 @@ The Wire Tap EIP supports 12 options which are listed below:
The WireTap uses a thread pool to process the
tapped messages. This thread pool will by default use the settings
-detailed at xref:latest@manual:ROOT:threading-model.adoc[Threading Model]. In
particular,
+detailed at xref:manual:ROOT:threading-model.adoc[Threading Model]. In
particular,
when the pool is exhausted (with all threads utilized), further wiretaps
will be executed synchronously by the calling thread. To remedy this,
you can configure an explicit thread pool on the xref:wireTap-eip.adoc[Wire
@@ -58,19 +58,19 @@ or more worker threads.
== WireTap Node
Camel's Wire Tap node supports two flavors when tapping an
-xref:latest@manual:ROOT:exchange.adoc[Exchange]:
+xref:manual:ROOT:exchange.adoc[Exchange]:
- With the traditional Wire Tap, Camel will copy the original
-xref:latest@manual:ROOT:exchange.adoc[Exchange] and set its
-xref:latest@manual:ROOT:exchange-pattern.adoc[Exchange Pattern] to *`InOnly`*,
as we want
-the tapped xref:latest@manual:ROOT:exchange.adoc[Exchange] to be sent in a
fire and forget
-style. The tapped xref:latest@manual:ROOT:exchange.adoc[Exchange] is then sent
in a
+xref:manual:ROOT:exchange.adoc[Exchange] and set its
+xref:manual:ROOT:exchange-pattern.adoc[Exchange Pattern] to *`InOnly`*, as we
want
+the tapped xref:manual:ROOT:exchange.adoc[Exchange] to be sent in a fire and
forget
+style. The tapped xref:manual:ROOT:exchange.adoc[Exchange] is then sent in a
separate thread so it can run in parallel with the original. Beware that
only the Exchange is copied - Wire Tap won't do a deep clone (unless you
specify a custom processor via *`onPrepareRef`* which does that). So all
copies could share objects from the original Exchange.
- Camel also provides an option of sending a new
-xref:latest@manual:ROOT:exchange.adoc[Exchange] allowing you to populate it
with new
+xref:manual:ROOT:exchange.adoc[Exchange] allowing you to populate it with new
values.
== Sending a Copy (traditional wiretap)
@@ -98,25 +98,25 @@ values.
}
----
-== Sending a New xref:latest@manual:ROOT:exchange.adoc[Exchange]
+== Sending a New xref:manual:ROOT:exchange.adoc[Exchange]
Camel supports either a processor or an
-xref:latest@manual:ROOT:expression.adoc[Expression] to populate the new
-xref:latest@manual:ROOT:exchange.adoc[Exchange]. Using a processor gives you
full power
-over how the xref:latest@manual:ROOT:exchange.adoc[Exchange] is populated as
you can set
-properties, headers, etc. An
xref:latest@manual:ROOT:expression.adoc[Expression] can only
+xref:manual:ROOT:expression.adoc[Expression] to populate the new
+xref:manual:ROOT:exchange.adoc[Exchange]. Using a processor gives you full
power
+over how the xref:manual:ROOT:exchange.adoc[Exchange] is populated as you can
set
+properties, headers, etc. An xref:manual:ROOT:expression.adoc[Expression] can
only
be used to set the *`IN`* body.
-The xref:latest@manual:ROOT:expression.adoc[Expression] or
-xref:latest@manual:ROOT:processor.adoc[Processor] is pre-populated with a copy
of the
-original xref:latest@manual:ROOT:exchange.adoc[Exchange], which allows you to
access the
-original message when you prepare a new
xref:latest@manual:ROOT:exchange.adoc[Exchange] to
+The xref:manual:ROOT:expression.adoc[Expression] or
+xref:manual:ROOT:processor.adoc[Processor] is pre-populated with a copy of the
+original xref:manual:ROOT:exchange.adoc[Exchange], which allows you to access
the
+original message when you prepare a new
xref:manual:ROOT:exchange.adoc[Exchange] to
be sent. You can use the *`copy`* option (enabled by default) to
indicate whether you want this.
Below is the processor variation,
where we disable *`copy`* by passing in *`false`* to create a new, empty
-xref:latest@manual:ROOT:exchange.adoc[Exchange]
+xref:manual:ROOT:exchange.adoc[Exchange]
[source,java]
----
@@ -156,8 +156,8 @@ part of the queue name:
If you send a new message using xref:wireTap-eip.adoc[Wire Tap], then you
could only set the message body using an
-xref:latest@manual:ROOT:expression.adoc[Expression] from the DSL. If you also
need to set
-headers, you would have to use a
xref:latest@manual:ROOT:processor.adoc[Processor]. From
+xref:manual:ROOT:expression.adoc[Expression] from the DSL. If you also need to
set
+headers, you would have to use a xref:manual:ROOT:processor.adoc[Processor].
From
It's possible to set headers as well using the DSL.
The following example sends a new message which has
diff --git a/core/camel-base/src/main/docs/properties-component.adoc
b/core/camel-base/src/main/docs/properties-component.adoc
index c3c2e91..f82847b 100644
--- a/core/camel-base/src/main/docs/properties-component.adoc
+++ b/core/camel-base/src/main/docs/properties-component.adoc
@@ -13,7 +13,7 @@ The properties component is used for property placeholders in
your Camel applica
It is *not* a regular Camel component with producer and consumer for routing
messages.
However, for historical reasons it was named `PropertiesComponent` and this
name is commonly known so we keep using it.
-IMPORTANT: See the
xref:latest@manual:ROOT:using-propertyplaceholder.adoc[Property Placeholder]
documentation for general information on using property placeholders in Camel.
+IMPORTANT: See the xref:manual:ROOT:using-propertyplaceholder.adoc[Property
Placeholder] documentation for general information on using property
placeholders in Camel.
The properties component requires to load the properties (key=value pairs)
from an external source such as `.properties` files.
The component is pluggable and you can configure to use other sources or write
a custom implementation (for example to load from a database).
diff --git a/docs/components/modules/ROOT/pages/properties-component.adoc
b/docs/components/modules/ROOT/pages/properties-component.adoc
index 4da1bfc..1852648 100644
--- a/docs/components/modules/ROOT/pages/properties-component.adoc
+++ b/docs/components/modules/ROOT/pages/properties-component.adoc
@@ -15,7 +15,7 @@ The properties component is used for property placeholders in
your Camel applica
It is *not* a regular Camel component with producer and consumer for routing
messages.
However, for historical reasons it was named `PropertiesComponent` and this
name is commonly known so we keep using it.
-IMPORTANT: See the
xref:latest@manual:ROOT:using-propertyplaceholder.adoc[Property Placeholder]
documentation for general information on using property placeholders in Camel.
+IMPORTANT: See the xref:manual:ROOT:using-propertyplaceholder.adoc[Property
Placeholder] documentation for general information on using property
placeholders in Camel.
The properties component requires to load the properties (key=value pairs)
from an external source such as `.properties` files.
The component is pluggable and you can configure to use other sources or write
a custom implementation (for example to load from a database).
diff --git a/docs/components/modules/others/pages/yaml-dsl.adoc
b/docs/components/modules/others/pages/yaml-dsl.adoc
index f0569fb..066e6b4 100644
--- a/docs/components/modules/others/pages/yaml-dsl.adoc
+++ b/docs/components/modules/others/pages/yaml-dsl.adoc
@@ -144,7 +144,7 @@ To define an endpoint with the YAML dsl you have three
options:
parameters:
authorizationToken: "XXX"
----
-. Using the YAML implementation of the
xref:latest@manual::Endpoint-dsl.adoc[Endpoint DSL]:
+. Using the YAML implementation of the xref:manual::Endpoint-dsl.adoc[Endpoint
DSL]:
+
[source,yaml]
----
diff --git a/docs/user-manual/modules/ROOT/pages/error-handling-in-camel.adoc
b/docs/user-manual/modules/ROOT/pages/error-handling-in-camel.adoc
index 08d9aef..2d1cf5c 100644
--- a/docs/user-manual/modules/ROOT/pages/error-handling-in-camel.adoc
+++ b/docs/user-manual/modules/ROOT/pages/error-handling-in-camel.adoc
@@ -120,7 +120,7 @@
https://issues.apache.org/jira/browse/CAMEL-5456[CAMEL-5456].
//NOTE: normal attribute replacement doesn't seem to work in xrefs in section
headers.
[[ErrorhandlinginCamel-Howdoestheerrorhandlerwork]]
-== How does the xref:latest@components:eips:dead-letter-channel.adoc[Dead
Letter Channel] error handler work
+== How does the xref:next@components:eips:dead-letter-channel.adoc[Dead Letter
Channel] error handler work
When Camel is started it will inspect the routes and weave in the error
handling into the routing. With up to 3 supported scopes, the error
diff --git a/docs/user-manual/modules/ROOT/references.adoc
b/docs/user-manual/modules/ROOT/references.adoc
index 80f7a38..248f88a 100644
--- a/docs/user-manual/modules/ROOT/references.adoc
+++ b/docs/user-manual/modules/ROOT/references.adoc
@@ -1,5 +1,5 @@
* *Reference*
-* xref:latest@components::index.adoc[Components]
-* xref:latest@components:dataformats:index.adoc[Data Formats]
-* xref:latest@components:languages:index.adoc[Languages]
+* xref:next@components::index.adoc[Components]
+* xref:next@components:dataformats:index.adoc[Data Formats]
+* xref:next@components:languages:index.adoc[Languages]
* xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[EIPs]
diff --git a/dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc
b/dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc
index 6ab3160..dc3f8a7 100644
--- a/dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc
+++ b/dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc
@@ -142,7 +142,7 @@ To define an endpoint with the YAML dsl you have three
options:
parameters:
authorizationToken: "XXX"
----
-. Using the YAML implementation of the
xref:latest@manual::Endpoint-dsl.adoc[Endpoint DSL]:
+. Using the YAML implementation of the xref:manual::Endpoint-dsl.adoc[Endpoint
DSL]:
+
[source,yaml]
----
