This is an automated email from the ASF dual-hosted git repository.
djencks pushed a commit to branch camel-3.0.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-3.0.x by this push:
new 11003db Aggregate eip content - xref fixes.
new 33dc65f Merge pull request #3660 from
djencks/camel-3.0.x-issue-14747-aggregate-eip-task-14755
11003db is described below
commit 11003db9471e58eed16ad9fe1a3c9511ac568165
Author: David Jencks <djen...@apache.org>
AuthorDate: Fri Mar 20 09:44:23 2020 -0700
Aggregate eip content - xref fixes.
---
components/camel-azure/src/main/docs/azure-blob-component.adoc | 2 +-
components/camel-bean/src/main/docs/bean-language.adoc | 6 +++---
components/camel-beanstalk/src/main/docs/beanstalk-component.adoc | 2 +-
components/camel-dataset/src/main/docs/dataset-component.adoc | 2 +-
components/camel-dataset/src/main/docs/dataset-test-component.adoc | 2 +-
.../src/main/docs/debezium-mongodb-component.adoc | 2 +-
.../src/main/docs/debezium-mysql-component.adoc | 2 +-
.../src/main/docs/debezium-postgres-component.adoc | 2 +-
.../src/main/docs/debezium-sqlserver-component.adoc | 2 +-
components/camel-disruptor/src/main/docs/disruptor-component.adoc | 2 +-
.../src/main/docs/elasticsearch-rest-component.adoc | 2 +-
components/camel-facebook/src/main/docs/facebook-component.adoc | 2 +-
components/camel-groovy/src/main/docs/groovy-language.adoc | 2 +-
components/camel-jms/src/main/docs/jms-component.adoc | 4 ++--
components/camel-language/src/main/docs/language-component.adoc | 2 +-
components/camel-mock/src/main/docs/mock-component.adoc | 2 +-
components/camel-mvel/src/main/docs/mvel-language.adoc | 2 +-
components/camel-ognl/src/main/docs/ognl-language.adoc | 2 +-
components/camel-quartz/src/main/docs/quartz-component.adoc | 2 +-
components/camel-saxon/src/main/docs/xquery-component.adoc | 2 +-
components/camel-saxon/src/main/docs/xquery-language.adoc | 2 +-
components/camel-spring/src/main/docs/spel-language.adoc | 4 ++--
components/camel-spring/src/main/docs/spring-event-component.adoc | 4 ++--
components/camel-spring/src/main/docs/spring.adoc | 2 +-
components/camel-xpath/src/main/docs/xpath-language.adoc | 2 +-
docs/components/modules/ROOT/pages/azure-blob-component.adoc | 2 +-
docs/components/modules/ROOT/pages/bean-language.adoc | 6 +++---
docs/components/modules/ROOT/pages/beanstalk-component.adoc | 2 +-
docs/components/modules/ROOT/pages/dataset-component.adoc | 2 +-
docs/components/modules/ROOT/pages/dataset-test-component.adoc | 2 +-
docs/components/modules/ROOT/pages/debezium-mongodb-component.adoc | 2 +-
docs/components/modules/ROOT/pages/debezium-mysql-component.adoc | 2 +-
docs/components/modules/ROOT/pages/debezium-postgres-component.adoc | 2 +-
.../components/modules/ROOT/pages/debezium-sqlserver-component.adoc | 2 +-
docs/components/modules/ROOT/pages/disruptor-component.adoc | 2 +-
.../components/modules/ROOT/pages/elasticsearch-rest-component.adoc | 2 +-
docs/components/modules/ROOT/pages/facebook-component.adoc | 2 +-
docs/components/modules/ROOT/pages/groovy-language.adoc | 2 +-
docs/components/modules/ROOT/pages/jms-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/language-component.adoc | 2 +-
docs/components/modules/ROOT/pages/mock-component.adoc | 2 +-
docs/components/modules/ROOT/pages/mvel-language.adoc | 2 +-
docs/components/modules/ROOT/pages/ognl-language.adoc | 2 +-
docs/components/modules/ROOT/pages/quartz-component.adoc | 2 +-
docs/components/modules/ROOT/pages/spel-language.adoc | 4 ++--
docs/components/modules/ROOT/pages/spring-event-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/spring.adoc | 2 +-
docs/components/modules/ROOT/pages/xpath-language.adoc | 2 +-
docs/components/modules/ROOT/pages/xquery-component.adoc | 2 +-
docs/components/modules/ROOT/pages/xquery-language.adoc | 2 +-
50 files changed, 60 insertions(+), 60 deletions(-)
diff --git a/components/camel-azure/src/main/docs/azure-blob-component.adoc
b/components/camel-azure/src/main/docs/azure-blob-component.adoc
index 1861171..15db917 100644
--- a/components/camel-azure/src/main/docs/azure-blob-component.adoc
+++ b/components/camel-azure/src/main/docs/azure-blob-component.adoc
@@ -277,4 +277,4 @@ Maven users will need to add the following dependency to
their `pom.xml`.
</dependency>
----
-where `${camel-version}` must be replaced by the actual version of Camel.
+where `+++${camel-version}+++` must be replaced by the actual version of Camel.
diff --git a/components/camel-bean/src/main/docs/bean-language.adoc
b/components/camel-bean/src/main/docs/bean-language.adoc
index c18101c..02cea5d 100644
--- a/components/camel-bean/src/main/docs/bean-language.adoc
+++ b/components/camel-bean/src/main/docs/bean-language.adoc
@@ -14,7 +14,7 @@ using the type of the message body and using any annotations
on the bean
methods.
The xref:latest@manual::bean-binding.adoc[Bean Binding] rules are used to bind
the
-xref:latest@manual::message.adoc[Message] Exchange to the method parameters;
so you can
+xref:{eip-vc}:eips:message.adoc[Message] Exchange to the method parameters; so
you can
annotate the bean to extract headers or other expressions such as
xref:xpath-language.adoc[XPath] or xref:xquery-language.adoc[XQuery] from the
message.
@@ -138,7 +138,7 @@ public boolean isGoldCustomer(@Header(name = "foo") Integer
fooHeader) {...}
----
So you can bind parameters of the method to the Exchange, the
-xref:latest@manual::message.adoc[Message] or individual headers, properties,
the body
+xref:{eip-vc}:eips:message.adoc[Message] or individual headers, properties,
the body
or other expressions.
[[BeanLanguage-Non-RegistryBeans]]
@@ -209,5 +209,5 @@ We have some test cases you can look at if it'll help
is a JUnit test case showing the Java xref:latest@manual::dsl.adoc[DSL] use of
the bean
expression being used in a filter
*
https://github.com/apache/camel/blob/master/components/camel-spring/src/test/resources/org/apache/camel/spring/processor/aggregator.xml[aggregator.xml]
-is a Spring XML test case for the
xref:latest@manual:eips:aggregate-eip.adoc[Aggregator] which
+is a Spring XML test case for the
xref:{eip-vc}:eips:aggregate-eip.adoc[Aggregator] which
uses a bean method call to test for the completion of the aggregation.
diff --git a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
index 1a0e121..993b8bf 100644
--- a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
+++ b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
@@ -190,7 +190,7 @@ Be careful when specifying `release`, as the failed job
will immediately
become available in the same tube and your consumer will try to acquire
it again. You can `release` and specify _jobDelay_ though.
-The beanstalk consumer is a Scheduled
xref:latest@manual::polling-consumer.adoc[Polling
+The beanstalk consumer is a Scheduled
xref:{eip-vc}:eips:polling-consumer.adoc[Polling
Consumer] which means there is more options you can configure, such as
how frequent the consumer should poll. For more details
see Polling Consumer.
diff --git a/components/camel-dataset/src/main/docs/dataset-component.adoc
b/components/camel-dataset/src/main/docs/dataset-component.adoc
index 3a2030a..5c6e8db 100644
--- a/components/camel-dataset/src/main/docs/dataset-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-component.adoc
@@ -12,7 +12,7 @@ notoriously difficult. The xref:mock-component.adoc[Mock],
xref:mock-component.a
and xref:dataset-component.adoc[DataSet] endpoints work great with the
Camel Testing Framework to simplify your unit and
integration testing using
-xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration
+xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's large range of Components
together with the powerful Bean Integration.
diff --git a/components/camel-dataset/src/main/docs/dataset-test-component.adoc
b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
index c5ef7bd..d8dac9a 100644
--- a/components/camel-dataset/src/main/docs/dataset-test-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
@@ -12,7 +12,7 @@ notoriously difficult. The xref:mock-component.adoc[Mock],
xref:mock-component.a
and xref:dataset-component.adoc[DataSet] endpoints work great with the
Camel Testing Framework to simplify your unit and
integration testing using
-xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration
+xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's large range of Components
together with the powerful Bean Integration.
diff --git
a/components/camel-debezium-mongodb/src/main/docs/debezium-mongodb-component.adoc
b/components/camel-debezium-mongodb/src/main/docs/debezium-mongodb-component.adoc
index 085357a..d85a58d 100644
---
a/components/camel-debezium-mongodb/src/main/docs/debezium-mongodb-component.adoc
+++
b/components/camel-debezium-mongodb/src/main/docs/debezium-mongodb-component.adoc
@@ -209,7 +209,7 @@ The following headers are available when consuming change
events from Debezium.
[width="100%",cols="2m,2m,1m,5",options="header"]
|===
| Header constant | Header value
| Type | Description
-| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "{server-name}.{database-name}.{table-name}".
+| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "+++{server-name}.{database-name}.{table-name}+++".
| DebeziumConstants.HEADER_KEY | "CamelDebeziumKey"
| Struct | The key of the event, normally is the table
Primary Key.
| DebeziumConstants.HEADER_SOURCE_METADATA | "CamelDebeziumSourceMetadata"
| Map | The metadata about the source event, for example
`table` name, database `name`, log position, etc, please refer to the Debezium
documentation for more info.
| DebeziumConstants.HEADER_OPERATION | "CamelDebeziumOperation"
| String | If presents, the type of event operation. Values
for the connector are `c` for create (or insert), `u` for update, `d` for
delete or `r` for read (in the case of a initial sync).
diff --git
a/components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
b/components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
index 8abe1db..d3842f7 100644
---
a/components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
+++
b/components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
@@ -276,7 +276,7 @@ The following headers are available when consuming change
events from Debezium.
[width="100%",cols="2m,2m,1m,5",options="header"]
|===
| Header constant | Header value
| Type | Description
-| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "{server-name}.{database-name}.{table-name}".
+| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "+++{server-name}.{database-name}.{table-name}+++".
| DebeziumConstants.HEADER_KEY | "CamelDebeziumKey"
| Struct | The key of the event, normally is the table
Primary Key.
| DebeziumConstants.HEADER_SOURCE_METADATA | "CamelDebeziumSourceMetadata"
| Map | The metadata about the source event, for example
`table` name, database `name`, log position, etc, please refer to the Debezium
documentation for more info.
| DebeziumConstants.HEADER_OPERATION | "CamelDebeziumOperation"
| String | If presents, the type of event operation. Values
for the connector are `c` for create (or insert), `u` for update, `d` for
delete or `r` in case of a snapshot event.
diff --git
a/components/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
b/components/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
index dba358e..45b5ad4 100644
---
a/components/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
+++
b/components/camel-debezium-postgres/src/main/docs/debezium-postgres-component.adoc
@@ -249,7 +249,7 @@ The following headers are available when consuming change
events from Debezium.
[width="100%",cols="2m,2m,1m,5",options="header"]
|===
| Header constant | Header value
| Type | Description
-| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "{server-name}.{database-name}.{table-name}".
+| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "+++{server-name}.{database-name}.{table-name}+++".
| DebeziumConstants.HEADER_KEY | "CamelDebeziumKey"
| Struct | The key of the event, normally is the table
Primary Key.
| DebeziumConstants.HEADER_SOURCE_METADATA | "CamelDebeziumSourceMetadata"
| Map | The metadata about the source event, for example
`table` name, database `name`, log position, etc, please refer to the Debezium
documentation for more info.
| DebeziumConstants.HEADER_OPERATION | "CamelDebeziumOperation"
| String | If presents, the type of event operation. Values
for the connector are `c` for create (or insert), `u` for update, `d` for
delete or `r` in case of a snapshot event.
diff --git
a/components/camel-debezium-sqlserver/src/main/docs/debezium-sqlserver-component.adoc
b/components/camel-debezium-sqlserver/src/main/docs/debezium-sqlserver-component.adoc
index a69561c..f72eda2 100644
---
a/components/camel-debezium-sqlserver/src/main/docs/debezium-sqlserver-component.adoc
+++
b/components/camel-debezium-sqlserver/src/main/docs/debezium-sqlserver-component.adoc
@@ -210,7 +210,7 @@ The following headers are available when consuming change
events from Debezium.
[width="100%",cols="2m,2m,1m,5",options="header"]
|===
| Header constant | Header value
| Type | Description
-| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "{server-name}.{database-name}.{table-name}".
+| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "+++{server-name}.{database-name}.{table-name}+++".
| DebeziumConstants.HEADER_KEY | "CamelDebeziumKey"
| Struct | The key of the event, normally is the table
Primary Key.
| DebeziumConstants.HEADER_SOURCE_METADATA | "CamelDebeziumSourceMetadata"
| Map | The metadata about the source event, for example
`table` name, database `name`, log position, etc, please refer to the Debezium
documentation for more info.
| DebeziumConstants.HEADER_OPERATION | "CamelDebeziumOperation"
| String | If presents, the type of event operation. Values
for the connector are `c` for create (or insert), `u` for update, `d` for
delete or `r` in case of a snapshot event.
diff --git a/components/camel-disruptor/src/main/docs/disruptor-component.adoc
b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
index 7424534..cefddd2 100644
--- a/components/camel-disruptor/src/main/docs/disruptor-component.adoc
+++ b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
@@ -244,7 +244,7 @@ without incurring significant latency spikes.
== Use of Request Reply
-The Disruptor component supports using
xref:latest@manual:eips:requestReply-eip.adoc[Request
+The Disruptor component supports using
xref:{eip-vc}:eips:requestReply-eip.adoc[Request
Reply], where the caller will wait for the Async route to complete. For
instance:
diff --git
a/components/camel-elasticsearch-rest/src/main/docs/elasticsearch-rest-component.adoc
b/components/camel-elasticsearch-rest/src/main/docs/elasticsearch-rest-component.adoc
index 7d7bd1c..3c778bd 100644
---
a/components/camel-elasticsearch-rest/src/main/docs/elasticsearch-rest-component.adoc
+++
b/components/camel-elasticsearch-rest/src/main/docs/elasticsearch-rest-component.adoc
@@ -314,7 +314,7 @@ try (ElasticsearchScrollRequestIterator response =
template.requestBody("direct:
}
----
-xref:latest@manual:eips:split-eip.adoc[Split EIP] can also be used.
+xref:{eip-vc}:eips:split-eip.adoc[Split EIP] can also be used.
[source,java]
----
diff --git a/components/camel-facebook/src/main/docs/facebook-component.adoc
b/components/camel-facebook/src/main/docs/facebook-component.adoc
index 02a1ae0..da28b69 100644
--- a/components/camel-facebook/src/main/docs/facebook-component.adoc
+++ b/components/camel-facebook/src/main/docs/facebook-component.adoc
@@ -353,7 +353,7 @@ facebook4j.PostUpdate body.
.to("facebook://postFeed/inBody=postUpdate);
----------------------------------------------------
-To poll, every 5 sec (You can set the
xref:latest@manual::polling-consumer.adoc[polling
+To poll, every 5 sec (You can set the
xref:{eip-vc}:eips:polling-consumer.adoc[polling
consumer] options by adding a prefix of "consumer"), all statuses on
your home feed:
diff --git a/components/camel-groovy/src/main/docs/groovy-language.adoc
b/components/camel-groovy/src/main/docs/groovy-language.adoc
index 6511dab..99e8e5e 100644
--- a/components/camel-groovy/src/main/docs/groovy-language.adoc
+++ b/components/camel-groovy/src/main/docs/groovy-language.adoc
@@ -17,7 +17,7 @@ To use a Groovy expression use the following Java code
---------------------------------------
For example you could use the *groovy* function to create an
-Predicate in a xref:latest@manual:eips:filter-eip.adoc[Message Filter] or as
an Expression for a
+Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message Filter] or as an
Expression for a
Recipient List
== Groovy Options
diff --git a/components/camel-jms/src/main/docs/jms-component.adoc
b/components/camel-jms/src/main/docs/jms-component.adoc
index 381d93a..de99464 100644
--- a/components/camel-jms/src/main/docs/jms-component.adoc
+++ b/components/camel-jms/src/main/docs/jms-component.adoc
@@ -599,7 +599,7 @@ the documentation.
Normally, when using xref:jms-component.adoc[JMS] as the transport, it only
transfers the body and headers as the payload. If you want to use
-xref:jms-component.adoc[JMS] with a
xref:latest@manual::dead-letter-channel.adoc[Dead Letter
+xref:jms-component.adoc[JMS] with a
xref:{eip-vc}:eips:dead-letter-channel.adoc[Dead Letter
Channel], using a JMS queue as the Dead Letter Queue, then normally the
caused Exception is not stored in the JMS message. You can, however, use
the `transferExchange` option on the JMS dead letter queue to instruct
@@ -1306,7 +1306,7 @@ Transactions and [Request Reply] over JMS
When using Request Reply over JMS you cannot
use a single transaction; JMS will not send any messages until a commit
is performed, so the server side won't receive anything at all until the
-transaction commits. Therefore to use
xref:latest@manual:eips:requestReply-eip.adoc[Request
+transaction commits. Therefore to use
xref:{eip-vc}:eips:requestReply-eip.adoc[Request
Reply] you must commit a transaction after sending the request and then
use a separate transaction for receiving the response.
diff --git a/components/camel-language/src/main/docs/language-component.adoc
b/components/camel-language/src/main/docs/language-component.adoc
index 24cba5a..229b58e 100644
--- a/components/camel-language/src/main/docs/language-component.adoc
+++ b/components/camel-language/src/main/docs/language-component.adoc
@@ -12,7 +12,7 @@ to an endpoint which executes a script by any of the supported
Languages in Camel. +
By having a component to execute language scripts, it allows more
dynamic routing capabilities. For example by using the
-Routing Slip or xref:latest@manual:eips:dynamic-router.adoc[Dynamic
+Routing Slip or xref:{eip-vc}:eips:dynamic-router.adoc[Dynamic
Router] EIPs you can send messages to `language` endpoints where the
script is dynamic defined as well.
diff --git a/components/camel-mock/src/main/docs/mock-component.adoc
b/components/camel-mock/src/main/docs/mock-component.adoc
index 6e2eda9..17f8158 100644
--- a/components/camel-mock/src/main/docs/mock-component.adoc
+++ b/components/camel-mock/src/main/docs/mock-component.adoc
@@ -12,7 +12,7 @@ notoriously difficult. The xref:mock-component.adoc[Mock],
xref:mock-component.a
and xref:dataset-component.adoc[DataSet] endpoints work great with the
Camel Testing Framework to simplify your unit and
integration testing using
-xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration
+xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's large range of Components
together with the powerful Bean Integration.
diff --git a/components/camel-mvel/src/main/docs/mvel-language.adoc
b/components/camel-mvel/src/main/docs/mvel-language.adoc
index 04ec28a..cab40b3 100644
--- a/components/camel-mvel/src/main/docs/mvel-language.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-language.adoc
@@ -98,7 +98,7 @@ The component supports 6 options, which are listed below.
== Samples
-For example you could use Mvel inside a
xref:latest@manual:eips:filter-eip.adoc[Message
+For example you could use Mvel inside a
xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter] in XML
[source,java]
diff --git a/components/camel-ognl/src/main/docs/ognl-language.adoc
b/components/camel-ognl/src/main/docs/ognl-language.adoc
index e367f89..94a45db 100644
--- a/components/camel-ognl/src/main/docs/ognl-language.adoc
+++ b/components/camel-ognl/src/main/docs/ognl-language.adoc
@@ -98,7 +98,7 @@ The component supports 2 options, which are listed below.
== Samples
-For example you could use OGNL inside a
xref:latest@manual:eips:filter-eip.adoc[Message
+For example you could use OGNL inside a
xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter] in XML
[source,java]
diff --git a/components/camel-quartz/src/main/docs/quartz-component.adoc
b/components/camel-quartz/src/main/docs/quartz-component.adoc
index a0c2c29..55fc0f2 100644
--- a/components/camel-quartz/src/main/docs/quartz-component.adoc
+++ b/components/camel-quartz/src/main/docs/quartz-component.adoc
@@ -411,7 +411,7 @@ but it does not want to be fired now.
The xref:quartz-component.adoc[Quartz] component provides a
Polling Consumer scheduler which allows to
-use cron based scheduling for xref:latest@manual::polling-consumer.adoc[Polling
+use cron based scheduling for xref:{eip-vc}:eips:polling-consumer.adoc[Polling
Consumer] such as the File and FTP
consumers.
diff --git a/components/camel-saxon/src/main/docs/xquery-component.adoc
b/components/camel-saxon/src/main/docs/xquery-component.adoc
index b2fc168..36f7d46 100644
--- a/components/camel-saxon/src/main/docs/xquery-component.adoc
+++ b/components/camel-saxon/src/main/docs/xquery-component.adoc
@@ -11,7 +11,7 @@ Camel supports http://www.w3.org/TR/xquery/[XQuery] to allow
an
Expression or Predicate to be
used in the DSL or xref:latest@manual::xml-configuration.adoc[Xml
Configuration]. For example you could use XQuery to create an
-Predicate in a xref:latest@manual:eips:filter-eip.adoc[Message
+Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter] or as an Expression for a Recipient List.
== Options
diff --git a/components/camel-saxon/src/main/docs/xquery-language.adoc
b/components/camel-saxon/src/main/docs/xquery-language.adoc
index 86fb424..dd0311b 100644
--- a/components/camel-saxon/src/main/docs/xquery-language.adoc
+++ b/components/camel-saxon/src/main/docs/xquery-language.adoc
@@ -7,7 +7,7 @@ Camel supports http://www.w3.org/TR/xquery/[XQuery] to allow an
Expression or Predicate to be
used in the DSL or xref:latest@manual::xml-configuration.adoc[Xml
Configuration]. For example you could use XQuery to create an
-Predicate in a xref:latest@manual:eips:filter-eip.adoc[Message
+Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
Recipient List.
diff --git a/components/camel-spring/src/main/docs/spel-language.adoc
b/components/camel-spring/src/main/docs/spel-language.adoc
index 43b32f3..b1c59f3 100644
--- a/components/camel-spring/src/main/docs/spel-language.adoc
+++ b/components/camel-spring/src/main/docs/spel-language.adoc
@@ -115,8 +115,8 @@ can invoke the "bar" method on this bean like this:
=== SpEL in enterprise integration patterns
-You can use SpEL as an expression for
xref:latest@manual:eips:recipientList-eip.adoc[Recipient
-List] or as a predicate inside a
xref:latest@manual:eips:filter-eip.adoc[Message
+You can use SpEL as an expression for
xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient
+List] or as a predicate inside a xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter]:
[source,xml]
diff --git a/components/camel-spring/src/main/docs/spring-event-component.adoc
b/components/camel-spring/src/main/docs/spring-event-component.adoc
index c0997e6..cdb2f94 100644
--- a/components/camel-spring/src/main/docs/spring-event-component.adoc
+++ b/components/camel-spring/src/main/docs/spring-event-component.adoc
@@ -11,8 +11,8 @@ The Spring Event component provides access to the Spring
`ApplicationEvent` objects. This allows you to publish
`ApplicationEvent` objects to a Spring `ApplicationContext` or to
consume them. You can then use
-xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration
-Patterns] to process them such as
xref:latest@manual:eips:filter-eip.adoc[Message
+xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns] to process them such as xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter].
== URI format
diff --git a/components/camel-spring/src/main/docs/spring.adoc
b/components/camel-spring/src/main/docs/spring.adoc
index 594b3b5..77cb39d 100644
--- a/components/camel-spring/src/main/docs/spring.adoc
+++ b/components/camel-spring/src/main/docs/spring.adoc
@@ -19,7 +19,7 @@ components like xref:jms-component.adoc[JMS] and
xref:jms-component.adoc[JPA]
Type Converter support for Spring Resources etc
* Allows you to reuse the Spring Testing
framework to simplify your unit and integration testing using
-xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration
+xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's powerful xref:mock-component.adoc[Mock] and
xref:test.adoc[Test] endpoints
diff --git a/components/camel-xpath/src/main/docs/xpath-language.adoc
b/components/camel-xpath/src/main/docs/xpath-language.adoc
index ef3b004..b462860 100644
--- a/components/camel-xpath/src/main/docs/xpath-language.adoc
+++ b/components/camel-xpath/src/main/docs/xpath-language.adoc
@@ -7,7 +7,7 @@ Camel supports http://www.w3.org/TR/xpath[XPath] to allow an
Expression or Predicate to be
used in the DSL or xref:latest@manual::xml-configuration.adoc[Xml
Configuration]. For example you could use XPath to create an
-Predicate in a xref:latest@manual:eips:filter-eip.adoc[Message
+Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
Recipient List.
diff --git a/docs/components/modules/ROOT/pages/azure-blob-component.adoc
b/docs/components/modules/ROOT/pages/azure-blob-component.adoc
index bfe5cd8..daf2a3e 100644
--- a/docs/components/modules/ROOT/pages/azure-blob-component.adoc
+++ b/docs/components/modules/ROOT/pages/azure-blob-component.adoc
@@ -278,4 +278,4 @@ Maven users will need to add the following dependency to
their `pom.xml`.
</dependency>
----
-where `${camel-version}` must be replaced by the actual version of Camel.
+where `+++${camel-version}+++` must be replaced by the actual version of Camel.
diff --git a/docs/components/modules/ROOT/pages/bean-language.adoc
b/docs/components/modules/ROOT/pages/bean-language.adoc
index 56fd6e1..bfb6d55 100644
--- a/docs/components/modules/ROOT/pages/bean-language.adoc
+++ b/docs/components/modules/ROOT/pages/bean-language.adoc
@@ -15,7 +15,7 @@ using the type of the message body and using any annotations
on the bean
methods.
The xref:latest@manual::bean-binding.adoc[Bean Binding] rules are used to bind
the
-xref:latest@manual::message.adoc[Message] Exchange to the method parameters;
so you can
+xref:{eip-vc}:eips:message.adoc[Message] Exchange to the method parameters; so
you can
annotate the bean to extract headers or other expressions such as
xref:xpath-language.adoc[XPath] or xref:xquery-language.adoc[XQuery] from the
message.
@@ -139,7 +139,7 @@ public boolean isGoldCustomer(@Header(name = "foo") Integer
fooHeader) {...}
----
So you can bind parameters of the method to the Exchange, the
-xref:latest@manual::message.adoc[Message] or individual headers, properties,
the body
+xref:{eip-vc}:eips:message.adoc[Message] or individual headers, properties,
the body
or other expressions.
[[BeanLanguage-Non-RegistryBeans]]
@@ -210,5 +210,5 @@ We have some test cases you can look at if it'll help
is a JUnit test case showing the Java xref:latest@manual::dsl.adoc[DSL] use of
the bean
expression being used in a filter
*
https://github.com/apache/camel/blob/master/components/camel-spring/src/test/resources/org/apache/camel/spring/processor/aggregator.xml[aggregator.xml]
-is a Spring XML test case for the
xref:latest@manual:eips:aggregate-eip.adoc[Aggregator] which
+is a Spring XML test case for the
xref:{eip-vc}:eips:aggregate-eip.adoc[Aggregator] which
uses a bean method call to test for the completion of the aggregation.
diff --git a/docs/components/modules/ROOT/pages/beanstalk-component.adoc
b/docs/components/modules/ROOT/pages/beanstalk-component.adoc
index 93e482b..de51698 100644
--- a/docs/components/modules/ROOT/pages/beanstalk-component.adoc
+++ b/docs/components/modules/ROOT/pages/beanstalk-component.adoc
@@ -191,7 +191,7 @@ Be careful when specifying `release`, as the failed job
will immediately
become available in the same tube and your consumer will try to acquire
it again. You can `release` and specify _jobDelay_ though.
-The beanstalk consumer is a Scheduled
xref:latest@manual::polling-consumer.adoc[Polling
+The beanstalk consumer is a Scheduled
xref:{eip-vc}:eips:polling-consumer.adoc[Polling
Consumer] which means there is more options you can configure, such as
how frequent the consumer should poll. For more details
see Polling Consumer.
diff --git a/docs/components/modules/ROOT/pages/dataset-component.adoc
b/docs/components/modules/ROOT/pages/dataset-component.adoc
index 50946b8..cd993a7 100644
--- a/docs/components/modules/ROOT/pages/dataset-component.adoc
+++ b/docs/components/modules/ROOT/pages/dataset-component.adoc
@@ -13,7 +13,7 @@ notoriously difficult. The xref:mock-component.adoc[Mock],
xref:mock-component.a
and xref:dataset-component.adoc[DataSet] endpoints work great with the
Camel Testing Framework to simplify your unit and
integration testing using
-xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration
+xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's large range of Components
together with the powerful Bean Integration.
diff --git a/docs/components/modules/ROOT/pages/dataset-test-component.adoc
b/docs/components/modules/ROOT/pages/dataset-test-component.adoc
index 550f637..642973e 100644
--- a/docs/components/modules/ROOT/pages/dataset-test-component.adoc
+++ b/docs/components/modules/ROOT/pages/dataset-test-component.adoc
@@ -13,7 +13,7 @@ notoriously difficult. The xref:mock-component.adoc[Mock],
xref:mock-component.a
and xref:dataset-component.adoc[DataSet] endpoints work great with the
Camel Testing Framework to simplify your unit and
integration testing using
-xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration
+xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's large range of Components
together with the powerful Bean Integration.
diff --git a/docs/components/modules/ROOT/pages/debezium-mongodb-component.adoc
b/docs/components/modules/ROOT/pages/debezium-mongodb-component.adoc
index 7aca62a..c0c1a6e 100644
--- a/docs/components/modules/ROOT/pages/debezium-mongodb-component.adoc
+++ b/docs/components/modules/ROOT/pages/debezium-mongodb-component.adoc
@@ -210,7 +210,7 @@ The following headers are available when consuming change
events from Debezium.
[width="100%",cols="2m,2m,1m,5",options="header"]
|===
| Header constant | Header value
| Type | Description
-| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "{server-name}.{database-name}.{table-name}".
+| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "+++{server-name}.{database-name}.{table-name}+++".
| DebeziumConstants.HEADER_KEY | "CamelDebeziumKey"
| Struct | The key of the event, normally is the table
Primary Key.
| DebeziumConstants.HEADER_SOURCE_METADATA | "CamelDebeziumSourceMetadata"
| Map | The metadata about the source event, for example
`table` name, database `name`, log position, etc, please refer to the Debezium
documentation for more info.
| DebeziumConstants.HEADER_OPERATION | "CamelDebeziumOperation"
| String | If presents, the type of event operation. Values
for the connector are `c` for create (or insert), `u` for update, `d` for
delete or `r` for read (in the case of a initial sync).
diff --git a/docs/components/modules/ROOT/pages/debezium-mysql-component.adoc
b/docs/components/modules/ROOT/pages/debezium-mysql-component.adoc
index b035fe0..0baab92 100644
--- a/docs/components/modules/ROOT/pages/debezium-mysql-component.adoc
+++ b/docs/components/modules/ROOT/pages/debezium-mysql-component.adoc
@@ -277,7 +277,7 @@ The following headers are available when consuming change
events from Debezium.
[width="100%",cols="2m,2m,1m,5",options="header"]
|===
| Header constant | Header value
| Type | Description
-| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "{server-name}.{database-name}.{table-name}".
+| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "+++{server-name}.{database-name}.{table-name}+++".
| DebeziumConstants.HEADER_KEY | "CamelDebeziumKey"
| Struct | The key of the event, normally is the table
Primary Key.
| DebeziumConstants.HEADER_SOURCE_METADATA | "CamelDebeziumSourceMetadata"
| Map | The metadata about the source event, for example
`table` name, database `name`, log position, etc, please refer to the Debezium
documentation for more info.
| DebeziumConstants.HEADER_OPERATION | "CamelDebeziumOperation"
| String | If presents, the type of event operation. Values
for the connector are `c` for create (or insert), `u` for update, `d` for
delete or `r` in case of a snapshot event.
diff --git
a/docs/components/modules/ROOT/pages/debezium-postgres-component.adoc
b/docs/components/modules/ROOT/pages/debezium-postgres-component.adoc
index 98295cd..3d7a1e4 100644
--- a/docs/components/modules/ROOT/pages/debezium-postgres-component.adoc
+++ b/docs/components/modules/ROOT/pages/debezium-postgres-component.adoc
@@ -250,7 +250,7 @@ The following headers are available when consuming change
events from Debezium.
[width="100%",cols="2m,2m,1m,5",options="header"]
|===
| Header constant | Header value
| Type | Description
-| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "{server-name}.{database-name}.{table-name}".
+| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "+++{server-name}.{database-name}.{table-name}+++".
| DebeziumConstants.HEADER_KEY | "CamelDebeziumKey"
| Struct | The key of the event, normally is the table
Primary Key.
| DebeziumConstants.HEADER_SOURCE_METADATA | "CamelDebeziumSourceMetadata"
| Map | The metadata about the source event, for example
`table` name, database `name`, log position, etc, please refer to the Debezium
documentation for more info.
| DebeziumConstants.HEADER_OPERATION | "CamelDebeziumOperation"
| String | If presents, the type of event operation. Values
for the connector are `c` for create (or insert), `u` for update, `d` for
delete or `r` in case of a snapshot event.
diff --git
a/docs/components/modules/ROOT/pages/debezium-sqlserver-component.adoc
b/docs/components/modules/ROOT/pages/debezium-sqlserver-component.adoc
index 1b7bd21..ed62410 100644
--- a/docs/components/modules/ROOT/pages/debezium-sqlserver-component.adoc
+++ b/docs/components/modules/ROOT/pages/debezium-sqlserver-component.adoc
@@ -211,7 +211,7 @@ The following headers are available when consuming change
events from Debezium.
[width="100%",cols="2m,2m,1m,5",options="header"]
|===
| Header constant | Header value
| Type | Description
-| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "{server-name}.{database-name}.{table-name}".
+| DebeziumConstants.HEADER_IDENTIFIER | "CamelDebeziumIdentifier"
| String | The identifier of the connector, normally is this
format "+++{server-name}.{database-name}.{table-name}+++".
| DebeziumConstants.HEADER_KEY | "CamelDebeziumKey"
| Struct | The key of the event, normally is the table
Primary Key.
| DebeziumConstants.HEADER_SOURCE_METADATA | "CamelDebeziumSourceMetadata"
| Map | The metadata about the source event, for example
`table` name, database `name`, log position, etc, please refer to the Debezium
documentation for more info.
| DebeziumConstants.HEADER_OPERATION | "CamelDebeziumOperation"
| String | If presents, the type of event operation. Values
for the connector are `c` for create (or insert), `u` for update, `d` for
delete or `r` in case of a snapshot event.
diff --git a/docs/components/modules/ROOT/pages/disruptor-component.adoc
b/docs/components/modules/ROOT/pages/disruptor-component.adoc
index 87788ce..8a5aeba 100644
--- a/docs/components/modules/ROOT/pages/disruptor-component.adoc
+++ b/docs/components/modules/ROOT/pages/disruptor-component.adoc
@@ -245,7 +245,7 @@ without incurring significant latency spikes.
== Use of Request Reply
-The Disruptor component supports using
xref:latest@manual:eips:requestReply-eip.adoc[Request
+The Disruptor component supports using
xref:{eip-vc}:eips:requestReply-eip.adoc[Request
Reply], where the caller will wait for the Async route to complete. For
instance:
diff --git
a/docs/components/modules/ROOT/pages/elasticsearch-rest-component.adoc
b/docs/components/modules/ROOT/pages/elasticsearch-rest-component.adoc
index 029fdba..7378b74 100644
--- a/docs/components/modules/ROOT/pages/elasticsearch-rest-component.adoc
+++ b/docs/components/modules/ROOT/pages/elasticsearch-rest-component.adoc
@@ -315,7 +315,7 @@ try (ElasticsearchScrollRequestIterator response =
template.requestBody("direct:
}
----
-xref:latest@manual:eips:split-eip.adoc[Split EIP] can also be used.
+xref:{eip-vc}:eips:split-eip.adoc[Split EIP] can also be used.
[source,java]
----
diff --git a/docs/components/modules/ROOT/pages/facebook-component.adoc
b/docs/components/modules/ROOT/pages/facebook-component.adoc
index 160a405..f534f58 100644
--- a/docs/components/modules/ROOT/pages/facebook-component.adoc
+++ b/docs/components/modules/ROOT/pages/facebook-component.adoc
@@ -354,7 +354,7 @@ facebook4j.PostUpdate body.
.to("facebook://postFeed/inBody=postUpdate);
----------------------------------------------------
-To poll, every 5 sec (You can set the
xref:latest@manual::polling-consumer.adoc[polling
+To poll, every 5 sec (You can set the
xref:{eip-vc}:eips:polling-consumer.adoc[polling
consumer] options by adding a prefix of "consumer"), all statuses on
your home feed:
diff --git a/docs/components/modules/ROOT/pages/groovy-language.adoc
b/docs/components/modules/ROOT/pages/groovy-language.adoc
index d4b3f72..e2488e9 100644
--- a/docs/components/modules/ROOT/pages/groovy-language.adoc
+++ b/docs/components/modules/ROOT/pages/groovy-language.adoc
@@ -18,7 +18,7 @@ To use a Groovy expression use the following Java code
---------------------------------------
For example you could use the *groovy* function to create an
-Predicate in a xref:latest@manual:eips:filter-eip.adoc[Message Filter] or as
an Expression for a
+Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message Filter] or as an
Expression for a
Recipient List
== Groovy Options
diff --git a/docs/components/modules/ROOT/pages/jms-component.adoc
b/docs/components/modules/ROOT/pages/jms-component.adoc
index 9a37d72..4775c6d 100644
--- a/docs/components/modules/ROOT/pages/jms-component.adoc
+++ b/docs/components/modules/ROOT/pages/jms-component.adoc
@@ -600,7 +600,7 @@ the documentation.
Normally, when using xref:jms-component.adoc[JMS] as the transport, it only
transfers the body and headers as the payload. If you want to use
-xref:jms-component.adoc[JMS] with a
xref:latest@manual::dead-letter-channel.adoc[Dead Letter
+xref:jms-component.adoc[JMS] with a
xref:{eip-vc}:eips:dead-letter-channel.adoc[Dead Letter
Channel], using a JMS queue as the Dead Letter Queue, then normally the
caused Exception is not stored in the JMS message. You can, however, use
the `transferExchange` option on the JMS dead letter queue to instruct
@@ -1307,7 +1307,7 @@ Transactions and [Request Reply] over JMS
When using Request Reply over JMS you cannot
use a single transaction; JMS will not send any messages until a commit
is performed, so the server side won't receive anything at all until the
-transaction commits. Therefore to use
xref:latest@manual:eips:requestReply-eip.adoc[Request
+transaction commits. Therefore to use
xref:{eip-vc}:eips:requestReply-eip.adoc[Request
Reply] you must commit a transaction after sending the request and then
use a separate transaction for receiving the response.
diff --git a/docs/components/modules/ROOT/pages/language-component.adoc
b/docs/components/modules/ROOT/pages/language-component.adoc
index bebf904..56e2efe 100644
--- a/docs/components/modules/ROOT/pages/language-component.adoc
+++ b/docs/components/modules/ROOT/pages/language-component.adoc
@@ -13,7 +13,7 @@ to an endpoint which executes a script by any of the supported
Languages in Camel. +
By having a component to execute language scripts, it allows more
dynamic routing capabilities. For example by using the
-Routing Slip or xref:latest@manual:eips:dynamic-router.adoc[Dynamic
+Routing Slip or xref:{eip-vc}:eips:dynamic-router.adoc[Dynamic
Router] EIPs you can send messages to `language` endpoints where the
script is dynamic defined as well.
diff --git a/docs/components/modules/ROOT/pages/mock-component.adoc
b/docs/components/modules/ROOT/pages/mock-component.adoc
index e537504..787dae6 100644
--- a/docs/components/modules/ROOT/pages/mock-component.adoc
+++ b/docs/components/modules/ROOT/pages/mock-component.adoc
@@ -13,7 +13,7 @@ notoriously difficult. The xref:mock-component.adoc[Mock],
xref:mock-component.a
and xref:dataset-component.adoc[DataSet] endpoints work great with the
Camel Testing Framework to simplify your unit and
integration testing using
-xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration
+xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's large range of Components
together with the powerful Bean Integration.
diff --git a/docs/components/modules/ROOT/pages/mvel-language.adoc
b/docs/components/modules/ROOT/pages/mvel-language.adoc
index 024d425..4bc508b 100644
--- a/docs/components/modules/ROOT/pages/mvel-language.adoc
+++ b/docs/components/modules/ROOT/pages/mvel-language.adoc
@@ -99,7 +99,7 @@ The component supports 6 options, which are listed below.
== Samples
-For example you could use Mvel inside a
xref:latest@manual:eips:filter-eip.adoc[Message
+For example you could use Mvel inside a
xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter] in XML
[source,java]
diff --git a/docs/components/modules/ROOT/pages/ognl-language.adoc
b/docs/components/modules/ROOT/pages/ognl-language.adoc
index ac826ef..062a4d4 100644
--- a/docs/components/modules/ROOT/pages/ognl-language.adoc
+++ b/docs/components/modules/ROOT/pages/ognl-language.adoc
@@ -99,7 +99,7 @@ The component supports 2 options, which are listed below.
== Samples
-For example you could use OGNL inside a
xref:latest@manual:eips:filter-eip.adoc[Message
+For example you could use OGNL inside a
xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter] in XML
[source,java]
diff --git a/docs/components/modules/ROOT/pages/quartz-component.adoc
b/docs/components/modules/ROOT/pages/quartz-component.adoc
index 10d3e94..9dce8a6 100644
--- a/docs/components/modules/ROOT/pages/quartz-component.adoc
+++ b/docs/components/modules/ROOT/pages/quartz-component.adoc
@@ -412,7 +412,7 @@ but it does not want to be fired now.
The xref:quartz-component.adoc[Quartz] component provides a
Polling Consumer scheduler which allows to
-use cron based scheduling for xref:latest@manual::polling-consumer.adoc[Polling
+use cron based scheduling for xref:{eip-vc}:eips:polling-consumer.adoc[Polling
Consumer] such as the File and FTP
consumers.
diff --git a/docs/components/modules/ROOT/pages/spel-language.adoc
b/docs/components/modules/ROOT/pages/spel-language.adoc
index 7cf9669..f4a8db7 100644
--- a/docs/components/modules/ROOT/pages/spel-language.adoc
+++ b/docs/components/modules/ROOT/pages/spel-language.adoc
@@ -116,8 +116,8 @@ can invoke the "bar" method on this bean like this:
=== SpEL in enterprise integration patterns
-You can use SpEL as an expression for
xref:latest@manual:eips:recipientList-eip.adoc[Recipient
-List] or as a predicate inside a
xref:latest@manual:eips:filter-eip.adoc[Message
+You can use SpEL as an expression for
xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient
+List] or as a predicate inside a xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter]:
[source,xml]
diff --git a/docs/components/modules/ROOT/pages/spring-event-component.adoc
b/docs/components/modules/ROOT/pages/spring-event-component.adoc
index 5daf0b7..8848b42 100644
--- a/docs/components/modules/ROOT/pages/spring-event-component.adoc
+++ b/docs/components/modules/ROOT/pages/spring-event-component.adoc
@@ -12,8 +12,8 @@ The Spring Event component provides access to the Spring
`ApplicationEvent` objects. This allows you to publish
`ApplicationEvent` objects to a Spring `ApplicationContext` or to
consume them. You can then use
-xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration
-Patterns] to process them such as
xref:latest@manual:eips:filter-eip.adoc[Message
+xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns] to process them such as xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter].
== URI format
diff --git a/docs/components/modules/ROOT/pages/spring.adoc
b/docs/components/modules/ROOT/pages/spring.adoc
index 2c0751b..7ea0623 100644
--- a/docs/components/modules/ROOT/pages/spring.adoc
+++ b/docs/components/modules/ROOT/pages/spring.adoc
@@ -20,7 +20,7 @@ components like xref:jms-component.adoc[JMS] and
xref:jms-component.adoc[JPA]
Type Converter support for Spring Resources etc
* Allows you to reuse the Spring Testing
framework to simplify your unit and integration testing using
-xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration
+xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's powerful xref:mock-component.adoc[Mock] and
xref:test.adoc[Test] endpoints
diff --git a/docs/components/modules/ROOT/pages/xpath-language.adoc
b/docs/components/modules/ROOT/pages/xpath-language.adoc
index 32dd2a1..58407f7 100644
--- a/docs/components/modules/ROOT/pages/xpath-language.adoc
+++ b/docs/components/modules/ROOT/pages/xpath-language.adoc
@@ -8,7 +8,7 @@ Camel supports http://www.w3.org/TR/xpath[XPath] to allow an
Expression or Predicate to be
used in the DSL or xref:latest@manual::xml-configuration.adoc[Xml
Configuration]. For example you could use XPath to create an
-Predicate in a xref:latest@manual:eips:filter-eip.adoc[Message
+Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
Recipient List.
diff --git a/docs/components/modules/ROOT/pages/xquery-component.adoc
b/docs/components/modules/ROOT/pages/xquery-component.adoc
index f13c140..e4b5c10 100644
--- a/docs/components/modules/ROOT/pages/xquery-component.adoc
+++ b/docs/components/modules/ROOT/pages/xquery-component.adoc
@@ -12,7 +12,7 @@ Camel supports http://www.w3.org/TR/xquery/[XQuery] to allow
an
Expression or Predicate to be
used in the DSL or xref:latest@manual::xml-configuration.adoc[Xml
Configuration]. For example you could use XQuery to create an
-Predicate in a xref:latest@manual:eips:filter-eip.adoc[Message
+Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter] or as an Expression for a Recipient List.
== Options
diff --git a/docs/components/modules/ROOT/pages/xquery-language.adoc
b/docs/components/modules/ROOT/pages/xquery-language.adoc
index dffa91c..01b3b4d 100644
--- a/docs/components/modules/ROOT/pages/xquery-language.adoc
+++ b/docs/components/modules/ROOT/pages/xquery-language.adoc
@@ -8,7 +8,7 @@ Camel supports http://www.w3.org/TR/xquery/[XQuery] to allow an
Expression or Predicate to be
used in the DSL or xref:latest@manual::xml-configuration.adoc[Xml
Configuration]. For example you could use XQuery to create an
-Predicate in a xref:latest@manual:eips:filter-eip.adoc[Message
+Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
Recipient List.
