This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit f4624cb1be9e84625834e662d9542d631fa1ad19
Author: nayananga@acerubuntu18.04 <nayanangamuhandi...@gmail.com>
AuthorDate: Fri Jul 19 17:33:26 2019 +0530
Fixed cross references in camel/components
---
.../camel-ahc/src/main/docs/ahc-component.adoc | 2 +-
.../src/main/docs/cometd-component.adoc | 2 +-
.../src/main/docs/controlbus-component.adoc | 4 ++--
.../src/main/docs/crypto-component.adoc | 2 +-
.../src/main/docs/dataformat-component.adoc | 6 ++---
.../src/main/docs/dataset-component.adoc | 2 +-
.../src/main/docs/dataset-test-component.adoc | 2 +-
.../main/docs/elasticsearch-rest-component.adoc | 2 +-
.../camel-elsql/src/main/docs/elsql-component.adoc | 2 +-
.../camel-file/src/main/docs/file-component.adoc | 26 +++++++++++-----------
.../camel-grape/src/main/docs/grape-component.adoc | 2 +-
.../src/main/docs/groovy-language.adoc | 2 +-
.../camel-http4/src/main/docs/http4-component.adoc | 2 +-
.../camel-irc/src/main/docs/irc-component.adoc | 2 +-
.../camel-jetty/src/main/docs/jetty-component.adoc | 4 ++--
.../camel-jms/src/main/docs/jms-component.adoc | 2 +-
.../src/main/docs/language-component.adoc | 4 ++--
.../camel-mail/src/main/docs/mail-component.adoc | 2 +-
.../camel-mock/src/main/docs/mock-component.adoc | 2 +-
.../src/main/docs/netty4-component.adoc | 2 +-
.../camel-paho/src/main/docs/paho-component.adoc | 2 +-
.../src/main/docs/properties-component.adoc | 8 +++----
.../src/main/docs/xquery-component.adoc | 2 +-
.../camel-saxon/src/main/docs/xquery-language.adoc | 2 +-
.../src/main/docs/spring-event-component.adoc | 2 +-
components/camel-spring/src/main/docs/spring.adoc | 8 +++----
.../src/main/docs/univocity-csv-dataformat.adoc | 2 +-
.../src/main/docs/univocity-fixed-dataformat.adoc | 2 +-
.../src/main/docs/univocity-tsv-dataformat.adoc | 2 +-
.../src/main/docs/websocket-component.adoc | 2 +-
.../src/main/docs/xmlsecurity-component.adoc | 2 +-
.../camel-xpath/src/main/docs/xpath-language.adoc | 4 ++--
32 files changed, 56 insertions(+), 56 deletions(-)
diff --git a/components/camel-ahc/src/main/docs/ahc-component.adoc
b/components/camel-ahc/src/main/docs/ahc-component.adoc
index 98a9606..5b9e91e 100644
--- a/components/camel-ahc/src/main/docs/ahc-component.adoc
+++ b/components/camel-ahc/src/main/docs/ahc-component.adoc
@@ -421,7 +421,7 @@ from("direct:start")
Using the JSSE Configuration Utility
The AHC component supports SSL/TLS configuration
-through the xref:camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-cometd/src/main/docs/cometd-component.adoc
b/components/camel-cometd/src/main/docs/cometd-component.adoc
index 8130b70..2d05c59 100644
--- a/components/camel-cometd/src/main/docs/cometd-component.adoc
+++ b/components/camel-cometd/src/main/docs/cometd-component.adoc
@@ -183,7 +183,7 @@
http://cometd.org/documentation/howtos/authentication[documented here]
#### Using the JSSE Configuration Utility
The Cometd component supports SSL/TLS configuration
-through the xref:camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git
a/components/camel-controlbus/src/main/docs/controlbus-component.adoc
b/components/camel-controlbus/src/main/docs/controlbus-component.adoc
index 0a605aa..cfd64bf 100644
--- a/components/camel-controlbus/src/main/docs/controlbus-component.adoc
+++ b/components/camel-controlbus/src/main/docs/controlbus-component.adoc
@@ -185,7 +185,7 @@ String xml =
template.requestBody("controlbus:route?action=stats", null, String.
=== Using Simple language
-You can use the xref:simple-language.adoc[Simple] language with the control
bus,
+You can use the xref:manual::simple-language.adoc[Simple] language with the
control bus,
for example to stop a specific route, you can send a message to the
`"controlbus:language:simple"` endpoint containing the following
message:
@@ -206,7 +206,7 @@ String status =
template.requestBody("controlbus:language:simple", "${camelConte
It's easier to use the `route` command to control lifecycle of
routes. The `language` command allows you to execute a language script
that has stronger powers such as xref:groovy-language.adoc[Groovy] or to some
-extend the xref:simple-language.adoc[Simple] language.
+extend the xref:manual::simple-language.adoc[Simple] language.
For example to shutdown Camel itself you can do:
diff --git a/components/camel-crypto/src/main/docs/crypto-component.adoc
b/components/camel-crypto/src/main/docs/crypto-component.adoc
index b2c76df..5734dbe 100644
--- a/components/camel-crypto/src/main/docs/crypto-component.adoc
+++ b/components/camel-crypto/src/main/docs/crypto-component.adoc
@@ -213,7 +213,7 @@ The component supports 34 options, which are listed below.
The most basic way to way to sign and verify an exchange is with a
KeyPair as follows.
-The same can be achieved with the xref:spring-xml-extensions.adoc[Spring
+The same can be achieved with the
xref:manual::spring-xml-extensions.adoc[Spring
XML Extensions] using references to keys
#### KeyStores and Aliases.
diff --git
a/components/camel-dataformat/src/main/docs/dataformat-component.adoc
b/components/camel-dataformat/src/main/docs/dataformat-component.adoc
index d523fa6..09bce42 100644
--- a/components/camel-dataformat/src/main/docs/dataformat-component.adoc
+++ b/components/camel-dataformat/src/main/docs/dataformat-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.12*
-The Dataformat component allows to use xref:data-format.adoc[Data
+The Dataformat component allows to use xref:manual::data-format.adoc[Data
Format] as a Camel Component.
=== URI format
@@ -15,7 +15,7 @@ dataformat:name:(marshal|unmarshal)[?options]
Where *name* is the name of the Data Format. And
then followed by the operation which must either be `marshal` or
-`unmarshal`. The options is used for configuring the xref:data-format.adoc[Data
+`unmarshal`. The options is used for configuring the
xref:manual::data-format.adoc[Data
Format] in use. See the Data Format documentation
for which options it support.
@@ -100,7 +100,7 @@ The component supports 3 options, which are listed below.
=== Samples
-For example to use the xref:jaxb-dataformat.adoc[JAXB]
xref:data-format.adoc[Data
+For example to use the xref:jaxb-dataformat.adoc[JAXB]
xref:manual::data-format.adoc[Data
Format] we can do as follows:
[source,java]
diff --git a/components/camel-dataset/src/main/docs/dataset-component.adoc
b/components/camel-dataset/src/main/docs/dataset-component.adoc
index 3469c30..290a296 100644
--- a/components/camel-dataset/src/main/docs/dataset-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-component.adoc
@@ -8,7 +8,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:enterprise-integration-patterns.adoc[Enterprise Integration
+xref:manual::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 1d88d7ca..da5eb9b 100644
--- a/components/camel-dataset/src/main/docs/dataset-test-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
@@ -8,7 +8,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:enterprise-integration-patterns.adoc[Enterprise Integration
+xref:manual::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-elasticsearch-rest/src/main/docs/elasticsearch-rest-component.adoc
b/components/camel-elasticsearch-rest/src/main/docs/elasticsearch-rest-component.adoc
index 935c7e6..5b691ee 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
@@ -303,7 +303,7 @@ try (ElasticsearchScrollRequestIterator response =
template.requestBody("direct:
}
----
-xref:split-eip.adoc[Split EIP] can also be used.
+xref:manual::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 61c253a..59dfc8c 100644
--- a/components/camel-elsql/src/main/docs/elsql-component.adoc
+++ b/components/camel-elsql/src/main/docs/elsql-component.adoc
@@ -40,7 +40,7 @@ The parameters to the SQL queries are named parameters in the
elsql
mapping files, and maps to corresponding keys from the Camel message, in
the given precedence:
-1. from message body if xref:simple-language.adoc[Simple]
+1. from message body if xref:manual::simple-language.adoc[Simple]
expression.
2. from message body if its a `java.util.Map`
diff --git a/components/camel-file/src/main/docs/file-component.adoc
b/components/camel-file/src/main/docs/file-component.adoc
index 0878732e..bbbe5a6 100644
--- a/components/camel-file/src/main/docs/file-component.adoc
+++ b/components/camel-file/src/main/docs/file-component.adoc
@@ -237,7 +237,7 @@ bean completes, and thus the route is completed, the file
consumer will
perform the move operation and move the file to the `.done` sub-folder.
The *move* and the *preMove* options are considered as a directory name
-(though if you use an expression such as xref:file-language.adoc[File
Language], or xref:simple-language.adoc[Simple] then the result of the
expression
+(though if you use an expression such as xref:manual::file-language.adoc[File
Language], or xref:manual::simple-language.adoc[Simple] then the result of the
expression
evaluation is the file name to be used - eg if you set
[source]
@@ -245,7 +245,7 @@ evaluation is the file name to be used - eg if you set
move=../backup/copy-of-${file:name}
----
-then that's using the xref:file-language.adoc[File Language] which we
+then that's using the xref:manual::file-language.adoc[File Language] which we
use return the file name to be used), which can be either relative or
absolute. If relative, the directory is created as a sub-folder from
within the folder where the file was consumed.
@@ -283,10 +283,10 @@ processed and after it's processed, it's moved to the
`.done` folder.
The *move* and *preMove* options
are Expression-based, so we have the full power of
-the xref:file-language.adoc[File Language] to do advanced configuration
+the xref:manual::file-language.adoc[File Language] to do advanced configuration
of the directory and name pattern. +
Camel will, in fact, internally convert the directory name you enter
-into a xref:file-language.adoc[File Language] expression. So when we
+into a xref:manual::file-language.adoc[File Language] expression. So when we
enter `move=.done` Camel will convert this into:
`\${file:parent}/.done/${file:onlyname}`. This is only done if
Camel detects that you have not provided a $\{ } in the option value
@@ -309,7 +309,7 @@ choice. For example to move the files in an error folder
with a
timestamp you can use
`moveFailed=/error/${``file:name.noext``}-${date:now:yyyyMMddHHmmssSSS}.${``file:ext`}.
-See more examples at xref:file-language.adoc[File Language]
+See more examples at xref:manual::file-language.adoc[File Language]
=== Message Headers
@@ -323,7 +323,7 @@ The following headers are supported by this component:
|`CamelFileName` |Specifies the name of the file to write (relative to the
endpoint
directory). This name can be a `String`; a `String` with a
-xref:file-language.adoc[File Language] or xref:simple-language.adoc[Simple]
+xref:manual::file-language.adoc[File Language] or
xref:manual::simple-language.adoc[Simple]
expression; or an Expression object. If it's
`null` then Camel will auto-generate a filename based on the message
unique ID.
@@ -530,8 +530,8 @@
from("direct:report").to("file:target/reports/?fileName=report.txt");
=== Filename Expression
Filename can be set either using the *expression* option or as a
-string-based xref:file-language.adoc[File Language] expression in the
-`CamelFileName` header. See the xref:file-language.adoc[File Language]
+string-based xref:manual::file-language.adoc[File Language] expression in the
+`CamelFileName` header. See the xref:manual::file-language.adoc[File Language]
for syntax and samples.
[[File2-Consumingfilesfromfolderswhereothersdropfilesdirectly]]
@@ -814,7 +814,7 @@ today's date as a sub-folder name:
from("file://inbox?move=backup/${date:now:yyyyMMdd}/${file:name}").to("...");
----
-See xref:file-language.adoc[File Language] for more samples.
+See xref:manual::file-language.adoc[File Language] for more samples.
=== Avoiding reading the same file more than once (idempotent consumer)
@@ -1011,7 +1011,7 @@ Registry for a bean with the ID, `mySorter`.
==== Sorting using sortBy
Camel supports pluggable sorting strategies. This strategy it to use the
-xref:file-language.adoc[File Language] to configure the sorting. The
+xref:manual::file-language.adoc[File Language] to configure the sorting. The
`sortBy` option is configured as follows:
[source]
@@ -1035,7 +1035,7 @@ This will sort by file name, you can reverse the order by
prefixing
sortBy=reverse:file:name
----
-As we have the full power of xref:file-language.adoc[File Language] we
+As we have the full power of xref:manual::file-language.adoc[File Language] we
can use some of the other parameters, so if we want to sort by file size
we do:
@@ -1079,7 +1079,7 @@ sortBy=file:modified;file:name
Now there is an issue here, can you spot it? Well the modified timestamp
of the file is too fine as it will be in milliseconds, but what if we
want to sort by date only and then subgroup by name? +
- Well as we have the true power of xref:file-language.adoc[File Language] we
can use its date command that supports patterns. So this
+ Well as we have the true power of xref:manual::file-language.adoc[File
Language] we can use its date command that supports patterns. So this
can be solved as:
[source]
@@ -1170,6 +1170,6 @@ problems.
=== See Also
-* xref:file-language.adoc[File Language]
+* xref:manual::file-language.adoc[File Language]
* FTP
* Polling Consumer
diff --git a/components/camel-grape/src/main/docs/grape-component.adoc
b/components/camel-grape/src/main/docs/grape-component.adoc
index 85a9708..5dbdaaa 100644
--- a/components/camel-grape/src/main/docs/grape-component.adoc
+++ b/components/camel-grape/src/main/docs/grape-component.adoc
@@ -132,7 +132,7 @@ By default Camel Grape component operates on the String
payloads:
producerTemplate.sendBody("grape:defaultMavenCoordinates",
"org.apache.camel/camel-ftp/2.15.2");
------------------------------------------------------------------------------------------------
-But of course Camel build-in xref:type-converter.adoc[type conversion
+But of course Camel build-in xref:manual::type-converter.adoc[type conversion
API] can perform the automatic data type transformations for you. In the
example below Camel automatically converts binary payload into the
String:
diff --git a/components/camel-groovy/src/main/docs/groovy-language.adoc
b/components/camel-groovy/src/main/docs/groovy-language.adoc
index cc62bba..e2c8000 100644
--- a/components/camel-groovy/src/main/docs/groovy-language.adoc
+++ b/components/camel-groovy/src/main/docs/groovy-language.adoc
@@ -6,7 +6,7 @@
Camel supports http://groovy.codehaus.org/[Groovy] among other
Scripting Languages to allow an
Expression or Predicate to be
-used in the DSL or xref:xml-configuration.adoc[Xml
+used in the DSL or xref:manual::xml-configuration.adoc[Xml
Configuration].
To use a Groovy expression use the following Java code
diff --git a/components/camel-http4/src/main/docs/http4-component.adoc
b/components/camel-http4/src/main/docs/http4-component.adoc
index 616a67e..a7e188b 100644
--- a/components/camel-http4/src/main/docs/http4-component.adoc
+++ b/components/camel-http4/src/main/docs/http4-component.adoc
@@ -565,7 +565,7 @@ behavior.
Using the JSSE Configuration Utility
The HTTP4 component supports SSL/TLS configuration
-through the xref:camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-irc/src/main/docs/irc-component.adoc
b/components/camel-irc/src/main/docs/irc-component.adoc
index 7fc0250..a07bfa7 100644
--- a/components/camel-irc/src/main/docs/irc-component.adoc
+++ b/components/camel-irc/src/main/docs/irc-component.adoc
@@ -150,7 +150,7 @@ The component supports 4 options, which are listed below.
#### Using the JSSE Configuration Utility
The IRC component supports SSL/TLS configuration
-through the xref:camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-jetty/src/main/docs/jetty-component.adoc
b/components/camel-jetty/src/main/docs/jetty-component.adoc
index e9e7cc5..5476b13 100644
--- a/components/camel-jetty/src/main/docs/jetty-component.adoc
+++ b/components/camel-jetty/src/main/docs/jetty-component.adoc
@@ -283,7 +283,7 @@ Jetty component will copy the HTTP request parameter, `one`
to the
exchange's `in.header`. We can then use the `simple` language to route
exchanges that contain this header to a specific endpoint and all others
to another. If we used a language more powerful than
-xref:simple-language.adoc[Simple] (such as xref:el-language.adoc[EL] or
+xref:manual::simple-language.adoc[Simple] (such as xref:el-language.adoc[EL] or
xref:ognl-language.adoc[OGNL]) we could also test for the parameter value and
do
routing based on the header value as well.
@@ -326,7 +326,7 @@ public void process(Exchange exchange) throws Exception {
Using the JSSE Configuration Utility
The Jetty component supports SSL/TLS configuration
-through the xref:camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-jms/src/main/docs/jms-component.adoc
b/components/camel-jms/src/main/docs/jms-component.adoc
index aed022e..f8d08ec 100644
--- a/components/camel-jms/src/main/docs/jms-component.adoc
+++ b/components/camel-jms/src/main/docs/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:dead-letter-channel.adoc[Dead Letter
+xref:jms-component.adoc[JMS] with a xref:manual::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
diff --git a/components/camel-language/src/main/docs/language-component.adoc
b/components/camel-language/src/main/docs/language-component.adoc
index dc3b08b..a3f0a81 100644
--- a/components/camel-language/src/main/docs/language-component.adoc
+++ b/components/camel-language/src/main/docs/language-component.adoc
@@ -8,7 +8,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:dynamic-router.adoc[Dynamic
+Routing Slip or xref:manual::dynamic-router.adoc[Dynamic
Router] EIPs you can send messages to `language` endpoints where the
script is dynamic defined as well.
@@ -132,7 +132,7 @@ script configured on the endpoint.
=== Examples
-For example you can use the xref:simple-language.adoc[Simple] language to
+For example you can use the xref:manual::simple-language.adoc[Simple] language
to
Message Translator a message:
In case you want to convert the message body type you can do this as
diff --git a/components/camel-mail/src/main/docs/mail-component.adoc
b/components/camel-mail/src/main/docs/mail-component.adoc
index 68dccfc..acb8b67 100644
--- a/components/camel-mail/src/main/docs/mail-component.adoc
+++ b/components/camel-mail/src/main/docs/mail-component.adoc
@@ -341,7 +341,7 @@ configuration.
==== Using the JSSE Configuration Utility
The mail component supports SSL/TLS configuration
-through the xref:camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-mock/src/main/docs/mock-component.adoc
b/components/camel-mock/src/main/docs/mock-component.adoc
index 5388d43..11c36a5 100644
--- a/components/camel-mock/src/main/docs/mock-component.adoc
+++ b/components/camel-mock/src/main/docs/mock-component.adoc
@@ -8,7 +8,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:enterprise-integration-patterns.adoc[Enterprise Integration
+xref:manual::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-netty4/src/main/docs/netty4-component.adoc
b/components/camel-netty4/src/main/docs/netty4-component.adoc
index 52d0ea9..40806ba 100644
--- a/components/camel-netty4/src/main/docs/netty4-component.adoc
+++ b/components/camel-netty4/src/main/docs/netty4-component.adoc
@@ -406,7 +406,7 @@ RouteBuilder builder = new RouteBuilder() {
Using the JSSE Configuration Utility
The Netty component supports SSL/TLS configuration
-through the xref:camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-paho/src/main/docs/paho-component.adoc
b/components/camel-paho/src/main/docs/paho-component.adoc
index cae5aa4..08bb67a 100644
--- a/components/camel-paho/src/main/docs/paho-component.adoc
+++ b/components/camel-paho/src/main/docs/paho-component.adoc
@@ -173,7 +173,7 @@ byte[] payload = "message".getBytes();
producerTemplate.sendBody("paho:topic", payload);
----
-But of course Camel build-in xref:type-converter.adoc[type conversion
+But of course Camel build-in xref:manual::type-converter.adoc[type conversion
API] can perform the automatic data type transformations for you. In the
example below Camel automatically converts binary payload into `String`
(and conversely):
diff --git
a/components/camel-properties/src/main/docs/properties-component.adoc
b/components/camel-properties/src/main/docs/properties-component.adoc
index a47fb77..7982075 100644
--- a/components/camel-properties/src/main/docs/properties-component.adoc
+++ b/components/camel-properties/src/main/docs/properties-component.adoc
@@ -390,9 +390,9 @@ ProducerTemplate for example:
template.sendBody("{{cool.start}}", "Hello World");
----
-=== Example with xref:simple-language.adoc[Simple] language
+=== Example with xref:manual::simple-language.adoc[Simple] language
-The xref:simple-language.adoc[Simple] language now also support using property
+The xref:manual::simple-language.adoc[Simple] language now also support using
property
placeholders, for example in the route below:
[source,java]
@@ -655,7 +655,7 @@ placeholder notation with `{{` and `}}`.
=== Clashing Spring property placeholders with Camels Simple language
Take notice when using Spring bridging placeholder then the spring `${ }`
-syntax clashes with the xref:simple-language.adoc[Simple] in Camel, and
therefore
+syntax clashes with the xref:manual::simple-language.adoc[Simple] in Camel,
and therefore
take care. For example:
[source,xml]
@@ -666,7 +666,7 @@ take care. For example:
----
clashes with Spring property placeholders, and you should use `$simple{ }`
-to indicate using the xref:simple-language.adoc[Simple] language in Camel.
+to indicate using the xref:manual::simple-language.adoc[Simple] language in
Camel.
[source,xml]
----
diff --git a/components/camel-saxon/src/main/docs/xquery-component.adoc
b/components/camel-saxon/src/main/docs/xquery-component.adoc
index 9a2e394..a55ec7c 100644
--- a/components/camel-saxon/src/main/docs/xquery-component.adoc
+++ b/components/camel-saxon/src/main/docs/xquery-component.adoc
@@ -5,7 +5,7 @@
Camel supports http://www.w3.org/TR/xquery/[XQuery] to allow an
Expression or Predicate to be
-used in the DSL or xref:xml-configuration.adoc[Xml
+used in the DSL or xref:manual::xml-configuration.adoc[Xml
Configuration]. For example you could use XQuery to create an
Predicate in a xref:message-filter.adoc[Message
Filter] or as an Expression for a
diff --git a/components/camel-saxon/src/main/docs/xquery-language.adoc
b/components/camel-saxon/src/main/docs/xquery-language.adoc
index 6b52fb5..bddfee1 100644
--- a/components/camel-saxon/src/main/docs/xquery-language.adoc
+++ b/components/camel-saxon/src/main/docs/xquery-language.adoc
@@ -5,7 +5,7 @@
Camel supports http://www.w3.org/TR/xquery/[XQuery] to allow an
Expression or Predicate to be
-used in the DSL or xref:xml-configuration.adoc[Xml
+used in the DSL or xref:manual::xml-configuration.adoc[Xml
Configuration]. For example you could use XQuery to create an
Predicate in a xref:message-filter.adoc[Message
Filter] or as an Expression for a
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 a166da2..ed628b1 100644
--- a/components/camel-spring/src/main/docs/spring-event-component.adoc
+++ b/components/camel-spring/src/main/docs/spring-event-component.adoc
@@ -7,7 +7,7 @@ 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:enterprise-integration-patterns.adoc[Enterprise Integration
+xref:manual::enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] to process them such as xref:message-filter.adoc[Message
Filter].
diff --git a/components/camel-spring/src/main/docs/spring.adoc
b/components/camel-spring/src/main/docs/spring.adoc
index f83baf7..6af9007 100644
--- a/components/camel-spring/src/main/docs/spring.adoc
+++ b/components/camel-spring/src/main/docs/spring.adoc
@@ -8,7 +8,7 @@ http://www.springframework.org/[Spring Framework] in a number
of ways.
components like xref:jms-component.adoc[JMS] and xref:jms-component.adoc[JPA]
* Camel works with Spring 2 XML processing with the
Xml Configuration
-* Camel Spring XML Schema's is defined at xref:xml-reference.adoc[Xml
+* Camel Spring XML Schema's is defined at xref:manual::xml-reference.adoc[Xml
Reference]
* Camel supports a powerful version of xref:spring-remoting.adoc[Spring
Remoting] which can use powerful routing between the client and server
@@ -24,7 +24,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:enterprise-integration-patterns.adoc[Enterprise Integration
+xref:manual::enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's powerful xref:mock-component.adoc[Mock] and
xref:test-component.adoc[Test] endpoints
Camel supports Spring Boot using the `camel-spring-boot` component.
@@ -228,7 +228,7 @@ above in the `<packageScan>` documentation.
*Available as of Camel 2.3*
-When defining routes in Camel using xref:xml-configuration.adoc[Xml
+When defining routes in Camel using xref:manual::xml-configuration.adoc[Xml
Configuration] you may want to define some routes in other XML files.
For example you may have many routes and it may help to maintain the
application if some of the routes are in separate XML files. You may
@@ -349,7 +349,7 @@ If you want to be injected with the CamelContext
in your POJO just implement the
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContextAware.html[CamelContextAware
interface]; then when Spring creates your POJO the CamelContext will be
-injected into your POJO. Also see the xref:bean-integration.adoc[Bean
+injected into your POJO. Also see the xref:manual::bean-integration.adoc[Bean
Integration] for further injections.
=== Integration Testing
diff --git
a/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
b/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
index c9911f8..651b44b 100644
---
a/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
+++
b/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.15*
-This xref:data-format.adoc[Data
+This xref:manual::data-format.adoc[Data
Format] uses http://www.univocity.com/pages/about-parsers[uniVocity-parsers]
for reading and writing 3 kinds of tabular data text files:
diff --git
a/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
b/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
index a54d9f4..c53c803 100644
---
a/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
+++
b/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.15*
-This xref:data-format.adoc[Data
+This xref:manual::data-format.adoc[Data
Format] uses http://www.univocity.com/pages/about-parsers[uniVocity-parsers]
for reading and writing 3 kinds of tabular data text files:
diff --git
a/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
b/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
index 8069fd1..ee5bc27 100644
---
a/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
+++
b/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.15*
-This xref:data-format.adoc[Data
+This xref:manual::data-format.adoc[Data
Format] uses http://www.univocity.com/pages/about-parsers[uniVocity-parsers]
for reading and writing 3 kinds of tabular data text files:
diff --git a/components/camel-websocket/src/main/docs/websocket-component.adoc
b/components/camel-websocket/src/main/docs/websocket-component.adoc
index 16f3864..604cf17 100644
--- a/components/camel-websocket/src/main/docs/websocket-component.adoc
+++ b/components/camel-websocket/src/main/docs/websocket-component.adoc
@@ -206,7 +206,7 @@ from("activemq:topic:newsTopic")
#### Using the JSSE Configuration Utility
The WebSocket component supports SSL/TLS configuration
-through the xref:camel-configuration-utilities.adoc[Camel JSSE
+through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git
a/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
b/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
index 0116b41..6bd9a79 100644
--- a/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
+++ b/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
@@ -8,7 +8,7 @@ signatures as described in the W3C standard
http://www.w3.org/TR/xmldsig-core/[XML Signature Syntax and Processing]
or as described in the successor
http://www.w3.org/TR/xmldsig-core1/[version 1.1]. For XML Encryption
-support, please refer to the XML Security xref:data-format.adoc[Data
+support, please refer to the XML Security xref:manual::data-format.adoc[Data
Format].
You can find an introduction to XML signature
diff --git a/components/camel-xpath/src/main/docs/xpath-language.adoc
b/components/camel-xpath/src/main/docs/xpath-language.adoc
index 5c673e3..68eee5a 100644
--- a/components/camel-xpath/src/main/docs/xpath-language.adoc
+++ b/components/camel-xpath/src/main/docs/xpath-language.adoc
@@ -5,7 +5,7 @@
Camel supports http://www.w3.org/TR/xpath[XPath] to allow an
Expression or Predicate to be
-used in the DSL or xref:xml-configuration.adoc[Xml
+used in the DSL or xref:manual::xml-configuration.adoc[Xml
Configuration]. For example you could use XPath to create an
Predicate in a xref:message-filter.adoc[Message
Filter] or as an Expression for a
@@ -127,7 +127,7 @@ exchange:
|function:properties |key for property |String |To lookup a property using the
xref:properties-component.adoc[Properties] component (property placeholders).
-|function:simple |simple expression |Object |To evaluate a
xref:simple-language.adoc[Simple] expression.
+|function:simple |simple expression |Object |To evaluate a
xref:manual::simple-language.adoc[Simple] expression.
|===
CAUTION: `function:properties` and `function:simple` is not supported
