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 533842ebcbe3d6c4199fc0eefbaf7e2e35803b85
Author: nayananga@acerubuntu18.04 <nayanangamuhandi...@gmail.com>
AuthorDate: Sat Jul 13 00:47:18 2019 +0530
mistakes fixed inside camel/components
---
components/camel-dataset/src/main/docs/dataset-component.adoc | 2 +-
components/camel-dataset/src/main/docs/dataset-test-component.adoc | 2 +-
components/camel-file/src/main/docs/file-component.adoc | 4 ++--
components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc | 4 ++--
components/camel-jetty/src/main/docs/jetty-component.adoc | 2 +-
components/camel-language/src/main/docs/language-component.adoc | 2 +-
components/camel-mock/src/main/docs/mock-component.adoc | 4 ++--
components/camel-mybatis/src/main/docs/mybatis-component.adoc | 2 +-
components/camel-seda/src/main/docs/seda-component.adoc | 2 +-
components/camel-spring/src/main/docs/spring.adoc | 2 +-
components/camel-stub/src/main/docs/stub-component.adoc | 4 ++--
components/camel-xpath/src/main/docs/xpath-language.adoc | 2 +-
12 files changed, 16 insertions(+), 16 deletions(-)
diff --git a/components/camel-dataset/src/main/docs/dataset-component.adoc
b/components/camel-dataset/src/main/docs/dataset-component.adoc
index 12a364c..3469c30 100644
--- a/components/camel-dataset/src/main/docs/dataset-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-component.adoc
@@ -4,7 +4,7 @@
*Available as of Camel version 1.3*
Testing of distributed and asynchronous processing is
-notoriously difficult. The xref:mock-component,Mock>>,
<<mock-component.adoc[Test]
+notoriously difficult. The xref:mock-component.adoc[Mock],
xref:mock-component.adoc[Test]
and xref:dataset-component.adoc[DataSet] endpoints work great with the
Camel Testing Framework to simplify your unit and
integration testing using
diff --git a/components/camel-dataset/src/main/docs/dataset-test-component.adoc
b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
index 94915e5..1d88d7ca 100644
--- a/components/camel-dataset/src/main/docs/dataset-test-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
@@ -4,7 +4,7 @@
*Available as of Camel version 1.3*
Testing of distributed and asynchronous processing is
-notoriously difficult. The xref:mock-component,Mock>>,
<<mock-component.adoc[Test]
+notoriously difficult. The xref:mock-component.adoc[Mock],
xref:mock-component.adoc[Test]
and xref:dataset-component.adoc[DataSet] endpoints work great with the
Camel Testing Framework to simplify your unit and
integration testing using
diff --git a/components/camel-file/src/main/docs/file-component.adoc
b/components/camel-file/src/main/docs/file-component.adoc
index 48a677e..0878732e 100644
--- a/components/camel-file/src/main/docs/file-component.adoc
+++ b/components/camel-file/src/main/docs/file-component.adoc
@@ -237,7 +237,7 @@ bean completes, and thus the route is completed, the file
consumer will
perform the move operation and move the file to the `.done` sub-folder.
The *move* and the *preMove* options are considered as a directory name
-(though if you use an expression such as xref:file-language,File Language>>,
or <<simple-language.adoc[Simple] then the result of the expression
+(though if you use an expression such as xref:file-language.adoc[File
Language], or xref:simple-language.adoc[Simple] then the result of the
expression
evaluation is the file name to be used - eg if you set
[source]
@@ -323,7 +323,7 @@ The following headers are supported by this component:
|`CamelFileName` |Specifies the name of the file to write (relative to the
endpoint
directory). This name can be a `String`; a `String` with a
-xref:file-language,File Language>> or <<simple-language.adoc[Simple]
+xref:file-language.adoc[File Language] or xref:simple-language.adoc[Simple]
expression; or an Expression object. If it's
`null` then Camel will auto-generate a filename based on the message
unique ID.
diff --git a/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
b/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
index bb61d2e..2132c9f 100644
--- a/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
+++ b/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
@@ -232,7 +232,7 @@ In this Spring DSL we have defined to use `iso-8859-1` as
the encoding:
*Available as of Camel 2.11*
-When marshalling using xref:jaxb-dataformat,JAXB>> or
<<jaxb-dataformat.adoc[SOAP] then
+When marshalling using xref:jaxb-dataformat.adoc[JAXB] or
xref:jaxb-dataformat.adoc[SOAP] then
the JAXB implementation will automatic assign namespace prefixes, such
as ns2, ns3, ns4 etc. To control this mapping, Camel allows you to refer
to a map which contains the desired mapping.
@@ -254,7 +254,7 @@ namespace "http://www.mycompany.com/foo/2"; is not using any
prefix.
</util:map>
-----------------------------------------------------------------------
-To use this in xref:jaxb-dataformat,JAXB>> or <<jaxb-dataformat.adoc[SOAP] you
refer to
+To use this in xref:jaxb-dataformat.adoc[JAXB] or
xref:jaxb-dataformat.adoc[SOAP] you refer to
this map, using the `namespacePrefixRef` attribute as shown below. Then
Camel will lookup in the Registry a `java.util.Map`
with the id "myMap", which was what we defined above.
diff --git a/components/camel-jetty/src/main/docs/jetty-component.adoc
b/components/camel-jetty/src/main/docs/jetty-component.adoc
index cdde045..e9e7cc5 100644
--- a/components/camel-jetty/src/main/docs/jetty-component.adoc
+++ b/components/camel-jetty/src/main/docs/jetty-component.adoc
@@ -283,7 +283,7 @@ Jetty component will copy the HTTP request parameter, `one`
to the
exchange's `in.header`. We can then use the `simple` language to route
exchanges that contain this header to a specific endpoint and all others
to another. If we used a language more powerful than
-xref:simple-language,Simple>> (such as <<el-language.adoc[EL] or
+xref:simple-language.adoc[Simple] (such as xref:el-language.adoc[EL] or
xref:ognl-language.adoc[OGNL]) we could also test for the parameter value and
do
routing based on the header value as well.
diff --git a/components/camel-language/src/main/docs/language-component.adoc
b/components/camel-language/src/main/docs/language-component.adoc
index 68b2c1a..81161fa 100644
--- a/components/camel-language/src/main/docs/language-component.adoc
+++ b/components/camel-language/src/main/docs/language-component.adoc
@@ -15,7 +15,7 @@ script is dynamic defined as well.
This component is provided out of the box in `camel-core` and hence no
additional JARs is needed. You only have to include additional Camel
components if the language of choice mandates it, such as using
-xref:groovy-language,Groovy>> or <<groovy-language.adoc[JavaScript] languages.
+xref:groovy-language.adoc[Groovy] or xref:groovy-language.adoc[JavaScript]
languages.
=== URI format
diff --git a/components/camel-mock/src/main/docs/mock-component.adoc
b/components/camel-mock/src/main/docs/mock-component.adoc
index 2e05129..28e0749 100644
--- a/components/camel-mock/src/main/docs/mock-component.adoc
+++ b/components/camel-mock/src/main/docs/mock-component.adoc
@@ -4,7 +4,7 @@
*Available as of Camel version 1.0*
Testing of distributed and asynchronous processing is
-notoriously difficult. The xref:mock-component,Mock>>,
<<mock-component.adoc[Test]
+notoriously difficult. The xref:mock-component.adoc[Mock],
xref:mock-component.adoc[Test]
and xref:dataset-component.adoc[DataSet] endpoints work great with the
Camel Testing Framework to simplify your unit and
integration testing using
@@ -28,7 +28,7 @@ Expression to create an order testing function,
* Messages arrive match some kind of Predicate such
as that specific headers have certain values, or that parts of the
messages match some predicate, such as by evaluating an
-xref:xpath-language,XPath>> or <<xpath-language.adoc[XQuery]
+xref:xpath-language.adoc[XPath] or xref:xpath-language.adoc[XQuery]
Expression.
[NOTE]
diff --git a/components/camel-mybatis/src/main/docs/mybatis-component.adoc
b/components/camel-mybatis/src/main/docs/mybatis-component.adoc
index 30e4a69..00bdaf1 100644
--- a/components/camel-mybatis/src/main/docs/mybatis-component.adoc
+++ b/components/camel-mybatis/src/main/docs/mybatis-component.adoc
@@ -321,7 +321,7 @@ See "ScheduledPollConsumer Options"
on Polling Consumer for more options.
Alternatively you can use another mechanism for triggering the scheduled
-polls, such as the xref:timer-component,Timer>> or
<<timer-component.adoc[Quartz]
+polls, such as the xref:timer-component.adoc[Timer] or
xref:timer-component.adoc[Quartz]
components. In the sample below we poll the database, every 30 seconds
using the xref:timer-component.adoc[Timer] component and send the data to the
JMS
queue:
diff --git a/components/camel-seda/src/main/docs/seda-component.adoc
b/components/camel-seda/src/main/docs/seda-component.adoc
index 2f52fe1..53d5812 100644
--- a/components/camel-seda/src/main/docs/seda-component.adoc
+++ b/components/camel-seda/src/main/docs/seda-component.adoc
@@ -17,7 +17,7 @@ applications), see the xref:vm-component.adoc[VM] component.
This component does not implement any kind of persistence or recovery,
if the VM terminates while messages are yet to be processed. If you need
persistence, reliability or distributed SEDA, try using either
-xref:jms-component,JMS>> or <<jms-component.adoc[ActiveMQ].
+xref:jms-component.adoc[JMS] or xref:jms-component.adoc[ActiveMQ].
TIP:*Synchronous*
The xref:direct-component.adoc[Direct] component provides synchronous
invocation
diff --git a/components/camel-spring/src/main/docs/spring.adoc
b/components/camel-spring/src/main/docs/spring.adoc
index 7476461..f83baf7 100644
--- a/components/camel-spring/src/main/docs/spring.adoc
+++ b/components/camel-spring/src/main/docs/spring.adoc
@@ -5,7 +5,7 @@ Apache Camel is designed to work nicely with the
http://www.springframework.org/[Spring Framework] in a number of ways.
* Camel uses Spring Transactions as the default transaction handling in
-components like xref:jms-component,JMS>> and <<jms-component.adoc[JPA]
+components like xref:jms-component.adoc[JMS] and xref:jms-component.adoc[JPA]
* Camel works with Spring 2 XML processing with the
Xml Configuration
* Camel Spring XML Schema's is defined at xref:xml-reference.adoc[Xml
diff --git a/components/camel-stub/src/main/docs/stub-component.adoc
b/components/camel-stub/src/main/docs/stub-component.adoc
index c16971c..5a7147d 100644
--- a/components/camel-stub/src/main/docs/stub-component.adoc
+++ b/components/camel-stub/src/main/docs/stub-component.adoc
@@ -6,11 +6,11 @@
The Stub component provides a simple way to stub out any physical
endpoints while in development or testing, allowing you for example to
run a route without needing to actually connect to a specific
-xref:mail-component,SMTP>> or <<mail-component.adoc[Http] endpoint. Just add
*stub:*
+xref:mail-component.adoc[SMTP] or xref:mail-component.adoc[Http] endpoint.
Just add *stub:*
in front of any endpoint URI to stub out the endpoint.
Internally the Stub component creates xref:vm-component.adoc[VM] endpoints. The
-main difference between xref:stub-component,Stub>> and
<<stub-component.adoc[VM] is
+main difference between xref:stub-component.adoc[Stub] and
xref:stub-component.adoc[VM] is
that xref:vm-component.adoc[VM] will validate the URI and parameters you give
it,
so putting vm: in front of a typical URI with query arguments will
usually fail. Stub won't though, as it basically ignores all query
diff --git a/components/camel-xpath/src/main/docs/xpath-language.adoc
b/components/camel-xpath/src/main/docs/xpath-language.adoc
index 7fb324b..5c673e3 100644
--- a/components/camel-xpath/src/main/docs/xpath-language.adoc
+++ b/components/camel-xpath/src/main/docs/xpath-language.adoc
@@ -16,7 +16,7 @@ Recipient List.
If the message body is stream based, which means the input it receives
is submitted to Camel as a stream. That means you will only be able to
read the content of the stream *once*. So often when you use
-xref:xpath-language,XPath>> as <<xpath-language.adoc[Message Filter] or
+xref:xpath-language.adoc[XPath] as xref:xpath-language.adoc[Message Filter] or
Content Based Router then you need to
access the data multiple times, and you should use
Stream Caching or convert the message body to
