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 8a0e8c26ca87d224d3459ea16c901c2d81ef9818
Author: nayananga@acerubuntu18.04 <nayanangamuhandi...@gmail.com>
AuthorDate: Sat Jul 13 00:40:36 2019 +0530
mistakes fixed inside camel/docs/user-manual/
---
docs/user-manual/modules/ROOT/pages/bam-example.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/content-filter-eip.adoc | 6 +++---
docs/user-manual/modules/ROOT/pages/data-format.adoc | 4 ++--
docs/user-manual/modules/ROOT/pages/dynamic-router.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/error-handling-in-camel.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/event-message.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/expression.adoc | 2 +-
.../faq/how-do-the-direct-event-seda-and-vm-endpoints-compare.adoc | 4 ++--
.../ROOT/pages/faq/how-does-camel-compare-to-servicemix-eip.adoc | 2 +-
.../modules/ROOT/pages/faq/how-does-camel-work-with-activemq.adoc | 4 ++--
.../modules/ROOT/pages/faq/how-does-the-camel-api-compare-to.adoc | 4 ++--
docs/user-manual/modules/ROOT/pages/file-language.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/languages.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/message-translator.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/rest-dsl.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/simple-language.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/testing.adoc | 4 ++--
docs/user-manual/modules/ROOT/pages/toD-eip.adoc | 2 +-
19 files changed, 26 insertions(+), 26 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/bam-example.adoc
b/docs/user-manual/modules/ROOT/pages/bam-example.adoc
index 21a32fb..568b397 100644
--- a/docs/user-manual/modules/ROOT/pages/bam-example.adoc
+++ b/docs/user-manual/modules/ROOT/pages/bam-example.adoc
@@ -85,7 +85,7 @@ occurs in this example we just send it to the
xref:log-component.adoc[Log]
component to log out an error level message to commons-logging / log4j.
You could change this to use some of the other
Components such as ActiveMQ,
-xref:jms-component,JMS>>, <<jms-component,IRC>>, <<jms-component.adoc[Mail],
+xref:jms-component.adoc[JMS], xref:jms-component.adoc[IRC],
xref:jms-component.adoc[Mail],
xref:xmpp-component.adoc[XMPP] etc.
[[BAMExample-Runningtheexample]]
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 5832f00..7801314 100644
--- a/docs/user-manual/modules/ROOT/pages/content-filter-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/content-filter-eip.adoc
@@ -15,8 +15,8 @@ content from the inbound message.
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: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:ScriptingLanguages-ScriptingLanguages.adoc[Scripting Languages].
=== Using the xref:FluentBuilders-FluentBuilders.adoc[Fluent Builders]
@@ -60,6 +60,6 @@ interested in:
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
+of xref:Endpoint-Endpoints.adoc[Endpoint] and xref: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/data-format.adoc
b/docs/user-manual/modules/ROOT/pages/data-format.adoc
index d232442..05ec6d7 100644
--- a/docs/user-manual/modules/ROOT/pages/data-format.adoc
+++ b/docs/user-manual/modules/ROOT/pages/data-format.adoc
@@ -39,7 +39,7 @@ The following data formats are currently supported:
** xref:csv-dataformat.adoc[CSV]
** xref:edi-dataformat.adoc[EDI]
** xref:flatpack-dataformat.adoc[Flatpack DataFormat]
-** uniVocity DataFormats xref:univocity-csv-dataformat,CSV>> /
<<univocity-tsv-dataformat,TSV>> / <<univocity-fixed-dataformat.adoc[Fixed
Length]
+** uniVocity DataFormats xref:univocity-csv-dataformat.adoc[CSV] /
xref:univocity-tsv-dataformat.adoc[TSV] /
xref:univocity-fixed-dataformat.adoc[Fixed Length]
* Domain specific marshalling
** xref:hl7-dataformat.adoc[HL7 DataFormat]
@@ -81,7 +81,7 @@ And related is the following:
If you receive a message from one of the Camel
xref:component.adoc[Components] such as xref:file-component.adoc[File],
-xref:http-component,HTTP>> or <<jms-component.adoc[JMS] you often want to
unmarshal
+xref:http-component.adoc[HTTP] or xref:jms-component.adoc[JMS] you often want
to unmarshal
the payload into some bean so that you can process it using some
xref:bean-integration.adoc[Bean Integration] or perform
xref:predicate.adoc[Predicate] evaluation and so forth. To do this use
diff --git a/docs/user-manual/modules/ROOT/pages/dynamic-router.adoc
b/docs/user-manual/modules/ROOT/pages/dynamic-router.adoc
index d55ee91..c4c592e 100644
--- a/docs/user-manual/modules/ROOT/pages/dynamic-router.adoc
+++ b/docs/user-manual/modules/ROOT/pages/dynamic-router.adoc
@@ -191,7 +191,7 @@ 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].
+xref:xpath-language.adoc[XPath] or xref:xpath-language.adoc[XQuery].
The method can be invoked in a number of ways as described in the
Bean Integration such as
diff --git a/docs/user-manual/modules/ROOT/pages/error-handling-in-camel.adoc
b/docs/user-manual/modules/ROOT/pages/error-handling-in-camel.adoc
index b81d813..6aff968 100644
--- a/docs/user-manual/modules/ROOT/pages/error-handling-in-camel.adoc
+++ b/docs/user-manual/modules/ROOT/pages/error-handling-in-camel.adoc
@@ -176,7 +176,7 @@ just a ERROR logger.
====
This applies to all kind of xref:component.adoc[Components] in Camel.
The sample above only uses xref:bean-component.adoc[Bean] but it's the same for
-xref:file-component,File>>, <<mail-component.adoc[Mail],
+xref:file-component.adoc[File], xref:mail-component.adoc[Mail],
xref:velocity-component.adoc[Velocity] or whatever component you use.
====
diff --git a/docs/user-manual/modules/ROOT/pages/event-message.adoc
b/docs/user-manual/modules/ROOT/pages/event-message.adoc
index 87d1434..5fa45f0 100644
--- a/docs/user-manual/modules/ROOT/pages/event-message.adoc
+++ b/docs/user-manual/modules/ROOT/pages/event-message.adoc
@@ -12,7 +12,7 @@ implement this pattern using the underlying transport or
protocols.
image:http://www.enterpriseintegrationpatterns.com/img/EventMessageSolution.gif[image]
The default behaviour of many xref:components.adoc[Components] is InOnly
-such as for xref:jms-component,JMS>>, <<jms-component.adoc[File] or
+such as for xref:jms-component.adoc[JMS], xref:jms-component.adoc[File] or
xref:seda-component.adoc[SEDA]
TIP: See the related xref:request-reply.adoc[Request Reply] message.
diff --git a/docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc
b/docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc
index 6334e97..47a2d62 100644
--- a/docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc
@@ -53,6 +53,6 @@ For more details see:
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
+of xref:Endpoint-Endpoints.adoc[Endpoint] and xref: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/expression.adoc
b/docs/user-manual/modules/ROOT/pages/expression.adoc
index c3f68fc..82cbf26 100644
--- a/docs/user-manual/modules/ROOT/pages/expression.adoc
+++ b/docs/user-manual/modules/ROOT/pages/expression.adoc
@@ -112,7 +112,7 @@ wish to use.
|Scripting Languages such as
BeanShell, JavaScript,
-xref:groovy-language,Groovy>>, <<groovy-language,PHP>>,
<<groovy-language.adoc[Python]
+xref:groovy-language.adoc[Groovy], xref:groovy-language.adoc[PHP],
xref:groovy-language.adoc[Python]
and xref:ruby-language.adoc[Ruby]
|http://camel.apache.org/maven/current/camel-script/apidocs/org/apache/camel/builder/script/ScriptBuilder.html[org.apache.camel.builder.script.ScriptBuilder]
|xref:sql-component.adoc[SQL]
|http://camel.apache.org/maven/current/camel-josql/apidocs/org/apache/camel/builder/sql/SqlBuilder.html[org.apache.camel.builder.josql.SqlBuilder]
diff --git
a/docs/user-manual/modules/ROOT/pages/faq/how-do-the-direct-event-seda-and-vm-endpoints-compare.adoc
b/docs/user-manual/modules/ROOT/pages/faq/how-do-the-direct-event-seda-and-vm-endpoints-compare.adoc
index ed868a1..6ba2814 100644
---
a/docs/user-manual/modules/ROOT/pages/faq/how-do-the-direct-event-seda-and-vm-endpoints-compare.adoc
+++
b/docs/user-manual/modules/ROOT/pages/faq/how-do-the-direct-event-seda-and-vm-endpoints-compare.adoc
@@ -1,7 +1,7 @@
[[Howdothedirecteventsedaandvmendpointscompare-Howdothedirecteventsedaandvmendpointscompare]]
=== How do the `direct`, `event`, `seda`, and `vm` endpoints compare?
-* xref:vm-component,VM>> and <<seda-component.adoc[SEDA] endpoints are
basically the
+* xref:vm-component.adoc[VM] and xref:seda-component.adoc[SEDA] endpoints are
basically the
same; they both offer asychronous in memory SEDA queues; they differ in
visibility -- endpoints are visible inside the same JVM or within the same
CamelContext respectively.
@@ -11,4 +11,4 @@ consumer when sending.
application events; so the consumer is invoked the same thread as Spring
notifies events. Event differs in that the payload should be a Spring
`ApplicationEvent` object whereas xref:direct-component.adoc[Direct],
-xref:seda-component,SEDA>> and <<vm-component.adoc[VM] can use any payload.
+xref:seda-component.adoc[SEDA] and xref:vm-component.adoc[VM] can use any
payload.
diff --git
a/docs/user-manual/modules/ROOT/pages/faq/how-does-camel-compare-to-servicemix-eip.adoc
b/docs/user-manual/modules/ROOT/pages/faq/how-does-camel-compare-to-servicemix-eip.adoc
index 87daff8..b4e634d 100644
---
a/docs/user-manual/modules/ROOT/pages/faq/how-does-camel-compare-to-servicemix-eip.adoc
+++
b/docs/user-manual/modules/ROOT/pages/faq/how-does-camel-compare-to-servicemix-eip.adoc
@@ -8,7 +8,7 @@ The main difference with ServiceMix EIP is its integrated into
the
existing ServiceMix XBean XML configuration whereas Camel has more
xref:../enterprise-integration-patterns.adoc[Enterprise Integration
Patterns] and can be used outside of JBI (e.g. just with pure
-xref:jms-component,JMS>> or <<mina-component.adoc[MINA]). Also Camel supports a
+xref:jms-component.adoc[JMS] or xref:mina-component.adoc[MINA]). Also Camel
supports a
xref:../dsl.adoc[Java DSL] or xref:../spring.adoc[XML configuration].
[[HowdoesCamelcomparetoServiceMixEIP-ConvertingfromServiceMixEIPtoCamel]]
diff --git
a/docs/user-manual/modules/ROOT/pages/faq/how-does-camel-work-with-activemq.adoc
b/docs/user-manual/modules/ROOT/pages/faq/how-does-camel-work-with-activemq.adoc
index 9b5fb44..8eab57f 100644
---
a/docs/user-manual/modules/ROOT/pages/faq/how-does-camel-work-with-activemq.adoc
+++
b/docs/user-manual/modules/ROOT/pages/faq/how-does-camel-work-with-activemq.adoc
@@ -9,8 +9,8 @@ Patterns] inside:
* the ActiveMQ JMS client
So Camel can route messages to and from xref:mail-component.adoc[Mail],
-xref:file-component,File>>, <<ftp-component,FTP>>, <<jpa-component.adoc[JPA],
-xref:xmpp-component,XMPP>> other <<jms-component.adoc[JMS] providers and any
of the
+xref:file-component.adoc[File], xref:ftp-component.adoc[FTP],
xref:jpa-component.adoc[JPA],
+xref:xmpp-component.adoc[XMPP] other xref:jms-component.adoc[JMS] providers
and any of the
other Camel xref:../component.adoc[Components] as well as implementating
all of the xref:../enterprise-integration-patterns.adoc[Enterprise
Integration Patterns] such as xref:content-based-router.adoc[Content
diff --git
a/docs/user-manual/modules/ROOT/pages/faq/how-does-the-camel-api-compare-to.adoc
b/docs/user-manual/modules/ROOT/pages/faq/how-does-the-camel-api-compare-to.adoc
index 107972c..8ba4e2e 100644
---
a/docs/user-manual/modules/ROOT/pages/faq/how-does-the-camel-api-compare-to.adoc
+++
b/docs/user-manual/modules/ROOT/pages/faq/how-does-the-camel-api-compare-to.adoc
@@ -6,8 +6,8 @@
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchan
and
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Message.html[Message]
map very closely to JBI in particular but also
-xref:cxf-component,CXF>>, <<http-component,HTTP>>, <<jms-component.adoc[JMS],
-xref:mail-component,Mail>>, <<xmpp-component.adoc[XMPP] and most other
integration
+xref:cxf-component.adoc[CXF], xref:http-component.adoc[HTTP],
xref:jms-component.adoc[JMS],
+xref:mail-component.adoc[Mail], xref:xmpp-component.adoc[XMPP] and most other
integration
abstractions. We want to prevent leaky abstractions, so the Camel API
exposes the underlying APIs so that a xref:../processor.adoc[Processor] can
make use of the underlying abstractions if they make sense.
diff --git a/docs/user-manual/modules/ROOT/pages/file-language.adoc
b/docs/user-manual/modules/ROOT/pages/file-language.adoc
index 41e7914..aa2e77d 100644
--- a/docs/user-manual/modules/ROOT/pages/file-language.adoc
+++ b/docs/user-manual/modules/ROOT/pages/file-language.adoc
@@ -222,7 +222,7 @@ 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]
+use the xref:file-language.adoc[File Language], xref: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.
diff --git a/docs/user-manual/modules/ROOT/pages/languages.adoc
b/docs/user-manual/modules/ROOT/pages/languages.adoc
index 40d7dc8..e1bceeb 100644
--- a/docs/user-manual/modules/ROOT/pages/languages.adoc
+++ b/docs/user-manual/modules/ROOT/pages/languages.adoc
@@ -28,7 +28,7 @@ The following is the list of currently supported languages:
* xref:mvel-language.adoc[Mvel]
* xref:ognl-language.adoc[OGNL]
* xref:ref-language.adoc[Ref Language]
-* xref:exchangeproperty-language,ExchangeProperty>> /
<<property-language.adoc[Property]
+* xref:exchangeproperty-language.adoc[ExchangeProperty] /
xref:property-language.adoc[Property]
* xref:scripting-languages-language.adoc[Scripting Languages] such as:
** xref:beanshell-language.adoc[BeanShell]
** xref:javascript-language.adoc[JavaScript]
diff --git a/docs/user-manual/modules/ROOT/pages/message-translator.adoc
b/docs/user-manual/modules/ROOT/pages/message-translator.adoc
index 0bca190..ce2c31f 100644
--- a/docs/user-manual/modules/ROOT/pages/message-translator.adoc
+++ b/docs/user-manual/modules/ROOT/pages/message-translator.adoc
@@ -54,7 +54,7 @@ invoke a bean
You can also use xref:templating.adoc[Templating] to consume a message
from one destination, transform it with something like
-xref:velocity-component,Velocity>> or <<velocity-component.adoc[XQuery] and
then send
+xref:velocity-component.adoc[Velocity] or xref:velocity-component.adoc[XQuery]
and then send
it on to another destination. For example using InOnly (one way
messaging)
diff --git a/docs/user-manual/modules/ROOT/pages/rest-dsl.adoc
b/docs/user-manual/modules/ROOT/pages/rest-dsl.adoc
index 43be56d..fd2e6b6 100644
--- a/docs/user-manual/modules/ROOT/pages/rest-dsl.adoc
+++ b/docs/user-manual/modules/ROOT/pages/rest-dsl.adoc
@@ -11,7 +11,7 @@ REST style with verbs such as get, post, delete etc.
The Rest DSL is a facade that builds xref:rest-component.adoc[Rest] endpoints
as
consumers for Camel routes. The actual REST transport is leveraged by
using Camel REST components such
-as xref:restlet-component,Restlet>>, <<restlet-component.adoc[Spark-rest], and
+as xref:restlet-component.adoc[Restlet],
xref:restlet-component.adoc[Spark-rest], and
others that has native REST integration.
=== Components supporting Rest DSL
diff --git a/docs/user-manual/modules/ROOT/pages/simple-language.adoc
b/docs/user-manual/modules/ROOT/pages/simple-language.adoc
index 1c5abcd..cc08482 100644
--- a/docs/user-manual/modules/ROOT/pages/simple-language.adoc
+++ b/docs/user-manual/modules/ROOT/pages/simple-language.adoc
@@ -246,7 +246,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 xref:simple-language.adoc[Simple] and xref: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.
diff --git a/docs/user-manual/modules/ROOT/pages/testing.adoc
b/docs/user-manual/modules/ROOT/pages/testing.adoc
index 8d603e0..62613f7 100644
--- a/docs/user-manual/modules/ROOT/pages/testing.adoc
+++ b/docs/user-manual/modules/ROOT/pages/testing.adoc
@@ -237,7 +237,7 @@ correctly
|xref:mock-component.adoc[Mock] |For testing routes and mediation rules using
mocks and allowing assertions to be added to an endpoint
-|xref:test-component,Test>> |Creates a <<test-component.adoc[Mock] endpoint
which
+|xref:test-component.adoc[Test] |Creates a xref:test-component.adoc[Mock]
endpoint which
expects to receive all the message bodies that could be polled from the
given underlying endpoint
|=======================================================================
@@ -266,7 +266,7 @@ a
http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/BlockingQueue.html[`java.util.concurrent.BlockingQueue`]
which is good for testing asynchronous transports
-|xref:stub-component,Stub>> |Works like <<stub-component.adoc[SEDA] but does
not
+|xref:stub-component.adoc[Stub] |Works like xref:stub-component.adoc[SEDA] but
does not
validate the endpoint URI, which makes stubbing much easier.
|=======================================================================
diff --git a/docs/user-manual/modules/ROOT/pages/toD-eip.adoc
b/docs/user-manual/modules/ROOT/pages/toD-eip.adoc
index 399db8a..baf1b62 100644
--- a/docs/user-manual/modules/ROOT/pages/toD-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/toD-eip.adoc
@@ -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 xref:simple-language.adoc[Simple] language and
xref: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
