This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit ffa2218022aad1eb751bdbcb638ebf73a86f8ba3
Author: nayananga@acerubuntu18.04 <nayanangamuhandi...@gmail.com>
AuthorDate: Mon Jun 24 13:26:08 2019 +0530
fixed link issues inside camel/components .adoc file and ran mvn clean
install in each folder then ran mvn clean package inside camel/docs
---
.../src/main/docs/ahc-ws-component.adoc | 2 +-
.../camel-ahc/src/main/docs/ahc-component.adoc | 2 +-
.../camel-amqp/src/main/docs/amqp-component.adoc | 2 +-
.../src/main/docs/aws-s3-component.adoc | 2 +-
.../src/main/docs/beanstalk-component.adoc | 4 +-
components/camel-cdi/src/main/docs/cdi.adoc | 30 ++++++-------
.../src/main/docs/cometd-component.adoc | 2 +-
.../src/main/docs/crypto-component.adoc | 2 +-
.../src/main/docs/cxf-transport.adoc | 2 +-
.../camel-cxf/src/main/docs/cxf-component.adoc | 52 +++++++++++-----------
.../camel-cxf/src/main/docs/cxfrs-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 +-
.../src/main/docs/disruptor-component.adoc | 2 +-
.../main/docs/elasticsearch-rest-component.adoc | 2 +-
.../src/main/docs/facebook-component.adoc | 2 +-
.../camel-grape/src/main/docs/grape-component.adoc | 2 +-
.../src/main/docs/groovy-language.adoc | 4 +-
.../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 | 6 +--
.../camel-jpa/src/main/docs/jpa-component.adoc | 14 +++---
.../docs/openshift-build-configs-component.adoc | 2 +-
.../src/main/docs/language-component.adoc | 2 +-
.../camel-mail/src/main/docs/mail-component.adoc | 2 +-
.../src/main/docs/metrics-component.adoc | 10 ++---
.../src/main/docs/micrometer-component.adoc | 10 ++---
.../camel-mock/src/main/docs/mock-component.adoc | 2 +-
.../camel-mvel/src/main/docs/mvel-language.adoc | 2 +-
.../src/main/docs/nagios-component.adoc | 2 +-
.../src/main/docs/netty4-component.adoc | 2 +-
.../camel-ognl/src/main/docs/ognl-language.adoc | 2 +-
.../camel-paho/src/main/docs/paho-component.adoc | 2 +-
.../camel-pdf/src/main/docs/pdf-component.adoc | 8 ++--
.../src/main/docs/properties-component.adoc | 2 +-
.../src/main/docs/quartz2-component.adoc | 2 +-
components/camel-ribbon/src/main/docs/ribbon.adoc | 2 +-
.../src/main/docs/xquery-component.adoc | 4 +-
.../camel-saxon/src/main/docs/xquery-language.adoc | 4 +-
.../src/main/docs/servlet-component.adoc | 2 +-
.../src/main/docs/soroush-component.adoc | 4 +-
.../src/main/docs/spring-boot.adoc | 2 +-
.../src/main/docs/spring-security.adoc | 2 +-
.../camel-spring/src/main/docs/spel-language.adoc | 4 +-
.../src/main/docs/spring-event-component.adoc | 4 +-
components/camel-spring/src/main/docs/spring.adoc | 20 ++++-----
.../src/main/docs/sql-stored-component.adoc | 4 +-
.../src/main/docs/telegram-component.adoc | 4 +-
.../camel-timer/src/main/docs/timer-component.adoc | 2 +-
.../camel-twitter/src/main/docs/twitter.adoc | 2 +-
.../src/main/docs/undertow-component.adoc | 2 +-
.../src/main/docs/univocity-csv-dataformat.adoc | 2 +-
.../src/main/docs/univocity-fixed-dataformat.adoc | 2 +-
.../src/main/docs/univocity-tsv-dataformat.adoc | 2 +-
.../src/main/docs/websocket-component.adoc | 2 +-
.../src/main/docs/xmlsecurity-component.adoc | 2 +-
.../camel-xpath/src/main/docs/xpath-language.adoc | 4 +-
.../camel-xslt/src/main/docs/xslt-component.adoc | 2 +-
components/camel-zipkin/src/main/docs/zipkin.adoc | 4 +-
.../components/modules/ROOT/pages/opentracing.adoc | 2 +-
62 files changed, 143 insertions(+), 143 deletions(-)
diff --git a/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
b/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
index 86e5366..531eef4 100644
--- a/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
+++ b/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
@@ -206,5 +206,5 @@ And the equivalent Spring sample:
* Endpoint
* Getting Started
-* link:../../../../camel-ahc/src/main/docs/readme.html[AHC]
+* xref:../../../../camel-ahc/src/main/docs/readme.adoc[AHC]
* <<atmosphere-websocket-component,Atmosphere-Websocket>>
diff --git a/components/camel-ahc/src/main/docs/ahc-component.adoc
b/components/camel-ahc/src/main/docs/ahc-component.adoc
index e7cd912..bd44369 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 link:camel-configuration-utilities.html[Camel JSSE
+through the xref: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-amqp/src/main/docs/amqp-component.adoc
b/components/camel-amqp/src/main/docs/amqp-component.adoc
index 565a0a9..7de0a34 100644
--- a/components/camel-amqp/src/main/docs/amqp-component.adoc
+++ b/components/camel-amqp/src/main/docs/amqp-component.adoc
@@ -30,7 +30,7 @@ amqp:[queue:|topic:]destinationName[?options]
### AMQP Options
You can specify all of the various configuration options of the
-link:../../../../camel-jms/src/main/docs/readme.html[JMS] component after the
destination name.
+xref:../../../../camel-jms/src/main/docs/readme.adoc[JMS] component after the
destination name.
diff --git a/components/camel-aws-s3/src/main/docs/aws-s3-component.adoc
b/components/camel-aws-s3/src/main/docs/aws-s3-component.adoc
index 412ddcc..4a48c28 100644
--- a/components/camel-aws-s3/src/main/docs/aws-s3-component.adoc
+++ b/components/camel-aws-s3/src/main/docs/aws-s3-component.adoc
@@ -170,7 +170,7 @@ The component supports 38 options, which are listed below.
| *camel.component.aws-s3.basic-property-binding* | Whether the component
should use basic property binding (Camel 2.x) or the newer property binding
with additional capabilities | false | Boolean
| *camel.component.aws-s3.configuration.accelerate-mode-enabled* | Define if
Accelerate Mode enabled is true or false | false | Boolean
| *camel.component.aws-s3.configuration.access-key* | Amazon AWS Access Key |
| String
-| *camel.component.aws-s3.configuration.amazon-s3-client* | Reference to a
`com.amazonaws.services.s3.AmazonS3` in the link:registry.html[Registry]. | |
AmazonS3
+| *camel.component.aws-s3.configuration.amazon-s3-client* | Reference to a
`com.amazonaws.services.s3.AmazonS3` in the
xref:components::registry.adoc[Registry]. | | AmazonS3
| *camel.component.aws-s3.configuration.auto-create-bucket* | Setting the
autocreation of the bucket | true | Boolean
| *camel.component.aws-s3.configuration.autoclose-body* | If this option is
true and includeBody is true, then the S3Object.close() method will be called
on exchange completion. This option is strongly related to includeBody option.
In case of setting includeBody to true and autocloseBody to false, it will be
up to the caller to close the S3Object stream. Setting autocloseBody to true,
will close the S3Object stream automatically. | true | Boolean
| *camel.component.aws-s3.configuration.aws-k-m-s-key-id* | Define the id of
KMS key to use in case KMS is enabled | | String
diff --git a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
index 56c8f34..c9441ab 100644
--- a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
+++ b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
@@ -46,7 +46,7 @@ beanstalk://localhost:11300/tube1+tube2
Tube name will be URL decoded, so if your tube names include special
characters like + or ?, you need to URL-encode them appropriately, or
-use the RAW syntax, see link:how-do-i-configure-endpoints.html[more
+use the RAW syntax, see xref:how-do-i-configure-endpoints.adoc[more
details here].
By the way, you cannot specify several tubes when you are writing jobs
@@ -183,7 +183,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 link:polling-consumer.html[Polling
+The beanstalk consumer is a Scheduled xref: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-cdi/src/main/docs/cdi.adoc
b/components/camel-cdi/src/main/docs/cdi.adoc
index 77e54d0..fcf0b33 100644
--- a/components/camel-cdi/src/main/docs/cdi.adoc
+++ b/components/camel-cdi/src/main/docs/cdi.adoc
@@ -158,8 +158,8 @@ class CustomCamelContext extends DefaultCamelContext {
}
----
-link:http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#producer_method[Producer]
-and
link:http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#disposer_method[disposer]
+http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#producer_method[Producer]
+and http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#disposer_method[disposer]
methods can also be used as well to customize the Camel context bean, e.g.:
[source,java]
@@ -180,7 +180,7 @@ class CamelContextFactory {
}
----
-Similarly,
link:http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#producer_field[producer
+Similarly,
http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#producer_field[producer
fields] can be used, e.g.:
[source,java]
@@ -330,7 +330,7 @@ PropertiesComponent propertiesComponent() {
----
If you want to
-use
link:http://deltaspike.apache.org/documentation/configuration.html[DeltaSpike
+use http://deltaspike.apache.org/documentation/configuration.html[DeltaSpike
configuration mechanism] you can declare the
following `PropertiesComponent` bean:
@@ -381,9 +381,9 @@ Note that CDI injection is supported within the type
converters.
==== Camel annotations
-As part of the Camel link:http://camel.apache.org/bean-integration.html[bean
+As part of the Camel http://camel.apache.org/bean-integration.html[bean
integration], Camel comes with a set
-of
link:http://camel.apache.org/bean-integration.html#BeanIntegration-Annotations[annotations]
that
+of
http://camel.apache.org/bean-integration.html#BeanIntegration-Annotations[annotations]
that
are seamlessly supported by Camel CDI. So you can use any of these
annotations in your CDI beans, e.g.:
@@ -566,11 +566,11 @@ PlatformTransactionManager
createTransactionManager(TransactionManager transacti
*Available as of Camel 2.17*
Camel provides a set
-of
link:http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/event/package-summary.html[management
+of
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/event/package-summary.html[management
events] that can be subscribed to for listening to Camel context,
service, route and exchange events. Camel CDI seamlessly translates
these Camel events into CDI events that can be observed using
-CDI
link:http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#observer_methods[observer
+CDI http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#observer_methods[observer
methods], e.g.:
[source,java]
@@ -596,7 +596,7 @@ void onRouteStarted(@Observes @Named("foo")
RouteStartedEvent event) {
When multiple Camel contexts exist in the CDI container, the Camel
context bean qualifiers, like `@ContextName`, can be used to refine the
observer method resolution to a particular Camel context as specified
-in
link:http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#observer_resolution[observer
+in
http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#observer_resolution[observer
resolution], e.g.:
[source,java]
@@ -633,7 +633,7 @@ detected in the deployment, and that per Camel context.
*Available as of Camel 2.17*
The CDI event endpoint bridges
-the link:http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#events[CDI
+the http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#events[CDI
events] with the Camel routes so that CDI events can be seamlessly
observed / consumed (resp. produced / fired) from Camel consumers (resp.
by Camel producers).
@@ -740,17 +740,17 @@ void observeCdiEvents(@Observes @ContextName("foo")
List<String> event) {
----
Note that the CDI event Camel endpoint dynamically adds
-an
link:http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#observer_methods[observer
+an http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#observer_methods[observer
method] for each unique combination of _event type_ and _event
qualifiers_ and solely relies on the container
-typesafe
link:http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#observer_resolution[observer
+typesafe
http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#observer_resolution[observer
resolution], which leads to an implementation as efficient as possible.
Besides, as the impedance between the _typesafe_ nature of CDI and
the _dynamic_ nature of
-the link:http://camel.apache.org/component.html[Camel component] model is
+the http://camel.apache.org/component.html[Camel component] model is
quite high, it is not possible to create an instance of the CDI event
-Camel endpoint via link:http://camel.apache.org/uris.html[URIs]. Indeed, the
+Camel endpoint via http://camel.apache.org/uris.html[URIs]. Indeed, the
URI format for the CDI event component is:
[source,text]
@@ -1067,7 +1067,7 @@ for (CamelContext context : contexts)
=== Maven Archetype
-Among the available link:camel-maven-archetypes.html[Camel Maven
+Among the available xref:camel-maven-archetypes.adoc[Camel Maven
archetypes], you can use the provided `camel-archetype-cdi` to generate
a Camel CDI Maven project, e.g.:
diff --git a/components/camel-cometd/src/main/docs/cometd-component.adoc
b/components/camel-cometd/src/main/docs/cometd-component.adoc
index a32d60a..8130b70 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 link:camel-configuration-utilities.html[Camel JSSE
+through the xref:camel-configuration-utilities.adoc[Camel JSSE
Configuration Utility]. This utility greatly decreases the amount of
component specific code you need to write and is configurable at the
endpoint and component levels. The following examples demonstrate how
diff --git a/components/camel-crypto/src/main/docs/crypto-component.adoc
b/components/camel-crypto/src/main/docs/crypto-component.adoc
index d9f0483..b2c76df 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 link:spring-xml-extensions.html[Spring
+The same can be achieved with the xref:spring-xml-extensions.adoc[Spring
XML Extensions] using references to keys
#### KeyStores and Aliases.
diff --git a/components/camel-cxf-transport/src/main/docs/cxf-transport.adoc
b/components/camel-cxf-transport/src/main/docs/cxf-transport.adoc
index b0d5355..c070fbf 100644
--- a/components/camel-cxf-transport/src/main/docs/cxf-transport.adoc
+++ b/components/camel-cxf-transport/src/main/docs/cxf-transport.adoc
@@ -254,5 +254,5 @@ on the address "camel://direct:EndpointA" and
"camel://direct:EndpointB"
[[CamelTransportforCXF-CompleteHowtoandExampleforattachingCameltoCXF]]
=== Complete Howto and Example for attaching Camel to CXF
-link:better-jms-transport-for-cxf-webservice-using-apache-camel.html[Better
+xref:better-jms-transport-for-cxf-webservice-using-apache-camel.adoc[Better
JMS Transport for CXF Webservice using Apache Camel]
diff --git a/components/camel-cxf/src/main/docs/cxf-component.adoc
b/components/camel-cxf/src/main/docs/cxf-component.adoc
index 4d56ad8..74b06da 100644
--- a/components/camel-cxf/src/main/docs/cxf-component.adoc
+++ b/components/camel-cxf/src/main/docs/cxf-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 1.0*
-NOTE: When using Apache CXF as a consumer, the
link:cxf-bean-component.html[CXF Bean
+NOTE: When using Apache CXF as a consumer, the
xref:cxf-bean-component.adoc[CXF Bean
Component] allows you to factor out how message payloads are received
from their processing as a RESTful or SOAP web service. This has the
potential of using a multitude of transports to consume web services.
@@ -17,50 +17,50 @@ The CXF component provides integration with
http://cxf.apache.org[Apache CXF] for connecting to
http://cxf.apache.org/docs/jax-ws.html[JAX-WS] services
hosted in CXF.
-* link:#cxf-component[CXF Component]
-** link:#uri-format[URI format]
-** link:#options[Options]
-*** link:#descriptions-of-the-dataformats[Descriptions of the
+* xref:#cxf-component[CXF Component]
+** xref:#uri-format[URI format]
+** xref:#options[Options]
+*** xref:#descriptions-of-the-dataformats[Descriptions of the
dataformats]
-**** link:#how-to-enable-cxfs-loggingoutinterceptor-in-message-mode[How to
+**** xref:#how-to-enable-cxfs-loggingoutinterceptor-in-message-mode[How to
enable CXF's LoggingOutInterceptor in MESSAGE mode]
-*** link:#description-of-relayheaders-option[Description of
+*** xref:#description-of-relayheaders-option[Description of
relayHeaders option]
-**** link:#available-only-in-pojo-mode[Available only in POJO mode]
-**** link:#changes-since-release20[Changes since Release 2.0]
-** link:#configure-the-cxf-endpoints-with-spring[Configure the CXF
+**** xref:#available-only-in-pojo-mode[Available only in POJO mode]
+**** xref:#changes-since-release20[Changes since Release 2.0]
+** xref:#configure-the-cxf-endpoints-with-spring[Configure the CXF
endpoints with Spring]
-** link:#configuring-the-cxf-endpoints-with-apache-aries-blueprint[Configuring
+** xref:#configuring-the-cxf-endpoints-with-apache-aries-blueprint[Configuring
the CXF Endpoints with Apache Aries Blueprint.]
-**
link:#how-to-make-the-camel-cxf-component-use-log4j-instead-of-javautillogging[How
+**
xref:#how-to-make-the-camel-cxf-component-use-log4j-instead-of-javautillogging[How
to make the camel-cxf component use log4j instead of java.util.logging]
-** link:#how-to-let-camel-cxf-response-message-with-xml-start-document[How to
+** xref:#how-to-let-camel-cxf-response-message-with-xml-start-document[How to
let camel-cxf response message with xml start document]
-** link:#how-to-override-the-cxf-producer-address-from-message-header[How to
+** xref:#how-to-override-the-cxf-producer-address-from-message-header[How to
override the CXF producer address from message header]
-**
link:#how-to-consume-a-message-from-a-camel-cxf-endpoint-in-pojo-data-format[How
+**
xref:#how-to-consume-a-message-from-a-camel-cxf-endpoint-in-pojo-data-format[How
to consume a message from a camel-cxf endpoint in POJO data format]
-**
link:#how-to-prepare-the-message-for-the-camel-cxf-endpoint-in-pojo-data-format[How
+**
xref:#how-to-prepare-the-message-for-the-camel-cxf-endpoint-in-pojo-data-format[How
to prepare the message for the camel-cxf endpoint in POJO data format]
-**
link:#how-to-deal-with-the-message-for-a-camel-cxf-endpoint-in-payload-dataformat[How
+**
xref:#how-to-deal-with-the-message-for-a-camel-cxf-endpoint-in-payload-dataformat[How
to deal with the message for a camel-cxf endpoint in PAYLOAD data
format]
-** link:#how-to-get-and-set-soap-headers-in-pojo-mode[How to get and set SOAP
+** xref:#how-to-get-and-set-soap-headers-in-pojo-mode[How to get and set SOAP
headers in POJO mode]
-** link:#how-to-get-and-set-soap-headers-in-payload-mode[How to get and set
+** xref:#how-to-get-and-set-soap-headers-in-payload-mode[How to get and set
SOAP headers in PAYLOAD mode]
-** link:#soap-headers-are-not-available-in-message-mode[SOAP headers are
+** xref:#soap-headers-are-not-available-in-message-mode[SOAP headers are
not available in MESSAGE mode]
-** link:#how-to-throw-a-soap-fault-from-camel[How to throw a SOAP Fault
+** xref:#how-to-throw-a-soap-fault-from-camel[How to throw a SOAP Fault
from Camel]
-**
link:#how-to-propagate-a-camel-cxf-endpoints-request-and-response-context[How
+**
xref:#how-to-propagate-a-camel-cxf-endpoints-request-and-response-context[How
to propagate a camel-cxf endpoint's request and response context]
-** link:#attachment-support[Attachment Support]
-** link:#streaming-support-in-payload-mode[Streaming Support in PAYLOAD
+** xref:#attachment-support[Attachment Support]
+** xref:#streaming-support-in-payload-mode[Streaming Support in PAYLOAD
mode]
-** link:#using-the-generic-cxf-dispatch-mode[Using the generic CXF
+** xref:#using-the-generic-cxf-dispatch-mode[Using the generic CXF
Dispatch mode]
-** link:#see-also[See Also]
+** xref:#see-also[See Also]
Maven users must add the following dependency to their `pom.xml`
for this component:
diff --git a/components/camel-cxf/src/main/docs/cxfrs-component.adoc
b/components/camel-cxf/src/main/docs/cxfrs-component.adoc
index 01daca9..39ab7ed 100644
--- a/components/camel-cxf/src/main/docs/cxfrs-component.adoc
+++ b/components/camel-cxf/src/main/docs/cxfrs-component.adoc
@@ -7,7 +7,7 @@ The CXFRS component provides integration with
http://cxf.apache.org[Apache CXF] for connecting to JAX-RS 1.1 and 2.0
services hosted in CXF.
-When using CXF as a consumer, the link:cxf-bean-component.html[CXF Bean
+When using CXF as a consumer, the xref:cxf-bean-component.adoc[CXF Bean
Component] allows you to factor out how message payloads are received
from their processing as a RESTful or SOAP web service. This has the
potential of using a multitude of transports to consume web services.
diff --git
a/components/camel-dataformat/src/main/docs/dataformat-component.adoc
b/components/camel-dataformat/src/main/docs/dataformat-component.adoc
index 2047466..b02a2c4 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 link:data-format.html[Data
+The *dataformat:* component allows to use xref: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 link:data-format.html[Data
+`unmarshal`. The options is used for configuring the xref: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 <<jaxb-dataformat,JAXB>> link:data-format.html[Data
+For example to use the <<jaxb-dataformat,JAXB>> xref: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 6d1bb22..b28114c 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 <<mock-component,Mock>>,
<<mock-component,Test>>
and <<dataset-component,DataSet>> endpoints work great with the
Camel Testing Framework to simplify your unit and
integration testing using
-link:enterprise-integration-patterns.html[Enterprise Integration
+xref:enterprise-integration-patterns.html[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 24700fb..f4f66a6 100644
--- a/components/camel-dataset/src/main/docs/dataset-test-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
@@ -10,7 +10,7 @@ notoriously difficult. The <<mock-component,Mock>>,
<<mock-component,Test>>
and <<dataset-component,DataSet>> endpoints work great with the
Camel Testing Framework to simplify your unit and
integration testing using
-link:enterprise-integration-patterns.html[Enterprise Integration
+xref: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-disruptor/src/main/docs/disruptor-component.adoc
b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
index 85a0d27..d5cfaba 100644
--- a/components/camel-disruptor/src/main/docs/disruptor-component.adoc
+++ b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
@@ -237,7 +237,7 @@ without incurring significant latency spikes.
### Use of Request Reply
-The Disruptor component supports using link:request-reply.html[Request
+The Disruptor component supports using xref:request-reply.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 2780bc9..e5e80fd 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
@@ -304,7 +304,7 @@ try (ElasticsearchScrollRequestIterator response =
template.requestBody("direct:
}
----
-link:split-eip.html[Split EIP] can also be used.
+xref:split-eip.adoc[Split EIP] can also be used.
[source,java]
----
diff --git a/components/camel-facebook/src/main/docs/facebook-component.adoc
b/components/camel-facebook/src/main/docs/facebook-component.adoc
index 0eaf5cb..8f89029 100644
--- a/components/camel-facebook/src/main/docs/facebook-component.adoc
+++ b/components/camel-facebook/src/main/docs/facebook-component.adoc
@@ -354,7 +354,7 @@ facebook4j.PostUpdate body.
.to("facebook://postFeed/inBody=postUpdate);
----------------------------------------------------
-To poll, every 5 sec (You can set the link:polling-consumer.html[polling
+To poll, every 5 sec (You can set the xref:polling-consumer.adoc[polling
consumer] options by adding a prefix of "consumer"), all statuses on
your home feed:
diff --git a/components/camel-grape/src/main/docs/grape-component.adoc
b/components/camel-grape/src/main/docs/grape-component.adoc
index 87f41d8..85a9708 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 link:type-converter.html[type conversion
+But of course Camel build-in xref: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 dc87cff..91e3bb3 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 link:xml-configuration.html[Xml
+used in the DSL or xref:xml-configuration.adoc[Xml
Configuration].
To use a Groovy expression use the following Java code
@@ -17,7 +17,7 @@ To use a Groovy expression use the following Java code
---------------------------------------
For example you could use the *groovy* function to create an
-Predicate in a link:message-filter.html[Message
+Predicate in a xref:message-filter.adoc[Message
Filter] or as an Expression for a
Recipient List
diff --git a/components/camel-http4/src/main/docs/http4-component.adoc
b/components/camel-http4/src/main/docs/http4-component.adoc
index e020eea..bbc300f 100644
--- a/components/camel-http4/src/main/docs/http4-component.adoc
+++ b/components/camel-http4/src/main/docs/http4-component.adoc
@@ -573,7 +573,7 @@ behavior.
Using the JSSE Configuration Utility
As of Camel 2.8, the HTTP4 component supports SSL/TLS configuration
-through the link:camel-configuration-utilities.html[Camel JSSE
+through the xref: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 e8a586f..88a7ef3 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
As of Camel 2.9, the IRC component supports SSL/TLS configuration
-through the link:camel-configuration-utilities.html[Camel JSSE
+through the xref: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 5b4cac1..e17efb7 100644
--- a/components/camel-jetty/src/main/docs/jetty-component.adoc
+++ b/components/camel-jetty/src/main/docs/jetty-component.adoc
@@ -262,7 +262,7 @@ If you need to expose a Jetty endpoint on all network
interfaces, the
`0.0.0.0` address should be used.
To listen across an entire URI prefix, see
-link:../../../../../docs/user-manual/en/faq/how-do-i-let-jetty-match-wildcards.adoc[How
do I let Jetty match wildcards].
+xref:../../../../../docs/user-manual/en/faq/how-do-i-let-jetty-match-wildcards.adoc[How
do I let Jetty match wildcards].
If you actually want to expose routes by HTTP and already have a
Servlet, you should instead refer to the
@@ -326,7 +326,7 @@ public void process(Exchange exchange) throws Exception {
Using the JSSE Configuration Utility
As of Camel 2.8, the Jetty component supports SSL/TLS configuration
-through the link:camel-configuration-utilities.html[Camel JSSE
+through the xref: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 d3d20a5a..ce99320 100644
--- a/components/camel-jms/src/main/docs/jms-component.adoc
+++ b/components/camel-jms/src/main/docs/jms-component.adoc
@@ -667,7 +667,7 @@ from("file://orders").
#### Using Annotations
-Camel also has annotations so you can use link:pojo-consuming.html[POJO
+Camel also has annotations so you can use xref:pojo-consuming.adoc[POJO
Consuming] and POJO Producing.
#### Spring DSL sample
@@ -696,7 +696,7 @@ the documentation.
Normally, when using <<jms-component,JMS>> as the transport, it only
transfers the body and headers as the payload. If you want to use
-<<jms-component,JMS>> with a link:dead-letter-channel.html[Dead Letter
+<<jms-component,JMS>> with a xref: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
@@ -1421,7 +1421,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 link:request-reply.html[Request
+transaction commits. Therefore to use xref:request-reply.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-jpa/src/main/docs/jpa-component.adoc
b/components/camel-jpa/src/main/docs/jpa-component.adoc
index c6be397..f91846f 100644
--- a/components/camel-jpa/src/main/docs/jpa-component.adoc
+++ b/components/camel-jpa/src/main/docs/jpa-component.adoc
@@ -81,7 +81,7 @@ jpa:entityClassName[?options]
-----------------------------
For sending to the endpoint, the _entityClassName_ is optional. If
-specified, it helps the link:http://camel.apache.org/type-converter.html[Type
Converter] to
+specified, it helps the http://camel.apache.org/type-converter.html[Type
Converter] to
ensure the body is of the correct type.
For consuming, the _entityClassName_ is mandatory.
@@ -401,7 +401,7 @@ the message body.
### Example
-See link:http://camel.apache.org/tracer-example.html[Tracer Example] for an
example using
+See http://camel.apache.org/tracer-example.html[Tracer Example] for an example
using
<<jpa-component,JPA>> to store traced messages into a database.
### Using the JPA-Based Idempotent Repository
@@ -480,9 +480,9 @@ argument to the JVM:
### See Also
-* link:http://camel.apache.org/configuring-camel.html[Configuring Camel]
-* link:http://camel.apache.org/component.html[Component]
-* link:http://camel.apache.org/endpoint.html[Endpoint]
-* link:http://camel.apache.org/getting-started.html[Getting Started]
+* http://camel.apache.org/configuring-camel.html[Configuring Camel]
+* http://camel.apache.org/component.html[Component]
+* http://camel.apache.org/endpoint.html[Endpoint]
+* http://camel.apache.org/getting-started.html[Getting Started]
-* link:http://camel.apache.org/tracer-example.html[Tracer Example]
+* http://camel.apache.org/tracer-example.html[Tracer Example]
diff --git
a/components/camel-kubernetes/src/main/docs/openshift-build-configs-component.adoc
b/components/camel-kubernetes/src/main/docs/openshift-build-configs-component.adoc
index 87a5477..8aa6c38 100644
---
a/components/camel-kubernetes/src/main/docs/openshift-build-configs-component.adoc
+++
b/components/camel-kubernetes/src/main/docs/openshift-build-configs-component.adoc
@@ -3,7 +3,7 @@
*Available as of Camel version 2.17*
-The *OpenShift Build Config* component is one of
link:kubernetes.html[Kubernetes Components] which
+The *OpenShift Build Config* component is one of
xref:kubernetes.adoc[Kubernetes Components] which
provides a producer to execute kubernetes build config operations.
diff --git a/components/camel-language/src/main/docs/language-component.adoc
b/components/camel-language/src/main/docs/language-component.adoc
index b934193..2ab5c27 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 link:dynamic-router.html[Dynamic
+Routing Slip or xref:dynamic-router.adoc[Dynamic
Router] EIPs you can send messages to `language` endpoints where the
script is dynamic defined as well.
diff --git a/components/camel-mail/src/main/docs/mail-component.adoc
b/components/camel-mail/src/main/docs/mail-component.adoc
index bace89e..5101e76 100644
--- a/components/camel-mail/src/main/docs/mail-component.adoc
+++ b/components/camel-mail/src/main/docs/mail-component.adoc
@@ -343,7 +343,7 @@ configuration.
==== Using the JSSE Configuration Utility
As of *Camel 2.10*, the mail component supports SSL/TLS configuration
-through the link:camel-configuration-utilities.html[Camel JSSE
+through the xref: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-metrics/src/main/docs/metrics-component.adoc
b/components/camel-metrics/src/main/docs/metrics-component.adoc
index be91191..45dc261 100644
--- a/components/camel-metrics/src/main/docs/metrics-component.adoc
+++ b/components/camel-metrics/src/main/docs/metrics-component.adoc
@@ -14,8 +14,8 @@ endif::[]
The **metrics:** component allows to collect various metrics directly
from Camel routes. Supported metric types
-are link:#MetricsComponent-counter[counter],
link:#MetricsComponent-histogram[histogram],
-link:#MetricsComponent-meter[meter], link:#MetricsComponent-timer[timer] and
link:#MetricsComponent-gauge[gauge]. http://metrics.dropwizard.io[Metrics]
provides
+are xref:#MetricsComponent-counter[counter],
xref:#MetricsComponent-histogram[histogram],
+xref:#MetricsComponent-meter[meter], xref:#MetricsComponent-timer[timer] and
xref:#MetricsComponent-gauge[gauge]. http://metrics.dropwizard.io[Metrics]
provides
simple way to measure behaviour of application. Configurable
reporting backend is enabling different integration options for
collecting and visualizing statistics. The component also provides
@@ -189,9 +189,9 @@ class MyBean extends RouteBuilder {
### Usage
Each metric has type and name. Supported types are
-link:#MetricsComponent-counter[counter],
-link:#MetricsComponent-histogram[histogram],
link:#MetricsComponent-meter[meter],
-link:#MetricsComponent-timer[timer] and link:#MetricsComponent-gauge[gauge].
+xref:#MetricsComponent-counter[counter],
+xref:#MetricsComponent-histogram[histogram],
xref:#MetricsComponent-meter[meter],
+xref:#MetricsComponent-timer[timer] and xref:#MetricsComponent-gauge[gauge].
Metric name is simple string. If metric type is not provided then type meter
is used by default.
#### Headers
diff --git
a/components/camel-micrometer/src/main/docs/micrometer-component.adoc
b/components/camel-micrometer/src/main/docs/micrometer-component.adoc
index bf869ed..a717ca8 100644
--- a/components/camel-micrometer/src/main/docs/micrometer-component.adoc
+++ b/components/camel-micrometer/src/main/docs/micrometer-component.adoc
@@ -14,8 +14,8 @@ endif::[]
The **micrometer:** component allows to collect various metrics directly
from Camel routes. Supported metric types
-are link:#MicrometerComponent-counter[counter],
link:#MicrometerComponent-distributionSummary[summary],
-and link:#MicrometerComponent-timer[timer]. http://micrometer.io/[Micrometer]
provides
+are xref:#MicrometerComponent-counter[counter],
xref:#MicrometerComponent-distributionSummary[summary],
+and xref:#MicrometerComponent-timer[timer]. http://micrometer.io/[Micrometer]
provides
simple way to measure the behaviour of an application. Configurable
reporting backends (via Micrometer registries) enable different integration
options for
collecting and visualizing statistics.
@@ -194,9 +194,9 @@ class MyBean extends RouteBuilder {
### Usage of producers
Each meter has type and name. Supported types are
-link:#MicrometerComponent-counter[counter],
-link:#MicrometerComponent-summary[distribution summary] and
-link:#MetricsComponent-timer[timer]. If no type is provided then a counter is
used by default.
+xref:#MicrometerComponent-counter[counter],
+xref:#MicrometerComponent-summary[distribution summary] and
+xref:#MetricsComponent-timer[timer]. If no type is provided then a counter is
used by default.
The meter name is a string that is evaluated as `Simple` expression. In
addition to using the `CamelMetricsName`
header (see below), this allows to select the meter depending on exchange data.
diff --git a/components/camel-mock/src/main/docs/mock-component.adoc
b/components/camel-mock/src/main/docs/mock-component.adoc
index 2fd421f..efbd2b8 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 <<mock-component,Mock>>,
<<mock-component,Test>>
and <<dataset-component,DataSet>> endpoints work great with the
Camel Testing Framework to simplify your unit and
integration testing using
-link:enterprise-integration-patterns.html[Enterprise Integration
+xref: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 9637527..4cd4214 100644
--- a/components/camel-mvel/src/main/docs/mvel-language.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-language.adoc
@@ -97,7 +97,7 @@ The component supports 5 options, which are listed below.
### Samples
-For example you could use Mvel inside a link:message-filter.html[Message
+For example you could use Mvel inside a xref:message-filter.adoc[Message
Filter] in XML
[source,java]
diff --git a/components/camel-nagios/src/main/docs/nagios-component.adoc
b/components/camel-nagios/src/main/docs/nagios-component.adoc
index 9748371..a25bc5f 100644
--- a/components/camel-nagios/src/main/docs/nagios-component.adoc
+++ b/components/camel-nagios/src/main/docs/nagios-component.adoc
@@ -182,7 +182,7 @@ Nagios. For example we can enable this from Java as follows:
In Spring XML its just a matter of defining a Spring bean with the type
`EventNotifier` and Camel will pick it up as documented here:
-link:advanced-configuration-of-camelcontext-using-spring.html[Advanced
+xref:advanced-configuration-of-camelcontext-using-spring.adoc[Advanced
configuration of CamelContext using Spring].
### See Also
diff --git a/components/camel-netty4/src/main/docs/netty4-component.adoc
b/components/camel-netty4/src/main/docs/netty4-component.adoc
index 28c5d6a..f3cfe16 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
As of Camel 2.9, the Netty component supports SSL/TLS configuration
-through the link:camel-configuration-utilities.html[Camel JSSE
+through the xref: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-ognl/src/main/docs/ognl-language.adoc
b/components/camel-ognl/src/main/docs/ognl-language.adoc
index 635068c..19fb4d6 100644
--- a/components/camel-ognl/src/main/docs/ognl-language.adoc
+++ b/components/camel-ognl/src/main/docs/ognl-language.adoc
@@ -98,7 +98,7 @@ The component supports 2 options, which are listed below.
### Samples
-For example you could use OGNL inside a link:message-filter.html[Message
+For example you could use OGNL inside a xref:message-filter.adoc[Message
Filter] in XML
[source,java]
diff --git a/components/camel-paho/src/main/docs/paho-component.adoc
b/components/camel-paho/src/main/docs/paho-component.adoc
index 63995bd..cae5aa4 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 link:type-converter.html[type conversion
+But of course Camel build-in xref: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-pdf/src/main/docs/pdf-component.adoc
b/components/camel-pdf/src/main/docs/pdf-component.adoc
index 1dd694a..856e6fc 100644
--- a/components/camel-pdf/src/main/docs/pdf-component.adoc
+++ b/components/camel-pdf/src/main/docs/pdf-component.adoc
@@ -128,12 +128,12 @@ operations. Expected type is
https://pdfbox.apache.org/docs/1.8.10/javadocs/org/apache/pdfbox/pdmodel/PDDocument.html[PDDocument].
Stores PDF document which will be used for append operation.
-|`protection-policy` |Expected type
-ishttps://pdfbox.apache.org/docs/1.8.10/javadocs/org/apache/pdfbox/pdmodel/encryption/ProtectionPolicy.html[ProtectionPolicy].
+|`protection-policy` |Expected type is
+https://pdfbox.apache.org/docs/1.8.10/javadocs/org/apache/pdfbox/pdmodel/encryption/ProtectionPolicy.html[ProtectionPolicy].
If specified then PDF document will be encrypted with it.
-|`decryption-material` |Expected type
-ishttps://pdfbox.apache.org/docs/1.8.10/javadocs/org/apache/pdfbox/pdmodel/encryption/DecryptionMaterial.html[DecryptionMaterial].
+|`decryption-material` |Expected type is
+https://pdfbox.apache.org/docs/1.8.10/javadocs/org/apache/pdfbox/pdmodel/encryption/DecryptionMaterial.html[DecryptionMaterial].
*Mandatory* header if PDF document is encrypted.
|=======================================================================
diff --git
a/components/camel-properties/src/main/docs/properties-component.adoc
b/components/camel-properties/src/main/docs/properties-component.adoc
index 1dbd5a4..4f49367 100644
--- a/components/camel-properties/src/main/docs/properties-component.adoc
+++ b/components/camel-properties/src/main/docs/properties-component.adoc
@@ -144,7 +144,7 @@ This works much like you would do if using Spring's
`<property-placeholder>` tag. However Spring have a limitation which
prevents 3rd party frameworks to leverage Spring property placeholders
to the fullest. See more at
-link:how-do-i-use-spring-property-placeholder-with-camel-xml.html[How do
+xref:how-do-i-use-spring-property-placeholder-with-camel-xml.adoc[How do
I use Spring Property Placeholder with Camel XML].
[TIP]
diff --git a/components/camel-quartz2/src/main/docs/quartz2-component.adoc
b/components/camel-quartz2/src/main/docs/quartz2-component.adoc
index 05bad7f..375380c 100644
--- a/components/camel-quartz2/src/main/docs/quartz2-component.adoc
+++ b/components/camel-quartz2/src/main/docs/quartz2-component.adoc
@@ -406,7 +406,7 @@ but it does not want to be fired now.
The <<quartz2-component,Quartz2>> component provides a
Polling Consumer scheduler which allows to
-use cron based scheduling for link:polling-consumer.html[Polling
+use cron based scheduling for xref:polling-consumer.adoc[Polling
Consumer] such as the File and FTP
consumers.
diff --git a/components/camel-ribbon/src/main/docs/ribbon.adoc
b/components/camel-ribbon/src/main/docs/ribbon.adoc
index b4dc6c9..9710a35 100644
--- a/components/camel-ribbon/src/main/docs/ribbon.adoc
+++ b/components/camel-ribbon/src/main/docs/ribbon.adoc
@@ -76,4 +76,4 @@ from("direct:start")
### See Also
-* link:http://camel.apache.org/servicecall-eip.html[ServiceCall EIP]
+* http://camel.apache.org/servicecall-eip.html[ServiceCall EIP]
diff --git a/components/camel-saxon/src/main/docs/xquery-component.adoc
b/components/camel-saxon/src/main/docs/xquery-component.adoc
index fc267f0..ef64bcd 100644
--- a/components/camel-saxon/src/main/docs/xquery-component.adoc
+++ b/components/camel-saxon/src/main/docs/xquery-component.adoc
@@ -5,9 +5,9 @@
Camel supports http://www.w3.org/TR/xquery/[XQuery] to allow an
Expression or Predicate to be
-used in the DSL or link:xml-configuration.html[Xml
+used in the DSL or xref:xml-configuration.adoc[Xml
Configuration]. For example you could use XQuery to create an
-Predicate in a link:message-filter.html[Message
+Predicate in a xref:message-filter.adoc[Message
Filter] or as an Expression for a
Recipient List.
diff --git a/components/camel-saxon/src/main/docs/xquery-language.adoc
b/components/camel-saxon/src/main/docs/xquery-language.adoc
index b8c44a3..6b52fb5 100644
--- a/components/camel-saxon/src/main/docs/xquery-language.adoc
+++ b/components/camel-saxon/src/main/docs/xquery-language.adoc
@@ -5,9 +5,9 @@
Camel supports http://www.w3.org/TR/xquery/[XQuery] to allow an
Expression or Predicate to be
-used in the DSL or link:xml-configuration.html[Xml
+used in the DSL or xref:xml-configuration.adoc[Xml
Configuration]. For example you could use XQuery to create an
-Predicate in a link:message-filter.html[Message
+Predicate in a xref:message-filter.adoc[Message
Filter] or as an Expression for a
Recipient List.
diff --git a/components/camel-servlet/src/main/docs/servlet-component.adoc
b/components/camel-servlet/src/main/docs/servlet-component.adoc
index 89debe8..f95ac88 100644
--- a/components/camel-servlet/src/main/docs/servlet-component.adoc
+++ b/components/camel-servlet/src/main/docs/servlet-component.adoc
@@ -509,7 +509,7 @@ The automatic mapping of the Camel servlet can also be
disabled.
* Getting Started
* <<ServletTomcatExample-ServletTomcatExample,Servlet Tomcat Example>>
-* link:servlet-tomcat-no-spring-example.html[Servlet Tomcat No Spring
+* xref:servlet-tomcat-no-spring-example.adoc[Servlet Tomcat No Spring
Example]
* <<http-component,HTTP>>
* <<jetty-component,Jetty>>
diff --git a/components/camel-soroush/src/main/docs/soroush-component.adoc
b/components/camel-soroush/src/main/docs/soroush-component.adoc
index c93310b..8738780 100644
--- a/components/camel-soroush/src/main/docs/soroush-component.adoc
+++ b/components/camel-soroush/src/main/docs/soroush-component.adoc
@@ -8,8 +8,8 @@ It allows a Camel-based application to send and receive
messages by acting as a
A Soroush Bot must be created before using this component, following the
instruction at the
-link:https://soroush-app.ir/developer.html[Soroush Bot Developers home].
-when a new Bot is created, the link:https://sapp.ir/mrbot[MrBot] provides
+https://soroush-app.ir/developer.html[Soroush Bot Developers home].
+when a new Bot is created, the https://sapp.ir/mrbot[MrBot] provides
an **authorization token** corresponding to the Bot. The authorization token
is a mandatory parameter for camel-soroush endpoint.
Maven users will need to add the following dependency to their `pom.xml`
diff --git a/components/camel-spring-boot/src/main/docs/spring-boot.adoc
b/components/camel-spring-boot/src/main/docs/spring-boot.adoc
index fbba62e..ca72b1d 100644
--- a/components/camel-spring-boot/src/main/docs/spring-boot.adoc
+++ b/components/camel-spring-boot/src/main/docs/spring-boot.adoc
@@ -602,7 +602,7 @@
https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-tes
To get the `CamelContext` or `ProducerTemplate`, you can inject them into the
class in the normal Spring manner, using `@Autowired`.
-You can also use
link:../../../../../docs/user-manual/en/spring-testing.adoc#camel-enhanced-spring-test[Camel
Spring test annotations] to configure tests declaratively. This example uses
the `@MockEndpoints` annotation to auto-mock an endpoint:
+You can also use
xref:../../../../../docs/user-manual/en/spring-testing.adoc#camel-enhanced-spring-test[Camel
Spring test annotations] to configure tests declaratively. This example uses
the `@MockEndpoints` annotation to auto-mock an endpoint:
[source,java]
----
diff --git
a/components/camel-spring-security/src/main/docs/spring-security.adoc
b/components/camel-spring-security/src/main/docs/spring-security.adoc
index a9ffd86..608adb5 100644
--- a/components/camel-spring-security/src/main/docs/spring-security.adoc
+++ b/components/camel-spring-security/src/main/docs/spring-security.adoc
@@ -86,7 +86,7 @@ exchange depending on your needs. For example, you might
create a
processor that gets credentials from an HTTP request header originating
in the <<jetty-component,Jetty>> component. No matter how the credentials
are collected, they need to be placed in the In message or the
-`SecurityContextHolder` so the Camel link:spring-security.html[Spring
+`SecurityContextHolder` so the Camel xref:spring-security.adoc[Spring
Security] component can access them:
[source,java]
diff --git a/components/camel-spring/src/main/docs/spel-language.adoc
b/components/camel-spring/src/main/docs/spel-language.adoc
index 1ff663b..8f6a30e 100644
--- a/components/camel-spring/src/main/docs/spel-language.adoc
+++ b/components/camel-spring/src/main/docs/spel-language.adoc
@@ -115,8 +115,8 @@ can invoke the "bar" method on this bean like this:
==== SpEL in enterprise integration patterns
-You can use SpEL as an expression for link:recipient-list.html[Recipient
-List] or as a predicate inside a link:message-filter.html[Message
+You can use SpEL as an expression for xref:recipient-list.adoc[Recipient
+List] or as a predicate inside a xref:message-filter.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 d7a2b81..ce08175 100644
--- a/components/camel-spring/src/main/docs/spring-event-component.adoc
+++ b/components/camel-spring/src/main/docs/spring-event-component.adoc
@@ -7,8 +7,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
-link:enterprise-integration-patterns.html[Enterprise Integration
-Patterns] to process them such as link:message-filter.html[Message
+xref:enterprise-integration-patterns.adoc[Enterprise Integration
+Patterns] to process them such as xref:message-filter.adoc[Message
Filter].
### URI format
diff --git a/components/camel-spring/src/main/docs/spring.adoc
b/components/camel-spring/src/main/docs/spring.adoc
index 4405529..9ce2fa7 100644
--- a/components/camel-spring/src/main/docs/spring.adoc
+++ b/components/camel-spring/src/main/docs/spring.adoc
@@ -8,9 +8,9 @@ http://www.springframework.org/[Spring Framework] in a number
of ways.
components like <<jms-component,JMS>> and <<jms-component,JPA>>
* Camel works with Spring 2 XML processing with the
Xml Configuration
-* Camel Spring XML Schema's is defined at link:xml-reference.html[Xml
+* Camel Spring XML Schema's is defined at xref:xml-reference.adoc[Xml
Reference]
-* Camel supports a powerful version of link:spring-remoting.html[Spring
+* Camel supports a powerful version of xref:spring-remoting.adoc[Spring
Remoting] which can use powerful routing between the client and server
side along with using all of the available
Components for the transport
@@ -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
-link:enterprise-integration-patterns.html[Enterprise Integration
+xref:enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and Camel's powerful <<mock-component,Mock>> and
<<test-component,Test>> endpoints
* From *Camel 2.15* onwards Camel supports Spring Boot using
@@ -113,7 +113,7 @@ inline namespace declaration:
==== Advanced configuration using Spring
See more details at
-link:advanced-configuration-of-camelcontext-using-spring.html[Advanced
+xref:advanced-configuration-of-camelcontext-using-spring.adoc[Advanced
configuration of CamelContext using Spring]
$### Using Java Code
@@ -243,7 +243,7 @@ above in the `<packageScan>` documentation.
*Available as of Camel 2.3*
-When defining routes in Camel using link:xml-configuration.html[Xml
+When defining routes in Camel using xref: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
@@ -356,7 +356,7 @@ SpringCamelContext lazily fetching components from the
spring context
for the scheme name you use for Endpoint
URIs.
-For more detail see link:how-do-i-configure-endpoints.html[Configuring
+For more detail see xref:how-do-i-configure-endpoints.adoc[Configuring
Endpoints and Components].
=== CamelContextAware
@@ -365,7 +365,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 link:bean-integration.html[Bean
+injected into your POJO. Also see the xref:bean-integration.adoc[Bean
Integration] for further injections.
=== Integration Testing
@@ -377,12 +377,12 @@ under Transactional Client.
=== See also
* Spring JMS Tutorial
-* link:creating-a-new-spring-based-camel-route.html[Creating a new
+* xref:creating-a-new-spring-based-camel-route.adoc[Creating a new
Spring based Camel Route]
* Spring example
* Xml Reference
-* link:advanced-configuration-of-camelcontext-using-spring.html[Advanced
+* xref:advanced-configuration-of-camelcontext-using-spring.adoc[Advanced
configuration of CamelContext using Spring]
-* link:how-do-i-import-routes-from-other-xml-files.html[How do I import
+* xref:how-do-i-import-routes-from-other-xml-files.adoc[How do I import
routes from other XML files]
diff --git a/components/camel-sql/src/main/docs/sql-stored-component.adoc
b/components/camel-sql/src/main/docs/sql-stored-component.adoc
index a1d07a5..e002488 100644
--- a/components/camel-sql/src/main/docs/sql-stored-component.adoc
+++ b/components/camel-sql/src/main/docs/sql-stored-component.adoc
@@ -5,7 +5,7 @@
The *sql-stored:* component allows you to work with databases using JDBC
Stored Procedure queries. This component is an extension to
-the link:sql-component.adoc[SQL Component] but specialized for calling
+the xref:sql-component.adoc[SQL Component] but specialized for calling
stored procedures.
This component uses `spring-jdbc` behind the scenes for the actual SQL
@@ -284,4 +284,4 @@ You should also include the specific database driver, if
needed.
=== See Also
-* link:sql-component.adoc[SQL Component]
+* xref:sql-component.adoc[SQL Component]
diff --git a/components/camel-telegram/src/main/docs/telegram-component.adoc
b/components/camel-telegram/src/main/docs/telegram-component.adoc
index 338f149..717b3ff 100644
--- a/components/camel-telegram/src/main/docs/telegram-component.adoc
+++ b/components/camel-telegram/src/main/docs/telegram-component.adoc
@@ -8,8 +8,8 @@ It allows a Camel-based application to send and receive
messages by acting as a
direct conversations with normal users, private and public groups or channels.
A Telegram Bot must be created before using this component, following the
instructions at the
-link:https://core.telegram.org/bots#3-how-do-i-create-a-bot[Telegram Bot
developers home].
-When a new Bot is created, the link:https://telegram.me/botfather[BotFather]
provides an
+https://core.telegram.org/bots#3-how-do-i-create-a-bot[Telegram Bot developers
home].
+When a new Bot is created, the https://telegram.me/botfather[BotFather]
provides an
**authorization token** corresponding to the Bot. The authorization token is a
mandatory parameter
for the camel-telegram endpoint.
diff --git a/components/camel-timer/src/main/docs/timer-component.adoc
b/components/camel-timer/src/main/docs/timer-component.adoc
index 6bd2d94..1547bbb 100644
--- a/components/camel-timer/src/main/docs/timer-component.adoc
+++ b/components/camel-timer/src/main/docs/timer-component.adoc
@@ -29,7 +29,7 @@ advanced scheduling.
TIP:*Specify time in human friendly format*
In *Camel 2.3* onwards you can specify the time in
-link:how-do-i-specify-time-period-in-a-human-friendly-syntax.html[human
+xref:how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc[human
friendly syntax].
diff --git a/components/camel-twitter/src/main/docs/twitter.adoc
b/components/camel-twitter/src/main/docs/twitter.adoc
index 2677a29..20dad96 100644
--- a/components/camel-twitter/src/main/docs/twitter.adoc
+++ b/components/camel-twitter/src/main/docs/twitter.adoc
@@ -141,7 +141,7 @@ from("direct:foo")
### Example
-See also the link:twitter-websocket-example.html[Twitter Websocket
+See also the xref:twitter-websocket-example.adoc[Twitter Websocket
Example].
### See Also
diff --git a/components/camel-undertow/src/main/docs/undertow-component.adoc
b/components/camel-undertow/src/main/docs/undertow-component.adoc
index ef66c97..0125f9d 100644
--- a/components/camel-undertow/src/main/docs/undertow-component.adoc
+++ b/components/camel-undertow/src/main/docs/undertow-component.adoc
@@ -227,7 +227,7 @@ If you need to expose an Undertow endpoint on all network
interfaces, the
`0.0.0.0` address should be used.
To listen across an entire URI prefix, see
-link:../../../../../docs/user-manual/en/faq/how-do-i-let-jetty-match-wildcards.adoc[How
do I let Jetty match wildcards].
+xref:../../../../../docs/user-manual/en/faq/how-do-i-let-jetty-match-wildcards.adoc[How
do I let Jetty match wildcards].
If you actually want to expose routes by HTTP and already have a
Servlet, you should instead refer to the
diff --git
a/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
b/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
index 6953058..c9911f8 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 link:data-format.html[Data
+This xref: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 79f83f0..a54d9f4 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 link:data-format.html[Data
+This xref: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 7713839..8069fd1 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 link:data-format.html[Data
+This xref: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 9200f43..9e927d9 100644
--- a/components/camel-websocket/src/main/docs/websocket-component.adoc
+++ b/components/camel-websocket/src/main/docs/websocket-component.adoc
@@ -211,7 +211,7 @@ from("activemq:topic:newsTopic")
#### Using the JSSE Configuration Utility
As of Camel 2.10, the WebSocket component supports SSL/TLS configuration
-through the link:camel-configuration-utilities.html[Camel JSSE
+through the xref: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 05fd8af..0c2573b 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 link:data-format.html[Data
+support, please refer to the XML Security xref: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 2aa0f82..190d1a3 100644
--- a/components/camel-xpath/src/main/docs/xpath-language.adoc
+++ b/components/camel-xpath/src/main/docs/xpath-language.adoc
@@ -5,9 +5,9 @@
Camel supports http://www.w3.org/TR/xpath[XPath] to allow an
Expression or Predicate to be
-used in the DSL or link:xml-configuration.html[Xml
+used in the DSL or xref:xml-configuration.adoc[Xml
Configuration]. For example you could use XPath to create an
-Predicate in a link:message-filter.html[Message
+Predicate in a xref:message-filter.adoc[Message
Filter] or as an Expression for a
Recipient List.
diff --git a/components/camel-xslt/src/main/docs/xslt-component.adoc
b/components/camel-xslt/src/main/docs/xslt-component.adoc
index ca4ce01..2439dcf 100644
--- a/components/camel-xslt/src/main/docs/xslt-component.adoc
+++ b/components/camel-xslt/src/main/docs/xslt-component.adoc
@@ -314,7 +314,7 @@ With Spring XML:
=== Dynamic stylesheets
To provide a dynamic stylesheet at runtime you can define a dynamic URI.
-See link:how-to-use-a-dynamic-uri-in-to.html[How to use a dynamic URI in
+See xref:how-to-use-a-dynamic-uri-in-to.adoc[How to use a dynamic URI in
to()] for more information.
*Available as of Camel 2.9 (removed in 2.11.4, 2.12.3 and 2.13.0)* +
diff --git a/components/camel-zipkin/src/main/docs/zipkin.adoc
b/components/camel-zipkin/src/main/docs/zipkin.adoc
index b2bbdb9..03f70c2 100644
--- a/components/camel-zipkin/src/main/docs/zipkin.adoc
+++ b/components/camel-zipkin/src/main/docs/zipkin.adoc
@@ -74,14 +74,14 @@ uses the rules from Intercept.
|includeMessageBody |false |Whether to include the Camel message body in the
zipkin traces.
This is not recommended for production usage, or when having big
payloads. You can limit the size by configuring the
-link:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.html[max
+xref:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
debug log size].
|includeMessageBodyStreams |false |Whether to include message bodies that are
stream based in the zipkin
traces. This requires enabling streamcaching on the
routes or globally on the CamelContext. This is not recommended for production
usage, or when having big
payloads. You can limit the size by configuring the
-link:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.html[max
+xref:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
debug log size].
|===
diff --git a/docs/components/modules/ROOT/pages/opentracing.adoc
b/docs/components/modules/ROOT/pages/opentracing.adoc
index 2610568..ff5ed86 100644
--- a/docs/components/modules/ROOT/pages/opentracing.adoc
+++ b/docs/components/modules/ROOT/pages/opentracing.adoc
@@ -4,7 +4,7 @@
*Available as of Camel 2.19*
IMPORTANT: Starting with Camel 2.21, it will be necessary to use an
OpenTracing complaint tracer that is
-compatible with OpenTracing Java API version 0.31 or higher.
+compatible with OpenTracing Java API version 0.31. From Camel 3.0.0.M4, it
will be necessary to use an OpenTracing compliant tracer that is compatible
with OpenTracing Java API version 0.32 or higher.
The camel-opentracing component is used for tracing and timing incoming and
outgoing Camel messages using http://opentracing.io/[OpenTracing].
