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 2a74add29db94862a30502593e59b3f35981b567
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Mon Jul 1 05:36:36 2019 +0200
Regen
---
.../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/file-language.adoc | 34 +++++++++++-----------
.../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 +--
.../modules/ROOT/pages/simple-language.adoc | 24 +++++++--------
docs/user-manual/modules/ROOT/pages/toD-eip.adoc | 14 ++++-----
.../modules/ROOT/pages/wireTap-eip.adoc | 4 +--
14 files changed, 91 insertions(+), 91 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/aggregate-eip.adoc
b/docs/user-manual/modules/ROOT/pages/aggregate-eip.adoc
index 9965366..7b3082e 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 xref:sql-component.adoc[SQL Component]
components.
+xref:leveldb.adoc[LevelDB], or <<sql-component,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 d0c9ccc..b60d58e 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 xref:Registry-Registry.adoc[Registry]
+the <<Registry-Registry,Registry>>
=== EIP options
@@ -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 <<bean-component,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 <<bean-component,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
+* <<class-component,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 d2fa9b5..a892778 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 xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]
+=== Using the <<FluentBuilders-FluentBuilders,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 xref:SpringXMLExtensions-SpringXMLExtensions.adoc[Spring XML
Extensions]
+=== Using the <<SpringXMLExtensions-SpringXMLExtensions,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
-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
+<<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
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 dd93503..5292374 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
-xref:EnterpriseIntegrationPatterns-EnterpriseIntegrationPatterns.adoc[EIP
patterns]
+<<EnterpriseIntegrationPatterns-EnterpriseIntegrationPatterns,EIP patterns>>
using one of the following mechanisms in the routing logic to transform
content from the inbound message.
-* xref:messageTranslator-eip.adoc[Message Translator]
-* invoking a xref:BeanIntegration-BeanIntegration.adoc[Java bean]
-* xref:Processor-Processor.adoc[Processor] object
+* <<messageTranslator-eip,Message Translator>>
+* invoking a <<BeanIntegration-BeanIntegration,Java bean>>
+* <<Processor-Processor,Processor>> object
image:http://www.enterpriseintegrationpatterns.com/img/ContentFilter.gif[image]
A common way to filter messages is to use an
-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].
+<<Expression-Expressions,Expression>> in the <<DSL-DSL,DSL>> like
+<<xquery-language,XQuery>>, <<sql-language,SQL>> or one of the supported
+<<ScriptingLanguages-ScriptingLanguages,Scripting Languages>>.
-=== Using the xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]
+=== Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>
-Here is a simple example using the xref:DSL-DSL.adoc[DSL] directly
+Here is a simple example using the <<DSL-DSL,DSL>> directly
-In this example we add our own xref:Processor-Processor.adoc[Processor]
+In this example we add our own <<Processor-Processor,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
-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
+<<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
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 d55ee91..e25baef 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 xref:bean-component.adoc[Bean] to compute the slip
+Which will leverage a <<bean-component,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,XPath>> or <<xpath-language.adoc[XQuery].
+<<xpath-language,XPath>> or <<xpath-language,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
+* <<bean-component,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 6334e97..a3082aa 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
-xref:EnterpriseIntegrationPatterns-EnterpriseIntegrationPatterns.adoc[EIP
patterns].
+<<EnterpriseIntegrationPatterns-EnterpriseIntegrationPatterns,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 xref:messageEndpoint-eip.adoc[Message
Endpoint]
-when a xref:message-eip.adoc[Message] is available for processing.
+interface which is invoked by the <<messageEndpoint-eip,Message Endpoint>>
+when a <<message-eip,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 xref:Registry-Registry.adoc[Registry] which is
-invoked when an event occurs from a xref:jms-component.adoc[JMS] queue.
+defined in the Camel <<Registry-Registry,Registry>> which is
+invoked when an event occurs from a <<jms-component,JMS>> queue.
-*Using the xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]*
+*Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>*
[source,java]
----
@@ -32,7 +32,7 @@ from("jms:queue:foo")
.processRef("processor");
----
-**Using the xref:SpringXMLExtensions-SpringXMLExtensions.adoc[Spring XML
Extensions]**
+**Using the <<SpringXMLExtensions-SpringXMLExtensions,Spring XML Extensions>>**
[source,xml]
----
@@ -44,15 +44,15 @@ from("jms:queue:foo")
For more details see:
-* xref:message-eip.adoc[Message]
-* xref:messageEndpoint-eip.adoc[Message Endpoint]
+* <<message-eip,Message>>
+* <<messageEndpoint-eip,Message Endpoint>>
[[eventDrivenConsumer-UsingThisPattern]]
=== Using This Pattern
If you would like to use this EIP Pattern then please read the
-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
+<<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
this pattern out.
diff --git a/docs/user-manual/modules/ROOT/pages/file-language.adoc
b/docs/user-manual/modules/ROOT/pages/file-language.adoc
index 41e7914..4f3dbe2 100644
--- a/docs/user-manual/modules/ROOT/pages/file-language.adoc
+++ b/docs/user-manual/modules/ROOT/pages/file-language.adoc
@@ -4,11 +4,11 @@
*Available as of Camel version 1.1*
The file language is merged with
-xref:simple-language.adoc[Simple] language which means you can use all the file
+<<simple-language,Simple>> language which means you can use all the file
syntax directly within the simple language.
The File Expression Language is an extension to the
-xref:simple-language.adoc[Simple] language, adding file related capabilities.
+<<simple-language,Simple>> language, adding file related capabilities.
These capabilities are related to common use cases working with file
path and names. The goal is to allow expressions to be used with the
File and FTP components for setting
@@ -31,18 +31,18 @@ The File language supports 2 options, which are listed
below.
=== Syntax
-This language is an *extension* to the xref:simple-language.adoc[Simple]
language
-so the xref:simple-language.adoc[Simple] syntax applies also. So the table
below
+This language is an *extension* to the <<simple-language,Simple>> language
+so the <<simple-language,Simple>> syntax applies also. So the table below
only lists the additional. +
- As opposed to xref:simple-language.adoc[Simple] language
-xref:file-language.adoc[File Language] also supports
-xref:constant-language.adoc[Constant] expressions so you can enter a fixed
+ As opposed to <<simple-language,Simple>> language
+<<file-language,File Language>> also supports
+<<constant-language,Constant>> expressions so you can enter a fixed
filename.
All the file tokens use the same expression name as the method on the
`java.io.File` object, for instance `file:absolute` refers to the
`java.io.File.getAbsolute()` method. Notice that not all expressions are
-supported by the current Exchange. For instance the
xref:ftp-component.adoc[FTP]
+supported by the current Exchange. For instance the <<ftp-component,FTP>>
component supports some of the options, where as the
File component supports all of them.
@@ -94,9 +94,9 @@ this expression strips only the last part, and keep the
others.
|file:modified |Date |yes |no |yes |no |Refers to the file last modified
returned as a Date type
|date:_command:pattern_ |String |yes |yes |yes |yes |for date formatting using
the `java.text.SimpleDateFormat` patterns. Is
-an *extension* to the xref:simple-language.adoc[Simple] language. Additional
+an *extension* to the <<simple-language,Simple>> language. Additional
command is: *file* (consumers only) for the last modified timestamp of
-the file. Notice: all the commands from the xref:simple-language.adoc[Simple]
+the file. Notice: all the commands from the <<simple-language,Simple>>
language can also be used.
|===
@@ -170,7 +170,7 @@ return as:
=== Samples
-You can enter a fixed xref:constant-language.adoc[Constant] expression such as
+You can enter a fixed <<constant-language,Constant>> expression such as
`myfile.txt`:
[source]
@@ -195,7 +195,7 @@ should be a sibling folder then you can append .. as:
fileName="../backup/${date:now:yyyyMMdd}/${file:name.noext}.bak"
----
-As this is an extension to the xref:simple-language.adoc[Simple] language we
have
+As this is an extension to the <<simple-language,Simple>> language we have
access to all the goodies from this language also, so in this use case
we want to use the in.header.type as a parameter in the dynamic
expression:
@@ -222,14 +222,14 @@
fileName="uniquefile-${bean:myguidgenerator.generateid}.txt"
----
And of course all this can be combined in one expression where you can
-use the xref:file-language,File Language>>, <<file-language.adoc[Simple]
-and the xref:bean-component.adoc[Bean] language in one combined expression.
This
+use the <<file-language,File Language>>, <<file-language,Simple>>
+and the <<bean-component,Bean>> language in one combined expression. This
is pretty powerful for those common file path patterns.
=== Using Spring PropertyPlaceholderConfigurer together with the File component
-In Camel you can use the xref:file-language.adoc[File Language] directly
-from the xref:simple-language.adoc[Simple] language which makes a
+In Camel you can use the <<file-language,File Language>> directly
+from the <<simple-language,Simple>> language which makes a
Content Based Router easier to do in
Spring XML, where we can route based on file extensions as shown below:
@@ -252,7 +252,7 @@ Spring XML, where we can route based on file extensions as
shown below:
----
If you use the `fileName` option on the File endpoint
-to set a dynamic filename using the xref:file-language.adoc[File Language]
then make sure you +
+to set a dynamic filename using the <<file-language,File Language>> then make
sure you +
use the alternative syntax to avoid
clashing with Springs `PropertyPlaceholderConfigurer`.
diff --git a/docs/user-manual/modules/ROOT/pages/idempotentConsumer-eip.adoc
b/docs/user-manual/modules/ROOT/pages/idempotentConsumer-eip.adoc
index 2c61d34..08aa4aa 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]
-* xref:sql-component.adoc[JdbcMessageIdRepository]
-* xref:jpa-component.adoc[JpaMessageIdRepository]
-* xref:infinispan-component.adoc[InfinispanIdempotentRepository]
-* xref:jcache-component.adoc[JCacheIdempotentRepository]
+* <<sql-component,JdbcMessageIdRepository>>
+* <<jpa-component,JpaMessageIdRepository>>
+* <<infinispan-component,InfinispanIdempotentRepository>>
+* <<jcache-component,JCacheIdempotentRepository>>
* xref:spring.adoc[SpringCacheIdempotentRepository]
-* xref:ehcache-component.adoc[EhcacheIdempotentRepository]
-* xref:kafka-component.adoc[KafkaIdempotentRepository]
+* <<ehcache-component,EhcacheIdempotentRepository>>
+* <<kafka-component,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 d2f1420..823f5c0 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 xref:log-component.adoc[Log] component which logs the
Message content.
+* You can use the <<log-component,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
xref:simple-language.adoc[Simple] language to construct a dynamic message which
gets logged.
+You can use the log DSL which allows you to use <<simple-language,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 xref:log-component.adoc[Log] component.
+Note that this option also affects <<log-component,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 25e4915..17c2d0b 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 xref:Endpoint-Endpoints.adoc[Endpoint] semantics given
a
+which supports the full <<Endpoint-Endpoints,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 68ac289..38103bb 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 xref:jms-component.adoc[JMS] with InOut the component
will
+For example when using <<jms-component,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 <<jms-component,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/simple-language.adoc
b/docs/user-manual/modules/ROOT/pages/simple-language.adoc
index 52fdee0..af1b5ae 100644
--- a/docs/user-manual/modules/ROOT/pages/simple-language.adoc
+++ b/docs/user-manual/modules/ROOT/pages/simple-language.adoc
@@ -8,17 +8,17 @@ created, but has since grown more powerful. It is primarily
intended for
being a really small and simple language for evaluating
Expressions and Predicates
without requiring any new dependencies or knowledge of
-xref:xpath-language.adoc[XPath]; so it is ideal for testing in camel-core. The
+<<xpath-language,XPath>>; so it is ideal for testing in camel-core. The
idea was to cover 95% of the common use cases when you need a little bit
of expression based script in your Camel routes.
However for much more complex use cases you are generally recommended to
choose a more expressive and powerful language such as:
-* xref:groovy-language.adoc[Groovy]
-* xref:spel-language.adoc[SpEL]
-* xref:mvel-component.adoc[MVEL]
-* xref:ognl-language.adoc[OGNL]
+* <<groovy-language,Groovy>>
+* <<spel-language,SpEL>>
+* <<mvel-component,MVEL>>
+* <<ognl-language,OGNL>>
The simple language uses `${body`} placeholders for complex expressions
where the expression contains constant literals. The $\{ } placeholders
@@ -188,9 +188,9 @@ Command accepts offsets such as: *now-24h* or
*in.header.xxx+1h* or even *now+1h
|date-with-timezone:_command:timezone:pattern_ |String |Date formatting using
`java.text.SimpleDataFormat` timezones and patterns.
-|bean:_bean expression_ |Object |Invoking a bean expression using the
xref:bean-component.adoc[Bean] language.
+|bean:_bean expression_ |Object |Invoking a bean expression using the
<<bean-component,Bean>> language.
Specifying a method name you must use dot as separator. We also support
-the ?method=methodname syntax that is used by the
xref:bean-component.adoc[Bean]
+the ?method=methodname syntax that is used by the <<bean-component,Bean>>
component.
|properties-location:_http://locationskey[locations:key]_ |String |Lookup a
property with the given key. The `locations`
@@ -250,7 +250,7 @@ INFO:Camel's OGNL support is for invoking methods only. You
cannot access
fields. Camel support accessing the length field of Java arrays.
-The xref:simple-language,Simple>> and <<simple-language.adoc[Bean] language now
+The <<simple-language,Simple>> and <<simple-language,Bean>> language now
supports a Camel OGNL notation for invoking beans in a chain like
fashion. Suppose the Message IN body contains a POJO which has a `getAddress()`
method.
@@ -471,7 +471,7 @@ function, otherwise parsed as literal.
|\ |To escape a value, eg \$, to indicate a $ sign.
Special: Use \n for new line, \t for tab, and \r for carriage return.
*Notice:* Escaping is *not* supported using the
-xref:file-language.adoc[File Language]. *Notice:* The escape character is not
supported, use the
+<<file-language,File Language>>. *Notice:* The escape character is not
supported, use the
following three special escaping instead.
|\n |To use newline character.
@@ -759,7 +759,7 @@ from("direct:order")
----
We can use the `?method=methodname` option that we are familiar with the
-xref:bean-component.adoc[Bean] component itself:
+<<bean-component,Bean>> component itself:
[source,java]
----
@@ -811,7 +811,7 @@ You can nest functions, such as shown below:
Suppose you have an enum for customers
And in a Content Based Router we can use
-the xref:simple-language.adoc[Simple] language to refer to this enum, to check
+the <<simple-language,Simple>> language to refer to this enum, to check
the message which enum it matches.
=== Using new lines or tabs in XML DSLs
@@ -842,7 +842,7 @@ whitespace characters.
=== Setting result type
-You can now provide a result type to the xref:simple-language.adoc[Simple]
+You can now provide a result type to the <<simple-language,Simple>>
expression, which means the result of the evaluation will be converted
to the desired type. This is most usable to define types such as
booleans, integers, etc.
diff --git a/docs/user-manual/modules/ROOT/pages/toD-eip.adoc
b/docs/user-manual/modules/ROOT/pages/toD-eip.adoc
index 35d3c68..bc7c5ae 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 xref:Endpoint-Endpoints.adoc[Endpoint] using one or
+computed <<Endpoint-Endpoints,Endpoint>> using one or
more xref:expression.adoc[Expression] that are concat together. By
-default the xref:simple-language.adoc[Simple] language is used to compute
+default the <<simple-language,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 xref:simple-language.adoc[Simple] language
+evaluated using the <<simple-language,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 xref:simple-language.adoc[Simple] such
-as xref:xpath-language.adoc[XPath] - this requires to prefix with language: as
+You can also use other languages than <<simple-language,Simple>> such
+as <<xpath-language,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 <<language-component,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 xref:simple-language,Simple>> language and <<simple-language.adoc[XPath]
where
+of <<simple-language,Simple>> language and <<simple-language,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 5cf420d..a1eb640 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 xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]
+* Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>
[source,java]
----
@@ -95,7 +95,7 @@ values.
=== Sending a New xref:exchange.adoc[Exchange]
-*Using the xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]*
+*Using the <<FluentBuilders-FluentBuilders,Fluent Builders>>*
Camel supports either a processor or an
xref:expression.adoc[Expression] to populate the new
