You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by zr...@apache.org on 2019/09/23 05:54:29 UTC
[camel] branch master updated: Replace broken documentation links
with xref
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
The following commit(s) were added to refs/heads/master by this push:
new 99c0a69 Replace broken documentation links with xref
99c0a69 is described below
commit 99c0a691f35868aa43c9c159e9076de0ea5e0c38
Author: Sohrab Hosseini <so...@gmail.com>
AuthorDate: Thu Sep 5 23:10:18 2019 +1000
Replace broken documentation links with xref
---
CONTRIBUTING.md | 2 +-
core/camel-core/src/main/docs/eips/hystrix-eip.adoc | 2 +-
core/camel-core/src/main/docs/eips/marshal-eip.adoc | 4 ++--
core/camel-core/src/main/docs/eips/pipeline-eip.adoc | 6 +++---
core/camel-core/src/main/docs/eips/process-eip.adoc | 6 +++---
core/camel-core/src/main/docs/eips/rollback-eip.adoc | 6 +++---
core/camel-core/src/main/docs/eips/step-eip.adoc | 2 +-
core/camel-core/src/main/docs/eips/to-eip.adoc | 12 ++++++------
core/camel-core/src/main/docs/eips/transform-eip.adoc | 2 +-
core/camel-core/src/main/docs/eips/unmarshal-eip.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/contributing.adoc | 2 +-
.../ROOT/pages/faq/how-does-camel-compare-to-mule.adoc | 3 +--
docs/user-manual/modules/ROOT/pages/hystrix-eip.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/marshal-eip.adoc | 4 ++--
docs/user-manual/modules/ROOT/pages/message-endpoint.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/message.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/pipeline-eip.adoc | 6 +++---
docs/user-manual/modules/ROOT/pages/process-eip.adoc | 6 +++---
docs/user-manual/modules/ROOT/pages/rollback-eip.adoc | 6 +++---
docs/user-manual/modules/ROOT/pages/step-eip.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/to-eip.adoc | 12 ++++++------
docs/user-manual/modules/ROOT/pages/transform-eip.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/unmarshal-eip.adoc | 2 +-
23 files changed, 47 insertions(+), 48 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8ba7689..7a63d034 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -49,7 +49,7 @@ To edit the documentation:
- Create a commit and raise a Pull Request
- If you want to add more documentation check for .adoc in codebase
-For more information see [How does the website work](https://github.com/apache/camel/blob/master/docs/user-manual/en/faq/how-does-the-website-work.adoc) or [How do I edit the website for more details](https://github.com/apache/camel/blob/master/docs/user-manual/en/faq/how-do-i-edit-the-website.adoc).
+For more information see https://camel.apache.org/manual/latest/faq/how-does-the-website-work.html[How does the website work] or https://camel.apache.org/manual/latest/faq/how-do-i-edit-the-website.html[How do I edit the website for more details].
## If you find a bug or problem
diff --git a/core/camel-core/src/main/docs/eips/hystrix-eip.adoc b/core/camel-core/src/main/docs/eips/hystrix-eip.adoc
index d1ea315..f398fd5 100644
--- a/core/camel-core/src/main/docs/eips/hystrix-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/hystrix-eip.adoc
@@ -95,7 +95,7 @@ And in XML DSL:
</camelContext>
----
-See https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/onFallback-eip.adoc[onFallback]
+See xref:onFallback-eip.adoc[onFallback].
== Other examples
diff --git a/core/camel-core/src/main/docs/eips/marshal-eip.adoc b/core/camel-core/src/main/docs/eips/marshal-eip.adoc
index a9c077d..ddc53aa 100644
--- a/core/camel-core/src/main/docs/eips/marshal-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/marshal-eip.adoc
@@ -1,7 +1,7 @@
[[marshal-eip]]
= Marshal EIP
-Marshalling is the opposite of unmarshalling, where a bean is marshalled into some binary or textual format for transmission over some transport via a Camel https://github.com/apache/camel/tree/master/components[Components]. Marshalling is used in the same way as unmarshalling above; in the https://github.com/apache/camel/blob/master/docs/user-manual/en/dsl.adoc[DSL] you can use a DataFormat instance, you can configure the DataFormat dynamically using the DSL or you can refer to a named [...]
+Marshalling is the opposite of unmarshalling, where a bean is marshalled into some binary or textual format for transmission over some transport via a Camel xref:components::index.adoc[Components]. Marshalling is used in the same way as unmarshalling above; in the xref:dsl.adoc[DSL] you can use a DataFormat instance, you can configure the DataFormat dynamically using the DSL or you can refer to a named instance of the format in the xref:registry.adoc[Registry].
== Options
@@ -17,7 +17,7 @@ The Marshal EIP supports 1 options which are listed below:
== Samples
-The following example unmarshals via serialization then marshals using a named JAXB data format to perform a kind of https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-translator.adoc[Message Translator]
+The following example unmarshals via serialization then marshals using a named JAXB data format to perform a kind of xref:message-translator.adoc[Message Translator].
[source,java]
----
diff --git a/core/camel-core/src/main/docs/eips/pipeline-eip.adoc b/core/camel-core/src/main/docs/eips/pipeline-eip.adoc
index 6e5662f..8396970 100644
--- a/core/camel-core/src/main/docs/eips/pipeline-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/pipeline-eip.adoc
@@ -1,12 +1,12 @@
[[pipeline-eip]]
= Pipeline EIP
-Camel supports the http://www.enterpriseintegrationpatterns.com/PipesAndFilters.html[Pipes and Filters] from the https://github.com/apache/camel/blob/master/docs/user-manual/en/enterprise-integration-patterns.adoc[EIP patterns] in various ways.
+Camel supports the http://www.enterpriseintegrationpatterns.com/PipesAndFilters.html[Pipes and Filters] from the xref:enterprise-integration-patterns.adoc[EIP patterns] in various ways.
image::eip/PipesAndFilters.gif[image]
With Camel you can split your processing across multiple independent
-https://github.com/apache/camel/blob/master/docs/user-manual/en/endpoint.adoc[Endpoint] instances which can then be chained
+xref:endpoint.adoc[Endpoint] instances which can then be chained
together.
== Options
@@ -19,7 +19,7 @@ The Pipeline EIP has no options.
== Examples
You can create pipelines of logic using multiple
-https://github.com/apache/camel/blob/master/docs/user-manual/en/endpoint.adoc[Endpoint] or https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-translator.adoc[Message
+xref:endpoint.adoc[Endpoint] or xref:message-translator.adoc[Message
Translator] instances as follows
Though pipeline is the default mode of operation when you specify
diff --git a/core/camel-core/src/main/docs/eips/process-eip.adoc b/core/camel-core/src/main/docs/eips/process-eip.adoc
index fd9e412..c7c1c09 100644
--- a/core/camel-core/src/main/docs/eips/process-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/process-eip.adoc
@@ -1,7 +1,7 @@
[[process-eip]]
= Process EIP
-The http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html[Processor] interface is used to implement consumers of message exchanges or to implement a https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-translator.adoc[Message Translator]
+The http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html[Processor] interface is used to implement consumers of message exchanges or to implement a xref:message-translator.adoc[Message Translator]
== Options
@@ -32,7 +32,7 @@ public class MyProcessor implements Processor {
You can then easily use this inside a route by declaring the bean in
Spring, say via the XML (or registering it in JNDI if that is your
-https://github.com/apache/camel/blob/master/docs/user-manual/en/registry.adoc[Registry])
+xref:registry.adoc[Registry])
[source,xml]
--------------------------------------------------------
@@ -58,7 +58,7 @@ Processor myProcessor = new MyProcessor();
from("activemq:myQueue").process(myProcessor);
----
-If you need to lookup the processor in the https://github.com/apache/camel/blob/master/docs/user-manual/en/registry.adoc[Registry]
+If you need to lookup the processor in the xref:registry.adoc[Registry]
then you should use the *processRef* DSL:
[source,java]
diff --git a/core/camel-core/src/main/docs/eips/rollback-eip.adoc b/core/camel-core/src/main/docs/eips/rollback-eip.adoc
index 6d900d5..98d2086 100644
--- a/core/camel-core/src/main/docs/eips/rollback-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/rollback-eip.adoc
@@ -9,7 +9,7 @@ using spring transactions.
image::eip/TransactionalClientSolution.gif[image]
-Transaction Oriented Endpoints like https://github.com/apache/camel/blob/master/components/camel-jms/src/main/docs/jms-component.adoc[JMS] support using a
+Transaction Oriented Endpoints like xref:components::jms-component.adoc[JMS] support using a
transaction for both inbound and outbound message exchanges. Endpoints
that support transactions will participate in the current transaction
context that they are called from.
@@ -115,7 +115,7 @@ from("activemq:queue:foo").policy(notsupported).to("activemq:queue:bar");
=== OSGi Blueprint
-If you are using https://github.com/apache/camel/blob/master/docs/user-manual/en/using-osgi-blueprint-with-camel.adoc[OSGi
+If you are using xref:using-osgi-blueprint-with-camel.adoc[OSGi
Blueprint] then you most likely have to explicit declare a policy and
refer to the policy from the transacted in the route.
@@ -188,7 +188,7 @@ Transaction error handler
When a route is marked as transacted using *transacted* Camel will
automatic use the
xref:transactionerrorhandler.adoc[TransactionErrorHandler] as
-https://github.com/apache/camel/blob/master/docs/user-manual/en/error-handler.adoc[Error Handler]. It supports basically the same
+xref:error-handler.adoc[Error Handler]. It supports basically the same
feature set as the xref:defaulterrorhandler.adoc[DefaultErrorHandler],
so you can for instance use xref:exception-clause.adoc[Exception Clause]
as well.
diff --git a/core/camel-core/src/main/docs/eips/step-eip.adoc b/core/camel-core/src/main/docs/eips/step-eip.adoc
index 0b14b23..d95fa00 100644
--- a/core/camel-core/src/main/docs/eips/step-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/step-eip.adoc
@@ -1,7 +1,7 @@
[[step-eip]]
= Step EIP
-Camel supports the http://www.enterpriseintegrationpatterns.com/PipesAndFilters.html[Pipes and Filters] from the https://github.com/apache/camel/blob/master/docs/user-manual/en/enterprise-integration-patterns.adoc[EIP patterns] in various ways.
+Camel supports the http://www.enterpriseintegrationpatterns.com/PipesAndFilters.html[Pipes and Filters] from the xref:enterprise-integration-patterns.adoc[EIP patterns] in various ways.
image::eip/PipesAndFilters.gif[image]
diff --git a/core/camel-core/src/main/docs/eips/to-eip.adoc b/core/camel-core/src/main/docs/eips/to-eip.adoc
index 8a2397f..fb1c22c 100644
--- a/core/camel-core/src/main/docs/eips/to-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/to-eip.adoc
@@ -3,12 +3,12 @@
See message related documentation
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message.adoc[Message]
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-bus.adoc[Message Bus]
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-channel.adoc[Message Channel]
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-endpoint.adoc[Message Endpoint]
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-router.adoc[Message Router]
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-translator.adoc[Message Translator]
+* xref:message.adoc[Message]
+* xref:message-bus.adoc[Message Bus]
+* xref:message-channel.adoc[Message Channel]
+* xref:message-endpoint.adoc[Message Endpoint]
+* xref:message-router.adoc[Message Router]
+* xref:message-translator.adoc[Message Translator]
== Options
diff --git a/core/camel-core/src/main/docs/eips/transform-eip.adoc b/core/camel-core/src/main/docs/eips/transform-eip.adoc
index 60cfbee..687d16c 100644
--- a/core/camel-core/src/main/docs/eips/transform-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/transform-eip.adoc
@@ -3,7 +3,7 @@
See below for details
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-translator.adoc[Message Translator]
+* xref:message-translator.adoc[Message Translator]
== Options
diff --git a/core/camel-core/src/main/docs/eips/unmarshal-eip.adoc b/core/camel-core/src/main/docs/eips/unmarshal-eip.adoc
index 62fcd96..c4e2816 100644
--- a/core/camel-core/src/main/docs/eips/unmarshal-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/unmarshal-eip.adoc
@@ -28,7 +28,7 @@ from("activemq:My.Queue").
to("mqseries:Another.Queue");
----
-The above uses a named DataFormat of _jaxb_ which is configured with a number of Java package names. You can if you prefer use a named reference to a data format which can then be defined in your https://github.com/apache/camel/blob/master/docs/user-manual/en/registry.adoc[Registry] such as via your xref:components::spring.adoc[Spring] XML file.
+The above uses a named DataFormat of _jaxb_ which is configured with a number of Java package names. You can if you prefer use a named reference to a data format which can then be defined in your xref:registry.adoc[Registry] such as via your xref:components::spring.adoc[Spring] XML file.
You can also use the DSL itself to define the data format as you use it.
For example the following uses Java serialization to unmarshal a binary
diff --git a/docs/user-manual/modules/ROOT/pages/contributing.adoc b/docs/user-manual/modules/ROOT/pages/contributing.adoc
index b9930b2..f034652 100644
--- a/docs/user-manual/modules/ROOT/pages/contributing.adoc
+++ b/docs/user-manual/modules/ROOT/pages/contributing.adoc
@@ -51,7 +51,7 @@ To edit the documentation:
** Create a commit and raise a Pull Request
* If you want to add more documentation check for .adoc in codebase
-For more information see https://github.com/apache/camel/blob/master/docs/user-manual/en/faq/how-does-the-website-work.adoc[How does the website work] or https://github.com/apache/camel/blob/master/docs/user-manual/en/faq/how-do-i-edit-the-website.adoc[How do I edit the website for more details].
+For more information see https://camel.apache.org/manual/latest/faq/how-does-the-website-work.html[How does the website work] or https://camel.apache.org/manual/latest/faq/how-do-i-edit-the-website.html[How do I edit the website for more details].
[#if-you-find-a-bug-or-problem]
== If you find a bug or problem
diff --git a/docs/user-manual/modules/ROOT/pages/faq/how-does-camel-compare-to-mule.adoc b/docs/user-manual/modules/ROOT/pages/faq/how-does-camel-compare-to-mule.adoc
index 8289d26..406024b 100644
--- a/docs/user-manual/modules/ROOT/pages/faq/how-does-camel-compare-to-mule.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq/how-does-camel-compare-to-mule.adoc
@@ -25,5 +25,4 @@ routing/mediation engines. The main differences are as follows:
* Camel supports an implicit xref:type-converter.adoc[Type Converter] in
the core API to make it simpler to connect components together requiring
different types of payload & headers
-* Camel uses the https://github.com/apache/camel/blob/master/docs/user-manual/en/notice.md[Apache 2 License] rather than Mule's more restrictive
- commercial license
+* Camel uses the https://apache.org/licenses/LICENSE-2.0[Apache 2 License] rather than Mule's more restrictive commercial license
diff --git a/docs/user-manual/modules/ROOT/pages/hystrix-eip.adoc b/docs/user-manual/modules/ROOT/pages/hystrix-eip.adoc
index 2f737da..92a168b 100644
--- a/docs/user-manual/modules/ROOT/pages/hystrix-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/hystrix-eip.adoc
@@ -96,7 +96,7 @@ And in XML DSL:
</camelContext>
----
-See https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/onFallback-eip.adoc[onFallback]
+See xref:onFallback-eip.adoc[onFallback].
== Other examples
diff --git a/docs/user-manual/modules/ROOT/pages/marshal-eip.adoc b/docs/user-manual/modules/ROOT/pages/marshal-eip.adoc
index f073e28..7572c02 100644
--- a/docs/user-manual/modules/ROOT/pages/marshal-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/marshal-eip.adoc
@@ -2,7 +2,7 @@
= Marshal EIP
:page-source: core/camel-core/src/main/docs/eips/marshal-eip.adoc
-Marshalling is the opposite of unmarshalling, where a bean is marshalled into some binary or textual format for transmission over some transport via a Camel https://github.com/apache/camel/tree/master/components[Components]. Marshalling is used in the same way as unmarshalling above; in the https://github.com/apache/camel/blob/master/docs/user-manual/en/dsl.adoc[DSL] you can use a DataFormat instance, you can configure the DataFormat dynamically using the DSL or you can refer to a named [...]
+Marshalling is the opposite of unmarshalling, where a bean is marshalled into some binary or textual format for transmission over some transport via a Camel xref:components::index.adoc[Components]. Marshalling is used in the same way as unmarshalling above; in the xref:dsl.adoc[DSL] you can use a DataFormat instance, you can configure the DataFormat dynamically using the DSL or you can refer to a named instance of the format in the xref:registry.adoc[Registry].
== Options
@@ -18,7 +18,7 @@ The Marshal EIP supports 1 options which are listed below:
== Samples
-The following example unmarshals via serialization then marshals using a named JAXB data format to perform a kind of https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-translator.adoc[Message Translator]
+The following example unmarshals via serialization then marshals using a named JAXB data format to perform a kind of xref:message-translator.adoc[Message Translator].
[source,java]
----
diff --git a/docs/user-manual/modules/ROOT/pages/message-endpoint.adoc b/docs/user-manual/modules/ROOT/pages/message-endpoint.adoc
index 8c65bc5..04c606f 100644
--- a/docs/user-manual/modules/ROOT/pages/message-endpoint.adoc
+++ b/docs/user-manual/modules/ROOT/pages/message-endpoint.adoc
@@ -24,5 +24,5 @@ implementations.
[[messageEndpoint-Example]]
== Samples
-See first example in https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/to-eip.adoc[To EIP]
+See first example in xref:to-eip.adoc[To EIP]
diff --git a/docs/user-manual/modules/ROOT/pages/message.adoc b/docs/user-manual/modules/ROOT/pages/message.adoc
index 2fb828e..8b0d05c 100644
--- a/docs/user-manual/modules/ROOT/pages/message.adoc
+++ b/docs/user-manual/modules/ROOT/pages/message.adoc
@@ -41,4 +41,4 @@ from("direct:startInOut")
.inOut("bean:process");
----
-See https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/to-eip.adoc[to-eip with pattern]
+See xref:to-eip.adoc[to-eip with pattern]
diff --git a/docs/user-manual/modules/ROOT/pages/pipeline-eip.adoc b/docs/user-manual/modules/ROOT/pages/pipeline-eip.adoc
index 6ef174e..da8af8c 100644
--- a/docs/user-manual/modules/ROOT/pages/pipeline-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/pipeline-eip.adoc
@@ -2,12 +2,12 @@
= Pipeline EIP
:page-source: core/camel-core/src/main/docs/eips/pipeline-eip.adoc
-Camel supports the http://www.enterpriseintegrationpatterns.com/PipesAndFilters.html[Pipes and Filters] from the https://github.com/apache/camel/blob/master/docs/user-manual/en/enterprise-integration-patterns.adoc[EIP patterns] in various ways.
+Camel supports the http://www.enterpriseintegrationpatterns.com/PipesAndFilters.html[Pipes and Filters] from the xref:enterprise-integration-patterns.adoc[EIP patterns] in various ways.
image::eip/PipesAndFilters.gif[image]
With Camel you can split your processing across multiple independent
-https://github.com/apache/camel/blob/master/docs/user-manual/en/endpoint.adoc[Endpoint] instances which can then be chained
+xref:endpoint.adoc[Endpoint] instances which can then be chained
together.
== Options
@@ -20,7 +20,7 @@ The Pipeline EIP has no options.
== Examples
You can create pipelines of logic using multiple
-https://github.com/apache/camel/blob/master/docs/user-manual/en/endpoint.adoc[Endpoint] or https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-translator.adoc[Message
+xref:endpoint.adoc[Endpoint] or xref:message-translator.adoc[Message
Translator] instances as follows
Though pipeline is the default mode of operation when you specify
diff --git a/docs/user-manual/modules/ROOT/pages/process-eip.adoc b/docs/user-manual/modules/ROOT/pages/process-eip.adoc
index 6f170e6..24254c8 100644
--- a/docs/user-manual/modules/ROOT/pages/process-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/process-eip.adoc
@@ -2,7 +2,7 @@
= Process EIP
:page-source: core/camel-core/src/main/docs/eips/process-eip.adoc
-The http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html[Processor] interface is used to implement consumers of message exchanges or to implement a https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-translator.adoc[Message Translator]
+The http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html[Processor] interface is used to implement consumers of message exchanges or to implement a xref:message-translator.adoc[Message Translator]
== Options
@@ -33,7 +33,7 @@ public class MyProcessor implements Processor {
You can then easily use this inside a route by declaring the bean in
Spring, say via the XML (or registering it in JNDI if that is your
-https://github.com/apache/camel/blob/master/docs/user-manual/en/registry.adoc[Registry])
+xref:registry.adoc[Registry])
[source,xml]
--------------------------------------------------------
@@ -59,7 +59,7 @@ Processor myProcessor = new MyProcessor();
from("activemq:myQueue").process(myProcessor);
----
-If you need to lookup the processor in the https://github.com/apache/camel/blob/master/docs/user-manual/en/registry.adoc[Registry]
+If you need to lookup the processor in the xref:registry.adoc[Registry]
then you should use the *processRef* DSL:
[source,java]
diff --git a/docs/user-manual/modules/ROOT/pages/rollback-eip.adoc b/docs/user-manual/modules/ROOT/pages/rollback-eip.adoc
index 94c6fcb..7b90f26 100644
--- a/docs/user-manual/modules/ROOT/pages/rollback-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/rollback-eip.adoc
@@ -10,7 +10,7 @@ using spring transactions.
image::eip/TransactionalClientSolution.gif[image]
-Transaction Oriented Endpoints like https://github.com/apache/camel/blob/master/components/camel-jms/src/main/docs/jms-component.adoc[JMS] support using a
+Transaction Oriented Endpoints like xref:components::jms-component.adoc[JMS] support using a
transaction for both inbound and outbound message exchanges. Endpoints
that support transactions will participate in the current transaction
context that they are called from.
@@ -116,7 +116,7 @@ from("activemq:queue:foo").policy(notsupported).to("activemq:queue:bar");
=== OSGi Blueprint
-If you are using https://github.com/apache/camel/blob/master/docs/user-manual/en/using-osgi-blueprint-with-camel.adoc[OSGi
+If you are using xref:using-osgi-blueprint-with-camel.adoc[OSGi
Blueprint] then you most likely have to explicit declare a policy and
refer to the policy from the transacted in the route.
@@ -189,7 +189,7 @@ Transaction error handler
When a route is marked as transacted using *transacted* Camel will
automatic use the
xref:transactionerrorhandler.adoc[TransactionErrorHandler] as
-https://github.com/apache/camel/blob/master/docs/user-manual/en/error-handler.adoc[Error Handler]. It supports basically the same
+xref:error-handler.adoc[Error Handler]. It supports basically the same
feature set as the xref:defaulterrorhandler.adoc[DefaultErrorHandler],
so you can for instance use xref:exception-clause.adoc[Exception Clause]
as well.
diff --git a/docs/user-manual/modules/ROOT/pages/step-eip.adoc b/docs/user-manual/modules/ROOT/pages/step-eip.adoc
index 5a19d9c..e823cfd 100644
--- a/docs/user-manual/modules/ROOT/pages/step-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/step-eip.adoc
@@ -2,7 +2,7 @@
= Step EIP
:page-source: core/camel-core/src/main/docs/eips/step-eip.adoc
-Camel supports the http://www.enterpriseintegrationpatterns.com/PipesAndFilters.html[Pipes and Filters] from the https://github.com/apache/camel/blob/master/docs/user-manual/en/enterprise-integration-patterns.adoc[EIP patterns] in various ways.
+Camel supports the http://www.enterpriseintegrationpatterns.com/PipesAndFilters.html[Pipes and Filters] from the xref:enterprise-integration-patterns.adoc[EIP patterns] in various ways.
image::eip/PipesAndFilters.gif[image]
diff --git a/docs/user-manual/modules/ROOT/pages/to-eip.adoc b/docs/user-manual/modules/ROOT/pages/to-eip.adoc
index 3f1fdfc..d4bd761 100644
--- a/docs/user-manual/modules/ROOT/pages/to-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/to-eip.adoc
@@ -4,12 +4,12 @@
See message related documentation
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message.adoc[Message]
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-bus.adoc[Message Bus]
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-channel.adoc[Message Channel]
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-endpoint.adoc[Message Endpoint]
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-router.adoc[Message Router]
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-translator.adoc[Message Translator]
+* xref:message.adoc[Message]
+* xref:message-bus.adoc[Message Bus]
+* xref:message-channel.adoc[Message Channel]
+* xref:message-endpoint.adoc[Message Endpoint]
+* xref:message-router.adoc[Message Router]
+* xref:message-translator.adoc[Message Translator]
== Options
diff --git a/docs/user-manual/modules/ROOT/pages/transform-eip.adoc b/docs/user-manual/modules/ROOT/pages/transform-eip.adoc
index 750bb99..3e7ba8c 100644
--- a/docs/user-manual/modules/ROOT/pages/transform-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/transform-eip.adoc
@@ -4,7 +4,7 @@
See below for details
-* https://github.com/apache/camel/blob/master/camel-core/src/main/docs/eips/message-translator.adoc[Message Translator]
+* xref:message-translator.adoc[Message Translator]
== Options
diff --git a/docs/user-manual/modules/ROOT/pages/unmarshal-eip.adoc b/docs/user-manual/modules/ROOT/pages/unmarshal-eip.adoc
index 7d52d01..8204421 100644
--- a/docs/user-manual/modules/ROOT/pages/unmarshal-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/unmarshal-eip.adoc
@@ -29,7 +29,7 @@ from("activemq:My.Queue").
to("mqseries:Another.Queue");
----
-The above uses a named DataFormat of _jaxb_ which is configured with a number of Java package names. You can if you prefer use a named reference to a data format which can then be defined in your https://github.com/apache/camel/blob/master/docs/user-manual/en/registry.adoc[Registry] such as via your xref:components::spring.adoc[Spring] XML file.
+The above uses a named DataFormat of _jaxb_ which is configured with a number of Java package names. You can if you prefer use a named reference to a data format which can then be defined in your xref:registry.adoc[Registry] such as via your xref:components::spring.adoc[Spring] XML file.
You can also use the DSL itself to define the data format as you use it.
For example the following uses Java serialization to unmarshal a binary