This is an automated email from the ASF dual-hosted git repository.
djencks pushed a commit to branch camel-3.11.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-3.11.x by this push:
new 59fe07f [CAMEL-16992] stay in version in component-component xrefs
59fe07f is described below
commit 59fe07f792cc44ac3a4801491940d89444a9da46
Author: David Jencks <[email protected]>
AuthorDate: Fri Sep 17 23:01:07 2021 -0700
[CAMEL-16992] stay in version in component-component xrefs
---
.../resources/org/apache/camel/catalog/docs/bean-language.adoc | 6 +++---
.../org/apache/camel/catalog/docs/beanstalk-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/dataset-component.adoc | 2 +-
.../org/apache/camel/catalog/docs/dataset-test-component.adoc | 2 +-
.../org/apache/camel/catalog/docs/datasonnet-language.adoc | 4 ++--
.../org/apache/camel/catalog/docs/disruptor-component.adoc | 2 +-
.../org/apache/camel/catalog/docs/elasticsearch-rest-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/elsql-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/facebook-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/groovy-language.adoc | 6 +++---
.../resources/org/apache/camel/catalog/docs/jms-component.adoc | 4 ++--
.../src/generated/resources/org/apache/camel/catalog/docs/jta.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/language-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/mock-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/mvel-language.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/ognl-language.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/quartz-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/sjms-component.adoc | 4 ++--
.../resources/org/apache/camel/catalog/docs/sjms2-component.adoc | 4 ++--
.../resources/org/apache/camel/catalog/docs/spel-language.adoc | 4 ++--
.../org/apache/camel/catalog/docs/spring-event-component.adoc | 4 ++--
.../org/apache/camel/catalog/docs/spring-rabbitmq-component.adoc | 4 ++--
.../resources/org/apache/camel/catalog/docs/spring-summary.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/sql-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/xpath-language.adoc | 4 ++--
.../resources/org/apache/camel/catalog/docs/xquery-language.adoc | 4 ++--
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 +-
components/camel-datasonnet/src/main/docs/datasonnet-language.adoc | 4 ++--
components/camel-disruptor/src/main/docs/disruptor-component.adoc | 2 +-
.../src/main/docs/elasticsearch-rest-component.adoc | 2 +-
components/camel-elsql/src/main/docs/elsql-component.adoc | 2 +-
components/camel-facebook/src/main/docs/facebook-component.adoc | 2 +-
components/camel-groovy/src/main/docs/groovy-language.adoc | 6 +++---
components/camel-jms/src/main/docs/jms-component.adoc | 4 ++--
components/camel-jta/src/main/docs/jta.adoc | 2 +-
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-language.adoc | 4 ++--
components/camel-sjms/src/main/docs/sjms-component.adoc | 4 ++--
components/camel-sjms2/src/main/docs/sjms2-component.adoc | 4 ++--
.../src/main/docs/spring-rabbitmq-component.adoc | 4 ++--
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-summary.adoc | 2 +-
components/camel-sql/src/main/docs/sql-component.adoc | 2 +-
components/camel-xpath/src/main/docs/xpath-language.adoc | 4 ++--
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/disruptor-component.adoc | 2 +-
.../components/modules/ROOT/pages/elasticsearch-rest-component.adoc | 2 +-
docs/components/modules/ROOT/pages/elsql-component.adoc | 2 +-
docs/components/modules/ROOT/pages/facebook-component.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/quartz-component.adoc | 2 +-
docs/components/modules/ROOT/pages/sjms-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/sjms2-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/spring-event-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/spring-rabbitmq-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/spring-summary.adoc | 2 +-
docs/components/modules/ROOT/pages/sql-component.adoc | 2 +-
docs/components/modules/languages/pages/bean-language.adoc | 6 +++---
docs/components/modules/languages/pages/datasonnet-language.adoc | 4 ++--
docs/components/modules/languages/pages/groovy-language.adoc | 6 +++---
docs/components/modules/languages/pages/mvel-language.adoc | 2 +-
docs/components/modules/languages/pages/ognl-language.adoc | 2 +-
docs/components/modules/languages/pages/spel-language.adoc | 4 ++--
docs/components/modules/languages/pages/xpath-language.adoc | 4 ++--
docs/components/modules/languages/pages/xquery-language.adoc | 4 ++--
docs/components/modules/others/pages/jta.adoc | 2 +-
docs/components/modules/others/pages/yaml-dsl.adoc | 2 +-
dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc | 2 +-
80 files changed, 119 insertions(+), 119 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/bean-language.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/bean-language.adoc
index 8df7e6f..5c174c3 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/bean-language.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/bean-language.adoc
@@ -20,7 +20,7 @@ using the type of the message body and using any annotations
on the bean
methods.
The xref:manual::bean-binding.adoc[Bean Binding] rules are used to bind the
-xref:{eip-vc}:eips:message.adoc[Message] Exchange to the method parameters; so
you can
+xref: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.
@@ -113,7 +113,7 @@ public boolean isGoldCustomer(@Header(name = "foo") Integer
fooHeader) {...}
----
So you can bind parameters of the method to the Exchange, the
-xref:{eip-vc}:eips:message.adoc[Message] or individual headers, properties,
the body
+xref:eips:message.adoc[Message] or individual headers, properties, the body
or other expressions.
[[BeanLanguage-Non-RegistryBeans]]
@@ -184,7 +184,7 @@ We have some test cases you can look at if it'll help
is a JUnit test case showing the Java xref:manual::dsl.adoc[DSL] use of the
bean
expression being used in a filter
*
https://github.com/apache/camel/blob/main/components/camel-spring/src/test/resources/org/apache/camel/spring/processor/aggregator.xml[aggregator.xml]
-is a Spring XML test case for the
xref:{eip-vc}:eips:aggregate-eip.adoc[Aggregator] which
+is a Spring XML test case for the xref:eips:aggregate-eip.adoc[Aggregator]
which
uses a bean method call to test for the completion of the aggregation.
include::{page-component-version}@camel-spring-boot::page$bean-starter.adoc[]
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/beanstalk-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/beanstalk-component.adoc
index e9b4035..c99b5b1 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/beanstalk-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/beanstalk-component.adoc
@@ -163,7 +163,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:{eip-vc}:eips:polling-consumer.adoc[Polling
+The beanstalk consumer is a Scheduled xref: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/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dataset-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dataset-component.adoc
index fdb35cf..eb7f5e4 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dataset-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dataset-component.adoc
@@ -18,7 +18,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+xref:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's large range of Components
together with the powerful Bean Integration.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dataset-test-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dataset-test-component.adoc
index 29514cb..6814bc3 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dataset-test-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dataset-test-component.adoc
@@ -18,7 +18,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+xref:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's large range of Components
together with the powerful Bean Integration.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/datasonnet-language.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/datasonnet-language.adoc
index 03e8085..a3f5df9 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/datasonnet-language.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/datasonnet-language.adoc
@@ -14,9 +14,9 @@ xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicat
used in the xref:manual::dsl.adoc[DSL].
For example you could use DataSonnet to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
+Predicate in a xref:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
-xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
+xref:eips:recipientList-eip.adoc[Recipient List].
To use a DataSonnet expression use the following Java code:
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/disruptor-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/disruptor-component.adoc
index 209fd53..c45f8a2 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/disruptor-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/disruptor-component.adoc
@@ -199,7 +199,7 @@ without incurring significant latency spikes.
== Use of Request Reply
-The Disruptor component supports using
xref:{eip-vc}:eips:requestReply-eip.adoc[Request
+The Disruptor component supports using xref:eips:requestReply-eip.adoc[Request
Reply], where the caller will wait for the Async route to complete. For
instance:
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/elasticsearch-rest-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/elasticsearch-rest-component.adoc
index 54a1c8a..bdbd612 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/elasticsearch-rest-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/elasticsearch-rest-component.adoc
@@ -278,7 +278,7 @@ try (ElasticsearchScrollRequestIterator response =
template.requestBody("direct:
}
----
-xref:{eip-vc}:eips:split-eip.adoc[Split EIP] can also be used.
+xref:eips:split-eip.adoc[Split EIP] can also be used.
[source,java]
----
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/elsql-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/elsql-component.adoc
index 0930fd6..7bc2b39 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/elsql-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/elsql-component.adoc
@@ -20,7 +20,7 @@ This component uses `spring-jdbc` behind the scenes for the
actual SQL
handling.
This component can be used as a
-xref:{eip-vc}:eips:transactional-client.adoc[Transactional Client].
+xref:eips:transactional-client.adoc[Transactional Client].
Maven users will need to add the following dependency to their `pom.xml`
for this component:
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/facebook-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/facebook-component.adoc
index ad7e870..b851a942 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/facebook-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/facebook-component.adoc
@@ -327,7 +327,7 @@ facebook4j.PostUpdate body.
.to("facebook://postFeed/inBody=postUpdate);
----------------------------------------------------
-To poll, every 5 sec (You can set the
xref:{eip-vc}:eips:polling-consumer.adoc[polling
+To poll, every 5 sec (You can set the xref:eips:polling-consumer.adoc[polling
consumer] options by adding a prefix of "consumer"), all statuses on
your home feed:
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/groovy-language.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/groovy-language.adoc
index 5f489f2..f405579 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/groovy-language.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/groovy-language.adoc
@@ -14,9 +14,9 @@ xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicat
used in the xref:manual::dsl.adoc[DSL].
For example you could use Groovy to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
+Predicate in a xref:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
-xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
+xref:eips:recipientList-eip.adoc[Recipient List].
To use a Groovy expression use the following Java code
@@ -26,7 +26,7 @@ groovy("someGroovyExpression")
---------------------------------------
For example you could use the *groovy* function to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message Filter] or as an
Expression for a
+Predicate in a xref:eips:filter-eip.adoc[Message Filter] or as an Expression
for a
Recipient List
== Groovy Options
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jms-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jms-component.adoc
index ab8da2b..73b043c 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jms-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jms-component.adoc
@@ -510,7 +510,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:{eip-vc}:eips:dead-letter-channel.adoc[Dead Letter
+xref:jms-component.adoc[JMS] with a xref: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
@@ -1217,7 +1217,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:{eip-vc}:eips:requestReply-eip.adoc[Request
+transaction commits. Therefore to use xref: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/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jta.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jta.adoc
index 7c75f75..783b492 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jta.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jta.adoc
@@ -11,4 +11,4 @@
include::{cq-version}@camel-quarkus:ROOT:partial$reference/others/jta.adoc[opts=
The `camel-jta` component is used for integrating Camel's transaction support
with JTA.
-See more details in the
xref:{eip-vc}:eips:transactional-client.adoc[Transactional Client]
documentation.
+See more details in the xref:eips:transactional-client.adoc[Transactional
Client] documentation.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/language-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/language-component.adoc
index 29f4561..11ec97e 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/language-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/language-component.adoc
@@ -18,7 +18,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:{eip-vc}:eips:dynamicRouter-eip.adoc[Dynamic
+Routing Slip or xref:eips:dynamicRouter-eip.adoc[Dynamic
Router] EIPs you can send messages to `language` endpoints where the
script is dynamic defined as well.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mock-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mock-component.adoc
index 1fc3947..9c7e135 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mock-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mock-component.adoc
@@ -18,7 +18,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+xref:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's large range of Components
together with the powerful Bean Integration.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mvel-language.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mvel-language.adoc
index 3957e8a..1ea70f5 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mvel-language.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/mvel-language.adoc
@@ -73,7 +73,7 @@ The MVEL language supports 1 options, which are listed below.
== Samples
-For example you could use Mvel inside a
xref:{eip-vc}:eips:filter-eip.adoc[Message
+For example you could use Mvel inside a xref:eips:filter-eip.adoc[Message
Filter] in XML
[source,java]
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ognl-language.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ognl-language.adoc
index 01d58ee..19367e8 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ognl-language.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ognl-language.adoc
@@ -77,7 +77,7 @@ The OGNL language supports 1 options, which are listed below.
== Samples
-For example you could use OGNL inside a
xref:{eip-vc}:eips:filter-eip.adoc[Message
+For example you could use OGNL inside a xref:eips:filter-eip.adoc[Message
Filter] in XML
[source,java]
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/quartz-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/quartz-component.adoc
index 672c2ad..7dac264 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/quartz-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/quartz-component.adoc
@@ -375,7 +375,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:{eip-vc}:eips:polling-consumer.adoc[Polling
+use cron based scheduling for xref:eips:polling-consumer.adoc[Polling
Consumer] such as the File and FTP
consumers.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sjms-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sjms-component.adoc
index 384ec40..9dba2f7 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sjms-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sjms-component.adoc
@@ -187,7 +187,7 @@ a message header. This allows Camel to reuse the same
endpoint, but send
to different destinations. This greatly reduces the number of endpoints
created and economizes on memory and thread resources.
-TIP: Using xref:{eip-vc}:eips:toD-eip.adoc[toD] is easier than specifying the
dynamic destination with a header
+TIP: Using xref:eips:toD-eip.adoc[toD] is easier than specifying the dynamic
destination with a header
You can specify the destination in the following headers:
@@ -236,7 +236,7 @@ another JMS endpoint).
If you need to send messages to a lot of different JMS destinations, it
makes sense to reuse a SJMS endpoint and specify the dynamic destinations
-with simple language using xref:{eip-vc}:eips:toD-eip.adoc[toD].
+with simple language using xref:eips:toD-eip.adoc[toD].
For example suppose you need to send messages to queues with order types,
then using toD could for example be done as follows:
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sjms2-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sjms2-component.adoc
index 2ac8caa..c78d74f 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sjms2-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sjms2-component.adoc
@@ -190,7 +190,7 @@ a message header. This allows Camel to reuse the same
endpoint, but send
to different destinations. This greatly reduces the number of endpoints
created and economizes on memory and thread resources.
-TIP: Using xref:{eip-vc}:eips:toD-eip.adoc[toD] is easier than specifying the
dynamic destination with a header
+TIP: Using xref:eips:toD-eip.adoc[toD] is easier than specifying the dynamic
destination with a header
You can specify the destination in the following headers:
@@ -239,7 +239,7 @@ another JMS endpoint).
If you need to send messages to a lot of different JMS destinations, it
makes sense to reuse a SJMS2 endpoint and specify the dynamic destinations
-with simple language using xref:{eip-vc}:eips:toD-eip.adoc[toD].
+with simple language using xref:eips:toD-eip.adoc[toD].
For example suppose you need to send messages to queues with order types,
then using toD could for example be done as follows:
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spel-language.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spel-language.adoc
index 120479c..291899f 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spel-language.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spel-language.adoc
@@ -126,8 +126,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:{eip-vc}:eips:recipientList-eip.adoc[Recipient
-List] or as a predicate inside a xref:{eip-vc}:eips:filter-eip.adoc[Message
+You can use SpEL as an expression for
xref:eips:recipientList-eip.adoc[Recipient
+List] or as a predicate inside a xref:eips:filter-eip.adoc[Message
Filter]:
[source,xml]
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spring-event-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spring-event-component.adoc
index 50b5776..974e744 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spring-event-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spring-event-component.adoc
@@ -18,8 +18,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
-Patterns] to process them such as xref:{eip-vc}:eips:filter-eip.adoc[Message
+xref:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns] to process them such as xref:eips:filter-eip.adoc[Message
Filter].
== URI format
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spring-rabbitmq-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spring-rabbitmq-component.adoc
index ea17fb5..ce8393a 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spring-rabbitmq-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spring-rabbitmq-component.adoc
@@ -265,7 +265,7 @@ a message header. This allows Camel to reuse the same
endpoint, but send
to different exchanges. This greatly reduces the number of endpoints
created and economizes on memory and thread resources.
-TIP: Using xref:{eip-vc}:eips:toD-eip.adoc[toD] is easier than specifying the
dynamic destination with headers
+TIP: Using xref:eips:toD-eip.adoc[toD] is easier than specifying the dynamic
destination with headers
You can specify using the following headers:
@@ -315,7 +315,7 @@ another RabbitMQ endpoint).
If you need to send messages to a lot of different exchanges, it
makes sense to reuse a endpoint and specify the dynamic destinations
-with simple language using xref:{eip-vc}:eips:toD-eip.adoc[toD].
+with simple language using xref:eips:toD-eip.adoc[toD].
For example suppose you need to send messages to exchanges with order types,
then using toD could for example be done as follows:
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spring-summary.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spring-summary.adoc
index f56472d..0eebfe0 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spring-summary.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/spring-summary.adoc
@@ -25,7 +25,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+xref:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's powerful xref:mock-component.adoc[Mock] and
xref:others:test.adoc[Test] endpoints
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sql-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sql-component.adoc
index 02b2bf8..532c4fb 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sql-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sql-component.adoc
@@ -46,7 +46,7 @@ pattern. See further below.
[TIP]
====
This component can be used as a
-xref:{eip-vc}:eips:transactional-client.adoc[Transactional Client].
+xref:eips:transactional-client.adoc[Transactional Client].
====
The SQL component uses the following endpoint URI notation:
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/xpath-language.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/xpath-language.adoc
index b1a9768..c636a55 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/xpath-language.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/xpath-language.adoc
@@ -14,9 +14,9 @@ xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicat
used in the xref:manual::dsl.adoc[DSL].
For example you could use XPath to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
+Predicate in a xref:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
-xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
+xref:eips:recipientList-eip.adoc[Recipient List].
*Streams*
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/xquery-language.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/xquery-language.adoc
index 76ccd4c..3dbdb94 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/xquery-language.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/xquery-language.adoc
@@ -14,9 +14,9 @@ xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicat
used in the xref:manual::dsl.adoc[DSL].
For example you could use XQuery to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
+Predicate in a xref:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
-xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
+xref:eips:recipientList-eip.adoc[Recipient List].
== XQuery Language options
diff --git a/components/camel-bean/src/main/docs/bean-language.adoc
b/components/camel-bean/src/main/docs/bean-language.adoc
index 8df7e6f..5c174c3 100644
--- a/components/camel-bean/src/main/docs/bean-language.adoc
+++ b/components/camel-bean/src/main/docs/bean-language.adoc
@@ -20,7 +20,7 @@ using the type of the message body and using any annotations
on the bean
methods.
The xref:manual::bean-binding.adoc[Bean Binding] rules are used to bind the
-xref:{eip-vc}:eips:message.adoc[Message] Exchange to the method parameters; so
you can
+xref: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.
@@ -113,7 +113,7 @@ public boolean isGoldCustomer(@Header(name = "foo") Integer
fooHeader) {...}
----
So you can bind parameters of the method to the Exchange, the
-xref:{eip-vc}:eips:message.adoc[Message] or individual headers, properties,
the body
+xref:eips:message.adoc[Message] or individual headers, properties, the body
or other expressions.
[[BeanLanguage-Non-RegistryBeans]]
@@ -184,7 +184,7 @@ We have some test cases you can look at if it'll help
is a JUnit test case showing the Java xref:manual::dsl.adoc[DSL] use of the
bean
expression being used in a filter
*
https://github.com/apache/camel/blob/main/components/camel-spring/src/test/resources/org/apache/camel/spring/processor/aggregator.xml[aggregator.xml]
-is a Spring XML test case for the
xref:{eip-vc}:eips:aggregate-eip.adoc[Aggregator] which
+is a Spring XML test case for the xref:eips:aggregate-eip.adoc[Aggregator]
which
uses a bean method call to test for the completion of the aggregation.
include::{page-component-version}@camel-spring-boot::page$bean-starter.adoc[]
diff --git a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
index e9b4035..c99b5b1 100644
--- a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
+++ b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
@@ -163,7 +163,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:{eip-vc}:eips:polling-consumer.adoc[Polling
+The beanstalk consumer is a Scheduled xref: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 fdb35cf..eb7f5e4 100644
--- a/components/camel-dataset/src/main/docs/dataset-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-component.adoc
@@ -18,7 +18,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+xref: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 29514cb..6814bc3 100644
--- a/components/camel-dataset/src/main/docs/dataset-test-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
@@ -18,7 +18,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+xref: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-datasonnet/src/main/docs/datasonnet-language.adoc
b/components/camel-datasonnet/src/main/docs/datasonnet-language.adoc
index 03e8085..a3f5df9 100644
--- a/components/camel-datasonnet/src/main/docs/datasonnet-language.adoc
+++ b/components/camel-datasonnet/src/main/docs/datasonnet-language.adoc
@@ -14,9 +14,9 @@ xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicat
used in the xref:manual::dsl.adoc[DSL].
For example you could use DataSonnet to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
+Predicate in a xref:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
-xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
+xref:eips:recipientList-eip.adoc[Recipient List].
To use a DataSonnet expression use the following Java code:
diff --git a/components/camel-disruptor/src/main/docs/disruptor-component.adoc
b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
index 209fd53..c45f8a2 100644
--- a/components/camel-disruptor/src/main/docs/disruptor-component.adoc
+++ b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
@@ -199,7 +199,7 @@ without incurring significant latency spikes.
== Use of Request Reply
-The Disruptor component supports using
xref:{eip-vc}:eips:requestReply-eip.adoc[Request
+The Disruptor component supports using xref: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 54a1c8a..bdbd612 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
@@ -278,7 +278,7 @@ try (ElasticsearchScrollRequestIterator response =
template.requestBody("direct:
}
----
-xref:{eip-vc}:eips:split-eip.adoc[Split EIP] can also be used.
+xref:eips:split-eip.adoc[Split EIP] can also be used.
[source,java]
----
diff --git a/components/camel-elsql/src/main/docs/elsql-component.adoc
b/components/camel-elsql/src/main/docs/elsql-component.adoc
index 0930fd6..7bc2b39 100644
--- a/components/camel-elsql/src/main/docs/elsql-component.adoc
+++ b/components/camel-elsql/src/main/docs/elsql-component.adoc
@@ -20,7 +20,7 @@ This component uses `spring-jdbc` behind the scenes for the
actual SQL
handling.
This component can be used as a
-xref:{eip-vc}:eips:transactional-client.adoc[Transactional Client].
+xref:eips:transactional-client.adoc[Transactional Client].
Maven users will need to add the following dependency to their `pom.xml`
for this component:
diff --git a/components/camel-facebook/src/main/docs/facebook-component.adoc
b/components/camel-facebook/src/main/docs/facebook-component.adoc
index ad7e870..b851a942 100644
--- a/components/camel-facebook/src/main/docs/facebook-component.adoc
+++ b/components/camel-facebook/src/main/docs/facebook-component.adoc
@@ -327,7 +327,7 @@ facebook4j.PostUpdate body.
.to("facebook://postFeed/inBody=postUpdate);
----------------------------------------------------
-To poll, every 5 sec (You can set the
xref:{eip-vc}:eips:polling-consumer.adoc[polling
+To poll, every 5 sec (You can set the xref: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 5f489f2..f405579 100644
--- a/components/camel-groovy/src/main/docs/groovy-language.adoc
+++ b/components/camel-groovy/src/main/docs/groovy-language.adoc
@@ -14,9 +14,9 @@ xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicat
used in the xref:manual::dsl.adoc[DSL].
For example you could use Groovy to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
+Predicate in a xref:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
-xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
+xref:eips:recipientList-eip.adoc[Recipient List].
To use a Groovy expression use the following Java code
@@ -26,7 +26,7 @@ groovy("someGroovyExpression")
---------------------------------------
For example you could use the *groovy* function to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message Filter] or as an
Expression for a
+Predicate in a xref: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 ab8da2b..73b043c 100644
--- a/components/camel-jms/src/main/docs/jms-component.adoc
+++ b/components/camel-jms/src/main/docs/jms-component.adoc
@@ -510,7 +510,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:{eip-vc}:eips:dead-letter-channel.adoc[Dead Letter
+xref:jms-component.adoc[JMS] with a xref: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
@@ -1217,7 +1217,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:{eip-vc}:eips:requestReply-eip.adoc[Request
+transaction commits. Therefore to use xref: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-jta/src/main/docs/jta.adoc
b/components/camel-jta/src/main/docs/jta.adoc
index 7c75f75..783b492 100644
--- a/components/camel-jta/src/main/docs/jta.adoc
+++ b/components/camel-jta/src/main/docs/jta.adoc
@@ -11,4 +11,4 @@
include::{cq-version}@camel-quarkus:ROOT:partial$reference/others/jta.adoc[opts=
The `camel-jta` component is used for integrating Camel's transaction support
with JTA.
-See more details in the
xref:{eip-vc}:eips:transactional-client.adoc[Transactional Client]
documentation.
+See more details in the xref:eips:transactional-client.adoc[Transactional
Client] documentation.
diff --git a/components/camel-language/src/main/docs/language-component.adoc
b/components/camel-language/src/main/docs/language-component.adoc
index 29f4561..11ec97e 100644
--- a/components/camel-language/src/main/docs/language-component.adoc
+++ b/components/camel-language/src/main/docs/language-component.adoc
@@ -18,7 +18,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:{eip-vc}:eips:dynamicRouter-eip.adoc[Dynamic
+Routing Slip or xref:eips:dynamicRouter-eip.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 1fc3947..9c7e135 100644
--- a/components/camel-mock/src/main/docs/mock-component.adoc
+++ b/components/camel-mock/src/main/docs/mock-component.adoc
@@ -18,7 +18,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+xref: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 3957e8a..1ea70f5 100644
--- a/components/camel-mvel/src/main/docs/mvel-language.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-language.adoc
@@ -73,7 +73,7 @@ The MVEL language supports 1 options, which are listed below.
== Samples
-For example you could use Mvel inside a
xref:{eip-vc}:eips:filter-eip.adoc[Message
+For example you could use Mvel inside a xref: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 01d58ee..19367e8 100644
--- a/components/camel-ognl/src/main/docs/ognl-language.adoc
+++ b/components/camel-ognl/src/main/docs/ognl-language.adoc
@@ -77,7 +77,7 @@ The OGNL language supports 1 options, which are listed below.
== Samples
-For example you could use OGNL inside a
xref:{eip-vc}:eips:filter-eip.adoc[Message
+For example you could use OGNL inside a xref: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 672c2ad..7dac264 100644
--- a/components/camel-quartz/src/main/docs/quartz-component.adoc
+++ b/components/camel-quartz/src/main/docs/quartz-component.adoc
@@ -375,7 +375,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:{eip-vc}:eips:polling-consumer.adoc[Polling
+use cron based scheduling for xref:eips:polling-consumer.adoc[Polling
Consumer] such as the File and FTP
consumers.
diff --git a/components/camel-saxon/src/main/docs/xquery-language.adoc
b/components/camel-saxon/src/main/docs/xquery-language.adoc
index 76ccd4c..3dbdb94 100644
--- a/components/camel-saxon/src/main/docs/xquery-language.adoc
+++ b/components/camel-saxon/src/main/docs/xquery-language.adoc
@@ -14,9 +14,9 @@ xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicat
used in the xref:manual::dsl.adoc[DSL].
For example you could use XQuery to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
+Predicate in a xref:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
-xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
+xref:eips:recipientList-eip.adoc[Recipient List].
== XQuery Language options
diff --git a/components/camel-sjms/src/main/docs/sjms-component.adoc
b/components/camel-sjms/src/main/docs/sjms-component.adoc
index 384ec40..9dba2f7 100644
--- a/components/camel-sjms/src/main/docs/sjms-component.adoc
+++ b/components/camel-sjms/src/main/docs/sjms-component.adoc
@@ -187,7 +187,7 @@ a message header. This allows Camel to reuse the same
endpoint, but send
to different destinations. This greatly reduces the number of endpoints
created and economizes on memory and thread resources.
-TIP: Using xref:{eip-vc}:eips:toD-eip.adoc[toD] is easier than specifying the
dynamic destination with a header
+TIP: Using xref:eips:toD-eip.adoc[toD] is easier than specifying the dynamic
destination with a header
You can specify the destination in the following headers:
@@ -236,7 +236,7 @@ another JMS endpoint).
If you need to send messages to a lot of different JMS destinations, it
makes sense to reuse a SJMS endpoint and specify the dynamic destinations
-with simple language using xref:{eip-vc}:eips:toD-eip.adoc[toD].
+with simple language using xref:eips:toD-eip.adoc[toD].
For example suppose you need to send messages to queues with order types,
then using toD could for example be done as follows:
diff --git a/components/camel-sjms2/src/main/docs/sjms2-component.adoc
b/components/camel-sjms2/src/main/docs/sjms2-component.adoc
index 2ac8caa..c78d74f 100644
--- a/components/camel-sjms2/src/main/docs/sjms2-component.adoc
+++ b/components/camel-sjms2/src/main/docs/sjms2-component.adoc
@@ -190,7 +190,7 @@ a message header. This allows Camel to reuse the same
endpoint, but send
to different destinations. This greatly reduces the number of endpoints
created and economizes on memory and thread resources.
-TIP: Using xref:{eip-vc}:eips:toD-eip.adoc[toD] is easier than specifying the
dynamic destination with a header
+TIP: Using xref:eips:toD-eip.adoc[toD] is easier than specifying the dynamic
destination with a header
You can specify the destination in the following headers:
@@ -239,7 +239,7 @@ another JMS endpoint).
If you need to send messages to a lot of different JMS destinations, it
makes sense to reuse a SJMS2 endpoint and specify the dynamic destinations
-with simple language using xref:{eip-vc}:eips:toD-eip.adoc[toD].
+with simple language using xref:eips:toD-eip.adoc[toD].
For example suppose you need to send messages to queues with order types,
then using toD could for example be done as follows:
diff --git
a/components/camel-spring-rabbitmq/src/main/docs/spring-rabbitmq-component.adoc
b/components/camel-spring-rabbitmq/src/main/docs/spring-rabbitmq-component.adoc
index ea17fb5..ce8393a 100644
---
a/components/camel-spring-rabbitmq/src/main/docs/spring-rabbitmq-component.adoc
+++
b/components/camel-spring-rabbitmq/src/main/docs/spring-rabbitmq-component.adoc
@@ -265,7 +265,7 @@ a message header. This allows Camel to reuse the same
endpoint, but send
to different exchanges. This greatly reduces the number of endpoints
created and economizes on memory and thread resources.
-TIP: Using xref:{eip-vc}:eips:toD-eip.adoc[toD] is easier than specifying the
dynamic destination with headers
+TIP: Using xref:eips:toD-eip.adoc[toD] is easier than specifying the dynamic
destination with headers
You can specify using the following headers:
@@ -315,7 +315,7 @@ another RabbitMQ endpoint).
If you need to send messages to a lot of different exchanges, it
makes sense to reuse a endpoint and specify the dynamic destinations
-with simple language using xref:{eip-vc}:eips:toD-eip.adoc[toD].
+with simple language using xref:eips:toD-eip.adoc[toD].
For example suppose you need to send messages to exchanges with order types,
then using toD could for example be done as follows:
diff --git a/components/camel-spring/src/main/docs/spel-language.adoc
b/components/camel-spring/src/main/docs/spel-language.adoc
index 120479c..291899f 100644
--- a/components/camel-spring/src/main/docs/spel-language.adoc
+++ b/components/camel-spring/src/main/docs/spel-language.adoc
@@ -126,8 +126,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:{eip-vc}:eips:recipientList-eip.adoc[Recipient
-List] or as a predicate inside a xref:{eip-vc}:eips:filter-eip.adoc[Message
+You can use SpEL as an expression for
xref:eips:recipientList-eip.adoc[Recipient
+List] or as a predicate inside a xref: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 50b5776..974e744 100644
--- a/components/camel-spring/src/main/docs/spring-event-component.adoc
+++ b/components/camel-spring/src/main/docs/spring-event-component.adoc
@@ -18,8 +18,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
-Patterns] to process them such as xref:{eip-vc}:eips:filter-eip.adoc[Message
+xref:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns] to process them such as xref:eips:filter-eip.adoc[Message
Filter].
== URI format
diff --git a/components/camel-spring/src/main/docs/spring-summary.adoc
b/components/camel-spring/src/main/docs/spring-summary.adoc
index f56472d..0eebfe0 100644
--- a/components/camel-spring/src/main/docs/spring-summary.adoc
+++ b/components/camel-spring/src/main/docs/spring-summary.adoc
@@ -25,7 +25,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+xref:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's powerful xref:mock-component.adoc[Mock] and
xref:others:test.adoc[Test] endpoints
diff --git a/components/camel-sql/src/main/docs/sql-component.adoc
b/components/camel-sql/src/main/docs/sql-component.adoc
index 02b2bf8..532c4fb 100644
--- a/components/camel-sql/src/main/docs/sql-component.adoc
+++ b/components/camel-sql/src/main/docs/sql-component.adoc
@@ -46,7 +46,7 @@ pattern. See further below.
[TIP]
====
This component can be used as a
-xref:{eip-vc}:eips:transactional-client.adoc[Transactional Client].
+xref:eips:transactional-client.adoc[Transactional Client].
====
The SQL component uses the following endpoint URI notation:
diff --git a/components/camel-xpath/src/main/docs/xpath-language.adoc
b/components/camel-xpath/src/main/docs/xpath-language.adoc
index b1a9768..c636a55 100644
--- a/components/camel-xpath/src/main/docs/xpath-language.adoc
+++ b/components/camel-xpath/src/main/docs/xpath-language.adoc
@@ -14,9 +14,9 @@ xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicat
used in the xref:manual::dsl.adoc[DSL].
For example you could use XPath to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
+Predicate in a xref:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
-xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
+xref:eips:recipientList-eip.adoc[Recipient List].
*Streams*
diff --git a/docs/components/modules/ROOT/pages/beanstalk-component.adoc
b/docs/components/modules/ROOT/pages/beanstalk-component.adoc
index 6134c94..f9702e5 100644
--- a/docs/components/modules/ROOT/pages/beanstalk-component.adoc
+++ b/docs/components/modules/ROOT/pages/beanstalk-component.adoc
@@ -165,7 +165,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:{eip-vc}:eips:polling-consumer.adoc[Polling
+The beanstalk consumer is a Scheduled xref: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 76c5132..d1f0dea 100644
--- a/docs/components/modules/ROOT/pages/dataset-component.adoc
+++ b/docs/components/modules/ROOT/pages/dataset-component.adoc
@@ -20,7 +20,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+xref: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 c8ed978..d11bfd4 100644
--- a/docs/components/modules/ROOT/pages/dataset-test-component.adoc
+++ b/docs/components/modules/ROOT/pages/dataset-test-component.adoc
@@ -20,7 +20,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+xref: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/disruptor-component.adoc
b/docs/components/modules/ROOT/pages/disruptor-component.adoc
index 24f8836..51ba5ac 100644
--- a/docs/components/modules/ROOT/pages/disruptor-component.adoc
+++ b/docs/components/modules/ROOT/pages/disruptor-component.adoc
@@ -201,7 +201,7 @@ without incurring significant latency spikes.
== Use of Request Reply
-The Disruptor component supports using
xref:{eip-vc}:eips:requestReply-eip.adoc[Request
+The Disruptor component supports using xref: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 0746af7..a5fdbdf 100644
--- a/docs/components/modules/ROOT/pages/elasticsearch-rest-component.adoc
+++ b/docs/components/modules/ROOT/pages/elasticsearch-rest-component.adoc
@@ -280,7 +280,7 @@ try (ElasticsearchScrollRequestIterator response =
template.requestBody("direct:
}
----
-xref:{eip-vc}:eips:split-eip.adoc[Split EIP] can also be used.
+xref:eips:split-eip.adoc[Split EIP] can also be used.
[source,java]
----
diff --git a/docs/components/modules/ROOT/pages/elsql-component.adoc
b/docs/components/modules/ROOT/pages/elsql-component.adoc
index 183f198..6d09f9c 100644
--- a/docs/components/modules/ROOT/pages/elsql-component.adoc
+++ b/docs/components/modules/ROOT/pages/elsql-component.adoc
@@ -22,7 +22,7 @@ This component uses `spring-jdbc` behind the scenes for the
actual SQL
handling.
This component can be used as a
-xref:{eip-vc}:eips:transactional-client.adoc[Transactional Client].
+xref:eips:transactional-client.adoc[Transactional Client].
Maven users will need to add the following dependency to their `pom.xml`
for this component:
diff --git a/docs/components/modules/ROOT/pages/facebook-component.adoc
b/docs/components/modules/ROOT/pages/facebook-component.adoc
index 719b7ca..c02a311 100644
--- a/docs/components/modules/ROOT/pages/facebook-component.adoc
+++ b/docs/components/modules/ROOT/pages/facebook-component.adoc
@@ -329,7 +329,7 @@ facebook4j.PostUpdate body.
.to("facebook://postFeed/inBody=postUpdate);
----------------------------------------------------
-To poll, every 5 sec (You can set the
xref:{eip-vc}:eips:polling-consumer.adoc[polling
+To poll, every 5 sec (You can set the xref: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/jms-component.adoc
b/docs/components/modules/ROOT/pages/jms-component.adoc
index fdfa6ee..640d7ff 100644
--- a/docs/components/modules/ROOT/pages/jms-component.adoc
+++ b/docs/components/modules/ROOT/pages/jms-component.adoc
@@ -512,7 +512,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:{eip-vc}:eips:dead-letter-channel.adoc[Dead Letter
+xref:jms-component.adoc[JMS] with a xref: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
@@ -1219,7 +1219,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:{eip-vc}:eips:requestReply-eip.adoc[Request
+transaction commits. Therefore to use xref: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 d4c300c..0a6d8ee 100644
--- a/docs/components/modules/ROOT/pages/language-component.adoc
+++ b/docs/components/modules/ROOT/pages/language-component.adoc
@@ -20,7 +20,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:{eip-vc}:eips:dynamicRouter-eip.adoc[Dynamic
+Routing Slip or xref:eips:dynamicRouter-eip.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 5f002e5..463ec7f 100644
--- a/docs/components/modules/ROOT/pages/mock-component.adoc
+++ b/docs/components/modules/ROOT/pages/mock-component.adoc
@@ -20,7 +20,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+xref: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/quartz-component.adoc
b/docs/components/modules/ROOT/pages/quartz-component.adoc
index c3eed9d..7bf81e5 100644
--- a/docs/components/modules/ROOT/pages/quartz-component.adoc
+++ b/docs/components/modules/ROOT/pages/quartz-component.adoc
@@ -377,7 +377,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:{eip-vc}:eips:polling-consumer.adoc[Polling
+use cron based scheduling for xref:eips:polling-consumer.adoc[Polling
Consumer] such as the File and FTP
consumers.
diff --git a/docs/components/modules/ROOT/pages/sjms-component.adoc
b/docs/components/modules/ROOT/pages/sjms-component.adoc
index 32a094b..e4ba035 100644
--- a/docs/components/modules/ROOT/pages/sjms-component.adoc
+++ b/docs/components/modules/ROOT/pages/sjms-component.adoc
@@ -189,7 +189,7 @@ a message header. This allows Camel to reuse the same
endpoint, but send
to different destinations. This greatly reduces the number of endpoints
created and economizes on memory and thread resources.
-TIP: Using xref:{eip-vc}:eips:toD-eip.adoc[toD] is easier than specifying the
dynamic destination with a header
+TIP: Using xref:eips:toD-eip.adoc[toD] is easier than specifying the dynamic
destination with a header
You can specify the destination in the following headers:
@@ -238,7 +238,7 @@ another JMS endpoint).
If you need to send messages to a lot of different JMS destinations, it
makes sense to reuse a SJMS endpoint and specify the dynamic destinations
-with simple language using xref:{eip-vc}:eips:toD-eip.adoc[toD].
+with simple language using xref:eips:toD-eip.adoc[toD].
For example suppose you need to send messages to queues with order types,
then using toD could for example be done as follows:
diff --git a/docs/components/modules/ROOT/pages/sjms2-component.adoc
b/docs/components/modules/ROOT/pages/sjms2-component.adoc
index 1e2dce0..a0f4b50 100644
--- a/docs/components/modules/ROOT/pages/sjms2-component.adoc
+++ b/docs/components/modules/ROOT/pages/sjms2-component.adoc
@@ -192,7 +192,7 @@ a message header. This allows Camel to reuse the same
endpoint, but send
to different destinations. This greatly reduces the number of endpoints
created and economizes on memory and thread resources.
-TIP: Using xref:{eip-vc}:eips:toD-eip.adoc[toD] is easier than specifying the
dynamic destination with a header
+TIP: Using xref:eips:toD-eip.adoc[toD] is easier than specifying the dynamic
destination with a header
You can specify the destination in the following headers:
@@ -241,7 +241,7 @@ another JMS endpoint).
If you need to send messages to a lot of different JMS destinations, it
makes sense to reuse a SJMS2 endpoint and specify the dynamic destinations
-with simple language using xref:{eip-vc}:eips:toD-eip.adoc[toD].
+with simple language using xref:eips:toD-eip.adoc[toD].
For example suppose you need to send messages to queues with order types,
then using toD could for example be done as follows:
diff --git a/docs/components/modules/ROOT/pages/spring-event-component.adoc
b/docs/components/modules/ROOT/pages/spring-event-component.adoc
index 7caa430..b215d05 100644
--- a/docs/components/modules/ROOT/pages/spring-event-component.adoc
+++ b/docs/components/modules/ROOT/pages/spring-event-component.adoc
@@ -20,8 +20,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
-Patterns] to process them such as xref:{eip-vc}:eips:filter-eip.adoc[Message
+xref:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns] to process them such as xref:eips:filter-eip.adoc[Message
Filter].
== URI format
diff --git a/docs/components/modules/ROOT/pages/spring-rabbitmq-component.adoc
b/docs/components/modules/ROOT/pages/spring-rabbitmq-component.adoc
index 966c31d..1918a60 100644
--- a/docs/components/modules/ROOT/pages/spring-rabbitmq-component.adoc
+++ b/docs/components/modules/ROOT/pages/spring-rabbitmq-component.adoc
@@ -267,7 +267,7 @@ a message header. This allows Camel to reuse the same
endpoint, but send
to different exchanges. This greatly reduces the number of endpoints
created and economizes on memory and thread resources.
-TIP: Using xref:{eip-vc}:eips:toD-eip.adoc[toD] is easier than specifying the
dynamic destination with headers
+TIP: Using xref:eips:toD-eip.adoc[toD] is easier than specifying the dynamic
destination with headers
You can specify using the following headers:
@@ -317,7 +317,7 @@ another RabbitMQ endpoint).
If you need to send messages to a lot of different exchanges, it
makes sense to reuse a endpoint and specify the dynamic destinations
-with simple language using xref:{eip-vc}:eips:toD-eip.adoc[toD].
+with simple language using xref:eips:toD-eip.adoc[toD].
For example suppose you need to send messages to exchanges with order types,
then using toD could for example be done as follows:
diff --git a/docs/components/modules/ROOT/pages/spring-summary.adoc
b/docs/components/modules/ROOT/pages/spring-summary.adoc
index 91c157e..83683f4 100644
--- a/docs/components/modules/ROOT/pages/spring-summary.adoc
+++ b/docs/components/modules/ROOT/pages/spring-summary.adoc
@@ -27,7 +27,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:{eip-vc}:eips:enterprise-integration-patterns.adoc[Enterprise Integration
+xref:eips:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's powerful xref:mock-component.adoc[Mock] and
xref:others:test.adoc[Test] endpoints
diff --git a/docs/components/modules/ROOT/pages/sql-component.adoc
b/docs/components/modules/ROOT/pages/sql-component.adoc
index 0d73401..02846d2 100644
--- a/docs/components/modules/ROOT/pages/sql-component.adoc
+++ b/docs/components/modules/ROOT/pages/sql-component.adoc
@@ -48,7 +48,7 @@ pattern. See further below.
[TIP]
====
This component can be used as a
-xref:{eip-vc}:eips:transactional-client.adoc[Transactional Client].
+xref:eips:transactional-client.adoc[Transactional Client].
====
The SQL component uses the following endpoint URI notation:
diff --git a/docs/components/modules/languages/pages/bean-language.adoc
b/docs/components/modules/languages/pages/bean-language.adoc
index 97a4ebc..71a5a99 100644
--- a/docs/components/modules/languages/pages/bean-language.adoc
+++ b/docs/components/modules/languages/pages/bean-language.adoc
@@ -22,7 +22,7 @@ using the type of the message body and using any annotations
on the bean
methods.
The xref:manual::bean-binding.adoc[Bean Binding] rules are used to bind the
-xref:{eip-vc}:eips:message.adoc[Message] Exchange to the method parameters; so
you can
+xref: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.
@@ -115,7 +115,7 @@ public boolean isGoldCustomer(@Header(name = "foo") Integer
fooHeader) {...}
----
So you can bind parameters of the method to the Exchange, the
-xref:{eip-vc}:eips:message.adoc[Message] or individual headers, properties,
the body
+xref:eips:message.adoc[Message] or individual headers, properties, the body
or other expressions.
[[BeanLanguage-Non-RegistryBeans]]
@@ -186,7 +186,7 @@ We have some test cases you can look at if it'll help
is a JUnit test case showing the Java xref:manual::dsl.adoc[DSL] use of the
bean
expression being used in a filter
*
https://github.com/apache/camel/blob/main/components/camel-spring/src/test/resources/org/apache/camel/spring/processor/aggregator.xml[aggregator.xml]
-is a Spring XML test case for the
xref:{eip-vc}:eips:aggregate-eip.adoc[Aggregator] which
+is a Spring XML test case for the xref:eips:aggregate-eip.adoc[Aggregator]
which
uses a bean method call to test for the completion of the aggregation.
include::{page-component-version}@camel-spring-boot::page$bean-starter.adoc[]
diff --git a/docs/components/modules/languages/pages/datasonnet-language.adoc
b/docs/components/modules/languages/pages/datasonnet-language.adoc
index fb832d1..fb6c79a 100644
--- a/docs/components/modules/languages/pages/datasonnet-language.adoc
+++ b/docs/components/modules/languages/pages/datasonnet-language.adoc
@@ -16,9 +16,9 @@ xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicat
used in the xref:manual::dsl.adoc[DSL].
For example you could use DataSonnet to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
+Predicate in a xref:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
-xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
+xref:eips:recipientList-eip.adoc[Recipient List].
To use a DataSonnet expression use the following Java code:
diff --git a/docs/components/modules/languages/pages/groovy-language.adoc
b/docs/components/modules/languages/pages/groovy-language.adoc
index 1e6abfa..8528f8e 100644
--- a/docs/components/modules/languages/pages/groovy-language.adoc
+++ b/docs/components/modules/languages/pages/groovy-language.adoc
@@ -16,9 +16,9 @@ xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicat
used in the xref:manual::dsl.adoc[DSL].
For example you could use Groovy to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
+Predicate in a xref:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
-xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
+xref:eips:recipientList-eip.adoc[Recipient List].
To use a Groovy expression use the following Java code
@@ -28,7 +28,7 @@ groovy("someGroovyExpression")
---------------------------------------
For example you could use the *groovy* function to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message Filter] or as an
Expression for a
+Predicate in a xref:eips:filter-eip.adoc[Message Filter] or as an Expression
for a
Recipient List
== Groovy Options
diff --git a/docs/components/modules/languages/pages/mvel-language.adoc
b/docs/components/modules/languages/pages/mvel-language.adoc
index 78b9160..05351ba 100644
--- a/docs/components/modules/languages/pages/mvel-language.adoc
+++ b/docs/components/modules/languages/pages/mvel-language.adoc
@@ -75,7 +75,7 @@ The MVEL language supports 1 options, which are listed below.
== Samples
-For example you could use Mvel inside a
xref:{eip-vc}:eips:filter-eip.adoc[Message
+For example you could use Mvel inside a xref:eips:filter-eip.adoc[Message
Filter] in XML
[source,java]
diff --git a/docs/components/modules/languages/pages/ognl-language.adoc
b/docs/components/modules/languages/pages/ognl-language.adoc
index 3a61734..a76989f 100644
--- a/docs/components/modules/languages/pages/ognl-language.adoc
+++ b/docs/components/modules/languages/pages/ognl-language.adoc
@@ -79,7 +79,7 @@ The OGNL language supports 1 options, which are listed below.
== Samples
-For example you could use OGNL inside a
xref:{eip-vc}:eips:filter-eip.adoc[Message
+For example you could use OGNL inside a xref:eips:filter-eip.adoc[Message
Filter] in XML
[source,java]
diff --git a/docs/components/modules/languages/pages/spel-language.adoc
b/docs/components/modules/languages/pages/spel-language.adoc
index 8fa40f9..2276bf1 100644
--- a/docs/components/modules/languages/pages/spel-language.adoc
+++ b/docs/components/modules/languages/pages/spel-language.adoc
@@ -128,8 +128,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:{eip-vc}:eips:recipientList-eip.adoc[Recipient
-List] or as a predicate inside a xref:{eip-vc}:eips:filter-eip.adoc[Message
+You can use SpEL as an expression for
xref:eips:recipientList-eip.adoc[Recipient
+List] or as a predicate inside a xref:eips:filter-eip.adoc[Message
Filter]:
[source,xml]
diff --git a/docs/components/modules/languages/pages/xpath-language.adoc
b/docs/components/modules/languages/pages/xpath-language.adoc
index 705905e..d856a73 100644
--- a/docs/components/modules/languages/pages/xpath-language.adoc
+++ b/docs/components/modules/languages/pages/xpath-language.adoc
@@ -16,9 +16,9 @@ xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicat
used in the xref:manual::dsl.adoc[DSL].
For example you could use XPath to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
+Predicate in a xref:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
-xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
+xref:eips:recipientList-eip.adoc[Recipient List].
*Streams*
diff --git a/docs/components/modules/languages/pages/xquery-language.adoc
b/docs/components/modules/languages/pages/xquery-language.adoc
index 0a82120..eec7c00 100644
--- a/docs/components/modules/languages/pages/xquery-language.adoc
+++ b/docs/components/modules/languages/pages/xquery-language.adoc
@@ -16,9 +16,9 @@ xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicat
used in the xref:manual::dsl.adoc[DSL].
For example you could use XQuery to create an
-Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
+Predicate in a xref:eips:filter-eip.adoc[Message
Filter] or as an Expression for a
-xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
+xref:eips:recipientList-eip.adoc[Recipient List].
== XQuery Language options
diff --git a/docs/components/modules/others/pages/jta.adoc
b/docs/components/modules/others/pages/jta.adoc
index 3ee1e1c..bab5ef6 100644
--- a/docs/components/modules/others/pages/jta.adoc
+++ b/docs/components/modules/others/pages/jta.adoc
@@ -13,4 +13,4 @@
include::{cq-version}@camel-quarkus:ROOT:partial$reference/others/jta.adoc[opts=
The `camel-jta` component is used for integrating Camel's transaction support
with JTA.
-See more details in the
xref:{eip-vc}:eips:transactional-client.adoc[Transactional Client]
documentation.
+See more details in the xref:eips:transactional-client.adoc[Transactional
Client] documentation.
diff --git a/docs/components/modules/others/pages/yaml-dsl.adoc
b/docs/components/modules/others/pages/yaml-dsl.adoc
index 029daf8..f0569fb 100644
--- a/docs/components/modules/others/pages/yaml-dsl.adoc
+++ b/docs/components/modules/others/pages/yaml-dsl.adoc
@@ -169,7 +169,7 @@ Support for Endpoint DSL auto completion
https://github.com/apache/camel-k-runti
== Defining beans
-In addition to the general support for creating beans provided by
xref:latest@components:others:main.adoc#_specifying_custom_beans[Camel Main],
the YAML DSL provide a convenient syntax to define and configure them:
+In addition to the general support for creating beans provided by
xref:main.adoc#_specifying_custom_beans[Camel Main], the YAML DSL provide a
convenient syntax to define and configure them:
[source,yaml]
----
diff --git a/dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc
b/dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc
index 080603d..6ab3160 100644
--- a/dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc
+++ b/dsl/camel-yaml-dsl/camel-yaml-dsl/src/main/docs/yaml-dsl.adoc
@@ -167,7 +167,7 @@ Support for Endpoint DSL auto completion
https://github.com/apache/camel-k-runti
== Defining beans
-In addition to the general support for creating beans provided by
xref:latest@components:others:main.adoc#_specifying_custom_beans[Camel Main],
the YAML DSL provide a convenient syntax to define and configure them:
+In addition to the general support for creating beans provided by
xref:others:main.adoc#_specifying_custom_beans[Camel Main], the YAML DSL
provide a convenient syntax to define and configure them:
[source,yaml]
----
