This is an automated email from the ASF dual-hosted git repository.
djencks pushed a commit to branch camel-2.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-2.x by this push:
new 7544d9a latest to next
7544d9a is described below
commit 7544d9af1898fa2cd4decb95cf84334bb0f00d5e
Author: David Jencks <djen...@apache.org>
AuthorDate: Sun Oct 24 12:52:46 2021 -0700
latest to next
---
.../src/main/docs/modules/ROOT/pages/dataformat-component.adoc | 6 +++---
camel-core/src/main/docs/modules/ROOT/pages/timer-component.adoc | 2 +-
camel-core/src/main/docs/modules/ROOT/pages/xslt-component.adoc | 2 +-
components/camel-ahc/src/main/docs/ahc-component.adoc | 2 +-
components/camel-beanstalk/src/main/docs/beanstalk-component.adoc | 2 +-
components/camel-cdi/src/main/docs/cdi.adoc | 2 +-
components/camel-cometd/src/main/docs/cometd-component.adoc | 2 +-
components/camel-crypto/src/main/docs/crypto-component.adoc | 2 +-
components/camel-grape/src/main/docs/grape-component.adoc | 2 +-
components/camel-http/src/main/docs/http-component.adoc | 2 +-
components/camel-http4/src/main/docs/http4-component.adoc | 2 +-
components/camel-irc/src/main/docs/irc-component.adoc | 2 +-
components/camel-jetty9/src/main/docs/jetty-component.adoc | 4 ++--
components/camel-jms/src/main/docs/jms-component.adoc | 2 +-
components/camel-jpa/src/main/docs/jpa-component.adoc | 2 +-
components/camel-lzf/src/main/docs/lzf-dataformat.adoc | 2 +-
components/camel-mail/src/main/docs/mail-component.adoc | 2 +-
components/camel-nagios/src/main/docs/nagios-component.adoc | 2 +-
components/camel-netty/src/main/docs/netty-component.adoc | 2 +-
components/camel-netty4/src/main/docs/netty4-component.adoc | 2 +-
components/camel-paho/src/main/docs/paho-component.adoc | 2 +-
components/camel-spring/src/main/docs/spring-summary.adoc | 6 +++---
components/camel-test-spring/src/main/docs/test-spring.adoc | 2 +-
components/camel-undertow/src/main/docs/undertow-component.adoc | 2 +-
.../src/main/docs/univocity-csv-dataformat.adoc | 2 +-
.../src/main/docs/univocity-fixed-dataformat.adoc | 2 +-
.../src/main/docs/univocity-tsv-dataformat.adoc | 2 +-
components/camel-websocket/src/main/docs/websocket-component.adoc | 2 +-
.../camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc | 2 +-
components/camel-zipkin/src/main/docs/zipkin.adoc | 4 ++--
docs/components/modules/ROOT/pages/ahc-component.adoc | 2 +-
docs/components/modules/ROOT/pages/beanstalk-component.adoc | 2 +-
docs/components/modules/ROOT/pages/cometd-component.adoc | 2 +-
docs/components/modules/ROOT/pages/crypto-component.adoc | 2 +-
docs/components/modules/ROOT/pages/grape-component.adoc | 2 +-
docs/components/modules/ROOT/pages/http-component.adoc | 2 +-
docs/components/modules/ROOT/pages/http4-component.adoc | 2 +-
docs/components/modules/ROOT/pages/irc-component.adoc | 2 +-
docs/components/modules/ROOT/pages/jetty-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/jms-component.adoc | 2 +-
docs/components/modules/ROOT/pages/jpa-component.adoc | 2 +-
docs/components/modules/ROOT/pages/mail-component.adoc | 2 +-
docs/components/modules/ROOT/pages/nagios-component.adoc | 2 +-
docs/components/modules/ROOT/pages/netty-component.adoc | 2 +-
docs/components/modules/ROOT/pages/netty4-component.adoc | 2 +-
docs/components/modules/ROOT/pages/paho-component.adoc | 2 +-
docs/components/modules/ROOT/pages/spring-summary.adoc | 6 +++---
docs/components/modules/ROOT/pages/undertow-component.adoc | 2 +-
docs/components/modules/ROOT/pages/websocket-component.adoc | 2 +-
docs/components/modules/ROOT/pages/xmlsecurity-component.adoc | 2 +-
docs/components/modules/dataformats/pages/lzf-dataformat.adoc | 2 +-
.../modules/dataformats/pages/univocity-csv-dataformat.adoc | 2 +-
.../modules/dataformats/pages/univocity-fixed-dataformat.adoc | 2 +-
.../modules/dataformats/pages/univocity-tsv-dataformat.adoc | 2 +-
docs/components/modules/others/pages/cdi.adoc | 2 +-
docs/components/modules/others/pages/test-spring.adoc | 2 +-
docs/components/modules/others/pages/zipkin.adoc | 4 ++--
57 files changed, 67 insertions(+), 67 deletions(-)
diff --git
a/camel-core/src/main/docs/modules/ROOT/pages/dataformat-component.adoc
b/camel-core/src/main/docs/modules/ROOT/pages/dataformat-component.adoc
index 6c7fe2c..b9ca158 100644
--- a/camel-core/src/main/docs/modules/ROOT/pages/dataformat-component.adoc
+++ b/camel-core/src/main/docs/modules/ROOT/pages/dataformat-component.adoc
@@ -9,7 +9,7 @@
*Since Camel {since}*
-The *dataformat:* component allows to use
xref:latest@manual::data-format.adoc[Data
+The *dataformat:* component allows to use xref:manual::data-format.adoc[Data
Format] as a Camel Component.
== URI format
@@ -21,7 +21,7 @@ dataformat:name:(marshal|unmarshal)[?options]
Where *name* is the name of the Data Format. And
then followed by the operation which must either be `marshal` or
-`unmarshal`. The options is used for configuring the
xref:latest@manual::data-format.adoc[Data
+`unmarshal`. The options is used for configuring the
xref:manual::data-format.adoc[Data
Format] in use. See the Data Format documentation
for which options it support.
@@ -67,7 +67,7 @@ with the following path and query parameters:
== Samples
-For example to use the xref:dataformats:jaxb-dataformat.adoc[JAXB]
xref:latest@manual::data-format.adoc[Data
+For example to use the xref:dataformats:jaxb-dataformat.adoc[JAXB]
xref:manual::data-format.adoc[Data
Format] we can do as follows:
[source,java]
diff --git a/camel-core/src/main/docs/modules/ROOT/pages/timer-component.adoc
b/camel-core/src/main/docs/modules/ROOT/pages/timer-component.adoc
index 78495af1..8cc8abe 100644
--- a/camel-core/src/main/docs/modules/ROOT/pages/timer-component.adoc
+++ b/camel-core/src/main/docs/modules/ROOT/pages/timer-component.adoc
@@ -35,7 +35,7 @@ advanced scheduling.
TIP:*Specify time in human friendly format*
In *Camel 2.3* onwards you can specify the time in
-xref:latest@manual:faq:how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc[human
+xref:manual:faq:how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc[human
friendly syntax].
diff --git a/camel-core/src/main/docs/modules/ROOT/pages/xslt-component.adoc
b/camel-core/src/main/docs/modules/ROOT/pages/xslt-component.adoc
index 5a335b9..577c054 100644
--- a/camel-core/src/main/docs/modules/ROOT/pages/xslt-component.adoc
+++ b/camel-core/src/main/docs/modules/ROOT/pages/xslt-component.adoc
@@ -284,7 +284,7 @@ With Spring XML:
== Dynamic stylesheets
To provide a dynamic stylesheet at runtime you can define a dynamic URI.
-See xref:latest@manual:faq:how-to-use-a-dynamic-uri-in-to.adoc[How to use a
dynamic URI in
+See xref:manual:faq:how-to-use-a-dynamic-uri-in-to.adoc[How to use a dynamic
URI in
to()] for more information.
*Since Camel 2.9 (removed in 2.11.4, 2.12.3 and 2.13.0*
diff --git a/components/camel-ahc/src/main/docs/ahc-component.adoc
b/components/camel-ahc/src/main/docs/ahc-component.adoc
index 6801954..9686891 100644
--- a/components/camel-ahc/src/main/docs/ahc-component.adoc
+++ b/components/camel-ahc/src/main/docs/ahc-component.adoc
@@ -429,7 +429,7 @@ from("direct:start")
Using the JSSE Configuration Utility
The AHC component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
index 58676a1..a37526d 100644
--- a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
+++ b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
@@ -52,7 +52,7 @@ beanstalk://localhost:11300/tube1+tube2
Tube name will be URL decoded, so if your tube names include special
characters like + or ?, you need to URL-encode them appropriately, or
-use the RAW syntax, see
xref:latest@manual:faq:how-do-i-configure-endpoints.adoc[more
+use the RAW syntax, see xref:manual:faq:how-do-i-configure-endpoints.adoc[more
details here].
By the way, you cannot specify several tubes when you are writing jobs
diff --git a/components/camel-cdi/src/main/docs/cdi.adoc
b/components/camel-cdi/src/main/docs/cdi.adoc
index b347ac2..52b7262 100644
--- a/components/camel-cdi/src/main/docs/cdi.adoc
+++ b/components/camel-cdi/src/main/docs/cdi.adoc
@@ -841,7 +841,7 @@ MockEndpoint outbound = endpoints
== Maven Archetype
-Among the available xref:latest@manual::camel-maven-archetypes.adoc[Camel Maven
+Among the available xref:manual::camel-maven-archetypes.adoc[Camel Maven
archetypes], you can use the provided `camel-archetype-cdi` to generate
a Camel CDI Maven project, e.g.:
diff --git a/components/camel-cometd/src/main/docs/cometd-component.adoc
b/components/camel-cometd/src/main/docs/cometd-component.adoc
index a86a719..21f66a2 100644
--- a/components/camel-cometd/src/main/docs/cometd-component.adoc
+++ b/components/camel-cometd/src/main/docs/cometd-component.adoc
@@ -187,7 +187,7 @@
http://cometd.org/documentation/howtos/authentication[documented here]
=== Using the JSSE Configuration Utility
The Cometd component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-crypto/src/main/docs/crypto-component.adoc
b/components/camel-crypto/src/main/docs/crypto-component.adoc
index b28d2ae..a555387 100644
--- a/components/camel-crypto/src/main/docs/crypto-component.adoc
+++ b/components/camel-crypto/src/main/docs/crypto-component.adoc
@@ -215,7 +215,7 @@ The component supports 33 options, which are listed below.
The most basic way to way to sign and verify an exchange is with a
KeyPair as follows.
-The same can be achieved with the
xref:latest@manual::spring-xml-extensions.adoc[Spring
+The same can be achieved with the
xref:manual::spring-xml-extensions.adoc[Spring
XML Extensions] using references to keys
=== KeyStores and Aliases.
diff --git a/components/camel-grape/src/main/docs/grape-component.adoc
b/components/camel-grape/src/main/docs/grape-component.adoc
index 62b851e..c6ce334 100644
--- a/components/camel-grape/src/main/docs/grape-component.adoc
+++ b/components/camel-grape/src/main/docs/grape-component.adoc
@@ -135,7 +135,7 @@ By default Camel Grape component operates on the String
payloads:
producerTemplate.sendBody("grape:defaultMavenCoordinates",
"org.apache.camel/camel-ftp/2.15.2");
------------------------------------------------------------------------------------------------
-But of course Camel build-in xref:latest@manual::type-converter.adoc[type
conversion
+But of course Camel build-in xref:manual::type-converter.adoc[type conversion
API] can perform the automatic data type transformations for you. In the
example below Camel automatically converts binary payload into the
String:
diff --git a/components/camel-http/src/main/docs/http-component.adoc
b/components/camel-http/src/main/docs/http-component.adoc
index 39da2b9..93c768a 100644
--- a/components/camel-http/src/main/docs/http-component.adoc
+++ b/components/camel-http/src/main/docs/http-component.adoc
@@ -542,7 +542,7 @@ behavior.
Using the JSSE Configuration Utility
The HTTP component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-http4/src/main/docs/http4-component.adoc
b/components/camel-http4/src/main/docs/http4-component.adoc
index 495188a..801ab08 100644
--- a/components/camel-http4/src/main/docs/http4-component.adoc
+++ b/components/camel-http4/src/main/docs/http4-component.adoc
@@ -588,7 +588,7 @@ behavior.
Using the JSSE Configuration Utility
As of Camel 2.8, the HTTP4 component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-irc/src/main/docs/irc-component.adoc
b/components/camel-irc/src/main/docs/irc-component.adoc
index d047dcc..3a35a71 100644
--- a/components/camel-irc/src/main/docs/irc-component.adoc
+++ b/components/camel-irc/src/main/docs/irc-component.adoc
@@ -151,7 +151,7 @@ The component supports 3 options, which are listed below.
=== Using the JSSE Configuration Utility
The IRC component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-jetty9/src/main/docs/jetty-component.adoc
b/components/camel-jetty9/src/main/docs/jetty-component.adoc
index da1be335..3db2212 100644
--- a/components/camel-jetty9/src/main/docs/jetty-component.adoc
+++ b/components/camel-jetty9/src/main/docs/jetty-component.adoc
@@ -320,7 +320,7 @@ If you need to expose a Jetty endpoint on all network
interfaces, the
`0.0.0.0` address should be used.
To listen across an entire URI prefix, see
-xref:latest@manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let
Jetty match
+xref:manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let Jetty
match
wildcards].
If you actually want to expose routes by HTTP and already have a
@@ -386,7 +386,7 @@ public void process(Exchange exchange) throws Exception {
Using the JSSE Configuration Utility
As of Camel 2.8, the Jetty component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-jms/src/main/docs/jms-component.adoc
b/components/camel-jms/src/main/docs/jms-component.adoc
index 26b555b..0153be3 100644
--- a/components/camel-jms/src/main/docs/jms-component.adoc
+++ b/components/camel-jms/src/main/docs/jms-component.adoc
@@ -663,7 +663,7 @@ from("file://orders").
=== Using Annotations
-Camel also has annotations so you can use
xref:latest@manual::pojo-consuming.adoc[POJO
+Camel also has annotations so you can use xref:manual::pojo-consuming.adoc[POJO
Consuming] and POJO Producing.
=== Spring DSL sample
diff --git a/components/camel-jpa/src/main/docs/jpa-component.adoc
b/components/camel-jpa/src/main/docs/jpa-component.adoc
index 429e014..375fa4b 100644
--- a/components/camel-jpa/src/main/docs/jpa-component.adoc
+++ b/components/camel-jpa/src/main/docs/jpa-component.adoc
@@ -87,7 +87,7 @@ jpa:entityClassName[?options]
-----------------------------
For sending to the endpoint, the _entityClassName_ is optional. If
-specified, it helps the xref:latest@manual::type-converter.adoc[Type
Converter] to
+specified, it helps the xref:manual::type-converter.adoc[Type Converter] to
ensure the body is of the correct type.
For consuming, the _entityClassName_ is mandatory.
diff --git a/components/camel-lzf/src/main/docs/lzf-dataformat.adoc
b/components/camel-lzf/src/main/docs/lzf-dataformat.adoc
index 8e4f290..6cd2ac9 100644
--- a/components/camel-lzf/src/main/docs/lzf-dataformat.adoc
+++ b/components/camel-lzf/src/main/docs/lzf-dataformat.adoc
@@ -9,7 +9,7 @@
The
-LZF xref:latest@manual::data-format.adoc[Data Format] is a message compression
+LZF xref:manual::data-format.adoc[Data Format] is a message compression
and de-compression format. It uses the
LZF deflate algorithm. Messages marshalled using LZF compression can be
unmarshalled using LZF decompression just prior to being consumed at the
diff --git a/components/camel-mail/src/main/docs/mail-component.adoc
b/components/camel-mail/src/main/docs/mail-component.adoc
index 1b38a9b..4711e71 100644
--- a/components/camel-mail/src/main/docs/mail-component.adoc
+++ b/components/camel-mail/src/main/docs/mail-component.adoc
@@ -343,7 +343,7 @@ configuration.
=== Using the JSSE Configuration Utility
The mail component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-nagios/src/main/docs/nagios-component.adoc
b/components/camel-nagios/src/main/docs/nagios-component.adoc
index 988d83d..993e376 100644
--- a/components/camel-nagios/src/main/docs/nagios-component.adoc
+++ b/components/camel-nagios/src/main/docs/nagios-component.adoc
@@ -185,5 +185,5 @@ Nagios. For example we can enable this from Java as follows:
In Spring XML its just a matter of defining a Spring bean with the type
`EventNotifier` and Camel will pick it up as documented here:
-xref:latest@manual::advanced-configuration-of-camelcontext-using-spring.adoc[Advanced
+xref:manual::advanced-configuration-of-camelcontext-using-spring.adoc[Advanced
configuration of CamelContext using Spring].
diff --git a/components/camel-netty/src/main/docs/netty-component.adoc
b/components/camel-netty/src/main/docs/netty-component.adoc
index b11344e..baf555c 100644
--- a/components/camel-netty/src/main/docs/netty-component.adoc
+++ b/components/camel-netty/src/main/docs/netty-component.adoc
@@ -396,7 +396,7 @@ RouteBuilder builder = new RouteBuilder() {
Using the JSSE Configuration Utility
The Netty component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-netty4/src/main/docs/netty4-component.adoc
b/components/camel-netty4/src/main/docs/netty4-component.adoc
index 52b5bdc..2b950cf 100644
--- a/components/camel-netty4/src/main/docs/netty4-component.adoc
+++ b/components/camel-netty4/src/main/docs/netty4-component.adoc
@@ -409,7 +409,7 @@ RouteBuilder builder = new RouteBuilder() {
Using the JSSE Configuration Utility
As of Camel 2.9, the Netty component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-paho/src/main/docs/paho-component.adoc
b/components/camel-paho/src/main/docs/paho-component.adoc
index e59d09b..4e6ca85 100644
--- a/components/camel-paho/src/main/docs/paho-component.adoc
+++ b/components/camel-paho/src/main/docs/paho-component.adoc
@@ -176,7 +176,7 @@ byte[] payload = "message".getBytes();
producerTemplate.sendBody("paho:topic", payload);
----
-But of course Camel build-in xref:latest@manual::type-converter.adoc[type
conversion
+But of course Camel build-in xref:manual::type-converter.adoc[type conversion
API] can perform the automatic data type transformations for you. In the
example below Camel automatically converts binary payload into `String`
(and conversely):
diff --git a/components/camel-spring/src/main/docs/spring-summary.adoc
b/components/camel-spring/src/main/docs/spring-summary.adoc
index aa58ffb..105a1aa 100644
--- a/components/camel-spring/src/main/docs/spring-summary.adoc
+++ b/components/camel-spring/src/main/docs/spring-summary.adoc
@@ -95,7 +95,7 @@ inline namespace declaration:
=== Advanced configuration using Spring
See more details at
-xref:latest@manual::advanced-configuration-of-camelcontext-using-spring.adoc[Advanced
+xref:manual::advanced-configuration-of-camelcontext-using-spring.adoc[Advanced
configuration of CamelContext using Spring]
$### Using Java Code
@@ -337,7 +337,7 @@ SpringCamelContext lazily fetching components from the
spring context
for the scheme name you use for Endpoint
URIs.
-For more detail see
xref:latest@manual:faq:how-do-i-configure-endpoints.adoc[Configuring
+For more detail see
xref:manual:faq:how-do-i-configure-endpoints.adoc[Configuring
Endpoints and Components].
== CamelContextAware
@@ -346,7 +346,7 @@ If you want to be injected with the CamelContext
in your POJO just implement the
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContextAware.html[CamelContextAware
interface]; then when Spring creates your POJO the CamelContext will be
-injected into your POJO. Also see the
xref:latest@manual::bean-integration.adoc[Bean
+injected into your POJO. Also see the xref:manual::bean-integration.adoc[Bean
Integration] for further injections.
== Integration Testing
diff --git a/components/camel-test-spring/src/main/docs/test-spring.adoc
b/components/camel-test-spring/src/main/docs/test-spring.adoc
index b909aff..f9316f9 100644
--- a/components/camel-test-spring/src/main/docs/test-spring.adoc
+++ b/components/camel-test-spring/src/main/docs/test-spring.adoc
@@ -14,7 +14,7 @@ Allows to test Camel with Spring applications such as Spring
XML files or Spring
This documentation is old and needs to be updated
====
-xref:latest@manual::testing.adoc[Testing] is a crucial part of any development
or integration work. The Spring Framework offers a number of features that
makes it easy to test while using Spring for Inversion of Control which works
with JUnit 3.x, JUnit 4.x, and http://testng.org[TestNG].
+xref:manual::testing.adoc[Testing] is a crucial part of any development or
integration work. The Spring Framework offers a number of features that makes
it easy to test while using Spring for Inversion of Control which works with
JUnit 3.x, JUnit 4.x, and http://testng.org[TestNG].
We can use Spring for IoC and the Camel xref:ROOT:mock-component.adoc[Mock]
and xref:test.adoc[Test] endpoints to create sophisticated integration/unit
tests that are easy to run and debug inside your IDE. There are three
supported approaches for testing with Spring in Camel.
[width="100%",cols="1,1,4,1",options="header",]
diff --git a/components/camel-undertow/src/main/docs/undertow-component.adoc
b/components/camel-undertow/src/main/docs/undertow-component.adoc
index a1b2d16..0883f9b 100644
--- a/components/camel-undertow/src/main/docs/undertow-component.adoc
+++ b/components/camel-undertow/src/main/docs/undertow-component.adoc
@@ -225,7 +225,7 @@ If you need to expose an Undertow endpoint on all network
interfaces, the
`0.0.0.0` address should be used.
To listen across an entire URI prefix, see
-xref:latest@manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let
Jetty match wildcards].
+xref:manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let Jetty
match wildcards].
If you actually want to expose routes by HTTP and already have a
Servlet, you should instead refer to the
diff --git
a/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
b/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
index 5ad419d..1523498 100644
---
a/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
+++
b/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
@@ -7,7 +7,7 @@
*Since Camel {since}*
-This xref:latest@manual::data-format.adoc[Data
+This xref:manual::data-format.adoc[Data
Format] uses http://www.univocity.com/pages/about-parsers[uniVocity-parsers]
for reading and writing 3 kinds of tabular data text files:
diff --git
a/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
b/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
index efbbe40..1d81e3a 100644
---
a/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
+++
b/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
@@ -7,7 +7,7 @@
*Since Camel {since}*
-This xref:latest@manual::data-format.adoc[Data
+This xref:manual::data-format.adoc[Data
Format] uses http://www.univocity.com/pages/about-parsers[uniVocity-parsers]
for reading and writing 3 kinds of tabular data text files:
diff --git
a/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
b/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
index 1260702..4809359 100644
---
a/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
+++
b/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
@@ -7,7 +7,7 @@
*Since Camel {since}*
-This xref:latest@manual::data-format.adoc[Data
+This xref:manual::data-format.adoc[Data
Format] uses http://www.univocity.com/pages/about-parsers[uniVocity-parsers]
for reading and writing 3 kinds of tabular data text files:
diff --git a/components/camel-websocket/src/main/docs/websocket-component.adoc
b/components/camel-websocket/src/main/docs/websocket-component.adoc
index c50f7699..6b383cf 100644
--- a/components/camel-websocket/src/main/docs/websocket-component.adoc
+++ b/components/camel-websocket/src/main/docs/websocket-component.adoc
@@ -209,7 +209,7 @@ from("activemq:topic:newsTopic")
=== Using the JSSE Configuration Utility
The WebSocket component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git
a/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
b/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
index d8572bb..396b257 100644
--- a/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
+++ b/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
@@ -13,7 +13,7 @@ signatures as described in the W3C standard
http://www.w3.org/TR/xmldsig-core/[XML Signature Syntax and Processing]
or as described in the successor
http://www.w3.org/TR/xmldsig-core1/[version 1.1]. For XML Encryption
-support, please refer to the XML Security
xref:latest@manual::data-format.adoc[Data
+support, please refer to the XML Security xref:manual::data-format.adoc[Data
Format].
You can find an introduction to XML signature
diff --git a/components/camel-zipkin/src/main/docs/zipkin.adoc
b/components/camel-zipkin/src/main/docs/zipkin.adoc
index 8fdec45..c23e126 100644
--- a/components/camel-zipkin/src/main/docs/zipkin.adoc
+++ b/components/camel-zipkin/src/main/docs/zipkin.adoc
@@ -79,14 +79,14 @@ uses the rules from Intercept.
|includeMessageBody |false |Whether to include the Camel message body in the
zipkin traces.
This is not recommended for production usage, or when having big
payloads. You can limit the size by configuring the
-xref:latest@manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
+xref:manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
debug log size].
|includeMessageBodyStreams |false |Whether to include message bodies that are
stream based in the zipkin
traces. This requires enabling streamcaching on the
routes or globally on the CamelContext. This is not recommended for production
usage, or when having big
payloads. You can limit the size by configuring the
-xref:latest@manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
+xref:manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
debug log size].
|===
diff --git a/docs/components/modules/ROOT/pages/ahc-component.adoc
b/docs/components/modules/ROOT/pages/ahc-component.adoc
index 24290ba..2ff15c5 100644
--- a/docs/components/modules/ROOT/pages/ahc-component.adoc
+++ b/docs/components/modules/ROOT/pages/ahc-component.adoc
@@ -431,7 +431,7 @@ from("direct:start")
Using the JSSE Configuration Utility
The AHC component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/docs/components/modules/ROOT/pages/beanstalk-component.adoc
b/docs/components/modules/ROOT/pages/beanstalk-component.adoc
index 546a26b..3a4ac27 100644
--- a/docs/components/modules/ROOT/pages/beanstalk-component.adoc
+++ b/docs/components/modules/ROOT/pages/beanstalk-component.adoc
@@ -54,7 +54,7 @@ beanstalk://localhost:11300/tube1+tube2
Tube name will be URL decoded, so if your tube names include special
characters like + or ?, you need to URL-encode them appropriately, or
-use the RAW syntax, see
xref:latest@manual:faq:how-do-i-configure-endpoints.adoc[more
+use the RAW syntax, see xref:manual:faq:how-do-i-configure-endpoints.adoc[more
details here].
By the way, you cannot specify several tubes when you are writing jobs
diff --git a/docs/components/modules/ROOT/pages/cometd-component.adoc
b/docs/components/modules/ROOT/pages/cometd-component.adoc
index 116cb06..868217b 100644
--- a/docs/components/modules/ROOT/pages/cometd-component.adoc
+++ b/docs/components/modules/ROOT/pages/cometd-component.adoc
@@ -189,7 +189,7 @@
http://cometd.org/documentation/howtos/authentication[documented here]
=== Using the JSSE Configuration Utility
The Cometd component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/docs/components/modules/ROOT/pages/crypto-component.adoc
b/docs/components/modules/ROOT/pages/crypto-component.adoc
index f8e5c61..eff19bf 100644
--- a/docs/components/modules/ROOT/pages/crypto-component.adoc
+++ b/docs/components/modules/ROOT/pages/crypto-component.adoc
@@ -217,7 +217,7 @@ The component supports 33 options, which are listed below.
The most basic way to way to sign and verify an exchange is with a
KeyPair as follows.
-The same can be achieved with the
xref:latest@manual::spring-xml-extensions.adoc[Spring
+The same can be achieved with the
xref:manual::spring-xml-extensions.adoc[Spring
XML Extensions] using references to keys
=== KeyStores and Aliases.
diff --git a/docs/components/modules/ROOT/pages/grape-component.adoc
b/docs/components/modules/ROOT/pages/grape-component.adoc
index 55b189e..3c34b2d 100644
--- a/docs/components/modules/ROOT/pages/grape-component.adoc
+++ b/docs/components/modules/ROOT/pages/grape-component.adoc
@@ -137,7 +137,7 @@ By default Camel Grape component operates on the String
payloads:
producerTemplate.sendBody("grape:defaultMavenCoordinates",
"org.apache.camel/camel-ftp/2.15.2");
------------------------------------------------------------------------------------------------
-But of course Camel build-in xref:latest@manual::type-converter.adoc[type
conversion
+But of course Camel build-in xref:manual::type-converter.adoc[type conversion
API] can perform the automatic data type transformations for you. In the
example below Camel automatically converts binary payload into the
String:
diff --git a/docs/components/modules/ROOT/pages/http-component.adoc
b/docs/components/modules/ROOT/pages/http-component.adoc
index e14c690..269844f 100644
--- a/docs/components/modules/ROOT/pages/http-component.adoc
+++ b/docs/components/modules/ROOT/pages/http-component.adoc
@@ -544,7 +544,7 @@ behavior.
Using the JSSE Configuration Utility
The HTTP component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/docs/components/modules/ROOT/pages/http4-component.adoc
b/docs/components/modules/ROOT/pages/http4-component.adoc
index bf56a85..0055393 100644
--- a/docs/components/modules/ROOT/pages/http4-component.adoc
+++ b/docs/components/modules/ROOT/pages/http4-component.adoc
@@ -590,7 +590,7 @@ behavior.
Using the JSSE Configuration Utility
As of Camel 2.8, the HTTP4 component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/docs/components/modules/ROOT/pages/irc-component.adoc
b/docs/components/modules/ROOT/pages/irc-component.adoc
index 1f8ca05..f5334aa 100644
--- a/docs/components/modules/ROOT/pages/irc-component.adoc
+++ b/docs/components/modules/ROOT/pages/irc-component.adoc
@@ -153,7 +153,7 @@ The component supports 3 options, which are listed below.
=== Using the JSSE Configuration Utility
The IRC component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/docs/components/modules/ROOT/pages/jetty-component.adoc
b/docs/components/modules/ROOT/pages/jetty-component.adoc
index 3dbc479..50ad8cc 100644
--- a/docs/components/modules/ROOT/pages/jetty-component.adoc
+++ b/docs/components/modules/ROOT/pages/jetty-component.adoc
@@ -322,7 +322,7 @@ If you need to expose a Jetty endpoint on all network
interfaces, the
`0.0.0.0` address should be used.
To listen across an entire URI prefix, see
-xref:latest@manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let
Jetty match
+xref:manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let Jetty
match
wildcards].
If you actually want to expose routes by HTTP and already have a
@@ -388,7 +388,7 @@ public void process(Exchange exchange) throws Exception {
Using the JSSE Configuration Utility
As of Camel 2.8, the Jetty component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/docs/components/modules/ROOT/pages/jms-component.adoc
b/docs/components/modules/ROOT/pages/jms-component.adoc
index d0738b0..b198349 100644
--- a/docs/components/modules/ROOT/pages/jms-component.adoc
+++ b/docs/components/modules/ROOT/pages/jms-component.adoc
@@ -665,7 +665,7 @@ from("file://orders").
=== Using Annotations
-Camel also has annotations so you can use
xref:latest@manual::pojo-consuming.adoc[POJO
+Camel also has annotations so you can use xref:manual::pojo-consuming.adoc[POJO
Consuming] and POJO Producing.
=== Spring DSL sample
diff --git a/docs/components/modules/ROOT/pages/jpa-component.adoc
b/docs/components/modules/ROOT/pages/jpa-component.adoc
index 5af5d09..8bf84f3 100644
--- a/docs/components/modules/ROOT/pages/jpa-component.adoc
+++ b/docs/components/modules/ROOT/pages/jpa-component.adoc
@@ -89,7 +89,7 @@ jpa:entityClassName[?options]
-----------------------------
For sending to the endpoint, the _entityClassName_ is optional. If
-specified, it helps the xref:latest@manual::type-converter.adoc[Type
Converter] to
+specified, it helps the xref:manual::type-converter.adoc[Type Converter] to
ensure the body is of the correct type.
For consuming, the _entityClassName_ is mandatory.
diff --git a/docs/components/modules/ROOT/pages/mail-component.adoc
b/docs/components/modules/ROOT/pages/mail-component.adoc
index 6449eaa..14207fc 100644
--- a/docs/components/modules/ROOT/pages/mail-component.adoc
+++ b/docs/components/modules/ROOT/pages/mail-component.adoc
@@ -345,7 +345,7 @@ configuration.
=== Using the JSSE Configuration Utility
The mail component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/docs/components/modules/ROOT/pages/nagios-component.adoc
b/docs/components/modules/ROOT/pages/nagios-component.adoc
index 55e7ad0..c51c0df 100644
--- a/docs/components/modules/ROOT/pages/nagios-component.adoc
+++ b/docs/components/modules/ROOT/pages/nagios-component.adoc
@@ -187,5 +187,5 @@ Nagios. For example we can enable this from Java as follows:
In Spring XML its just a matter of defining a Spring bean with the type
`EventNotifier` and Camel will pick it up as documented here:
-xref:latest@manual::advanced-configuration-of-camelcontext-using-spring.adoc[Advanced
+xref:manual::advanced-configuration-of-camelcontext-using-spring.adoc[Advanced
configuration of CamelContext using Spring].
diff --git a/docs/components/modules/ROOT/pages/netty-component.adoc
b/docs/components/modules/ROOT/pages/netty-component.adoc
index 2f9b3e6..950d856 100644
--- a/docs/components/modules/ROOT/pages/netty-component.adoc
+++ b/docs/components/modules/ROOT/pages/netty-component.adoc
@@ -398,7 +398,7 @@ RouteBuilder builder = new RouteBuilder() {
Using the JSSE Configuration Utility
The Netty component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/docs/components/modules/ROOT/pages/netty4-component.adoc
b/docs/components/modules/ROOT/pages/netty4-component.adoc
index a6b23a5..fa65e14 100644
--- a/docs/components/modules/ROOT/pages/netty4-component.adoc
+++ b/docs/components/modules/ROOT/pages/netty4-component.adoc
@@ -411,7 +411,7 @@ RouteBuilder builder = new RouteBuilder() {
Using the JSSE Configuration Utility
As of Camel 2.9, the Netty component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/docs/components/modules/ROOT/pages/paho-component.adoc
b/docs/components/modules/ROOT/pages/paho-component.adoc
index 890e3b2..c89d008 100644
--- a/docs/components/modules/ROOT/pages/paho-component.adoc
+++ b/docs/components/modules/ROOT/pages/paho-component.adoc
@@ -178,7 +178,7 @@ byte[] payload = "message".getBytes();
producerTemplate.sendBody("paho:topic", payload);
----
-But of course Camel build-in xref:latest@manual::type-converter.adoc[type
conversion
+But of course Camel build-in xref:manual::type-converter.adoc[type conversion
API] can perform the automatic data type transformations for you. In the
example below Camel automatically converts binary payload into `String`
(and conversely):
diff --git a/docs/components/modules/ROOT/pages/spring-summary.adoc
b/docs/components/modules/ROOT/pages/spring-summary.adoc
index c570f7d..48ec13d 100644
--- a/docs/components/modules/ROOT/pages/spring-summary.adoc
+++ b/docs/components/modules/ROOT/pages/spring-summary.adoc
@@ -97,7 +97,7 @@ inline namespace declaration:
=== Advanced configuration using Spring
See more details at
-xref:latest@manual::advanced-configuration-of-camelcontext-using-spring.adoc[Advanced
+xref:manual::advanced-configuration-of-camelcontext-using-spring.adoc[Advanced
configuration of CamelContext using Spring]
$### Using Java Code
@@ -339,7 +339,7 @@ SpringCamelContext lazily fetching components from the
spring context
for the scheme name you use for Endpoint
URIs.
-For more detail see
xref:latest@manual:faq:how-do-i-configure-endpoints.adoc[Configuring
+For more detail see
xref:manual:faq:how-do-i-configure-endpoints.adoc[Configuring
Endpoints and Components].
== CamelContextAware
@@ -348,7 +348,7 @@ If you want to be injected with the CamelContext
in your POJO just implement the
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContextAware.html[CamelContextAware
interface]; then when Spring creates your POJO the CamelContext will be
-injected into your POJO. Also see the
xref:latest@manual::bean-integration.adoc[Bean
+injected into your POJO. Also see the xref:manual::bean-integration.adoc[Bean
Integration] for further injections.
== Integration Testing
diff --git a/docs/components/modules/ROOT/pages/undertow-component.adoc
b/docs/components/modules/ROOT/pages/undertow-component.adoc
index 2f6164c..52e88fa 100644
--- a/docs/components/modules/ROOT/pages/undertow-component.adoc
+++ b/docs/components/modules/ROOT/pages/undertow-component.adoc
@@ -227,7 +227,7 @@ If you need to expose an Undertow endpoint on all network
interfaces, the
`0.0.0.0` address should be used.
To listen across an entire URI prefix, see
-xref:latest@manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let
Jetty match wildcards].
+xref:manual:faq:how-do-i-let-jetty-match-wildcards.adoc[How do I let Jetty
match wildcards].
If you actually want to expose routes by HTTP and already have a
Servlet, you should instead refer to the
diff --git a/docs/components/modules/ROOT/pages/websocket-component.adoc
b/docs/components/modules/ROOT/pages/websocket-component.adoc
index f8d08b4..ad3f175 100644
--- a/docs/components/modules/ROOT/pages/websocket-component.adoc
+++ b/docs/components/modules/ROOT/pages/websocket-component.adoc
@@ -211,7 +211,7 @@ from("activemq:topic:newsTopic")
=== Using the JSSE Configuration Utility
The WebSocket component supports SSL/TLS configuration
-through the xref:latest@manual::camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/docs/components/modules/ROOT/pages/xmlsecurity-component.adoc
b/docs/components/modules/ROOT/pages/xmlsecurity-component.adoc
index 4597f9a..02d8298f 100644
--- a/docs/components/modules/ROOT/pages/xmlsecurity-component.adoc
+++ b/docs/components/modules/ROOT/pages/xmlsecurity-component.adoc
@@ -15,7 +15,7 @@ signatures as described in the W3C standard
http://www.w3.org/TR/xmldsig-core/[XML Signature Syntax and Processing]
or as described in the successor
http://www.w3.org/TR/xmldsig-core1/[version 1.1]. For XML Encryption
-support, please refer to the XML Security
xref:latest@manual::data-format.adoc[Data
+support, please refer to the XML Security xref:manual::data-format.adoc[Data
Format].
You can find an introduction to XML signature
diff --git a/docs/components/modules/dataformats/pages/lzf-dataformat.adoc
b/docs/components/modules/dataformats/pages/lzf-dataformat.adoc
index 151c9ee..a1ecbbf 100644
--- a/docs/components/modules/dataformats/pages/lzf-dataformat.adoc
+++ b/docs/components/modules/dataformats/pages/lzf-dataformat.adoc
@@ -11,7 +11,7 @@
The
-LZF xref:latest@manual::data-format.adoc[Data Format] is a message compression
+LZF xref:manual::data-format.adoc[Data Format] is a message compression
and de-compression format. It uses the
LZF deflate algorithm. Messages marshalled using LZF compression can be
unmarshalled using LZF decompression just prior to being consumed at the
diff --git
a/docs/components/modules/dataformats/pages/univocity-csv-dataformat.adoc
b/docs/components/modules/dataformats/pages/univocity-csv-dataformat.adoc
index e58ff30..73d657b 100644
--- a/docs/components/modules/dataformats/pages/univocity-csv-dataformat.adoc
+++ b/docs/components/modules/dataformats/pages/univocity-csv-dataformat.adoc
@@ -9,7 +9,7 @@
*Since Camel {since}*
-This xref:latest@manual::data-format.adoc[Data
+This xref:manual::data-format.adoc[Data
Format] uses http://www.univocity.com/pages/about-parsers[uniVocity-parsers]
for reading and writing 3 kinds of tabular data text files:
diff --git
a/docs/components/modules/dataformats/pages/univocity-fixed-dataformat.adoc
b/docs/components/modules/dataformats/pages/univocity-fixed-dataformat.adoc
index e7e4016..5107b32 100644
--- a/docs/components/modules/dataformats/pages/univocity-fixed-dataformat.adoc
+++ b/docs/components/modules/dataformats/pages/univocity-fixed-dataformat.adoc
@@ -9,7 +9,7 @@
*Since Camel {since}*
-This xref:latest@manual::data-format.adoc[Data
+This xref:manual::data-format.adoc[Data
Format] uses http://www.univocity.com/pages/about-parsers[uniVocity-parsers]
for reading and writing 3 kinds of tabular data text files:
diff --git
a/docs/components/modules/dataformats/pages/univocity-tsv-dataformat.adoc
b/docs/components/modules/dataformats/pages/univocity-tsv-dataformat.adoc
index 537bc87..ac992a9 100644
--- a/docs/components/modules/dataformats/pages/univocity-tsv-dataformat.adoc
+++ b/docs/components/modules/dataformats/pages/univocity-tsv-dataformat.adoc
@@ -9,7 +9,7 @@
*Since Camel {since}*
-This xref:latest@manual::data-format.adoc[Data
+This xref:manual::data-format.adoc[Data
Format] uses http://www.univocity.com/pages/about-parsers[uniVocity-parsers]
for reading and writing 3 kinds of tabular data text files:
diff --git a/docs/components/modules/others/pages/cdi.adoc
b/docs/components/modules/others/pages/cdi.adoc
index 231e07c..1a1bc76 100644
--- a/docs/components/modules/others/pages/cdi.adoc
+++ b/docs/components/modules/others/pages/cdi.adoc
@@ -843,7 +843,7 @@ MockEndpoint outbound = endpoints
== Maven Archetype
-Among the available xref:latest@manual::camel-maven-archetypes.adoc[Camel Maven
+Among the available xref:manual::camel-maven-archetypes.adoc[Camel Maven
archetypes], you can use the provided `camel-archetype-cdi` to generate
a Camel CDI Maven project, e.g.:
diff --git a/docs/components/modules/others/pages/test-spring.adoc
b/docs/components/modules/others/pages/test-spring.adoc
index 372b328..bab87a1 100644
--- a/docs/components/modules/others/pages/test-spring.adoc
+++ b/docs/components/modules/others/pages/test-spring.adoc
@@ -16,7 +16,7 @@ Allows to test Camel with Spring applications such as Spring
XML files or Spring
This documentation is old and needs to be updated
====
-xref:latest@manual::testing.adoc[Testing] is a crucial part of any development
or integration work. The Spring Framework offers a number of features that
makes it easy to test while using Spring for Inversion of Control which works
with JUnit 3.x, JUnit 4.x, and http://testng.org[TestNG].
+xref:manual::testing.adoc[Testing] is a crucial part of any development or
integration work. The Spring Framework offers a number of features that makes
it easy to test while using Spring for Inversion of Control which works with
JUnit 3.x, JUnit 4.x, and http://testng.org[TestNG].
We can use Spring for IoC and the Camel xref:ROOT:mock-component.adoc[Mock]
and xref:test.adoc[Test] endpoints to create sophisticated integration/unit
tests that are easy to run and debug inside your IDE. There are three
supported approaches for testing with Spring in Camel.
[width="100%",cols="1,1,4,1",options="header",]
diff --git a/docs/components/modules/others/pages/zipkin.adoc
b/docs/components/modules/others/pages/zipkin.adoc
index 966997f..085515d 100644
--- a/docs/components/modules/others/pages/zipkin.adoc
+++ b/docs/components/modules/others/pages/zipkin.adoc
@@ -81,14 +81,14 @@ uses the rules from Intercept.
|includeMessageBody |false |Whether to include the Camel message body in the
zipkin traces.
This is not recommended for production usage, or when having big
payloads. You can limit the size by configuring the
-xref:latest@manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
+xref:manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
debug log size].
|includeMessageBodyStreams |false |Whether to include message bodies that are
stream based in the zipkin
traces. This requires enabling streamcaching on the
routes or globally on the CamelContext. This is not recommended for production
usage, or when having big
payloads. You can limit the size by configuring the
-xref:latest@manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
+xref:manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
debug log size].
|===
