You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by dj...@apache.org on 2020/03/22 00:34:32 UTC
[camel] branch camel-2.x updated: fix xrefs to aggregated eip
content.
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 91652d5 fix xrefs to aggregated eip content.
new 3787783 Merge pull request #3661 from djencks/camel-2.x-issue-14747-aggregate-eip-task-14756
91652d5 is described below
commit 91652d52f0f3f53c6c4df4cbb295e204a45e7463
Author: David Jencks <dj...@apache.org>
AuthorDate: Fri Mar 20 10:11:30 2020 -0700
fix xrefs to aggregated eip content.
---
components/camel-bam/src/main/docs/bam.adoc | 2 +-
components/camel-beanstalk/src/main/docs/beanstalk-component.adoc | 4 ++--
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 | 4 ++--
components/camel-groovy-dsl/src/main/docs/groovy-dsl.adoc | 2 +-
components/camel-groovy/src/main/docs/groovy-language.adoc | 2 +-
components/camel-jms/src/main/docs/jms-component.adoc | 6 +++---
components/camel-josql/src/main/docs/sql-language.adoc | 2 +-
components/camel-jpa/src/main/docs/jpa-component.adoc | 2 +-
components/camel-juel/src/main/docs/el-language.adoc | 2 +-
components/camel-jxpath/src/main/docs/jxpath-language.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-quartz2/src/main/docs/quartz2-component.adoc | 2 +-
components/camel-ruby/src/main/docs/ruby.adoc | 2 +-
components/camel-saxon/src/main/docs/xquery-component.adoc | 2 +-
components/camel-saxon/src/main/docs/xquery-language.adoc | 2 +-
components/camel-script/src/main/docs/javaScript-language.adoc | 2 +-
components/camel-script/src/main/docs/php-language.adoc | 2 +-
components/camel-script/src/main/docs/python-language.adoc | 2 +-
components/camel-script/src/main/docs/ruby-language.adoc | 2 +-
.../camel-servletlistener/src/main/docs/servletlistener.adoc | 8 ++++----
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 | 4 ++--
components/camel-test-spring/src/main/docs/test-spring.adoc | 2 +-
components/camel-test/src/main/docs/test.adoc | 2 +-
docs/components/modules/ROOT/pages/bam.adoc | 2 +-
docs/components/modules/ROOT/pages/beanstalk-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/disruptor-component.adoc | 2 +-
docs/components/modules/ROOT/pages/el-language.adoc | 2 +-
.../modules/ROOT/pages/elasticsearch-rest-component.adoc | 2 +-
docs/components/modules/ROOT/pages/facebook-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/groovy-dsl.adoc | 2 +-
docs/components/modules/ROOT/pages/groovy-language.adoc | 2 +-
docs/components/modules/ROOT/pages/javaScript-language.adoc | 2 +-
docs/components/modules/ROOT/pages/jms-component.adoc | 6 +++---
docs/components/modules/ROOT/pages/jpa-component.adoc | 2 +-
docs/components/modules/ROOT/pages/jxpath-language.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/php-language.adoc | 2 +-
docs/components/modules/ROOT/pages/python-language.adoc | 2 +-
docs/components/modules/ROOT/pages/quartz-component.adoc | 2 +-
docs/components/modules/ROOT/pages/quartz2-component.adoc | 2 +-
docs/components/modules/ROOT/pages/ruby-language.adoc | 2 +-
docs/components/modules/ROOT/pages/ruby.adoc | 2 +-
docs/components/modules/ROOT/pages/servletlistener.adoc | 8 ++++----
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 | 4 ++--
docs/components/modules/ROOT/pages/sql-language.adoc | 2 +-
docs/components/modules/ROOT/pages/test-spring.adoc | 2 +-
docs/components/modules/ROOT/pages/test.adoc | 2 +-
docs/components/modules/ROOT/pages/xquery-component.adoc | 2 +-
docs/components/modules/ROOT/pages/xquery-language.adoc | 2 +-
58 files changed, 78 insertions(+), 78 deletions(-)
diff --git a/components/camel-bam/src/main/docs/bam.adoc b/components/camel-bam/src/main/docs/bam.adoc
index de95c72..ac16ad5 100644
--- a/components/camel-bam/src/main/docs/bam.adoc
+++ b/components/camel-bam/src/main/docs/bam.adoc
@@ -13,7 +13,7 @@ Invoice from system B within a specific time period.
[[BAM-HowCamelBAMWorks]]
== How Camel BAM Works
-Camel BAM uses a xref:manual::correlation-identifier.adoc[Correlation
+Camel BAM uses a xref:{eip-vc}:eips:correlation-identifier.adoc[Correlation
Identifier] on an input message to determine the _Process Instance_ to
which it belongs. The process instance is an entity bean which can
maintain state for each _Activity_ (where an activity typically maps to
diff --git a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
index 6ae062a..53db7be 100644
--- a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
+++ b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
@@ -180,7 +180,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.
@@ -253,4 +253,4 @@ manually.
So the second route periodically requests Beanstalk to _kick_ 10 jobs
out of buried and/or delayed state to the normal queue.
-
\ No newline at end of file
+
diff --git a/components/camel-disruptor/src/main/docs/disruptor-component.adoc b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
index 792b7d6..dbb2aec 100644
--- a/components/camel-disruptor/src/main/docs/disruptor-component.adoc
+++ b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
@@ -235,7 +235,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 0c488a5..16ab909 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
@@ -301,7 +301,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 7314aa8..4389515 100644
--- a/components/camel-facebook/src/main/docs/facebook-component.adoc
+++ b/components/camel-facebook/src/main/docs/facebook-component.adoc
@@ -344,7 +344,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:
@@ -365,4 +365,4 @@ CamelFacebook.query header.
from("direct:foo")
.setHeader("CamelFacebook.query", header("bar"))
.to("facebook://posts");
---------------------------------------------------------
\ No newline at end of file
+--------------------------------------------------------
diff --git a/components/camel-groovy-dsl/src/main/docs/groovy-dsl.adoc b/components/camel-groovy-dsl/src/main/docs/groovy-dsl.adoc
index f61d458..0359d30 100644
--- a/components/camel-groovy-dsl/src/main/docs/groovy-dsl.adoc
+++ b/components/camel-groovy-dsl/src/main/docs/groovy-dsl.adoc
@@ -6,7 +6,7 @@ DSL, but it additionally allows to use Groovy language
features in your routes, particularly
http://www.groovy-lang.org/closures.html[Closures] acting as
Processor, Expression,
-Predicate, or xref:latest@manual:eips:aggregate-eip.adoc[Aggregation
+Predicate, or xref:{eip-vc}:eips:aggregate-eip.adoc[Aggregation
Strategy].
With the Groovy DSL you write your RouteBuilder classes entirely in
diff --git a/components/camel-groovy/src/main/docs/groovy-language.adoc b/components/camel-groovy/src/main/docs/groovy-language.adoc
index af80572..e293ec3 100644
--- a/components/camel-groovy/src/main/docs/groovy-language.adoc
+++ b/components/camel-groovy/src/main/docs/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/components/camel-jms/src/main/docs/jms-component.adoc b/components/camel-jms/src/main/docs/jms-component.adoc
index 5291ecc..71ddb9c 100644
--- a/components/camel-jms/src/main/docs/jms-component.adoc
+++ b/components/camel-jms/src/main/docs/jms-component.adoc
@@ -691,7 +691,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
@@ -1405,7 +1405,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.
@@ -1543,4 +1543,4 @@ wmq.setDestinationResolver(new DestinationResolver() {
return wmqSession.createQueue("queue:///" + destinationName + "?targetClient=1");
}
});
-----------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file
+----------------------------------------------------------------------------------------------------------------------------------
diff --git a/components/camel-josql/src/main/docs/sql-language.adoc b/components/camel-josql/src/main/docs/sql-language.adoc
index 7755070..ba55c0f 100644
--- a/components/camel-josql/src/main/docs/sql-language.adoc
+++ b/components/camel-josql/src/main/docs/sql-language.adoc
@@ -37,7 +37,7 @@ Camel supports http://en.wikipedia.org/wiki/SQL[SQL] 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 SQL 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-jpa/src/main/docs/jpa-component.adoc b/components/camel-jpa/src/main/docs/jpa-component.adoc
index 407e49b..a1deddc 100644
--- a/components/camel-jpa/src/main/docs/jpa-component.adoc
+++ b/components/camel-jpa/src/main/docs/jpa-component.adoc
@@ -403,7 +403,7 @@ xref:jpa-component.adoc[JPA] to store traced messages into a database.
== Using the JPA-Based Idempotent Repository
-The Idempotent Consumer from the xref:latest@manual::enterprise-integration-patterns.adoc[EIP patterns] is used to filter out duplicate messages. A JPA-based idempotent repository is provided.
+The Idempotent Consumer from the xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[EIP patterns] is used to filter out duplicate messages. A JPA-based idempotent repository is provided.
To use the JPA based idempotent repository.
diff --git a/components/camel-juel/src/main/docs/el-language.adoc b/components/camel-juel/src/main/docs/el-language.adoc
index 50ad5f5..c971940 100644
--- a/components/camel-juel/src/main/docs/el-language.adoc
+++ b/components/camel-juel/src/main/docs/el-language.adoc
@@ -12,7 +12,7 @@ Expression or Predicate to be
used in the DSL or xref:latest@manual::xml-configuration.adoc[Xml
Configuration].
-For example you could use EL inside a xref:latest@manual:eips:filter-eip.adoc[Message
+For example you could use EL inside a xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter] in XML
[source,xml]
diff --git a/components/camel-jxpath/src/main/docs/jxpath-language.adoc b/components/camel-jxpath/src/main/docs/jxpath-language.adoc
index 55ebe49..88acd61 100644
--- a/components/camel-jxpath/src/main/docs/jxpath-language.adoc
+++ b/components/camel-jxpath/src/main/docs/jxpath-language.adoc
@@ -9,7 +9,7 @@ XPath expressions to be used on beans in an
Expression or Predicate to be
used in the DSL or xref:latest@manual::xml-configuration.adoc[Xml
Configuration]. For example you could use JXPath 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-mvel/src/main/docs/mvel-language.adoc b/components/camel-mvel/src/main/docs/mvel-language.adoc
index 487b8e2..c5f607f 100644
--- a/components/camel-mvel/src/main/docs/mvel-language.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-language.adoc
@@ -97,7 +97,7 @@ The component supports 4 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 2cd140d..35de290 100644
--- a/components/camel-ognl/src/main/docs/ognl-language.adoc
+++ b/components/camel-ognl/src/main/docs/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/components/camel-quartz/src/main/docs/quartz-component.adoc b/components/camel-quartz/src/main/docs/quartz-component.adoc
index 0615dbb..ae4cf00 100644
--- a/components/camel-quartz/src/main/docs/quartz-component.adoc
+++ b/components/camel-quartz/src/main/docs/quartz-component.adoc
@@ -397,7 +397,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-quartz2/src/main/docs/quartz2-component.adoc b/components/camel-quartz2/src/main/docs/quartz2-component.adoc
index 267b2ed..c9fa893 100644
--- a/components/camel-quartz2/src/main/docs/quartz2-component.adoc
+++ b/components/camel-quartz2/src/main/docs/quartz2-component.adoc
@@ -308,7 +308,7 @@ The timeZone value is the values accepted by `java.util.TimeZone`.
The xref:quartz2-component.adoc[Quartz2] 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-ruby/src/main/docs/ruby.adoc b/components/camel-ruby/src/main/docs/ruby.adoc
index 951b850..79ddc9f 100644
--- a/components/camel-ruby/src/main/docs/ruby.adoc
+++ b/components/camel-ruby/src/main/docs/ruby.adoc
@@ -15,7 +15,7 @@ To use a Ruby expression use the following Java code
-----------------------------------
For example you could use the *ruby* function 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-saxon/src/main/docs/xquery-component.adoc b/components/camel-saxon/src/main/docs/xquery-component.adoc
index 94a2271..03aa030 100644
--- a/components/camel-saxon/src/main/docs/xquery-component.adoc
+++ b/components/camel-saxon/src/main/docs/xquery-component.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.
diff --git a/components/camel-saxon/src/main/docs/xquery-language.adoc b/components/camel-saxon/src/main/docs/xquery-language.adoc
index c31d9a6..53b26a5 100644
--- a/components/camel-saxon/src/main/docs/xquery-language.adoc
+++ b/components/camel-saxon/src/main/docs/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.
diff --git a/components/camel-script/src/main/docs/javaScript-language.adoc b/components/camel-script/src/main/docs/javaScript-language.adoc
index 3065dabf..84a10b6 100644
--- a/components/camel-script/src/main/docs/javaScript-language.adoc
+++ b/components/camel-script/src/main/docs/javaScript-language.adoc
@@ -19,7 +19,7 @@ To use a JavaScript expression use the following Java code
-----------------------------------------------
For example you could use the *javaScript* function 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-script/src/main/docs/php-language.adoc b/components/camel-script/src/main/docs/php-language.adoc
index be24d4a..240f2de 100644
--- a/components/camel-script/src/main/docs/php-language.adoc
+++ b/components/camel-script/src/main/docs/php-language.adoc
@@ -18,7 +18,7 @@ To use a PHP expression use the following Java code
---------------------------------
For example you could use the *php* function 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-script/src/main/docs/python-language.adoc b/components/camel-script/src/main/docs/python-language.adoc
index cdada7b..8e77c9c 100644
--- a/components/camel-script/src/main/docs/python-language.adoc
+++ b/components/camel-script/src/main/docs/python-language.adoc
@@ -18,7 +18,7 @@ To use a Python expression use the following Java code
---------------------------------------
For example you could use the *python* function 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-script/src/main/docs/ruby-language.adoc b/components/camel-script/src/main/docs/ruby-language.adoc
index 6cd0d5b..fc1ddf8 100644
--- a/components/camel-script/src/main/docs/ruby-language.adoc
+++ b/components/camel-script/src/main/docs/ruby-language.adoc
@@ -18,7 +18,7 @@ To use a Ruby expression use the following Java code
-----------------------------------
For example you could use the *ruby* function 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-servletlistener/src/main/docs/servletlistener.adoc b/components/camel-servletlistener/src/main/docs/servletlistener.adoc
index 9fb6b99f..ff48510 100644
--- a/components/camel-servletlistener/src/main/docs/servletlistener.adoc
+++ b/components/camel-servletlistener/src/main/docs/servletlistener.adoc
@@ -282,8 +282,8 @@ as disabling JMX.
This component uses either JNDI or Simple as the
Registry.
- This allows you to lookup xref:latest@manual:eips:bean-eip.adoc[Bean]s and other services in
-JNDI, and as well to bind and unbind your own xref:latest@manual:eips:bean-eip.adoc[Bean]s.
+ This allows you to lookup xref:{eip-vc}:eips:bean-eip.adoc[Bean]s and other services in
+JNDI, and as well to bind and unbind your own xref:{eip-vc}:eips:bean-eip.adoc[Bean]s.
This is done from Java code by implementing the
`org.apache.camel.component.servletlistener.CamelContextLifecycle`.
@@ -309,8 +309,8 @@ interface.
</context-param>
-------------------------------------------------------------------------------------
-As we enlisted our HelloBean xref:latest@manual:eips:bean-eip.adoc[Bean] using the name
-"myBean" we can refer to this xref:latest@manual:eips:bean-eip.adoc[Bean] in the Camel routes
+As we enlisted our HelloBean xref:{eip-vc}:eips:bean-eip.adoc[Bean] using the name
+"myBean" we can refer to this xref:{eip-vc}:eips:bean-eip.adoc[Bean] in the Camel routes
as shown below:
[source,java]
diff --git a/components/camel-spring/src/main/docs/spel-language.adoc b/components/camel-spring/src/main/docs/spel-language.adoc
index 943afa7..65a29d2 100644
--- a/components/camel-spring/src/main/docs/spel-language.adoc
+++ b/components/camel-spring/src/main/docs/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/components/camel-spring/src/main/docs/spring-event-component.adoc b/components/camel-spring/src/main/docs/spring-event-component.adoc
index 8dbca4d..31f16f6 100644
--- a/components/camel-spring/src/main/docs/spring-event-component.adoc
+++ b/components/camel-spring/src/main/docs/spring-event-component.adoc
@@ -8,8 +8,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 a8d24e6..9f5c0c0 100644
--- a/components/camel-spring/src/main/docs/spring.adoc
+++ b/components/camel-spring/src/main/docs/spring.adoc
@@ -20,7 +20,7 @@ instances or the CamelContext instance itself
and auto-expose Spring beans as components and endpoints.
* 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 Mock and
xref:test.adoc[Test] endpoints
Camel supports Spring Boot using the `camel-spring-boot` component.
@@ -353,4 +353,4 @@ Integration] for further injections.
To avoid a hung route when testing using Spring Transactions see the
note about Spring Integration Testing
-under Transactional Client.
\ No newline at end of file
+under Transactional Client.
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 2ed5a08..862ceed 100644
--- a/components/camel-test-spring/src/main/docs/test-spring.adoc
+++ b/components/camel-test-spring/src/main/docs/test-spring.adoc
@@ -434,7 +434,7 @@ public class MyCamelTest extends AbstractJUnit38SpringContextTests {
== Sending and Receiving Messages
-It might be that the xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration Patterns] you have defined in either http://camel.apache.org/spring.html[Spring] XML or using the Java http://camel.apache.org/dsl.html[DSL] do all of the sending and receiving and you might just work with the http://camel.apache.org/mock.html[Mock] endpoints as described above. However sometimes in a test case its useful to explicitly send or receive messages directly.
+It might be that the xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration Patterns] you have defined in either http://camel.apache.org/spring.html[Spring] XML or using the Java http://camel.apache.org/dsl.html[DSL] do all of the sending and receiving and you might just work with the http://camel.apache.org/mock.html[Mock] endpoints as described above. However sometimes in a test case its useful to explicitly send or receive messages directly.
To send or receive messages you should use the http://camel.apache.org/bean-integration.html[Bean Integration] mechanism. For example to send messages inject a `ProducerTemplate` using the `@EndpointInject` annotation then call the various send methods on this object to send a message to an endpoint. To consume messages use the `@MessageDriven` annotation on a method to have the method invoked when a message is received.
[source,java]
diff --git a/components/camel-test/src/main/docs/test.adoc b/components/camel-test/src/main/docs/test.adoc
index 1b21568..affce30 100644
--- a/components/camel-test/src/main/docs/test.adoc
+++ b/components/camel-test/src/main/docs/test.adoc
@@ -6,7 +6,7 @@ notoriously difficult. The Mock, Test
and 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/bam.adoc b/docs/components/modules/ROOT/pages/bam.adoc
index 0a56b2e..dc3de2a 100644
--- a/docs/components/modules/ROOT/pages/bam.adoc
+++ b/docs/components/modules/ROOT/pages/bam.adoc
@@ -14,7 +14,7 @@ Invoice from system B within a specific time period.
[[BAM-HowCamelBAMWorks]]
== How Camel BAM Works
-Camel BAM uses a xref:manual::correlation-identifier.adoc[Correlation
+Camel BAM uses a xref:{eip-vc}:eips:correlation-identifier.adoc[Correlation
Identifier] on an input message to determine the _Process Instance_ to
which it belongs. The process instance is an entity bean which can
maintain state for each _Activity_ (where an activity typically maps to
diff --git a/docs/components/modules/ROOT/pages/beanstalk-component.adoc b/docs/components/modules/ROOT/pages/beanstalk-component.adoc
index c151bdd..542856d 100644
--- a/docs/components/modules/ROOT/pages/beanstalk-component.adoc
+++ b/docs/components/modules/ROOT/pages/beanstalk-component.adoc
@@ -181,7 +181,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.
@@ -254,4 +254,4 @@ manually.
So the second route periodically requests Beanstalk to _kick_ 10 jobs
out of buried and/or delayed state to the normal queue.
-
\ No newline at end of file
+
diff --git a/docs/components/modules/ROOT/pages/disruptor-component.adoc b/docs/components/modules/ROOT/pages/disruptor-component.adoc
index 7d6d3bf..aef6b41 100644
--- a/docs/components/modules/ROOT/pages/disruptor-component.adoc
+++ b/docs/components/modules/ROOT/pages/disruptor-component.adoc
@@ -236,7 +236,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/el-language.adoc b/docs/components/modules/ROOT/pages/el-language.adoc
index 51f2a8c..eff8ebe 100644
--- a/docs/components/modules/ROOT/pages/el-language.adoc
+++ b/docs/components/modules/ROOT/pages/el-language.adoc
@@ -13,7 +13,7 @@ Expression or Predicate to be
used in the DSL or xref:latest@manual::xml-configuration.adoc[Xml
Configuration].
-For example you could use EL inside a xref:latest@manual:eips:filter-eip.adoc[Message
+For example you could use EL inside a xref:{eip-vc}:eips:filter-eip.adoc[Message
Filter] in XML
[source,xml]
diff --git a/docs/components/modules/ROOT/pages/elasticsearch-rest-component.adoc b/docs/components/modules/ROOT/pages/elasticsearch-rest-component.adoc
index 5febead..ecea617 100644
--- a/docs/components/modules/ROOT/pages/elasticsearch-rest-component.adoc
+++ b/docs/components/modules/ROOT/pages/elasticsearch-rest-component.adoc
@@ -302,7 +302,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 882c885..f2172c0 100644
--- a/docs/components/modules/ROOT/pages/facebook-component.adoc
+++ b/docs/components/modules/ROOT/pages/facebook-component.adoc
@@ -345,7 +345,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:
@@ -366,4 +366,4 @@ CamelFacebook.query header.
from("direct:foo")
.setHeader("CamelFacebook.query", header("bar"))
.to("facebook://posts");
---------------------------------------------------------
\ No newline at end of file
+--------------------------------------------------------
diff --git a/docs/components/modules/ROOT/pages/groovy-dsl.adoc b/docs/components/modules/ROOT/pages/groovy-dsl.adoc
index 4e02331..b7ad393 100644
--- a/docs/components/modules/ROOT/pages/groovy-dsl.adoc
+++ b/docs/components/modules/ROOT/pages/groovy-dsl.adoc
@@ -7,7 +7,7 @@ DSL, but it additionally allows to use Groovy language
features in your routes, particularly
http://www.groovy-lang.org/closures.html[Closures] acting as
Processor, Expression,
-Predicate, or xref:latest@manual:eips:aggregate-eip.adoc[Aggregation
+Predicate, or xref:{eip-vc}:eips:aggregate-eip.adoc[Aggregation
Strategy].
With the Groovy DSL you write your RouteBuilder classes entirely in
diff --git a/docs/components/modules/ROOT/pages/groovy-language.adoc b/docs/components/modules/ROOT/pages/groovy-language.adoc
index da111ee..731ea74 100644
--- a/docs/components/modules/ROOT/pages/groovy-language.adoc
+++ b/docs/components/modules/ROOT/pages/groovy-language.adoc
@@ -19,7 +19,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/javaScript-language.adoc b/docs/components/modules/ROOT/pages/javaScript-language.adoc
index 85ea569..90aca69 100644
--- a/docs/components/modules/ROOT/pages/javaScript-language.adoc
+++ b/docs/components/modules/ROOT/pages/javaScript-language.adoc
@@ -20,7 +20,7 @@ To use a JavaScript expression use the following Java code
-----------------------------------------------
For example you could use the *javaScript* function 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/jms-component.adoc b/docs/components/modules/ROOT/pages/jms-component.adoc
index ab10fc8..bc95e5e 100644
--- a/docs/components/modules/ROOT/pages/jms-component.adoc
+++ b/docs/components/modules/ROOT/pages/jms-component.adoc
@@ -692,7 +692,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
@@ -1406,7 +1406,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.
@@ -1544,4 +1544,4 @@ wmq.setDestinationResolver(new DestinationResolver() {
return wmqSession.createQueue("queue:///" + destinationName + "?targetClient=1");
}
});
-----------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file
+----------------------------------------------------------------------------------------------------------------------------------
diff --git a/docs/components/modules/ROOT/pages/jpa-component.adoc b/docs/components/modules/ROOT/pages/jpa-component.adoc
index 7383a87..e16960b 100644
--- a/docs/components/modules/ROOT/pages/jpa-component.adoc
+++ b/docs/components/modules/ROOT/pages/jpa-component.adoc
@@ -404,7 +404,7 @@ xref:jpa-component.adoc[JPA] to store traced messages into a database.
== Using the JPA-Based Idempotent Repository
-The Idempotent Consumer from the xref:latest@manual::enterprise-integration-patterns.adoc[EIP patterns] is used to filter out duplicate messages. A JPA-based idempotent repository is provided.
+The Idempotent Consumer from the xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[EIP patterns] is used to filter out duplicate messages. A JPA-based idempotent repository is provided.
To use the JPA based idempotent repository.
diff --git a/docs/components/modules/ROOT/pages/jxpath-language.adoc b/docs/components/modules/ROOT/pages/jxpath-language.adoc
index 91e8d23..5caac85 100644
--- a/docs/components/modules/ROOT/pages/jxpath-language.adoc
+++ b/docs/components/modules/ROOT/pages/jxpath-language.adoc
@@ -10,7 +10,7 @@ XPath expressions to be used on beans in an
Expression or Predicate to be
used in the DSL or xref:latest@manual::xml-configuration.adoc[Xml
Configuration]. For example you could use JXPath 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/mvel-language.adoc b/docs/components/modules/ROOT/pages/mvel-language.adoc
index e8b5267..c4c4132 100644
--- a/docs/components/modules/ROOT/pages/mvel-language.adoc
+++ b/docs/components/modules/ROOT/pages/mvel-language.adoc
@@ -98,7 +98,7 @@ The component supports 4 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 5f117ee..7a921ae 100644
--- a/docs/components/modules/ROOT/pages/ognl-language.adoc
+++ b/docs/components/modules/ROOT/pages/ognl-language.adoc
@@ -100,7 +100,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/php-language.adoc b/docs/components/modules/ROOT/pages/php-language.adoc
index 393db2c..6ef6c36 100644
--- a/docs/components/modules/ROOT/pages/php-language.adoc
+++ b/docs/components/modules/ROOT/pages/php-language.adoc
@@ -19,7 +19,7 @@ To use a PHP expression use the following Java code
---------------------------------
For example you could use the *php* function 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/python-language.adoc b/docs/components/modules/ROOT/pages/python-language.adoc
index 8099bab..deb0727 100644
--- a/docs/components/modules/ROOT/pages/python-language.adoc
+++ b/docs/components/modules/ROOT/pages/python-language.adoc
@@ -19,7 +19,7 @@ To use a Python expression use the following Java code
---------------------------------------
For example you could use the *python* function 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/quartz-component.adoc b/docs/components/modules/ROOT/pages/quartz-component.adoc
index 4660975..6211922 100644
--- a/docs/components/modules/ROOT/pages/quartz-component.adoc
+++ b/docs/components/modules/ROOT/pages/quartz-component.adoc
@@ -398,7 +398,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/quartz2-component.adoc b/docs/components/modules/ROOT/pages/quartz2-component.adoc
index 78c5a90..b51ea7d 100644
--- a/docs/components/modules/ROOT/pages/quartz2-component.adoc
+++ b/docs/components/modules/ROOT/pages/quartz2-component.adoc
@@ -309,7 +309,7 @@ The timeZone value is the values accepted by `java.util.TimeZone`.
The xref:quartz2-component.adoc[Quartz2] 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/ruby-language.adoc b/docs/components/modules/ROOT/pages/ruby-language.adoc
index 40180fa..b3a94aa 100644
--- a/docs/components/modules/ROOT/pages/ruby-language.adoc
+++ b/docs/components/modules/ROOT/pages/ruby-language.adoc
@@ -19,7 +19,7 @@ To use a Ruby expression use the following Java code
-----------------------------------
For example you could use the *ruby* function 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/ruby.adoc b/docs/components/modules/ROOT/pages/ruby.adoc
index 576b271..a7f75e6 100644
--- a/docs/components/modules/ROOT/pages/ruby.adoc
+++ b/docs/components/modules/ROOT/pages/ruby.adoc
@@ -16,7 +16,7 @@ To use a Ruby expression use the following Java code
-----------------------------------
For example you could use the *ruby* function 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/servletlistener.adoc b/docs/components/modules/ROOT/pages/servletlistener.adoc
index ab05e0a..f55af9c 100644
--- a/docs/components/modules/ROOT/pages/servletlistener.adoc
+++ b/docs/components/modules/ROOT/pages/servletlistener.adoc
@@ -283,8 +283,8 @@ as disabling JMX.
This component uses either JNDI or Simple as the
Registry.
- This allows you to lookup xref:latest@manual:eips:bean-eip.adoc[Bean]s and other services in
-JNDI, and as well to bind and unbind your own xref:latest@manual:eips:bean-eip.adoc[Bean]s.
+ This allows you to lookup xref:{eip-vc}:eips:bean-eip.adoc[Bean]s and other services in
+JNDI, and as well to bind and unbind your own xref:{eip-vc}:eips:bean-eip.adoc[Bean]s.
This is done from Java code by implementing the
`org.apache.camel.component.servletlistener.CamelContextLifecycle`.
@@ -310,8 +310,8 @@ interface.
</context-param>
-------------------------------------------------------------------------------------
-As we enlisted our HelloBean xref:latest@manual:eips:bean-eip.adoc[Bean] using the name
-"myBean" we can refer to this xref:latest@manual:eips:bean-eip.adoc[Bean] in the Camel routes
+As we enlisted our HelloBean xref:{eip-vc}:eips:bean-eip.adoc[Bean] using the name
+"myBean" we can refer to this xref:{eip-vc}:eips:bean-eip.adoc[Bean] in the Camel routes
as shown below:
[source,java]
diff --git a/docs/components/modules/ROOT/pages/spel-language.adoc b/docs/components/modules/ROOT/pages/spel-language.adoc
index 78f55c0..1b73712 100644
--- a/docs/components/modules/ROOT/pages/spel-language.adoc
+++ b/docs/components/modules/ROOT/pages/spel-language.adoc
@@ -117,8 +117,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 5a4f211..97b193b 100644
--- a/docs/components/modules/ROOT/pages/spring-event-component.adoc
+++ b/docs/components/modules/ROOT/pages/spring-event-component.adoc
@@ -9,8 +9,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 0e31f0e..2204c76 100644
--- a/docs/components/modules/ROOT/pages/spring.adoc
+++ b/docs/components/modules/ROOT/pages/spring.adoc
@@ -21,7 +21,7 @@ instances or the CamelContext instance itself
and auto-expose Spring beans as components and endpoints.
* 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 Mock and
xref:test.adoc[Test] endpoints
Camel supports Spring Boot using the `camel-spring-boot` component.
@@ -354,4 +354,4 @@ Integration] for further injections.
To avoid a hung route when testing using Spring Transactions see the
note about Spring Integration Testing
-under Transactional Client.
\ No newline at end of file
+under Transactional Client.
diff --git a/docs/components/modules/ROOT/pages/sql-language.adoc b/docs/components/modules/ROOT/pages/sql-language.adoc
index 76fe0e4..5a714f7 100644
--- a/docs/components/modules/ROOT/pages/sql-language.adoc
+++ b/docs/components/modules/ROOT/pages/sql-language.adoc
@@ -38,7 +38,7 @@ Camel supports http://en.wikipedia.org/wiki/SQL[SQL] 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 SQL 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/test-spring.adoc b/docs/components/modules/ROOT/pages/test-spring.adoc
index 0093a91..d125358 100644
--- a/docs/components/modules/ROOT/pages/test-spring.adoc
+++ b/docs/components/modules/ROOT/pages/test-spring.adoc
@@ -435,7 +435,7 @@ public class MyCamelTest extends AbstractJUnit38SpringContextTests {
== Sending and Receiving Messages
-It might be that the xref:latest@manual::enterprise-integration-patterns.adoc[Enterprise Integration Patterns] you have defined in either http://camel.apache.org/spring.html[Spring] XML or using the Java http://camel.apache.org/dsl.html[DSL] do all of the sending and receiving and you might just work with the http://camel.apache.org/mock.html[Mock] endpoints as described above. However sometimes in a test case its useful to explicitly send or receive messages directly.
+It might be that the xref:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration Patterns] you have defined in either http://camel.apache.org/spring.html[Spring] XML or using the Java http://camel.apache.org/dsl.html[DSL] do all of the sending and receiving and you might just work with the http://camel.apache.org/mock.html[Mock] endpoints as described above. However sometimes in a test case its useful to explicitly send or receive messages directly.
To send or receive messages you should use the http://camel.apache.org/bean-integration.html[Bean Integration] mechanism. For example to send messages inject a `ProducerTemplate` using the `@EndpointInject` annotation then call the various send methods on this object to send a message to an endpoint. To consume messages use the `@MessageDriven` annotation on a method to have the method invoked when a message is received.
[source,java]
diff --git a/docs/components/modules/ROOT/pages/test.adoc b/docs/components/modules/ROOT/pages/test.adoc
index 4c09e68..d69262e 100644
--- a/docs/components/modules/ROOT/pages/test.adoc
+++ b/docs/components/modules/ROOT/pages/test.adoc
@@ -7,7 +7,7 @@ notoriously difficult. The Mock, Test
and 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/xquery-component.adoc b/docs/components/modules/ROOT/pages/xquery-component.adoc
index 8072631..5ad9e2f 100644
--- a/docs/components/modules/ROOT/pages/xquery-component.adoc
+++ b/docs/components/modules/ROOT/pages/xquery-component.adoc
@@ -9,7 +9,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/docs/components/modules/ROOT/pages/xquery-language.adoc b/docs/components/modules/ROOT/pages/xquery-language.adoc
index 92cb61a..3692474 100644
--- a/docs/components/modules/ROOT/pages/xquery-language.adoc
+++ b/docs/components/modules/ROOT/pages/xquery-language.adoc
@@ -9,7 +9,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.