You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2017/01/11 18:27:07 UTC
[02/14] camel git commit: Use single line header for adoc files
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-twitter/src/main/docs/twitter-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-twitter/src/main/docs/twitter-component.adoc b/components/camel-twitter/src/main/docs/twitter-component.adoc
index 246f13d..72196d3 100644
--- a/components/camel-twitter/src/main/docs/twitter-component.adoc
+++ b/components/camel-twitter/src/main/docs/twitter-component.adoc
@@ -1,4 +1,4 @@
-# Twitter Component
+## Twitter Component
ifdef::env-github[]
:caution-caption: :boom:
:important-caption: :exclamation:
@@ -8,9 +8,7 @@ ifdef::env-github[]
endif::[]
[[ConfluenceContent]]
-[[Twitter-Twitter]]
-Twitter
-~~~~~~~
+### Twitter
*Available as of Camel 2.10*
@@ -38,18 +36,14 @@ for this component:
</dependency>
----
-[[Twitter-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source]
----
twitter://endpoint[?options]
----
-[[Twitter-TwitterComponent]]
-Twitter component
-^^^^^^^^^^^^^^^^^
+### Twitter component
The twitter component can be configured with the Twitter account
settings which is mandatory to configure before using.
@@ -85,9 +79,7 @@ The Twitter component supports 8 options which are listed below.
You can also configure these options directly in the endpoint.
-[[Twitter-ConsumerEndpoints]]
-Consumer endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer endpoints
Rather than the endpoints returning a List through one single route
exchange, camel-twitter creates one route exchange per returned object.
@@ -130,9 +122,7 @@ polling* |[line-through]*twitter4j.Status* |[line-through]*@deprecated.
Removed from Camel 2.11 onwards.*
|=======================================================================
-[[Twitter-ProducerEndpoints]]
-Producer endpoints
-^^^^^^^^^^^^^^^^^^
+### Producer endpoints
[width="100%",cols="20%,80%",options="header",]
|==============================
@@ -142,9 +132,7 @@ Producer endpoints
|timeline/user |String
|==============================
-[[Twitter-URIOptions]]
-URI options
-^^^^^^^^^^^
+### URI options
@@ -212,9 +200,7 @@ The Twitter component supports 43 endpoint options which are listed below:
-[[Twitter-Messageheaders]]
-Message headers
-^^^^^^^^^^^^^^^
+### Message headers
[width="100%",cols="20%,80%",options="header",]
|=======================================================================
@@ -234,15 +220,11 @@ the option of `numberOfPages` which sets how many pages we want to
twitter returns.
|=======================================================================
-[[Twitter-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
All message bodies utilize objects provided by the Twitter4J API.
-[[Twitter-Usecases]]
-Use cases
-^^^^^^^^^
+### Use cases
NOTE: *API Rate Limits:* Twitter REST APIs encapsulated by http://twitter4j.org/[Twitter4J] are
subjected to https://dev.twitter.com/rest/public/rate-limiting[API Rate
@@ -251,9 +233,7 @@ https://dev.twitter.com/rest/public/rate-limits[API Rate Limits]
documentation. Note that endpoints/resources not listed in that page are
default to 15 requests per allotted user per window.
-[[Twitter-TocreateastatusupdatewithinyourTwitterprofile,sendthisproduceraStringbody]]
-To create a status update within your Twitter profile, send this producer a String body:
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### To create a status update within your Twitter profile, send this producer a String body:
[source,java]
----
@@ -261,9 +241,7 @@ from("direct:foo")
.to("twitter://timeline/user?consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]);
----
-[[Twitter-Topoll,every60sec.,allstatusesonyourhometimeline]]
-To poll, every 60 sec., all statuses on your home timeline:
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### To poll, every 60 sec., all statuses on your home timeline:
[source,java]
----
@@ -271,9 +249,7 @@ from("twitter://timeline/home?type=polling&delay=60&consumerKey=[s]&consumerSecr
.to("bean:blah");
----
-[[Twitter-TosearchforallstatuseswiththekeywordCamel]]
-To search for all statuses with the keyword 'camel':
-++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### To search for all statuses with the keyword 'camel':
[source,java]
----
@@ -281,9 +257,7 @@ from("twitter://search?type=direct&keywords=camel&consumerKey=[s]&consumerSecret
.to("bean:blah");
----
-[[Twitter-Searchingusingaproducerwithstatickeywords]]
-Searching using a producer with static keywords:
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Searching using a producer with static keywords:
[source,java]
----
@@ -291,9 +265,7 @@ from("direct:foo")
.to("twitter://search?keywords=camel&consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]");
----
-[[Twitter-Searchingusingaproducerwithdynamickeywordsfromheader]]
-Searching using a producer with dynamic keywords from header:
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Searching using a producer with dynamic keywords from header:
In the `bar` header we have the keywords we want to search, so we can
assign this value to the `CamelTwitterKeywords` header:
@@ -305,20 +277,16 @@ from("direct:foo")
.to("twitter://search?consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]");
----
-[[Twitter-Example]]
-Example
-^^^^^^^
+### Example
See also the link:twitter-websocket-example.html[Twitter Websocket
Example].
-[[Twitter-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
* link:endpoint.html[Endpoint]
* link:getting-started.html[Getting Started]
-* link:twitter-websocket-example.html[Twitter Websocket Example]
+* link:twitter-websocket-example.html[Twitter Websocket Example]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-undertow/src/main/docs/undertow-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-undertow/src/main/docs/undertow-component.adoc b/components/camel-undertow/src/main/docs/undertow-component.adoc
index cc4143d..66373a9 100644
--- a/components/camel-undertow/src/main/docs/undertow-component.adoc
+++ b/components/camel-undertow/src/main/docs/undertow-component.adoc
@@ -1,4 +1,4 @@
-# Undertow Component
+## Undertow Component
*Available as of Camel 2.16*
@@ -21,9 +21,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Undertow-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------------------------------
@@ -33,9 +31,7 @@ undertow:http://hostname[:port][/resourceUri][?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Undertow-Options]]
-Options
-^^^^^^^
+### Options
@@ -93,9 +89,7 @@ The Undertow component supports 18 endpoint options which are listed below:
-[[Undertow-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Camel uses the same message headers as the link:http.html[HTTP]
component.
@@ -108,9 +102,7 @@ example, given a client request with the URL,
`http://myserver/myserver?orderid=123`, the exchange will contain a
header named `orderid` with the value 123.
-[[Undertow-ProducerExample]]
-Producer Example
-^^^^^^^^^^^^^^^^
+### Producer Example
The following is a basic example of how to send an HTTP request to an
existing HTTP endpoint.
@@ -132,9 +124,7 @@ or in Spring XML
<route>
----------------------------------------------
-[[Undertow-ConsumerExample]]
-Consumer Example
-^^^^^^^^^^^^^^^^
+### Consumer Example
In this sample we define a route that exposes a HTTP service at
`http://localhost:8080/myapp/myservice`:
@@ -167,9 +157,7 @@ Servlet, you should instead refer to the
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=46339[Servlet
Transport].
-[[Undertow-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -177,5 +165,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:jetty.html[Jetty]
-* link:http.html[HTTP]
-
+* link:http.html[HTTP]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc b/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
index 923d509..1bf0e75 100644
--- a/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
+++ b/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
@@ -1,4 +1,4 @@
-# uniVocity CSV DataFormat
+## uniVocity CSV DataFormat
*Available as of Camel 2.15.0*
@@ -28,9 +28,7 @@ download page for the latest versions]).
</dependency>
----------------------------------------------------
-[[uniVocity-parsersformats-Options]]
-Options
-^^^^^^^
+### Options
Most configuration options of the uniVocity-parsers are available in the
data formats. If you want more information about a particular option,
@@ -41,9 +39,7 @@ page].
The 3 data formats share common options and have dedicated ones, this
section presents them all.
-[[uniVocity-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
@@ -79,9 +75,7 @@ The uniVocity CSV dataformat supports 18 options which are listed below.
-[[uniVocity-parsersformats-Marshallingusages]]
-Marshalling usages
-^^^^^^^^^^^^^^^^^^
+### Marshalling usages
The marshalling accepts either:
@@ -90,9 +84,7 @@ The marshalling accepts either:
Any other body will throws an exception.
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintoCSVformat]]
-Usage example: marshalling a Map into CSV format
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into CSV format
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -105,9 +97,7 @@ Usage example: marshalling a Map into CSV format
</route>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintofixed-widthformat]]
-Usage example: marshalling a Map into fixed-width format
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into fixed-width format
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -124,9 +114,7 @@ Usage example: marshalling a Map into fixed-width format
</route>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintoTSVformat]]
-Usage example: marshalling a Map into TSV format
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into TSV format
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -139,9 +127,7 @@ Usage example: marshalling a Map into TSV format
</route>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[uniVocity-parsersformats-Unmarshallingusages]]
-Unmarshalling usages
-^^^^^^^^^^^^^^^^^^^^
+### Unmarshalling usages
The unmarshalling uses an�`InputStream` in order to read the data.
@@ -156,9 +142,7 @@ All the rows can either:
* be collected at once into a list�(`lazyLoad`�option�with�`false`);
* be read on the fly using an iterator�(`lazyLoad`�option�with�`true`).
-[[uniVocity-parsersformats-UsageexampleunmarshallingaCSVformatintomapswithautomaticheaders]]
-Usage example: unmarshalling a CSV format into maps with automatic headers
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: unmarshalling a CSV format into maps with automatic headers
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -171,9 +155,7 @@ Usage example: unmarshalling a CSV format into maps with automatic headers
</route>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[uniVocity-parsersformats-Usageexampleunmarshallingafixed-widthformatintolists]]
-Usage example: unmarshalling a fixed-width format into lists
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: unmarshalling a fixed-width format into lists
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -188,5 +170,4 @@ Usage example: unmarshalling a fixed-width format into lists
</unmarshal>
<to uri="mock:result"/>
</route>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc b/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
index f834d92..86abe57 100644
--- a/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
+++ b/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
@@ -1,4 +1,4 @@
-# uniVocity Fixed Length DataFormat
+## uniVocity Fixed Length DataFormat
*Available as of Camel 2.15.0*
@@ -28,9 +28,7 @@ download page for the latest versions]).
</dependency>
----------------------------------------------------
-[[uniVocity-parsersformats-Options]]
-Options
-^^^^^^^
+### Options
Most configuration options of the uniVocity-parsers are available in the
data formats. If you want more information about a particular option,
@@ -41,9 +39,7 @@ page].
The 3 data formats share common options and have dedicated ones, this
section presents them all.
-[[uniVocity-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
@@ -78,9 +74,7 @@ The uniVocity Fixed Length dataformat supports 17 options which are listed below
-[[uniVocity-parsersformats-Marshallingusages]]
-Marshalling usages
-^^^^^^^^^^^^^^^^^^
+### Marshalling usages
The marshalling accepts either:
@@ -89,9 +83,7 @@ The marshalling accepts either:
Any other body will throws an exception.
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintoCSVformat]]
-Usage example: marshalling a Map into CSV format
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into CSV format
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -104,9 +96,7 @@ Usage example: marshalling a Map into CSV format
</route>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintofixed-widthformat]]
-Usage example: marshalling a Map into fixed-width format
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into fixed-width format
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -123,9 +113,7 @@ Usage example: marshalling a Map into fixed-width format
</route>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintoTSVformat]]
-Usage example: marshalling a Map into TSV format
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into TSV format
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -138,9 +126,7 @@ Usage example: marshalling a Map into TSV format
</route>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[uniVocity-parsersformats-Unmarshallingusages]]
-Unmarshalling usages
-^^^^^^^^^^^^^^^^^^^^
+### Unmarshalling usages
The unmarshalling uses an�`InputStream` in order to read the data.
@@ -155,9 +141,7 @@ All the rows can either:
* be collected at once into a list�(`lazyLoad`�option�with�`false`);
* be read on the fly using an iterator�(`lazyLoad`�option�with�`true`).
-[[uniVocity-parsersformats-UsageexampleunmarshallingaCSVformatintomapswithautomaticheaders]]
-Usage example: unmarshalling a CSV format into maps with automatic headers
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: unmarshalling a CSV format into maps with automatic headers
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -170,9 +154,7 @@ Usage example: unmarshalling a CSV format into maps with automatic headers
</route>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[uniVocity-parsersformats-Usageexampleunmarshallingafixed-widthformatintolists]]
-Usage example: unmarshalling a fixed-width format into lists
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: unmarshalling a fixed-width format into lists
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -187,5 +169,4 @@ Usage example: unmarshalling a fixed-width format into lists
</unmarshal>
<to uri="mock:result"/>
</route>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc b/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
index 9a21af3..c7e812f 100644
--- a/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
+++ b/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
@@ -1,4 +1,4 @@
-# uniVocity TSV DataFormat
+## uniVocity TSV DataFormat
*Available as of Camel 2.15.0*
@@ -28,9 +28,7 @@ download page for the latest versions]).
</dependency>
----------------------------------------------------
-[[uniVocity-parsersformats-Options]]
-Options
-^^^^^^^
+### Options
Most configuration options of the uniVocity-parsers are available in the
data formats. If you want more information about a particular option,
@@ -41,9 +39,7 @@ page].
The 3 data formats share common options and have dedicated ones, this
section presents them all.
-[[uniVocity-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
@@ -76,9 +72,7 @@ The uniVocity TSV dataformat supports 15 options which are listed below.
-[[uniVocity-parsersformats-Marshallingusages]]
-Marshalling usages
-^^^^^^^^^^^^^^^^^^
+### Marshalling usages
The marshalling accepts either:
@@ -87,9 +81,7 @@ The marshalling accepts either:
Any other body will throws an exception.
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintoCSVformat]]
-Usage example: marshalling a Map into CSV format
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into CSV format
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -102,9 +94,7 @@ Usage example: marshalling a Map into CSV format
</route>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintofixed-widthformat]]
-Usage example: marshalling a Map into fixed-width format
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into fixed-width format
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -121,9 +111,7 @@ Usage example: marshalling a Map into fixed-width format
</route>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintoTSVformat]]
-Usage example: marshalling a Map into TSV format
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into TSV format
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -136,9 +124,7 @@ Usage example: marshalling a Map into TSV format
</route>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[uniVocity-parsersformats-Unmarshallingusages]]
-Unmarshalling usages
-^^^^^^^^^^^^^^^^^^^^
+### Unmarshalling usages
The unmarshalling uses an�`InputStream` in order to read the data.
@@ -153,9 +139,7 @@ All the rows can either:
* be collected at once into a list�(`lazyLoad`�option�with�`false`);
* be read on the fly using an iterator�(`lazyLoad`�option�with�`true`).
-[[uniVocity-parsersformats-UsageexampleunmarshallingaCSVformatintomapswithautomaticheaders]]
-Usage example: unmarshalling a CSV format into maps with automatic headers
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: unmarshalling a CSV format into maps with automatic headers
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -168,9 +152,7 @@ Usage example: unmarshalling a CSV format into maps with automatic headers
</route>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[uniVocity-parsersformats-Usageexampleunmarshallingafixed-widthformatintolists]]
-Usage example: unmarshalling a fixed-width format into lists
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: unmarshalling a fixed-width format into lists
[source,xml]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -185,5 +167,4 @@ Usage example: unmarshalling a fixed-width format into lists
</unmarshal>
<to uri="mock:result"/>
</route>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-velocity/src/main/docs/velocity-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-velocity/src/main/docs/velocity-component.adoc b/components/camel-velocity/src/main/docs/velocity-component.adoc
index 83b5b0b..ea9026e 100644
--- a/components/camel-velocity/src/main/docs/velocity-component.adoc
+++ b/components/camel-velocity/src/main/docs/velocity-component.adoc
@@ -1,4 +1,4 @@
-# Velocity Component
+## Velocity Component
The *velocity:* component allows you to process a message using an
http://velocity.apache.org/[Apache Velocity] template. This can be ideal
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Velocity-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------
@@ -34,9 +32,7 @@ file://folder/myfile.vm[file://folder/myfile.vm]).
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Velocity-Options]]
-Options
-^^^^^^^
+### Options
@@ -75,9 +71,7 @@ The Velocity component supports 6 endpoint options which are listed below:
// endpoint options: END
-[[Velocity-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
The velocity component sets a couple headers on the message (you can't
set these yourself and from Camel 2.1 velocity component will not set
@@ -111,9 +105,7 @@ $in.setHeader("fruit", "Apple")
The `fruit` header is now accessible from the `message.out.headers`.
-[[Velocity-VelocityContext]]
-Velocity Context
-^^^^^^^^^^^^^^^^
+### Velocity Context
Camel will provide exchange information in the Velocity context (just a
`Map`). The `Exchange` is transfered as:
@@ -152,9 +144,7 @@ setting the message header *CamelVelocityContext�*just like this
�
-[[Velocity-Hotreloading]]
-Hot reloading
-^^^^^^^^^^^^^
+### Hot reloading
The Velocity template resource is, by default, hot reloadable for both
file and classpath resources (expanded jar). If you set
@@ -162,9 +152,7 @@ file and classpath resources (expanded jar). If you set
hot reloading is not possible. This scenario can be used in production,
when the resource never changes.
-[[Velocity-Dynamictemplates]]
-Dynamic templates
-^^^^^^^^^^^^^^^^^
+### Dynamic templates
*Available as of Camel 2.1* +
Camel provides two headers by which you can define a different resource
@@ -182,9 +170,7 @@ endpoint configured.
|CamelVelocityTemplate |String |*Camel 2.1:* The template to use instead of the endpoint configured.
|=======================================================================
-[[Velocity-Samples]]
-Samples
-^^^^^^^
+### Samples
For example you could use something like
@@ -246,9 +232,7 @@ from("direct:in").
to("velocity:dummy");
---------------------------------------------------------------------------------------------------------------
-[[Velocity-TheEmailSample]]
-The Email Sample
-^^^^^^^^^^^^^^^^
+### The Email Sample
In this sample we want to use Velocity templating for an order
confirmation email. The email template is laid out in Velocity as:
@@ -265,12 +249,9 @@ ${body}
And the java code:
-[[Velocity-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
* link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-vertx/src/main/docs/vertx-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-vertx/src/main/docs/vertx-component.adoc b/components/camel-vertx/src/main/docs/vertx-component.adoc
index faba01d..2dd007d 100644
--- a/components/camel-vertx/src/main/docs/vertx-component.adoc
+++ b/components/camel-vertx/src/main/docs/vertx-component.adoc
@@ -1,4 +1,4 @@
-# Vert.x Component
+## Vert.x Component
*Available as of Camel 2.12*
@@ -24,18 +24,14 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Vertx-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------
vertx:channelName[?options]
---------------------------
-[[Vertx-Options]]
-Options
-^^^^^^^
+### Options
@@ -86,9 +82,7 @@ point when sending to a vertx endpoint.
You can append query options to the URI in the following format, ?option=value&option=value&...
-----------------------------------------------------------------------------------------------
-[[Vertx-ConnectingtotheexistingVert.xinstance]]
-Connecting to the existing Vert.x instance
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Connecting to the existing Vert.x instance
If you would like to connect to the Vert.x instance already existing in
your JVM, you can set the instance on the component level:
@@ -101,12 +95,9 @@ vertxComponent.setVertx(vertx);
camelContext.addComponent("vertx", vertxComponent);
-----------------------------------------------------
-[[Vertx-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
* link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-weather/src/main/docs/weather-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-weather/src/main/docs/weather-component.adoc b/components/camel-weather/src/main/docs/weather-component.adoc
index f4f1915..f0de088 100644
--- a/components/camel-weather/src/main/docs/weather-component.adoc
+++ b/components/camel-weather/src/main/docs/weather-component.adoc
@@ -1,4 +1,4 @@
-# Weather Component
+## Weather Component
*Available as of Camel 2.12*
@@ -24,26 +24,20 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Weather-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------
weather://<unused name>[?options]
---------------------------------
-[[Weather-REMARK]]
-REMARK
-^^^^^^
+### REMARK
Since the 9th of October, an Api Key is required to access the
openweather service. This key is passed as parameter to the URI
definition of the weather endpoint using the appid param�!
-[[Weather-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -111,16 +105,12 @@ The Weather component supports 44 endpoint options which are listed below:
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Weather-Exchangedataformat]]
-Exchange data format
-^^^^^^^^^^^^^^^^^^^^
+### Exchange data format
Camel will deliver the body as a json formatted java.lang.String (see
the `mode` option above).
-[[Weather-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -132,9 +122,7 @@ Message Headers
location from this header instead.
|=======================================================================
-[[Weather-Samples]]
-Samples
-^^^^^^^
+### Samples
In this sample we find the 7 day weather forecast for Madrid, Spain:
@@ -172,4 +160,4 @@ And to get the weather at the current location, then:
[source,java]
--------------------------------------------------------------------------------------------------------------------------------
String json = template.requestBodyAndHeader("direct:start", "", "CamelWeatherLocation", "current&appid=APIKEY", String.class);
---------------------------------------------------------------------------------------------------------------------------------
+--------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-websocket/src/main/docs/websocket-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-websocket/src/main/docs/websocket-component.adoc b/components/camel-websocket/src/main/docs/websocket-component.adoc
index aaf0c24..e6943df 100644
--- a/components/camel-websocket/src/main/docs/websocket-component.adoc
+++ b/components/camel-websocket/src/main/docs/websocket-component.adoc
@@ -1,4 +1,4 @@
-# Jetty Websocket Component
+## Jetty Websocket Component
*Available as of Camel 2.10*
@@ -14,9 +14,7 @@ protocol, the SSLContextParameters must be defined.
Camel 2.18 uses Jetty 9
-[[Websocket-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------------------
@@ -26,9 +24,7 @@ websocket://hostname[:port][/resourceUri][?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Websocket-Options]]
-Websocket Options
-^^^^^^^^^^^^^^^^^
+### Websocket Options
@@ -105,9 +101,7 @@ The Jetty Websocket component supports 21 endpoint options which are listed belo
�
-[[Websocket-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
The websocket component uses 2 headers to indicate to either send
messages back to a single/current client, or to all clients.
@@ -121,9 +115,7 @@ use the `sendToAll` option on the endpoint instead of using this header.
|`WebsocketConstants.CONNECTION_KEY` |Sends the message to the client with the given connection key.
|=======================================================================
-[[Websocket-Usage]]
-Usage
-^^^^^
+### Usage
In this example we let Camel exposes a websocket server which clients
can communicate with. The websocket server uses the default host and
@@ -150,13 +142,9 @@ from("activemq:topic:newsTopic")
.to("websocket://localhost:8443/newsTopic?sendToAll=true&staticResources=classpath:webapp");
-----------------------------------------------------------------------------------------------
-[[Websocket-SettingupSSLforWebSocketComponent]]
-Setting up SSL for WebSocket Component
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting up SSL for WebSocket Component
-[[Websocket-UsingtheJSSEConfigurationUtility]]
-Using the JSSE Configuration Utility
-++++++++++++++++++++++++++++++++++++
+#### Using the JSSE Configuration Utility
As of Camel 2.10, the WebSocket component supports SSL/TLS configuration
through the link:camel-configuration-utilities.html[Camel JSSE
@@ -234,9 +222,7 @@ Java DSL based configuration of endpoint
...
----------------------------------------------------------------------------------------------------------
-[[Websocket-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -247,5 +233,4 @@ See Also
* link:jetty.html[Jetty]
* link:twitter-websocket-example.html[Twitter Websocket Example]
demonstrates how to poll a constant feed of twitter searches and publish
-results in real time using web socket to a web page.
-
+results in real time using web socket to a web page.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmlbeans/src/main/docs/xmlBeans-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmlbeans/src/main/docs/xmlBeans-dataformat.adoc b/components/camel-xmlbeans/src/main/docs/xmlBeans-dataformat.adoc
index ba593b6..b0a4a2e 100644
--- a/components/camel-xmlbeans/src/main/docs/xmlBeans-dataformat.adoc
+++ b/components/camel-xmlbeans/src/main/docs/xmlBeans-dataformat.adoc
@@ -1,4 +1,4 @@
-# XML Beans DataFormat
+## XML Beans DataFormat
XmlBeans is a link:data-format.html[Data Format] which uses the
http://xmlbeans.apache.org/[XmlBeans library] to unmarshal an XML
@@ -12,9 +12,7 @@ from("activemq:My.Queue").
to("mqseries:Another.Queue");
-------------------------------
-[[XmlBeans-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The XML Beans dataformat supports 2 options which are listed below.
@@ -31,9 +29,7 @@ The XML Beans dataformat supports 2 options which are listed below.
{% endraw %}
// dataformat options: END
-[[XmlBeans-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use XmlBeans in your camel routes you need to add the dependency on
*camel-xmlbeans* which implements this data format.
@@ -50,4 +46,4 @@ link:download.html[the download page for the latest versions]).
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmljson/src/main/docs/xmljson-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmljson/src/main/docs/xmljson-dataformat.adoc b/components/camel-xmljson/src/main/docs/xmljson-dataformat.adoc
index 472cc2e..4f9e86a 100644
--- a/components/camel-xmljson/src/main/docs/xmljson-dataformat.adoc
+++ b/components/camel-xmljson/src/main/docs/xmljson-dataformat.adoc
@@ -1,4 +1,4 @@
-# XML JSon DataFormat
+## XML JSon DataFormat
*Available as of Camel 2.10*
@@ -17,9 +17,7 @@ semantics are assigned as follows:
* marshalling => converting from XML to JSON
* unmarshalling => converting from JSON to XML.
-[[XmlJson-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The XML JSon dataformat supports 13 options which are listed below.
@@ -47,13 +45,9 @@ The XML JSon dataformat supports 13 options which are listed below.
{% endraw %}
// dataformat options: END
-[[XmlJson-BasicUsagewithJavaDSL]]
-Basic Usage with Java DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Basic Usage with Java DSL
-[[XmlJson-Explicitlyinstantiatingthedataformat]]
-Explicitly instantiating the data format
-++++++++++++++++++++++++++++++++++++++++
+#### Explicitly instantiating the data format
Just instantiate the `XmlJsonDataFormat` from package
`org.apache.camel.dataformat.xmljson`. Make sure you have installed the
@@ -92,9 +86,7 @@ from("direct:marshal").marshal(xmlJsonFormat).to("mock:json");
from("direct:unmarshal").unmarshal(xmlJsonFormat).to("mock:xml");
----
-[[XmlJson-Definingthedataformatin-line]]
-Defining the data format in-line
-++++++++++++++++++++++++++++++++
+#### Defining the data format in-line
Alternatively, you can define the data format inline by using the
`xmljson()` DSL element:
@@ -125,9 +117,7 @@ from("direct:marshalInlineOptions").marshal().xmljson(xmlJsonOptions).to("mock:j
from("direct:unmarshalInlineOptions").unmarshal().xmljson(xmlJsonOptions).to("mock:xmlInlineOptions");
----
-[[XmlJson-BasicusagewithSpringorBlueprintDSL]]
-Basic usage with Spring or Blueprint DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Basic usage with Spring or Blueprint DSL
Within the `<dataFormats>` block, simply configure an `xmljson` element
with unique IDs:
@@ -172,9 +162,7 @@ The syntax with link:using-osgi-blueprint-with-camel.html[Blueprint] is
identical to that of the Spring DSL. Just ensure the correct namespaces
and schemaLocations are in use.
-[[XmlJson-Namespacemappings]]
-Namespace mappings
-^^^^^^^^^^^^^^^^^^
+### Namespace mappings
XML has namespaces to fully qualify elements and attributes; JSON
doesn't. You need to take this into account when performing XML-JSON
@@ -231,9 +219,7 @@ namespacesFormat.setRootElement("person");
And you can achieve the same in Spring DSL.
-[[XmlJson-Example]]
-Example
-+++++++
+#### Example
Using the namespace bindings in the Java snippet above on the following
JSON string:
@@ -265,9 +251,7 @@ _________________________________________________________
That's why the elements are in a different order in the output XML.
-[[XmlJson-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use the link:xmljson.html[XmlJson] dataformat in your camel routes
you need to add the following dependency to your pom:
@@ -290,9 +274,7 @@ license with ASF; so add this manually -->
</dependency>
----
-[[XmlJson-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:data-format.html[Data Format]
-* http://json-lib.sourceforge.net/[json-lib]
+* http://json-lib.sourceforge.net/[json-lib]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmlrpc/src/main/docs/xmlrpc-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmlrpc/src/main/docs/xmlrpc-component.adoc b/components/camel-xmlrpc/src/main/docs/xmlrpc-component.adoc
index f4942c4..293d0eb 100644
--- a/components/camel-xmlrpc/src/main/docs/xmlrpc-component.adoc
+++ b/components/camel-xmlrpc/src/main/docs/xmlrpc-component.adoc
@@ -1,4 +1,4 @@
-# XML RPC Component
+## XML RPC Component
*Available as of Camel 2.11*
@@ -20,9 +20,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[XmlRpc-XmlRpcOverview]]
-XmlRpc Overview
-^^^^^^^^^^^^^^^
+### XmlRpc Overview
It's a http://xmlrpc.scripting.com/spec[spec] and a set of
implementations that allow software running on disparate operating
@@ -86,18 +84,14 @@ A typical XML-RPC fault would be:
</methodResponse>
--------------------------------------------------------------
-[[XmlRpc-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------
xmlrpc://serverUri[?options]
----------------------------
-[[XmlRpc-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -137,9 +131,7 @@ The XML RPC component supports 19 endpoint options which are listed below:
// endpoint options: END
-[[XmlRpc-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Camel XmlRpc uses these headers.
@@ -150,17 +142,13 @@ Camel XmlRpc uses these headers.
|`CamelXmlRpcMethodName` |The XmlRpc method name which will be use for invoking the XmlRpc server.
|=======================================================================
-[[XmlRpc-UsingtheXmlRpcdataformat]]
-Using the XmlRpc data format
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the XmlRpc data format
As the XmlRpc message could be request or response, when you use the
XmlRpcDataFormat, you need to specify the dataformat is for request or
not.
-[[XmlRpc-InvokeXmlRpcServicefromClient]]
-Invoke XmlRpc Service from Client
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Invoke XmlRpc Service from Client
To invoke the XmlRpc service, you need to specify the methodName on the
message header and put the parameters into the message body like below
@@ -173,12 +161,10 @@ XmlRpcException.
String response = template.requestBodyAndHeader(xmlRpcServiceAddress, new Object[]{"me"}, XmlRpcConstants.METHOD_NAME, "hello", String.class);
-------------------------------------------------------------------------------------------------------------------------------------------------
-[[XmlRpc-HowtoconfiguretheXmlRpcClientwithJavacode]]
-How to configure the XmlRpcClient with Java code
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to configure the XmlRpcClient with Java code
camel-xmlrpc provides a pluggable strategy for configuring the
XmlRpcClient used by the component, user just to implement the
*XmlRpcClientConfigurer* interface and can configure the XmlRpcClient as
he wants. The clientConfigure instance reference can be set through the
-uri option clientConfigure.
+uri option clientConfigure.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmlrpc/src/main/docs/xmlrpc-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmlrpc/src/main/docs/xmlrpc-dataformat.adoc b/components/camel-xmlrpc/src/main/docs/xmlrpc-dataformat.adoc
index 4afb7ea..112fffa 100644
--- a/components/camel-xmlrpc/src/main/docs/xmlrpc-dataformat.adoc
+++ b/components/camel-xmlrpc/src/main/docs/xmlrpc-dataformat.adoc
@@ -1,4 +1,4 @@
-# XML RPC DataFormat
+## XML RPC DataFormat
As the XmlRpc message could be request or response, when you use the
XmlRpcDataFormat, you need to specify the dataformat is for request or
@@ -34,9 +34,7 @@ not.
</camelContext>
-------------------------------------------------------------------------------------------------------------------------------------------------
-[[XmlRpc-Dataformat-Options]]
-XmlRpc Dataformat Options
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### XmlRpc Dataformat Options
// dataformat options: START
The XML RPC dataformat supports 2 options which are listed below.
@@ -51,6 +49,4 @@ The XML RPC dataformat supports 2 options which are listed below.
| contentTypeHeader | false | Boolean | Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML or application/json for data formats marshalling to JSon etc.
|=======================================================================
{% endraw %}
-// dataformat options: END
-
-
+// dataformat options: END
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc b/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc
index 656e607..7402627 100644
--- a/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc
+++ b/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc
@@ -1,4 +1,4 @@
-# XML Security DataFormat
+## XML Security DataFormat
The XMLSecurity Data Format facilitates encryption and decryption of XML
payloads at the Document, Element, and Element Content levels (including
@@ -33,9 +33,7 @@ configuration. This enables true namespace matching, even if the prefix
values in the XPath query and the target xml document are not equivalent
strings.
-[[XMLSecurityDataFormat-Options]]
-XMLSecurity Options
-^^^^^^^^^^^^^^^^^^^
+### XMLSecurity Options
// dataformat options: START
The XML Security dataformat supports 12 options which are listed below.
@@ -63,9 +61,7 @@ The XML Security dataformat supports 12 options which are listed below.
// dataformat options: END
-[[XMLSecurityDataFormat-KeyCipherAlgorithm]]
-Key Cipher Algorithm
-++++++++++++++++++++
+#### Key Cipher Algorithm
As of Camel 2.12.0, the default Key Cipher Algorithm is now
XMLCipher.RSA_OAEP instead of XMLCipher.RSA_v1dot5. Usage of
@@ -73,30 +69,22 @@ XMLCipher.RSA_v1dot5 is discouraged due to various attacks. Requests
that use RSA v1.5 as the key cipher algorithm will be rejected unless it
has been explicitly configured as the key cipher algorithm.
-[[XMLSecurityDataFormat-Marshal]]
-Marshal
-^^^^^^^
+### Marshal
In order to encrypt the payload, the `marshal` processor needs to be
applied on the route followed by the *`secureXML()`* tag.
-[[XMLSecurityDataFormat-Unmarshal]]
-Unmarshal
-^^^^^^^^^
+### Unmarshal
In order to decrypt the payload, the `unmarshal` processor needs to be
applied on the route followed by the *`secureXML()`* tag.
-[[XMLSecurityDataFormat-Examples]]
-Examples
-^^^^^^^^
+### Examples
Given below are several examples of how marshalling could be performed
at the Document, Element, and Content levels.
-[[XMLSecurityDataFormat-FullPayloadencryptiondecryption]]
-Full Payload encryption/decryption
-++++++++++++++++++++++++++++++++++
+#### Full Payload encryption/decryption
[source,java]
----------------------------
@@ -106,9 +94,7 @@ from("direct:start")
.to("direct:end");
----------------------------
-[[XMLSecurityDataFormat-PartialPayloadContentOnlyencryptiondecryption]]
-Partial Payload Content Only encryption/decryption
-++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Partial Payload Content Only encryption/decryption
[source,java]
------------------------------------------------------
@@ -121,9 +107,7 @@ from("direct:start")
.to("direct:end");
------------------------------------------------------
-[[XMLSecurityDataFormat-PartialMultiNodePayloadContentOnlyencryptiondecryption]]
-Partial Multi Node Payload Content Only encryption/decryption
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Partial Multi Node Payload Content Only encryption/decryption
[source,java]
------------------------------------------------------
@@ -136,9 +120,7 @@ from("direct:start")
.to("direct:end");
------------------------------------------------------
-[[XMLSecurityDataFormat-PartialPayloadContentOnlyencryptiondecryptionwithchoiceofpassPhrasepassword]]
-Partial Payload Content Only encryption/decryption with choice of passPhrase(password)
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Partial Payload Content Only encryption/decryption with choice of passPhrase(password)
[source,java]
------------------------------------------------------------------
@@ -152,9 +134,7 @@ from("direct:start")
.to("direct:end");
------------------------------------------------------------------
-[[XMLSecurityDataFormat-PartialPayloadContentOnlyencryptiondecryptionwithpassPhrasepasswordandAlgorithm]]
-Partial Payload Content Only encryption/decryption with passPhrase(password) and Algorithm
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Partial Payload Content Only encryption/decryption with passPhrase(password) and Algorithm
[source,java]
-----------------------------------------------------------------------------
@@ -170,9 +150,7 @@ from("direct:start")
.to("direct:end");
-----------------------------------------------------------------------------
-[[XMLSecurityDataFormat-PartialPayloadContentwithNamespacesupport]]
-Partial Payload Content with Namespace support
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Partial Payload Content with Namespace support
[[XMLSecurityDataFormat-JavaDSL]]
Java DSL
@@ -217,9 +195,7 @@ attribute of the `secureXML` element.
...
---------------------------------------------------------------------------------
-[[XMLSecurityDataFormat-AsymmetricKeyEncryption]]
-Asymmetric Key Encryption
-+++++++++++++++++++++++++
+#### Asymmetric Key Encryption
[[XMLSecurityDataFormat-SpringXMLSender]]
Spring XML Sender
@@ -271,8 +247,6 @@ Spring XML Recipient
...
----------------------------------------------------------------------------------------------
-[[XMLSecurityDataFormat-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
-This data format is provided within the *camel-xmlsecurity* component.
+This data format is provided within the *camel-xmlsecurity* component.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc b/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
index c4f7758..ec5a794 100644
--- a/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
+++ b/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
@@ -1,4 +1,4 @@
-# XML Security Component
+## XML Security Component
*Available as of Camel 2.12.0*
@@ -37,9 +37,7 @@ for this component:
</dependency>
----
-[[XMLSecuritycomponent-XMLSignatureWrappingModes]]
-XML Signature Wrapping Modes
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### XML Signature Wrapping Modes
XML Signature differs between enveloped, enveloping, and detached XML
signature. In the
@@ -146,9 +144,7 @@ Elements):
�
-[[XMLSecuritycomponent-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
The camel component consists of two endpoints which have the following
URI format:
@@ -171,9 +167,7 @@ signature and set to the body of the out-message.
* The `name` part in the URI can be chosen by the user to distinguish
between different signer/verifier endpoints within the camel context.
-[[XMLSecuritycomponent-BasicExample]]
-Basic Example
-^^^^^^^^^^^^^
+### Basic Example
The following example shows the basic usage of the component.
@@ -224,9 +218,7 @@ the parent element of the Signature element; see option
For creating _detached_ XML signatures, see sub-chapter "Detached XML
Signatures as Siblings of the Signed Elements".
-[[XMLSecuritycomponent-ComponentOptions]]
-Component Options
-^^^^^^^^^^^^^^^^
+### Component Options
@@ -252,9 +244,7 @@ The XML Security component supports 2 options which are listed below.
-[[XMLSecuritycomponent-EndpointOptions]]
-Endpoint Options
-^^^^^^^^^^^^^^^^
+### Endpoint Options
// endpoint options: START
@@ -307,9 +297,7 @@ The XML Security component supports 37 endpoint options which are listed below:
-[[XMLSecuritycomponent-OutputNodeDeterminationinEnvelopingXMLSignatureCase]]
-Output Node Determination in Enveloping XML Signature Case
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Output Node Determination in Enveloping XML Signature Case
After the validation the node is extracted from the XML signature
document which is finally returned to the output-message body. In the
@@ -377,9 +365,7 @@ or the structure:
</Signature>
----
-[[XMLSecuritycomponent-DetachedXMLSignaturesasSiblingsoftheSignedElements]]
-Detached XML Signatures as Siblings of the Signed Elements
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Detached XML Signatures as Siblings of the Signed Elements
**Since 2.14.0**
@@ -483,9 +469,7 @@ from("direct:detached")
----
-[[XMLSecuritycomponent-XAdES-BESEPESfortheSignerEndpoint]]
-XAdES-BES/EPES for the Signer Endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### XAdES-BES/EPES for the Signer Endpoint
*Available as of Camel 2.15.0*�
@@ -660,9 +644,7 @@ from("direct:xades").to("xmlsecurity:sign://xades?keyAccessor=#keyAccessorDefaul
</bean>
----
-[[XMLSecuritycomponent-Headers]]
-Headers
-+++++++
+#### Headers
[width="100%",cols="1m,1m,4",options="header",]
|=======================================================================
@@ -686,9 +668,7 @@ namespace parameter value
parameter value
|=======================================================================
-[[XMLSecuritycomponent-LimitationswithregardtoXAdESversion1.4.2]]
-Limitations with regard to XAdES version 1.4.2
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Limitations with regard to XAdES version 1.4.2
* No support for signature form XAdES-T and XAdES-C
* Only signer part implemented. Verifier part currently not available.
@@ -713,8 +693,6 @@ the XML signer endpoint).
* The `AllDataObjectsTimeStamp` element is not supported
* The `IndividualDataObjectsTimeStamp` element is not supported
-[[XMLSecuritycomponent-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
-* http://www.w3.org/TR/xmldsig-bestpractices/[Best Practices]
+* http://www.w3.org/TR/xmldsig-bestpractices/[Best Practices]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmpp/src/main/docs/xmpp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmpp/src/main/docs/xmpp-component.adoc b/components/camel-xmpp/src/main/docs/xmpp-component.adoc
index f9f263b..f9e3139 100644
--- a/components/camel-xmpp/src/main/docs/xmpp-component.adoc
+++ b/components/camel-xmpp/src/main/docs/xmpp-component.adoc
@@ -1,4 +1,4 @@
-# XMPP Component
+## XMPP Component
The *xmpp:* component implements an XMPP (Jabber) transport.
@@ -15,9 +15,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[XMPP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,text]
------------------------------------------------------
@@ -33,9 +31,7 @@ starting.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[XMPP-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -77,9 +73,7 @@ The XMPP component supports 21 endpoint options which are listed below:
// endpoint options: END
-[[XMPP-HeadersandsettingSubjectorLanguage]]
-Headers and setting Subject or Language
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Headers and setting Subject or Language
Camel sets the message IN headers as properties on the XMPP message. You
can configure a `HeaderFilterStategy` if you need custom filtering of
@@ -87,9 +81,7 @@ headers.
The *Subject* and *Language* of the XMPP message are also set if they
are provided as IN headers.
-[[XMPP-Examples]]
-Examples
-^^^^^^^^
+### Examples
User `superman` to join room `krypton` at `jabber` server with password,
`secret`:
@@ -152,12 +144,9 @@ from("direct:start").
�
-[[XMPP-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
* link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xstream/src/main/docs/json-xstream-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xstream/src/main/docs/json-xstream-dataformat.adoc b/components/camel-xstream/src/main/docs/json-xstream-dataformat.adoc
index 5045fbd..2215f6f 100644
--- a/components/camel-xstream/src/main/docs/json-xstream-dataformat.adoc
+++ b/components/camel-xstream/src/main/docs/json-xstream-dataformat.adoc
@@ -1,4 +1,4 @@
-# JSon XStream DataFormat
+## JSon XStream DataFormat
XStream is a link:data-format.html[Data Format] which uses the
http://xstream.codehaus.org/[XStream library] to marshal and unmarshal
@@ -20,9 +20,7 @@ Maven users will need to add the following dependency to their
</dependency>
----------------------------------------------------------
-[[XStream-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The JSon XStream dataformat supports 17 options which are listed below.
@@ -55,9 +53,7 @@ The JSon XStream dataformat supports 17 options which are listed below.
// dataformat options: END
-[[XStream-UsingtheJavaDSL]]
-Using the Java DSL
-^^^^^^^^^^^^^^^^^^
+### Using the Java DSL
[source,java]
-----------------------------------------------------------
@@ -84,9 +80,7 @@ from("direct:marshal").
to("mock:marshaled");
---------------------------------------------------------
-[[XStream-XMLInputFactoryandXMLOutputFactory]]
-XMLInputFactory and XMLOutputFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### XMLInputFactory and XMLOutputFactory
http://xstream.codehaus.org/[The XStream library] uses the
`javax.xml.stream.XMLInputFactory` and
@@ -104,9 +98,7 @@ looking in the `META-INF/services/javax.xml.stream.XMLInputFactory`,
available to the JRE.
4. Use the platform default XMLInputFactory,XMLOutputFactory instance.
-[[XStream-HowtosettheXMLencodinginXstreamDataFormat]]
-How to set the XML encoding in Xstream DataFormat?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to set the XML encoding in Xstream DataFormat?
From Camel 2.2.0, you can set the encoding of XML in Xstream DataFormat
by setting the Exchange's property with the key `Exchange.CHARSET_NAME`,
@@ -119,9 +111,7 @@ from("activemq:My.Queue").
to("mqseries:Another.Queue");
-------------------------------
-[[XStream-SettingthetypepermissionsofXstreamDataFormat]]
-Setting the type permissions of Xstream DataFormat
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting the type permissions of Xstream DataFormat
In Camel, one can always use its own processing step in the route to
filter and block certain XML documents to be routed to the XStream's
@@ -154,4 +144,4 @@ DataFormat instance by setting its type permissions property.
permissions="org.apache.camel.samples.xstream.*"/>
...
--------------------------------------------------------------------
+-------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xstream/src/main/docs/xstream-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xstream/src/main/docs/xstream-dataformat.adoc b/components/camel-xstream/src/main/docs/xstream-dataformat.adoc
index 13e84ce..ccb948f 100644
--- a/components/camel-xstream/src/main/docs/xstream-dataformat.adoc
+++ b/components/camel-xstream/src/main/docs/xstream-dataformat.adoc
@@ -1,4 +1,4 @@
-# XStream DataFormat
+## XStream DataFormat
XStream is a link:data-format.html[Data Format] which uses the
http://xstream.codehaus.org/[XStream library] to marshal and unmarshal
@@ -20,9 +20,7 @@ Maven users will need to add the following dependency to their
</dependency>
----------------------------------------------------------
-[[XStream-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The XStream dataformat supports 10 options which are listed below.
@@ -48,9 +46,7 @@ The XStream dataformat supports 10 options which are listed below.
// dataformat options: END
-[[XStream-UsingtheJavaDSL]]
-Using the Java DSL
-^^^^^^^^^^^^^^^^^^
+### Using the Java DSL
[source,java]
-----------------------------------------------------------
@@ -77,9 +73,7 @@ from("direct:marshal").
to("mock:marshaled");
---------------------------------------------------------
-[[XStream-XMLInputFactoryandXMLOutputFactory]]
-XMLInputFactory and XMLOutputFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### XMLInputFactory and XMLOutputFactory
http://xstream.codehaus.org/[The XStream library] uses the
`javax.xml.stream.XMLInputFactory` and
@@ -97,9 +91,7 @@ looking in the `META-INF/services/javax.xml.stream.XMLInputFactory`,
available to the JRE.
4. Use the platform default XMLInputFactory,XMLOutputFactory instance.
-[[XStream-HowtosettheXMLencodinginXstreamDataFormat]]
-How to set the XML encoding in Xstream DataFormat?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to set the XML encoding in Xstream DataFormat?
From Camel 2.2.0, you can set the encoding of XML in Xstream DataFormat
by setting the Exchange's property with the key `Exchange.CHARSET_NAME`,
@@ -112,9 +104,7 @@ from("activemq:My.Queue").
to("mqseries:Another.Queue");
-------------------------------
-[[XStream-SettingthetypepermissionsofXstreamDataFormat]]
-Setting the type permissions of Xstream DataFormat
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting the type permissions of Xstream DataFormat
In Camel, one can always use its own processing step in the route to
filter and block certain XML documents to be routed to the XStream's
@@ -147,4 +137,4 @@ DataFormat instance by setting its type permissions property.
permissions="org.apache.camel.samples.xstream.*"/>
...
--------------------------------------------------------------------
+-------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-yammer/src/main/docs/yammer-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-yammer/src/main/docs/yammer-component.adoc b/components/camel-yammer/src/main/docs/yammer-component.adoc
index 946ebbe..122c3cb 100644
--- a/components/camel-yammer/src/main/docs/yammer-component.adoc
+++ b/components/camel-yammer/src/main/docs/yammer-component.adoc
@@ -1,4 +1,4 @@
-# Yammer Component
+## Yammer Component
*Available as of Camel 2.12*
@@ -25,18 +25,14 @@ for this component:
</dependency>
----
-[[Yammer-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source]
----
yammer:[function]?[options]
----
-[[Yammer-ComponentOptions]]
-Component options
-^^^^^^^^^^^^^^^^^
+### Component options
The Yammer component can be configured with the Yammer account settings
which are mandatory to configure before using.
@@ -66,9 +62,7 @@ The Yammer component supports 4 options which are listed below.
You can also configure these options directly in the endpoint.
-[[Yammer-EndpointOptions]]
-Endpoint options
-^^^^^^^^^^^^^^^^^
+### Endpoint options
@@ -115,9 +109,7 @@ The Yammer component supports 29 endpoint options which are listed below:
-[[Yammer-Consumingmessages]]
-Consuming messages
-^^^^^^^^^^^^^^^^^^
+### Consuming messages
The Yammer component provides several endpoints for consuming
messages:
@@ -148,9 +140,7 @@ and topics that the user is following.
|=======================================================================
-[[Yammer-Messageformat]]
-Message format
-++++++++++++++
+#### Message format
All messages by default are converted to a POJO model provided in the
`org.apache.camel.component.yammer.model` package. The original message
@@ -259,9 +249,7 @@ That said, marshaling this data into POJOs is not free so if you need
you can switch back to using pure JSON by adding the `useJson=false`
option to your URI.
-[[Yammer-Creatingmessages]]
-Creating messages
-^^^^^^^^^^^^^^^^^
+### Creating messages
To create a new message in the account of the current user, you can use
the following URI:
@@ -306,9 +294,7 @@ assertEquals(1, messages.getMessages().size());
assertEquals("Hi from Camel!", messages.getMessages().get(0).getBody().getPlain());
----
-[[Yammer-Retrievinguserrelationships]]
-Retrieving user relationships
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Retrieving user relationships
The Yammer component can retrieve user relationships:
@@ -318,9 +304,7 @@ yammer:relationships?[options]
----
-[[Yammer-Retrievingusers]]
-Retrieving users
-^^^^^^^^^^^^^^^^
+### Retrieving users
The Yammer component provides several endpoints for retrieving
users:
@@ -335,9 +319,7 @@ users:
|=====================================================
-[[Yammer-Usinganenricher]]
-Using an enricher
-^^^^^^^^^^^^^^^^^
+### Using an enricher
It is helpful sometimes (or maybe always in the case of users or
relationship consumers) to use an enricher pattern rather than a route
@@ -361,11 +343,9 @@ from("direct:start")
This will go out and fetch the current user's `User` object and set it as
the Camel message body.
-[[Yammer-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
* link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
+* link:getting-started.html[Getting Started]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-zipfile/src/main/docs/zipfile-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-zipfile/src/main/docs/zipfile-dataformat.adoc b/components/camel-zipfile/src/main/docs/zipfile-dataformat.adoc
index 91e2a76..dc3660d 100644
--- a/components/camel-zipfile/src/main/docs/zipfile-dataformat.adoc
+++ b/components/camel-zipfile/src/main/docs/zipfile-dataformat.adoc
@@ -1,4 +1,4 @@
-# Zip File DataFormat
+## Zip File DataFormat
TIP:*Available since Camel 2.11.0*
@@ -13,9 +13,7 @@ https://blogs.oracle.com/xuemingshen/entry/zip64_support_for_4g_zipfile[Java
Since Camel 2.12.3 there is also a aggregation strategy that can
aggregate multiple messages into a single Zip file.
-[[ZipFile-Options]]
-ZipFile Options
-^^^^^^^^^^^^^^^
+### ZipFile Options
// dataformat options: START
@@ -35,9 +33,7 @@ The Zip File dataformat supports 2 options which are listed below.
-[[ZipFileDataFormat-Marshal]]
-Marshal
-^^^^^^^
+### Marshal
In this example we marshal a regular text/XML payload to a compressed
payload using Zip file compression, and send it to an ActiveMQ queue
@@ -78,9 +74,7 @@ from("direct:start").setHeader(Exchange.FILE_NAME, constant("report.txt")).marsh
This route would result in a Zip file named "report.txt.zip" in the
output directory, containing a single Zip entry named "report.txt".
-[[ZipFileDataFormat-Unmarshal]]
-Unmarshal
-^^^^^^^^^
+### Unmarshal
In this example we unmarshal a Zip file payload from an ActiveMQ queue
called MY_QUEUE to its original format, and forward it for processing to
@@ -119,9 +113,7 @@ like this
.end();
----------------------------------------------------------------------------------------------------
-[[ZipFileDataFormat-Aggregate]]
-Aggregate
-^^^^^^^^^
+### Aggregate
TIP:*Available since Camel 2.12.3*
@@ -157,9 +149,7 @@ the�`CamelFileName`�header explicitly in your route:
.to("file:output/directory");
------------------------------------------------------------
-[[ZipFileDataFormat-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Zip files in your camel routes you need to add a dependency on
*camel-zipfile* which implements this data format.
@@ -176,4 +166,4 @@ link:download.html[the download page for the latest versions]).
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-zookeeper/src/main/docs/zookeeper-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-zookeeper/src/main/docs/zookeeper-component.adoc b/components/camel-zookeeper/src/main/docs/zookeeper-component.adoc
index b139627..fd0ce0f 100644
--- a/components/camel-zookeeper/src/main/docs/zookeeper-component.adoc
+++ b/components/camel-zookeeper/src/main/docs/zookeeper-component.adoc
@@ -1,4 +1,4 @@
-# ZooKeeper Component
+## ZooKeeper Component
*Available as of Camel 2.9*
@@ -28,9 +28,7 @@ for this component:
</dependency>
----
-[[Zookeeper-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source]
----
@@ -40,9 +38,7 @@ zookeeper://zookeeper-server[:port][/path][?options]
The path from the URI specifies the node in the ZooKeeper server (a.k.a.
_znode_) that will be the target of the endpoint:
-[[Zookeeper-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The ZooKeeper component supports 1 options which are listed below.
@@ -84,13 +80,9 @@ The ZooKeeper component supports 14 endpoint options which are listed below:
// endpoint options: END
-[[Zookeeper-Usecases]]
-Use cases
-^^^^^^^^^
+### Use cases
-[[Zookeeper-Readingfromaznode]]
-Reading from a _znode_
-+++++++++++++++++++++
+#### Reading from a _znode_
The following snippet will read the data from the _znode_
`/somepath/somenode/` provided that it already exists. The data
@@ -110,9 +102,7 @@ endpoint await its creation:
from("zookeeper://localhost:39913/somepath/somenode?awaitCreation=true").to("mock:result");
----
-[[Zookeeper-ReadingfromaznodeAdditionalCamel210onwards]]
-Reading from a _znode_ (additional Camel 2.10 onwards)
-++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Reading from a _znode_ (additional Camel 2.10 onwards)
When data is read due to a `WatchedEvent` received from the ZooKeeper
ensemble, the `CamelZookeeperEventType` header holds ZooKeeper's
@@ -121,9 +111,7 @@ value from that `WatchedEvent`. If the data is read initially (not
triggered by a `WatchedEvent`) the `CamelZookeeperEventType` header will not
be set.
-[[Zookeeper-Writingtoaznode]]
-Writing to a _znode_
-++++++++++++++++++++
+#### Writing to a _znode_
The following snippet will write the payload of the exchange into the
znode at `/somepath/somenode/` provided that it already exists:
@@ -216,9 +204,7 @@ Object testPayload = ...
template.sendBodyAndHeader("direct:create-and-write-to-persistent-znode", testPayload, "CamelZooKeeperCreateMode", "PERSISTENT");
----
-[[Zookeeper-ZooKeeperenabledRoutepolicy]]
-ZooKeeper enabled Route policies
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### ZooKeeper enabled Route policies
ZooKeeper allows for very simple and effective leader election out of
the box. This component exploits this election capability in a
@@ -276,11 +262,9 @@ There are currently 3 policies defined in the component, with different SLAs:
thus you can be sure that no even is processed before the Policy takes its decision.
-[[Zookeeper-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
* link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
+* link:getting-started.html[Getting Started]
\ No newline at end of file