This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit da3b41ee7786a741882cda4d3cb3cb62ede0f8c6
Author: nayananga@acerubuntu18.04 <nayanangamuhandi...@gmail.com>
AuthorDate: Fri Jul 19 17:06:01 2019 +0530
fixed incorrect cross references in core/camel-core
---
core/camel-core/src/main/docs/eips/aggregate-eip.adoc | 2 +-
core/camel-core/src/main/docs/eips/bean-eip.adoc | 6 +++---
core/camel-core/src/main/docs/eips/content-filter-eip.adoc | 2 +-
core/camel-core/src/main/docs/eips/dynamic-router.adoc | 6 +++---
.../src/main/docs/eips/eventDrivenConsumer-eip.adoc | 2 +-
.../src/main/docs/eips/idempotentConsumer-eip.adoc | 14 +++++++-------
core/camel-core/src/main/docs/eips/log-eip.adoc | 4 ++--
core/camel-core/src/main/docs/eips/requestReply-eip.adoc | 4 ++--
core/camel-core/src/main/docs/eips/toD-eip.adoc | 4 ++--
core/camel-core/src/main/docs/eips/unmarshal-eip.adoc | 2 +-
10 files changed, 23 insertions(+), 23 deletions(-)
diff --git a/core/camel-core/src/main/docs/eips/aggregate-eip.adoc
b/core/camel-core/src/main/docs/eips/aggregate-eip.adoc
index 9965366..e4e0d3c 100644
--- a/core/camel-core/src/main/docs/eips/aggregate-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/aggregate-eip.adoc
@@ -187,7 +187,7 @@ consumer etc)
The aggregator provides a pluggable repository which you can implement
your own `org.apache.camel.spi.AggregationRepository`. +
If you need persistent repository then you can use either Camel
-xref:leveldb.adoc[LevelDB], or xref:sql-component.adoc[SQL Component]
components.
+xref:components::leveldb.adoc[LevelDB], or
xref:components::sql-component.adoc[SQL Component] components.
=== Using TimeoutAwareAggregationStrategy
diff --git a/core/camel-core/src/main/docs/eips/bean-eip.adoc
b/core/camel-core/src/main/docs/eips/bean-eip.adoc
index d0c9ccc..003c728 100644
--- a/core/camel-core/src/main/docs/eips/bean-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/bean-eip.adoc
@@ -30,7 +30,7 @@ The Bean EIP supports 4 options which are listed below:
=== Bean as endpoint
-Camel also supports invoking xref:bean-component.adoc[Bean] as an Endpoint. In
the
+Camel also supports invoking xref:components::bean-component.adoc[Bean] as an
Endpoint. In the
route below:
What happens is that when the exchange is routed to the `myBean` Camel
@@ -43,7 +43,7 @@ type and storing the output of the method on the Exchange Out
body.
=== Java DSL bean syntax
-Java DSL comes with syntactic sugar for the xref:bean-component.adoc[Bean]
+Java DSL comes with syntactic sugar for the
xref:components::bean-component.adoc[Bean]
component. Instead of specifying the bean explicitly as the endpoint
(i.e. `to("bean:beanName")`) you can use the following syntax:
@@ -84,6 +84,6 @@ mechanisms in Camel.
=== See also
-* xref:class-component.adoc[Class] component
+* xref:components::class-component.adoc[Class] component
* xref:bean-binding.adoc[Bean Binding]
* xref:bean-integration.adoc[Bean Integration]
diff --git a/core/camel-core/src/main/docs/eips/content-filter-eip.adoc
b/core/camel-core/src/main/docs/eips/content-filter-eip.adoc
index 7801314..08a9d98 100644
--- a/core/camel-core/src/main/docs/eips/content-filter-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/content-filter-eip.adoc
@@ -16,7 +16,7 @@
image:http://www.enterpriseintegrationpatterns.com/img/ContentFilter.gif[image]
A common way to filter messages is to use an
xref:Expression-Expressions.adoc[Expression] in the xref:DSL-DSL.adoc[DSL] like
-xref:xquery-language.adoc[XQuery], xref:sql-language.adoc[SQL] or one of the
supported
+xref:components::xquery-language.adoc[XQuery], xref:sql-language.adoc[SQL] or
one of the supported
xref:ScriptingLanguages-ScriptingLanguages.adoc[Scripting Languages].
=== Using the xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]
diff --git a/core/camel-core/src/main/docs/eips/dynamic-router.adoc
b/core/camel-core/src/main/docs/eips/dynamic-router.adoc
index c4c592e..e6866fd 100644
--- a/core/camel-core/src/main/docs/eips/dynamic-router.adoc
+++ b/core/camel-core/src/main/docs/eips/dynamic-router.adoc
@@ -60,7 +60,7 @@ from("direct:start")
.dynamicRouter(method(DynamicRouterTest.class, "slip"));
----
-Which will leverage a xref:bean-component.adoc[Bean] to compute the slip
+Which will leverage a xref:components::bean-component.adoc[Bean] to compute
the slip
_on-the-fly_, which could be implemented as follows:
[source,java]
@@ -191,12 +191,12 @@ In the above we can use the
Parameter Binding Annotations
to bind different parts of the Message to method
parameters or use an Expression such as using
-xref:xpath-language.adoc[XPath] or xref:xpath-language.adoc[XQuery].
+xref:components::xpath-language.adoc[XPath] or
xref:components::xpath-language.adoc[XQuery].
The method can be invoked in a number of ways as described in the
Bean Integration such as
* POJO Producing
* Spring Remoting
-* xref:bean-component.adoc[Bean] component
+* xref:components::bean-component.adoc[Bean] component
diff --git a/core/camel-core/src/main/docs/eips/eventDrivenConsumer-eip.adoc
b/core/camel-core/src/main/docs/eips/eventDrivenConsumer-eip.adoc
index 47a2d62..2fc4f98 100644
--- a/core/camel-core/src/main/docs/eips/eventDrivenConsumer-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/eventDrivenConsumer-eip.adoc
@@ -22,7 +22,7 @@ when a xref:message-eip.adoc[Message] is available for
processing.
The following demonstrates a
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html[Processor]
defined in the Camel xref:Registry-Registry.adoc[Registry] which is
-invoked when an event occurs from a xref:jms-component.adoc[JMS] queue.
+invoked when an event occurs from a xref:components::jms-component.adoc[JMS]
queue.
*Using the xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]*
diff --git a/core/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
b/core/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
index 2c61d34..da153e4 100644
--- a/core/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
@@ -19,13 +19,13 @@ Camel provides the following Idempotent Consumer
implementations:
* MemoryIdempotentRepository
* xref:file2.adoc[FileIdempotentRepository]
* xref:hazelcast-component.adoc[HazelcastIdempotentRepository]
-* xref:sql-component.adoc[JdbcMessageIdRepository]
-* xref:jpa-component.adoc[JpaMessageIdRepository]
-* xref:infinispan-component.adoc[InfinispanIdempotentRepository]
-* xref:jcache-component.adoc[JCacheIdempotentRepository]
-* xref:spring.adoc[SpringCacheIdempotentRepository]
-* xref:ehcache-component.adoc[EhcacheIdempotentRepository]
-* xref:kafka-component.adoc[KafkaIdempotentRepository]
+* xref:components::sql-component.adoc[JdbcMessageIdRepository]
+* xref:components::jpa-component.adoc[JpaMessageIdRepository]
+* xref:components::infinispan-component.adoc[InfinispanIdempotentRepository]
+* xref:components::jcache-component.adoc[JCacheIdempotentRepository]
+* xref:components::spring.adoc[SpringCacheIdempotentRepository]
+* xref:components::ehcache-component.adoc[EhcacheIdempotentRepository]
+* xref:components::kafka-component.adoc[KafkaIdempotentRepository]
=== Options
diff --git a/core/camel-core/src/main/docs/eips/log-eip.adoc
b/core/camel-core/src/main/docs/eips/log-eip.adoc
index d2f1420..86240ac 100644
--- a/core/camel-core/src/main/docs/eips/log-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/log-eip.adoc
@@ -4,7 +4,7 @@
How can I log the processing of a xref:message.adoc[Message]?
Camel provides many ways to log the fact that you are processing a message.
Here are just a few examples:
-* You can use the xref:log-component.adoc[Log] component which logs the
Message content.
+* You can use the xref:components::log-component.adoc[Log] component which
logs the Message content.
* You can use the xref:tracer.adoc[Tracer] which trace logs message flow.
* You can also use a xref:processor.adoc[Processor] or xref:bean.adoc[Bean]
and log from Java code.
* You can use the log DSL.
@@ -165,7 +165,7 @@ In some scenarios it is required that the bundle associated
with logger should b
*Available as of Camel 2.19*
You can enable security masking for logging by setting `logMask` flag to
`true`.
-Note that this option also affects xref:log-component.adoc[Log] component.
+Note that this option also affects xref:components::log-component.adoc[Log]
component.
To enable mask in Java DSL at CamelContext level:
[source,java]
diff --git a/core/camel-core/src/main/docs/eips/requestReply-eip.adoc
b/core/camel-core/src/main/docs/eips/requestReply-eip.adoc
index 68ac289..9c44cba 100644
--- a/core/camel-core/src/main/docs/eips/requestReply-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/requestReply-eip.adoc
@@ -11,7 +11,7 @@ this pattern using the underlying transport or protocols.
image:http://www.enterpriseintegrationpatterns.com/img/RequestReply.gif[image]
-For example when using xref:jms-component.adoc[JMS] with InOut the component
will
+For example when using xref:components::jms-component.adoc[JMS] with InOut the
component will
by default perform these actions
* create by default a temporary inbound queue
@@ -27,7 +27,7 @@ TIP: *Related* See the related Event Message message
[[RequestReply-ExplicitlyspecifyingInOut]]
=== Explicitly specifying InOut
-When consuming messages from xref:jms-component.adoc[JMS] a Request-Reply is
+When consuming messages from xref:components::jms-component.adoc[JMS] a
Request-Reply is
indicated by the presence of the *JMSReplyTo* header.
You can explicitly force an endpoint to be in Request Reply mode by
diff --git a/core/camel-core/src/main/docs/eips/toD-eip.adoc
b/core/camel-core/src/main/docs/eips/toD-eip.adoc
index baf1b62..cbdb5f4 100644
--- a/core/camel-core/src/main/docs/eips/toD-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/toD-eip.adoc
@@ -68,7 +68,7 @@ then the header foo is appended. So for example if the header
foo has
value order, then the endpoint is computed as "mock:order".
You can also use other languages than xref:simple-language.adoc[Simple] such
-as xref:xpath-language.adoc[XPath] - this requires to prefix with language: as
+as xref:components::xpath-language.adoc[XPath] - this requires to prefix with
language: as
shown below (simple language is the default language). If you do not
specify language: then the endpoint is a component name. And in some
cases there is both a component and language with the same name such as
@@ -90,7 +90,7 @@ from("direct:start")
.toD("language:xpath:/order/@uri");
----
-You can also concat multiple xref:language-component.adoc[Language](s) together
+You can also concat multiple
xref:components::language-component.adoc[Language](s) together
using the plus sign `+` such as shown below:
[source,xml]
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 2bb37a5..fe917a8 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: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
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.
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
