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 b456ef9d900c3f1c3c0547558b69f53d2291308f
Author: nayananga@acerubuntu18.04 <nayanangamuhandi...@gmail.com>
AuthorDate: Sat Jun 29 23:08:05 2019 +0530
ran yarn gulp inside camel/docs
---
.../modules/ROOT/pages/file-language.adoc | 34 +++++++++++-----------
.../modules/ROOT/pages/simple-language.adoc | 24 +++++++--------
2 files changed, 29 insertions(+), 29 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/file-language.adoc
b/docs/user-manual/modules/ROOT/pages/file-language.adoc
index 4f3dbe2..41e7914 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
-<<simple-language,Simple>> language which means you can use all the file
+xref:simple-language.adoc[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
-<<simple-language,Simple>> language, adding file related capabilities.
+xref:simple-language.adoc[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 <<simple-language,Simple>> language
-so the <<simple-language,Simple>> syntax applies also. So the table below
+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
only lists the additional. +
- As opposed to <<simple-language,Simple>> language
-<<file-language,File Language>> also supports
-<<constant-language,Constant>> expressions so you can enter a fixed
+ 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
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 <<ftp-component,FTP>>
+supported by the current Exchange. For instance the
xref:ftp-component.adoc[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 <<simple-language,Simple>> language. Additional
+an *extension* to the xref:simple-language.adoc[Simple] language. Additional
command is: *file* (consumers only) for the last modified timestamp of
-the file. Notice: all the commands from the <<simple-language,Simple>>
+the file. Notice: all the commands from the xref:simple-language.adoc[Simple]
language can also be used.
|===
@@ -170,7 +170,7 @@ return as:
=== Samples
-You can enter a fixed <<constant-language,Constant>> expression such as
+You can enter a fixed xref:constant-language.adoc[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 <<simple-language,Simple>> language we have
+As this is an extension to the xref:simple-language.adoc[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 <<file-language,File Language>>, <<file-language,Simple>>
-and the <<bean-component,Bean>> language in one combined expression. This
+use the xref:file-language,File Language>>, <<file-language.adoc[Simple]
+and the xref:bean-component.adoc[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 <<file-language,File Language>> directly
-from the <<simple-language,Simple>> language which makes a
+In Camel you can use the xref:file-language.adoc[File Language] directly
+from the xref:simple-language.adoc[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 <<file-language,File Language>> then make
sure you +
+to set a dynamic filename using the xref:file-language.adoc[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/simple-language.adoc
b/docs/user-manual/modules/ROOT/pages/simple-language.adoc
index af1b5ae..52fdee0 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
-<<xpath-language,XPath>>; so it is ideal for testing in camel-core. The
+xref:xpath-language.adoc[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:
-* <<groovy-language,Groovy>>
-* <<spel-language,SpEL>>
-* <<mvel-component,MVEL>>
-* <<ognl-language,OGNL>>
+* xref:groovy-language.adoc[Groovy]
+* xref:spel-language.adoc[SpEL]
+* xref:mvel-component.adoc[MVEL]
+* xref:ognl-language.adoc[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
<<bean-component,Bean>> language.
+|bean:_bean expression_ |Object |Invoking a bean expression using the
xref:bean-component.adoc[Bean] language.
Specifying a method name you must use dot as separator. We also support
-the ?method=methodname syntax that is used by the <<bean-component,Bean>>
+the ?method=methodname syntax that is used by the
xref:bean-component.adoc[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 <<simple-language,Simple>> and <<simple-language,Bean>> language now
+The xref:simple-language,Simple>> and <<simple-language.adoc[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
-<<file-language,File Language>>. *Notice:* The escape character is not
supported, use the
+xref:file-language.adoc[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
-<<bean-component,Bean>> component itself:
+xref:bean-component.adoc[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 <<simple-language,Simple>> language to refer to this enum, to check
+the xref:simple-language.adoc[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 <<simple-language,Simple>>
+You can now provide a result type to the xref:simple-language.adoc[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.
