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 702d9910276ed71320866c50257d8d7bee5a3543
Author: nayananga@acerubuntu18.04 <nayanangamuhandi...@gmail.com>
AuthorDate: Sat Jun 29 23:10:43 2019 +0530
ran yarn gulp inside camel/docs
---
.../modules/ROOT/pages/aggregate-eip.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/bean-eip.adoc | 8 +++----
.../ROOT/pages/content-based-router-eip.adoc | 12 +++++-----
.../modules/ROOT/pages/content-filter-eip.adoc | 28 +++++++++++-----------
.../modules/ROOT/pages/dynamic-router.adoc | 6 ++---
.../ROOT/pages/eventDrivenConsumer-eip.adoc | 26 ++++++++++----------
.../modules/ROOT/pages/idempotentConsumer-eip.adoc | 12 +++++-----
docs/user-manual/modules/ROOT/pages/log-eip.adoc | 6 ++---
.../modules/ROOT/pages/process-eip.adoc | 2 +-
.../modules/ROOT/pages/requestReply-eip.adoc | 4 ++--
docs/user-manual/modules/ROOT/pages/toD-eip.adoc | 14 +++++------
.../modules/ROOT/pages/wireTap-eip.adoc | 4 ++--
12 files changed, 62 insertions(+), 62 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/aggregate-eip.adoc
b/docs/user-manual/modules/ROOT/pages/aggregate-eip.adoc
index 7b3082e..9965366 100644
--- a/docs/user-manual/modules/ROOT/pages/aggregate-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/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 <<sql-component,SQL Component>> components.
+xref:leveldb.adoc[LevelDB], or xref:sql-component.adoc[SQL Component]
components.
=== Using TimeoutAwareAggregationStrategy
diff --git a/docs/user-manual/modules/ROOT/pages/bean-eip.adoc
b/docs/user-manual/modules/ROOT/pages/bean-eip.adoc
index b60d58e..d0c9ccc 100644
--- a/docs/user-manual/modules/ROOT/pages/bean-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/bean-eip.adoc
@@ -11,7 +11,7 @@ bean:beanID[?options]
----
Where *beanID* can be any string which is used to look up the bean in
-the <<Registry-Registry,Registry>>
+the xref:Registry-Registry.adoc[Registry]
=== EIP options
@@ -30,7 +30,7 @@ The Bean EIP supports 4 options which are listed below:
=== Bean as endpoint
-Camel also supports invoking <<bean-component,Bean>> as an Endpoint. In the
+Camel also supports invoking xref: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 <<bean-component,Bean>>
+Java DSL comes with syntactic sugar for the xref: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
-* <<class-component,Class>> component
+* xref:class-component.adoc[Class] component
* xref:bean-binding.adoc[Bean Binding]
* xref:bean-integration.adoc[Bean Integration]
diff --git a/docs/user-manual/modules/ROOT/pages/content-based-router-eip.adoc
b/docs/user-manual/modules/ROOT/pages/content-based-router-eip.adoc
index a892778..d2fa9b5 100644
--- a/docs/user-manual/modules/ROOT/pages/content-based-router-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/content-based-router-eip.adoc
@@ -13,7 +13,7 @@ The following example shows how to route a request from an
input
*seda:a* endpoint to either *seda:b*, *seda:c* or *seda:d* depending on
the evaluation of various xref:predicate.adoc[Predicate] expressions
-=== Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>
+=== Using the xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]
[source,java]
----
@@ -41,7 +41,7 @@ can I not use when or otherwise in a Java Camel route] if you
have
problems with the Java DSL, accepting using `when` or `otherwise`.
====
-=== Using the <<SpringXMLExtensions-SpringXMLExtensions,Spring XML Extensions>>
+=== Using the xref:SpringXMLExtensions-SpringXMLExtensions.adoc[Spring XML
Extensions]
[source,java]
----
@@ -72,8 +72,8 @@
https://github.com/apache/camel/blob/master/camel-core/src/test/java/org/apache/
=== Using This Pattern
If you would like to use this EIP Pattern then please read the
-<<GettingStarted-GettingStarted,Getting Started>>. You may also find the
-<<Architecture-Architecture,Architecture>> useful particularly the description
-of <<Endpoint-Endpoints,Endpoint>> and xref:uris.adoc[URIs]. Then you could
-try out some of the <<Examples-Examples,Examples>> first before trying
+xref:GettingStarted-GettingStarted.adoc[Getting Started]. You may also find the
+xref:Architecture-Architecture.adoc[Architecture] useful particularly the
description
+of xref:Endpoint-Endpoints.adoc[Endpoint] and xref:uris.adoc[URIs]. Then you
could
+try out some of the xref:Examples-Examples.adoc[Examples] first before trying
this pattern out.
diff --git a/docs/user-manual/modules/ROOT/pages/content-filter-eip.adoc
b/docs/user-manual/modules/ROOT/pages/content-filter-eip.adoc
index 5292374..dd93503 100644
--- a/docs/user-manual/modules/ROOT/pages/content-filter-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/content-filter-eip.adoc
@@ -4,26 +4,26 @@
Camel supports the
http://www.enterpriseintegrationpatterns.com/ContentFilter.html[Content
Filter] from the
-<<EnterpriseIntegrationPatterns-EnterpriseIntegrationPatterns,EIP patterns>>
+xref:EnterpriseIntegrationPatterns-EnterpriseIntegrationPatterns.adoc[EIP
patterns]
using one of the following mechanisms in the routing logic to transform
content from the inbound message.
-* <<messageTranslator-eip,Message Translator>>
-* invoking a <<BeanIntegration-BeanIntegration,Java bean>>
-* <<Processor-Processor,Processor>> object
+* xref:messageTranslator-eip.adoc[Message Translator]
+* invoking a xref:BeanIntegration-BeanIntegration.adoc[Java bean]
+* xref:Processor-Processor.adoc[Processor] object
image:http://www.enterpriseintegrationpatterns.com/img/ContentFilter.gif[image]
A common way to filter messages is to use an
-<<Expression-Expressions,Expression>> in the <<DSL-DSL,DSL>> like
-<<xquery-language,XQuery>>, <<sql-language,SQL>> or one of the supported
-<<ScriptingLanguages-ScriptingLanguages,Scripting Languages>>.
+xref:Expression-Expressions,Expression>> in the <<DSL-DSL.adoc[DSL] like
+xref:xquery-language,XQuery>>, <<sql-language.adoc[SQL] or one of the supported
+xref:ScriptingLanguages-ScriptingLanguages.adoc[Scripting Languages].
-=== Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>
+=== Using the xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]
-Here is a simple example using the <<DSL-DSL,DSL>> directly
+Here is a simple example using the xref:DSL-DSL.adoc[DSL] directly
-In this example we add our own <<Processor-Processor,Processor>>
+In this example we add our own xref:Processor-Processor.adoc[Processor]
For further examples of this pattern in use you could look at one of the
JUnit tests
@@ -58,8 +58,8 @@ interested in:
=== Using This Pattern
If you would like to use this EIP Pattern then please read the
-<<GettingStarted-GettingStarted,Getting Started>>, you may also find the
-<<Architecture-Architecture,Architecture>> useful particularly the description
-of <<Endpoint-Endpoints,Endpoint>> and <<URIs-URIs,URIs>>. Then you could
-try out some of the <<Examples-Examples,Examples>> first before trying
+xref:GettingStarted-GettingStarted.adoc[Getting Started], you may also find the
+xref:Architecture-Architecture.adoc[Architecture] useful particularly the
description
+of xref:Endpoint-Endpoints,Endpoint>> and <<URIs-URIs.adoc[URIs]. Then you
could
+try out some of the xref:Examples-Examples.adoc[Examples] first before trying
this pattern out.
diff --git a/docs/user-manual/modules/ROOT/pages/dynamic-router.adoc
b/docs/user-manual/modules/ROOT/pages/dynamic-router.adoc
index e25baef..d55ee91 100644
--- a/docs/user-manual/modules/ROOT/pages/dynamic-router.adoc
+++ b/docs/user-manual/modules/ROOT/pages/dynamic-router.adoc
@@ -60,7 +60,7 @@ from("direct:start")
.dynamicRouter(method(DynamicRouterTest.class, "slip"));
----
-Which will leverage a <<bean-component,Bean>> to compute the slip
+Which will leverage a xref: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
-<<xpath-language,XPath>> or <<xpath-language,XQuery>>.
+xref:xpath-language,XPath>> or <<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
-* <<bean-component,Bean>> component
+* xref:bean-component.adoc[Bean] component
diff --git a/docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc
b/docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc
index a3082aa..6334e97 100644
--- a/docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc
@@ -4,7 +4,7 @@
Camel supports the
http://www.enterpriseintegrationpatterns.com/EventDrivenConsumer.html[Event
Driven Consumer]
from the
-<<EnterpriseIntegrationPatterns-EnterpriseIntegrationPatterns,EIP patterns>>.
+xref:EnterpriseIntegrationPatterns-EnterpriseIntegrationPatterns.adoc[EIP
patterns].
The default consumer model is event based (i.e. asynchronous)
as this means that the Camel container can then manage pooling,
threading and concurrency for you in a declarative manner.
@@ -13,18 +13,18 @@
image:http://www.enterpriseintegrationpatterns.com/img/EventDrivenConsumerSoluti
The Event Driven Consumer is implemented by consumers implementing the
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html[Processor]
-interface which is invoked by the <<messageEndpoint-eip,Message Endpoint>>
-when a <<message-eip,Message>> is available for processing.
+interface which is invoked by the xref:messageEndpoint-eip.adoc[Message
Endpoint]
+when a xref:message-eip.adoc[Message] is available for processing.
[[eventDrivenConsumer-Example]]
=== Example
The following demonstrates a
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html[Processor]
-defined in the Camel <<Registry-Registry,Registry>> which is
-invoked when an event occurs from a <<jms-component,JMS>> queue.
+defined in the Camel xref:Registry-Registry.adoc[Registry] which is
+invoked when an event occurs from a xref:jms-component.adoc[JMS] queue.
-*Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>*
+*Using the xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]*
[source,java]
----
@@ -32,7 +32,7 @@ from("jms:queue:foo")
.processRef("processor");
----
-**Using the <<SpringXMLExtensions-SpringXMLExtensions,Spring XML Extensions>>**
+**Using the xref:SpringXMLExtensions-SpringXMLExtensions.adoc[Spring XML
Extensions]**
[source,xml]
----
@@ -44,15 +44,15 @@ from("jms:queue:foo")
For more details see:
-* <<message-eip,Message>>
-* <<messageEndpoint-eip,Message Endpoint>>
+* xref:message-eip.adoc[Message]
+* xref:messageEndpoint-eip.adoc[Message Endpoint]
[[eventDrivenConsumer-UsingThisPattern]]
=== Using This Pattern
If you would like to use this EIP Pattern then please read the
-<<GettingStarted-GettingStarted,Getting Started>>, you may also find the
-<<Architecture-Architecture,Architecture>> useful particularly the description
-of <<Endpoint-Endpoints,Endpoint>> and <<URIs-URIs,URIs>>. Then you could
-try out some of the <<Examples-Examples,Examples>> first before trying
+xref:GettingStarted-GettingStarted.adoc[Getting Started], you may also find the
+xref:Architecture-Architecture.adoc[Architecture] useful particularly the
description
+of xref:Endpoint-Endpoints,Endpoint>> and <<URIs-URIs.adoc[URIs]. Then you
could
+try out some of the xref:Examples-Examples.adoc[Examples] first before trying
this pattern out.
diff --git a/docs/user-manual/modules/ROOT/pages/idempotentConsumer-eip.adoc
b/docs/user-manual/modules/ROOT/pages/idempotentConsumer-eip.adoc
index 08aa4aa..2c61d34 100644
--- a/docs/user-manual/modules/ROOT/pages/idempotentConsumer-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/idempotentConsumer-eip.adoc
@@ -19,13 +19,13 @@ Camel provides the following Idempotent Consumer
implementations:
* MemoryIdempotentRepository
* xref:file2.adoc[FileIdempotentRepository]
* xref:hazelcast-component.adoc[HazelcastIdempotentRepository]
-* <<sql-component,JdbcMessageIdRepository>>
-* <<jpa-component,JpaMessageIdRepository>>
-* <<infinispan-component,InfinispanIdempotentRepository>>
-* <<jcache-component,JCacheIdempotentRepository>>
+* xref:sql-component.adoc[JdbcMessageIdRepository]
+* xref:jpa-component.adoc[JpaMessageIdRepository]
+* xref:infinispan-component.adoc[InfinispanIdempotentRepository]
+* xref:jcache-component.adoc[JCacheIdempotentRepository]
* xref:spring.adoc[SpringCacheIdempotentRepository]
-* <<ehcache-component,EhcacheIdempotentRepository>>
-* <<kafka-component,KafkaIdempotentRepository>>
+* xref:ehcache-component.adoc[EhcacheIdempotentRepository]
+* xref:kafka-component.adoc[KafkaIdempotentRepository]
=== Options
diff --git a/docs/user-manual/modules/ROOT/pages/log-eip.adoc
b/docs/user-manual/modules/ROOT/pages/log-eip.adoc
index 823f5c0..d2f1420 100644
--- a/docs/user-manual/modules/ROOT/pages/log-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/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 <<log-component,Log>> component which logs the Message
content.
+* You can use the xref: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.
@@ -31,7 +31,7 @@ The log DSL is much lighter and meant for logging human logs
such as Starting to
=== Samples
-You can use the log DSL which allows you to use <<simple-language,Simple>>
language to construct a dynamic message which gets logged.
+You can use the log DSL which allows you to use
xref:simple-language.adoc[Simple] language to construct a dynamic message which
gets logged.
For example you can do
@@ -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 <<log-component,Log>> component.
+Note that this option also affects xref:log-component.adoc[Log] component.
To enable mask in Java DSL at CamelContext level:
[source,java]
diff --git a/docs/user-manual/modules/ROOT/pages/process-eip.adoc
b/docs/user-manual/modules/ROOT/pages/process-eip.adoc
index 17c2d0b..25e4915 100644
--- a/docs/user-manual/modules/ROOT/pages/process-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/process-eip.adoc
@@ -88,7 +88,7 @@ refactor it into a separate class.
There is a base class called
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/ProcessorEndpoint.html[ProcessorEndpoint]
-which supports the full <<Endpoint-Endpoints,Endpoint>> semantics given a
+which supports the full xref:Endpoint-Endpoints.adoc[Endpoint] semantics given
a
Processor instance.
So you just need to create a
https://github.com/apache/camel/tree/master/components[Component] class by
diff --git a/docs/user-manual/modules/ROOT/pages/requestReply-eip.adoc
b/docs/user-manual/modules/ROOT/pages/requestReply-eip.adoc
index 38103bb..68ac289 100644
--- a/docs/user-manual/modules/ROOT/pages/requestReply-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/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 <<jms-component,JMS>> with InOut the component will
+For example when using xref: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 <<jms-component,JMS>> a Request-Reply is
+When consuming messages from xref: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/docs/user-manual/modules/ROOT/pages/toD-eip.adoc
b/docs/user-manual/modules/ROOT/pages/toD-eip.adoc
index bc7c5ae..35d3c68 100644
--- a/docs/user-manual/modules/ROOT/pages/toD-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/toD-eip.adoc
@@ -2,9 +2,9 @@
== To D EIP
There is a new `.toD` / `<toD>` that allows to send a message to a dynamic
-computed <<Endpoint-Endpoints,Endpoint>> using one or
+computed xref:Endpoint-Endpoints.adoc[Endpoint] using one or
more xref:expression.adoc[Expression] that are concat together. By
-default the <<simple-language,Simple>> language is used to compute
+default the xref:simple-language.adoc[Simple] language is used to compute
the endpoint.
=== Options
@@ -45,7 +45,7 @@ And in XML:
----
You can also prefix the uri with a value because by default the uri is
-evaluated using the <<simple-language,Simple>> language
+evaluated using the xref:simple-language.adoc[Simple] language
[source,java]
----
@@ -67,8 +67,8 @@ In the example above we compute an endpoint that has prefix
"mock:" and
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 <<simple-language,Simple>> such
-as <<xpath-language,XPath>> - this requires to prefix with language: as
+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
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 <<language-component,Language>>(s) together
+You can also concat multiple xref:language-component.adoc[Language](s) together
using the plus sign `+` such as shown below:
[source,xml]
@@ -102,7 +102,7 @@ using the plus sign `+` such as shown below:
----
In the example above the uri is a combination
-of <<simple-language,Simple>> language and <<simple-language,XPath>> where
+of xref:simple-language,Simple>> language and <<simple-language.adoc[XPath]
where
the first part is simple (simple is default language). And then the plus
sign separate to another language, where we specify the language name
followed by a colon
diff --git a/docs/user-manual/modules/ROOT/pages/wireTap-eip.adoc
b/docs/user-manual/modules/ROOT/pages/wireTap-eip.adoc
index a1eb640..5cf420d 100644
--- a/docs/user-manual/modules/ROOT/pages/wireTap-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/wireTap-eip.adoc
@@ -68,7 +68,7 @@ values.
=== Sending a Copy (traditional wiretap)
-* Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>
+* Using the xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]
[source,java]
----
@@ -95,7 +95,7 @@ values.
=== Sending a New xref:exchange.adoc[Exchange]
-*Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>*
+*Using the xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]*
Camel supports either a processor or an
xref:expression.adoc[Expression] to populate the new
