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:06 UTC
[01/14] camel git commit: Make heading in adoc files sane again.
Repository: camel
Updated Branches:
refs/heads/master e378f76f3 -> 284296813
Make heading in adoc files sane again.
Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/11dfcc00
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/11dfcc00
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/11dfcc00
Branch: refs/heads/master
Commit: 11dfcc00b44070f07c3dc0d2c06daf56d6afe191
Parents: e378f76
Author: Claus Ibsen <da...@apache.org>
Authored: Wed Jan 11 18:30:25 2017 +0100
Committer: Claus Ibsen <da...@apache.org>
Committed: Wed Jan 11 19:26:15 2017 +0100
----------------------------------------------------------------------
.../maven/packaging/ReadmeComponentMojo.java | 97 ++++++++++----------
1 file changed, 48 insertions(+), 49 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/camel/blob/11dfcc00/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/ReadmeComponentMojo.java
----------------------------------------------------------------------
diff --git a/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/ReadmeComponentMojo.java b/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/ReadmeComponentMojo.java
index 8393470..3725acf 100644
--- a/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/ReadmeComponentMojo.java
+++ b/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/ReadmeComponentMojo.java
@@ -24,6 +24,7 @@ import java.util.List;
import java.util.Map;
import java.util.Set;
import java.util.TreeSet;
+import java.util.stream.Collectors;
import org.apache.camel.maven.packaging.model.ComponentModel;
import org.apache.camel.maven.packaging.model.ComponentOptionModel;
@@ -131,7 +132,7 @@ public class ReadmeComponentMojo extends AbstractMojo {
boolean exists = file.exists();
boolean updated = false;
- updated |= updateTitle(file, model.getTitle() + " Component");
+ updated |= updateTitles(file, model.getTitle() + " Component");
if (model.getComponentOptions() != null) {
String options = templateComponentOptions(model);
@@ -182,7 +183,7 @@ public class ReadmeComponentMojo extends AbstractMojo {
boolean exists = file.exists();
boolean updated = false;
- updated |= updateTitle(file, model.getTitle() + " DataFormat");
+ updated |= updateTitles(file, model.getTitle() + " DataFormat");
if (model.getDataFormatOptions() != null) {
String options = templateDataFormatOptions(model);
@@ -260,7 +261,7 @@ public class ReadmeComponentMojo extends AbstractMojo {
boolean exists = file.exists();
boolean updated = false;
- updated |= updateTitle(file, model.getTitle() + " Language");
+ updated |= updateTitles(file, model.getTitle() + " Language");
if (model.getLanguageOptions() != null) {
String options = templateLanguageOptions(model);
@@ -282,71 +283,69 @@ public class ReadmeComponentMojo extends AbstractMojo {
}
}
- private boolean updateTitle(File file, String title) throws MojoExecutionException {
+ private boolean updateTitles(File file, String title) throws MojoExecutionException {
if (!file.exists()) {
return false;
}
- // they may be in old title format which we want to avoid
- // [[Bean-BeanComponent]]
- // Bean Component
- // ~~~~~~~~~~~~~~
+ boolean updated = false;
try {
String text = loadText(new FileInputStream(file));
- // grab the first 3 lines which can have old legacy format
- String before = StringHelper.before(text, "\n");
- text = StringHelper.after(text, "\n");
- String before2 = StringHelper.before(text, "\n");
- text = StringHelper.after(text, "\n");
- String before3 = StringHelper.before(text, "\n");
- text = StringHelper.after(text, "\n");
-
- // skip old title format
- if (before3 != null && before3.startsWith("~~~")) {
- before = null;
- before2 = null;
- before3 = null;
- }
- if (before2 != null && before2.startsWith("~~~")) {
- before = null;
- before2 = null;
- }
+ List<String> newLines = new ArrayList<>();
- String oldTitle = before;
- if (oldTitle == null) {
- oldTitle = before2;
- }
- if (oldTitle == null) {
- oldTitle = before3;
- }
+ String[] lines = text.split("\n");
+ for (int i = 0; i < lines.length; i++) {
+ String line = lines[i];
- String changed = "# " + title;
- if (!changed.equals(oldTitle)) {
- // insert title in top of file
- String newText = changed + "\n";
- // keep the before lines that was okay to keep
- if (before != null) {
- newText += before + "\n";
+ if (i == 0) {
+ // first line is the title to make the text less noisy we use level 2
+ String newLine = "## " + title;
+ newLines.add(newLine);
+ updated = !line.equals(newLine);
+ continue;
}
- if (before2 != null) {
- newText += before2 + "\n";
- }
- if (before3 != null) {
- newText += before3 + "\n";
+
+ // use single line headers with # as level instead of the cumbersome adoc weird style
+ if (line.startsWith("^^^") || line.startsWith("~~~") || line.startsWith("+++") ) {
+ String level = line.startsWith("+++") ? "####" : "###";
+
+ // transform legacy heading into new style
+ int idx = newLines.size() - 1;
+ String prev = newLines.get(idx);
+
+ newLines.set(idx, level + " " + prev);
+
+ // okay if 2nd-prev line is a [[title]] we need to remove that too
+ // so we have nice clean sub titles
+ idx = newLines.size() - 2;
+ if (idx >= 0) {
+ prev = newLines.get(idx);
+ if (prev.startsWith("[[")) {
+ // remove
+ newLines.remove(idx);
+ }
+ }
+
+ updated = true;
+ } else {
+ // okay normal text so just add it
+ newLines.add(line);
}
- // and remember the doc body
- newText += text;
+ }
+
+ if (updated) {
+ // build the new updated text
+ String newText = newLines.stream().collect(Collectors.joining("\n"));
writeText(file, newText);
- return true;
}
} catch (Exception e) {
throw new MojoExecutionException("Error reading file " + file + " Reason: " + e, e);
}
- return false;
+ return updated;
}
private boolean updateComponentOptions(File file, String changed) throws MojoExecutionException {
[13/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/properties-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/properties-component.adoc b/camel-core/src/main/docs/properties-component.adoc
index f5ef239..78b22c7 100644
--- a/camel-core/src/main/docs/properties-component.adoc
+++ b/camel-core/src/main/docs/properties-component.adoc
@@ -1,10 +1,8 @@
-# Properties Component
+## Properties Component
*Available as of Camel 2.3*
-[[Properties-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source]
----
@@ -13,9 +11,7 @@ properties:key[?options]
Where *key* is the key for the property to lookup
-[[Properties-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The Properties component supports 16 options which are listed below.
@@ -71,9 +67,7 @@ The Properties component supports 7 endpoint options which are listed below:
You can use the method `resolvePropertyPlaceholders` on the
`CamelContext` to resolve a property from any Java code.
-[[Properties-UsingPropertyPlaceholder]]
-Using PropertyPlaceholder
-~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using PropertyPlaceholder
*Available as of Camel 2.3*
@@ -108,9 +102,7 @@ service idiom.
* *Camel 2.14.1* Using custom functions, which can be plugged into the
property component.
-[[Properties-Syntax]]
-Syntax
-^^^^^^
+### Syntax
The syntax to use Camel's property placeholder is to use `{{key}}` for
example `{{file.uri}}` where `file.uri` is the property key.
@@ -126,9 +118,7 @@ NOTE: Do not use colon in the property key. The colon is used as a separator
token when you are providing a default value, which is supported from
*Camel 2.14.1* onwards.
-[[Properties-PropertyResolver]]
-PropertyResolver
-^^^^^^^^^^^^^^^^
+### PropertyResolver
Camel provides a pluggable mechanism which allows 3rd part to provide
their own resolver to lookup properties. Camel provides a default
@@ -144,9 +134,7 @@ prefix is provided)
* `blueprint:` *Camel 2.7:* to use a specific OSGi blueprint placeholder
service
-[[Properties-Defininglocation]]
-Defining location
-^^^^^^^^^^^^^^^^^
+### Defining location
The `PropertiesResolver` need to know a location(s) where to resolve the
properties. You can define 1 to many locations. If you define the
@@ -169,9 +157,7 @@ pc.setLocations(
"com/mycompany/defaults.properties");
----
-[[Properties-Usingsystemandenvironmentvariablesinlocations]]
-Using system and environment variables in locations
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using system and environment variables in locations
*Available as of Camel 2.7*
@@ -205,9 +191,7 @@ You can have multiple placeholders in the same location, such as:
location=file:${env:APP_HOME}/etc/${prop.name}.properties
----
-[[Properties-Usingsystemandenvironmentvariablestoconfigurepropertyprefixesandsuffixes]]
-Using system and environment variables to configure property prefixes and suffixes
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using system and environment variables to configure property prefixes and suffixes
*Available as of Camel 2.12.5, 2.13.3, 2.14.0*
@@ -244,9 +228,7 @@ property�`stage` either to�`dev` (the message will be routed
to�`mock:result1`) or�`test` (the message will be routed
to�`mock:result2`).
-[[Properties-ConfiguringinJavaDSL]]
-Configuring in Java DSL
-^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring in Java DSL
You have to create and register the `PropertiesComponent` under the name
`properties` such as:
@@ -258,9 +240,7 @@ pc.setLocation("classpath:com/mycompany/myprop.properties");
context.addComponent("properties", pc);
----
-[[Properties-ConfiguringinSpringXML]]
-Configuring in Spring XML
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring in Spring XML
Spring XML offers two variations to configure. You can define a spring
bean as a `PropertiesComponent` which resembles the way done in Java
@@ -310,9 +290,7 @@ Setting the properties location through the location tag works just fine but som
Camel 2.10 onwards supports specifying a value for the cache option both
inside the Spring as well as the Blueprint XML.
-[[Properties-UsingaPropertiesfromthe]]
-Using a Properties from the link:registry.html[Registry]
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using a Properties from the link:registry.html[Registry]
*Available as of Camel 2.4* +
For example in OSGi you may want to expose a service which returns the
@@ -330,9 +308,7 @@ Where `myProperties` is the id to use for lookup in the OSGi registry.
Notice we use the `ref:` prefix to tell Camel that it should lookup the
properties for the link:registry.html[Registry].
-[[Properties-Examplesusingpropertiescomponent]]
-Examples using properties component
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Examples using properties component
When using property placeholders in the endpoint URIs you can either use
the `properties:` component or define the placeholders directly in the
@@ -382,9 +358,7 @@ location in the given uri using the `locations` option:
from("direct:start").to("properties:bar.end?locations=com/mycompany/bar.properties");
----
-[[Properties-Examples]]
-Examples
-^^^^^^^^
+### Examples
You can also use property placeholders directly in the endpoint uris
without having to use `properties:`.
@@ -421,9 +395,7 @@ link:producertemplate.html[ProducerTemplate] for example:
template.sendBody("{{cool.start}}", "Hello World");
----
-[[Properties-Examplewithlanguage]]
-Example with link:simple.html[Simple] language
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Example with link:simple.html[Simple] language
The link:simple.html[Simple] language now also support using property
placeholders, for example in the route below:
@@ -451,9 +423,7 @@ from("direct:start")
.transform().simple("Hi ${body}. ${properties:com/mycompany/bar.properties:bar.quote}.");
----
-[[Properties-AdditionalpropertyplaceholdersupportedinSpringXML]]
-Additional property placeholder supported in Spring XML
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional property placeholder supported in Spring XML
The property placeholders is also supported in many of the Camel Spring
XML tags such as
@@ -465,9 +435,7 @@ The example below has property placeholder in the `<jmxAgent>` tag:
You can also define property placeholders in the various attributes on
the `<camelContext>` tag such as `trace` as shown here:
-[[Properties-OverridingapropertysettingusingaJVMSystemProperty]]
-Overriding a property setting using a JVM System Property
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Overriding a property setting using a JVM System Property
*Available as of Camel 2.5* +
It is possible to override a property value at runtime using a JVM
@@ -504,9 +472,7 @@ System.clearProperty("cool.result");
assertMockEndpointsSatisfied();
----
-[[Properties-UsingpropertyplaceholdersforanykindofattributeintheXMLDSL]]
-Using property placeholders for any kind of attribute in the XML DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using property placeholders for any kind of attribute in the XML DSL
*Available as of Camel 2.7*
@@ -533,9 +499,7 @@ In our properties file we have the value defined as
stop=true
----
-[[Properties-UsingpropertyplaceholderintheJavaDSL]]
-Using property placeholder in the Java DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using property placeholder in the Java DSL
*Available as of Camel 2.7*
@@ -543,9 +507,7 @@ Likewise we have added support for defining placeholders in the Java DSL
using the new `placeholder` DSL as shown in the following equivalent
example:
-[[Properties-UsingBlueprintpropertyplaceholderwithCamelroutes]]
-Using Blueprint property placeholder with Camel routes
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using Blueprint property placeholder with Camel routes
*Available as of Camel 2.7*
@@ -658,9 +620,7 @@ location="blueprint:myblueprint.placeholder,classpath:myproperties.properties"
Each location is separated by comma.
-[[Properties-OverridingBlueprintpropertyplaceholdersoutsideCamelContext]]
-Overriding Blueprint property placeholders outside CamelContext
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Overriding Blueprint property placeholders outside CamelContext
*Available as of Camel 2.10.4*
@@ -680,9 +640,7 @@ return value *must* be the `persistence-id` of the
`<cm:property-placeholder>` tag, which you define in the blueprint XML
file.
-[[Properties-Using.cfgor.propertiesfileforBlueprintpropertyplaceholders]]
-Using .cfg or .properties file for Blueprint property placeholders
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using .cfg or .properties file for Blueprint property placeholders
*Available as of Camel 2.10.4*
@@ -714,9 +672,7 @@ placeholders such as:
greeting=Bye
----
-[[Properties-Using.cfgfileandoverridingpropertiesforBlueprintpropertyplaceholders]]
-Using .cfg file and overriding properties for Blueprint property placeholders
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using .cfg file and overriding properties for Blueprint property placeholders
You can do both as well. Here is a complete example. First we have the
Blueprint XML file:
@@ -732,9 +688,7 @@ echo=Yay
destination=mock:result
----
-[[Properties-BridgingSpringandCamelpropertyplaceholders]]
-Bridging Spring and Camel property placeholders
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Bridging Spring and Camel property placeholders
*Available as of Camel 2.10*
@@ -764,9 +718,7 @@ Notice how the hello bean is using pure Spring property placeholders
using the `${ }` notation. And in the Camel routes we use the Camel
placeholder notation with `{{` and `}}`.
-[[Properties-ClashingSpringpropertyplaceholderswithCamelslanguage]]
-Clashing Spring property placeholders with Camels link:simple.html[Simple] language
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Clashing Spring property placeholders with Camels link:simple.html[Simple] language
Take notice when using Spring bridging placeholder then the spring `${ }`
syntax clashes with the link:simple.html[Simple] in Camel, and therefore
@@ -792,9 +744,7 @@ to indicate using the link:simple.html[Simple] language in Camel.
An alternative is to configure the `PropertyPlaceholderConfigurer` with
`ignoreUnresolvablePlaceholders` option to `true`.
-[[Properties-OverridingpropertiesfromCameltestkit]]
-Overriding properties from Camel test kit
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Overriding properties from Camel test kit
*Available as of Camel 2.10*
@@ -823,9 +773,7 @@ instruct Camel to ignore any locations which was not discoverable, for
example if you run the unit test, in an environment that does not have
access to the location of the properties.
-[[Properties-UsingPropertyInject]]
-Using @PropertyInject
-^^^^^^^^^^^^^^^^^^^^^
+### Using @PropertyInject
*Available as of Camel 2.12*
@@ -876,9 +824,7 @@ You can also add a default value if the key does not exists, such as:
private int timeout;
----
-[[Properties-Usingoutoftheboxfunctions]]
-Using out of the box functions
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using out of the box functions
*Available as of Camel 2.14.1*
@@ -981,9 +927,7 @@ example to call a service on localhost, maybe for unit testing etc
</camelContext>
----
-[[Properties-Usingcustomfunctions]]
-Using custom functions
-^^^^^^^^^^^^^^^^^^^^^^
+### Using custom functions
*Available as of Camel 2.14.1*
@@ -1054,15 +998,11 @@ To register a custom function from Java code is as shown below:
�
-[[Properties-SeeAlso]]
-See Also
-~~~~~~~~
+### See Also
* link:properties.html[Properties] component
-[[Properties-SeeAlso.1]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -1070,4 +1010,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:jasypt.html[Jasypt] for using encrypted values (eg passwords) in
-the properties
+the properties
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/ref-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/ref-component.adoc b/camel-core/src/main/docs/ref-component.adoc
index 4bc2125..d6e9d36 100644
--- a/camel-core/src/main/docs/ref-component.adoc
+++ b/camel-core/src/main/docs/ref-component.adoc
@@ -1,11 +1,9 @@
-# Ref Component
+## Ref Component
The *ref:* component is used for lookup of existing endpoints bound in
the link:registry.html[Registry].
-[[Ref-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------
@@ -17,9 +15,7 @@ link:registry.html[Registry] (usually, but not always, the Spring
registry). If you are using the Spring registry, `someName` would be the
bean ID of an endpoint in the Spring registry.
-[[Ref-Options]]
-Ref Options
-^^^^^^^^^^^
+### Ref Options
// component options: START
The Ref component has no options.
@@ -43,9 +39,7 @@ The Ref component supports 5 endpoint options which are listed below:
// endpoint options: END
-[[Ref-Runtimelookup]]
-Runtime lookup
-^^^^^^^^^^^^^^
+### Runtime lookup
This component can be used when you need dynamic discovery of endpoints
in the link:registry.html[Registry] where you can compute the URI at
@@ -77,9 +71,7 @@ link:registry.html[Registry] such as:
</camelContext>
----------------------------------------------------------------------------------
-[[Ref-Sample]]
-Sample
-^^^^^^
+### Sample
In the sample below we use the `ref:` in the URI to reference the
endpoint with the spring ID, `endpoint2`:
@@ -93,12 +85,9 @@ You could, of course, have used the `ref` attribute instead:
Which is the more common way to write it.
-[[Ref-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/camel-core/src/main/docs/ref-language.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/ref-language.adoc b/camel-core/src/main/docs/ref-language.adoc
index bc6c176..2908142 100644
--- a/camel-core/src/main/docs/ref-language.adoc
+++ b/camel-core/src/main/docs/ref-language.adoc
@@ -1,4 +1,4 @@
-# Ref Language
+## Ref Language
*Available as of Camel 2.8*
@@ -7,9 +7,7 @@ link:expression.html[Expression] or link:predicate.html[Predicate] from the link
This is particular useable in XML DSLs.
-[[RefLanguage-Options]]
-Ref Language options
-^^^^^^^^^^^^^^^^^^^^
+### Ref Language options
// language options: START
The Ref language supports 1 options which are listed below.
@@ -25,9 +23,7 @@ The Ref language supports 1 options which are listed below.
{% endraw %}
// language options: END
-[[RefLanguage-Exampleusage]]
-Example usage
-^^^^^^^^^^^^^
+### Example usage
The link:splitter.html[Splitter] in XML DSL can utilize a custom
expression using `<ref>` like:
@@ -59,8 +55,6 @@ And the same example using Java DSL:
from("seda:a").split().ref("myExpression").to("seda:b");
--------------------------------------------------------
-[[RefLanguage-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
-The Ref language is part of *camel-core*.
+The Ref language is part of *camel-core*.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/rest-api-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/rest-api-component.adoc b/camel-core/src/main/docs/rest-api-component.adoc
index f575373..6857be5 100644
--- a/camel-core/src/main/docs/rest-api-component.adoc
+++ b/camel-core/src/main/docs/rest-api-component.adoc
@@ -1,4 +1,4 @@
-# REST API Component
+## REST API Component
*Available as of Camel 2.14*
@@ -6,9 +6,7 @@ Apache Camel offers a REST styled DSL which can be used with Java or
XML. The intention is to allow end users to define REST services using a
REST style with verbs such as get, post, delete etc.
-[[RestDSL-Howitworks]]
-How it works
-++++++++++++
+#### How it works
The Rest DSL is a facade that builds link:rest.html[Rest]�endpoints as
consumers for Camel routes. The actual REST transport is leveraged by
@@ -16,9 +14,7 @@ using Camel REST components such
as�link:restlet.html[Restlet],�link:spark-rest.html[Spark-rest], and
others that has native REST integration.
-[[RestDSL-ComponentssupportingRestDSL]]
-Components supporting Rest DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Components supporting Rest DSL
The following Camel components supports the Rest DSL. See the bottom of
this page for how to integrate a component with the Rest DSL.
@@ -39,9 +35,7 @@ supports�link:swagger-java.html[Swagger Java]�from Camel 2.17 onwards)
* link:undertow.html[camel-undertow]�(also
supports�link:swagger-java.html[Swagger Java]�from Camel 2.17 onwards)
-[[RestDSL-RestDSLwithJava]]
-Rest DSL with Java
-^^^^^^^^^^^^^^^^^^
+### Rest DSL with Java
To use the Rest DSL in Java then just do as with regular Camel routes by
extending the�`RouteBuilder` and define the routes in the�`configure`
@@ -91,9 +85,7 @@ routing directly to an endpoint using to(). An alternative is to embed a
Camel route directly using route() - there is such an example further
below.
-[[RestDSL-RestDSLwithXML]]
-Rest DSL with XML
-^^^^^^^^^^^^^^^^^
+### Rest DSL with XML
The REST DSL supports the XML DSL also using either Spring or Blueprint.
The example above can be define in XML as shown below:
@@ -129,9 +121,7 @@ The example above can be define in XML as shown below:
�
-[[RestDSL-Usingbasepath]]
-Using base path
-^^^^^^^^^^^^^^^
+### Using base path
The REST DSL allows to define base path to make the DSL a bit more DRY.
For example to define a customer path, we can set the base path in
@@ -189,9 +179,7 @@ only. The example above can be defined as:
</rest>
-------------------------------------------
-[[RestDSL-UsingDynamicTo]]
-Using Dynamic To
-^^^^^^^^^^^^^^^^
+### Using Dynamic To
*Available as of Camel 2.16*
@@ -207,9 +195,7 @@ over�link:jms.html[JMS] where the queue name is dynamic defined
}
-------------------------------------------------------------------------
-[[RestDSL-AndinXMLDSL]]
-And in XML DSL
-^^^^^^^^^^^^^^
+### And in XML DSL
[source,xml]
---------------------------------------------------
@@ -226,9 +212,7 @@ See more details at�link:message-endpoint.html[Message Endpoint] about
the dynamic to, and what syntax it supports. By default it uses
the�link:simple.html[Simple] language, but it has more power than so.
-[[RestDSL-EmbeddingCamelroutes]]
-Embedding Camel routes
-^^^^^^^^^^^^^^^^^^^^^^
+### Embedding Camel routes
Each of the rest service becomes a Camel route,�so in the first example
we have 2 x get and 1 x post REST service, which each become a Camel
@@ -275,9 +259,7 @@ today.
---------------------------------------------------------------------------------------------
-[[RestDSL-ManagingRestservices]]
-Managing Rest services
-^^^^^^^^^^^^^^^^^^^^^^
+### Managing Rest services
Each of the rest service becomes a Camel route, so in the first example
we have 2 x get and 1 x post REST service, which each become a Camel
@@ -292,9 +274,7 @@ performance statistics.
There is also a Rest Registry JMX MBean that contains a registry of all
REST services which has been defined.�
-[[RestDSL-BindingtoPOJOsusing]]
-Binding to POJOs using
-^^^^^^^^^^^^^^^^^^^^^^
+### Binding to POJOs using
The Rest DSL supports automatic binding json/xml contents to/from POJOs
using Camels�link:data-format.html[Data Format]. By default the binding
@@ -481,9 +461,7 @@ public class UserPojo {
By having the JAXB annotations the POJO supports both json and xml
bindings.
-[[RestDSL-ConfiguringRestDSL]]
-Configuring Rest DSL
-^^^^^^^^^^^^^^^^^^^^
+### Configuring Rest DSL
// component options: START
@@ -532,9 +510,7 @@ example configure 2 component options, and 3 endpoint options etc.
�
-[[RestDSL-EnablingordisablingJacksonJSONfeatures]]
-Enabling or disabling Jackson JSON features
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling or disabling Jackson JSON features
*Available as of Camel 2.15*
@@ -588,9 +564,7 @@ The rest configuration is of course also possible using XML DSL
�
-[[RestDSL-DefaultCORSheaders]]
-Default CORS headers
-^^^^^^^^^^^^^^^^^^^^
+### Default CORS headers
*Available as of Camel 2.14.1*
@@ -612,9 +586,7 @@ Access-Control-Request-Method, Access-Control-Request-Headers
|Access-Control-Max-Age |3600
|=======================================================================
�
-[[RestDSL-Definingacustomerrormessageas-is]]
-Defining a custom error message as-is
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Defining a custom error message as-is
If you want to define custom error messages to be sent back to the
client with a HTTP error code (eg such as 400, 404 etc.) then
@@ -658,9 +630,7 @@ the HTTP error code to 400. This is important, as that tells rest-dsl
that this is a custom error message, and the message should not use the
output pojo binding (eg would otherwise bind to CountryPojo).
-[[RestDSL-CatchingJsonParserExceptionandreturningacustomerrormessage]]
-Catching JsonParserException and returning a custom error message
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Catching JsonParserException and returning a custom error message
From�*Camel 2.14.1* onwards you return a custom message as-is (see
previous section). So we can leverage this with Camel error handler to
@@ -679,9 +649,7 @@ onException(JsonParseException.class)
�
-[[RestDSL-ParameterdefaultValues]]
-Parameter default Values
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Parameter default Values
You can specify default values for parameters in the rest-dsl, such as
the verbose parameter below:
@@ -703,9 +671,7 @@ key�`verbose` then Camel will now include a header with key�`verbose`
and the value�`false` because it was declared as the default value. This
functionality is only applicable for query parameters.
-[[RestDSL-IntegratingaCamelcomponentwithRestDSL]]
-Integrating a Camel component with Rest DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Integrating a Camel component with Rest DSL
Any Apache Camel component can integrate with the Rest DSL if they can
be used as a REST service (eg as a REST consumer in Camel lingo). To
@@ -717,9 +683,7 @@ Camel consumer that exposes the REST services based on the given
parameters, such as path, verb, and other options. For example see the
source code for camel-restlet, camel-spark-rest.
-[[RestDSL-SwaggerAPI]]
-Swagger API
-^^^^^^^^^^^
+### Swagger API
The Rest DSL supports link:swagger-java.html[Swagger Java]�by
the�`camel-swagger-java` module. See more details at
@@ -777,14 +741,11 @@ And in Java DSL
For an example see the�`examples/camel-example-servlet-rest-tomcat`�of
the Apache Camel distribution.
-[[RestDSL-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:dsl.html[DSL]
* link:rest.html[Rest]
* link:swagger-java.html[Swagger Java]
* link:spark-rest.html[Spark-rest]
* link:how-do-i-import-rests-from-other-xml-files.html[How do I import
-rests from other XML files]
-
+rests from other XML files]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/rest-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/rest-component.adoc b/camel-core/src/main/docs/rest-component.adoc
index 6a3e54a..054c36d 100644
--- a/camel-core/src/main/docs/rest-component.adoc
+++ b/camel-core/src/main/docs/rest-component.adoc
@@ -1,4 +1,4 @@
-# REST Component
+## REST Component
*Available as of Camel 2.14*
@@ -8,18 +8,14 @@ REST transport.
From Camel 2.18 onwards the rest component can also be used as a client (producer) to call REST services.
-[[Rest-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------------------------
rest://method:path[:uriTemplate]?[options]
--------------------------------------------
-[[Rest-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
The REST component supports 3 options which are listed below.
@@ -65,9 +61,7 @@ The REST component supports 17 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[Components-Supported]]
-Supported rest components
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Supported rest components
The following components support rest consumer (link:rest-dsl.html[Rest DSL]):
@@ -89,9 +83,7 @@ The following components support rest producer:
* camel-restlet
* camel-undertow
-[[Rest-PathanduriTemplatesyntax]]
-Path and uriTemplate syntax
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Path and uriTemplate syntax
The path and uriTemplate option is defined using a REST syntax where you
define the REST context path using support for parameters.�
@@ -130,9 +122,7 @@ have two REST services configured using uriTemplates.
.transform().simple("Bonjour ${header.me}");
------------------------------------------------
-[[Rest-Producer]]
-Rest producer examples
-^^^^^^^^^^^^^^^^^^^^^^
+### Rest producer examples
You can use the rest component to call REST services like any other Camel component.
@@ -183,9 +173,7 @@ to use http4 you can do:
--------------------------------------------
-[[Rest-Producer-Binding]]
-Rest producer binding
-^^^^^^^^^^^^^^^^^^^^^
+### Rest producer binding
The REST producer supports binding using JSon or XML like the rest-dsl does.
@@ -229,9 +217,7 @@ For example if the REST service returns a JSon payload that binds to `com.foo.My
IMPORTANT: You must configure `outType` option if you want POJO binding to happen for the response messages received from calling the REST service.
-[[Rest-Moreexamples]]
-More examples
-^^^^^^^^^^^^^
+### More examples
See�link:rest-dsl.html[Rest DSL]�which offers more examples and how you
can use the Rest DSL to define those in a nicer RESTful way.
@@ -242,9 +228,7 @@ link:rest-dsl.html[Rest DSL] with link:servlet.html[SERVLET]�as
transport�that can be deployed on Apache Tomcat, or similar web
containers.
-[[Rest-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -252,5 +236,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:rest-dsl.html[Rest DSL]
-* link:servlet.html[SERVLET]
-
+* link:servlet.html[SERVLET]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/scheduler-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/scheduler-component.adoc b/camel-core/src/main/docs/scheduler-component.adoc
index 98a498a..a942f1a 100644
--- a/camel-core/src/main/docs/scheduler-component.adoc
+++ b/camel-core/src/main/docs/scheduler-component.adoc
@@ -1,4 +1,4 @@
-# Scheduler Component
+## Scheduler Component
*Available as of Camel 2.15*
@@ -10,9 +10,7 @@ JDK�`ScheduledExecutorService`. Where as the timer uses a JDK�`Timer`.
You can only consume events from this endpoint.
-[[Scheduler-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------
@@ -30,9 +28,7 @@ You can append query options to the URI in the following format,
*Note:* The IN body of the generated exchange is `null`. So
`exchange.getIn().getBody()` returns `null`.
-[[Scheduler-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The Scheduler component supports 1 options which are listed below.
@@ -82,9 +78,7 @@ The Scheduler component supports 21 endpoint options which are listed below:
// endpoint options: END
-[[Scheduler-Moreinformation]]
-More information
-^^^^^^^^^^^^^^^^
+### More information
This component is a scheduler
http://camel.apache.org/polling-consumer.html[Polling Consumer]�where
@@ -92,9 +86,7 @@ you can find more information about the options above, and examples at
the http://camel.apache.org/polling-consumer.html[Polling
Consumer]�page.
-[[Scheduler-ExchangeProperties]]
-Exchange Properties
-^^^^^^^^^^^^^^^^^^^
+### Exchange Properties
When the timer is fired, it adds the following information as properties
to the `Exchange`:
@@ -108,9 +100,7 @@ to the `Exchange`:
|`Exchange.TIMER_FIRED_TIME` |`Date` |The time when the consumer fired.
|=======================================================================
-[[Scheduler-Sample]]
-Sample
-^^^^^^
+### Sample
To set up a route that generates an event every 60 seconds:
@@ -137,17 +127,13 @@ And the route in Spring DSL:
�
-[[Scheduler-Forcingtheschedulertotriggerimmediatelywhencompleted]]
-Forcing the scheduler to trigger immediately when completed
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Forcing the scheduler to trigger immediately when completed
To let the scheduler trigger as soon as the previous task is complete,
you can set the option greedy=true. But beware then the scheduler will
keep firing all the time. So use this with caution.
-[[Scheduler-Forcingtheschedulertobeidle]]
-Forcing the scheduler to be idle
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Forcing the scheduler to be idle
There can be use cases where you want the scheduler to trigger and be
greedy. But sometimes you want "tell the scheduler" that there was no
@@ -163,9 +149,7 @@ exchange.
�
-[[Scheduler-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -173,5 +157,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:timer.html[Timer]
-* link:quartz.html[Quartz]
-
+* link:quartz.html[Quartz]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/seda-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/seda-component.adoc b/camel-core/src/main/docs/seda-component.adoc
index 7fb7d10..9c0bb25 100644
--- a/camel-core/src/main/docs/seda-component.adoc
+++ b/camel-core/src/main/docs/seda-component.adoc
@@ -1,4 +1,4 @@
-# SEDA Component
+## SEDA Component
The *seda:* component provides asynchronous
http://www.eecs.harvard.edu/~mdw/proj/seda/[SEDA] behavior, so that
@@ -20,9 +20,7 @@ TIP:*Synchronous*
The link:direct.html[Direct] component provides synchronous invocation
of any consumers when a producer sends a message exchange.
-[[SEDA-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------
@@ -35,9 +33,7 @@ within the current link:camelcontext.html[CamelContext].
You can append query options to the URI in the following format:
`?option=value&option=value&\u2026`
-[[SEDA-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The SEDA component supports 3 options which are listed below.
@@ -85,9 +81,7 @@ The SEDA component supports 17 endpoint options which are listed below:
// endpoint options: END
-[[SEDA-ChoosingBlockingQueueimplementation]]
-Choosing BlockingQueue implementation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Choosing BlockingQueue implementation
*Available as of Camel 2.12*
@@ -120,9 +114,7 @@ ArrayBlockingQueueFactory and PriorityBlockingQueueFactory:
<from>seda:priority?queueFactory=#priorityQueueFactory&size=100</from>
-----------------------------------------------------------------------------------------------------
-[[SEDA-UseofRequestReply]]
-Use of Request Reply
-^^^^^^^^^^^^^^^^^^^^
+### Use of Request Reply
The link:seda.html[SEDA] component supports using
link:request-reply.html[Request Reply], where the caller will wait for
@@ -151,9 +143,7 @@ between the waiting threads properly.
This has been improved in *Camel 2.3* onwards, which allows you to chain
as many endpoints as you like.
-[[SEDA-Concurrentconsumers]]
-Concurrent consumers
-^^^^^^^^^^^^^^^^^^^^
+### Concurrent consumers
By default, the SEDA endpoint uses a single consumer thread, but you can
configure it to use concurrent consumer threads. So instead of thread
@@ -168,9 +158,7 @@ As for the difference between the two, note a _thread pool_ can
increase/shrink dynamically at runtime depending on load, whereas the
number of concurrent consumers is always fixed.
-[[SEDA-Threadpools]]
-Thread pools
-^^^^^^^^^^^^
+### Thread pools
Be aware that adding a thread pool to a SEDA endpoint by doing something
like:
@@ -194,9 +182,7 @@ from("direct:stageName").thread(5).process(...)
You can also directly configure number of threads that process messages
on a SEDA endpoint using the `concurrentConsumers` option.
-[[SEDA-Sample]]
-Sample
-^^^^^^
+### Sample
In the route below we use the SEDA queue to send the request to this
async queue to be able to send a fire-and-forget message for further
@@ -210,9 +196,7 @@ another thread for further processing. Since this is from a unit test,
it will be sent to a `mock` endpoint where we can do assertions in the
unit test.
-[[SEDA-UsingmultipleConsumers]]
-Using multipleConsumers
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using multipleConsumers
*Available as of Camel 2.2*
@@ -227,9 +211,7 @@ As the beans are part of an unit test they simply send the message to a
mock endpoint, but notice how we can use @Consume to consume from the
seda queue.
-[[SEDA-Extractingqueueinformation.]]
-Extracting queue information.
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Extracting queue information.
If needed, information such as queue size, etc. can be obtained without
using JMX in this fashion:
@@ -240,9 +222,7 @@ SedaEndpoint seda = context.getEndpoint("seda:xxxx");
int size = seda.getExchanges().size();
-----------------------------------------------------
-[[SEDA-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -252,5 +232,4 @@ See Also
* link:vm.html[VM]
* link:disruptor.html[Disruptor]
* link:direct.html[Direct]
-* link:async.html[Async]
-
+* link:async.html[Async]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/serialization-dataformat.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/serialization-dataformat.adoc b/camel-core/src/main/docs/serialization-dataformat.adoc
index 3ee351f..ee81d0f 100644
--- a/camel-core/src/main/docs/serialization-dataformat.adoc
+++ b/camel-core/src/main/docs/serialization-dataformat.adoc
@@ -1,4 +1,4 @@
-# Java Object Serialization DataFormat
+## Java Object Serialization DataFormat
Serialization is a link:data-format.html[Data Format] which uses the
standard Java Serialization mechanism to unmarshal a binary payload into
@@ -13,9 +13,7 @@ from("file://foo/bar").
to("activemq:Some.Queue");
------------------------------
-[[Serialization-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The Java Object Serialization dataformat supports 1 options which are listed below.
@@ -31,9 +29,7 @@ The Java Object Serialization dataformat supports 1 options which are listed bel
{% endraw %}
// dataformat options: END
-[[Serialization-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
This data format is provided in *camel-core* so no additional
-dependencies is needed.
+dependencies is needed.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/simple-language.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/simple-language.adoc b/camel-core/src/main/docs/simple-language.adoc
index b5c6cca..fc54cd6 100644
--- a/camel-core/src/main/docs/simple-language.adoc
+++ b/camel-core/src/main/docs/simple-language.adoc
@@ -1,4 +1,4 @@
-# Simple Language
+## Simple Language
The Simple Expression Language was a really simple language when it was
created, but has since grown more powerful. It is primarily intended for
@@ -76,9 +76,7 @@ You can have multiple functions in the same expression:
having another $\{ } placeholder in an existing, is not allowed). +
From *Camel 2.9* onwards you can nest functions.
-[[SimpleLanguage-Options]]
-Simple Language options
-^^^^^^^^^^^^^^^^^^^^^^^
+### Simple Language options
// language options: START
The Simple language supports 2 options which are listed below.
@@ -95,9 +93,7 @@ The Simple language supports 2 options which are listed below.
{% endraw %}
// language options: END
-[[Simple-Variables]]
-Variables
-^^^^^^^^^
+### Variables
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -289,9 +285,7 @@ includes the route strack-trace). This can be used if you do not want to
log sensitive data from the message itself.
|=======================================================================
-[[Simple-OGNLexpressionsupport]]
-OGNL expression support
-^^^^^^^^^^^^^^^^^^^^^^^
+### OGNL expression support
*Available as of Camel 2.3*
@@ -426,9 +420,7 @@ And yes you can combine this with the operator support as shown below:
simple("${body.address.zip} > 1000")
------------------------------------
-[[Simple-Operatorsupport]]
-Operator support
-^^^^^^^^^^^^^^^^
+### Operator support
The parser is limited to only support a single operator.
@@ -726,9 +718,7 @@ order:
</from>
------------------------------------------------------------
-[[Simple-Usingandor]]
-Using and / or
-++++++++++++++
+#### Using and / or
If you have two expressions you can combine them with the `and` or `or`
operator.
@@ -760,9 +750,7 @@ language expression. This might change in the future. +
simple("${in.header.title} contains 'Camel' and ${in.header.type'} == 'gold' and ${in.header.number} range 100..200")
---------------------------------------------------------------------------------------------------------------------
-[[Simple-Samples]]
-Samples
-^^^^^^^
+### Samples
In the Spring XML sample below we filter based on a header value:
@@ -877,9 +865,7 @@ From Camel 2.9 onwards you can nest functions, such as shown below:
</setHeader>
--------------------------------------------------
-[[Simple-Referringtoconstantsorenums]]
-Referring to constants or enums
-+++++++++++++++++++++++++++++++
+#### Referring to constants or enums
*Available as of Camel 2.11*
@@ -889,9 +875,7 @@ And in a link:content-based-router.html[Content Based Router] we can use
the link:simple.html[Simple] language to refer to this enum, to check
the message which enum it matches.
-[[Simple-UsingnewlinesortabsinXMLDSLs]]
-Using new lines or tabs in XML DSLs
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using new lines or tabs in XML DSLs
*Available as of Camel 2.9.3*
@@ -905,9 +889,7 @@ XML DSLs as you can escape the value now
</transform>
-------------------------------------------------------
-[[Simple-Leadingandtrailingwhitespacehandling]]
-Leading and trailing whitespace handling
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Leading and trailing whitespace handling
*Available as of Camel 2.10.0*
@@ -923,9 +905,7 @@ whitespace characters.
</setBody>
---------------------------------------------------------------------------------
-[[Simple-Settingresulttype]]
-Setting result type
-^^^^^^^^^^^^^^^^^^^
+### Setting result type
*Available as of Camel 2.8*
@@ -951,9 +931,7 @@ And in XML DSL
</setHeader>
---------------------------------------------------------------------------------------
-[[Simple-Changingfunctionstartandendtokens]]
-Changing function start and end tokens
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Changing function start and end tokens
*Available as of Camel 2.9.1*
@@ -978,9 +956,7 @@ applications which share the same *camel-core* on their classpath. +
For example in an OSGi server this may affect many applications, where
as a Web Application as a WAR file it only affects the Web Application.
-[[Simple-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -994,9 +970,7 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").simple("resource:classpath:mysimple.txt")
----------------------------------------------------------------
-[[Simple-SettingSpringbeanstoExchangeproperties]]
-Setting Spring beans to Exchange properties
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting Spring beans to Exchange properties
*Available as of Camel 2.6*
@@ -1015,8 +989,6 @@ You can set a spring bean into an exchange property as shown below:
</route>
-------------------------------------------------------
-[[Simple-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
-The link:simple.html[Simple] language is part of *camel-core*.
+The link:simple.html[Simple] language is part of *camel-core*.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/string-dataformat.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/string-dataformat.adoc b/camel-core/src/main/docs/string-dataformat.adoc
index b43199b..0a6c72a 100644
--- a/camel-core/src/main/docs/string-dataformat.adoc
+++ b/camel-core/src/main/docs/string-dataformat.adoc
@@ -1,11 +1,9 @@
-# String Encoding DataFormat
+## String Encoding DataFormat
The String link:data-format.html[Data Format] is a textual based format
that supports encoding.
-[[String-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The String Encoding dataformat supports 2 options which are listed below.
@@ -22,9 +20,7 @@ The String Encoding dataformat supports 2 options which are listed below.
{% endraw %}
// dataformat options: END
-[[String-Marshal]]
-Marshal
-^^^^^^^
+### Marshal
In this example we marshal the file content to String object in UTF-8
encoding.
@@ -34,9 +30,7 @@ encoding.
from("file://data.csv").marshal().string("UTF-8").to("jms://myqueue");
----------------------------------------------------------------------
-[[String-Unmarshal]]
-Unmarshal
-^^^^^^^^^
+### Unmarshal
In this example we unmarshal the payload from the JMS queue to a String
object using UTF-8 encoding, before its processed by the newOrder
@@ -47,9 +41,7 @@ processor.
from("jms://queue/order").unmarshal().string("UTF-8").processRef("newOrder");
-----------------------------------------------------------------------------
-[[String-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
This data format is provided in *camel-core* so no additional
-dependencies is needed.
+dependencies is needed.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/stub-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/stub-component.adoc b/camel-core/src/main/docs/stub-component.adoc
index a10370d..8b255dd 100644
--- a/camel-core/src/main/docs/stub-component.adoc
+++ b/camel-core/src/main/docs/stub-component.adoc
@@ -1,4 +1,4 @@
-# Stub Component
+## Stub Component
*Available as of Camel 2.10*
@@ -16,9 +16,7 @@ usually fail. Stub won't though, as it basically ignores all query
parameters to let you quickly stub out one or more endpoints in your
route temporarily.
-[[Stub-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------
@@ -27,9 +25,7 @@ stub:someUri
Where *`someUri`* can be any URI with any query parameters.
-[[Stub-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The Stub component supports 3 options which are listed below.
@@ -77,9 +73,7 @@ The Stub component supports 17 endpoint options which are listed below:
// endpoint options: END
-[[Stub-Examples]]
-Examples
-^^^^^^^^
+### Examples
Here are a few samples:
@@ -87,12 +81,9 @@ Here are a few samples:
*
stub:http://somehost.bar.com/something[http://somehost.bar.com/something]
-[[Stub-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/camel-core/src/main/docs/test-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/test-component.adoc b/camel-core/src/main/docs/test-component.adoc
index 39a5050..51e9232 100644
--- a/camel-core/src/main/docs/test-component.adoc
+++ b/camel-core/src/main/docs/test-component.adoc
@@ -1,4 +1,4 @@
-# Test Component
+## Test Component
link:testing.html[Testing] of distributed and asynchronous processing is
notoriously difficult. The link:mock.html[Mock], link:test.html[Test]
@@ -37,9 +37,7 @@ for this component when using *Camel 2.8* or older:
From Camel 2.9 onwards the link:test.html[Test] component is provided
directly in the camel-core.
-[[Test-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------------
@@ -50,9 +48,7 @@ Where *expectedMessagesEndpointUri* refers to some other
link:component.html[Component] URI that the expected message bodies are
pulled from before starting the test.
-[[Test-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
The Test component has no options.
@@ -86,9 +82,7 @@ The Test component supports 15 endpoint options which are listed below:
// endpoint options: END
-[[Test-Example]]
-Example
-^^^^^^^
+### Example
For example, you could write a test case as follows:
@@ -105,14 +99,11 @@ method], your test case will perform the necessary assertions.
To see how you can set other expectations on the test endpoint, see the
link:mock.html[Mock] component.
-[[Test-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:spring-testing.html[Spring Testing]
-
+* link:spring-testing.html[Spring Testing]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/timer-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/timer-component.adoc b/camel-core/src/main/docs/timer-component.adoc
index 5eb25eb..e8eb075 100644
--- a/camel-core/src/main/docs/timer-component.adoc
+++ b/camel-core/src/main/docs/timer-component.adoc
@@ -1,11 +1,9 @@
-# Timer Component
+## Timer Component
The *timer:* component is used to generate message exchanges when a
timer fires You can only consume events from this endpoint.
-[[Timer-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------
@@ -32,9 +30,7 @@ link:how-do-i-specify-time-period-in-a-human-friendly-syntax.html[human
friendly syntax].
-[[Timer-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The Timer component has no options.
@@ -66,9 +62,7 @@ The Timer component supports 13 endpoint options which are listed below:
// endpoint options: END
-[[Timer-ExchangeProperties]]
-Exchange Properties
-^^^^^^^^^^^^^^^^^^^
+### Exchange Properties
When the timer is fired, it adds the following information as properties
to the `Exchange`:
@@ -88,9 +82,7 @@ to the `Exchange`:
|`Exchange.TIMER_COUNTER` |`Long` |*Camel 2.8:* The current fire counter. Starts from 1.
|=======================================================================
-[[Timer-Sample]]
-Sample
-^^^^^^
+### Sample
To set up a route that generates an event every 60 seconds:
@@ -115,13 +107,9 @@ And the route in Spring DSL:
</route>
-------------------------------------------------------------
-[[Timer-Firingassoonaspossible]]
-Firing as soon as possible
-++++++++++++++++++++++++++
+#### Firing as soon as possible
-[[Timer-AvailableasofCamel2.17]]
-Available as of Camel 2.17
-++++++++++++++++++++++++++
+#### Available as of Camel 2.17
You may want to fire messages in a Camel route as soon as possible you
can use a negative delay:
@@ -143,9 +131,7 @@ reached.
If you don't specify a repeatCount then the timer will continue firing
messages until the route will be stopped.�
-[[Timer-Firingonlyonce]]
-Firing only once
-++++++++++++++++
+#### Firing only once
*Available as of Camel 2.8*
@@ -160,14 +146,11 @@ starting the route. To do that you use the repeatCount option as shown:
</route>
-------------------------------------------------
-[[Timer-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:quartz.html[Quartz]
-
+* link:quartz.html[Quartz]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/tokenize-language.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/tokenize-language.adoc b/camel-core/src/main/docs/tokenize-language.adoc
index ee82fdf..a93b725 100644
--- a/camel-core/src/main/docs/tokenize-language.adoc
+++ b/camel-core/src/main/docs/tokenize-language.adoc
@@ -1,4 +1,4 @@
-# Tokenize Language
+## Tokenize Language
The tokenizer language is a built-in language in camel-core, which is
most often used only with the link:splitter.html[Splitter] EIP to split
@@ -11,9 +11,7 @@ language is recommended�as it offers a faster, more efficient
tokenization specifically for XML documents.�For more details
see�link:splitter.html[Splitter].
-[[Tokenize-Options]]
-Tokenize Options
-^^^^^^^^^^^^^^^^
+### Tokenize Options
// language options: START
The Tokenize language supports 10 options which are listed below.
@@ -36,4 +34,4 @@ The Tokenize language supports 10 options which are listed below.
| trim | true | Boolean | Whether to trim the value to remove leading and trailing whitespaces and line breaks
|=======================================================================
{% endraw %}
-// language options: END
+// language options: END
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/validator-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/validator-component.adoc b/camel-core/src/main/docs/validator-component.adoc
index 1ba29d0..70af5af 100644
--- a/camel-core/src/main/docs/validator-component.adoc
+++ b/camel-core/src/main/docs/validator-component.adoc
@@ -1,4 +1,4 @@
-# Validator Component
+## Validator Component
The Validation component performs XML validation of the message body
using the JAXP Validation API and based on any of the supported XML
@@ -15,9 +15,7 @@ Syntax]
The link:msv.html[MSV] component also supports
http://relaxng.org/[RelaxNG XML Syntax].
-[[Validation-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------------------
@@ -49,9 +47,7 @@ for this component when using *Camel 2.8* or older:
From Camel 2.9 onwards the link:validation.html[Validation] component is
provided directly in the camel-core.
-[[Validation-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The Validator component supports 1 options which are listed below.
@@ -92,9 +88,7 @@ The Validator component supports 12 endpoint options which are listed below:
// endpoint options: END
-[[Validation-Example]]
-Example
-^^^^^^^
+### Example
The following
http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/component/validator/camelContext.xml[example]
@@ -103,9 +97,7 @@ goes to one of two endpoints, either *mock:valid* or *mock:invalid*
based on whether or not the XML matches the given schema (which is
supplied on the classpath).
-[[Validation-Advanced:JMXmethodclearCachedSchema]]
-Advanced: JMX method clearCachedSchema
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Advanced: JMX method clearCachedSchema
Since *Camel 2.17*, you can force that the cached schema in the
validator endpoint is cleared and reread with the next process call with
@@ -113,12 +105,9 @@ the JMX operation�`clearCachedSchema. `You can also use this method to
programmatically clear the cache. This method is available on the
`ValidatorEndpoint `class`.`
-[[Validation-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/camel-core/src/main/docs/vm-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/vm-component.adoc b/camel-core/src/main/docs/vm-component.adoc
index 61bc85e..af20a7a 100644
--- a/camel-core/src/main/docs/vm-component.adoc
+++ b/camel-core/src/main/docs/vm-component.adoc
@@ -1,4 +1,4 @@
-# VM Component
+## VM Component
The *vm:* component provides asynchronous
http://www.eecs.harvard.edu/~mdw/proj/seda/[SEDA] behavior, exchanging
@@ -13,9 +13,7 @@ this mechanism to communicate across web applications (provided that
VM is an extension to the link:seda.html[Seda] component.
-[[VM-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------
@@ -58,9 +56,7 @@ from("direct:foo").to("vm:bar");
from("vm:bar?concurrentConsumers=5").to("file://output");
---------------------------------------------------------
-[[VM-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The VM component supports 3 options which are listed below.
@@ -111,9 +107,7 @@ The VM component supports 17 endpoint options which are listed below:
See the link:seda.html[Seda] component for options and other important
usage details as the same rules apply to the link:vm.html[Vm] component.
-[[VM-Samples]]
-Samples
-^^^^^^^
+### Samples
In the route below we send exchanges across CamelContext instances to a
VM queue named `order.email`:
@@ -131,13 +125,10 @@ deployed in another `.war` application):
from("vm:order.email").bean(MyOrderEmailSender.class);
------------------------------------------------------
-[[VM-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:seda.html[Seda]
-
+* link:seda.html[Seda]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/xpath-language.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/xpath-language.adoc b/camel-core/src/main/docs/xpath-language.adoc
index bf86be9..20e0cd3 100644
--- a/camel-core/src/main/docs/xpath-language.adoc
+++ b/camel-core/src/main/docs/xpath-language.adoc
@@ -1,4 +1,4 @@
-# XPath Language
+## XPath Language
Camel supports http://www.w3.org/TR/xpath[XPath] to allow an
link:expression.html[Expression] or link:predicate.html[Predicate] to be
@@ -33,9 +33,7 @@ from("queue:foo").
otherwise().to("queue:others");
-------------------------------------------
-[[XPath-Options]]
-XPath Language options
-^^^^^^^^^^^^^^^^^^^^^^
+### XPath Language options
// language options: START
The XPath language supports 8 options which are listed below.
@@ -58,16 +56,12 @@ The XPath language supports 8 options which are listed below.
{% endraw %}
// language options: END
-[[XPath-Namespaces]]
-Namespaces
-^^^^^^^^^^
+### Namespaces
You can easily use namespaces with XPath expressions using the
Namespaces helper class.
-[[XPath-Variables]]
-Variables
-^^^^^^^^^
+### Variables
Variables in XPath is defined in different namespaces. The default
namespace is `http://camel.apache.org/schema/spring`.
@@ -94,18 +88,14 @@ Camel will resolve variables according to either:
* namespace given
* no namespace given
-[[XPath-Namespacegiven]]
-Namespace given
-+++++++++++++++
+#### Namespace given
If the namespace is given then Camel is instructed exactly what to
return. However when resolving either *in* or *out* Camel will try to
resolve a header with the given local part first, and return it. If the
local part has the value *body* then the body is returned instead.
-[[XPath-Nonamespacegiven]]
-No namespace given
-++++++++++++++++++
+#### No namespace given
If there is no namespace given then Camel resolves only based on the
local part. Camel will try to resolve a variable in the following steps:
@@ -115,9 +105,7 @@ fluent builder
* from message.in.header if there is a header with the given key
* from exchange.properties if there is a property with the given key
-[[XPath-Functions]]
-Functions
-^^^^^^^^^
+### Functions
Camel adds the following XPath functions that can be used to access the
exchange:
@@ -148,9 +136,7 @@ Here's an example showing some of these functions in use.
And the new functions introduced in Camel 2.5:
-[[XPath-UsingXMLconfiguration]]
-Using XML configuration
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using XML configuration
If you prefer to configure your routes in your link:spring.html[Spring]
XML file then you can use XPath expressions as follows
@@ -182,9 +168,7 @@ See also this
http://camel.465427.n5.nabble.com/fail-filter-XPATH-camel-td476424.html[discussion
on the mailinglist] about using your own namespaces with xpath
-[[XPath-Settingresulttype]]
-Setting result type
-^^^^^^^^^^^^^^^^^^^
+### Setting result type
The link:xpath.html[XPath] expression will return a result type using
native XML objects such as `org.w3c.dom.NodeList`. But many times you
@@ -218,9 +202,7 @@ Where we use the xpath function concat to prefix the order name with
`foo-`. In this case we have to specify that we want a String as result
type so the concat function works.
-[[XPath-UsingXPathonHeaders]]
-Using XPath on Headers
-^^^^^^^^^^^^^^^^^^^^^^
+### Using XPath on Headers
*Available as of Camel 2.11*
@@ -237,9 +219,7 @@ shown:
xpath("/invoice/@orderType = 'premium'", "invoiceDetails")
------------------------------------------------------------
-[[XPath-Examples]]
-Examples
-^^^^^^^^
+### Examples
Here is a simple
http://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/XPathFilterTest.java[example]
@@ -260,9 +240,7 @@ which values is *Kong*. +
And the spring XML equivalent of the route:
-[[XPath-XPathinjection]]
-XPath injection
-~~~~~~~~~~~~~~~
+### XPath injection
You can use link:bean-integration.html[Bean Integration] to invoke a
method on a bean and use various languages such as XPath to extract a
@@ -293,9 +271,7 @@ public class Foo {
}
----------------------------------------------------------------------------------------------------------
-[[XPath-UsingXPathBuilderwithoutanExchange]]
-Using XPathBuilder without an Exchange
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using XPathBuilder without an Exchange
*Available as of Camel 2.3*
@@ -335,9 +311,7 @@ do it a bit simpler:
String name = XPathBuilder.xpath("foo/bar").evaluate(context, "<foo><bar>cheese</bar></foo>");
--------------------------------------------------------------------------------------------------
-[[XPath-UsingSaxonwithXPathBuilder]]
-Using Saxon with XPathBuilder
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using Saxon with XPathBuilder
*Available as of Camel 2.3*
@@ -353,9 +327,7 @@ Using ObjectModel
The easy one
-[[XPath-SettingacustomXPathFactoryusingSystemProperty]]
-Setting a custom XPathFactory using System Property
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting a custom XPathFactory using System Property
*Available as of Camel 2.3*
@@ -382,9 +354,7 @@ To use Apache Xerces you can configure the system property
-Djavax.xml.xpath.XPathFactory=org.apache.xpath.jaxp.XPathFactoryImpl
---------------------------------------------------------------------
-[[XPath-EnablingSaxonfromSpringDSL]]
-Enabling Saxon from Spring DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling Saxon from Spring DSL
*Available as of Camel 2.10*
@@ -412,9 +382,7 @@ Shortcut
<xpath saxon="true" resultType="java.lang.String">current-dateTime()</xpath>
----------------------------------------------------------------------------
-[[XPath-Namespaceauditingtoaiddebugging]]
-Namespace auditing to aid debugging
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Namespace auditing to aid debugging
*Available as of Camel 2.10*
@@ -435,9 +403,7 @@ Therefore, the utmost we can do is assist you in debugging such issues
by adding two new features to the XPath Expression Language and are thus
accesible from both predicates and expressions.
-[[XPath-LoggingtheNamespaceContextofyourXPathexpressionpredicate]]
-Logging the Namespace Context of your XPath expression/predicate
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Logging the Namespace Context of your XPath expression/predicate
Every time a new XPath expression is created in the internal pool, Camel
will log the namespace context of the expression under the
@@ -460,9 +426,7 @@ logger such as `org.apache.camel` or the root logger
link:xpath.html[Auditing Namespaces], in which case the logging will
occur on the INFO level
-[[XPath-Auditingnamespaces]]
-Auditing namespaces
-+++++++++++++++++++
+#### Auditing namespaces
Camel is able to discover and dump all namespaces present on every
incoming message before evaluating an XPath expression, providing all
@@ -512,9 +476,7 @@ the following:
xmlns:b=[http://apache.org/camelA, http://apache.org/camelB]}
--------------------------------------------------------------------------------------------------
-[[XPath-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -528,8 +490,6 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").xpath("resource:classpath:myxpath.txt", String.class)
----------------------------------------------------------------------------
-[[XPath-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
-The XPath language is part of camel-core.
+The XPath language is part of camel-core.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/xslt-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/xslt-component.adoc b/camel-core/src/main/docs/xslt-component.adoc
index 30e171d..fb9c48b 100644
--- a/camel-core/src/main/docs/xslt-component.adoc
+++ b/camel-core/src/main/docs/xslt-component.adoc
@@ -1,12 +1,10 @@
-# XSLT Component
+## XSLT Component
The *xslt:* component allows you to process a message using an
http://www.w3.org/TR/xslt[XSLT] template. This can be ideal when using
link:templating.html[Templating] to generate respopnses for requests.
-[[XSLT-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------
@@ -64,9 +62,7 @@ for this component when using *Camel 2.8* or older:
From Camel 2.9 onwards the link:xslt.html[XSLT] component is provided
directly in the camel-core.
-[[XSLT-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The XSLT component supports 5 options which are listed below.
@@ -116,9 +112,7 @@ The XSLT component supports 17 endpoint options which are listed below:
// endpoint options: END
-[[XSLT-UsingXSLTendpoints]]
-Using XSLT endpoints
-^^^^^^^^^^^^^^^^^^^^
+### Using XSLT endpoints
For example you could use something like
@@ -141,9 +135,7 @@ from("activemq:My.Queue").
to("activemq:Another.Queue");
--------------------------------------
-[[XSLT-GettingParametersintotheXSLTtoworkwith]]
-Getting Parameters into the XSLT to work with
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Getting Parameters into the XSLT to work with
By default, all headers are added as parameters which are available in
the XSLT. +
@@ -168,9 +160,7 @@ available:
<xsl:template ...>
------------------------------
-[[XSLT-SpringXMLversions]]
-Spring XML versions
-^^^^^^^^^^^^^^^^^^^
+### Spring XML versions
To use the above examples in Spring XML you would use something like
@@ -191,9 +181,7 @@ case] along with
http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/spring/processor/XsltTest-context.xml[its
Spring XML] if you want a concrete example.
-[[XSLT-Usingxsl:include]]
-Using xsl:include
-^^^^^^^^^^^^^^^^^
+### Using xsl:include
*Camel 2.2 or older* +
If you use xsl:include in your XSL files then in Camel 2.2 or older it
@@ -251,9 +239,7 @@ You can also refer back in the paths such as
Which then will resolve the xsl file under `org/apache/camel/component`.
-[[XSLT-Usingxsl:includeanddefaultprefix]]
-Using xsl:include and default prefix
-++++++++++++++++++++++++++++++++++++
+#### Using xsl:include and default prefix
When using xsl:include such as:
@@ -294,9 +280,7 @@ the endpoint was configured with "file:" as prefix. +
match. And have both file and classpath loading. But that would be
unusual, as most people either use file or classpath based resources.
-[[XSLT-UsingSaxonextensionfunctions]]
-Using Saxon extension functions
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using Saxon extension functions
Since Saxon 9.2, writing extension functions has been supplemented by a
new mechanism, referred to
@@ -345,9 +329,7 @@ Spring example:
�
-[[XSLT-Dynamicstylesheets]]
-Dynamic stylesheets
-^^^^^^^^^^^^^^^^^^^
+### Dynamic stylesheets
To provide a dynamic stylesheet at runtime you can define a dynamic URI.
See�link:how-to-use-a-dynamic-uri-in-to.html[How to use a dynamic URI in
@@ -358,9 +340,7 @@ to()] for more information.
define a stylesheet to use instead of what is configured on the endpoint
URI. This allows you to provide a dynamic stylesheet at runtime.
-[[XSLT-Accessingwarnings,errorsandfatalErrorsfromXSLTErrorListener]]
-Accessing warnings, errors and fatalErrors from XSLT ErrorListener
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Accessing warnings, errors and fatalErrors from XSLT ErrorListener
*Available as of Camel 2.14*
@@ -396,9 +376,7 @@ that contains the message in the `getMessage()` method on the exception.
The exception is stored on the Exchange as a warning with the
key�`Exchange.XSLT_WARNING.`
-[[XSLT-NotesonusingXSLTandJavaVersions]]
-Notes on using XSLT and Java Versions
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Notes on using XSLT and Java Versions
Here are some observations from Sameer, a Camel user, which he kindly
shared with us:
@@ -439,12 +417,9 @@ for the jvm or as specified by the container.
Hope this post saves newbie Camel riders some time.
________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
-[[XSLT-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/camel-core/src/main/docs/xtokenize-language.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/xtokenize-language.adoc b/camel-core/src/main/docs/xtokenize-language.adoc
index b1f1761..e27d9b7 100644
--- a/camel-core/src/main/docs/xtokenize-language.adoc
+++ b/camel-core/src/main/docs/xtokenize-language.adoc
@@ -1,4 +1,4 @@
-# XML Tokenize Language
+## XML Tokenize Language
The xml tokenizer language is a built-in language in camel-core, which
is a truly XML-aware tokenizer that can be used with the Splitter as the
@@ -10,9 +10,7 @@ Tokenizer.�
For more details see link:splitter.html[Splitter].
-[[XMLTokenizer-Options]]
-XML Tokenizer Options
-^^^^^^^^^^^^^^^^^^^^^
+### XML Tokenizer Options
// language options: START
The XML Tokenize language supports 4 options which are listed below.
@@ -29,4 +27,4 @@ The XML Tokenize language supports 4 options which are listed below.
| trim | true | Boolean | Whether to trim the value to remove leading and trailing whitespaces and line breaks
|=======================================================================
{% endraw %}
-// language options: END
+// language options: END
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/zip-dataformat.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/zip-dataformat.adoc b/camel-core/src/main/docs/zip-dataformat.adoc
index 9a400ca..ba85881 100644
--- a/camel-core/src/main/docs/zip-dataformat.adoc
+++ b/camel-core/src/main/docs/zip-dataformat.adoc
@@ -1,4 +1,4 @@
-# Zip Deflate Compression DataFormat
+## Zip Deflate Compression DataFormat
The Zip link:data-format.html[Data Format] is a message compression and
de-compression format. Messages marshalled using Zip compression can be
@@ -14,9 +14,7 @@ Which means that when using big files, the entire file content is loaded
into memory. This is subject to change in the future, to allow a streaming based
solution to have a low memory footprint.
-[[ZipDataFormat-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The Zip Deflate Compression dataformat supports 2 options which are listed below.
@@ -33,9 +31,7 @@ The Zip Deflate Compression dataformat supports 2 options which are listed below
{% endraw %}
// dataformat options: END
-[[ZipDataFormat-Marshal]]
-Marshal
-^^^^^^^
+### Marshal
In this example we marshal a regular text/XML payload to a compressed
payload employing zip compression `Deflater.BEST_COMPRESSION` and send
@@ -54,9 +50,7 @@ send it as
from("direct:start").marshal().zip().to("activemq:queue:MY_QUEUE");
-------------------------------------------------------------------
-[[ZipDataFormat-Unmarshal]]
-Unmarshal
-^^^^^^^^^
+### Unmarshal
In this example we unmarshal�a zipped�payload from an ActiveMQ queue
called MY_QUEUE�to its original format,�and forward it for�processing�to
@@ -69,9 +63,7 @@ unmarshalling to avoid errors.
from("activemq:queue:MY_QUEUE").unmarshal().zip().process(new UnZippedMessageProcessor());�
-------------------------------------------------------------------------------------------
-[[ZipDataFormat-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
This data format is provided in *camel-core* so no additional
-dependencies are needed.
+dependencies are needed.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc b/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
index c35e7f1..019fa5d 100644
--- a/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
+++ b/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc
@@ -1,4 +1,4 @@
-# AHC Websocket Component
+## AHC Websocket Component
*Available as of Camel 2.14*
@@ -23,9 +23,7 @@ their�`pom.xml`�for this component:
</dependency>
------------------------------------------------------------
-[[AHC-WS-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
-------------------------------------------------
@@ -35,9 +33,7 @@ ahc-wss://hostname[:port][/resourceUri][?options]
Will by default use port 80 for ahc-ws and 443 for ahc-wss.
-[[AHC-WS-AHC-WSOptions]]
-AHC-WS Options
-^^^^^^^^^^^^^^
+### AHC-WS Options
As the AHC-WS component is based on the AHC component, you can use the
various configuration options of the AHC component.
@@ -97,17 +93,13 @@ The AHC Websocket component supports 19 endpoint options which are listed below:
// endpoint options: END
-[[AHC-WS-WritingandReadingDataoverWebsocket]]
-Writing and Reading Data over Websocket
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Writing and Reading Data over Websocket
An ahc-ws endpoint can either write data to the socket or read from the
socket, depending on whether the endpoint is configured as the producer
or the consumer, respectively.
-[[AHC-WS-ConfiguringURItoWriteorReadData]]
-Configuring URI to Write or Read Data
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring URI to Write or Read Data
In the route below, Camel will write to the specified websocket
connection.
@@ -153,9 +145,7 @@ And the equivalent Spring sample:
�
-[[AHC-WS-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -163,5 +153,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:../../../../camel-ahc/src/main/docs/readme.html[AHC]
-* link:atmosphere-websocket.html[Atmosphere-Websocket]
-
+* link:atmosphere-websocket.html[Atmosphere-Websocket]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ahc/src/main/docs/ahc-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ahc/src/main/docs/ahc-component.adoc b/components/camel-ahc/src/main/docs/ahc-component.adoc
index e9e97d7..72369c9 100644
--- a/components/camel-ahc/src/main/docs/ahc-component.adoc
+++ b/components/camel-ahc/src/main/docs/ahc-component.adoc
@@ -1,4 +1,4 @@
-# AHC Component
+## AHC Component
*Available as of Camel 2.8*
@@ -22,9 +22,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[AHC-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------------------
@@ -37,9 +35,7 @@ Will by default use port 80 for HTTP and 443 for HTTPS.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[AHC-AhcEndpointOptions]]
-AhcEndpoint Options
-^^^^^^^^^^^^^^^^^^^
+### AhcEndpoint Options
@@ -79,9 +75,7 @@ The AHC component supports 14 endpoint options which are listed below:
-[[AHC-AhcComponentOptions]]
-AhcComponent Options
-^^^^^^^^^^^^^^^^^^^^
+### AhcComponent Options
@@ -124,9 +118,7 @@ propagate those options to
configure/override a custom option. Options set on endpoints will always
take precedence over options from the `AhcComponent`.
-[[AHC-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -152,18 +144,14 @@ a content type, such as `text/html`.
provide a content encoding, such as `gzip`.
|=======================================================================
-[[AHC-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
Camel will store the HTTP response from the external server on the OUT
body. All headers from the IN message will be copied to the OUT message,
so headers are preserved during routing. Additionally Camel will add the
HTTP response headers as well to the OUT message headers.
-[[AHC-Responsecode]]
-Response code
-^^^^^^^^^^^^^
+### Response code
Camel will handle according to the HTTP response code:
@@ -181,9 +169,7 @@ The option, `throwExceptionOnFailure`, can be set to `false` to prevent
the `AhcOperationFailedException` from being thrown for failed response
codes. This allows you to get any response from the remote server.
-[[AHC-AhcOperationFailedException]]
-AhcOperationFailedException
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### AhcOperationFailedException
This exception contains the following information:
@@ -193,9 +179,7 @@ This exception contains the following information:
* Response body as a `java.lang.String`, if server provided a body as
response
-[[AHC-CallingusingGETorPOST]]
-Calling using GET or POST
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Calling using GET or POST
The following algorithm is used to determine if either `GET` or `POST`
HTTP method should be used: +
@@ -205,9 +189,7 @@ HTTP method should be used: +
4. `POST` if there is data to send (body is not null). +
5. `GET` otherwise.
-[[AHC-ConfiguringURItocall]]
-Configuring URI to call
-^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring URI to call
You can set the HTTP producer's URI directly form the endpoint URI. In
the route below, Camel will call out to the external server, `oldhost`,
@@ -241,9 +223,7 @@ from("direct:start")
.to("ahc:http://oldhost");
-------------------------------------------------------------
-[[AHC-ConfiguringURIParameters]]
-Configuring URI Parameters
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring URI Parameters
The *ahc* producer supports URI parameters to be sent to the HTTP
server. The URI parameters can either be set directly on the endpoint
@@ -264,9 +244,7 @@ from("direct:start")
.to("ahc:http://oldhost");
-------------------------------------------------------------------------------
-[[AHC-HowtosetthehttpmethodtotheHTTPproducer]]
-How to set the http method to the HTTP producer
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to set the http method to the HTTP producer
The HTTP component provides a way to set the HTTP request method by
setting the message header. Here is an example;
@@ -295,9 +273,7 @@ And the equivalent Spring sample:
</camelContext>
---------------------------------------------------------------------
-[[AHC-Configuringcharset]]
-Configuring charset
-^^^^^^^^^^^^^^^^^^^
+### Configuring charset
If you are using `POST` to send data you can configure the `charset`
using the `Exchange` property:
@@ -307,9 +283,7 @@ using the `Exchange` property:
exchange.setProperty(Exchange.CHARSET_NAME, "iso-8859-1");
----------------------------------------------------------
-[[AHC-URIParametersfromtheendpointURI]]
-URI Parameters from the endpoint URI
-++++++++++++++++++++++++++++++++++++
+#### URI Parameters from the endpoint URI
In this sample we have the complete URI endpoint that is just what you
would have typed in a web browser. Multiple URI parameters can of course
@@ -322,9 +296,7 @@ web browser. Camel does no tricks here.
template.sendBody("ahc:http://www.google.com/search?q=Camel", null);
--------------------------------------------------------------------
-[[AHC-URIParametersfromtheMessage]]
-URI Parameters from the Message
-+++++++++++++++++++++++++++++++
+#### URI Parameters from the Message
[source,java]
---------------------------------------------------------------------
@@ -337,9 +309,7 @@ template.sendBody("ahc:http://www.google.com/search", null, headers);
In the header value above notice that it should *not* be prefixed with
`?` and you can separate parameters as usual with the `&` char.
-[[AHC-GettingtheResponseCode]]
-Getting the Response Code
-+++++++++++++++++++++++++
+#### Getting the Response Code
You can get the HTTP response code from the AHC component by getting the
value from the Out message header with `Exchange.HTTP_RESPONSE_CODE`.
@@ -355,9 +325,7 @@ Exchange exchange = template.send("ahc:http://www.google.com/search", new Proces
int responseCode = out.getHeader(Exchange.HTTP_RESPONSE_CODE, Integer.class);
----------------------------------------------------------------------------------------------
-[[AHC-ConfiguringAsyncHttpClient]]
-Configuring AsyncHttpClient
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring AsyncHttpClient
The `AsyncHttpClient` client uses a `AsyncHttpClientConfig` to configure
the client. See the documentation at +
@@ -399,9 +367,7 @@ from("direct:start")
.to("ahc:http://localhost:8080/foo?clientConfig.maxRequestRetry=3&clientConfig.followRedirects=true")
---------------------------------------------------------------------------------------------------------
-[[AHC-SSLSupport]]
-SSL Support (HTTPS)
-^^^^^^^^^^^^^^^^^^^
+### SSL Support (HTTPS)
[[AHC-UsingtheJSSEConfigurationUtility]]
Using the JSSE Configuration Utility
@@ -453,9 +419,7 @@ Spring DSL based configuration of endpoint
...
----------------------------------------------------------------------------------
-[[AHC-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -464,5 +428,4 @@ See Also
* link:jetty.html[Jetty]
* link:http.html[HTTP]
-* link:http4.html[HTTP4]
-
+* link:http4.html[HTTP4]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-amqp/src/main/docs/amqp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-amqp/src/main/docs/amqp-component.adoc b/components/camel-amqp/src/main/docs/amqp-component.adoc
index 5b34c67..ea76541 100644
--- a/components/camel-amqp/src/main/docs/amqp-component.adoc
+++ b/components/camel-amqp/src/main/docs/amqp-component.adoc
@@ -1,4 +1,4 @@
-# AMQP Component
+## AMQP Component
The *amqp:* component supports the http://www.amqp.org/[AMQP 1.0
protocol] using the JMS Client API of the http://qpid.apache.org/[Qpid]
@@ -20,18 +20,14 @@ for this component:
</dependency>
------------------------------------------------------------------------------------------------
-[[AMQP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------------
amqp:[queue:|topic:]destinationName[?options]
---------------------------------------------
-[[AMQP-AMQPOptions]]
-AMQP Options
-^^^^^^^^^^^^
+### AMQP Options
You can specify all of the various configuration options of the
link:../../../../camel-jms/src/main/docs/readme.html[JMS] component after the destination name.
@@ -232,9 +228,7 @@ The AMQP component supports 86 endpoint options which are listed below:
-[[AMQP-Usage]]
-Usage
-^^^^^
+### Usage
As AMQP component is inherited from JMS component, the usage of the
former is almost identical to the latter:
@@ -252,9 +246,7 @@ from(...).
to("amqp:topic:notify");
------------------------------------
-[[AMQP-ConfiguringAMQPcomponent]]
-Configuring AMQP component
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring AMQP component
Starting from the Camel 2.16.1 you can also use the
`AMQPComponent#amqp10Component(String connectionURI)` factory method to
@@ -338,9 +330,7 @@ AMQPConnectionDetails amqpConnection() {
}
-----------------------------------------------
-[[AMQP-Usingtopics]]
-Using topics
-^^^^^^^^^^^^
+### Using topics
To have using topics working with�`camel-amqp`�you need to configure the
component to use�`topic://`�as topic prefix, as shown below:
@@ -361,12 +351,9 @@ Keep in mind that both��`AMQPComponent#amqpComponent()`�methods and
`AMQPConnectionDetails` pre-configure the component with the topic
prefix, so you don't have to configure it explicitly.
-[[AMQP-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-apns/src/main/docs/apns-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-apns/src/main/docs/apns-component.adoc b/components/camel-apns/src/main/docs/apns-component.adoc
index 09a1a32..0d9c4b0 100644
--- a/components/camel-apns/src/main/docs/apns-component.adoc
+++ b/components/camel-apns/src/main/docs/apns-component.adoc
@@ -1,4 +1,4 @@
-# APNS Component
+## APNS Component
*Available as of Camel 2.8*
@@ -30,9 +30,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[APNS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
To send notifications:
@@ -48,9 +46,7 @@ To consume feedback:
apns:consumer[?options]
-----------------------
-[[APNS-Options]]
-Options
-^^^^^^^
+### Options
@@ -107,9 +103,7 @@ The APNS component supports 21 endpoint options which are listed below:
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[APNS-Component]]
-Component
-+++++++++
+#### Component
The `ApnsComponent` must be configured with a
`com.notnoop.apns.ApnsService`. The service can be created and
@@ -119,18 +113,14 @@ further below for an example. And as well in the
https://svn.apache.org/repos/asf/camel/trunk/components/camel-apns/[test
source code].
-[[APNS-Exchangedataformat]]
-Exchange data format
-^^^^^^^^^^^^^^^^^^^^
+### Exchange data format
When Camel will fetch feedback data corresponding to inactive devices,
it will retrieve a List of InactiveDevice objects. Each InactiveDevice
object of the retrieved list will be setted as the In body, and then
processed by the consumer endpoint.
-[[APNS-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Camel Apns uses these headers.
@@ -145,9 +135,7 @@ onwards APNS_NOTIFICATION is used for sending message body as
com.notnoop.apns.ApnsNotification types.
|=======================================================================
-[[APNS-ApnsServiceFactorybuildercallback]]
-ApnsServiceFactory builder callback
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### ApnsServiceFactory builder callback
`ApnsServiceFactory` comes with the empty callback method that could be
used to configure (or even replace) the default `ApnsServiceBuilder`
@@ -172,13 +160,9 @@ ApnsServiceFactory proxiedApnsServiceFactory = new ApnsServiceFactory(){
};
-------------------------------------------------------------------------------------------
-[[APNS-Samples]]
-Samples
-^^^^^^^
+### Samples
-[[APNS-CamelXmlroute]]
-Camel Xml route
-+++++++++++++++
+#### Camel Xml route
[source,xml]
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -234,9 +218,7 @@ Camel Xml route
</beans>
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[APNS-CamelJavaroute]]
-Camel Java route
-++++++++++++++++
+#### Camel Java route
[[APNS-Createcamelcontextanddeclareapnscomponentprogrammatically]]
Create camel context and declare apns component programmatically
@@ -301,13 +283,10 @@ from("apns:consumer?initialDelay=10&delay=3600&timeUnit=SECONDS")
.to("mock:result");
--------------------------------------------------------------------------
-[[APNS-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* http://camel.apache.org/component.html[Component]
* http://camel.apache.org/endpoint.html[Endpoint]
*
http://blog.xebia.fr/2010/09/30/creer-un-composant-apache-camel-de-connexion-a-lapns-1-sur-3/[Blog
-about using APNS (in french)]
-
+about using APNS (in french)]
\ No newline at end of file
[04/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-quartz2/src/main/docs/quartz2-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-quartz2/src/main/docs/quartz2-component.adoc b/components/camel-quartz2/src/main/docs/quartz2-component.adoc
index 2ad143b..71a3e1e 100644
--- a/components/camel-quartz2/src/main/docs/quartz2-component.adoc
+++ b/components/camel-quartz2/src/main/docs/quartz2-component.adoc
@@ -1,4 +1,4 @@
-# Quartz2 Component
+## Quartz2 Component
*Available as of Camel 2.12.0*
@@ -24,9 +24,7 @@ for this component:
remain on old Quartz 1.x, please +
use the old link:quartz.html[Quartz] component instead.
-[[Quartz2-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------------
@@ -44,9 +42,7 @@ name.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Quartz2-Options]]
-Options
-^^^^^^^
+### Options
@@ -130,9 +126,7 @@ to the <camelContext> that this id is unique, as this is
required by the `QuartzScheduler` in the OSGi container. If you do not
set any `id` on <camelContext> then a unique id is auto assigned, and there is no problem.
-[[Quartz2-Configuringquartz.propertiesfile]]
-Configuring quartz.properties file
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring quartz.properties file
By default Quartz will look for a `quartz.properties` file in the
`org/quartz` directory of the classpath. If you are using WAR
@@ -160,9 +154,7 @@ To do this you can configure this in Spring XML as follows
</bean>
-------------------------------------------------------------------------------
-[[Quartz2-EnablingQuartzschedulerinJMX]]
-Enabling Quartz scheduler in JMX
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling Quartz scheduler in JMX
You need to configure the quartz scheduler properties to enable JMX. +
That is typically setting the option
@@ -172,9 +164,7 @@ configuration file.
From Camel 2.13 onwards Camel will automatic set this option to true,
unless explicit disabled.
-[[Quartz2-StartingtheQuartzscheduler]]
-Starting the Quartz scheduler
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Starting the Quartz scheduler
The link:quartz2.html[Quartz2] component offers an option to let the
Quartz scheduler be started delayed, or not auto started at all.
@@ -188,9 +178,7 @@ This is an example:
</bean>
------------------------------------------------------------------------------
-[[Quartz2-Clustering]]
-Clustering
-^^^^^^^^^^
+### Clustering
If you use Quartz in clustered mode, e.g. the `JobStore` is clustered.
Then the link:quartz2.html[Quartz2] component will *not* pause/remove
@@ -200,9 +188,7 @@ to keep running on the other nodes in the cluster.
*Note*: When running in clustered node no checking is done to ensure
unique job name/group for endpoints.
-[[Quartz2-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Camel adds the getters from the Quartz Execution Context as header
values. The following headers are added: +
@@ -214,9 +200,7 @@ values. The following headers are added: +
The `fireTime` header contains the `java.util.Date` of when the exchange
was fired.
-[[Quartz2-UsingCronTriggers]]
-Using Cron Triggers
-^^^^^^^^^^^^^^^^^^^
+### Using Cron Triggers
Quartz supports
http://www.quartz-scheduler.org/documentation/quartz-2.x/tutorials/crontrigger[Cron-like
@@ -249,9 +233,7 @@ valid URI syntax:
|`+` | _Space_
|=======================================================================
-[[Quartz2-Specifyingtimezone]]
-Specifying time zone
-^^^^^^^^^^^^^^^^^^^^
+### Specifying time zone
The Quartz Scheduler allows you to configure time zone per trigger. For
example to use a timezone of your country, then you can do as follows:
@@ -263,9 +245,7 @@ quartz2://groupName/timerName?cron=0+0/5+12-18+?+*+MON-FRI&trigger.timeZone=Euro
The timeZone value is the values accepted by `java.util.TimeZone`.
-[[Quartz2-UsingQuartzScheduledPollConsumerScheduler]]
-Using QuartzScheduledPollConsumerScheduler
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using QuartzScheduledPollConsumerScheduler
The link:quartz2.html[Quartz2] component provides a
link:polling-consumer.html[Polling Consumer] scheduler which allows to
@@ -325,9 +305,7 @@ use the following as well:
.to("bean:process");
--------------------------------------------------------------------
-[[Quartz2-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -335,5 +313,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:quartz.html[Quartz]
-* link:timer.html[Timer]
-
+* link:timer.html[Timer]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-quickfix/src/main/docs/quickfix-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-quickfix/src/main/docs/quickfix-component.adoc b/components/camel-quickfix/src/main/docs/quickfix-component.adoc
index 7b09d03..aa0f021 100644
--- a/components/camel-quickfix/src/main/docs/quickfix-component.adoc
+++ b/components/camel-quickfix/src/main/docs/quickfix-component.adoc
@@ -1,8 +1,6 @@
-# QuickFix Component
+## QuickFix Component
[[ConfluenceContent]]
-[[Quickfix-QuickFIXJComponent]]
-QuickFIX/J Component
-~~~~~~~~~~~~~~~~~~~~
+### QuickFIX/J Component
The *quickfix* component adapts the
http://www.quickfixj.org/[QuickFIX/J] FIX engine for using in Camel .
@@ -32,9 +30,7 @@ for this component:
</dependency>
----
-[[Quickfix-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source]
----
@@ -69,9 +65,7 @@ quickfix:config.cfg?sessionID=FIX.4.2:MyTradingCompany->SomeExchange
quickfix:config.cfg?sessionID=FIX.4.2:MyTradingCompany->SomeExchange&lazyCreateEngine=true
----
-[[Quickfix-Endpoints]]
-Endpoints
-~~~~~~~~~
+### Endpoints
FIX sessions are endpoints for the *quickfix* component. An endpoint URI
may specify a single session or all sessions managed by a specific
@@ -87,9 +81,7 @@ include the session-related fields in the FIX message being sent. If a
session is specified in the URI then the component will automatically
inject the session-related fields into the FIX message.
-[[Quickfix-Options]]
-Options
-~~~~~~~
+### Options
// component options: START
The QuickFix component supports 5 options which are listed below.
@@ -127,9 +119,7 @@ The QuickFix component supports 7 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[Quickfix-ExchangeFormat]]
-Exchange Format
-^^^^^^^^^^^^^^^
+### Exchange Format
The exchange headers include information to help with exchange
filtering, routing and other processing. The following headers are
@@ -157,9 +147,7 @@ dictionary to parse certain types of messages (with repeating groups,
for example). By injecting a DataDictionary header in the route after
receiving a message string, the FIX engine can properly parse the data.
-[[Quickfix-QuickFIXJConfigurationExtensions]]
-QuickFIX/J Configuration Extensions
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### QuickFIX/J Configuration Extensions
When using QuickFIX/J directly, one typically writes code to create
instances of logging adapters, message stores and communication
@@ -174,9 +162,7 @@ QuickFIX/J configuration, see the
http://www.quickfixj.org/quickfixj/usermanual/usage/configuration.html[QFJ
user manual].
-[[Quickfix-CommunicationConnectors]]
-Communication Connectors
-++++++++++++++++++++++++
+#### Communication Connectors
When the component detects an initiator or acceptor session setting in
the QuickFIX/J configuration file it will automatically create the
@@ -205,9 +191,7 @@ and must be placed in the settings default section.
`ThreadedSocketAcceptor`
|=======================================================================
-[[Quickfix-Logging]]
-Logging
-+++++++
+#### Logging
The QuickFIX/J logger implementation can be specified by including the
following settings in the default section of the configuration file. The
@@ -234,9 +218,7 @@ will cause this log to be used.
|`JdbcDriver` |Use a `JdbcLog`
|=======================================================================
-[[Quickfix-MessageStore]]
-Message Store
-+++++++++++++
+#### Message Store
The QuickFIX/J message store implementation can be specified by
including the following settings in the default section of the
@@ -255,18 +237,14 @@ QuickFIX/J settings file.
|`SleepycatDatabaseDir` |Use a `SleepcatStore`
|=============================================
-[[Quickfix-MessageFactory]]
-Message Factory
-+++++++++++++++
+#### Message Factory
A message factory is used to construct domain objects from raw FIX
messages. The default message factory is `DefaultMessageFactory`.
However, advanced applications may require a custom message factory.
This can be set on the QuickFIX/J component.
-[[Quickfix-JMX]]
-JMX
-+++
+#### JMX
[width="100%",cols="10%,90%",options="header",]
|============================================
@@ -274,9 +252,7 @@ JMX
|`UseJmx` |if `Y`, then enable QuickFIX/J JMX
|============================================
-[[Quickfix-OtherDefaults]]
-Other Defaults
-++++++++++++++
+#### Other Defaults
The component provides some default settings for what are normally
required settings in QuickFIX/J configuration files. `SessionStartTime`
@@ -284,9 +260,7 @@ and `SessionEndTime` default to "00:00:00", meaning the session will not
be automatically started and stopped. The `HeartBtInt` (heartbeat
interval) defaults to 30 seconds.
-[[Quickfix-MinimalInitiatorConfigurationExample]]
-Minimal Initiator Configuration Example
-+++++++++++++++++++++++++++++++++++++++
+#### Minimal Initiator Configuration Example
[source]
----
@@ -297,9 +271,7 @@ SenderCompID=YOUR_SENDER
TargetCompID=YOUR_TARGET
----
-[[Quickfix-UsingtheInOutMessageExchangePattern]]
-Using the InOut Message Exchange Pattern
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the InOut Message Exchange Pattern
*Camel 2.8+*
@@ -311,9 +283,7 @@ be a single request message and single reply message to the request.
Examples include an
OrderStatusRequest message and UserRequest.
-[[Quickfix-ImplementingInOutExchangesforConsumers]]
-Implementing InOut Exchanges for Consumers
-++++++++++++++++++++++++++++++++++++++++++
+#### Implementing InOut Exchanges for Consumers
Add "exchangePattern=InOut" to the QuickFIX/J enpoint URI. The
`MessageOrderStatusService` in
@@ -329,9 +299,7 @@ to the requestor session.
.bean(new MarketOrderStatusService());
----
-[[Quickfix-ImplementingInOutExchangesforProducers]]
-Implementing InOut Exchanges for Producers
-++++++++++++++++++++++++++++++++++++++++++
+#### Implementing InOut Exchanges for Producers
For producers, sending a message will block until a reply is received or
a timeout occurs. There
@@ -367,9 +335,7 @@ exchange.setProperty(QuickfixjProducer.CORRELATION_CRITERIA_KEY,
.withField(OrderID.FIELD, request.getString(OrderID.FIELD)));
----
-[[Quickfix-Example]]
-Example
-+++++++
+#### Example
The source code contains an example called `RequestReplyExample` that
demonstrates the InOut exchanges
@@ -385,9 +351,7 @@ provided as the web response.
The Spring configuration have changed from Camel 2.9 onwards. See
further below for example.
-[[Quickfix-SpringConfiguration]]
-Spring Configuration
-^^^^^^^^^^^^^^^^^^^^
+### Spring Configuration
*Camel 2.6 - 2.8.x*
@@ -462,9 +426,7 @@ settings for both sessions.
include::../../test/resources/org/apache/camel/component/quickfixj/QuickfixjSpringTest-context.xml[tags=e1]
----
-[[Quickfix-Exceptionhandling]]
-Exception handling
-^^^^^^^^^^^^^^^^^^
+### Exception handling
QuickFIX/J behavior can be modified if certain exceptions are thrown
during processing of a message. If a `RejectLogon` exception is thrown
@@ -481,9 +443,7 @@ being processed __synchronously__. If it is processed asynchronously (on
another thread), the FIX engine will immediately send the unmodified
outgoing message when it's callback method returns.
-[[Quickfix-FIXSequenceNumberManagement]]
-FIX Sequence Number Management
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### FIX Sequence Number Management
If an application exception is thrown during _synchronous_ exchange
processing, this will cause QuickFIX/J to not increment incoming FIX
@@ -508,9 +468,7 @@ sending messages.
See the FIX protocol specifications and the QuickFIX/J documentation for
more details about FIX sequence number management.
-[[Quickfix-RouteExamples]]
-Route Examples
-^^^^^^^^^^^^^^
+### Route Examples
Several examples are included in the QuickFIX/J component source code
(test subdirectories). One of these examples implements a trival trade
@@ -546,9 +504,7 @@ from("quickfix:examples/inprocess.cfg?sessionID=FIX.4.2:TRADER->MARKET").
bean(new MyTradeExecutionProcessor());
----
-[[Quickfix-QuickFIXJComponentPriortoCamel2.5]]
-QuickFIX/J Component Prior to Camel 2.5
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### QuickFIX/J Component Prior to Camel 2.5
The *quickfix* component is an implementation of the
http://www.quickfixj.org/[QuickFIX/J] engine for Java . This engine
@@ -559,9 +515,7 @@ standard.
*Note:* The component can be used to send/receives messages to a FIX
server.
-[[Quickfix-URIformat.1]]
-URI format
-^^^^^^^^^^
+### URI format
[source]
----
@@ -581,9 +535,7 @@ The quickfix-server endpoint must be used to receive from FIX server FIX
messages and quickfix-client endpoint in the case that you want to send
messages to a FIX gateway.
-[[Quickfix-Exchangedataformat]]
-Exchange data format
-^^^^^^^^^^^^^^^^^^^^
+### Exchange data format
The QuickFIX/J engine is like CXF component a messaging bus using MINA
as protocol layer to create the socket connection with the FIX engine
@@ -602,9 +554,7 @@ dataformat] to transform the FIX message into your own java POJO
When a message must be send to QuickFix, then you must create a
QuickFix.Message instance.
-[[Quickfix-Lazycreatingengines]]
-Lazy creating engines
-^^^^^^^^^^^^^^^^^^^^^
+### Lazy creating engines
From *Camel 2.12.3* onwards, you can configure the QuickFixComponent to
lazy create and start the engines, which then only start these
@@ -612,9 +562,7 @@ on-demand. For example you can use this when you have multiple Camel
applications in a cluster with master/slaves. And want the slaves to be
standby.
-[[Quickfix-Samples]]
-Samples
-^^^^^^^
+### Samples
Direction : to FIX gateway
@@ -638,11 +586,9 @@ Direction : from FIX gateway
</route>
----
-[[Quickfix-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-rabbitmq/src/main/docs/rabbitmq-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc b/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc
index 15e99e4..cf8a122 100644
--- a/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc
+++ b/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc
@@ -1,4 +1,4 @@
-# RabbitMQ Component
+## RabbitMQ Component
*Available as of Camel 2.12*
@@ -20,9 +20,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[RabbitMQ-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------------------------
@@ -35,9 +33,7 @@ RabbitMQ client default (5672). The exchange name determines which
exchange produced messages will sent to. In the case of consumers, the
exchange name determines which exchange the queue will bind to.
-[[RabbitMQ-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -122,9 +118,7 @@ See
http://www.rabbitmq.com/releases/rabbitmq-java-client/current-javadoc/com/rabbitmq/client/ConnectionFactory.html[http://www.rabbitmq.com/releases/rabbitmq-java-client/current-javadoc/com/rabbitmq/client/ConnectionFactory.html]
and the AMQP specification for more information on connection options.
-[[RabbitMQ-Customconnectionfactory]]
-Custom connection factory
-~~~~~~~~~~~~~~~~~~~~~~~~~
+### Custom connection factory
[source,xml]
----------------------------------------------------------------------------------------
@@ -210,18 +204,14 @@ producer will also set the headers for downstream processors once the
exchange has taken place. Any headers set prior to production that the
producer sets will be overriden.
-[[RabbitMQ-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
The component will use the camel exchange in body as the rabbit mq
message body. The camel exchange in object must be convertible to a byte
array. Otherwise the producer will throw an exception of unsupported
body type.
-[[RabbitMQ-Samples]]
-Samples
-^^^^^^^
+### Samples
To receive messages from a queue that is bound to an exchange A with the
routing key B,
@@ -246,12 +236,9 @@ To send messages to an exchange called C
...to("rabbitmq://localhost/B")
-------------------------------
-[[RabbitMQ-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-restlet/src/main/docs/restlet-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-restlet/src/main/docs/restlet-component.adoc b/components/camel-restlet/src/main/docs/restlet-component.adoc
index 55d6abe..99e7c47 100644
--- a/components/camel-restlet/src/main/docs/restlet-component.adoc
+++ b/components/camel-restlet/src/main/docs/restlet-component.adoc
@@ -1,4 +1,4 @@
-# Restlet Component
+## Restlet Component
The *Restlet* component provides http://www.restlet.org[Restlet] based
link:endpoint.html[endpoints] for consuming and producing RESTful
@@ -17,9 +17,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Restlet-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------
@@ -57,9 +55,7 @@ synchronous=true as option on the endpoint uris, Or set it on the
RestletComponent as a global option so all endpoints inherit this
option.
-[[Restlet-Options]]
-Options
-^^^^^^^
+### Options
@@ -133,9 +129,7 @@ The Restlet component supports 22 endpoint options which are listed below:
// endpoint options: END
-[[Restlet-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -185,21 +179,15 @@ create responses using the API from Restlet. See examples below.
the List of CacheDirective of Restlet from the camel message header.
|=======================================================================
-[[Restlet-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
Camel will store the restlet response from the external server on the
OUT body. All headers from the IN message will be copied to the OUT
message, so that headers are preserved during routing.
-[[Restlet-Samples]]
-Samples
-^^^^^^^
+### Samples
-[[Restlet-RestletEndpointwithAuthentication]]
-Restlet Endpoint with Authentication
-++++++++++++++++++++++++++++++++++++
+#### Restlet Endpoint with Authentication
The following route starts a `restlet` consumer endpoint that listens
for `POST` requests on http://localhost:8080. The processor creates a
@@ -237,9 +225,7 @@ The sample client gets a response like the following:
received [<order foo='1'/>] as an order id = 89531
--------------------------------------------------
-[[Restlet-SinglerestletendpointtoservicemultiplemethodsandURItemplates]]
-Single restlet endpoint to service multiple methods and URI templates
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Single restlet endpoint to service multiple methods and URI templates
It is possible to create a single route to service multiple HTTP methods
using the `restletMethods` option. This snippet also shows how to
@@ -264,9 +250,7 @@ The `restletUriPatterns=#uriTemplates` option references the
</util:list>
--------------------------------------------------------
-[[Restlet-UsingRestletAPItopopulateresponse]]
-Using Restlet API to populate response
-++++++++++++++++++++++++++++++++++++++
+#### Using Restlet API to populate response
*Available as of Camel 2.8*
@@ -277,9 +261,7 @@ the response from an inlined Camel link:processor.html[Processor]:
*Generating response using Restlet Response API*
-[[Restlet-Configuringmaxthreadsoncomponent]]
-Configuring max threads on component
-++++++++++++++++++++++++++++++++++++
+#### Configuring max threads on component
To configure the max threads options you must do this on the component,
such as:
@@ -291,9 +273,7 @@ such as:
</bean>
-------------------------------------------------------------------------------
-[[Restlet-UsingtheRestletservletwithinawebapp]]
-Using the Restlet servlet within a webapp
-+++++++++++++++++++++++++++++++++++++++++
+#### Using the Restlet servlet within a webapp
*Available as of Camel 2.8* +
There are
@@ -386,12 +366,9 @@ well:
</repository>
--------------------------------------------------
-[[Restlet-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-rmi/src/main/docs/rmi-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-rmi/src/main/docs/rmi-component.adoc b/components/camel-rmi/src/main/docs/rmi-component.adoc
index 83f6b5c..f550f54 100644
--- a/components/camel-rmi/src/main/docs/rmi-component.adoc
+++ b/components/camel-rmi/src/main/docs/rmi-component.adoc
@@ -1,4 +1,4 @@
-# RMI Component
+## RMI Component
The *rmi:* component binds link:exchange.html[Exchange]s to the RMI
protocol (JRMP).
@@ -24,9 +24,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[RMI-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------------------------------------------
@@ -43,9 +41,7 @@ rmi://localhost:1099/path/to/service
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[RMI-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -75,9 +71,7 @@ The RMI component supports 9 endpoint options which are listed below:
// endpoint options: END
-[[RMI-Using]]
-Using
-^^^^^
+### Using
To call out to an existing RMI service registered in an RMI registry,
create a route similar to the following:
@@ -110,12 +104,9 @@ In XML DSL you can do as follows from *Camel 2.7* onwards:
</camel:route>
------------------------------------------------------------------------------------------------------------------------
-[[RMI-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-routebox/src/main/docs/routebox-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-routebox/src/main/docs/routebox-component.adoc b/components/camel-routebox/src/main/docs/routebox-component.adoc
index 23139f7..12a61fc 100644
--- a/components/camel-routebox/src/main/docs/routebox-component.adoc
+++ b/components/camel-routebox/src/main/docs/routebox-component.adoc
@@ -1,4 +1,4 @@
-# RouteBox Component
+## RouteBox Component
*Available as of Camel 2.6*
@@ -49,9 +49,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Routebox-TheneedforaCamelRouteboxendpoint]]
-The need for a Camel Routebox endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### The need for a Camel Routebox endpoint
The routebox component is designed to ease integration in complex
environments needing
@@ -87,9 +85,7 @@ delegate requests to inner fine grained routes to achieve a specific
integration objective, collect the final inner result, and continue to
progress to the next step along the coarse-grained route.
-[[Routebox-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------
@@ -99,9 +95,7 @@ routebox:routeboxname[?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Routebox-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -140,18 +134,14 @@ The RouteBox component supports 18 endpoint options which are listed below:
// endpoint options: END
-[[Routebox-SendingReceivingMessagestofromtheroutebox]]
-Sending/Receiving Messages to/from the routebox
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending/Receiving Messages to/from the routebox
Before sending requests it is necessary to properly configure the
routebox by loading the required URI parameters into the Registry as
shown below. In the case of Spring, if the necessary beans are declared
correctly, the registry is automatically populated by Camel.
-[[Routebox-Step1:LoadinginnerroutedetailsintotheRegistry]]
-Step 1: Loading inner route details into the Registry
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Step 1: Loading inner route details into the Registry
[source,java]
------------------------------------------------------------------------------------------------------------
@@ -188,9 +178,7 @@ private JndiRegistry createInnerRegistry() throws Exception {
CamelContext context = new DefaultCamelContext(createRegistry());
------------------------------------------------------------------------------------------------------------
-[[Routebox-Step2:OptionalyusingaDispatchStrategyinsteadofaDispatchMap]]
-Step 2: Optionaly using a Dispatch Strategy instead of a Dispatch Map
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Step 2: Optionaly using a Dispatch Strategy instead of a Dispatch Map
Using a dispatch Strategy involves implementing the interface
_org.apache.camel.component.routebox.strategy.RouteboxDispatchStrategy_
@@ -220,9 +208,7 @@ public class SimpleRouteDispatchStrategy implements RouteboxDispatchStrategy {
}
-------------------------------------------------------------------------------------------------------------------------------------------------
-[[Routebox-Step2:Launchingarouteboxconsumer]]
-Step 2: Launching a routebox consumer
-+++++++++++++++++++++++++++++++++++++
+#### Step 2: Launching a routebox consumer
When creating a route consumer, note that the # entries in the
routeboxUri are matched to the created inner registry, routebuilder list
@@ -252,9 +238,7 @@ public void testRouteboxRequests() throws Exception {
}
----------------------------------------------------------------------------------------------------------------------
-[[Routebox-Step3:Usingarouteboxproducer]]
-Step 3: Using a routebox producer
-+++++++++++++++++++++++++++++++++
+#### Step 3: Using a routebox producer
When sending requests to the routebox, it is not necessary for producers
do not need to know the inner route endpoint URI and they can simply
@@ -276,4 +260,4 @@ from ("direct:sendToMapBasedRoutebox")
.setHeader("ROUTE_DISPATCH_KEY", constant("addToCatalog"))
.to("routebox:multipleRoutes?innerRegistry=#registry&routeBuilders=#routes&dispatchMap=#map")
.to("log:Routes operation performed?showAll=true");
------------------------------------------------------------------------------------------------------------
+-----------------------------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-rss/src/main/docs/rss-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-rss/src/main/docs/rss-component.adoc b/components/camel-rss/src/main/docs/rss-component.adoc
index 79e56c1..460170a 100644
--- a/components/camel-rss/src/main/docs/rss-component.adoc
+++ b/components/camel-rss/src/main/docs/rss-component.adoc
@@ -1,4 +1,4 @@
-# RSS Component
+## RSS Component
The *rss:* component is used for polling RSS feeds. Camel will default
poll the feed every 60th seconds.
@@ -24,9 +24,7 @@ version] of http://rometools.github.io/rome/[ROME] hosted on ServiceMix
to solve some OSGi https://issues.apache.org/jira/browse/SMX4-510[class
loading issues].
-[[RSS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------
@@ -38,9 +36,7 @@ Where `rssUri` is the URI to the RSS feed to poll.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[RSS-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -89,9 +85,7 @@ The RSS component supports 28 endpoint options which are listed below:
// endpoint options: END
-[[RSS-Exchangedatatypes]]
-Exchange data types
-^^^^^^^^^^^^^^^^^^^
+### Exchange data types
Camel initializes the In body on the Exchange with a ROME `SyndFeed`.
Depending on the value of the `splitEntries` flag, Camel returns either
@@ -106,9 +100,7 @@ a `SyndFeed` with one `SyndEntry` or a `java.util.List` of `SyndEntrys`.
|`splitEntries` |`false` |The entire list of entries from the current feed is set in the exchange.
|=======================================================================
-[[RSS-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -117,9 +109,7 @@ Message Headers
|`CamelRssFeed` |The entire `SyncFeed` object.
|=======================================================================
-[[RSS-RSSDataformat]]
-RSS Dataformat
-^^^^^^^^^^^^^^
+### RSS Dataformat
The RSS component ships with an RSS dataformat that can be used to
convert between String (as XML) and ROME RSS model objects.
@@ -140,9 +130,7 @@ understand them as well, for example if the feed uses `alt=rss`, then
you can for example do
`from("rss:http://someserver.com/feeds/posts/default?alt=rss&splitEntries=false&consumer.delay=1000").to("bean:rss");`
-[[RSS-Filteringentries]]
-Filtering entries
-^^^^^^^^^^^^^^^^^
+### Filtering entries
You can filter out entries quite easily using XPath, as shown in the
data format section above. You can also exploit Camel's
@@ -152,14 +140,11 @@ would be:
The custom bean for this would be:
-[[RSS-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:atom.html[Atom]
-
+* link:atom.html[Atom]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-rss/src/main/docs/rss-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-rss/src/main/docs/rss-dataformat.adoc b/components/camel-rss/src/main/docs/rss-dataformat.adoc
index b43e2cc..1275169 100644
--- a/components/camel-rss/src/main/docs/rss-dataformat.adoc
+++ b/components/camel-rss/src/main/docs/rss-dataformat.adoc
@@ -1,4 +1,4 @@
-# RSS DataFormat
+## RSS DataFormat
The RSS component ships with an RSS dataformat that can be used to
convert between String (as XML) and ROME RSS model objects.
@@ -18,9 +18,7 @@ understand them as well, for example if the feed uses `alt=rss`, then
you can for example do
`from("rss:http://someserver.com/feeds/posts/default?alt=rss&splitEntries=false&consumer.delay=1000").to("bean:rss");`
-[[RSS-RSSDataformat-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The RSS dataformat supports 1 options which are listed below.
@@ -34,6 +32,4 @@ The RSS dataformat supports 1 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-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc b/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc
index b68ff28..b8b2657 100644
--- a/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc
+++ b/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc
@@ -1,4 +1,4 @@
-# Salesforce Component
+## Salesforce Component
*Available as of Camel 2.12*
@@ -20,9 +20,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Salesforce-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
The URI scheme for a salesforce component is as follows
@@ -34,18 +32,14 @@ salesforce:topic?options
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Salesforce-SupportedSalesforceAPIs]]
-Supported Salesforce APIs
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Supported Salesforce APIs
The component supports the following Salesforce APIs
Producer endpoints can use the following APIs. Most of the APIs process
one record at a time, the Query API can retrieve multiple Records.
-[[Salesforce-RestAPI]]
-Rest API
-++++++++
+#### Rest API
* getVersions - Gets supported Salesforce REST API versions
* getResources - Gets available Salesforce REST Resource endpoints
@@ -86,9 +80,7 @@ list of errors while creating the new object.
...to("salesforce:upsertSObject?sObjectIdName=Name")...
-----------------------------------------------------------
-[[Salesforce-RestBulkAPI]]
-Rest Bulk API
-+++++++++++++
+#### Rest Bulk API
Producer endpoints can use the following APIs. All Job data formats,
i.e. xml, csv, zip/xml, and zip/csv are supported. +
@@ -124,9 +116,7 @@ error.
...to("salesforce:createBatchJob")..
----------------------------------------
-[[Salesforce-RestStreamingAPI]]
-Rest Streaming API
-++++++++++++++++++
+#### Rest Streaming API
Consumer endpoints can use the following sytax for streaming endpoints
to receive Salesforce notifications on create/update.
@@ -145,13 +135,9 @@ To subscribe to an existing topic
from("salesforce:CamelTestTopic&sObjectName=Merchandise__c")...
-------------------------------------------------------------------
-[[Salesforce-Examples]]
-Examples
-~~~~~~~~
+### Examples
-[[Salesforce-UploadingadocumenttoaContentWorkspace]]
-Uploading a document to a ContentWorkspace
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Uploading a document to a ContentWorkspace
Create the ContentVersion in Java, using a Processor instance:
@@ -191,9 +177,7 @@ Give the output from the processor to the Salesforce component:
.to("salesforce:createSObject");
-----------------------------------------------------------------------------------------------------
-[[Salesforce-LimitsAPI]]
-Using Salesforce Limits API
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using Salesforce Limits API
With `salesforce:limits` operation you can fetch of API limits from Salesforce and then act upon that data received.
The result of `salesforce:limits` operation is mapped to `org.apache.camel.component.salesforce.api.dto.Limits`
@@ -221,9 +205,7 @@ from("direct:querySalesforce")
.endChoice()
-----------------------------------------------------------------------------------------------------
-[[Salesforce-Approval]]
-Working with approvals
-^^^^^^^^^^^^^^^^^^^^^^
+### Working with approvals
All the properties are named exactly the same as in the Salesforce REST API prefixed with `approval.`. You can set
approval properties by setting `approval.PropertyName` of the Endpoint these will be used as template -- meaning
@@ -268,9 +250,7 @@ body.put("nextApproverIds", userId);
final ApprovalResult result = template.requestBody("direct:example1", body, ApprovalResult.class);
-----------------------------------------------------------------------------------------------------
-[[Salesforce-RecentItems]]
-Using Salesforce Recent Items API
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using Salesforce Recent Items API
To fetch the recent items use `salesforce:recent` operation. This operation returns an `java.util.List` of
`org.apache.camel.component.salesforce.api.dto.RecentItem` objects (`List<RecentItem>`) that in turn contain
@@ -285,8 +265,7 @@ from("direct:fetchRecentItems")
.log("${body.name} at ${body.attributes.url}");
-----------------------------------------------------------------------------------------------------
-Working with approvals
-^^^^^^^^^^^^^^^^^^^^^^
+### Working with approvals
All the properties are named exactly the same as in the Salesforce REST API prefixed with `approval.`. You can set
approval properties by setting `approval.PropertyName` of the Endpoint these will be used as template -- meaning
@@ -331,9 +310,7 @@ body.put("nextApproverIds", userId);
final ApprovalResult result = template.requestBody("direct:example1", body, ApprovalResult.class);
-----------------------------------------------------------------------------------------------------
-[[Salesforce-CompositeAPI-Tree]]
-Using Salesforce Composite API to submit SObject tree
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using Salesforce Composite API to submit SObject tree
To create up to 200 records including parent-child relationships use `salesforce:composite-tree` operation. This
requires an instance of `org.apache.camel.component.salesforce.api.dto.composite.SObjectTree` in the input
@@ -375,9 +352,7 @@ final List<SObjectNode> succeeded = result.get(false);
final String firstId = succeeded.get(0).getId();
-----------------------------------------------------------------------------------------------------
-[[Salesforce-CompositeAPI-Batch]]
-Using Salesforce Composite API to submit multiple requests in a batch
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using Salesforce Composite API to submit multiple requests in a batch
The Composite API batch operation (`composite-batch`) allows you to accumulate multiple requests in a batch and then
submit them in one go, saving the round trip cost of multiple individual requests. Each response is then received in a
list of responses with the order perserved, so that the n-th requests response is in the n-th place of the response.
@@ -434,16 +409,12 @@ final Object updateResultData = deleteResult.getResult(); // probably null
-----------------------------------------------------------------------------------------------------
-[[Salesforce-CamelSalesforceMavenPlugin]]
-Camel Salesforce Maven Plugin
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Camel Salesforce Maven Plugin
This Maven plugin generates DTOs for the Camel
link:salesforce.html[Salesforce].
-[[Salesforce-Options]]
-Options
-^^^^^^^
+### Options
@@ -560,12 +531,9 @@ The generated DTOs use Jackson and XStream annotations. All Salesforce
field types are supported. Date and time fields are mapped to Joda
DateTime, and picklist fields are mapped to generated Java Enumerations.
-[[Salesforce-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-sap-netweaver/src/main/docs/sap-netweaver-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-sap-netweaver/src/main/docs/sap-netweaver-component.adoc b/components/camel-sap-netweaver/src/main/docs/sap-netweaver-component.adoc
index 3720b4d..b594cb1 100644
--- a/components/camel-sap-netweaver/src/main/docs/sap-netweaver-component.adoc
+++ b/components/camel-sap-netweaver/src/main/docs/sap-netweaver-component.adoc
@@ -1,4 +1,4 @@
-# SAP NetWeaver Component
+## SAP NetWeaver Component
*Available as of Camel 2.12*
@@ -21,9 +21,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[SAPNetWeaver-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
The URI scheme for a sap netweaver gateway component is as follows
@@ -35,9 +33,7 @@ sap-netweaver:https://host:8080/path?username=foo&password=secret
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[SAPNetWeaver-Prerequisites]]
-Prerequisites
-^^^^^^^^^^^^^
+### Prerequisites
You would need to have an account to the SAP NetWeaver system to be able
to leverage this component. SAP provides a
@@ -47,9 +43,7 @@ requires for an account.
This component uses the basic authentication scheme for logging into SAP
NetWeaver.
-[[SAPNetWeaver-Componentandendpointoptions]]
-SAPNetWeaver options
-^^^^^^^^^^^^^^^^^^^^
+### SAPNetWeaver options
// component options: START
@@ -77,9 +71,7 @@ The SAP NetWeaver component supports 7 endpoint options which are listed below:
// endpoint options: END
-[[SAPNetWeaver-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
The following headers can be used by the producer.
@@ -92,9 +84,7 @@ http://msdn.microsoft.com/en-us/library/cc956153.aspx[MS ADO.Net Data
Service] format.
|=======================================================================
-[[SAPNetWeaver-Examples]]
-Examples
-^^^^^^^^
+### Examples
This example is using the flight demo example from SAP, which is
available online over the internet
@@ -176,14 +166,11 @@ Destination city: SAN FRANCISCO
Destination airport: SFO
-------------------------------
-[[SAPNetWeaver-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: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-saxon/src/main/docs/xquery-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-saxon/src/main/docs/xquery-component.adoc b/components/camel-saxon/src/main/docs/xquery-component.adoc
index ba4730b..4f62111 100644
--- a/components/camel-saxon/src/main/docs/xquery-component.adoc
+++ b/components/camel-saxon/src/main/docs/xquery-component.adoc
@@ -1,4 +1,4 @@
-# XQuery Component
+## XQuery Component
Camel supports http://www.w3.org/TR/xquery/[XQuery] to allow an
link:expression.html[Expression] or link:predicate.html[Predicate] to be
@@ -8,9 +8,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
Filter] or as an link:expression.html[Expression] for a
link:recipient-list.html[Recipient List].
-[[XQuery-Options]]
-Options
-^^^^^^^
+### Options
@@ -74,9 +72,7 @@ The XQuery component supports 31 endpoint options which are listed below:
// endpoint options: END
-[[XQuery-Examples]]
-Examples
-^^^^^^^^
+### Examples
[source,java]
---------------------------
@@ -96,9 +92,7 @@ from("direct:start").
recipientList().xquery("concat('mock:foo.', /person/@city)", String.class);
-----------------------------------------------------------------------------
-[[XQuery-Variables]]
-Variables
-^^^^^^^^^
+### Variables
The IN message body will be set as the `contextItem`. Besides this these
Variables is also added as parameters:
@@ -125,9 +119,7 @@ with they own key name, for instance if there is an IN header with the
key name *foo* then its added as *foo*.
|=======================================================================
-[[XQuery-UsingXMLconfiguration]]
-Using XML configuration
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using XML configuration
If you prefer to configure your routes in your link:spring.html[Spring]
XML file then you can use XPath expressions as follows
@@ -165,9 +157,7 @@ attribute:
<xquery type="java.lang.String">concat('mock:foo.', /person/@city)</xquery>
-------------------------------------------------------------------------------
-[[XQuery-UsingXQueryastransformation]]
-Using XQuery as transformation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using XQuery as transformation
We can do a message translation using transform or setBody in the route,
as shown below:
@@ -190,9 +180,7 @@ from("direct:start").
�
-[[XQuery-UsingXQueryasanendpoint]]
-Using XQuery as an endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using XQuery as an endpoint
Sometimes an XQuery expression can be quite large; it can essentally be
used for link:templating.html[Templating]. So you may want to use an
@@ -213,9 +201,7 @@ The following example shows how to take a message of an ActiveMQ queue
</camelContext>
-------------------------------------------------------------------------
-[[XQuery-Examples.1]]
-Examples
-^^^^^^^^
+### Examples
Here is a simple
http://svn.apache.org/repos/asf/camel/trunk/components/camel-saxon/src/test/java/org/apache/camel/builder/saxon/XQueryFilterTest.java[example]
@@ -227,9 +213,7 @@ http://svn.apache.org/repos/asf/camel/trunk/components/camel-saxon/src/test/java
uses XQuery with namespaces as a predicate in a
link:message-filter.html[Message Filter]
-[[XQuery-LearningXQuery]]
-Learning XQuery
-^^^^^^^^^^^^^^^
+### Learning XQuery
XQuery is a very powerful language for querying, searching, sorting and
returning XML. For help learning XQuery try these tutorials
@@ -242,9 +226,7 @@ Tutorial]
You might also find the http://www.w3.org/TR/xpath-functions/[XQuery
function reference] useful
-[[XQuery-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -258,9 +240,7 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").xquery("resource:classpath:myxquery.txt", String.class)
------------------------------------------------------------------------------
-[[XQuery-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use XQuery in your camel routes you need to add the a dependency on
*camel-saxon* which implements the XQuery language.
@@ -276,4 +256,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-saxon</artifactId>
<version>x.x.x</version>
</dependency>
---------------------------------------
+--------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-saxon/src/main/docs/xquery-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-saxon/src/main/docs/xquery-language.adoc b/components/camel-saxon/src/main/docs/xquery-language.adoc
index 852c9f2..4f31903 100644
--- a/components/camel-saxon/src/main/docs/xquery-language.adoc
+++ b/components/camel-saxon/src/main/docs/xquery-language.adoc
@@ -1,4 +1,4 @@
-# XQuery Language
+## XQuery Language
Camel supports http://www.w3.org/TR/xquery/[XQuery] to allow an
link:expression.html[Expression] or link:predicate.html[Predicate] to be
@@ -8,9 +8,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
Filter] or as an link:expression.html[Expression] for a
link:recipient-list.html[Recipient List].
-[[XQuery-Options]]
-XQuery Language options
-^^^^^^^^^^^^^^^^^^^^^^^
+### XQuery Language options
// language options: START
The XQuery language supports 3 options which are listed below.
@@ -28,9 +26,7 @@ The XQuery language supports 3 options which are listed below.
{% endraw %}
// language options: END
-[[XQuery-Examples]]
-Examples
-^^^^^^^^
+### Examples
[source,java]
---------------------------
@@ -50,9 +46,7 @@ from("direct:start").
recipientList().xquery("concat('mock:foo.', /person/@city)", String.class);
-----------------------------------------------------------------------------
-[[XQuery-Variables]]
-Variables
-^^^^^^^^^
+### Variables
The IN message body will be set as the `contextItem`. Besides this these
Variables is also added as parameters:
@@ -79,9 +73,7 @@ with they own key name, for instance if there is an IN header with the
key name *foo* then its added as *foo*.
|=======================================================================
-[[XQuery-UsingXMLconfiguration]]
-Using XML configuration
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using XML configuration
If you prefer to configure your routes in your link:spring.html[Spring]
XML file then you can use XPath expressions as follows
@@ -119,9 +111,7 @@ attribute:
<xquery type="java.lang.String">concat('mock:foo.', /person/@city)</xquery>
-------------------------------------------------------------------------------
-[[XQuery-UsingXQueryastransformation]]
-Using XQuery as transformation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using XQuery as transformation
We can do a message translation using transform or setBody in the route,
as shown below:
@@ -144,9 +134,7 @@ from("direct:start").
�
-[[XQuery-UsingXQueryasanendpoint]]
-Using XQuery as an endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using XQuery as an endpoint
Sometimes an XQuery expression can be quite large; it can essentally be
used for link:templating.html[Templating]. So you may want to use an
@@ -167,9 +155,7 @@ The following example shows how to take a message of an ActiveMQ queue
</camelContext>
-------------------------------------------------------------------------
-[[XQuery-Examples.1]]
-Examples
-^^^^^^^^
+### Examples
Here is a simple
http://svn.apache.org/repos/asf/camel/trunk/components/camel-saxon/src/test/java/org/apache/camel/builder/saxon/XQueryFilterTest.java[example]
@@ -181,9 +167,7 @@ http://svn.apache.org/repos/asf/camel/trunk/components/camel-saxon/src/test/java
uses XQuery with namespaces as a predicate in a
link:message-filter.html[Message Filter]
-[[XQuery-LearningXQuery]]
-Learning XQuery
-^^^^^^^^^^^^^^^
+### Learning XQuery
XQuery is a very powerful language for querying, searching, sorting and
returning XML. For help learning XQuery try these tutorials
@@ -196,9 +180,7 @@ Tutorial]
You might also find the http://www.w3.org/TR/xpath-functions/[XQuery
function reference] useful
-[[XQuery-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -212,9 +194,7 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").xquery("resource:classpath:myxquery.txt", String.class)
------------------------------------------------------------------------------
-[[XQuery-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use XQuery in your camel routes you need to add the a dependency on
*camel-saxon* which implements the XQuery language.
@@ -230,4 +210,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-saxon</artifactId>
<version>x.x.x</version>
</dependency>
---------------------------------------
+--------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-schematron/src/main/docs/schematron-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-schematron/src/main/docs/schematron-component.adoc b/components/camel-schematron/src/main/docs/schematron-component.adoc
index 2de9dfa..bb5c23b 100644
--- a/components/camel-schematron/src/main/docs/schematron-component.adoc
+++ b/components/camel-schematron/src/main/docs/schematron-component.adoc
@@ -1,4 +1,4 @@
-# Schematron Component
+## Schematron Component
*Available as of Camel 2.14*
@@ -17,18 +17,14 @@ written in a way that Schematron rules are loaded at the start of the
endpoint (only once) this is to minimise the overhead of instantiating a
Java Templates object representing the rules.
-[[Schematron-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------
schematron://path?[options]
---------------------------
-[[Schematron-URIoptions]]
-URI options
-^^^^^^^^^^^
+### URI options
// component options: START
@@ -58,9 +54,7 @@ The Schematron component supports 5 endpoint options which are listed below:
-[[Schematron-Headers]]
-Headers
-^^^^^^^
+### Headers
[width="100%",cols="10%,10%,10%,70%",options="header",]
|=======================================================================
@@ -71,9 +65,7 @@ Headers
|CamelSchematronValidationReport |The schematrion report body in XML format. See an example below |String |IN
|=======================================================================
-[[Schematron-URIandpathsyntax]]
-URI and path syntax
-^^^^^^^^^^^^^^^^^^^
+### URI and path syntax
The following example shows how to invoke the schematron processor in
Java DSL. The schematron rules file is sourced from the class path:
@@ -124,9 +116,7 @@ an update, all you need is to restart the route or the component. No
harm in storing these rules in the class path though, but you will have
to build and deploy the component to pick up the changes.
-[[Schematron-Schematronrulesandreportsamples]]
-Schematron rules and report samples
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Schematron rules and report samples
Here is an example of schematron rules
@@ -175,5 +165,4 @@ TIP: *Useful Links and resources*
to Schematron]�by Mulleberry technologies. An excellent document in PDF
to get you started on Schematron.
* http://www.schematron.com[Schematron official site]. This contains
-links to other resources
-
+links to other resources
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-script/src/main/docs/javaScript-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-script/src/main/docs/javaScript-language.adoc b/components/camel-script/src/main/docs/javaScript-language.adoc
index 2dc2fca..a4dfdfa 100644
--- a/components/camel-script/src/main/docs/javaScript-language.adoc
+++ b/components/camel-script/src/main/docs/javaScript-language.adoc
@@ -1,4 +1,4 @@
-# JavaScript Language
+## JavaScript Language
Camel supports
http://en.wikipedia.org/wiki/JavaScript[JavaScript/ECMAScript] among
@@ -19,9 +19,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
Filter] or as an link:expression.html[Expression] for a
link:recipient-list.html[Recipient List]
-[[JavaScript-Language-options]]
-Javascript Language Options
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Javascript Language Options
// language options: START
The JavaScript language supports 1 options which are listed below.
@@ -37,9 +35,7 @@ The JavaScript language supports 1 options which are listed below.
{% endraw %}
// language options: END
-[[JavaScript-Example]]
-Example
-^^^^^^^
+### Example
In the sample below we use JavaScript to create a
link:predicate.html[Predicate] use in the route path, to route exchanges
@@ -72,9 +68,7 @@ And a Spring DSL sample as well:
</route>
-------------------------------------------------------------------------------
-[[JavaScript-ScriptContext]]
-ScriptContext
-^^^^^^^^^^^^^
+### ScriptContext
The JSR-223 scripting languages ScriptContext is pre configured with the
following attributes all set at `ENGINE_SCOPE`:
@@ -102,9 +96,7 @@ further below for example.
See link:scripting-languages.html[Scripting Languages] for the list of
languages with explicit DSL support.
-[[JavaScript-AdditionalargumentstoScriptingEngine]]
-Additional arguments to ScriptingEngine
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional arguments to ScriptingEngine
*Available as of Camel 2.8*
@@ -112,9 +104,7 @@ You can provide additional arguments to the `ScriptingEngine` using a
header on the Camel message with the key `CamelScriptArguments`. +
See this example:
-[[JavaScript-Usingpropertiesfunction]]
-Using properties function
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using properties function
*Available as of Camel 2.9*
@@ -139,9 +129,7 @@ same example is simpler:
.setHeader("myHeader").groovy("properties.resolve(request.headers.get('foo'))")
-------------------------------------------------------------------------------
-[[JavaScript-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -155,9 +143,7 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").groovy("resource:classpath:mygroovy.groovy")
-------------------------------------------------------------------
-[[JavaScript-Howtogettheresultfrommultiplestatementsscript]]
-How to get the result from multiple statements script
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get the result from multiple statements script
*Available as of Camel 2.14*
@@ -177,9 +163,7 @@ result = body * 2 + 1
�
-[[JavaScript-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use scripting languages in your camel routes you need to add the a
dependency on *camel-script* which integrates the JSR-223 scripting
@@ -196,4 +180,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-script</artifactId>
<version>x.x.x</version>
</dependency>
----------------------------------------
+---------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-script/src/main/docs/php-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-script/src/main/docs/php-language.adoc b/components/camel-script/src/main/docs/php-language.adoc
index c7dcb13..d7c8a01 100644
--- a/components/camel-script/src/main/docs/php-language.adoc
+++ b/components/camel-script/src/main/docs/php-language.adoc
@@ -1,4 +1,4 @@
-# PHP Language
+## PHP Language
Camel supports http://www.php.net/[PHP] among other
link:scripting-languages.html[Scripting Languages] to allow an
@@ -18,9 +18,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
Filter] or as an link:expression.html[Expression] for a
link:recipient-list.html[Recipient List]
-[[PHP-Language-options]]
-PHP Language Options
-^^^^^^^^^^^^^^^^^^^^
+### PHP Language Options
// language options: START
The PHP language supports 1 options which are listed below.
@@ -36,9 +34,7 @@ The PHP language supports 1 options which are listed below.
{% endraw %}
// language options: END
-[[PHP-ScriptContext]]
-ScriptContext
-^^^^^^^^^^^^^
+### ScriptContext
The JSR-223 scripting languages ScriptContext is pre configured with the
following attributes all set at `ENGINE_SCOPE`:
@@ -66,9 +62,7 @@ further below for example.
See link:scripting-languages.html[Scripting Languages] for the list of
languages with explicit DSL support.
-[[PHP-AdditionalargumentstoScriptingEngine]]
-Additional arguments to ScriptingEngine
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional arguments to ScriptingEngine
*Available as of Camel 2.8*
@@ -76,9 +70,7 @@ You can provide additional arguments to the `ScriptingEngine` using a
header on the Camel message with the key `CamelScriptArguments`. +
See this example:
-[[PHP-Usingpropertiesfunction]]
-Using properties function
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using properties function
*Available as of Camel 2.9*
@@ -103,9 +95,7 @@ same example is simpler:
.setHeader("myHeader").groovy("properties.resolve(request.headers.get('foo'))")
-------------------------------------------------------------------------------
-[[PHP-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -119,9 +109,7 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").groovy("resource:classpath:mygroovy.groovy")
-------------------------------------------------------------------
-[[PHP-Howtogettheresultfrommultiplestatementsscript]]
-How to get the result from multiple statements script
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get the result from multiple statements script
*Available as of Camel 2.14*
@@ -141,9 +129,7 @@ result = body * 2 + 1
�
-[[PHP-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use scripting languages in your camel routes you need to add the a
dependency on *camel-script* which integrates the JSR-223 scripting
@@ -160,4 +146,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-script</artifactId>
<version>x.x.x</version>
</dependency>
----------------------------------------
+---------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-script/src/main/docs/python-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-script/src/main/docs/python-language.adoc b/components/camel-script/src/main/docs/python-language.adoc
index aa4fd07..b9d26b7 100644
--- a/components/camel-script/src/main/docs/python-language.adoc
+++ b/components/camel-script/src/main/docs/python-language.adoc
@@ -1,4 +1,4 @@
-# Python Language
+## Python Language
Camel supports http://www.python.org/[Python] among other
link:scripting-languages.html[Scripting Languages] to allow an
@@ -18,9 +18,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
Filter] or as an link:expression.html[Expression] for a
link:recipient-list.html[Recipient List]
-[[Python-Language-options]]
-Python Language Options
-^^^^^^^^^^^^^^^^^^^^^^^
+### Python Language Options
// language options: START
The Python language supports 1 options which are listed below.
@@ -36,9 +34,7 @@ The Python language supports 1 options which are listed below.
{% endraw %}
// language options: END
-[[Python-Example]]
-Example
-^^^^^^^
+### Example
In the sample below we use Python to create a
link:predicate.html[Predicate] use in the route path, to route exchanges
@@ -71,9 +67,7 @@ And a Spring DSL sample as well:
</route>
-------------------------------------------------------------------
-[[Python-ScriptContext]]
-ScriptContext
-^^^^^^^^^^^^^
+### ScriptContext
The JSR-223 scripting languages ScriptContext is pre configured with the
following attributes all set at `ENGINE_SCOPE`:
@@ -101,9 +95,7 @@ further below for example.
See link:scripting-languages.html[Scripting Languages] for the list of
languages with explicit DSL support.
-[[Python-AdditionalargumentstoScriptingEngine]]
-Additional arguments to ScriptingEngine
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional arguments to ScriptingEngine
*Available as of Camel 2.8*
@@ -111,9 +103,7 @@ You can provide additional arguments to the `ScriptingEngine` using a
header on the Camel message with the key `CamelScriptArguments`. +
See this example:
-[[Python-Usingpropertiesfunction]]
-Using properties function
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using properties function
*Available as of Camel 2.9*
@@ -138,9 +128,7 @@ same example is simpler:
.setHeader("myHeader").groovy("properties.resolve(request.headers.get('foo'))")
-------------------------------------------------------------------------------
-[[Python-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -154,9 +142,7 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").groovy("resource:classpath:mygroovy.groovy")
-------------------------------------------------------------------
-[[Python-Howtogettheresultfrommultiplestatementsscript]]
-How to get the result from multiple statements script
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get the result from multiple statements script
*Available as of Camel 2.14*
@@ -176,9 +162,7 @@ result = body * 2 + 1
�
-[[Python-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use scripting languages in your camel routes you need to add the a
dependency on *camel-script* which integrates the JSR-223 scripting
@@ -195,4 +179,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-script</artifactId>
<version>x.x.x</version>
</dependency>
----------------------------------------
+---------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-script/src/main/docs/ruby-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-script/src/main/docs/ruby-language.adoc b/components/camel-script/src/main/docs/ruby-language.adoc
index 7a3e83e..6f11c00 100644
--- a/components/camel-script/src/main/docs/ruby-language.adoc
+++ b/components/camel-script/src/main/docs/ruby-language.adoc
@@ -1,4 +1,4 @@
-# Ruby Language
+## Ruby Language
Camel supports http://www.ruby-lang.org/en/[Ruby] among other
link:scripting-languages.html[Scripting Languages] to allow an
@@ -18,9 +18,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
Filter] or as an link:expression.html[Expression] for a
link:recipient-list.html[Recipient List]
-[[Ruby-Language-options]]
-Ruby Language Options
-^^^^^^^^^^^^^^^^^^^^^
+### Ruby Language Options
// language options: START
The Ruby language supports 1 options which are listed below.
@@ -36,9 +34,7 @@ The Ruby language supports 1 options which are listed below.
{% endraw %}
// language options: END
-[[Ruby-Example]]
-Example
-^^^^^^^
+### Example
In the sample below we use Ruby to create a
link:predicate.html[Predicate] use in the route path, to route exchanges
@@ -71,9 +67,7 @@ And a Spring DSL sample as well:
</route>
----------------------------------------------------------------
-[[Ruby-ScriptContext]]
-ScriptContext
-^^^^^^^^^^^^^
+### ScriptContext
The JSR-223 scripting languages ScriptContext is pre configured with the
following attributes all set at `ENGINE_SCOPE`:
@@ -101,9 +95,7 @@ further below for example.
See link:scripting-languages.html[Scripting Languages] for the list of
languages with explicit DSL support.
-[[Ruby-AdditionalargumentstoScriptingEngine]]
-Additional arguments to ScriptingEngine
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional arguments to ScriptingEngine
*Available as of Camel 2.8*
@@ -111,9 +103,7 @@ You can provide additional arguments to the `ScriptingEngine` using a
header on the Camel message with the key `CamelScriptArguments`. +
See this example:
-[[Ruby-Usingpropertiesfunction]]
-Using properties function
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using properties function
*Available as of Camel 2.9*
@@ -138,9 +128,7 @@ same example is simpler:
.setHeader("myHeader").groovy("properties.resolve(request.headers.get('foo'))")
-------------------------------------------------------------------------------
-[[Ruby-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -154,9 +142,7 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").groovy("resource:classpath:mygroovy.groovy")
-------------------------------------------------------------------
-[[Ruby-Howtogettheresultfrommultiplestatementsscript]]
-How to get the result from multiple statements script
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get the result from multiple statements script
*Available as of Camel 2.14*
@@ -176,9 +162,7 @@ result = body * 2 + 1
�
-[[Ruby-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use scripting languages in your camel routes you need to add the a
dependency on *camel-script* which integrates the JSR-223 scripting
@@ -195,4 +179,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-script</artifactId>
<version>x.x.x</version>
</dependency>
----------------------------------------
+---------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-servicenow/src/main/docs/servicenow-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-servicenow/src/main/docs/servicenow-component.adoc b/components/camel-servicenow/src/main/docs/servicenow-component.adoc
index 258ec81..8ce386b 100644
--- a/components/camel-servicenow/src/main/docs/servicenow-component.adoc
+++ b/components/camel-servicenow/src/main/docs/servicenow-component.adoc
@@ -1,4 +1,4 @@
-# ServiceNow Component
+## ServiceNow Component
*Available as of Camel 2.18*
@@ -19,18 +19,14 @@ for this component:
</dependency>
-------------------------------------------------
-[[ServiceNow-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------
servicenow://instanceName?[options]
---------------------------------------
-[[ServiceNow-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -108,9 +104,7 @@ The ServiceNow component supports 41 endpoint options which are listed below:
-[[ServiceNow-Headers]]
-Headers
-^^^^^^^
+### Headers
[width="100%",cols="10%,10%,10%,10%,60%",options="header",]
|===
@@ -263,9 +257,7 @@ NOTE: link:http://wiki.servicenow.com/index.php?title=REST_API#Available_APIs[Fu
NOTE: https://docs.servicenow.com/bundle/helsinki-servicenow-platform/page/integrate/inbound-rest/reference/r_RESTResources.html[Helsinki REST API Documentation]
-[[ServiceNow-Usageexamples]]
-Usage examples:
-^^^^^^^^^^^^^^^
+### Usage examples:
�
{% raw %}
[source,java]
@@ -292,4 +284,4 @@ FluentProducerTemplate.on(context)
.to("direct:servicenow")
.send();
-------------------------------------------------------------------------------------------------------------------
-{% endraw %}
+{% endraw %}
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-servlet/src/main/docs/servlet-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-servlet/src/main/docs/servlet-component.adoc b/components/camel-servlet/src/main/docs/servlet-component.adoc
index bc35e2e..30209cd 100644
--- a/components/camel-servlet/src/main/docs/servlet-component.adoc
+++ b/components/camel-servlet/src/main/docs/servlet-component.adoc
@@ -1,4 +1,4 @@
-# Servlet Component
+## Servlet Component
The *servlet:* component provides HTTP based
link:endpoint.html[endpoints] for consuming HTTP requests that arrive at
@@ -27,9 +27,7 @@ body appears to be empty or you need to access the data multiple times
link:stream-caching.html[Stream caching] or convert the message body to
a `String` which is safe to be read multiple times.
-[[SERVLET-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------
@@ -39,9 +37,7 @@ servlet://relative_path[?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[SERVLET-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The Servlet component supports 7 options which are listed below.
@@ -96,9 +92,7 @@ The Servlet component supports 22 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[SERVLET-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Camel will apply the same Message Headers as the link:http.html[HTTP]
component.
@@ -108,18 +102,14 @@ Camel will also populate *all* `request.parameter` and
`http://myserver/myserver?orderid=123`, the exchange will contain a
header named `orderid` with the value 123.
-[[SERVLET-Usage]]
-Usage
-^^^^^
+### Usage
You can consume only from endpoints generated by the Servlet component.
Therefore, it should be used only as input into your Camel routes. To
issue HTTP requests against other HTTP endpoints, use the
link:http.html[HTTP Component]
-[[SERVLET-PuttingCamelJARsintheappserverbootclasspath]]
-Putting Camel JARs in the app server boot classpath
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Putting Camel JARs in the app server boot classpath
If you put the Camel JARs such as `camel-core`, `camel-servlet`, etc. in
the boot classpath of your application server (eg usually in its lib
@@ -178,9 +168,7 @@ But its *strongly advised* to use unique servlet-name for each Camel
application to avoid this duplication clash, as well any unforeseen
side-effects.
-[[SERVLET-Sample]]
-Sample
-^^^^^^
+### Sample
INFO: From Camel 2.7 onwards it's easier to use link:servlet.html[Servlet] in
Spring web applications. See link:servlet-tomcat-example.html[Servlet
@@ -204,15 +192,11 @@ endpoint uses the relative path to specify the endpoint's URL. A client
can access the `camel-servlet` endpoint through the servlet publish
address: `("http://localhost:8080/camel/services") + RELATIVE_PATH("/hello")`.
-[[SERVLET-SamplewhenusingSpring3.x]]
-Sample when using Spring 3.x
-++++++++++++++++++++++++++++
+#### Sample when using Spring 3.x
See link:servlet-tomcat-example.html[Servlet Tomcat Example]
-[[SERVLET-SamplewhenusingSpring2.x]]
-Sample when using Spring 2.x
-++++++++++++++++++++++++++++
+#### Sample when using Spring 2.x
When using the Servlet component in a Camel/Spring application it's
often required to load the Spring ApplicationContext _after_ the Servlet
@@ -243,9 +227,7 @@ like this:
<web-app>
-------------------------------------------------------------------------
-[[SERVLET-SamplewhenusingOSGi]]
-Sample when using OSGi
-++++++++++++++++++++++
+#### Sample when using OSGi
From *Camel 2.6.0*, you can publish the
http://svn.apache.org/repos/asf/camel/trunk/components/camel-servlet/src/main/java/org/apache/camel/component/servlet/CamelHttpTransportServlet.java[CamelHttpTransportServlet]
@@ -258,9 +240,7 @@ the
http://svn.apache.org/repos/asf/camel/trunk/components/camel-servlet/src/main/java/org/apache/camel/component/servlet/CamelHttpTransportServlet.java[CamelHttpTransportServlet]
on the OSGi platform
-[[SERVLET-Spring-Boot]]
-Usage with Spring-Boot
-++++++++++++++++++++++
+#### Usage with Spring-Boot
From *Camel 2.19.0* onwards, the _camel-servlet-starter_ library binds automatically all the rest endpoints under the "/camel/*" context path.
The following table summarizes the additional configuration properties available in the camel-servlet-starter library.
@@ -276,9 +256,7 @@ The automatic mapping of the Camel servlet can also be disabled.
|=======================================================================
{% endraw %}
-[[SERVLET-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -289,5 +267,4 @@ See Also
* link:servlet-tomcat-no-spring-example.html[Servlet Tomcat No Spring
Example]
* link:http.html[HTTP]
-* link:jetty.html[Jetty]
-
+* link:jetty.html[Jetty]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-sip/src/main/docs/sip-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-sip/src/main/docs/sip-component.adoc b/components/camel-sip/src/main/docs/sip-component.adoc
index 082d621..4b405ed 100644
--- a/components/camel-sip/src/main/docs/sip-component.adoc
+++ b/components/camel-sip/src/main/docs/sip-component.adoc
@@ -1,4 +1,4 @@
-# SIP Component
+## SIP Component
*Available as of Camel 2.5*
@@ -45,9 +45,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Sip-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
The URI scheme for a sip endpoint is as follows:
@@ -63,9 +61,7 @@ UDP.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Sip-Options]]
-Options
-^^^^^^^
+### Options
The SIP Component offers an extensive set of configuration options &
capability to create custom stateful headers needed to propagate state
@@ -134,13 +130,9 @@ The SIP component supports 45 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[Sip-SendingMessagestofromaSIPendpoint]]
-Sending Messages to/from a SIP endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending Messages to/from a SIP endpoint
-[[Sip-CreatingaCamelSIPPublisher]]
-Creating a Camel SIP Publisher
-++++++++++++++++++++++++++++++
+#### Creating a Camel SIP Publisher
In the example below, a SIP Publisher is created to send SIP Event
publications to +
@@ -164,9 +156,7 @@ producerTemplate.sendBodyAndHeader(
Request.PUBLISH);
----------------------------------------------------------------------------------------------------------------------------------------------
-[[Sip-CreatingaCamelSIPSubscriber]]
-Creating a Camel SIP Subscriber
-+++++++++++++++++++++++++++++++
+#### Creating a Camel SIP Subscriber
In the example below, a SIP Subscriber is created to receive SIP Event
publications sent to +
@@ -208,4 +198,4 @@ and is capable of communicating with both Publisher as well as
Subscriber. It has a separate SIP stackName distinct from Publisher as
well as Subscriber. While it is set up as a Camel Consumer, it does not
actually send any messages along the route to the endpoint
-"mock:neverland".
+"mock:neverland".
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-sjms/src/main/docs/sjms-batch-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-sjms/src/main/docs/sjms-batch-component.adoc b/components/camel-sjms/src/main/docs/sjms-batch-component.adoc
index 98d6671..241b47d 100644
--- a/components/camel-sjms/src/main/docs/sjms-batch-component.adoc
+++ b/components/camel-sjms/src/main/docs/sjms-batch-component.adoc
@@ -1,8 +1,6 @@
-# Simple JMS Batch Component
+## Simple JMS Batch Component
[[ConfluenceContent]]
-[[SJMSBatch-SJMSBatchComponent]]
-SJMS Batch Component
-~~~~~~~~~~~~~~~~~~~~
+### SJMS Batch Component
*Available as of Camel 2.16*
@@ -78,9 +76,7 @@ for this component:
</dependency>
----
-[[SJMSBatch-URIformat]]
-URI format
-++++++++++
+#### URI format
[source]
----
@@ -110,9 +106,7 @@ broker. A plain link:sjms.html[SJMS] consumer endpoint can be used in
conjunction with a regular non-persistence backed
link:aggregator2.html[aggregator] in this scenario.
-[[SJMSBatch-ComponentOptionsandConfigurations]]
-Component Options and Configurations
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Component Options and Configurations
@@ -182,4 +176,4 @@ The Simple JMS Batch component supports 23 endpoint options which are listed bel
The `completionSize` endpoint attribute is used in conjunction with
`completionTimeout`, where the first condition to be met will cause the
-aggregated `Exchange` to be emitted down the route.
+aggregated `Exchange` to be emitted down the route.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-sjms/src/main/docs/sjms-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-sjms/src/main/docs/sjms-component.adoc b/components/camel-sjms/src/main/docs/sjms-component.adoc
index 7cb31cc..3e74bfc 100644
--- a/components/camel-sjms/src/main/docs/sjms-component.adoc
+++ b/components/camel-sjms/src/main/docs/sjms-component.adoc
@@ -1,4 +1,4 @@
-# Simple JMS Component
+## Simple JMS Component
ifdef::env-github[]
:icon-smile: :smiley:
:caution-caption: :boom:
@@ -14,9 +14,7 @@ ifndef::env-github[]
endif::[]
[[ConfluenceContent]]
-[[SJMS-SJMSComponent]]
-SJMS Component
-~~~~~~~~~~~~~~
+### SJMS Component
*Available as of Camel 2.11*
@@ -61,9 +59,7 @@ for this component:
</dependency>
----
-[[SJMS-URIformat]]
-URI format
-++++++++++
+#### URI format
[source]
----
@@ -97,9 +93,7 @@ sjms:topic:Stocks.Prices
You append query options to the URI using the following format,
`?option=value&option=value&...`
-[[SJMS-ComponentOptionsandConfigurations]]
-Component Options and Configurations
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Component Options and Configurations
@@ -212,13 +206,9 @@ component.setConnectionResource(connectionResource);
component.setMaxConnections(1);
----
-[[SJMS-ProducerUsage]]
-Producer Usage
-^^^^^^^^^^^^^^
+### Producer Usage
-[[SJMS-InOnlyProducer]]
-InOnly Producer - (Default)
-+++++++++++++++++++++++++++
+#### InOnly Producer - (Default)
The _InOnly_ producer is the default behavior of the SJMS Producer
Endpoint.
@@ -229,9 +219,7 @@ from("direct:start")
.to("sjms:queue:bar");
----
-[[SJMS-InOutProducer]]
-InOut Producer
-++++++++++++++
+#### InOut Producer
To enable _InOut_ behavior append the `exchangePattern` attribute to the
URI. By default it will use a dedicated TemporaryQueue for each
@@ -252,13 +240,9 @@ from("direct:start")
.to("sjms:queue:bar?exchangePattern=InOut&namedReplyTo=my.reply.to.queue");
----
-[[SJMS-ConsumerUsage]]
-Consumer Usage
-^^^^^^^^^^^^^^
+### Consumer Usage
-[[SJMS-InOnlyConsumer]]
-InOnly Consumer - (Default)
-+++++++++++++++++++++++++++
+#### InOnly Consumer - (Default)
The _InOnly_ xonsumer is the default Exchange behavior of the SJMS
Consumer Endpoint.
@@ -269,9 +253,7 @@ from("sjms:queue:bar")
.to("mock:result");
----
-[[SJMS-InOutConsumer]]
-InOut Consumer
-++++++++++++++
+#### InOut Consumer
To enable _InOut_ behavior append the `exchangePattern` attribute to the
URI.
@@ -282,13 +264,9 @@ from("sjms:queue:in.out.test?exchangePattern=InOut")
.transform(constant("Bye Camel"));
----
-[[SJMS-AdvancedUsageNotes]]
-Advanced Usage Notes
-^^^^^^^^^^^^^^^^^^^^
+### Advanced Usage Notes
-[[SJMS-PlugableConnectionResourceManagementconnectionresource]]
-Plugable Connection Resource Management [[SJMS-connectionresource]]
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Plugable Connection Resource Management [[SJMS-connectionresource]]
SJMS provides JMS
http://docs.oracle.com/javaee/5/api/javax/jms/Connection.html[`Connection`]
@@ -370,15 +348,11 @@ camelContext.addComponent("sjms", component);
To see the full example of its usage please refer to the
https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/test/java/org/apache/camel/component/sjms/it/ConnectionResourceIT.java[`ConnectionResourceIT`].
-[[SJMS-Session,Consumer,&ProducerPooling&CachingManagement]]
-Session, Consumer, & Producer Pooling & Caching Management
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Session, Consumer, & Producer Pooling & Caching Management
Coming soon ...
-[[SJMS-BatchMessageSupport]]
-Batch Message Support
-+++++++++++++++++++++
+#### Batch Message Support
The SjmsProducer supports publishing a collection of messages by
creating an Exchange that encapsulates a `List`. This SjmsProducer will
@@ -411,9 +385,7 @@ Then publish the list:
template.sendBody("sjms:queue:batch.queue", messages);
----
-[[SJMS-CustomizableTransactionCommitStrategies]]
-Customizable Transaction Commit Strategies (Local JMS Transactions only)
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Customizable Transaction Commit Strategies (Local JMS Transactions only)
SJMS provides a developer the means to create a custom and plugable
transaction strategy through the use of the
@@ -426,9 +398,7 @@ is the
https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/tx/BatchTransactionCommitStrategy.java[`BatchTransactionCommitStrategy`]
which is detailed further in the next section.
-[[SJMS-TransactedBatchConsumersAndProducers]]
-Transacted Batch Consumers & Producers
-++++++++++++++++++++++++++++++++++++++
+#### Transacted Batch Consumers & Producers
The SJMS component has been designed to support the batching of local JMS
transactions on both the Producer and Consumer endpoints. How they are
@@ -499,13 +469,9 @@ Now publish the List with transactions enabled:
template.sendBody("sjms:queue:batch.queue?transacted=true", messages);
----
-[[SJMS-AdditionalNotes]]
-Additional Notes
-^^^^^^^^^^^^^^^^
+### Additional Notes
-[[SJMS-MessageHeaderFormat]]
-Message Header Format
-+++++++++++++++++++++
+#### Message Header Format
The SJMS Component uses the same header format strategy that is used in
the Camel JMS Component. This plugable strategy ensures that messages
@@ -530,9 +496,7 @@ custom strategy for formatting keys.
For the `exchange.in.header`, the following rules apply for the header
values:
-[[SJMS-MessageContent]]
-Message Content
-+++++++++++++++
+#### Message Content
To deliver content over the wire we must ensure that the body of the
message that is being delivered adheres to the JMS Message
@@ -542,9 +506,7 @@ The types, `String`, `CharSequence`, `Date`, `BigDecimal` and `BigInteger` are a
converted to their `toString()` representation. All other types are
dropped.
-[[SJMS-Clustering]]
-Clustering
-++++++++++
+#### Clustering
When using _InOut_ with SJMS in a clustered environment you must either
use TemporaryQueue destinations or use a unique named reply to
@@ -561,17 +523,13 @@ The _InOut_ Consumer uses this strategy as well ensuring that all
responses messages to the included `JMSReplyTo` destination also have the
`JMSCorrelationId` copied from the request as well.
-[[SJMS-TransactionSupporttransactions]]
-Transaction Support [[SJMS-transactions]]
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Transaction Support [[SJMS-transactions]]
SJMS currently only supports the use of internal JMS Transactions. There
is no support for the Camel Transaction Processor or the Java
Transaction API (JTA).
-[[SJMS-DoesSpringlessMeanICantUseSpring]]
-Does Springless Mean I Can't Use Spring?
-++++++++++++++++++++++++++++++++++++++++
+#### Does Springless Mean I Can't Use Spring?
Not at all. Below is an example of the SJMS component using the Spring
DSL:
@@ -589,4 +547,4 @@ DSL:
Springless refers to moving away from the dependency on the Spring JMS
API. A new JMS client API is being developed from the ground up to power
-SJMS.
+SJMS.
\ No newline at end of file
[14/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
Use single line header for adoc files
Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/28429681
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/28429681
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/28429681
Branch: refs/heads/master
Commit: 2842968134a3885958c97405629e02fc87d69dc1
Parents: 11dfcc0
Author: Claus Ibsen <da...@apache.org>
Authored: Wed Jan 11 19:26:34 2017 +0100
Committer: Claus Ibsen <da...@apache.org>
Committed: Wed Jan 11 19:26:34 2017 +0100
----------------------------------------------------------------------
camel-core/readme-eip.adoc | 3 -
camel-core/src/main/docs/bean-component.adoc | 33 +---
camel-core/src/main/docs/bean-language.adoc | 28 +--
camel-core/src/main/docs/binding-component.adoc | 27 +--
camel-core/src/main/docs/browse-component.adoc | 21 +--
camel-core/src/main/docs/class-component.adoc | 25 +--
camel-core/src/main/docs/constant-language.adoc | 16 +-
.../src/main/docs/controlbus-component.adoc | 40 ++---
.../src/main/docs/dataformat-component.adoc | 21 +--
camel-core/src/main/docs/dataset-component.adoc | 57 ++----
camel-core/src/main/docs/direct-component.adoc | 21 +--
.../src/main/docs/direct-vm-component.adoc | 21 +--
.../main/docs/exchangeProperty-language.adoc | 16 +-
camel-core/src/main/docs/file-component.adoc | 169 +++++-------------
camel-core/src/main/docs/file-language.adoc | 36 ++--
camel-core/src/main/docs/gzip-dataformat.adoc | 20 +--
camel-core/src/main/docs/header-language.adoc | 16 +-
.../src/main/docs/language-component.adoc | 29 +--
camel-core/src/main/docs/log-component.adoc | 41 ++---
camel-core/src/main/docs/mock-component.adoc | 60 ++-----
.../src/main/docs/properties-component.adoc | 124 ++++---------
camel-core/src/main/docs/ref-component.adoc | 25 +--
camel-core/src/main/docs/ref-language.adoc | 16 +-
.../src/main/docs/rest-api-component.adoc | 81 +++------
camel-core/src/main/docs/rest-component.adoc | 37 ++--
.../src/main/docs/scheduler-component.adoc | 37 ++--
camel-core/src/main/docs/seda-component.adoc | 45 ++---
.../src/main/docs/serialization-dataformat.adoc | 12 +-
camel-core/src/main/docs/simple-language.adoc | 60 ++-----
camel-core/src/main/docs/string-dataformat.adoc | 20 +--
camel-core/src/main/docs/stub-component.adoc | 21 +--
camel-core/src/main/docs/test-component.adoc | 21 +--
camel-core/src/main/docs/timer-component.adoc | 37 ++--
camel-core/src/main/docs/tokenize-language.adoc | 8 +-
.../src/main/docs/validator-component.adoc | 25 +--
camel-core/src/main/docs/vm-component.adoc | 21 +--
camel-core/src/main/docs/xpath-language.adoc | 84 +++------
camel-core/src/main/docs/xslt-component.adoc | 53 ++----
.../src/main/docs/xtokenize-language.adoc | 8 +-
camel-core/src/main/docs/zip-dataformat.adoc | 20 +--
.../src/main/docs/ahc-ws-component.adoc | 25 +--
.../camel-ahc/src/main/docs/ahc-component.adoc | 77 +++-----
.../src/main/docs/amqp-component.adoc | 29 +--
.../src/main/docs/apns-component.adoc | 45 ++---
.../src/main/docs/asterisk-component.adoc | 16 +-
.../src/main/docs/atmos-component.adoc | 23 +--
.../docs/atmosphere-websocket-component.adoc | 25 +--
.../src/main/docs/atom-component.adoc | 29 +--
.../src/main/docs/avro-component.adoc | 28 +--
.../src/main/docs/avro-dataformat.adoc | 17 +-
.../src/main/docs/aws-cw-component.adoc | 33 +---
.../src/main/docs/aws-ddb-component.adoc | 69 ++------
.../src/main/docs/aws-ddbstream-component.adoc | 53 ++----
.../src/main/docs/aws-ec2-component.adoc | 25 +--
.../src/main/docs/aws-kinesis-component.adoc | 48 ++---
.../src/main/docs/aws-s3-component.adoc | 45 ++---
.../src/main/docs/aws-sdb-component.adoc | 49 ++----
.../src/main/docs/aws-ses-component.adoc | 37 ++--
.../src/main/docs/aws-sns-component.adoc | 37 ++--
.../src/main/docs/aws-sqs-component.adoc | 45 ++---
.../src/main/docs/aws-swf-component.adoc | 48 ++---
.../src/main/docs/barcode-dataformat.adoc | 24 +--
.../src/main/docs/base64-dataformat.adoc | 20 +--
.../src/main/docs/bean-validator-component.adoc | 25 +--
.../src/main/docs/beanio-dataformat.adoc | 24 +--
.../src/main/docs/beanstalk-component.adoc | 29 +--
.../src/main/docs/bindy-dataformat.adoc | 80 +++------
.../src/main/docs/bonita-component.adoc | 24 +--
.../src/main/docs/boon-dataformat.adoc | 20 +--
.../camel-box/src/main/docs/box-component.adoc | 76 +++-----
.../src/main/docs/braintree-component.adoc | 96 +++-------
.../src/main/docs/cache-component.adoc | 89 +++-------
.../src/main/docs/cql-component.adoc | 36 ++--
.../src/main/docs/castor-dataformat.adoc | 20 +--
.../main/docs/chronicle-engine-component.adoc | 5 +-
.../src/main/docs/chunk-component.adoc | 33 +---
.../src/main/docs/cm-sms-component.adoc | 12 +-
.../src/main/docs/cmis-component.adoc | 33 +---
.../src/main/docs/coap-component.adoc | 10 +-
.../src/main/docs/cometd-component.adoc | 33 +---
.../src/main/docs/consul-component.adoc | 16 +-
.../src/main/docs/context-component.adoc | 24 +--
.../src/main/docs/couchdb-component.adoc | 24 +--
.../src/main/docs/crypto-component.adoc | 80 +++------
.../src/main/docs/crypto-dataformat.adoc | 33 ++--
.../src/main/docs/pgp-dataformat.adoc | 52 ++----
.../camel-csv/src/main/docs/csv-dataformat.adoc | 43 ++---
.../camel-cxf/src/main/docs/cxf-component.adoc | 89 +++-------
.../src/main/docs/cxfrs-component.adoc | 44 ++---
.../src/main/docs/disruptor-component.adoc | 40 ++---
.../camel-dns/src/main/docs/dns-component.adoc | 37 ++--
.../src/main/docs/docker-component.adoc | 24 +--
.../src/main/docs/dozer-component.adoc | 37 ++--
.../src/main/docs/drill-component.adoc | 21 +--
.../src/main/docs/dropbox-component.adoc | 96 +++-------
.../src/main/docs/ehcache-component.adoc | 24 +--
.../camel-ejb/src/main/docs/ejb-component.adoc | 33 +---
.../src/main/docs/elasticsearch-component.adoc | 29 +--
.../src/main/docs/elsql-component.adoc | 25 +--
.../src/main/docs/etcd-component.adoc | 6 +-
.../src/main/docs/eventadmin-component.adoc | 28 +--
.../src/main/docs/exec-component.adoc | 49 ++----
.../src/main/docs/facebook-component.adoc | 36 ++--
.../src/main/docs/flatpack-component.adoc | 53 ++----
.../src/main/docs/flatpack-dataformat.adoc | 16 +-
.../src/main/docs/flink-component.adoc | 25 +--
.../camel-fop/src/main/docs/fop-component.adoc | 29 +--
.../src/main/docs/freemarker-component.adoc | 41 ++---
.../camel-ftp/src/main/docs/ftp-component.adoc | 93 +++-------
.../camel-ftp/src/main/docs/ftps-component.adoc | 9 +-
.../camel-ftp/src/main/docs/sftp-component.adoc | 8 +-
.../src/main/docs/ganglia-component.adoc | 36 ++--
.../src/main/docs/geocoder-component.adoc | 24 +--
.../camel-git/src/main/docs/git-component.adoc | 20 +--
.../src/main/docs/github-component.adoc | 20 +--
.../main/docs/google-calendar-component.adoc | 32 +---
.../src/main/docs/google-drive-component.adoc | 28 +--
.../src/main/docs/google-mail-component.adoc | 32 +---
.../src/main/docs/google-pubsub-component.adoc | 36 ++--
.../src/main/docs/gora-component.adoc | 36 ++--
.../src/main/docs/grape-component.adoc | 49 ++----
.../src/main/docs/groovy-language.adoc | 40 ++---
.../src/main/docs/json-gson-dataformat.adoc | 12 +-
.../src/main/docs/guava-eventbus-component.adoc | 24 +--
.../src/main/docs/hazelcast-component.adoc | 148 ++++------------
.../src/main/docs/hbase-component.adoc | 65 ++-----
.../src/main/docs/hdfs-component.adoc | 36 ++--
.../src/main/docs/hdfs2-component.adoc | 44 ++---
.../src/main/docs/hessian-dataformat.adoc | 16 +-
.../src/main/docs/hipchat-component.adoc | 36 ++--
.../camel-hl7/src/main/docs/hl7-dataformat.adoc | 65 ++-----
.../src/main/docs/terser-language.adoc | 13 +-
.../src/main/docs/http-component.adoc | 101 +++--------
.../src/main/docs/http4-component.adoc | 96 +++-------
.../src/main/docs/ibatis-component.adoc | 41 ++---
.../src/main/docs/ical-dataformat.adoc | 17 +-
.../src/main/docs/infinispan-component.adoc | 29 +--
.../src/main/docs/influxdb-component.adoc | 25 +--
.../camel-irc/src/main/docs/irc-component.adoc | 36 ++--
.../src/main/docs/ironmq-component.adoc | 33 ++--
.../src/main/docs/json-jackson-dataformat.adoc | 12 +-
.../src/main/docs/jacksonxml-dataformat.adoc | 52 ++----
.../src/main/docs/javaspace-component.adoc | 33 +---
.../src/main/docs/jaxb-dataformat.adoc | 56 ++----
.../src/main/docs/jbpm-component.adoc | 24 +--
.../src/main/docs/jcache-component.adoc | 6 +-
.../src/main/docs/jclouds-component.adoc | 56 ++----
.../camel-jcr/src/main/docs/jcr-component.adoc | 25 +--
.../src/main/docs/jdbc-component.adoc | 45 ++---
.../src/main/docs/jetty-component.adoc | 81 +++------
.../src/main/docs/jgroups-component.adoc | 44 ++---
.../src/main/docs/jibx-dataformat.adoc | 16 +-
.../src/main/docs/jing-component.adoc | 21 +--
.../src/main/docs/jira-component.adoc | 16 +-
.../camel-jms/src/main/docs/jms-component.adoc | 176 +++++--------------
.../camel-jmx/src/main/docs/jmx-component.adoc | 144 ++++-----------
.../src/main/docs/json-johnzon-dataformat.adoc | 12 +-
.../src/main/docs/jolt-component.adoc | 21 +--
.../camel-josql/src/main/docs/sql-language.adoc | 12 +-
.../camel-jpa/src/main/docs/jpa-component.adoc | 57 ++----
.../camel-jsch/src/main/docs/scp-component.adoc | 21 +--
.../src/main/docs/jsonpath-language.adoc | 40 ++---
.../src/main/docs/jt400-component.adoc | 45 ++---
.../camel-juel/src/main/docs/el-language.adoc | 20 +--
.../src/main/docs/jxpath-language.adoc | 36 ++--
.../src/main/docs/kafka-component.adoc | 41 ++---
.../src/main/docs/kestrel-component.adoc | 45 ++---
.../src/main/docs/krati-component.adoc | 40 ++---
.../src/main/docs/kubernetes-component.adoc | 16 +-
.../src/main/docs/ldap-component.adoc | 37 ++--
.../src/main/docs/linkedin-component.adoc | 60 ++-----
.../src/main/docs/lucene-component.adoc | 48 ++---
.../src/main/docs/lumberjack-component.adoc | 25 +--
.../camel-lzf/src/main/docs/lzf-dataformat.adoc | 20 +--
.../src/main/docs/mail-component.adoc | 87 +++------
.../main/docs/mime-multipart-dataformat.adoc | 24 +--
.../src/main/docs/metrics-component.adoc | 104 +++--------
.../src/main/docs/mina-component.adoc | 49 ++----
.../src/main/docs/mina2-component.adoc | 45 ++---
.../src/main/docs/mllp-component.adoc | 35 +---
.../src/main/docs/gridfs-component.adoc | 49 ++----
.../src/main/docs/mongodb-component.adoc | 128 ++++----------
.../src/main/docs/mongodb3-component.adoc | 124 ++++---------
.../src/main/docs/mqtt-component.adoc | 25 +--
.../camel-msv/src/main/docs/msv-component.adoc | 21 +--
.../src/main/docs/mustache-component.adoc | 33 +---
.../src/main/docs/mvel-component.adoc | 37 ++--
.../camel-mvel/src/main/docs/mvel-language.adoc | 24 +--
.../src/main/docs/mybatis-component.adoc | 61 ++-----
.../src/main/docs/nagios-component.adoc | 25 +--
.../src/main/docs/nats-component.adoc | 16 +-
.../src/main/docs/netty-http-component.adoc | 53 ++----
.../src/main/docs/netty-component.adoc | 73 ++------
.../src/main/docs/netty4-http-component.adoc | 53 ++----
.../src/main/docs/netty4-component.adoc | 67 ++-----
.../camel-ognl/src/main/docs/ognl-language.adoc | 24 +--
.../src/main/docs/olingo2-component.adoc | 37 ++--
.../src/main/docs/openshift-component.adoc | 29 +--
.../main/docs/openstack-cinder-component.adoc | 47 ++---
.../main/docs/openstack-glance-component.adoc | 29 +--
.../main/docs/openstack-keystone-component.adoc | 80 +++------
.../main/docs/openstack-neutron-component.adoc | 69 ++------
.../src/main/docs/openstack-nova-component.adoc | 58 ++----
.../main/docs/openstack-swift-component.adoc | 47 ++---
.../src/main/docs/optaplanner-component.adoc | 33 +---
.../src/main/docs/paho-component.adoc | 29 +--
.../src/main/docs/paxlogging-component.adoc | 24 +--
.../camel-pdf/src/main/docs/pdf-component.adoc | 20 +--
.../src/main/docs/pgevent-component.adoc | 13 +-
.../src/main/docs/lpr-component.adoc | 36 ++--
.../src/main/docs/protobuf-dataformat.adoc | 32 +---
.../src/main/docs/quartz-component.adoc | 45 ++---
.../src/main/docs/quartz2-component.adoc | 49 ++----
.../src/main/docs/quickfix-component.adoc | 112 +++---------
.../src/main/docs/rabbitmq-component.adoc | 29 +--
.../src/main/docs/restlet-component.adoc | 49 ++----
.../camel-rmi/src/main/docs/rmi-component.adoc | 21 +--
.../src/main/docs/routebox-component.adoc | 36 ++--
.../camel-rss/src/main/docs/rss-component.adoc | 33 +---
.../camel-rss/src/main/docs/rss-dataformat.adoc | 10 +-
.../src/main/docs/salesforce-component.adoc | 68 ++-----
.../src/main/docs/sap-netweaver-component.adoc | 29 +--
.../src/main/docs/xquery-component.adoc | 44 ++---
.../src/main/docs/xquery-language.adoc | 44 ++---
.../src/main/docs/schematron-component.adoc | 25 +--
.../src/main/docs/javaScript-language.adoc | 36 ++--
.../src/main/docs/php-language.adoc | 32 +---
.../src/main/docs/python-language.adoc | 36 ++--
.../src/main/docs/ruby-language.adoc | 36 ++--
.../src/main/docs/servicenow-component.adoc | 20 +--
.../src/main/docs/servlet-component.adoc | 49 ++----
.../camel-sip/src/main/docs/sip-component.adoc | 24 +--
.../src/main/docs/sjms-batch-component.adoc | 16 +-
.../src/main/docs/sjms-component.adoc | 88 +++-------
.../src/main/docs/slack-component.adoc | 25 +--
.../src/main/docs/smpp-component.adoc | 49 ++----
.../main/docs/yaml-snakeyaml-dataformat.adoc | 20 +--
.../src/main/docs/snmp-component.adoc | 29 +--
.../src/main/docs/soapjaxb-dataformat.adoc | 52 ++----
.../src/main/docs/solr-component.adoc | 29 +--
.../src/main/docs/spark-rest-component.adoc | 33 +---
.../src/main/docs/spark-component.adoc | 49 ++----
.../src/main/docs/splunk-component.adoc | 37 ++--
.../src/main/docs/spring-batch-component.adoc | 40 ++---
.../main/docs/spring-integration-component.adoc | 33 +---
.../src/main/docs/spring-ldap-component.adoc | 41 ++---
.../src/main/docs/spring-redis-component.adoc | 29 +--
.../src/main/docs/spring-ws-component.adoc | 65 ++-----
.../src/main/docs/spel-language.adoc | 36 ++--
.../src/main/docs/spring-event-component.adoc | 17 +-
.../camel-sql/src/main/docs/sql-component.adoc | 60 ++-----
.../src/main/docs/sql-stored-component.adoc | 21 +--
.../camel-ssh/src/main/docs/ssh-component.adoc | 29 +--
.../src/main/docs/stax-component.adoc | 29 +--
.../src/main/docs/stomp-component.adoc | 25 +--
.../src/main/docs/stream-component.adoc | 25 +--
.../main/docs/string-template-component.adoc | 37 ++--
.../src/main/docs/syslog-dataformat.adoc | 29 +--
.../src/main/docs/tidyMarkup-dataformat.adoc | 20 +--
.../src/main/docs/tarfile-dataformat.adoc | 24 +--
.../src/main/docs/telegram-component.adoc | 36 ++--
.../src/main/docs/twitter-component.adoc | 68 ++-----
.../src/main/docs/undertow-component.adoc | 29 +--
.../src/main/docs/univocity-csv-dataformat.adoc | 41 ++---
.../main/docs/univocity-fixed-dataformat.adoc | 41 ++---
.../src/main/docs/univocity-tsv-dataformat.adoc | 41 ++---
.../src/main/docs/velocity-component.adoc | 41 ++---
.../src/main/docs/vertx-component.adoc | 21 +--
.../src/main/docs/weather-component.adoc | 28 +--
.../src/main/docs/websocket-component.adoc | 33 +---
.../src/main/docs/xmlBeans-dataformat.adoc | 12 +-
.../src/main/docs/xmljson-dataformat.adoc | 40 ++---
.../src/main/docs/xmlrpc-component.adoc | 32 +---
.../src/main/docs/xmlrpc-dataformat.adoc | 10 +-
.../src/main/docs/secureXML-dataformat.adoc | 56 ++----
.../src/main/docs/xmlsecurity-component.adoc | 48 ++---
.../src/main/docs/xmpp-component.adoc | 25 +--
.../src/main/docs/json-xstream-dataformat.adoc | 24 +--
.../src/main/docs/xstream-dataformat.adoc | 24 +--
.../src/main/docs/yammer-component.adoc | 44 ++---
.../src/main/docs/zipfile-dataformat.adoc | 24 +--
.../src/main/docs/zookeeper-component.adoc | 36 ++--
282 files changed, 3002 insertions(+), 8010 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/readme-eip.adoc
----------------------------------------------------------------------
diff --git a/camel-core/readme-eip.adoc b/camel-core/readme-eip.adoc
index 1e7285e..a31e5b1 100644
--- a/camel-core/readme-eip.adoc
+++ b/camel-core/readme-eip.adoc
@@ -126,9 +126,6 @@ Enterprise Integration Patterns
| link:src/main/docs/eips/serviceCall-eip.adoc[Service Call] +
`<serviceCall>` | Remote service call definition
-| link:src/main/docs/eips/serviceCallConfiguration-eip.adoc[Service Call Configuration] +
-`<serviceCallConfiguration>` | Remote service call configuration
-
| link:src/main/docs/eips/setBody-eip.adoc[Set Body] +
`<setBody>` | Sets the contents of the message body
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/bean-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/bean-component.adoc b/camel-core/src/main/docs/bean-component.adoc
index b35606b..aef918a 100644
--- a/camel-core/src/main/docs/bean-component.adoc
+++ b/camel-core/src/main/docs/bean-component.adoc
@@ -1,10 +1,8 @@
-# Bean Component
+## Bean Component
The *bean:* component binds beans to Camel message exchanges.
-[[Bean-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------
@@ -14,9 +12,7 @@ bean:beanID[?options]
Where *beanID* can be any string which is used to look up the bean in
the link:registry.html[Registry]
-[[Bean-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -46,9 +42,7 @@ The Bean component supports 6 endpoint options which are listed below:
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Bean-Using]]
-Using
-^^^^^
+### Using
The object instance that is used to consume messages must be explicitly
registered with the link:registry.html[Registry]. For example, if you
@@ -82,9 +76,7 @@ And the same route using Spring DSL:
</route>
----------------------------
-[[Bean-Beanasendpoint]]
-Bean as endpoint
-^^^^^^^^^^^^^^^^
+### Bean as endpoint
Camel also supports invoking link:bean.html[Bean] as an Endpoint. In the
route below:
@@ -97,9 +89,7 @@ Camel will use link:bean-binding.html[Bean Binding] to invoke the
`sayHello` method, by converting the Exchange's In body to the `String`
type and storing the output of the method on the Exchange Out body.
-[[Bean-JavaDSLbeansyntax]]
-Java DSL bean syntax
-^^^^^^^^^^^^^^^^^^^^
+### Java DSL bean syntax
Java DSL comes with syntactic sugar for the link:bean.html[Bean]
component. Instead of specifying the bean explicitly as the endpoint
@@ -131,9 +121,7 @@ from("direct:start").bean(new ExampleBean(), "methodName");
from("direct:start").bean(ExampleBean.class);
---------------------------------------------------------------
-[[Bean-BeanBinding]]
-Bean Binding
-^^^^^^^^^^^^
+### Bean Binding
How bean methods to be invoked are chosen (if they are not specified
explicitly through the *method* parameter) and how parameter values are
@@ -142,9 +130,7 @@ link:bean-binding.html[Bean Binding] mechanism which is used throughout
all of the various link:bean-integration.html[Bean Integration]
mechanisms in Camel.
-[[Bean-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -153,5 +139,4 @@ See Also
* link:class.html[Class] component
* link:bean-binding.html[Bean Binding]
-* link:bean-integration.html[Bean Integration]
-
+* link:bean-integration.html[Bean Integration]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/bean-language.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/bean-language.adoc b/camel-core/src/main/docs/bean-language.adoc
index 5f8d514..f89399a 100644
--- a/camel-core/src/main/docs/bean-language.adoc
+++ b/camel-core/src/main/docs/bean-language.adoc
@@ -1,4 +1,4 @@
-# Bean method Language
+## Bean method Language
The purpose of the Bean Language is to be able to implement an
link:expression.html[Expression] or link:predicate.html[Predicate] using
@@ -18,9 +18,7 @@ link:message.html[Message] Exchange to the method parameters; so you can
annotate the bean to extract headers or other expressions such as
link:xpath.html[XPath] or link:xquery.html[XQuery] from the message.
-[[Bean-Options]]
-Bean Options
-^^^^^^^^^^^^
+### Bean Options
// language options: START
The Bean method language supports 5 options which are listed below.
@@ -41,9 +39,7 @@ The Bean method language supports 5 options which are listed below.
// language options: END
-[[BeanLanguage-UsingBeanExpressionsfromtheJavaDSL]]
-Using Bean Expressions from the Java DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using Bean Expressions from the Java DSL
[source,java]
----------------------------------------------
@@ -52,9 +48,7 @@ from("activemq:topic:OrdersTopic").
to("activemq:BigSpendersQueue");
----------------------------------------------
-[[BeanLanguage-UsingBeanExpressionsfromXML]]
-Using Bean Expressions from XML
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using Bean Expressions from XML
[source,xml]
--------------------------------------------------
@@ -72,9 +66,7 @@ Using Bean Expressions from XML
Note, the `bean` attribute of the method expression element is now
deprecated. You should now make use of `ref` attribute instead.
-[[BeanLanguage-Writingtheexpressionbean]]
-Writing the expression bean
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Writing the expression bean
The bean in the above examples is just any old Java Bean with a method
called isGoldCustomer() that returns some object that is easily
@@ -110,9 +102,7 @@ So you can bind parameters of the method to the Exchange, the
link:message.html[Message] or individual headers, properties, the body
or other expressions.
-[[BeanLanguage-Nonregistrybeans]]
-Non registry beans
-^^^^^^^^^^^^^^^^^^
+### Non registry beans
The link:bean-language.html[Bean Language] also supports invoking beans
that isn't registered in the link:registry.html[Registry]. This is
@@ -170,8 +160,6 @@ Which also can be done in a bit shorter and nice way:
to("activemq:BigSpendersQueue");
------------------------------------------------------
-[[BeanLanguage-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
-The Bean language is part of *camel-core*.
+The Bean language is part of *camel-core*.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/binding-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/binding-component.adoc b/camel-core/src/main/docs/binding-component.adoc
index 14533d5..61cc1e2 100644
--- a/camel-core/src/main/docs/binding-component.adoc
+++ b/camel-core/src/main/docs/binding-component.adoc
@@ -1,7 +1,4 @@
-# Binding Component
-[[Binding-Binding]]
-Binding
--------
+## Binding Component
In Camel terms a _binding_ is a way of wrapping an
link:endpoint.html[Endpoint] in a contract; such as a
@@ -17,9 +14,7 @@ provide a way of wrapping Camel endpoints with contracts inside the
Camel framework itself; so you can use them easily inside any Camel
route.
-[[Binding-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -46,9 +41,7 @@ The Binding component supports 6 endpoint options which are listed below:
// endpoint options: END
-[[Binding-UsingBindings]]
-Using Bindings
-~~~~~~~~~~~~~~
+### Using Bindings
A Binding is currently a bean which defines the contract (though we'll
hopefully add bindings to the Camel DSL).
@@ -56,9 +49,7 @@ hopefully add bindings to the Camel DSL).
There are a few approaches to defining a bound endpoint (i.e. an
endpoint bound with a Binding).
-[[Binding-UsingthebindingURI]]
-Using the binding URI
-^^^^^^^^^^^^^^^^^^^^^
+### Using the binding URI
You can prefix any endpoint URI with *binding:nameOfBinding:* where
_nameOfBinding_ is the name of the Binding bean in your registry.
@@ -72,9 +63,7 @@ Here we are using the "jaxb" binding which may, for example, use the
JAXB link:data-format.html[Data Format] to marshal and unmarshal
messages.
-[[Binding-UsingaBindingComponent]]
-Using a BindingComponent
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Using a BindingComponent
There is a link:component.html[Component] called BindingComponent which
can be configured in your link:registry.html[Registry] by dependency
@@ -101,9 +90,7 @@ which would be using the queueus "foo.myQueue" and "foo.anotherQueue"
and would use the given Jackson link:data-format.html[Data Format] to
marshal on and off the queue.
-[[Binding-WhentouseBindings]]
-When to use Bindings
-~~~~~~~~~~~~~~~~~~~~
+### When to use Bindings
If you only use an endpoint once in a single route; a binding may
actually be more complex and more work than just using the 'raw'
@@ -122,4 +109,4 @@ BindingComponent to wrap the endpoints in the binding of your choice.
So bindings are a composition tool really; only use them when they make
sense - the extra complexity may not be worth it unless you have lots of
-routes or endpoints.
+routes or endpoints.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/browse-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/browse-component.adoc b/camel-core/src/main/docs/browse-component.adoc
index 925246f..c26fd95 100644
--- a/camel-core/src/main/docs/browse-component.adoc
+++ b/camel-core/src/main/docs/browse-component.adoc
@@ -1,13 +1,11 @@
-# Browse Component
+## Browse Component
The Browse component provides a simple
link:browsableendpoint.html[BrowsableEndpoint] which can be useful for
testing, visualisation tools or debugging. The exchanges sent to the
endpoint are all available to be browsed.
-[[Browse-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------
@@ -17,9 +15,7 @@ browse:someName[?options]
Where *someName* can be any string to uniquely identify the endpoint.
-[[Gora-Options]]
-Options
-~~~~~~~
+### Options
// component options: START
@@ -45,9 +41,7 @@ The Browse component supports 5 endpoint options which are listed below:
// endpoint options: END
-[[Browse-Sample]]
-Sample
-^^^^^^
+### Sample
In the route below, we insert a `browse:` component to be able to browse
the Exchanges that are passing through:
@@ -75,12 +69,9 @@ We can now inspect the received exchanges from within the Java code:
}
--------------------------------------------------------------------------------------------------------
-[[Browse-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/camel-core/src/main/docs/class-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/class-component.adoc b/camel-core/src/main/docs/class-component.adoc
index 5b0a96d..c1a904a 100644
--- a/camel-core/src/main/docs/class-component.adoc
+++ b/camel-core/src/main/docs/class-component.adoc
@@ -1,4 +1,4 @@
-# Class Component
+## Class Component
*Available as of Camel 2.4*
@@ -7,9 +7,7 @@ in the same way as the link:bean.html[Bean] component but instead of
looking up beans from a link:registry.html[Registry] it creates the bean
based on the class name.
-[[Class-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------
@@ -19,9 +17,7 @@ class:className[?options]
Where *className* is the fully qualified class name to create and use as
bean.
-[[Class-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -48,9 +44,7 @@ The Class component supports 6 endpoint options which are listed below:
// endpoint options: END
-[[Class-Using]]
-Using
-^^^^^
+### Using
You simply use the *class* component just as the link:bean.html[Bean]
component but by specifying the fully qualified classname instead. +
@@ -69,9 +63,7 @@ example `hello`:
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean?method=hello").to("mock:result");
--------------------------------------------------------------------------------------------------------------
-[[Class-Settingpropertiesonthecreatedinstance]]
-Setting properties on the created instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Setting properties on the created instance
In the endpoint uri you can specify properties to set on the created
instance, for example if it has a `setPrefix` method:
@@ -112,9 +104,7 @@ id `foo` and invoke the `setCool` method on the created instance of the
TIP:See more details at the link:bean.html[Bean] component as the *class*
component works in much the same way.
-[[Class-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -123,5 +113,4 @@ See Also
* link:bean.html[Bean]
* link:bean-binding.html[Bean Binding]
-* link:bean-integration.html[Bean Integration]
-
+* link:bean-integration.html[Bean Integration]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/constant-language.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/constant-language.adoc b/camel-core/src/main/docs/constant-language.adoc
index c045e1f..29f7795 100644
--- a/camel-core/src/main/docs/constant-language.adoc
+++ b/camel-core/src/main/docs/constant-language.adoc
@@ -1,11 +1,9 @@
-# Constant Language
+## Constant Language
The Constant Expression Language is really just a way to specify
constant strings as a type of expression.
-[[Constant-Options]]
-Constant Options
-^^^^^^^^^^^^^^^^
+### Constant Options
// language options: START
@@ -23,9 +21,7 @@ The Constant language supports 1 options which are listed below.
// language options: END
-[[Constant-Exampleusage]]
-Example usage
-^^^^^^^^^^^^^
+### Example usage
The setHeader element of the Spring DSL can utilize a constant
expression like:
@@ -52,8 +48,6 @@ And the same example using Java DSL:
from("seda:a").setHeader("theHeader", constant("the value")).to("mock:b");
--------------------------------------------------------------------------
-[[Constant-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
-The Constant language is part of *camel-core*.
+The Constant language is part of *camel-core*.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/controlbus-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/controlbus-component.adoc b/camel-core/src/main/docs/controlbus-component.adoc
index 24eca34..5780e04 100644
--- a/camel-core/src/main/docs/controlbus-component.adoc
+++ b/camel-core/src/main/docs/controlbus-component.adoc
@@ -1,7 +1,5 @@
-# Control Bus Component
-[[ControlBus-ControlBus]]
-ControlBus
-^^^^^^^^^^
+## Control Bus Component
+### ControlBus
The http://www.eaipatterns.com/ControlBus.html[Control Bus] from the
link:enterprise-integration-patterns.html[EIP patterns] allows for the
@@ -26,9 +24,7 @@ link:controlbus-component.html[ControlBus Component] that allows you to
send messages to a control bus link:endpoint.html[Endpoint] that reacts
accordingly.
-[[ControlBus-ControlBusComponent]]
-ControlBus Component
-~~~~~~~~~~~~~~~~~~~~
+### ControlBus Component
*Available as of Camel 2.11*
@@ -47,9 +43,7 @@ controlbus:command[?options]
Where *command* can be any string to identify which type of command to
use.
-[[ControlBus-Commands]]
-Commands
-^^^^^^^^
+### Commands
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -62,9 +56,7 @@ evaluating the message body. If there is any result from the evaluation,
then the result is put in the message body.
|=======================================================================
-[[ControlBus-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -95,13 +87,9 @@ The Control Bus component supports 7 endpoint options which are listed below:
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[ControlBus-Samples]]
-Samples
-^^^^^^^
+### Samples
-[[ControlBus-Usingroutecommand]]
-Using route command
-+++++++++++++++++++
+#### Using route command
The route command allows you to do common tasks on a given route very
easily, for example to start a route, you can send an empty message to
@@ -146,9 +134,7 @@ just omit the routeId parameter as shown below:
String xml = template.requestBody("controlbus:route?action=stats", null, String.class);
---------------------------------------------------------------------------------------
-[[ControlBus-Usinglanguage]]
-Using link:simple.html[Simple] language
-+++++++++++++++++++++++++++++++++++++++
+#### Using link:simple.html[Simple] language
You can use the link:simple.html[Simple] language with the control bus,
for example to stop a specific route, you can send a message to the
@@ -186,9 +172,7 @@ message we sent to the control bus component.
TIP:You can also use other languages such as link:groovy.html[Groovy], etc.
-[[ControlBus-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -199,13 +183,11 @@ See Also
* link:jmx.html[JMX] Component
* Using link:camel-jmx.html[JMX] with Camel
-[[ControlBus-UsingThisPattern]]
-Using This Pattern
-++++++++++++++++++
+#### Using This Pattern
If you would like to use this EIP Pattern then please read the
link:getting-started.html[Getting Started], you may also find the
link:architecture.html[Architecture] useful particularly the description
of link:endpoint.html[Endpoint] and link:uris.html[URIs]. Then you could
try out some of the link:examples.html[Examples] first before trying
-this pattern out.
+this pattern out.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/dataformat-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/dataformat-component.adoc b/camel-core/src/main/docs/dataformat-component.adoc
index 73738a3..d1bd85d 100644
--- a/camel-core/src/main/docs/dataformat-component.adoc
+++ b/camel-core/src/main/docs/dataformat-component.adoc
@@ -1,13 +1,11 @@
-# Data Format Component
+## Data Format Component
*Available as of Camel 2.12*
The *dataformat:* component allows to use link:data-format.html[Data
Format] as a Camel link:component.html[Component].
-[[DataFormatComponent-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------------
@@ -20,9 +18,7 @@ then followed by the operation which must either be `marshal` or
Format] in use. See the link:data-format.html[Data Format] documentation
for which options it support.
-[[DataFormatComponent-Options]]
-DataFormat Options
-^^^^^^^^^^^^^^^^^^
+### DataFormat Options
// component options: START
@@ -46,9 +42,7 @@ The Data Format component supports 3 endpoint options which are listed below:
// endpoint options: END
-[[DataFormatComponent-Samples]]
-Samples
-^^^^^^^
+### Samples
For example to use the link:jaxb.html[JAXB] link:data-format.html[Data
Format] we can do as follows:
@@ -73,13 +67,10 @@ And in XML DSL you do:
</camelContext>
-----------------------------------------------------------------------
-[[DataFormatComponent-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:data-format.html[Data Format]
-
+* link:data-format.html[Data Format]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/dataset-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/dataset-component.adoc b/camel-core/src/main/docs/dataset-component.adoc
index 62c5585..3f2fc135 100644
--- a/camel-core/src/main/docs/dataset-component.adoc
+++ b/camel-core/src/main/docs/dataset-component.adoc
@@ -1,4 +1,4 @@
-# Dataset Component
+## Dataset Component
link:testing.html[Testing] of distributed and asynchronous processing is
notoriously difficult. The link:mock.html[Mock], link:test.html[Test]
@@ -18,9 +18,7 @@ data set is received.
Camel will use the link:log.html[throughput logger] when sending
dataset's.
-[[DataSet-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------
@@ -40,9 +38,7 @@ some implementations that can be used for testing:
and�`org.apache.camel.component.dataset.FileDataSet`, all of which
extend `DataSetSupport`.
-[[DataSet-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -86,9 +82,7 @@ The Dataset component supports 20 endpoint options which are listed below:
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[DataSet-ConfiguringDataSet]]
-Configuring DataSet
-^^^^^^^^^^^^^^^^^^^
+### Configuring DataSet
Camel will lookup in the link:registry.html[Registry] for a bean
implementing the DataSet interface. So you can register your own DataSet
@@ -101,9 +95,7 @@ as:
</bean>
--------------------------------------------------------
-[[DataSet-Example]]
-Example
-^^^^^^^
+### Example
For example, to test that a set of messages are sent to a queue and then
consumed from the queue without losing any messages:
@@ -126,16 +118,12 @@ data set is and what the messages look like etc. �
�
-[[DataSet-DataSetSupport(abstractclass)]]
-`DataSetSupport`�(abstract class)
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### `DataSetSupport`�(abstract class)
The DataSetSupport abstract class is a nice starting point for new
DataSets, and provides some useful features to derived classes.
-[[DataSet-PropertiesonDataSetSupport]]
-Properties on DataSetSupport
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Properties on DataSetSupport
[width="100%",cols="10%,10%,10%,70%",options="header",]
|=======================================================================
|Property |Type |Default |Description
@@ -153,15 +141,11 @@ progress. Useful for showing progress of a large load test. If < 0, then
`size` / 5, if is 0 then `size`, else set to `reportCount` value.
|=======================================================================
-[[DataSet-SimpleDataSet]]
-`SimpleDataSet`
-^^^^^^^^^^^^^^^
+### `SimpleDataSet`
The `SimpleDataSet` extends `DataSetSupport`, and adds a default body.
-[[DataSet-AdditionalPropertiesonSimpleDataSet]]
-Additional Properties on SimpleDataSet
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional Properties on SimpleDataSet
[width="100%",cols="10%,10%,10%,70%",options="header",]
|=======================================================================
@@ -174,16 +158,12 @@ configure the `SimpleDataSet` to use it by setting the
`outputTransformer` property.
|=======================================================================
-[[DataSet-ListDataSet(Camel2.17)]]
-`ListDataSet (Camel 2.17)`
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### `ListDataSet (Camel 2.17)`
The List`DataSet`�extends�`DataSetSupport`, and adds a list of default
bodies.
-[[DataSet-AdditionalPropertiesonListDataSet]]
-Additional Properties on ListDataSet
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional Properties on ListDataSet
[width="100%",cols="10%,10%,10%,70%",options="header",]
|=======================================================================
@@ -204,16 +184,12 @@ the payload for the exchange will be selected using the modulus of the
`CamelDataSetIndex % defaultBodies.size()` )
|=======================================================================
-[[DataSet-FileDataSetCamel2.17]]
-FileDataSet (Camel 2.17)
-^^^^^^^^^^^^^^^^^^^^^^^^
+### FileDataSet (Camel 2.17)
The�`SimpleDataSet`�extends `ListDataSet`, and adds support for loading
the bodies from a file.
-[[DataSet-AdditionalPropertiesonFileDataSet]]
-Additional Properties on FileDataSet
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional Properties on FileDataSet
[width="100%",cols="10%,10%,10%,70%",options="header",]
|=======================================================================
@@ -225,13 +201,10 @@ Additional Properties on FileDataSet
the file into multiple payloads.
|=======================================================================
-[[DataSet-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:spring-testing.html[Spring Testing]
-
+* link:spring-testing.html[Spring Testing]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/direct-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/direct-component.adoc b/camel-core/src/main/docs/direct-component.adoc
index 6afdb46..05f3055 100644
--- a/camel-core/src/main/docs/direct-component.adoc
+++ b/camel-core/src/main/docs/direct-component.adoc
@@ -1,4 +1,4 @@
-# Direct Component
+## Direct Component
The *direct:* component provides direct, synchronous invocation of any
consumers when a producer sends a message exchange. +
@@ -13,9 +13,7 @@ TIP:*Connection to other camel contexts*
The link:vm.html[VM] component provides connections between Camel
contexts as long they run in the same *JVM*.
-[[Direct-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,text]
-------------------------
@@ -24,9 +22,7 @@ direct:someName[?options]
Where *someName* can be any string to uniquely identify the endpoint
-[[Direct-Options]]
-Options
-^^^^^^^
+### Options
@@ -68,9 +64,7 @@ The Direct component supports 8 endpoint options which are listed below:
// endpoint options: END
-[[Direct-Samples]]
-Samples
-^^^^^^^
+### Samples
In the route below we use the direct component to link the two routes
together:
@@ -106,14 +100,11 @@ And the sample using spring DSL:
See also samples from the link:seda.html[SEDA] component, how they can
be used together.
-[[Direct-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:seda.html[SEDA]
-* link:vm.html[VM]
-
+* link:vm.html[VM]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/direct-vm-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/direct-vm-component.adoc b/camel-core/src/main/docs/direct-vm-component.adoc
index 82629b3..9ff9692 100644
--- a/camel-core/src/main/docs/direct-vm-component.adoc
+++ b/camel-core/src/main/docs/direct-vm-component.adoc
@@ -1,4 +1,4 @@
-# Direct VM Component
+## Direct VM Component
*Available as of Camel 2.10*
@@ -26,9 +26,7 @@ Transactions - Tx.
image:direct-vm.data/camel-direct-vm.png[image]
-[[Direct-VM-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------
@@ -37,9 +35,7 @@ direct-vm:someName
Where *someName* can be any string to uniquely identify the endpoint
-[[Direct-VM-Options]]
-Options
-^^^^^^^
+### Options
@@ -85,9 +81,7 @@ The Direct VM component supports 10 endpoint options which are listed below:
// endpoint options: END
-[[Direct-VM-Samples]]
-Samples
-^^^^^^^
+### Samples
In the route below we use the direct component to link the two routes
together:
@@ -125,9 +119,7 @@ And the sample using spring DSL:
</route>
--------------------------------------------------
-[[Direct-VM-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -136,5 +128,4 @@ See Also
* link:direct.html[Direct]
* link:seda.html[SEDA]
-* link:vm.html[VM]
-
+* link:vm.html[VM]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/exchangeProperty-language.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/exchangeProperty-language.adoc b/camel-core/src/main/docs/exchangeProperty-language.adoc
index ecb7e86..fd3c1f0 100644
--- a/camel-core/src/main/docs/exchangeProperty-language.adoc
+++ b/camel-core/src/main/docs/exchangeProperty-language.adoc
@@ -1,11 +1,9 @@
-# ExchangeProperty Language
+## ExchangeProperty Language
The ExchangeProperty Expression Language allows you to extract values of
named exchange properties.
-[[ExchangeProperty-Options]]
-Exchange Property Options
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Exchange Property Options
// language options: START
The ExchangeProperty language supports 1 options which are listed below.
@@ -21,9 +19,7 @@ The ExchangeProperty language supports 1 options which are listed below.
{% endraw %}
// language options: END
-[[ExchangeProperty-Exampleusage]]
-Example usage
-^^^^^^^^^^^^^
+### Example usage
The recipientList element of the Spring DSL can utilize a
exchangeProperty expression like:
@@ -62,8 +58,6 @@ call)
from("direct:a").recipientList().exchangeProperty("myProperty");
------------------------------------------------------------------
-[[ExchangeProperty-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
-The ExchangeProperty language is part of *camel-core*.
+The ExchangeProperty language is part of *camel-core*.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/file-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/file-component.adoc b/camel-core/src/main/docs/file-component.adoc
index df80d2e..5b9f760 100644
--- a/camel-core/src/main/docs/file-component.adoc
+++ b/camel-core/src/main/docs/file-component.adoc
@@ -1,12 +1,10 @@
-# File Component
+## File Component
The File component provides access to file systems, allowing files to be
processed by any other Camel link:components.html[Components] or
messages from other components to be saved to disk.
-[[File2-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------
@@ -47,13 +45,9 @@ your environment. To help with this Camel provides different `readLock`
options and `doneFileName` option that you can use. See also the section
_Consuming files from folders where others drop files directly_.
-[[File2-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
-[[File2-Options]]
-File2 Options
-+++++++++++++
+#### File2 Options
// component options: START
@@ -157,16 +151,12 @@ The File component supports 81 endpoint options which are listed below:
-[[File2-Defaultbehaviorforfileproducer]]
-Default behavior for file producer
-++++++++++++++++++++++++++++++++++
+#### Default behavior for file producer
* By default it will override any existing file, if one exist with the
same name.
-[[File2-MoveandDeleteoperations]]
-Move and Delete operations
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Move and Delete operations
Any move or delete operations is executed after (post command) the
routing has completed; so during processing of the `Exchange` the file
@@ -230,9 +220,7 @@ You can combine the *pre* move and the regular move:
So in this situation, the file is in the `inprogress` folder when being
processed and after it's processed, it's moved to the `.done` folder.
-[[File2-FinegrainedcontroloverMoveandPreMoveoption]]
-Fine grained control over Move and PreMove option
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### Fine grained control over Move and PreMove option
The *move* and *preMove* options
are�link:expression.html[Expression]-based, so we have the full power of
@@ -254,9 +242,7 @@ the pattern, we can do:
move=backup/${date:now:yyyyMMdd}/${file:name}
---------------------------------------------
-[[File2-AboutmoveFailed]]
-About moveFailed
-++++++++++++++++
+#### About moveFailed
The `moveFailed` option allows you to move files that *could not* be
processed succesfully to another location such as a error folder of your
@@ -266,15 +252,11 @@ timestamp you can use
See more examples at link:file-language.html[File Language]
-[[File2-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
The following headers are supported by this component:
-[[File2-Fileproduceronly]]
-File producer only
-++++++++++++++++++
+#### File producer only
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -298,9 +280,7 @@ if the option `fileName` has been configured, then this is still being
evaluated.
|=======================================================================
-[[File2-Fileconsumeronly]]
-File consumer only
-++++++++++++++++++
+#### File consumer only
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -333,15 +313,11 @@ relative filename. For absolute files this is the absolute path.
*Camel 2.10.3 and older* the type is `Date`.
|=======================================================================
-[[File2-BatchConsumer]]
-Batch Consumer
-^^^^^^^^^^^^^^
+### Batch Consumer
This component implements the link:batch-consumer.html[Batch Consumer].
-[[File2-ExchangeProperties,fileconsumeronly]]
-Exchange Properties, file consumer only
-+++++++++++++++++++++++++++++++++++++++
+#### Exchange Properties, file consumer only
As the file consumer implements the�`BatchConsumer` it supports batching
the files it polls. By batching we mean that Camel will add the
@@ -365,9 +341,7 @@ This allows you for instance to know how many files exist in this batch
and for instance let the link:aggregator2.html[Aggregator2] aggregate
this number of files.
-[[File2-Usingcharset]]
-Using charset
-^^^^^^^^^^^^^
+### Using charset
*Available as of Camel 2.9.3* +
The charset option allows for configuring an encoding of the files on
@@ -455,9 +429,7 @@ DEBUG GenericFileConverter - Read file /Users/davsclaus/workspace/came
DEBUG FileOperations - Using Reader to write file: target/charset/output.txt with charset: iso-8859-1
----------------------------------------------------------------------------------------------------------------------------------------------
-[[File2-Commongotchaswithfolderandfilenames]]
-Common gotchas with folder and filenames
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Common gotchas with folder and filenames
When Camel is producing files (writing files) there are a few gotchas
affecting how to set a filename of your choice. By default, Camel will
@@ -497,18 +469,14 @@ And a syntax where we set the filename on the endpoint with the
from("direct:report").to("file:target/reports/?fileName=report.txt");
---------------------------------------------------------------------
-[[File2-FilenameExpression]]
-Filename Expression
-^^^^^^^^^^^^^^^^^^^
+### Filename Expression
Filename can be set either using the *expression* option or as a
string-based link:file-language.html[File Language] expression in the
`CamelFileName` header. See the link:file-language.html[File Language]
for syntax and samples.
-[[File2-Consumingfilesfromfolderswhereothersdropfilesdirectly]]
-Consuming files from folders where others drop files directly
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Consuming files from folders where others drop files directly
Beware if you consume files from a folder where other applications write
files to directly. Take a look at the different readLock options to see
@@ -523,9 +491,7 @@ good at detecting this. You may also want to look at the doneFileName
option, which uses a marker file (done file) to signal when a file is
done and ready to be consumed.
-[[File2-Usingdonefiles]]
-Using done files
-^^^^^^^^^^^^^^^^
+### Using done files
*Available as of Camel 2.6*
@@ -573,9 +539,7 @@ from("file:bar?doneFileName=ready-${file:name}");
* `hello.txt` - is the file to be consumed
* `ready-hello.txt` - is the associated done file
-[[File2-Writingdonefiles]]
-Writing done files
-^^^^^^^^^^^^^^^^^^
+### Writing done files
*Available as of Camel 2.6*
@@ -622,22 +586,16 @@ was `foo.txt` in the same directory as the target file.
Will for example create a file named `foo.done` if the target file was
`foo.txt` in the same directory as the target file.
-[[File2-Samples]]
-Samples
-^^^^^^^
+### Samples
-[[File2-Readfromadirectoryandwritetoanotherdirectory]]
-Read from a directory and write to another directory
-++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Read from a directory and write to another directory
[source,java]
-----------------------------------------------------------
from("file://inputdir/?delete=true").to("file://outputdir")
-----------------------------------------------------------
-[[File2-Readfromadirectoryandwritetoanotherdirectoryusingaoverruledynamicname]]
-Read from a directory and write to another directory using a overrule dynamic name
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Read from a directory and write to another directory using a overrule dynamic name
[source,java]
---------------------------------------------------------------------------------------------
@@ -648,9 +606,7 @@ Listen on a directory and create a message for each file dropped there.
Copy the contents to the `outputdir` and delete the file in the
`inputdir`.
-[[File2-Readingrecursivelyfromadirectoryandwritingtoanother]]
-Reading recursively from a directory and writing to another
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Reading recursively from a directory and writing to another
[source,java]
--------------------------------------------------------------------------
@@ -698,9 +654,7 @@ outputdir/foo.txt
outputdir/bar.txt
-----------------
-[[File2-Readingfromadirectoryandthedefaultmoveoperation]]
-Reading from a directory and the default move operation
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Reading from a directory and the default move operation
Camel will by default move any processed file into a `.camel`
subdirectory in the directory the file was consumed from.
@@ -729,9 +683,7 @@ outputdir/foo.txt
outputdir/sub/bar.txt
---------------------------
-[[File2-Readfromadirectoryandprocessthemessageinjava]]
-Read from a directory and process the message in java
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Read from a directory and process the message in java
[source,java]
-----------------------------------------------------------
@@ -746,17 +698,13 @@ from("file://inputdir/").process(new Processor() {
The body will be a `File` object that points to the file that was just
dropped into the `inputdir` directory.
-[[File2-Writingtofiles]]
-Writing to files
-++++++++++++++++
+#### Writing to files
Camel is of course also able to write files, i.e. produce files. In the
sample below we receive some reports on the SEDA queue that we process
before they are being written to a directory.
-[[File2-WritetosubdirectoryusingExchange.FILE_NAME]]
-Write to subdirectory using `Exchange.FILE_NAME`
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Write to subdirectory using `Exchange.FILE_NAME`
Using a single route, it is possible to write a file to any number of
subdirectories. If you have a route setup as such:
@@ -781,9 +729,7 @@ Exchange.FILE_NAME = foo/bye.txt => /rootDirectory/foo/bye.txt
This allows you to have a single route to write files to multiple
destinations.
-[[File2-Writingfilethroughthetemporarydirectoryrelativetothefinaldestination]]
-Writing file through the temporary directory relative to the final destination
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Writing file through the temporary directory relative to the final destination
Sometime you need to temporarily write the files to some directory
relative to the destination directory. Such situation usually happens
@@ -799,9 +745,7 @@ from("direct:start").
to("file:///var/myapp/finalDirectory?tempPrefix=/../filesInProgress/");
-------------------------------------------------------------------------
-[[File2-Usingexpressionforfilenames]]
-Using expression for filenames
-++++++++++++++++++++++++++++++
+#### Using expression for filenames
In this sample we want to move consumed files to a backup folder using
today's date as a sub-folder name:
@@ -813,9 +757,7 @@ from("file://inbox?move=backup/${date:now:yyyyMMdd}/${file:name}").to("...");
See link:file-language.html[File Language] for more samples.
-[[File2-Avoidingreadingthesamefilemorethanonceidempotentconsumer]]
-Avoiding reading the same file more than once (idempotent consumer)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Avoiding reading the same file more than once (idempotent consumer)
Camel supports link:idempotent-consumer.html[Idempotent Consumer]
directly within the component so it will skip already processed files.
@@ -865,9 +807,7 @@ consumed before:
DEBUG FileConsumer is idempotent and the file has been consumed before. Will skip this file: target\idempotent\report.txt
-------------------------------------------------------------------------------------------------------------------------
-[[File2-Usingafilebasedidempotentrepository]]
-Using a file based idempotent repository
-++++++++++++++++++++++++++++++++++++++++
+#### Using a file based idempotent repository
In this section we will use the file based idempotent repository
`org.apache.camel.processor.idempotent.FileIdempotentRepository` instead
@@ -887,9 +827,7 @@ idempotent repository and define our file consumer to use our repository
with the `idempotentRepository` using `#` sign to indicate
link:registry.html[Registry] lookup:
-[[File2-UsingaJPAbasedidempotentrepository]]
-Using a JPA based idempotent repository
-+++++++++++++++++++++++++++++++++++++++
+#### Using a JPA based idempotent repository
In this section we will use the JPA based idempotent repository instead
of the in-memory based that is used as default.
@@ -940,9 +878,7 @@ option:
</route>
---------------------------------------------------------------------------------
-[[File2-Filterusingorg.apache.camel.component.file.GenericFileFilter]]
-Filter using org.apache.camel.component.file.GenericFileFilter
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Filter using org.apache.camel.component.file.GenericFileFilter
Camel supports pluggable filtering strategies. You can then configure
the endpoint with such a filter to skip certain files being processed.
@@ -965,9 +901,7 @@ spring XML file:
</route>
----------------------------------------------------------
-[[File2-FilteringusingANTpathmatcher]]
-Filtering using ANT path matcher
-++++++++++++++++++++++++++++++++
+#### Filtering using ANT path matcher
TIP:*New options from Camel 2.10 onwards*
There are now `antInclude` and `antExclude` options to make it easy to
@@ -988,9 +922,7 @@ The file paths is matched with the following rules:
The sample below demonstrates how to use it:
-[[File2-SortingusingComparator]]
-Sorting using Comparator
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Sorting using Comparator
Camel supports pluggable sorting strategies. This strategy it to use the
build in `java.util.Comparator` in Java. You can then configure the
@@ -1021,9 +953,7 @@ link:registry.html[Registry] by prefixing the id with `#`. So writing
`sorter=#mySorter`, will instruct Camel to go look in the
link:registry.html[Registry] for a bean with the ID, `mySorter`.
-[[File2-SortingusingsortBy]]
-Sorting using sortBy
-^^^^^^^^^^^^^^^^^^^^
+### Sorting using sortBy
Camel supports pluggable sorting strategies. This strategy it to use the
link:file-language.html[File Language] to configure the sorting. The
@@ -1111,9 +1041,7 @@ per group, so we could reverse the file names:
sortBy=date:file:yyyyMMdd;reverse:file:name
-------------------------------------------
-[[File2-UsingGenericFileProcessStrategy]]
-Using GenericFileProcessStrategy
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using GenericFileProcessStrategy
The option `processStrategy` can be used to use a custom
`GenericFileProcessStrategy` that allows you to implement your own
@@ -1134,9 +1062,7 @@ resources etc.
* in the `commit()` method we can move the actual file and also delete
the _ready_ file.
-[[File2-Usingfilter]]
-Using filter
-^^^^^^^^^^^^
+### Using filter
The `filter` option allows you to implement a custom filter in Java code
by implementing the `org.apache.camel.component.file.GenericFileFilter`
@@ -1149,9 +1075,7 @@ directories, to avoid traversing down unwanted directories.
For example to skip any directories which starts with `"skip"` in the
name, can be implemented as follows:
-[[File2-HowtousetheCamelerrorhandlertodealwithexceptionstriggeredoutsidetheroutingengine]]
-How to use the Camel error handler to deal with exceptions triggered outside the routing engine
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to use the Camel error handler to deal with exceptions triggered outside the routing engine
The file and ftp consumers, will by default try to pickup files. Only if
that is successful then a Camel link:exchange.html[Exchange] can be
@@ -1203,9 +1127,7 @@ class="com.foo.MyExceptionHandler"/>:
The source code for this example can be seen
https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/component/file/FileConsumerCustomExceptionHandlerTest.java[here]
-[[File2-Usingconsumer.bridgeErrorHandler]]
-Using consumer.bridgeErrorHandler
-+++++++++++++++++++++++++++++++++
+#### Using consumer.bridgeErrorHandler
*Available as of Camel 2.10*
@@ -1227,16 +1149,12 @@ does *not* apply. The link:exchange.html[Exchange] is processed directly
by the Camel link:error-handler.html[Error Handler], and does not allow
prior actions such as interceptors, onCompletion to take action.
-[[File2-Debuglogging]]
-Debug logging
-^^^^^^^^^^^^^
+### Debug logging
This component has log level *TRACE* that can be helpful if you have
problems.
-[[File2-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -1245,5 +1163,4 @@ See Also
* link:file-language.html[File Language]
* link:ftp2.html[FTP]
-* link:polling-consumer.html[Polling Consumer]
-
+* link:polling-consumer.html[Polling Consumer]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/file-language.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/file-language.adoc b/camel-core/src/main/docs/file-language.adoc
index 7a8628f..580c297 100644
--- a/camel-core/src/main/docs/file-language.adoc
+++ b/camel-core/src/main/docs/file-language.adoc
@@ -1,4 +1,4 @@
-# File Language
+## File Language
INFO:*File language is now merged with Simple language*
From Camel 2.2 onwards, the file language is now merged with
@@ -12,9 +12,7 @@ path and names. The goal is to allow expressions to be used with the
link:file2.html[File] and link:ftp.html[FTP] components for setting
dynamic file patterns for both consumer and producer.
-[[FileLanguage-Options]]
-File Language options
-^^^^^^^^^^^^^^^^^^^^^
+### File Language options
// language options: START
The File language supports 2 options which are listed below.
@@ -31,9 +29,7 @@ The File language supports 2 options which are listed below.
{% endraw %}
// language options: END
-[[FileLanguage-Syntax]]
-Syntax
-^^^^^^
+### Syntax
This language is an *extension* to the link:simple.html[Simple] language
so the link:simple.html[Simple] syntax applies also. So the table below
@@ -104,13 +100,9 @@ the file. Notice: all the commands from the link:simple.html[Simple]
language can also be used.
|=======================================================================
-[[FileLanguage-Filetokenexample]]
-File token example
-^^^^^^^^^^^^^^^^^^
+### File token example
-[[FileLanguage-Relativepaths]]
-Relative paths
-++++++++++++++
+#### Relative paths
We have a `java.io.File` handle for the file `hello.txt` in the
following *relative* directory: `.\filelanguage\test`. And we configure
@@ -142,9 +134,7 @@ tokens will return as:
|file:absolute.path |\workspace\camel\camel-core\target\filelanguage\test\hello.txt
|=======================================================================
-[[FileLanguage-Absolutepaths]]
-Absolute paths
-++++++++++++++
+#### Absolute paths
We have a `java.io.File` handle for the file `hello.txt` in the
following *absolute* directory:
@@ -178,9 +168,7 @@ return as:
|file:absolute.path |\workspace\camel\camel-core\target\filelanguage\test\hello.txt
|=======================================================================
-[[FileLanguage-Samples]]
-Samples
-^^^^^^^
+### Samples
You can enter a fixed link:constant.html[Constant] expression such as
`myfile.txt`:
@@ -238,9 +226,7 @@ use the link:file-language.html[File Language], link:simple.html[Simple]
and the link:bean.html[Bean] language in one combined expression. This
is pretty powerful for those common file path patterns.
-[[FileLanguage-UsingSpringPropertyPlaceholderConfigurertogetherwiththeFilecomponent]]
-Using Spring PropertyPlaceholderConfigurer together with the link:file2.html[File] component
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using Spring PropertyPlaceholderConfigurer together with the link:file2.html[File] component
In Camel you can use the link:file-language.html[File Language] directly
from the link:simple.html[Simple] language which makes a
@@ -304,8 +290,6 @@ Invalid bean definition with name 'sampleRoute' defined in class path resource [
Could not resolve placeholder 'date:now:yyyyMMdd'
----------------------------------------------------------------------------------------------------
-[[FileLanguage-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
-The File language is part of *camel-core*.
+The File language is part of *camel-core*.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/gzip-dataformat.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/gzip-dataformat.adoc b/camel-core/src/main/docs/gzip-dataformat.adoc
index 7a0b708..5417db1 100644
--- a/camel-core/src/main/docs/gzip-dataformat.adoc
+++ b/camel-core/src/main/docs/gzip-dataformat.adoc
@@ -1,4 +1,4 @@
-# GZip DataFormat
+## GZip DataFormat
The GZip link:data-format.html[Data Format] is a message compression and
de-compression format. It uses the same deflate algorithm that is used
@@ -10,9 +10,7 @@ The compression capability is quite useful when you deal with large XML
and Text based payloads or when you read messages previously comressed
using `gzip` tool.
-[[GZipdataformat-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The GZip dataformat supports 1 options which are listed below.
@@ -28,9 +26,7 @@ The GZip dataformat supports 1 options which are listed below.
{% endraw %}
// dataformat options: END
-[[GZipdataformat-Marshal]]
-Marshal
-^^^^^^^
+### Marshal
In this example we marshal a regular text/XML payload to a compressed
payload employing gzip compression format and send it an ActiveMQ queue
@@ -41,9 +37,7 @@ called MY_QUEUE.
from("direct:start").marshal().gzip().to("activemq:queue:MY_QUEUE");
--------------------------------------------------------------------
-[[GZipdataformat-Unmarshal]]
-Unmarshal
-^^^^^^^^^
+### Unmarshal
In this example we unmarshal�a gzipped�payload from an ActiveMQ queue
called MY_QUEUE�to its original format,�and forward it for�processing�to
@@ -54,9 +48,7 @@ the `UnGZippedMessageProcessor`.
from("activemq:queue:MY_QUEUE").unmarshal().gzip().process(new UnGZippedMessageProcessor());
---------------------------------------------------------------------------------------------
-[[GZipdataformat-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
This data format is provided in *camel-core* so no additional
-dependencies is needed.
+dependencies is needed.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/header-language.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/header-language.adoc b/camel-core/src/main/docs/header-language.adoc
index 94d09b4..1b9c9c2 100644
--- a/camel-core/src/main/docs/header-language.adoc
+++ b/camel-core/src/main/docs/header-language.adoc
@@ -1,11 +1,9 @@
-# Header Language
+## Header Language
The Header Expression Language allows you to extract values of named
headers.
-[[Header-Options]]
-Header Options
-^^^^^^^^^^^^^^
+### Header Options
// language options: START
The Header language supports 1 options which are listed below.
@@ -21,9 +19,7 @@ The Header language supports 1 options which are listed below.
{% endraw %}
// language options: END
-[[Header-Exampleusage]]
-Example usage
-^^^^^^^^^^^^^
+### Example usage
The recipientList element of the Spring DSL can utilize a header
expression like:
@@ -42,8 +38,6 @@ notice that header is not a parameter but a stacked method call)
from("direct:a").recipientList().header("myHeader");
------------------------------------------------------
-[[Header-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
-The Header language is part of *camel-core*.
+The Header language is part of *camel-core*.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/language-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/language-component.adoc b/camel-core/src/main/docs/language-component.adoc
index 88a3c38..7f62527 100644
--- a/camel-core/src/main/docs/language-component.adoc
+++ b/camel-core/src/main/docs/language-component.adoc
@@ -1,4 +1,4 @@
-# Language Component
+## Language Component
*Available as of Camel 2.5*
@@ -16,9 +16,7 @@ additional JARs is needed. You only have to include additional Camel
components if the language of choice mandates it, such as using
link:groovy.html[Groovy] or link:javascript.html[JavaScript] languages.
-[[Language-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------------------
@@ -34,9 +32,7 @@ link:language.html[Language]s in Camel
language://languageName:resource:scheme:location][?options]
-----------------------------------------------------------
-[[Language-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -65,9 +61,7 @@ The Language component supports 8 endpoint options which are listed below:
// endpoint options: END
-[[Language-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
The following message headers can be used to affect the behavior of the
component
@@ -80,9 +74,7 @@ component
script configured on the endpoint.
|=======================================================================
-[[Language-Examples]]
-Examples
-^^^^^^^^
+### Examples
For example you can use the link:simple.html[Simple] language to
link:message-translator.html[Message Translator] a message:
@@ -103,9 +95,7 @@ Object out = producer.requestBodyAndHeader("language:xpath", "<foo>Hello World</
assertEquals("Hello World", out);
--------------------------------------------------------------------------------------------------------------------------------
-[[Language-Loadingscriptsfromresources]]
-Loading scripts from resources
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading scripts from resources
*Available as of Camel 2.9*
@@ -126,9 +116,7 @@ From *Camel 2.11* onwards you can refer to the resource similar to the
other link:language.html[Language]s in Camel by prefixing with
`"resource:"` as shown below:
-[[Language-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -137,5 +125,4 @@ See Also
* link:languages.html[Languages]
* link:routing-slip.html[Routing Slip]
* link:dynamic-router.html[Dynamic Router]
-* link:script.html[Script]
-
+* link:script.html[Script]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/log-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/log-component.adoc b/camel-core/src/main/docs/log-component.adoc
index be6598b..e365f86 100644
--- a/camel-core/src/main/docs/log-component.adoc
+++ b/camel-core/src/main/docs/log-component.adoc
@@ -1,4 +1,4 @@
-# Log Component
+## Log Component
The *log:* component logs message exchanges to the underlying logging
mechanism.
@@ -12,9 +12,7 @@ logging via, among others:
http://java.sun.com/j2se/1.4.2/docs/api/java/util/logging/package-summary.html[JDK
Util Logging logging]
-[[Log-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------------
@@ -51,9 +49,7 @@ There is also a `log` directly in the DSL, but it has a different
purpose. Its meant for lightweight and human logs. See more details at
link:logeip.html[LogEIP].
-[[Log-Options]]
-Options
-^^^^^^^
+### Options
@@ -112,9 +108,7 @@ The Log component supports 26 endpoint options which are listed below:
// endpoint options: END
-[[Log-Regularloggersample]]
-Regular logger sample
-^^^^^^^^^^^^^^^^^^^^^
+### Regular logger sample
In the route below we log the incoming orders at `DEBUG` level before
the order is processed:
@@ -135,9 +129,7 @@ Or using Spring XML to define the route:
</route>
---------------------------------------------------
-[[Log-Regularloggerwithformattersample]]
-Regular logger with formatter sample
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Regular logger with formatter sample
In the route below we log the incoming orders at `INFO` level before the
order is processed.
@@ -148,9 +140,7 @@ from("activemq:orders").
to("log:com.mycompany.order?showAll=true&multiline=true").to("bean:processOrder");
--------------------------------------------------------------------------------------
-[[Log-ThroughputloggerwithgroupSizesample]]
-Throughput logger with groupSize sample
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Throughput logger with groupSize sample
In the route below we log the throughput of the incoming orders at
`DEBUG` level grouped by 10 messages.
@@ -161,9 +151,7 @@ from("activemq:orders").
to("log:com.mycompany.order?level=DEBUG&groupSize=10").to("bean:processOrder");
-----------------------------------------------------------------------------------
-[[Log-ThroughputloggerwithgroupIntervalsample]]
-Throughput logger with groupInterval sample
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Throughput logger with groupInterval sample
This route will result in message stats logged every 10s, with an
initial 60s delay and stats should be displayed even if there isn't any
@@ -182,9 +170,7 @@ The following will be logged:
"Received: 1000 new messages, with total 2000 so far. Last group took: 10000 millis which is: 100 messages per second. average: 100"
------------------------------------------------------------------------------------------------------------------------------------
-[[Log-Fullcustomizationoftheloggingoutput]]
-Full customization of the logging output
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Full customization of the logging output
*Available as of Camel 2.11*
@@ -266,9 +252,7 @@ options:
<to uri="log:bar?param1=bar&param2=200"/>
---------------------------------------------
-[[Log-UsingLogcomponentinOSGi]]
-Using Log component in OSGi
-+++++++++++++++++++++++++++
+#### Using Log component in OSGi
*Improvement as of Camel 2.12.4/2.13.1*
@@ -284,9 +268,7 @@ should be the bundle which contains route definition. To do this, either
register single instance of�`org.slf4j.Logger` in the Registry or
reference it using�`logger` URI parameter.
-[[Log-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -297,5 +279,4 @@ See Also
* link:how-do-i-use-log4j.html[How do I use log4j]
* link:how-do-i-use-java-14-logging.html[How do I use Java 1.4 logging]
* link:logeip.html[LogEIP] for using `log` directly in the DSL for human
-logs.
-
+logs.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/camel-core/src/main/docs/mock-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/mock-component.adoc b/camel-core/src/main/docs/mock-component.adoc
index dff920f..58e70cd 100644
--- a/camel-core/src/main/docs/mock-component.adoc
+++ b/camel-core/src/main/docs/mock-component.adoc
@@ -1,4 +1,4 @@
-# Mock Component
+## Mock Component
ifdef::env-github[]
:caution-caption: :boom:
:important-caption: :exclamation:
@@ -7,9 +7,7 @@ ifdef::env-github[]
:warning-caption: :warning:
endif::[]
-[[Mock-MockComponent]]
-Mock Component
-~~~~~~~~~~~~~~
+### Mock Component
link:testing.html[Testing] of distributed and asynchronous processing is
notoriously difficult. The link:mock.html[Mock], link:test.html[Test]
@@ -65,9 +63,7 @@ From Camel 2.10 onwards there are two new options `retainFirst`, and
endpoints keep in memory.
-[[Mock-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source]
----
@@ -80,9 +76,7 @@ endpoint.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Mock-Options]]
-Options
-^^^^^^^
+### Options
@@ -120,9 +114,7 @@ The Mock component supports 11 endpoint options which are listed below:
-[[Mock-SimpleExample]]
-Simple Example
-^^^^^^^^^^^^^^
+### Simple Example
Here's a simple example of Mock endpoint in use. First, the endpoint is
resolved on the context. Then we set an expectation, and then, after the
@@ -149,9 +141,7 @@ Camel will by default wait 10 seconds when the `assertIsSatisfied()` is
invoked. This can be configured by setting the
`setResultWaitTime(millis)` method.
-[[Mock-UsingassertPeriod]]
-Using `assertPeriod`
-++++++++++++++++++++
+#### Using `assertPeriod`
*Available as of Camel 2.7* +
When the assertion is satisfied then Camel will stop waiting and
@@ -174,9 +164,7 @@ resultEndpoint.expectedMessageCount(2);
resultEndpoint.assertIsSatisfied();
----
-[[Mock-Settingexpectations]]
-Setting expectations
-^^^^^^^^^^^^^^^^^^^^
+### Setting expectations
You can see from the Javadoc of
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/mock/MockEndpoint.html[MockEndpoint]
@@ -220,9 +208,7 @@ Here's another example:
resultEndpoint.expectedBodiesReceived("firstMessageBody", "secondMessageBody", "thirdMessageBody");
----
-[[Mock-Addingexpectationstospecificmessages]]
-Adding expectations to specific messages
-++++++++++++++++++++++++++++++++++++++++
+#### Adding expectations to specific messages
In addition, you can use the
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/mock/MockEndpoint.html#message(int)[`message(int
@@ -242,9 +228,7 @@ There are some examples of the Mock endpoint in use in the
http://svn.apache.org/viewvc/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/[`camel-core`
processor tests].
-[[Mock-Mockingexistingendpoints]]
-Mocking existing endpoints
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Mocking existing endpoints
*Available as of Camel 2.7*
@@ -313,9 +297,7 @@ That means Camel will use more memory. This may not be suitable when you
send in a lot of messages.
-[[Mock-Mockingexistingendpointsusingthecamel-testcomponent]]
-Mocking existing endpoints using the `camel-test` component
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Mocking existing endpoints using the `camel-test` component
Instead of using the `adviceWith` to instruct Camel to mock endpoints,
you can easily enable this behavior when using the `camel-test` Test
@@ -335,9 +317,7 @@ include::../../../../components/camel-test/src/test/java/org/apache/camel/test/p
----
-[[Mock-MockingexistingendpointswithXMLDSL]]
-Mocking existing endpoints with XML DSL
-+++++++++++++++++++++++++++++++++++++++
+#### Mocking existing endpoints with XML DSL
If you do not use the `camel-test` component for unit testing (as shown
above) you can use a different approach when using XML files for
@@ -377,9 +357,7 @@ in the constructor for the bean:
</bean>
----
-[[Mock-Mockingendpointsandskipsendingtooriginalendpoint]]
-Mocking endpoints and skip sending to original endpoint
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Mocking endpoints and skip sending to original endpoint
*Available as of Camel 2.10*
@@ -405,9 +383,7 @@ The same example using the link:testing.html[Test Kit]
include::../../../../components/camel-test/src/test/java/org/apache/camel/test/patterns/IsMockEndpointsAndSkipJUnit4Test.java[tags=e1]
----
-[[Mock-Limitingthenumberofmessagestokeep]]
-Limiting the number of messages to keep
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Limiting the number of messages to keep
*Available as of Camel 2.10*
@@ -444,9 +420,7 @@ methods that work on message bodies, headers, etc. will only operate on
the retained messages. In the example above they can test only the
expectations on the 10 retained messages.
-[[Mock-Testingwitharrivaltimes]]
-Testing with arrival times
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Testing with arrival times
*Available as of Camel 2.7*
@@ -502,9 +476,7 @@ In the example above we use `seconds` as the time unit, but Camel offers
`milliseconds`, and `minutes` as well.
-[[Mock-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -512,4 +484,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:spring-testing.html[Spring Testing]
-* link:testing.html[Testing]
+* link:testing.html[Testing]
\ No newline at end of file
[12/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-asterisk/src/main/docs/asterisk-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-asterisk/src/main/docs/asterisk-component.adoc b/components/camel-asterisk/src/main/docs/asterisk-component.adoc
index 7369bb2..9f69aec 100644
--- a/components/camel-asterisk/src/main/docs/asterisk-component.adoc
+++ b/components/camel-asterisk/src/main/docs/asterisk-component.adoc
@@ -1,4 +1,4 @@
-# Asterisk Component
+## Asterisk Component
*Available as of Camel 2.18*
@@ -19,18 +19,14 @@ for this component:
</dependency>
------------------------------------------------------------
-[[AsteriskComponent-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------------------------------------------------------------------------------------------------
asterisk:name[?options]
-------------------------------------------------------------------------------------------------------------------------
-[[AsteriskComponent-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The Asterisk component has no options.
@@ -56,11 +52,9 @@ The Asterisk component supports 9 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[Asterisk-Actions]]
-Action
-^^^^^^
+### Action
Supported actions are:
* QUEUE_STATUS, Queue Status
* SIP_PEERS, List SIP Peers
-* EXTENSION_STATE, Check Extension Status
+* EXTENSION_STATE, Check Extension Status
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-atmos/src/main/docs/atmos-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-atmos/src/main/docs/atmos-component.adoc b/components/camel-atmos/src/main/docs/atmos-component.adoc
index 989846b..ec4fbe6 100644
--- a/components/camel-atmos/src/main/docs/atmos-component.adoc
+++ b/components/camel-atmos/src/main/docs/atmos-component.adoc
@@ -1,4 +1,4 @@
-# Atmos Component
+## Atmos Component
*Available as of Camel 2.15*
@@ -11,9 +11,7 @@ https://github.com/emcvipr/dataservices-sdk-java[Atmos Client].
from("atmos:foo/get?remotePath=/path").to("mock:test");
-------------------------------
-[[Atmos-Options]]
-Options
-~~~~~~~
+### Options
// component options: START
@@ -48,9 +46,7 @@ The Atmos component supports 14 endpoint options which are listed below:
// endpoint options: END
-[[Atmos-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Atmos in your camel routes you need to add the dependency
on *camel-atmos* which implements this data format.
@@ -71,8 +67,7 @@ link:download.html[the download page for the latest versions]).
[[Atmos-Integrations]]
-Integrations
-^^^^^^^^^^^^
+### Integrations
When you look at atmos integrations, there is one type of consumer,
GetConsumer, which is a type of ScheduledPollConsumer.
@@ -86,9 +81,7 @@ Whereas there are 4 types of producers which are
* `Move`
* `Put`
-[[Atmos-Examples]]
-Examples
-^^^^^^^^
+### Examples
These example are taken from tests:
@@ -124,11 +117,9 @@ exhange
DOWNLOADED_FILE, DOWNLOADED_FILES, UPLOADED_FILE, UPLOADED_FILES, FOUND_FILES, DELETED_PATH, MOVED_PATH;
-------------------------------
-[[Atmos-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-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc b/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc
index 2acbac9..b97c166 100644
--- a/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc
+++ b/components/camel-atmosphere-websocket/src/main/docs/atmosphere-websocket-component.adoc
@@ -1,4 +1,4 @@
-# Atmosphere Websocket Component
+## Atmosphere Websocket Component
*Available as of Camel 2.14*
@@ -29,9 +29,7 @@ their�`pom.xml`�for this component:
</dependency>
------------------------------------------------------------
-[[Atmosphere-Websocket-Options]]
-Atmosphere-Websocket Options
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Atmosphere-Websocket Options
@@ -106,26 +104,20 @@ The Atmosphere Websocket component supports 36 endpoint options which are listed
// endpoint options: END
-[[Atmosphere-Websocket-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
-----------------------------------------------
atmosphere-websocket:///relative path[?options]
-----------------------------------------------
-[[Atmosphere-Websocket-ReadingandWritingDataoverWebsocket]]
-Reading and Writing Data over Websocket
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Reading and Writing Data over Websocket
An atmopshere-websocket endpoint can either write data to the socket or
read from the socket, depending on whether the endpoint is configured as
the producer or the consumer, respectively.
-[[Atmosphere-Websocket-ConfiguringURItoReadorWriteData]]
-Configuring URI to Read or Write Data
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring URI to Read or Write Data
In the route below, Camel will read from the specified websocket
connection.
@@ -171,9 +163,7 @@ And the equivalent Spring sample:
�
-[[Atmosphere-Websocket-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -183,5 +173,4 @@ See Also
* link:servlet.html[SERVLET]
* link:ahc-ws.html[AHC-WS]
*
-https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=39621544[Websocket]
-
+https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=39621544[Websocket]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-atom/src/main/docs/atom-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-atom/src/main/docs/atom-component.adoc b/components/camel-atom/src/main/docs/atom-component.adoc
index 2349a17..922c407 100644
--- a/components/camel-atom/src/main/docs/atom-component.adoc
+++ b/components/camel-atom/src/main/docs/atom-component.adoc
@@ -1,4 +1,4 @@
-# Atom Component
+## Atom Component
The *atom:* component is used for polling Atom feeds.
@@ -19,9 +19,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Atom-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------
@@ -30,9 +28,7 @@ atom://atomUri[?options]
Where *atomUri* is the URI to the Atom feed to poll.
-[[Atom-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -84,9 +80,7 @@ The Atom component supports 28 endpoint options which are listed below:
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Atom-Exchangedataformat]]
-Exchange data format
-^^^^^^^^^^^^^^^^^^^^
+### Exchange data format
Camel will set the In body on the returned `Exchange` with the entries.
Depending on the `splitEntries` flag Camel will either return one
@@ -105,9 +99,7 @@ Depending on the `splitEntries` flag Camel will either return one
Camel can set the `Feed` object on the In header (see `feedHeader`
option to disable this):
-[[Atom-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Camel atom uses these headers.
@@ -118,9 +110,7 @@ Camel atom uses these headers.
header.
|=======================================================================
-[[Atom-Samples]]
-Samples
-^^^^^^^
+### Samples
In this sample we poll James Strachan's blog.
@@ -133,14 +123,11 @@ In this sample we want to filter only good blogs we like to a SEDA
queue. The sample also shows how to setup Camel standalone, not running
in any Container or using Spring.
-[[Atom-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:rss.html[RSS]
-
+* link:rss.html[RSS]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-avro/src/main/docs/avro-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-avro/src/main/docs/avro-component.adoc b/components/camel-avro/src/main/docs/avro-component.adoc
index cc18ca0..f305d84 100644
--- a/components/camel-avro/src/main/docs/avro-component.adoc
+++ b/components/camel-avro/src/main/docs/avro-component.adoc
@@ -1,4 +1,4 @@
-# Avro Component
+## Avro Component
*Available as of Camel 2.10*
@@ -21,9 +21,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[avro-ApacheAvroOverview]]
-Apache Avro Overview
-^^^^^^^^^^^^^^^^^^^^
+### Apache Avro Overview
Avro allows you to define message types and a protocol using a json like
format and then generate java code for the specified types and messages.
@@ -90,9 +88,7 @@ class Value {
_Note: Existing classes can be used only for RPC (see below), not in
data format._
-[[avro-UsingtheAvrodataformat]]
-Using the Avro data format
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the Avro data format
Using the avro data format is as easy as specifying that the class that
you want to marshal or unmarshal in your route.
@@ -129,9 +125,7 @@ reference it from your route.
In the same manner you can umarshal using the avro data format.
-[[avro-UsingAvroRPCinCamel]]
-Using Avro RPC in Camel
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using Avro RPC in Camel
As mentioned above Avro also provides RPC support over multiple
transports such as http and netty. Camel provides consumers and
@@ -170,9 +164,7 @@ got only one parameter, *since 2.12* you can use `singleParameter` URI
option to receive it direcly in the "in" message body without array
wrapping.
-[[avro-AvroRPCURIOptions]]
-Avro RPC URI Options
-^^^^^^^^^^^^^^^^^^^^
+### Avro RPC URI Options
@@ -223,9 +215,7 @@ The Avro component supports 14 endpoint options which are listed below:
// endpoint options: END
-[[avro-AvroRPCHeaders]]
-Avro RPC Headers
-^^^^^^^^^^^^^^^^
+### Avro RPC Headers
[width="100%",cols="20%,80%",options="header",]
|=======================================================================
@@ -235,9 +225,7 @@ Avro RPC Headers
URI (if any)
|=======================================================================
-[[avro-Examples]]
-Examples
-^^^^^^^^
+### Examples
An example of using camel avro producers via http:
@@ -299,4 +287,4 @@ task:
In the example above, get takes only one parameter, so `singleParameter`
is used and `getProcessor` will receive Value class directly in body,
while `putProcessor` will receive an array of size 2 with String key and
-Value value filled as array contents.
+Value value filled as array contents.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-avro/src/main/docs/avro-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-avro/src/main/docs/avro-dataformat.adoc b/components/camel-avro/src/main/docs/avro-dataformat.adoc
index 233db77..e749dc6 100644
--- a/components/camel-avro/src/main/docs/avro-dataformat.adoc
+++ b/components/camel-avro/src/main/docs/avro-dataformat.adoc
@@ -1,4 +1,4 @@
-# Avro DataFormat
+## Avro DataFormat
*Available as of Camel 2.10*
@@ -21,9 +21,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[avro-ApacheAvroOverview]]
-Apache Avro Overview
-^^^^^^^^^^^^^^^^^^^^
+### Apache Avro Overview
Avro allows you to define message types and a protocol using a json like
format and then generate java code for the specified types and messages.
@@ -90,9 +88,7 @@ class Value {
_Note: Existing classes can be used only for RPC (see below), not in
data format._
-[[avro-UsingtheAvrodataformat]]
-Using the Avro data format
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the Avro data format
Using the avro data format is as easy as specifying that the class that
you want to marshal or unmarshal in your route.
@@ -130,9 +126,7 @@ reference it from your route.
In the same manner you can umarshal using the avro data format.
-[[avro-AvroDataformat-options]]
-Avro Dataformat Options
-^^^^^^^^^^^^^^^^^^^^^^^
+### Avro Dataformat Options
// dataformat options: START
The Avro dataformat supports 2 options which are listed below.
@@ -147,5 +141,4 @@ The Avro 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-aws/src/main/docs/aws-cw-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-cw-component.adoc b/components/camel-aws/src/main/docs/aws-cw-component.adoc
index 9e86f2b..d5ec81e 100644
--- a/components/camel-aws/src/main/docs/aws-cw-component.adoc
+++ b/components/camel-aws/src/main/docs/aws-cw-component.adoc
@@ -1,4 +1,4 @@
-# AWS CloudWatch Component
+## AWS CloudWatch Component
*Available as of Camel 2.11
@@ -13,9 +13,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon CloudWatch. More information are available at
http://aws.amazon.com/cloudwatch/[Amazon CloudWatch].
-[[AWS-CW-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
----------------------------
@@ -26,9 +24,7 @@ The metrics will be created if they don't already exists. +
You can append query options to the URI in the following format,
`?options=value&option2=value&...`
-[[AWS-CW-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -69,13 +65,9 @@ You have to provide the amazonCwClient in the
link:registry.html[Registry] or your accessKey and secretKey to access
the http://aws.amazon.com/cloudwatch/[Amazon's CloudWatch].
-[[AWS-CW-Usage]]
-Usage
-^^^^^
+### Usage
-[[AWS-CW-MessageheadersevaluatedbytheCWproducer]]
-Message headers evaluated by the CW producer
-++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the CW producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -98,9 +90,7 @@ Message headers evaluated by the CW producer
|`CamelAwsCwMetricDimensions` |`Map<String, String>` |*Camel 2.12:* A map of dimension names and dimension values.
|=======================================================================
-[[AWS-CW-AdvancedAmazonCloudWatchconfiguration]]
-Advanced AmazonCloudWatch configuration
-+++++++++++++++++++++++++++++++++++++++
+#### Advanced AmazonCloudWatch configuration
If you need more control over the `AmazonCloudWatch` instance
configuration you can create your own instance and refer to it from the
@@ -129,9 +119,7 @@ AmazonCloudWatch client = new AmazonCloudWatchClient(awsCredentials, clientConfi
registry.bind("client", client);
------------------------------------------------------------------------------------------
-[[AWS-CW-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -149,14 +137,11 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.10 or higher).
-[[AWS-CW-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:aws.html[AWS Component]
-
+* link:aws.html[AWS Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-aws/src/main/docs/aws-ddb-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-ddb-component.adoc b/components/camel-aws/src/main/docs/aws-ddb-component.adoc
index 07138e6..4c74023 100644
--- a/components/camel-aws/src/main/docs/aws-ddb-component.adoc
+++ b/components/camel-aws/src/main/docs/aws-ddb-component.adoc
@@ -1,4 +1,4 @@
-# AWS DynamoDB Component
+## AWS DynamoDB Component
*Available as of Camel 2.10*
@@ -11,9 +11,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon DynamoDB. More information are available at
http://aws.amazon.com/dynamodb[Amazon DynamoDB].
-[[AWS-DDB-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
------------------------------
@@ -23,9 +21,7 @@ aws-ddb://domainName[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-[[AWS-DDB-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -68,13 +64,9 @@ You have to provide the amazonDDBClient in the
link:registry.html[Registry] or your accessKey and secretKey to access
the http://aws.amazon.com/dynamodb[Amazon's DynamoDB].
-[[AWS-DDB-Usage]]
-Usage
-^^^^^
+### Usage
-[[AWS-DDB-MessageheadersevaluatedbytheDDBproducer]]
-Message headers evaluated by the DDB producer
-+++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the DDB producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -127,9 +119,7 @@ the query.*From Camel 2.16.0 this header doesn't exist anymore.*
|`CamelAwsDdbUpdateValues` |`Map<String, AttributeValueUpdate>` |Map of attribute name to the new value and action for the update.
|=======================================================================
-[[AWS-DDB-MessageheaderssetduringBatchGetItemsoperation]]
-Message headers set during BatchGetItems operation
-++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during BatchGetItems operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -141,9 +131,7 @@ Message headers set during BatchGetItems operation
processed with the current response.
|=======================================================================
-[[AWS-DDB-MessageheaderssetduringDeleteItemoperation]]
-Message headers set during DeleteItem operation
-+++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during DeleteItem operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -152,9 +140,7 @@ Message headers set during DeleteItem operation
|`CamelAwsDdbAttributes` |`Map<String, AttributeValue>` |The list of attributes returned by the operation.
|=======================================================================
-[[AWS-DDB-MessageheaderssetduringDeleteTableoperation]]
-Message headers set during DeleteTable operation
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during DeleteTable operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -178,9 +164,7 @@ Message headers set during DeleteTable operation
|`CamelAwsDdbTableStatus` |`String` |The status of the table: CREATING, UPDATING, DELETING, ACTIVE
|=======================================================================
-[[AWS-DDB-MessageheaderssetduringDescribeTableoperation]]
-Message headers set during DescribeTable operation
-++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during DescribeTable operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -207,9 +191,7 @@ not KeySchema*
|`CamelAwsDdbWriteCapacity` |`Long` |WriteCapacityUnits property of this table.
|=======================================================================
-[[AWS-DDB-MessageheaderssetduringGetItemoperation]]
-Message headers set during GetItem operation
-++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during GetItem operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -219,9 +201,7 @@ Message headers set during GetItem operation
|=======================================================================
-[[AWS-DDB-MessageheaderssetduringPutItemoperation]]
-Message headers set during PutItem operation
-++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during PutItem operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -231,9 +211,7 @@ Message headers set during PutItem operation
|=======================================================================
-[[AWS-DDB-MessageheaderssetduringQueryoperation]]
-Message headers set during Query operation
-++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during Query operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -250,9 +228,7 @@ consumed during the operation.
|`CamelAwsDdbCount` |`Integer` |Number of items in the response.
|=======================================================================
-[[AWS-DDB-MessageheaderssetduringScanoperation]]
-Message headers set during Scan operation
-+++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during Scan operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -271,9 +247,7 @@ consumed during the operation.
|`CamelAwsDdbScannedCount` |`Integer` |Number of items in the complete scan before any filters are applied.
|=======================================================================
-[[AWS-DDB-MessageheaderssetduringUpdateItemoperation]]
-Message headers set during UpdateItem operation
-+++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during UpdateItem operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -283,9 +257,7 @@ Message headers set during UpdateItem operation
|=======================================================================
-[[AWS-DDB-AdvancedAmazonDynamoDBconfiguration]]
-Advanced AmazonDynamoDB configuration
-+++++++++++++++++++++++++++++++++++++
+#### Advanced AmazonDynamoDB configuration
If you need more control over the `AmazonDynamoDB` instance
configuration you can create your own instance and refer to it from the
@@ -314,9 +286,7 @@ AmazonDynamoDB client = new AmazonDynamoDBClient(awsCredentials, clientConfigura
registry.bind("client", client);
--------------------------------------------------------------------------------------
-[[AWS-DDB-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -334,14 +304,11 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.10 or higher).
-[[AWS-DDB-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:aws.html[AWS Component]
-
+* link:aws.html[AWS Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-aws/src/main/docs/aws-ddbstream-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-ddbstream-component.adoc b/components/camel-aws/src/main/docs/aws-ddbstream-component.adoc
index 56b04c1..b33ef60 100644
--- a/components/camel-aws/src/main/docs/aws-ddbstream-component.adoc
+++ b/components/camel-aws/src/main/docs/aws-ddbstream-component.adoc
@@ -1,4 +1,4 @@
-# AWS DynamoDB Streams Component
+## AWS DynamoDB Streams Component
*Available as of Camel 2.7*
@@ -11,9 +11,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon DynamoDB Streams. More information are available
at�http://aws.amazon.com/dynamodb/[AWS DynamoDB]
-[[AWS-DDBSTREAM-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
------------------------------------
@@ -24,9 +22,7 @@ The stream needs to be created prior to it being used. +
You can append query options to the URI in the following format,
?options=value&option2=value&...
-[[AWS-DDBSTREAM-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -83,9 +79,7 @@ You have to provide the�amazonDynamoDbStreamsClient in the
link:registry.html[Registry] with proxies and relevant credentials
configured.
-[[AWS-DDBSTREAM-SequenceNumbers]]
-Sequence Numbers
-^^^^^^^^^^^^^^^^
+### Sequence Numbers
You can provide a literal string as the sequence number or provide a
bean in the registry. An example of using the bean would be to save your
@@ -95,9 +89,7 @@ It is an error to provide a sequence number that is greater than the
largest sequence number in the describe-streams result, as this will
lead to the AWS call returning an HTTP 400.
-[[AWS-DDBSTREAM-BatchConsumer]]
-Batch Consumer
-^^^^^^^^^^^^^^
+### Batch Consumer
This component implements the link:batch-consumer.html[Batch Consumer].
@@ -105,13 +97,9 @@ This allows you for instance to know how many messages exists in this
batch and for instance let the link:aggregator.html[Aggregator]
aggregate this number of messages.
-[[AWS-DDBSTREAM-Usage]]
-Usage
-^^^^^
+### Usage
-[[AWS-DDBSTREAM-AmazonDynamoDBStreamsClientconfiguration]]
-AmazonDynamoDBStreamsClient�configuration
-+++++++++++++++++++++++++++++++++++++++++
+#### AmazonDynamoDBStreamsClient�configuration
You will need to create an instance of AmazonDynamoDBStreamsClient and
bind it to the registry
@@ -129,9 +117,7 @@ region.createClient(AmazonDynamoDBStreamsClient.class, null, clientConfiguration
registry.bind("kinesisClient", client);
--------------------------------------------------------------------------------------------------------------------
-[[AWS-DDBSTREAM-ProvidingAWSCredentials]]
-Providing AWS Credentials
-+++++++++++++++++++++++++
+#### Providing AWS Credentials
It is recommended that the credentials are obtained by using the
http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/DefaultAWSCredentialsProviderChain.html[DefaultAWSCredentialsProviderChain]
@@ -140,13 +126,9 @@ however, a
different�http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/AWSCredentialsProvider.html[AWSCredentialsProvider]
can be specified when calling createClient(...).
-[[AWS-DDBSTREAM-CopingwithDowntime]]
-Coping with Downtime
-^^^^^^^^^^^^^^^^^^^^
+### Coping with Downtime
-[[AWS-DDBSTREAM-AWSDynamoDBStreamsoutageoflessthan24hours]]
-AWS DynamoDB Streams outage of less than 24 hours
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### AWS DynamoDB Streams outage of less than 24 hours
The consumer will resume from the last seen sequence number (as
implemented
@@ -154,16 +136,12 @@ for�https://issues.apache.org/jira/browse/CAMEL-9515[CAMEL-9515]), so
you should receive a flood of events in quick succession, as long as the
outage did not also include DynamoDB itself.
-[[AWS-DDBSTREAM-AWSDynamoDBStreamsoutageofmorethan24hours]]
-AWS DynamoDB Streams outage of more than 24 hours
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### AWS DynamoDB Streams outage of more than 24 hours
Given that AWS only retain 24 hours worth of changes, you will have
missed change events no matter what mitigations are in place.
-[[AWS-DDBSTREAM-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -181,9 +159,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.7 or higher).
-[[AWS-DDBSTREAM-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -191,5 +167,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:aws.html[AWS Component] +
- +
-
+ +
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-aws/src/main/docs/aws-ec2-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-ec2-component.adoc b/components/camel-aws/src/main/docs/aws-ec2-component.adoc
index a5a18b1..9acf32c 100644
--- a/components/camel-aws/src/main/docs/aws-ec2-component.adoc
+++ b/components/camel-aws/src/main/docs/aws-ec2-component.adoc
@@ -1,4 +1,4 @@
-# AWS EC2 Component
+## AWS EC2 Component
*Available as of Camel 2.16*
@@ -11,9 +11,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon EC2. More information are available at
https://aws.amazon.com/it/ec2/[Amazon EC2].
-[[AWS-EC2-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
-------------------------
@@ -23,9 +21,7 @@ aws-ec2://label[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-[[AWS-EC2-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -63,13 +59,9 @@ You have to provide the amazonEc2Client in the
link:registry.html[Registry] or your accessKey and secretKey to access
the https://aws.amazon.com/it/ec2/[Amazon EC2] service.
-[[AWS-EC2-Usage]]
-Usage
-^^^^^
+### Usage
-[[AWS-EC2-MessageheadersevaluatedbytheEC2producer]]
-Message headers evaluated by the EC2 producer
-+++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the EC2 producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -115,14 +107,11 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.16 or higher).
-[[AWS-EC2-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:aws.html[AWS Component]
-
+* link:aws.html[AWS Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-aws/src/main/docs/aws-kinesis-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-kinesis-component.adoc b/components/camel-aws/src/main/docs/aws-kinesis-component.adoc
index 27f0794..6a59c3b 100644
--- a/components/camel-aws/src/main/docs/aws-kinesis-component.adoc
+++ b/components/camel-aws/src/main/docs/aws-kinesis-component.adoc
@@ -1,4 +1,4 @@
-# AWS Kinesis Component
+## AWS Kinesis Component
*Available as of Camel 2.17*
@@ -11,9 +11,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon Kinesis. More information are available
at�http://aws.amazon.com/kinesis/[AWS Kinesis]
-[[AWS-KINESIS-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
-----------------------------------
@@ -24,9 +22,7 @@ The stream needs to be created prior to it being used. +
You can append query options to the URI in the following format,
?options=value&option2=value&...
-[[AWS-KINESIS-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -86,9 +82,7 @@ You have to provide the�amazonKinesisClient in the
link:registry.html[Registry] with proxies and relevant credentials
configured.
-[[AWS-KINESIS-BatchConsumer]]
-Batch Consumer
-^^^^^^^^^^^^^^
+### Batch Consumer
This component implements the link:batch-consumer.html[Batch Consumer].
@@ -96,13 +90,9 @@ This allows you for instance to know how many messages exists in this
batch and for instance let the link:aggregator.html[Aggregator]
aggregate this number of messages.
-[[AWS-KINESIS-Usage]]
-Usage
-^^^^^
+### Usage
-[[AWS-KINESIS-MessageheaderssetbytheKinesisconsumer]]
-Message headers set by the Kinesis consumer
-+++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the Kinesis consumer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -116,9 +106,7 @@ size is not defined by the API. If it is to be used as a numerical type then use
|`CamelAwsKinesisPartitionKey` |`String` |Identifies which shard in the stream the data record is assigned to.
|=======================================================================
-[[AWS-KINESIS-AmazonKinesisconfiguration]]
-AmazonKinesis configuration
-+++++++++++++++++++++++++++
+#### AmazonKinesis configuration
You will need to create an instance of AmazonDynamoDBStreamsClient and
bind it to the registry
@@ -136,9 +124,7 @@ region.createClient(AmazonDynamoDBStreamsClient.class, null, clientConfiguration
registry.bind("kinesisClient", client);
--------------------------------------------------------------------------------------------------------------------
-[[AWS-KINESIS-ProvidingAWSCredentials]]
-Providing AWS Credentials
-+++++++++++++++++++++++++
+#### Providing AWS Credentials
It is recommended that the credentials are obtained by using the
http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/DefaultAWSCredentialsProviderChain.html[DefaultAWSCredentialsProviderChain]
@@ -147,9 +133,7 @@ however, a
different�http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/AWSCredentialsProvider.html[AWSCredentialsProvider]
can be specified when calling createClient(...).
-[[AWS-Kinesis-MessageheaderssetbytheKinesisproducer]]
-Message headers used by the Kinesis producer to write to Kinesis. The producer expects that the message body is a `ByteBuffer`.
-+++++++++++++++++++++++++++++++++++++++
+#### Message headers used by the Kinesis producer to write to Kinesis. The producer expects that the message body is a `ByteBuffer`.
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -161,8 +145,7 @@ Message headers used by the Kinesis producer to write to Kinesis. The producer
|=======================================================================
-Message headers set by the Kinesis producer on successful storage of a Record
-+++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the Kinesis producer on successful storage of a Record
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -176,9 +159,7 @@ http://docs.aws.amazon.com/kinesis/latest/APIReference/API_PutRecord.html#API_Pu
|=======================================================================
-[[AWS-KINESIS-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -196,14 +177,11 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.17 or higher).
-[[AWS-KINESIS-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:aws.html[AWS Component]
-
+* link:aws.html[AWS Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-aws/src/main/docs/aws-s3-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-s3-component.adoc b/components/camel-aws/src/main/docs/aws-s3-component.adoc
index 581740f..5d1f9e1 100644
--- a/components/camel-aws/src/main/docs/aws-s3-component.adoc
+++ b/components/camel-aws/src/main/docs/aws-s3-component.adoc
@@ -1,4 +1,4 @@
-# AWS S3 Storage Service Component
+## AWS S3 Storage Service Component
*Available as of Camel 2.8*
@@ -11,9 +11,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon S3. More information are available at
http://aws.amazon.com/s3[Amazon S3].
-[[AWS-S3-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
------------------------------
@@ -33,9 +31,7 @@ from("aws-s3:helloBucket?accessKey=yourAccessKey&secretKey=yourSecretKey&prefix=
--------------------------------------------------------------------------------
-[[AWS-S3-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -117,9 +113,7 @@ You have to provide the amazonS3Client in the
link:registry.html[Registry] or your accessKey and secretKey to access
the http://aws.amazon.com/s3[Amazon's S3].
-[[AWS-S3-BatchConsumer]]
-Batch Consumer
-^^^^^^^^^^^^^^
+### Batch Consumer
This component implements the link:batch-consumer.html[Batch Consumer].
@@ -127,13 +121,9 @@ This allows you for instance to know how many messages exists in this
batch and for instance let the link:aggregator.html[Aggregator]
aggregate this number of messages.
-[[AWS-S3-Usage]]
-Usage
-^^^^^
+### Usage
-[[AWS-S3-MessageheadersevaluatedbytheS3producer]]
-Message headers evaluated by the S3 producer
-++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the S3 producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -180,9 +170,7 @@ the object using AWS-managed keys. For example use AES256.
|`CamelAwsS3VersionId` |`String` |The version Id of the object to be stored or returned from the current operation
|=======================================================================
-[[AWS-S3-MessageheaderssetbytheS3producer]]
-Message headers set by the S3 producer
-++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the S3 producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -193,9 +181,7 @@ Message headers set by the S3 producer
|=======================================================================
-[[AWS-S3-MessageheaderssetbytheS3consumer]]
-Message headers set by the S3 consumer
-++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the S3 consumer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -244,9 +230,7 @@ specify caching behavior along the HTTP request/reply chain.
object using AWS-managed keys.
|=======================================================================
-[[AWS-S3-AdvancedAmazonS3configuration]]
-Advanced AmazonS3 configuration
-+++++++++++++++++++++++++++++++
+#### Advanced AmazonS3 configuration
If your Camel Application is running behind a firewall or if you need to
have more control over the `AmazonS3` instance configuration, you can
@@ -273,9 +257,7 @@ from("aws-s3://MyBucket?amazonS3Client=#client&delay=5000&maxMessagesPerPoll=5")
.to("mock:result");
--------------------------------------------------------------------------------
-[[AWS-S3-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -293,14 +275,11 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.8 or higher).
-[[AWS-S3-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:aws.html[AWS Component]
-
+* link:aws.html[AWS Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-aws/src/main/docs/aws-sdb-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-sdb-component.adoc b/components/camel-aws/src/main/docs/aws-sdb-component.adoc
index 70cef12..5beac46 100644
--- a/components/camel-aws/src/main/docs/aws-sdb-component.adoc
+++ b/components/camel-aws/src/main/docs/aws-sdb-component.adoc
@@ -1,4 +1,4 @@
-# AWS SimpleDB Component
+## AWS SimpleDB Component
*Available as of Camel 2.8.4*
@@ -11,9 +11,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon SDB. More information are available at
http://aws.amazon.com/sdb[Amazon SDB].
-[[AWS-SDB-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
------------------------------
@@ -23,9 +21,7 @@ aws-sdb://domainName[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-[[AWS-SDB-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -65,13 +61,9 @@ You have to provide the amazonSDBClient in the
link:registry.html[Registry] or your accessKey and secretKey to access
the http://aws.amazon.com/sdb[Amazon's SDB].
-[[AWS-SDB-Usage]]
-Usage
-^^^^^
+### Usage
-[[AWS-SDB-MessageheadersevaluatedbytheSDBproducer]]
-Message headers evaluated by the SDB producer
-+++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the SDB producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -107,9 +99,7 @@ to 100.
specified attributes will be updated/deleted or not.
|=======================================================================
-[[AWS-SDB-MessageheaderssetduringDomainMetadataoperation]]
-Message headers set during DomainMetadata operation
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during DomainMetadata operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -130,9 +120,7 @@ Message headers set during DomainMetadata operation
|`CamelAwsSdbItemNameSize` |`Long` |The total size of all item names in the domain, in bytes.
|=======================================================================
-[[AWS-SDB-MessageheaderssetduringGetAttributesoperation]]
-Message headers set during GetAttributes operation
-++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during GetAttributes operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -141,9 +129,7 @@ Message headers set during GetAttributes operation
|`CamelAwsSdbAttributes` |`List<Attribute>` |The list of attributes returned by the operation.
|=======================================================================
-[[AWS-SDB-MessageheaderssetduringListDomainsoperation]]
-Message headers set during ListDomains operation
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during ListDomains operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -155,9 +141,7 @@ Message headers set during ListDomains operation
specified MaxNumberOfDomains still available.
|=======================================================================
-[[AWS-SDB-MessageheaderssetduringSelectoperation]]
-Message headers set during Select operation
-+++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during Select operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -170,9 +154,7 @@ matched, the response size exceeded 1 megabyte, or the execution time
exceeded 5 seconds.
|=======================================================================
-[[AWS-SDB-AdvancedAmazonSimpleDBconfiguration]]
-Advanced AmazonSimpleDB configuration
-+++++++++++++++++++++++++++++++++++++
+#### Advanced AmazonSimpleDB configuration
If you need more control over the `AmazonSimpleDB` instance
configuration you can create your own instance and refer to it from the
@@ -201,9 +183,7 @@ AmazonSimpleDB client = new AmazonSimpleDBClient(awsCredentials, clientConfigura
registry.bind("client", client);
--------------------------------------------------------------------------------------
-[[AWS-SDB-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -221,14 +201,11 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.8.4 or higher).
-[[AWS-SDB-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:aws.html[AWS Component]
-
+* link:aws.html[AWS Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-aws/src/main/docs/aws-ses-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-ses-component.adoc b/components/camel-aws/src/main/docs/aws-ses-component.adoc
index 0b45ea6..e222899 100644
--- a/components/camel-aws/src/main/docs/aws-ses-component.adoc
+++ b/components/camel-aws/src/main/docs/aws-ses-component.adoc
@@ -1,4 +1,4 @@
-# AWS Simple Email Service Component
+## AWS Simple Email Service Component
*Available as of Camel 2.8.4*
@@ -11,9 +11,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon SES. More information are available at
http://aws.amazon.com/ses[Amazon SES].
-[[AWS-SES-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
------------------------
@@ -23,9 +21,7 @@ aws-ses://from[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-[[AWS-SES-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -66,13 +62,9 @@ You have to provide the amazonSESClient in the
link:registry.html[Registry] or your accessKey and secretKey to access
the http://aws.amazon.com/ses[Amazon's SES].
-[[AWS-SES-Usage]]
-Usage
-^^^^^
+### Usage
-[[AWS-SES-MessageheadersevaluatedbytheSESproducer]]
-Message headers evaluated by the SES producer
-+++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the SES producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -91,9 +83,7 @@ Message headers evaluated by the SES producer
|`CamelAwsSesHtmlEmail` |`Boolean` |*Since Camel 2.12.3* The flag to show if email content is HTML.
|=======================================================================
-[[AWS-SES-MessageheaderssetbytheSESproducer]]
-Message headers set by the SES producer
-+++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the SES producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -102,9 +92,7 @@ Message headers set by the SES producer
|`CamelAwsSesMessageId` |`String` |The Amazon SES message ID.
|=======================================================================
-[[AWS-SES-AdvancedAmazonSimpleEmailServiceconfiguration]]
-Advanced AmazonSimpleEmailService configuration
-+++++++++++++++++++++++++++++++++++++++++++++++
+#### Advanced AmazonSimpleEmailService configuration
If you need more control over the `AmazonSimpleEmailService` instance
configuration you can create your own instance and refer to it from the
@@ -132,9 +120,7 @@ AmazonSimpleEmailService client = new AmazonSimpleEmailServiceClient(awsCredenti
registry.bind("client", client);
----------------------------------------------------------------------------------------------------------
-[[AWS-SES-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -152,14 +138,11 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.8.4 or higher).
-[[AWS-SES-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:aws.html[AWS Component]
-
+* link:aws.html[AWS Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-aws/src/main/docs/aws-sns-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-sns-component.adoc b/components/camel-aws/src/main/docs/aws-sns-component.adoc
index 479a3ba..65bfdf8 100644
--- a/components/camel-aws/src/main/docs/aws-sns-component.adoc
+++ b/components/camel-aws/src/main/docs/aws-sns-component.adoc
@@ -1,4 +1,4 @@
-# AWS Simple Notification System Component
+## AWS Simple Notification System Component
*Available as of Camel 2.8*
@@ -13,9 +13,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon SNS. More information are available at
http://aws.amazon.com/sns[Amazon SNS].
-[[AWS-SNS-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
-----------------------------
@@ -26,9 +24,7 @@ The topic will be created if they don't already exists. +
You can append query options to the URI in the following format,
`?options=value&option2=value&...`
-[[AWS-SNS-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -70,13 +66,9 @@ You have to provide the amazonSNSClient in the
link:registry.html[Registry] or your accessKey and secretKey to access
the http://aws.amazon.com/sns[Amazon's SNS].
-[[AWS-SNS-Usage]]
-Usage
-^^^^^
+### Usage
-[[AWS-SNS-MessageheadersevaluatedbytheSNSproducer]]
-Message headers evaluated by the SNS producer
-+++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the SNS producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -86,9 +78,7 @@ Message headers evaluated by the SNS producer
`SnsConfiguration` is used.
|=======================================================================
-[[AWS-SNS-MessageheaderssetbytheSNSproducer]]
-Message headers set by the SNS producer
-+++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the SNS producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -97,9 +87,7 @@ Message headers set by the SNS producer
|`CamelAwsSnsMessageId` |`String` |The Amazon SNS message ID.
|=======================================================================
-[[AWS-SNS-AdvancedAmazonSNSconfiguration]]
-Advanced AmazonSNS configuration
-++++++++++++++++++++++++++++++++
+#### Advanced AmazonSNS configuration
If you need more control over the `AmazonSNS` instance configuration you
can create your own instance and refer to it from the URI:
@@ -126,9 +114,7 @@ AmazonSNS client = new AmazonSNSClient(awsCredentials, clientConfiguration);
registry.bind("client", client);
--------------------------------------------------------------------------------------
-[[AWS-SNS-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -146,14 +132,11 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.8 or higher).
-[[AWS-SNS-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:aws.html[AWS Component]
-
+* link:aws.html[AWS Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-aws/src/main/docs/aws-sqs-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-sqs-component.adoc b/components/camel-aws/src/main/docs/aws-sqs-component.adoc
index 3bbca32..29e870a 100644
--- a/components/camel-aws/src/main/docs/aws-sqs-component.adoc
+++ b/components/camel-aws/src/main/docs/aws-sqs-component.adoc
@@ -1,4 +1,4 @@
-# AWS Simple Queue Service Component
+## AWS Simple Queue Service Component
*Available as of Camel 2.6*
@@ -11,9 +11,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon SQS. More information are available at
http://aws.amazon.com/sqs[Amazon SQS].
-[[AWS-SQS-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
------------------------------
@@ -24,9 +22,7 @@ The queue will be created if they don't already exists. +
You can append query options to the URI in the following format,
?options=value&option2=value&...
-[[AWS-SQS-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -108,9 +104,7 @@ You have to provide the amazonSQSClient in the
link:registry.html[Registry] or your accessKey and secretKey to access
the http://aws.amazon.com/sqs[Amazon's SQS].
-[[AWS-SQS-BatchConsumer]]
-Batch Consumer
-^^^^^^^^^^^^^^
+### Batch Consumer
This component implements the link:batch-consumer.html[Batch Consumer].
@@ -118,13 +112,9 @@ This allows you for instance to know how many messages exists in this
batch and for instance let the link:aggregator.html[Aggregator]
aggregate this number of messages.
-[[AWS-SQS-Usage]]
-Usage
-^^^^^
+### Usage
-[[AWS-SQS-MessageheaderssetbytheSQSproducer]]
-Message headers set by the SQS producer
-+++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the SQS producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -138,9 +128,7 @@ Message headers set by the SQS producer
see by others.
|=======================================================================
-[[AWS-SQS-MessageheaderssetbytheSQSconsumer]]
-Message headers set by the SQS consumer
-+++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the SQS consumer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -155,9 +143,7 @@ Message headers set by the SQS consumer
|`CamelAwsSqsAttributes` |`Map<String, String>` |The Amazon SQS message attributes.
|=======================================================================
-[[AWS-SQS-AdvancedAmazonSQSconfiguration]]
-Advanced AmazonSQS configuration
-++++++++++++++++++++++++++++++++
+#### Advanced AmazonSQS configuration
If your Camel Application is running behind a firewall or if you need to
have more control over the AmazonSQS instance configuration, you can
@@ -184,9 +170,7 @@ from("aws-sqs://MyQueue?amazonSQSClient=#client&delay=5000&maxMessagesPerPoll=5"
.to("mock:result");
---------------------------------------------------------------------------------
-[[AWS-SQS-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -204,9 +188,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.6 or higher).
-[[AWS-SQS-JMS-styleSelectors]]
-JMS-style Selectors
-^^^^^^^^^^^^^^^^^^^
+### JMS-style Selectors
SQS does not allow selectors, but you can effectively achieve this by
using the link:message-filter.html[Camel Filter EIP] and setting an
@@ -230,14 +212,11 @@ will not make it through the filter AND also not be deleted from the SQS
queue. After 5000 miliseconds, the message will become visible to other
consumers.
-[[AWS-SQS-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:aws.html[AWS Component]
-
+* link:aws.html[AWS Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-aws/src/main/docs/aws-swf-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-swf-component.adoc b/components/camel-aws/src/main/docs/aws-swf-component.adoc
index ff40134..18247bc 100644
--- a/components/camel-aws/src/main/docs/aws-swf-component.adoc
+++ b/components/camel-aws/src/main/docs/aws-swf-component.adoc
@@ -1,4 +1,4 @@
-# AWS Simple Workflow Component
+## AWS Simple Workflow Component
*Available as of Camel 2.13*
@@ -11,9 +11,7 @@ You must have a valid Amazon Web Services developer account, and be
signed up to use Amazon Simple Workflow. More information are available
at http://aws.amazon.com/swf/[Amazon Simple Workflow].
-[[AWS-SWF-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
---------------------------------------
@@ -23,9 +21,7 @@ aws-swf://<workflow|activity>[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-[[AWS-SWF-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -84,13 +80,9 @@ You have to provide the�amazonSWClient in the
link:registry.html[Registry] or your accessKey and secretKey to access
the http://aws.amazon.com/swf[Amazon's Simple Workflow Service].
-[[AWS-SWF-Usage]]
-Usage
-^^^^^
+### Usage
-[[AWS-SWF-MessageheadersevaluatedbytheSWFWorkflowProducer]]
-Message headers evaluated by the SWF Workflow Producer
-++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the SWF Workflow Producer
A workflow producer allows interacting with a workflow. It can start a
new workflow execution, query its state, send signals to a running
@@ -120,9 +112,7 @@ workflow, or terminate and cancel it.
|`CamelSWFChildPolicy` |`String` |The policy to use on child workflows when terminating a workflow.
|=======================================================================
-[[AWS-SWF-MessageheaderssetbytheSWFWorkflowProducer]]
-Message headers set by the SWF Workflow Producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the SWF Workflow Producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -133,9 +123,7 @@ Message headers set by the SWF Workflow Producer
|`CamelAwsDdbKeyCamelSWFRunId` |`String` |The worfklow run ID used or generated.
|=======================================================================
-[[AWS-SWF-MessageheaderssetbytheSWFWorkflowConsumer]]
-Message headers set by the SWF Workflow Consumer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the SWF Workflow Consumer
A workflow consumer represents the workflow logic. When it is started,
it will start polling workflow decision tasks and process them. In
@@ -157,9 +145,7 @@ CamelSWFSignalReceivedAction or CamelSWFGetStateAction.
|`CamelSWFWorkflowStartTime` |`long` |The time of the start event for this decision task.
|=======================================================================
-[[AWS-SWF-MessageheaderssetbytheSWFActivityProducer]]
-Message headers set by the SWF Activity Producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the SWF Activity Producer
An activity producer allows scheduling activity tasks. An activity
producer can be used only from a thread started by a workflow consumer
@@ -174,9 +160,7 @@ ie, it can process synchronous exchanges started by a workflow consumer.
|`CamelSWFVersion` |`String` |The activity version to schedule.
|=======================================================================
-[[AWS-SWF-MessageheaderssetbytheSWFActivityConsumer]]
-Message headers set by the SWF Activity Consumer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the SWF Activity Consumer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -186,9 +170,7 @@ Message headers set by the SWF Activity Consumer
completed tasks.
|=======================================================================
-[[AWS-SWF-AdvancedamazonSWClientconfiguration]]
-Advanced amazonSWClient configuration
-+++++++++++++++++++++++++++++++++++++
+#### Advanced amazonSWClient configuration
If you need more control over the�AmazonSimpleWorkflowClient instance
configuration you can create your own instance and refer to it from the
@@ -211,9 +193,7 @@ AmazonSimpleWorkflowClient client = new AmazonSimpleWorkflowClient(awsCredential
registry.bind("client", client);
--------------------------------------------------------------------------------------------------------
-[[AWS-SWF-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -231,13 +211,11 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.13 or higher).
-[[AWS-SWF-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:aws.html[AWS Component]
+link:aws.html[AWS Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-barcode/src/main/docs/barcode-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-barcode/src/main/docs/barcode-dataformat.adoc b/components/camel-barcode/src/main/docs/barcode-dataformat.adoc
index e6d6810..56323d2 100644
--- a/components/camel-barcode/src/main/docs/barcode-dataformat.adoc
+++ b/components/camel-barcode/src/main/docs/barcode-dataformat.adoc
@@ -1,4 +1,4 @@
-# Barcode DataFormat
+## Barcode DataFormat
*Available as of Camel 2.14*
@@ -8,9 +8,7 @@ component is to create a barcode image from a String (marshal) and a
String from a barcode image (unmarshal). You're free to use all features
that zxing offers.
-[[BarcodeDataFormat-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use the barcode data format in your camel routes you need to add the
a dependency on *camel-barcode* which implements this data format.
@@ -28,9 +26,7 @@ link:download.html[the download page for the latest versions]).
</dependency>
----------------------------------------
-[[Barcode-Options]]
-Barcode Options
-^^^^^^^^^^^^^^^
+### Barcode Options
// dataformat options: START
The Barcode dataformat supports 5 options which are listed below.
@@ -50,9 +46,7 @@ The Barcode dataformat supports 5 options which are listed below.
{% endraw %}
// dataformat options: END
-[[BarcodeDataFormat-UsingtheJavaDSL]]
-Using the Java DSL
-^^^^^^^^^^^^^^^^^^
+### Using the Java DSL
First you have to initialize the barcode data fomat class. You can use
the default constructor, or one of parameterized (see JavaDoc). The
@@ -88,9 +82,7 @@ code.addToHintMap(DecodeHintType.TRY_HARDER, Boolean.true);
For possible hints, please consult the xzing documentation.
-[[BarcodeDataFormat-Marshalling]]
-Marshalling
-+++++++++++
+#### Marshalling
[source,java]
----------------------------
@@ -110,9 +102,7 @@ You should find inside the 'barcode_out' folder this image:
image:barcode-data-format.data/qr-code.png[image]
-[[BarcodeDataFormat-Unmarshalling]]
-Unmarshalling
-+++++++++++++
+#### Unmarshalling
The unmarshaller is generic. For unmarshalling you can use any
BarcodeDataFormat instance. If you've two instances, one for
@@ -139,4 +129,4 @@ the barcode data format as header variable:
|=======================================================================
�
-�
+�
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-base64/src/main/docs/base64-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-base64/src/main/docs/base64-dataformat.adoc b/components/camel-base64/src/main/docs/base64-dataformat.adoc
index abafbb3..19f3316 100644
--- a/components/camel-base64/src/main/docs/base64-dataformat.adoc
+++ b/components/camel-base64/src/main/docs/base64-dataformat.adoc
@@ -1,12 +1,10 @@
-# Base64 DataFormat
+## Base64 DataFormat
*Available as of Camel 2.11* +
The Base64 link:data-format.html[Data Format] is a data format for
http://en.wikipedia.org/wiki/Base64[base64 encoding and decoding].
-[[Base64-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The Base64 dataformat supports 4 options which are listed below.
@@ -54,9 +52,7 @@ Most of the time, you won't need to declare the data format if you use
the default options. In that case, you can declare the data format
inline as shown below.
-[[Base64-Marshal]]
-Marshal
-^^^^^^^
+### Marshal
In this example we marshal the file content to base64 object.
@@ -76,9 +72,7 @@ In Spring DSL:
<to uri="jms://myqueue"/>
-----------------------------
-[[Base64-Unmarshal]]
-Unmarshal
-^^^^^^^^^
+### Unmarshal
In this example we unmarshal the payload from the JMS queue to a byte[]
object, before its processed by the newOrder processor.
@@ -99,9 +93,7 @@ In Spring DSL:
<to uri="bean:newOrder"/>
-------------------------------
-[[Base64-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Base64 in your Camel routes you need to add a dependency on
*camel-base64* which implements this data format.
@@ -115,4 +107,4 @@ If you use Maven you can just add the following to your pom.xml:
<artifactId>camel-base64</artifactId>
<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-bean-validator/src/main/docs/bean-validator-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc b/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc
index ba3b418..ec3f62a 100644
--- a/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc
+++ b/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc
@@ -1,4 +1,4 @@
-# Bean Validator Component
+## Bean Validator Component
*Available as of Camel 2.3*
@@ -22,9 +22,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[BeanValidator-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------
@@ -42,9 +40,7 @@ Where *label* is an arbitrary text value describing the endpoint. +
You can append query options to the URI in the following format,
?option=value&option=value&...
-[[BeanValidator-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -72,9 +68,7 @@ The Bean Validator component supports 7 endpoint options which are listed below:
// endpoint options: END
-[[BeanValidator-OSGideployment]]
-OSGi deployment
-^^^^^^^^^^^^^^^
+### OSGi deployment
To use Hibernate Validator in the OSGi environment use dedicated
`ValidationProviderResolver` implementation, just as
@@ -99,9 +93,7 @@ If no custom�`ValidationProviderResolver` is defined and the validator
component has been deployed into the OSGi environment,
the�`HibernateValidationProviderResolver` will be automatically used.
-[[BeanValidator-Example]]
-Example
-^^^^^^^
+### Example
Assumed we have a java bean with the following annotations
@@ -244,12 +236,9 @@ and the `constraints-car.xml` file
</constraint-mappings>
----------------------------------------------------------------------------------------------------
-[[BeanValidator-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-beanio/src/main/docs/beanio-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-beanio/src/main/docs/beanio-dataformat.adoc b/components/camel-beanio/src/main/docs/beanio-dataformat.adoc
index 06e7518..c23409c 100644
--- a/components/camel-beanio/src/main/docs/beanio-dataformat.adoc
+++ b/components/camel-beanio/src/main/docs/beanio-dataformat.adoc
@@ -1,4 +1,4 @@
-# BeanIO DataFormat
+## BeanIO DataFormat
*Available as of Camel 2.10*
@@ -11,9 +11,7 @@ http://beanio.org/2.0/docs/reference/index.html#TheMappingFile[mappings
XML] file where you define the mapping from the flat format to Objects
(POJOs). This mapping file is mandatory to use.
-[[BeanIO-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The BeanIO dataformat supports 8 options which are listed below.
@@ -36,17 +34,13 @@ The BeanIO dataformat supports 8 options which are listed below.
{% endraw %}
// dataformat options: END
-[[BeanIO-Usage]]
-Usage
-^^^^^
+### Usage
An example of a
https://svn.apache.org/repos/asf/camel/trunk/components/camel-beanio/src/test/resources/org/apache/camel/dataformat/beanio/mappings.xml[mapping
file is here].
-[[BeanIO-UsingJavaDSL]]
-Using Java DSL
-++++++++++++++
+#### Using Java DSL
To use the `BeanIODataFormat` you need to configure the data format with
the mapping file, as well the name of the stream. +
@@ -63,17 +57,13 @@ List<Employee> into a stream of CSV data.
The CSV data could for example be as below:
-[[BeanIO-UsingXMLDSL]]
-Using XML DSL
-+++++++++++++
+#### Using XML DSL
To use the BeanIO data format in XML, you need to configure it using the
<beanio> XML tag as shown below. The routes is similar to the example
above.
-[[BeanIO-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use BeanIO in your Camel routes you need to add a dependency on
*camel-beanio* which implements this data format.
@@ -89,4 +79,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-beanio</artifactId>
<version>2.10.0</version>
</dependency>
----------------------------------------
+---------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
index 1c8bad8..f88cd85 100644
--- a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
+++ b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
@@ -1,4 +1,4 @@
-# Beanstalk Component
+## Beanstalk Component
*Available in Camel 2.15*
@@ -9,9 +9,7 @@ You can find the detailed explanation of Beanstalk job lifecycle
at�http://github.com/kr/beanstalkd/blob/v1.3/doc/protocol.txt[Beanstalk
protocol].
-[[Beanstalk-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users need to add the following dependency to their `pom.xml`
@@ -27,9 +25,7 @@ Maven users need to add the following dependency to their `pom.xml`
where `${camel-version`} must be replaced by the actual version of Camel
(2.15.0 or higher).
-[[Beanstalk-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,xml]
------------------------------------------
@@ -56,9 +52,7 @@ details here].
By the way, you cannot specify several tubes when you are writing jobs
into Beanstalk.
-[[Beanstalk-options]]
-Beanstalk options
-^^^^^^^^^^^^^^^^^
+### Beanstalk options
@@ -146,9 +140,7 @@ Consumer] which means there is more options you can configure, such as
how frequent the consumer should poll. For more details
see�link:polling-consumer.html[Polling Consumer].
-[[Beanstalk-ConsumerHeaders]]
-Consumer Headers
-^^^^^^^^^^^^^^^^
+### Consumer Headers
The consumer stores a number of job headers in the Exchange message:
@@ -178,9 +170,7 @@ queue
|_beanstalk.kicks_ |int |the number of times this job has been kicked
|=======================================================================
-[[Beanstalk-Examples]]
-Examples
-^^^^^^^^
+### Examples
This Camel component lets you both request the jobs for processing and
supply them to Beanstalkd daemon. Our simple demo routes may look like
@@ -220,12 +210,9 @@ out of buried and/or delayed state to the normal queue.
�
-[[Beanstalk-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-bindy/src/main/docs/bindy-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-bindy/src/main/docs/bindy-dataformat.adoc b/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
index b32aa26..1cd20c7 100644
--- a/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
+++ b/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
@@ -1,4 +1,4 @@
-# Bindy DataFormat
+## Bindy DataFormat
The goal of this component is to allow the parsing/binding of
non-structured data (or to be more precise non-XML data) +
@@ -50,9 +50,7 @@ From *Camel 2.16* onwards this is no longer the case, as you can safely
have multiple models in the same package, as you configure bindy using
class names instead of package names now.
-[[Bindy-Options]]
-Options
-^^^^^^^
+### Options
@@ -91,9 +89,7 @@ The Bindy dataformat supports 4 options which are listed below.
-[[Bindy-Annotations]]
-Annotations
-~~~~~~~~~~~
+### Annotations
The annotations created allow to map different concept of your model to
the POJO like :
@@ -111,9 +107,7 @@ financial messages),
This section will describe them :
-[[Bindy-1.CsvRecord]]
-1. CsvRecord
-^^^^^^^^^^^^
+### 1. CsvRecord
The CsvRecord annotation is used to identified the root class of the
model. It represents a record = a line of a CSV file and can be linked
@@ -351,9 +345,7 @@ public Class Order {
Remark : pos is used to parse the file, stream while positions is used
to generate the CSV
-[[Bindy-2.Link]]
-2. Link
-^^^^^^^
+### 2. Link
The link annotation will allow to link objects together.
@@ -405,9 +397,7 @@ public class Client {
}
---------------------
-[[Bindy-3.DataField]]
-3. DataField
-^^^^^^^^^^^^
+### 3. DataField
The DataField annotation defines the property of the field. Each
datafield is identified by its position in the record, a type (string,
@@ -708,9 +698,7 @@ public class Order {
This attribute is only applicable to optional fields.
-[[Bindy-4.FixedLengthRecord]]
-4. FixedLengthRecord
-^^^^^^^^^^^^^^^^^^^^
+### 4. FixedLengthRecord
The FixedLengthRecord annotation is used to identified the root class of
the model. It represents a record = a line of a file/message containing
@@ -1141,9 +1129,7 @@ public static class Order {
}
-------------------------------------------------------------------------------
-[[Bindy-5.Message]]
-5. Message
-^^^^^^^^^^
+### 5. Message
The Message annotation is used to identified the class of your model who
will contain key value pairs fields. This kind of format is used mainly
@@ -1222,9 +1208,7 @@ message looks like (src\test\data\fix\fix.txt) and the Order, Trailer,
Header classes
(src\test\java\org\apache\camel\dataformat\bindy\model\fix\simple\Order.java)
-[[Bindy-6.KeyValuePairField]]
-6. KeyValuePairField
-^^^^^^^^^^^^^^^^^^^^
+### 6. KeyValuePairField
The KeyValuePairField annotation defines the property of a key value
pair field. Each KeyValuePairField is identified by a tag (= key) and
@@ -1324,9 +1308,7 @@ public class Order {
}
-----------------------------------------------------------------------------------------------------------------
-[[Bindy-7.Section]]
-7. Section
-^^^^^^^^^^
+### 7. Section
In FIX message of fixed length records, it is common to have different
sections in the representation of the information : header, body and
@@ -1409,9 +1391,7 @@ public class Trailer {
}
----------------------------------------------
-[[Bindy-8.OneToMany]]
-8. OneToMany
-^^^^^^^^^^^^
+### 8. OneToMany
The purpose of the annotation @OneToMany is to allow to work with a
List<?> field defined a POJO class or from a record containing
@@ -1540,9 +1520,7 @@ public class Security {
private String side;
---------------------------------------------------------------------------------------------------
-[[Bindy-9.BindyConverter]]
-9. BindyConverter
-^^^^^^^^^^^^^^^^^
+### 9. BindyConverter
The purpose of the annotation @BindyConverter is define a converter
to be used on field level. The provided class must implement the
@@ -1572,9 +1550,7 @@ Format interface.
...
---------------------------------------------------------------------------------------------------
-[[Bindy-10.FormatFactories]]
-10. FormatFactories
-^^^^^^^^^^^^^^^^^^^
+### 10. FormatFactories
The purpose of the annotation @FormatFactories is to define a set of converters
at record-level. The provided classes must implement the FormatFactoryInterface interface.
@@ -1627,9 +1603,7 @@ at record-level. The provided classes must implement the FormatFactoryInterface
}
---------------------------------------------------------------------------------------------------
-[[Bindy-SupportedDatatypes]]
-Supported Datatypes
-^^^^^^^^^^^^^^^^^^^
+### Supported Datatypes
The DefaultFormatFactory makes formatting of the following datatype available by
returning an instance of the interface FormatFactoryInterface based on the provided
@@ -1655,9 +1629,7 @@ FormattingOptions:
The DefaultFormatFactory can be overridden by providing an instance of
FactoryRegistry in the registry in use (e.g. spring or JNDI).
-[[Bindy-UsingtheJavaDSL]]
-Using the Java DSL
-^^^^^^^^^^^^^^^^^^
+### Using the Java DSL
The next step consists in instantiating the DataFormat _bindy_ class
associated with this record type and providing Java package name(s) as
@@ -1679,9 +1651,7 @@ DataFormat bindy = new BindyCsvDataFormat("com.acme.model");
DataFormat bindy = new BindyCsvDataFormat(com.acme.model.MyModel.class);
------------------------------------------------------------------------
-[[Bindy-Settinglocale]]
-Setting locale
-++++++++++++++
+#### Setting locale
Bindy supports configuring the locale on the dataformat, such as�
@@ -1721,9 +1691,7 @@ BindyCsvDataFormat bindy = new BindyCsvDataFormat(com.acme.model.MyModel.class);
bindy.setLocale(Locale.getDefault().getISO3Country());
--------------------------------------------------------------------------------
-[[Bindy-Unmarshaling]]
-Unmarshaling
-++++++++++++
+#### Unmarshaling
[source,java]
-----------------------------
@@ -1807,9 +1775,7 @@ from("file://inbox?charset=Cp922")
.to("direct:handleOrders");
---------------------------------
-[[Bindy-Marshaling]]
-Marshaling
-++++++++++
+#### Marshaling
To generate CSV records from a collection of model objects, you create
the following route :
@@ -1821,9 +1787,7 @@ from("direct:handleOrders")
.to("file://outbox")
---------------------------
-[[Bindy-UsingSpringXML]]
-Using Spring XML
-^^^^^^^^^^^^^^^^
+### Using Spring XML
This is really easy to use Spring as your favorite DSL language to
declare the routes to be used for camel-bindy. The following example
@@ -1887,9 +1851,7 @@ the queue manager will raise an error
====
-[[Bindy-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Bindy in your camel routes you need to add the a dependency on
*camel-bindy* which implements this data format.
@@ -1905,4 +1867,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-bindy</artifactId>
<version>x.x.x</version>
</dependency>
---------------------------------------
+--------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-bonita/src/main/docs/bonita-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-bonita/src/main/docs/bonita-component.adoc b/components/camel-bonita/src/main/docs/bonita-component.adoc
index 820151c..cf3b709 100644
--- a/components/camel-bonita/src/main/docs/bonita-component.adoc
+++ b/components/camel-bonita/src/main/docs/bonita-component.adoc
@@ -1,12 +1,10 @@
-# Bonita Component
+## Bonita Component
*Available as of Camel 2.19*
This Camel component allow you to communicate with a remote Bonita engine.
-[[Bonita-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------
@@ -15,9 +13,7 @@ bonita://[operation]?[options]
Where *operation* is the specific action to perform on Bonita.
-[[Bonita-Options]]
-General Options
-^^^^^^^^^^^^^^^
+### General Options
// component options: START
The Bonita component has no options.
@@ -45,16 +41,12 @@ The Bonita component supports 10 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[Bonita-BodyMessage]]
-Body content
-^^^^^^^^^^^^
+### Body content
For the startCase operation, the input variables are retrieved from the body message. This one has to contains a Map<String,Serializable>.
-[[Bonita-Examples]]
-Examples
-^^^^^^^^
+### Examples
The following example start a new case in Bonita:
@@ -63,9 +55,7 @@ The following example start a new case in Bonita:
from("direct:start).to("bonita:startCase?hostname=localhost&port=8080&processName=TestProcess&username=install&password=install")
----------------------------------------------------------------------
-[[Bonita-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Bonita in your Camel routes you need to add a dependency on
*camel-bonita*, which implements the component.
@@ -81,4 +71,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-bonita</artifactId>
<version>x.x.x</version>
</dependency>
--------------------------------------
+-------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-boon/src/main/docs/boon-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-boon/src/main/docs/boon-dataformat.adoc b/components/camel-boon/src/main/docs/boon-dataformat.adoc
index 1f882d3..6196c10 100644
--- a/components/camel-boon/src/main/docs/boon-dataformat.adoc
+++ b/components/camel-boon/src/main/docs/boon-dataformat.adoc
@@ -1,4 +1,4 @@
-# Boon DataFormat
+## Boon DataFormat
*Available in Camel 2.16*
@@ -10,9 +10,7 @@ simple
and�https://github.com/RichardHightower/json-parsers-benchmark[fast
parser]�than other common parsers currently used.
-[[Boon-Options]]
-Options
-^^^^^^^
+### Options
@@ -37,9 +35,7 @@ The Boon dataformat supports 3 options which are listed below.
-[[Boon-UsingtheJavaDSL]]
-Using the Java DSL
-^^^^^^^^^^^^^^^^^^
+### Using the Java DSL
[source,java]
------------------------------------------------------------------------
@@ -50,9 +46,7 @@ from("activemq:My.Queue")
.to("mqseries:Another.Queue");
------------------------------------------------------------------------
-[[Boon-UsingBlueprintXML]]
-Using Blueprint XML
-^^^^^^^^^^^^^^^^^^^
+### Using Blueprint XML
[source,java]
---------------------------------------------------------------------------------
@@ -69,9 +63,7 @@ Using Blueprint XML
</camelContext>
---------------------------------------------------------------------------------
-[[Boon-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
[source,java]
-------------------------------------
@@ -80,4 +72,4 @@ Dependencies
<artifactId>camel-boon</artifactId>
<version>x.x.x</version>
</dependency>
--------------------------------------
+-------------------------------------
\ No newline at end of file
[03/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-slack/src/main/docs/slack-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-slack/src/main/docs/slack-component.adoc b/components/camel-slack/src/main/docs/slack-component.adoc
index 9e0a5bc..6b41a65 100644
--- a/components/camel-slack/src/main/docs/slack-component.adoc
+++ b/components/camel-slack/src/main/docs/slack-component.adoc
@@ -1,4 +1,4 @@
-# Slack Component
+## Slack Component
*Available as of Camel 2.16*
@@ -21,9 +21,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Slack-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
To send a message to a channel.
@@ -39,9 +37,7 @@ To send a direct message to a slackuser.
slack:@username[?options]
-------------------------
-[[Slack-Options]]
-Options
-^^^^^^^
+### Options
@@ -80,9 +76,7 @@ The Slack component supports 6 endpoint options which are listed below:
// endpoint options: END
-[[Slack-SlackComponent.1]]
-SlackComponent
-^^^^^^^^^^^^^^
+### SlackComponent
The SlackComponent with XML must be configured as a Spring or Blueprint
bean that contains the incoming webhook url for the integration as a
@@ -97,9 +91,7 @@ parameter.
For Java you can configure this using Java code.
-[[Slack-Example]]
-Example
-^^^^^^^
+### Example
A CamelContext with Blueprint could be as:
@@ -122,12 +114,9 @@ A CamelContext with Blueprint could be as:
</blueprint>
---------------------------------------------------------------------------------------------------------------------------
-[[Slack-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-smpp/src/main/docs/smpp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-smpp/src/main/docs/smpp-component.adoc b/components/camel-smpp/src/main/docs/smpp-component.adoc
index 8db80ec..c83cf21 100644
--- a/components/camel-smpp/src/main/docs/smpp-component.adoc
+++ b/components/camel-smpp/src/main/docs/smpp-component.adoc
@@ -1,4 +1,4 @@
-# SMPP Component
+## SMPP Component
*CamelSmppFinalStatusAvailable as of Camel 2.2*
@@ -27,9 +27,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[SMPP-SMSlimitations]]
-SMS limitations
-^^^^^^^^^^^^^^^
+### SMS limitations
SMS is neither reliable or secure.� Users who require reliable and
secure delivery may want to consider using the XMPP or SIP components
@@ -56,9 +54,7 @@ schemes and other purposes where security is important.
While the Camel component makes it as easy as possible to send messages
to the SMS network, it can not offer an easy solution to these problems.
-[[SMPP-Datacoding,alphabetandinternationalcharactersets]]
-Data coding, alphabet and international character sets
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Data coding, alphabet and international character sets
Data coding and alphabet can be specified on a per-message basis.�
Default values can be specified for the endpoint.� It is important to
@@ -129,9 +125,7 @@ control panel option]. It is suggested that users check with their SMSC
operator to confirm exactly which character set is being used as the
default.
-[[SMPP-Messagesplittingandthrottling]]
-Message splitting and throttling
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Message splitting and throttling
After transforming a message body from a String to a byte array, the
Camel component is also responsible for splitting the message into parts
@@ -149,9 +143,7 @@ that has been split may be counted separately by the provider's
throttling mechanism.� The Camel Throttler component can be useful for
throttling messages in the SMPP route before handing them to the SMSC.
-[[SMPP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------------------------
@@ -169,9 +161,7 @@ use SSLSocket to init a connection to the server.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[SMPP-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
@@ -255,9 +245,7 @@ You can have as many of these options as you like.
smpp://smppclient@localhost:2775?password=password&enquireLinkTimer=3000&transactionTimer=5000&systemType=consumer
------------------------------------------------------------------------------------------------------------------
-[[SMPP-ProducerMessageHeaders]]
-Producer Message Headers
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Producer Message Headers
The following message headers can be used to affect the behavior of the
SMPP producer
@@ -392,9 +380,7 @@ converted in the following way:
`org.jsmpp.bean.OptionalParameter.Null` -> `null`
|=======================================================================
-[[SMPP-ConsumerMessageHeaders]]
-Consumer Message Headers
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Consumer Message Headers
The following message headers are used by the SMPP consumer to set the
request data from the SMSC in the message header
@@ -529,9 +515,7 @@ TIP: *JSMPP library*
See the documentation of the http://jsmpp.org[JSMPP Library] for more
details about the underlying library.
-[[SMPP-Exceptionhandling]]
-Exception handling
-^^^^^^^^^^^^^^^^^^
+### Exception handling
This component supports the general Camel exception handling
capabilities
@@ -564,9 +548,7 @@ from("smpp://smppclient@localhost:2775?password=password&enquireLinkTimer=3000&t
Please refer to the http://smsforum.net/SMPP_v3_4_Issue1_2.zip[SMPP
specification] for the complete list of error codes and their meanings.
-[[SMPP-Samples]]
-Samples
-^^^^^^^
+### Samples
A route which sends an SMS using the Java DSL:
@@ -613,9 +595,7 @@ If you need an SMSC simulator for your test, you can use the simulator
provided by
http://opensmpp.logica.com/CommonPart/Download/download2.html#simulator[Logica].
-[[SMPP-Debuglogging]]
-Debug logging
-^^^^^^^^^^^^^
+### Debug logging
This component has log level *DEBUG*, which can be helpful in debugging
problems. If you use log4j, you can add the following line to your
@@ -626,12 +606,9 @@ configuration:
log4j.logger.org.apache.camel.component.smpp=DEBUG
--------------------------------------------------
-[[SMPP-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-snakeyaml/src/main/docs/yaml-snakeyaml-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-snakeyaml/src/main/docs/yaml-snakeyaml-dataformat.adoc b/components/camel-snakeyaml/src/main/docs/yaml-snakeyaml-dataformat.adoc
index 10f4289..03d6e98 100644
--- a/components/camel-snakeyaml/src/main/docs/yaml-snakeyaml-dataformat.adoc
+++ b/components/camel-snakeyaml/src/main/docs/yaml-snakeyaml-dataformat.adoc
@@ -1,4 +1,4 @@
-# YAML SnakeYAML DataFormat
+## YAML SnakeYAML DataFormat
YAML is a�link:data-format.html[Data Format]�to marshal and unmarshal
Java objects to and from�http://www.yaml.org/[YAML].
@@ -12,9 +12,7 @@ Every library requires adding the special camel component (see
"Dependency..." paragraphs further down). By default Camel uses the
SnakeYAML library.
-[[YAML-Options]]
-YAML Options
-^^^^^^^^^^^^
+### YAML Options
// dataformat options: START
The YAML SnakeYAML dataformat supports 11 options which are listed below.
@@ -42,9 +40,7 @@ The YAML SnakeYAML dataformat supports 11 options which are listed below.
WARNING: SnakeYAML can load any class from YAML definition which may lead to security breach so by default, SnakeYAML DataForma restrict the object it can load to standard Java objects like List or Long. If you want to load custom POJOs you need to add theirs type to SnakeYAML DataFormat type filter list. If your source is trusted, you can set the property allowAnyType to true so SnakeYAML DataForma won't perform any filter on the types.
-[[YAMLDataFormat-UsingYAMLdataformatwiththeSnakeYAMLlibrary]]
-Using YAML data format with the SnakeYAML library
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using YAML data format with the SnakeYAML library
- Turn Object messages into yaml then send to MQSeries
+
@@ -77,9 +73,7 @@ from("activemq:My.Queue")
.to("mqseries:Another.Queue");
------------------------------------------------------------
-[[YAMLDataFormat-UsingYAMLinSpringDSL]]
-Using YAML in Spring DSL
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Using YAML in Spring DSL
When using�link:data-format.html[Data Format]�in Spring DSL you need to
declare the data formats first. This is done in the�*DataFormats*�XML
@@ -131,9 +125,7 @@ And then you can refer to those ids in the route:
-------------------------------------
-[[YAMLDataFormat-DependenciesforSnakeYAML]]
-Dependencies for SnakeYAML
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Dependencies for SnakeYAML
To use YAML in your camel routes you need to add the a dependency
on�*camel-snakeyaml*�which implements this data format.
@@ -153,4 +145,4 @@ substituting the version number for the latest & greatest release
�
-�
+�
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-snmp/src/main/docs/snmp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-snmp/src/main/docs/snmp-component.adoc b/components/camel-snmp/src/main/docs/snmp-component.adoc
index 3cd76e0..9c3dad8 100644
--- a/components/camel-snmp/src/main/docs/snmp-component.adoc
+++ b/components/camel-snmp/src/main/docs/snmp-component.adoc
@@ -1,4 +1,4 @@
-# SNMP Component
+## SNMP Component
*Available as of Camel 2.1*
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[SNMP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------------
@@ -33,9 +31,7 @@ and receiving traps.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[SNMP-Producer]]
-Snmp Producer
-^^^^^^^^^^^^^
+### Snmp Producer
*Available from 2.18 release*
@@ -43,9 +39,7 @@ It can also be used to request information using GET method.
The response body type is org.apache.camel.component.snmp.SnmpMessage
-[[SNMP-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -101,9 +95,7 @@ The SNMP component supports 36 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[SNMP-Theresultofapoll]]
-The result of a poll
-^^^^^^^^^^^^^^^^^^^^
+### The result of a poll
Given the situation, that I poll for the following OIDs:
@@ -154,9 +146,7 @@ requested....1.3.6.1.2.1.1.1.0. +
So it may absolutely happen, that you receive more than you
requested...be prepared.
-[[SNMP-Examples]]
-Examples
-^^^^^^^^
+### Examples
Polling a remote device:
@@ -185,12 +175,9 @@ convertBodyTo(String.class).
to("activemq:snmp.states");
------------------------------------------------------------------------------
-[[SNMP-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-soap/src/main/docs/soapjaxb-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc b/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc
index 70d1d62..3e4aa17 100644
--- a/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc
+++ b/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc
@@ -1,4 +1,4 @@
-# SOAP DataFormat
+## SOAP DataFormat
*Available as of Camel 2.3*
@@ -16,9 +16,7 @@ onwards.
See link:jaxb.html[JAXB] for details how you can control namespace
prefix mappings when marshalling using link:soap.html[SOAP] data format.
-[[SOAP-Options]]
-SOAP Options
-^^^^^^^^^^^^
+### SOAP Options
// dataformat options: START
@@ -43,9 +41,7 @@ The SOAP dataformat supports 7 options which are listed below.
-[[SOAP-ElementNameStrategy]]
-ElementNameStrategy
-^^^^^^^^^^^^^^^^^^^
+### ElementNameStrategy
An element name strategy is used for two purposes. The first is to find
a xml element name for a given object and soap action when marshaling
@@ -72,9 +68,7 @@ similar tool then you probably will want to use the
ServiceInterfaceStrategy. In the case you have no annotated service
interface you should use QNameStrategy or TypeNameStrategy.
-[[SOAP-UsingtheJavaDSL]]
-Using the Java DSL
-^^^^^^^^^^^^^^^^^^
+### Using the Java DSL
The following example uses a named DataFormat of _soap_ which is
configured with the package com.example.customerservice to initialize
@@ -100,9 +94,7 @@ As the SOAP dataformat inherits from the link:jaxb.html[JAXB] dataformat
most settings apply here as well
-[[SOAP-UsingSOAP1.2]]
-Using SOAP 1.2
-++++++++++++++
+#### Using SOAP 1.2
*Available as of Camel 2.11*
@@ -140,9 +132,7 @@ And in the Camel route
</route>
---------------------------------------------------------------------------------------------------------------
-[[SOAP-Multi-partMessages]]
-Multi-part Messages
-^^^^^^^^^^^^^^^^^^^
+### Multi-part Messages
*Available as of Camel 2.8.1*
@@ -166,9 +156,7 @@ ServiceInterfaceStrategy strat = new ServiceInterfaceStrategy(com.example.custo
SoapJaxbDataFormat soapDataFormat = new SoapJaxbDataFormat("com.example.customerservice.multipart", strat);
-------------------------------------------------------------------------------------------------------------------------------------------
-[[SOAP-Multi-partRequest]]
-Multi-part Request
-++++++++++++++++++
+#### Multi-part Request
The payload parameters for a multi-part request are initiazlied using a
`BeanInvocation` object that reflects the signature of the target
@@ -201,9 +189,7 @@ beanInvocation.setArgs(args);
exchange.getIn().setBody(beanInvocation);
----------------------------------------------------------------------------------------
-[[SOAP-Multi-partResponse]]
-Multi-part Response
-+++++++++++++++++++
+#### Multi-part Response
A multi-part soap response may include an element in the soap body and
will have one or more elements in the soap header. The camel-soap
@@ -220,9 +206,7 @@ camel-jaxb.
You can also have the camel-soap DataFormate ignore header content
all-together by setting the `ignoreUnmarshalledHeaders` value to `true`.
-[[SOAP-HolderObjectmapping]]
-Holder Object mapping
-+++++++++++++++++++++
+#### Holder Object mapping
JAX-WS specifies the use of a type-parameterized `javax.xml.ws.Holder`
object for `In/Out` and `Out` parameters. A `Holder` object may be used
@@ -232,13 +216,9 @@ values in accordance with the JAXB mapping for the class of the
`Holder`'s value. No mapping is provided for `Holder` objects in an
unmarshalled response.
-[[SOAP-Examples]]
-Examples
-^^^^^^^^
+### Examples
-[[SOAP-Webserviceclient]]
-Webservice client
-+++++++++++++++++
+#### Webservice client
The following route supports marshalling the request and unmarshalling a
response or fault.
@@ -273,9 +253,7 @@ CustomerService proxy = ProxyHelper.createProxy(startEndpoint, classLoader, Cust
GetCustomersByNameResponse response = proxy.getCustomersByName(new GetCustomersByName());
---------------------------------------------------------------------------------------------------
-[[SOAP-WebserviceServer]]
-Webservice Server
-+++++++++++++++++
+#### Webservice Server
Using the following route sets up a webservice server that listens on
jms queue customerServiceQueue and processes requests using the class
@@ -297,9 +275,7 @@ from("jms://queue:customerServiceQueue")
.marshal(soapDF);
---------------------------------------------------------------------------------------------------------------------------------------
-[[SOAP-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use the SOAP dataformat in your camel routes you need to add the
following dependency to your pom.
@@ -311,4 +287,4 @@ following dependency to your pom.
<artifactId>camel-soap</artifactId>
<version>2.3.0</version>
</dependency>
--------------------------------------
+-------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-solr/src/main/docs/solr-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-solr/src/main/docs/solr-component.adoc b/components/camel-solr/src/main/docs/solr-component.adoc
index ebcf0ce..4c5e957 100644
--- a/components/camel-solr/src/main/docs/solr-component.adoc
+++ b/components/camel-solr/src/main/docs/solr-component.adoc
@@ -1,4 +1,4 @@
-# Solr Component
+## Solr Component
*Available as of Camel 2.9*
@@ -19,9 +19,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Solr-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
*NOTE:* solrs and solrCloud are new added since *Camel 2.14*.
@@ -32,9 +30,7 @@ solrs://host[:port]/solr?[options]
solrCloud://host[:port]/solr?[options]
--------------------------------------
-[[Solr-Options]]
-Solr Options
-^^^^^^^^^^^^
+### Solr Options
// component options: START
@@ -69,9 +65,7 @@ The Solr component supports 14 endpoint options which are listed below:
// endpoint options: END
-[[Solr-MessageOperations]]
-Message Operations
-^^^^^^^^^^^^^^^^^^
+### Message Operations
The following Solr operations are currently supported. Simply set an
exchange header with a key of "SolrOperation" and a value set to one of
@@ -116,9 +110,7 @@ bean]
optimize command
|=======================================================================
-[[Solr-Example]]
-Example
-^^^^^^^
+### Example
Below is a simple INSERT, DELETE and COMMIT example
@@ -177,9 +169,7 @@ delete routes and then call the commit route.
template.sendBody("direct:commit", null);
-----------------------------------------------
-[[Solr-QueryingSolr]]
-Querying Solr
-^^^^^^^^^^^^^
+### Querying Solr
Currently, this component doesn't support querying data natively (may be
added later). For now, you can query Solr using link:http.html[HTTP] as
@@ -203,12 +193,9 @@ Tutorial]
http://wiki.apache.org/solr/SolrQuerySyntax[Solr Query Syntax]
-[[Solr-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-spark-rest/src/main/docs/spark-rest-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spark-rest/src/main/docs/spark-rest-component.adoc b/components/camel-spark-rest/src/main/docs/spark-rest-component.adoc
index c09f81c..db249c6 100644
--- a/components/camel-spark-rest/src/main/docs/spark-rest-component.adoc
+++ b/components/camel-spark-rest/src/main/docs/spark-rest-component.adoc
@@ -1,4 +1,4 @@
-# Spark Rest Component
+## Spark Rest Component
*Available as of Camel 2.14*
@@ -20,18 +20,14 @@ for this component:
</dependency>
-------------------------------------------------
-[[Spark-rest-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------------
spark-rest://verb:path?[options]
----------------------------------
-[[Spark-rest-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
@@ -87,9 +83,7 @@ The Spark Rest component supports 13 endpoint options which are listed below:
// endpoint options: END
-[[Spark-rest-PathusingSparksyntax]]
-Path using Spark syntax
-^^^^^^^^^^^^^^^^^^^^^^^
+### Path using Spark syntax
The path option is defined using a Spark REST syntax where you define
the REST context path using support for parameters and splat. See more
@@ -113,9 +107,7 @@ header with the key "me".
.transform().simple("Bye ${header.me}");
--------------------------------------------
-[[Spark-rest-MappingtoCamelMessage]]
-Mapping to Camel Message
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Mapping to Camel Message
The Spark Request object is mapped to a Camel Message as
a�`org.apache.camel.component.sparkrest.SparkMessage` which has access
@@ -135,9 +127,7 @@ Simple language to construct a response message.
.transform().simple("Bye big ${header.splat[1]} from ${header.splat[0]}");
------------------------------------------------------------------------------
-[[Spark-rest-RestDSL]]
-Rest DSL
-^^^^^^^^
+### Rest DSL
Apache Camel provides a new Rest DSL that allow to define the REST
services in a nice REST style. For example we can define a REST hello
@@ -171,23 +161,18 @@ service as shown below:
See more details at the�link:rest-dsl.html[Rest DSL].
-[[Spark-rest-Moreexamples]]
-More examples
-^^^^^^^^^^^^^
+### More examples
There is a *camel-example-spark-rest-tomcat* example in the Apache Camel
distribution, that demonstrates how to use camel-spark-rest in a web
application that can be deployed on Apache Tomcat, or similar web
containers.
-[[Spark-rest-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:rest.html[Rest]
-
+* link:rest.html[Rest]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-spark/src/main/docs/spark-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spark/src/main/docs/spark-component.adoc b/components/camel-spark/src/main/docs/spark-component.adoc
index fc71216..e5cc252 100644
--- a/components/camel-spark/src/main/docs/spark-component.adoc
+++ b/components/camel-spark/src/main/docs/spark-component.adoc
@@ -1,4 +1,4 @@
-# Apache Spark Component
+## Apache Spark Component
INFO: Apache Spark component is available starting from Camel *2.17*.
@@ -10,9 +10,7 @@ message from various transports, dynamically choose a task to execute,
use incoming message as input data for that task and finally deliver the
results of the execution back to the Camel pipeline.
-[[ApacheSpark-Supportedarchitecturalstyles]]
-Supported architectural styles
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Supported architectural styles
Spark component can be used as a driver application deployed into an
application server (or executed as a fat jar).
@@ -28,18 +26,14 @@ While Spark component is primary designed to work as a _long running
job_�serving as an bridge between Spark cluster and the other endpoints,
you can also use it as a _fire-once_ short job. ��
-[[ApacheSpark-RunningSparkinOSGiservers]]
-Running Spark in OSGi servers
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Running Spark in OSGi servers
Currently the Spark component doesn't support execution in the OSGi
container. Spark has been designed to be executed as a fat jar, usually
submitted as a job to a cluster. For those reasons running Spark in an
OSGi server is at least challenging and is not support by Camel as well.
-[[ApacheSpark-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
Currently the Spark component supports only producers - it it intended
to invoke a Spark job and return results. You can call RDD, data frame
@@ -52,9 +46,7 @@ or Hive SQL job.
spark:{rdd|dataframe|hive}
--------------------------
-[[ApacheSpark-options]]
-Spark options
-+++++++++++++
+#### Spark options
@@ -95,9 +87,7 @@ The Apache Spark component supports 7 endpoint options which are listed below:
// endpoint options: END
�
-[[ApacheSpark-RDDjobs]]
-RDD jobs�
-^^^^^^^^^
+### RDD jobs�
To invoke an RDD job, use the following URI:
@@ -166,9 +156,7 @@ JavaRDDLike myRdd(JavaSparkContext sparkContext) {
}
--------------------------------------------------
-[[ApacheSpark-VoidRDDcallbacks]]
-Void RDD callbacks
-++++++++++++++++++
+#### Void RDD callbacks
If your RDD callback doesn't return any value back to a Camel pipeline,
you can either return `null` value or use�`VoidRddCallback` base class:
@@ -188,9 +176,7 @@ RddCallback<Void> rddCallback() {
}
------------------------------------------------------------------
-[[ApacheSpark-ConvertingRDDcallbacks]]
-Converting RDD callbacks
-++++++++++++++++++++++++
+#### Converting RDD callbacks
If you know what type of the input data will be sent to the RDD
callback, you can use�`ConvertingRddCallback` and let Camel to
@@ -213,9 +199,7 @@ RddCallback<Long> rddCallback(CamelContext context) {
}
---------------------------------------------------------------------------
-[[ApacheSpark-AnnotatedRDDcallbacks]]
-Annotated RDD callbacks
-+++++++++++++++++++++++
+#### Annotated RDD callbacks
Probably the easiest way to work with the RDD callbacks is to provide
class with method marked with�`@RddCallback` annotation:
@@ -282,9 +266,7 @@ long result = producerTemplate.requestBody("spark:rdd?rdd=#rdd&rddCallback=#rddC
�
-[[ApacheSpark-DataFramejobs]]
-DataFrame jobs
-^^^^^^^^^^^^^^
+### DataFrame jobs
Instead of working with RDDs Spark component can work with DataFrames as
well.�
@@ -359,9 +341,7 @@ DataFrame cars(HiveContext hiveContext) {
}
------------------------------------------------------------------------
-[[ApacheSpark-Hivejobs]]
-Hive jobs
-^^^^^^^^^
+### Hive jobs
�Instead of working with RDDs or DataFrame Spark component can also
receive Hive SQL queries as payloads.�To send Hive query to Spark
@@ -401,12 +381,9 @@ DataFrame cars(HiveContext hiveContext) {
}
------------------------------------------------------------------------
-[[ApacheSpark-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-splunk/src/main/docs/splunk-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-splunk/src/main/docs/splunk-component.adoc b/components/camel-splunk/src/main/docs/splunk-component.adoc
index c45960c..c93716a 100644
--- a/components/camel-splunk/src/main/docs/splunk-component.adoc
+++ b/components/camel-splunk/src/main/docs/splunk-component.adoc
@@ -1,4 +1,4 @@
-# Splunk Component
+## Splunk Component
*Available as of Camel 2.13*
@@ -19,18 +19,14 @@ for this component:
</dependency>
---------------------------------------------
-[[Splunk-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------
splunk://[endpoint]?[options]
-------------------------------
-[[Splunk-ProducerEndpoints:]]
-Producer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Producer Endpoints:
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -62,9 +58,7 @@ SplunkEvent.��See comment under message body.
In this example a converter is required to convert to a SplunkEvent
class.
-[[Splunk-ConsumerEndpoints:]]
-Consumer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints:
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -87,9 +81,7 @@ name of the query in the savedSearch option.
camel-splunk creates a route exchange per search result with a
SplunkEvent in the body.
-[[Splunk-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
@@ -165,9 +157,7 @@ The Splunk component supports 43 endpoint options which are listed below:
// endpoint options: END
-[[Splunk-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
Splunk operates on data in key/value pairs. The SplunkEvent class is a
placeholder for such data, and should be in the message body for the producer.
@@ -178,9 +168,7 @@ As of Camel 2.16.0 you can send raw data to Splunk by setting the raw
option on the producer endpoint. This is useful for eg. json/xml and
other payloads where Splunk has build in support.�
-[[Splunk-UseCases]]
-Use Cases
-^^^^^^^^^
+### Use Cases
Search Twitter for tweets with music and publish events to Splunk
@@ -229,21 +217,16 @@ Search Splunk for tweets
.log("${body}");
--------------------------------------------------------------------------------------------------------------------------------
-[[Splunk-Othercomments]]
-Other comments
-^^^^^^^^^^^^^^
+### Other comments
Splunk comes with a variety of options for leveraging machine generated
data with prebuilt apps for analyzing and displaying this. +
For example the jmx app. could be used to publish jmx attributes, eg.
route and jvm metrics to Splunk, and displaying this on a dashboard.
-[[Splunk-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-spring-batch/src/main/docs/spring-batch-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring-batch/src/main/docs/spring-batch-component.adoc b/components/camel-spring-batch/src/main/docs/spring-batch-component.adoc
index a7cfbcc..843a2cd 100644
--- a/components/camel-spring-batch/src/main/docs/spring-batch-component.adoc
+++ b/components/camel-spring-batch/src/main/docs/spring-batch-component.adoc
@@ -1,4 +1,4 @@
-# Spring Batch Component
+## Spring Batch Component
The *spring-batch:* component and support classes provide integration
bridge between Camel and http://www.springsource.org/spring-batch[Spring
@@ -17,9 +17,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[SpringBatch-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------
@@ -34,9 +32,7 @@ WARNING:This component can only be used to define producer endpoints, which
means that you cannot use the Spring Batch component in a `from()`
statement.
-[[SpringBatch-Options]]
-Options
-^^^^^^^
+### Options
@@ -83,9 +79,7 @@ The Spring Batch component supports 5 endpoint options which are listed below:
-[[SpringBatch-Usage]]
-Usage
-^^^^^
+### Usage
When Spring Batch component receives the message, it triggers the job
execution. The job will be executed using the
@@ -107,9 +101,7 @@ parameters. `String`, `Long`, `Double` and `java.util.Date` values are
copied to the `org.springframework.batch.core.JobParametersBuilder` -
other data types are converted to Strings.
-[[SpringBatch-Examples]]
-Examples
-^^^^^^^^
+### Examples
Triggering the Spring Batch job execution:
@@ -140,16 +132,12 @@ JobExecution jobExecution = mockEndpoint.getExchanges().get(0).getIn().getBody(J
BatchStatus currentJobStatus = jobExecution.getStatus();
---------------------------------------------------------------------------------------------------
-[[SpringBatch-Supportclasses]]
-Support classes
-^^^^^^^^^^^^^^^
+### Support classes
Apart from the Component, Camel Spring Batch provides also support
classes, which can be used to hook into Spring Batch infrastructure.
-[[SpringBatch-CamelItemReader]]
-CamelItemReader
-+++++++++++++++
+#### CamelItemReader
`CamelItemReader` can be used to read batch data directly from the Camel
infrastructure.
@@ -173,9 +161,7 @@ JMS queue.
</batch:job>
-----------------------------------------------------------------------------------------------
-[[SpringBatch-CamelItemWriter]]
-CamelItemWriter
-+++++++++++++++
+#### CamelItemWriter
`CamelItemWriter` has similar purpose as `CamelItemReader`, but it is
dedicated to write chunk of the processed data.
@@ -199,9 +185,7 @@ JMS queue.
</batch:job>
-----------------------------------------------------------------------------------------------
-[[SpringBatch-CamelItemProcessor]]
-CamelItemProcessor
-++++++++++++++++++
+#### CamelItemProcessor
`CamelItemProcessor` is the implementation of Spring Batch
`org.springframework.batch.item.ItemProcessor` interface. The latter
@@ -241,9 +225,7 @@ the http://camel.apache.org/simple.html[Simple expression language].
</batch:job>
-------------------------------------------------------------------------------------------------------------
-[[SpringBatch-CamelJobExecutionListener]]
-CamelJobExecutionListener
-+++++++++++++++++++++++++
+#### CamelJobExecutionListener
`CamelJobExecutionListener` is the implementation of the
`org.springframework.batch.core.JobExecutionListener` interface sending
@@ -274,4 +256,4 @@ JMS queue.
<batch:listener ref="camelJobExecutionListener"/>
</batch:listeners>
</batch:job>
------------------------------------------------------------------------------------------------------------------------
+-----------------------------------------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-spring-integration/src/main/docs/spring-integration-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring-integration/src/main/docs/spring-integration-component.adoc b/components/camel-spring-integration/src/main/docs/spring-integration-component.adoc
index 3d3dc08..954991e 100644
--- a/components/camel-spring-integration/src/main/docs/spring-integration-component.adoc
+++ b/components/camel-spring-integration/src/main/docs/spring-integration-component.adoc
@@ -1,4 +1,4 @@
-# Spring Integration Component
+## Spring Integration Component
The *spring-integration:* component provides a bridge for Camel
components to talk to
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[SpringIntegration-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------------------------------
@@ -35,9 +33,7 @@ used by the Spring Integration Spring context. It will equal to the
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[SpringIntegration-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -66,9 +62,7 @@ The Spring Integration component supports 8 endpoint options which are listed be
// endpoint options: END
-[[SpringIntegration-Usage]]
-Usage
-^^^^^
+### Usage
The Spring integration component is a bridge that connects Camel
endpoints with Spring integration endpoints through the Spring
@@ -76,21 +70,15 @@ integration's input channels and output channels. Using this component,
we can send Camel messages to Spring Integration endpoints or receive
messages from Spring integration endpoints in a Camel routing context.
-[[SpringIntegration-Examples]]
-Examples
-^^^^^^^^
+### Examples
-[[SpringIntegration-UsingtheSpringintegrationendpoint]]
-Using the Spring integration endpoint
-+++++++++++++++++++++++++++++++++++++
+#### Using the Spring integration endpoint
You can set up a Spring integration endpoint using a URI, as follows:
Or directly using a Spring integration channel name:
-[[SpringIntegration-TheSourceandTargetadapter]]
-The Source and Target adapter
-+++++++++++++++++++++++++++++
+#### The Source and Target adapter
Spring integration also provides the Spring integration's source and
target adapters, which can route messages from a Spring integration
@@ -101,12 +89,9 @@ This example uses the following namespaces:
You can bind your source or target to a Camel endpoint as follows:
-[[SpringIntegration-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-spring-ldap/src/main/docs/spring-ldap-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring-ldap/src/main/docs/spring-ldap-component.adoc b/components/camel-spring-ldap/src/main/docs/spring-ldap-component.adoc
index df5f34e..48ee50b 100644
--- a/components/camel-spring-ldap/src/main/docs/spring-ldap-component.adoc
+++ b/components/camel-spring-ldap/src/main/docs/spring-ldap-component.adoc
@@ -1,4 +1,4 @@
-# Spring LDAP Component
+## Spring LDAP Component
*Available since Camel 2.11*
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[SpringLDAP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------------------
@@ -32,9 +30,7 @@ http://static.springsource.org/spring-ldap/site/apidocs/org/springframework/ldap
LDAP Template bean]. In this bean, you configure the URL and the
credentials for your LDAP access.
-[[SpringLDAP-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -59,9 +55,7 @@ The Spring LDAP component supports 4 endpoint options which are listed below:
// endpoint options: END
-[[SpringLDAP-Usage]]
-Usage
-^^^^^
+### Usage
The component supports producer endpoint only. An attempt to create a
consumer endpoint will result in an `UnsupportedOperationException`. +
@@ -75,48 +69,36 @@ operations. For the `search` and `function_driven` operations, the body is set t
the search, see
http://static.springsource.org/spring-ldap/site/apidocs/org/springframework/ldap/core/LdapTemplate.html#search%28java.lang.String,%20java.lang.String,%20int,%20org.springframework.ldap.core.AttributesMapper%29[http://static.springsource.org/spring-ldap/site/apidocs/org/springframework/ldap/core/LdapTemplate.html#search%28java.lang.String,%20java.lang.String,%20int,%20org.springframework.ldap.core.AttributesMapper%29].
-[[SpringLDAP-Search]]
-Search
-++++++
+#### Search
The message body must have an entry with the key *`filter`*. The value
must be a `String` representing a valid LDAP filter, see
http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol#Search_and_Compare[http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol#Search_and_Compare].
-[[SpringLDAP-Bind]]
-Bind
-++++
+#### Bind
The message body must have an entry with the key *`attributes`*. The
value must be an instance of
http://docs.oracle.com/javase/6/docs/api/javax/naming/directory/Attributes.html[javax.naming.directory.Attributes]
This entry specifies the LDAP node to be created.
-[[SpringLDAP-Unbind]]
-Unbind
-++++++
+#### Unbind
No further entries necessary, the node with the specified *`dn`* is
deleted.
-[[SpringLDAP-Authenticate]]
-Authenticate
-+++++++++++
+#### Authenticate
The message body must have entries with the keys *`filter`* and *`password`*. The
values must be an instance of `String` representing a valid LDAP filter and a user password, respectively.
-[[SpringLDAP-ModifyAttributes]]
-Modify Attributes
-++++++++++++++++
+#### Modify Attributes
The message body must have an entry with the key *`modificationItems`*. The
value must be an instance of any array of type
http://docs.oracle.com/javase/6/docs/api/javax/naming/directory/ModificationItem.html[javax.naming.directory.ModificationItem]
-[[SpringLDAP-FunctionDriven]]
-Function-Driven
-++++++++++++++++
+#### Function-Driven
The message body must have entries with the keys *`function`* and *`request`*. The *`function`* value must be of type `java.util.function.BiFunction<L, Q, S>`. The `L` type parameter must be of type `org.springframework.ldap.core.LdapOperations`. The *`request`* value must be the same type as the `Q` type parameter in the *`function`* and it must encapsulate the parameters expected by the LdapTemplate method being invoked within the *`function`*. The `S` type parameter represents the response type as returned by the LdapTemplate method being invoked.
This operation allows dynamic invocation of LdapTemplate methods that are not covered by the operations mentioned above.
@@ -132,5 +114,4 @@ in `org.apache.camel.springldap.SpringLdapProducer`:
* public static final String PASSWORD = "password";
* public static final String MODIFICATION_ITEMS = "modificationItems";
* public static final String FUNCTION = "function";
-* public static final String REQUEST = "request";
-
+* public static final String REQUEST = "request";
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-spring-redis/src/main/docs/spring-redis-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring-redis/src/main/docs/spring-redis-component.adoc b/components/camel-spring-redis/src/main/docs/spring-redis-component.adoc
index cdc2286..7a96cca 100644
--- a/components/camel-spring-redis/src/main/docs/spring-redis-component.adoc
+++ b/components/camel-spring-redis/src/main/docs/spring-redis-component.adoc
@@ -1,4 +1,4 @@
-# Spring Redis Component
+## Spring Redis Component
*Available as of Camel 2.11*
@@ -15,9 +15,7 @@ INFO:*Prerequisites*
In order to use this component, you must have a Redis server running.
-[[SpringRedis-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
----------------------------------
@@ -27,9 +25,7 @@ spring-redis://host:port[?options]
You can append query options to the URI in the following format,
`?options=value&option2=value&...`
-[[SpringRedis-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -62,16 +58,12 @@ The Spring Redis component supports 12 endpoint options which are listed below:
// endpoint options: END
-[[SpringRedis-Usage]]
-Usage
-^^^^^
+### Usage
See also the unit tests available
at�https://github.com/apache/camel/tree/master/components/camel-spring-redis/src/test/java/org/apache/camel/component/redis[https://github.com/apache/camel/tree/master/components/camel-spring-redis/src/test/java/org/apache/camel/component/redis].
-[[SpringRedis-MessageheadersevaluatedbytheRedisproducer]]
-Message headers evaluated by the Redis producer
-+++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Redis producer
The producer issues commands to the server and each command has
different set of parameters with specific types. The result from the
@@ -343,9 +335,7 @@ milliseconds |CamelRedis.Key (String), CamelRedis.Timestamp (Long) |Boolean
|`PUBLISH` |Post a message to a channel |CamelRedis.Channel (String), CamelRedis.Message (Object) |void
|=======================================================================
-[[SpringRedis-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -363,12 +353,9 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.11 or higher).
-[[SpringRedis-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-spring-ws/src/main/docs/spring-ws-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc b/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc
index 5bdbab2..45331bb 100644
--- a/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc
+++ b/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc
@@ -1,4 +1,4 @@
-# Spring WebService Component
+## Spring WebService Component
*Available as of Camel 2.6*
@@ -33,9 +33,7 @@ module is also included in Spring-WS 1.5.9 (see
http://stackoverflow.com/questions/3313314/can-spring-ws-1-5-be-used-with-spring-3[this
post])
-[[SpringWebServices-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
The URI scheme for this component is as follows
@@ -79,9 +77,7 @@ calling upon.
You can append query *options* to the URI in the following format,
`?option=value&option=value&...`
-[[SpringWebServices-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -127,9 +123,7 @@ The Spring WebService component supports 25 endpoint options which are listed be
// endpoint options: END
-[[SpringWebServices-Messageheaders]]
-Message headers
-+++++++++++++++
+#### Message headers
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -160,9 +154,7 @@ outputAction option if present
faultAction option if present
|=======================================================================
-[[SpringWebServices-Accessingwebservices]]
-Accessing web services
-~~~~~~~~~~~~~~~~~~~~~~
+### Accessing web services
To call a web service at `http://foo.com/bar` simply define a route:
@@ -181,9 +173,7 @@ template.requestBody("direct:example", "<foobar xmlns=\"http://foo.com\"><msg>te
Remember if it's a SOAP service you're calling you don't have to include
SOAP tags. Spring-WS will perform the XML-to-SOAP marshaling.
-[[SpringWebServices-SendingSOAPandWS-Addressingactionheaders]]
-Sending SOAP and WS-Addressing action headers
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending SOAP and WS-Addressing action headers
When a remote web service requires a SOAP action or use of the
WS-Addressing standard you define your route as:
@@ -203,9 +193,7 @@ template.requestBodyAndHeader("direct:example",
SpringWebserviceConstants.SPRING_WS_SOAP_ACTION, "http://baz.com");
--------------------------------------------------------------------
-[[SpringWebServices-UsingSOAPheaders]]
-Using SOAP headers
-^^^^^^^^^^^^^^^^^^
+### Using SOAP headers
*Available as of Camel 2.11.1*
@@ -237,9 +225,7 @@ For an example see this
https://svn.apache.org/repos/asf/camel/trunk/components/camel-spring-ws/src/test/java/org/apache/camel/component/spring/ws/SoapHeaderTest.java[unit
test].
-[[SpringWebServices-Theheaderandattachmentpropagation]]
-The header and attachment propagation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### The header and attachment propagation
Spring WS Camel supports propagation of the headers and attachments into
Spring-WS WebServiceMessage response since version *2.10.3*.�The
@@ -258,9 +244,7 @@ Note: If the exchange header in the pipeline contains text, it generates
Qname(key)=value attribute in the soap header. Recommended is to create
a QName class directly and put into any key into header.
-[[SpringWebServices-HowtouseMTOMattachments]]
-How to use MTOM attachments
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to use MTOM attachments
The BasicMessageFilter provides all required information for Apache
Axiom in order to produce MTOM message. If you want to use Apache Camel
@@ -318,9 +302,7 @@ from("direct:send")
- Now, your producer will generate MTOM message with otpmized
attachments.
-[[SpringWebServices-Thecustomheaderandattachmentfiltering]]
-The custom header and attachment filtering
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### The custom header and attachment filtering
If you need to provide your custom processing of either headers or
attachments, extend existing BasicMessageFilter and override the
@@ -363,9 +345,7 @@ protected void doProcessSoapAttachements(Message inOrOut, SoapMessage response)
{ your code /*no need to call super*/ }
-------------------------------------------------------------------------------
-[[SpringWebServices-UsingacustomMessageSenderandMessageFactory]]
-Using a custom MessageSender and MessageFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using a custom MessageSender and MessageFactory
A custom message sender or factory in the registry can be referenced
like this:
@@ -398,9 +378,7 @@ Spring configuration:
</bean>
---------------------------------------------------------------------------------------------------------------------
-[[SpringWebServices-Exposingwebservices]]
-Exposing web services
-~~~~~~~~~~~~~~~~~~~~~
+### Exposing web services
In order to expose a web service using this component you first need to
set-up a
@@ -459,9 +437,7 @@ comes in). Also don't forget to check out the
link:spring-ws-example.html[Spring Web Services Example] included in the
Camel distribution.
-[[SpringWebServices-Endpointmappinginroutes]]
-Endpoint mapping in routes
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Endpoint mapping in routes
With the XML configuration in-place you can now use Camel's DSL to
define what web service requests are handled by your endpoint:
@@ -503,9 +479,7 @@ from("spring-ws:xpathresult:abc?expression=//foobar&endpointMapping=#endpointMap
.convertBodyTo(String.class).to(mock:example)
--------------------------------------------------------------------------------------
-[[SpringWebServices-Alternativeconfiguration,usingexistingendpointmappings]]
-Alternative configuration, using existing endpoint mappings
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Alternative configuration, using existing endpoint mappings
For every endpoint with mapping-type `beanname` one bean of type
`CamelEndpointDispatcher` with a corresponding name is required in the
@@ -548,9 +522,7 @@ An example of a route using `beanname`:
<bean id="FutureEndpointDispatcher" class="org.apache.camel.component.spring.ws.bean.CamelEndpointDispatcher" />
------------------------------------------------------------------------------------------------------------------------
-[[SpringWebServices-POJO-unmarshalling]]
-POJO (un)marshalling
-~~~~~~~~~~~~~~~~~~~~
+### POJO (un)marshalling
Camel's link:data-format.html[pluggable data formats] offer support for
pojo/xml marshalling using libraries such as JAXB, XStream, JibX, Castor
@@ -577,12 +549,9 @@ from("spring-ws:rootqname:{http://example.com/}GetFoo?endpointMapping=#endpointM
.to("mock:example").marshal(jaxb);
--------------------------------------------------------------------------------------------------------
-[[SpringWebServices-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-spring/src/main/docs/spel-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring/src/main/docs/spel-language.adoc b/components/camel-spring/src/main/docs/spel-language.adoc
index 8efff63..3020b22 100644
--- a/components/camel-spring/src/main/docs/spel-language.adoc
+++ b/components/camel-spring/src/main/docs/spel-language.adoc
@@ -1,4 +1,4 @@
-# SpEL Language
+## SpEL Language
*Available as of Camel 2.7*
@@ -8,9 +8,7 @@ to be used as an link:expression.html[Expression] or
link:predicate.html[Predicate] in the link:dsl.html[DSL] or
link:xml-configuration.html[Xml Configuration].
-[[SpEL-Variables]]
-Variables
-^^^^^^^^^
+### Variables
The following variables are available in expressions and predicates
written in SpEL:
@@ -42,9 +40,7 @@ written in SpEL:
|property(name, type) |Type |the property by the given name as the given type
|=======================================================================
-[[SpEL-Options]]
-Options
-^^^^^^^
+### Options
// language options: START
The SpEL language supports 1 options which are listed below.
@@ -60,13 +56,9 @@ The SpEL language supports 1 options which are listed below.
{% endraw %}
// language options: END
-[[SpEL-Samples]]
-Samples
-^^^^^^^
+### Samples
-[[SpEL-Expressiontemplating]]
-Expression templating
-+++++++++++++++++++++
+#### Expression templating
SpEL expressions need to be surrounded by `#{` `}` delimiters since
expression templating is enabled. This allows you to combine SpEL
@@ -106,9 +98,7 @@ template.sendBodyAndHeader("direct:example", "World", "dayOrNight", "day");
The output on `mock:result` will be _"Hello World! What a beautiful
day"_
-[[SpEL-Beanintegration]]
-Bean integration
-++++++++++++++++
+#### Bean integration
You can reference beans defined in the link:registry.html[Registry]
(most likely an `ApplicationContext`) in your SpEL expressions. For
@@ -120,9 +110,7 @@ can invoke the "bar" method on this bean like this:
#{@foo.bar == 'xyz'}
--------------------
-[[SpEL-SpELinenterpriseintegrationpatterns]]
-SpEL in enterprise integration patterns
-+++++++++++++++++++++++++++++++++++++++
+#### SpEL in enterprise integration patterns
You can use SpEL as an expression for link:recipient-list.html[Recipient
List] or as a predicate inside a link:message-filter.html[Message
@@ -146,9 +134,7 @@ And the equivalent in Java DSL:
from("direct:foo").filter().spel("#{request.headers['foo'] == 'bar'}").to("direct:bar");
-------------------------------------------------------------------------------------------
-[[SpEL-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -162,9 +148,7 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").spel("resource:classpath:myspel.txt")
------------------------------------------------------------
-[[SpEL-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
You need Spring 3.0 or higher to use Spring Expression Language. If you
use Maven you could just add the following to your `pom.xml`:
@@ -177,4 +161,4 @@ use Maven you could just add the following to your `pom.xml`:
<version>xxx</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-spring/src/main/docs/spring-event-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring/src/main/docs/spring-event-component.adoc b/components/camel-spring/src/main/docs/spring-event-component.adoc
index 1de4c1d..0a8c65a 100644
--- a/components/camel-spring/src/main/docs/spring-event-component.adoc
+++ b/components/camel-spring/src/main/docs/spring-event-component.adoc
@@ -1,4 +1,4 @@
-# Spring Event Component
+## Spring Event Component
The *spring-event:* component provides access to the Spring
`ApplicationEvent` objects. This allows you to publish
@@ -8,9 +8,7 @@ link:enterprise-integration-patterns.html[Enterprise Integration
Patterns] to process them such as link:message-filter.html[Message
Filter].
-[[SpringEvent-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------------
@@ -20,9 +18,7 @@ spring-event://default[?options]
Note, at the moment there are no options for this component. That can
easily change in future releases, so please check back.
-[[Spring-Event-Options]]
-Spring Event Options
-^^^^^^^^^^^^^^^^^^^^
+### Spring Event Options
@@ -60,12 +56,9 @@ The Spring Event component supports 5 endpoint options which are listed below:
// endpoint options: END
-[[SpringEvent-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-sql/src/main/docs/sql-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-sql/src/main/docs/sql-component.adoc b/components/camel-sql/src/main/docs/sql-component.adoc
index ee3c325..6bef6d2 100644
--- a/components/camel-sql/src/main/docs/sql-component.adoc
+++ b/components/camel-sql/src/main/docs/sql-component.adoc
@@ -1,4 +1,4 @@
-# SQL Component
+## SQL Component
The *sql:* component allows you to work with databases using JDBC
queries. The difference between this component and link:jdbc.html[JDBC]
@@ -29,9 +29,7 @@ further below.
* a JDBC based repository for the link:aggregator2.html[Aggregator] EIP
pattern. See further below.
-[[SQLComponent-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
WARNING:From Camel 2.11 onwards this component can create both consumer (e.g.
`from()`) and producer endpoints (e.g. `to()`).
@@ -102,9 +100,7 @@ also use comments such as the�\u2013 dash line.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[SQLComponent-Options]]
-Options
-^^^^^^^
+### Options
@@ -184,9 +180,7 @@ The SQL component supports 46 endpoint options which are listed below:
// endpoint options: END
-[[SQLComponent-Treatmentofthemessagebody]]
-Treatment of the message body
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Treatment of the message body
The SQL component tries to convert the message body to an object of
`java.util.Iterator` type and then uses this iterator to fill the query
@@ -211,9 +205,7 @@ parameters must be provided in a header with the
key�SqlConstants.SQL_PARAMETERS. This allows the SQL component to work
more dynamic as the SQL query is from the message body.
-[[SQLComponent-Resultofthequery]]
-Result of the query
-^^^^^^^^^^^^^^^^^^^
+### Result of the query
For `select` operations, the result is an instance of
`List<Map<String, Object>>` type, as returned by the
@@ -235,9 +227,7 @@ from("jms:order.inbox")
.to("jms:order.booking");
-------------------------------------------------------------------------------------------
-[[SQLComponent-UsingStreamList]]
-Using StreamList
-^^^^^^^^^^^^^^^^
+### Using StreamList
From*Camel 2.18* onwards the producer supports outputType=StreamList
that uses an iterator to stream the output of the query. This allows to
@@ -258,9 +248,7 @@ from("direct:withSplitModel")
�
-[[SQLComponent-Headervalues]]
-Header values
-^^^^^^^^^^^^^
+### Header values
When performing `update` operations, the SQL Component stores the update
count in the following message headers:
@@ -295,9 +283,7 @@ message headers (*Available as of Camel 2.12.4, 2.13.1*):
|CamelSqlGeneratedKeyRows |Rows that contains the generated keys (a list of maps of keys).
|=======================================================================
-[[SQLComponent-Generatedkeys]]
-Generated keys
-^^^^^^^^^^^^^^
+### Generated keys
*Available as of Camel 2.12.4, 2.13.1 and 2.14 *
@@ -312,9 +298,7 @@ You can see more details in this
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob_plain;f=components/camel-sql/src/test/java/org/apache/camel/component/sql/SqlGeneratedKeysTest.java;hb=3962b23f94bb4bc23011b931add08c3f6833c82e[unit
test].
-[[SQLComponent-Configuration]]
-Configuration
-^^^^^^^^^^^^^
+### Configuration
You can now set a reference to a `DataSource` in the URI directly:
@@ -323,9 +307,7 @@ You can now set a reference to a `DataSource` in the URI directly:
sql:select * from table where id=# order by name?dataSource=myDS
----------------------------------------------------------------
-[[SQLComponent-Sample]]
-Sample
-^^^^^^
+### Sample
In the sample below we execute a query and retrieve the result as a
`List` of rows, where each row is a `Map<String, Object` and the key is
@@ -354,9 +336,7 @@ We could configure the `DataSource` in Spring XML as follows:
<jee:jndi-lookup id="myDS" jndi-name="jdbc/myDataSource"/>
-----------------------------------------------------------
-[[SQLComponent-Usingnamedparameters]]
-Using named parameters
-++++++++++++++++++++++
+#### Using named parameters
*Available as of Camel 2.11*
@@ -385,9 +365,7 @@ parameters will be taken from the body.
.to("sql:select * from projects where license = :#lic and id > :#min order by id")
---------------------------------------------------------------------------------------
-[[SQLComponent-Usingexpressionparameters]]
-Using expression parameters
-+++++++++++++++++++++++++++
+#### Using expression parameters
*Available as of Camel 2.14*
@@ -403,9 +381,7 @@ from("direct:projects")
.to("sql:select * from projects where license = :#${body} and id > :#${property.min} order by id")
----------------------------------------------------------------------------------------------------
-[[SQLComponent-UsingINquerieswithdynamicvalues]]
-Using IN queries with dynamic values
-++++++++++++++++++++++++++++++++++++
+#### Using IN queries with dynamic values
*Available as of Camel 2.17*
@@ -474,9 +450,7 @@ from("direct:query")
�
-[[SQLComponent-UsingtheJDBCbasedidempotentrepository]]
-Using the JDBC based idempotent repository
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using the JDBC based idempotent repository
*Available as of Camel 2.7*: In this section we will use the JDBC based
idempotent repository.
@@ -751,9 +725,7 @@ class="org.apache.camel.processor.aggregate.jdbc.DefaultJdbcOptimisticLockingExc
-------------------------------------------------------------------------------
�
-[[SQLComponent-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -762,4 +734,4 @@ See Also
link:sql-stored-procedure.html[SQL Stored Procedure]
-link:jdbc.html[JDBC]
+link:jdbc.html[JDBC]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-sql/src/main/docs/sql-stored-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-sql/src/main/docs/sql-stored-component.adoc b/components/camel-sql/src/main/docs/sql-stored-component.adoc
index 2a2d174..6145378 100644
--- a/components/camel-sql/src/main/docs/sql-stored-component.adoc
+++ b/components/camel-sql/src/main/docs/sql-stored-component.adoc
@@ -1,4 +1,4 @@
-# SQL StoredProcedure Component
+## SQL StoredProcedure Component
*Available as of Camel 2.17*
@@ -23,9 +23,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[SQLStoredProcedure-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
The SQL component uses the following endpoint URI notation:
@@ -60,9 +58,7 @@ SUBNUMBERS(
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[SQLStoredProcedure-Options]]
-Options
-^^^^^^^
+### Options
@@ -102,9 +98,7 @@ The SQL StoredProcedure component supports 7 endpoint options which are listed b
// endpoint options: END
-[[SQLStoredProcedure-Declaringthestoredproceduretemplate]]
-Declaring the stored procedure template
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Declaring the stored procedure template
The template is declared using a syntax that would be similar to a Java
method signature. The name of the stored procedure, and then the
@@ -127,14 +121,11 @@ In SQL term the stored procedure could be declared as:
CREATE PROCEDURE SUBNUMBERS(VALUE1 INTEGER, VALUE2 INTEGER,OUT RESULT INTEGER)
------------------------------------------------------------------------------
-[[SQLStoredProcedure-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:sql-component.html[SQL Component]
-
+* link:sql-component.html[SQL Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ssh/src/main/docs/ssh-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ssh/src/main/docs/ssh-component.adoc b/components/camel-ssh/src/main/docs/ssh-component.adoc
index 5eaaf98..542616e 100644
--- a/components/camel-ssh/src/main/docs/ssh-component.adoc
+++ b/components/camel-ssh/src/main/docs/ssh-component.adoc
@@ -1,4 +1,4 @@
-# SSH Component
+## SSH Component
*Available as of Camel 2.10*
@@ -18,18 +18,14 @@ for this component:
</dependency>
------------------------------------------------------------
-[[SSH-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------------------------------
ssh:[username[:password]@]host[:port][?options]
-----------------------------------------------
-[[SSH-Options]]
-Options
-^^^^^^^
+### Options
@@ -100,9 +96,7 @@ The SSH component supports 28 endpoint options which are listed below:
// endpoint options: END
-[[SSH-UsageasaProducerendpoint]]
-Usage as a Producer endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Usage as a Producer endpoint
When the SSH Component is used as a Producer (`.to("ssh://...")`), it
will send the message body as the command to execute on the remote SSH
@@ -123,9 +117,7 @@ an XML encoded newline (` `).
</route>
----------------------------------------------
-[[SSH-Authentication]]
-Authentication
-^^^^^^^^^^^^^^
+### Authentication
The SSH Component can authenticate against the remote SSH server using
one of two mechanisms: Public Key certificate or username/password.
@@ -192,19 +184,14 @@ of Camel you are using.
</dependency>
-----------------------------------------
-[[SSH-Example]]
-Example
-^^^^^^^
+### Example
See the `examples/camel-example-ssh` and
`examples/camel-example-ssh-security` in the Camel distribution.
-[[SSH-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-stax/src/main/docs/stax-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-stax/src/main/docs/stax-component.adoc b/components/camel-stax/src/main/docs/stax-component.adoc
index d56cc01..d4c5070 100644
--- a/components/camel-stax/src/main/docs/stax-component.adoc
+++ b/components/camel-stax/src/main/docs/stax-component.adoc
@@ -1,4 +1,4 @@
-# StAX Component
+## StAX Component
*Available as of Camel 2.9*
@@ -21,9 +21,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[StAX-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------
@@ -46,9 +44,7 @@ using the # syntax as shown:
stax:#myHandler
---------------
-[[Stax-Options]]
-Options
-~~~~~~~
+### Options
// component options: START
@@ -71,9 +67,7 @@ The StAX component supports 2 endpoint options which are listed below:
// endpoint options: END
-[[StAX-UsageofacontenthandlerasStAXparser]]
-Usage of a content handler as StAX parser
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Usage of a content handler as StAX parser
The message body after the handling is the handler itself.
@@ -93,9 +87,7 @@ from("file:target/in")
});
--------------------------------------------------------------------------------------------------------
-[[StAX-IterateoveracollectionusingJAXBandStAX]]
-Iterate over a collection using JAXB and StAX
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Iterate over a collection using JAXB and StAX
First we suppose you have JAXB objects.
@@ -199,18 +191,13 @@ from("file:target/in")
.to("mock:records");
-------------------------------------------------
-[[StAX-ThepreviousexamplewithXMLDSL]]
-The previous example with XML DSL
-+++++++++++++++++++++++++++++++++
+#### The previous example with XML DSL
The example above could be implemented as follows in XML DSL
-[[StAX-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-stomp/src/main/docs/stomp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-stomp/src/main/docs/stomp-component.adoc b/components/camel-stomp/src/main/docs/stomp-component.adoc
index 41dc26d..3c9d48c 100644
--- a/components/camel-stomp/src/main/docs/stomp-component.adoc
+++ b/components/camel-stomp/src/main/docs/stomp-component.adoc
@@ -1,4 +1,4 @@
-# Stomp Component
+## Stomp Component
*Available as of Camel 2.12*
@@ -20,9 +20,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Stomp-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------
@@ -31,9 +29,7 @@ stomp:queue:destination[?options]
Where *destination* is the name of the queue.
-[[Stomp-Options]]
-Options
-^^^^^^^
+### Options
@@ -85,9 +81,7 @@ The Stomp component supports 10 endpoint options which are listed below:
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Stomp-Samples]]
-Samples
-^^^^^^^
+### Samples
Sending messages:
@@ -103,9 +97,7 @@ Consuming messages:
from("stomp:queue:test").transform(body().convertToString()).to("mock:result")
------------------------------------------------------------------------------
-[[Stomp-Endpoints]]
-Endpoints
-~~~~~~~~~
+### Endpoints
Camel supports the link:message-endpoint.html[Message Endpoint] pattern
using the
@@ -134,12 +126,9 @@ implements the link:polling-consumer.html[Polling Consumer] pattern for
consuming message exchanges from the endpoint via a
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/PollingConsumer.html[PollingConsumer]
-[[Stomp-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:message-endpoint.html[Message Endpoint] pattern
* link:uris.html[URIs]
-* link:writing-components.html[Writing Components]
-
+* link:writing-components.html[Writing Components]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-stream/src/main/docs/stream-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-stream/src/main/docs/stream-component.adoc b/components/camel-stream/src/main/docs/stream-component.adoc
index 8655e51..cf8f3d5 100644
--- a/components/camel-stream/src/main/docs/stream-component.adoc
+++ b/components/camel-stream/src/main/docs/stream-component.adoc
@@ -1,4 +1,4 @@
-# Stream Component
+## Stream Component
The *stream:* component provides access to the `System.in`, `System.out`
and `System.err` streams as well as allowing streaming of file and URL.
@@ -16,9 +16,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Stream-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------
@@ -43,9 +41,7 @@ producers (that is, it cannot appear in `from()`).
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Stream-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -85,9 +81,7 @@ The Stream component supports 19 endpoint options which are listed below:
// endpoint options: END
-[[Stream-Messagecontent]]
-Message content
-^^^^^^^^^^^^^^^
+### Message content
The *stream:* component supports either `String` or `byte[]` for writing
to streams. Just add either `String` or `byte[]` content to the
@@ -100,9 +94,7 @@ add a `java.io.OutputStream` object to `message.in.header` in the key
`header`. +
See samples for an example.
-[[Stream-Samples]]
-Samples
-^^^^^^^
+### Samples
In the following sample we route messages from the `direct:in` endpoint
to the `System.out` stream:
@@ -138,12 +130,9 @@ file will be re-opened and scanned with each iteration of
scanStreamDelay. Until NIO2 is available we cannot reliably detect when
a file is deleted/recreated.
-[[Stream-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-stringtemplate/src/main/docs/string-template-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-stringtemplate/src/main/docs/string-template-component.adoc b/components/camel-stringtemplate/src/main/docs/string-template-component.adoc
index 1c63368..8fe61b3 100644
--- a/components/camel-stringtemplate/src/main/docs/string-template-component.adoc
+++ b/components/camel-stringtemplate/src/main/docs/string-template-component.adoc
@@ -1,4 +1,4 @@
-# String Template Component
+## String Template Component
The *string-template:* component allows you to process a message using a
http://www.stringtemplate.org/[String Template]. This can be ideal when
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[StringTemplate-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------------------
@@ -33,9 +31,7 @@ invoke; or the complete URL of the remote template.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[StringTemplate-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -61,26 +57,20 @@ The String Template component supports 5 endpoint options which are listed below
// endpoint options: END
-[[StringTemplate-Headers]]
-Headers
-^^^^^^^
+### Headers
Camel will store a reference to the resource in the message header with
key, `org.apache.camel.stringtemplate.resource`. The Resource is an
`org.springframework.core.io.Resource` object.
-[[StringTemplate-Hotreloading]]
-Hot reloading
-^^^^^^^^^^^^^
+### Hot reloading
The string template resource is by default hot-reloadable for both file
and classpath resources (expanded jar). If you set `contentCache=true`,
Camel loads the resource only once and hot-reloading is not possible.
This scenario can be used in production when the resource never changes.
-[[StringTemplate-StringTemplateAttributes]]
-StringTemplate Attributes
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### StringTemplate Attributes
Since Camel 2.14, you can define the custom context map by setting the
message header "*CamelStringTemplateVariableMap*" just like the below
@@ -97,9 +87,7 @@ variableMap.put("exchange", exchange);
exchange.getIn().setHeader("CamelStringTemplateVariableMap", variableMap);
--------------------------------------------------------------------------
-[[StringTemplate-Samples]]
-Samples
-^^^^^^^
+### Samples
For example you could use a string template as follows in order to
formulate a response to a message:
@@ -110,9 +98,7 @@ from("activemq:My.Queue").
to("string-template:com/acme/MyResponse.tm");
-----------------------------------------------
-[[StringTemplate-TheEmailSample]]
-The Email Sample
-^^^^^^^^^^^^^^^^
+### The Email Sample
In this sample we want to use a string template to send an order
confirmation email. The email template is laid out in `StringTemplate`
@@ -131,12 +117,9 @@ Regards Camel Riders Bookstore
And the java code is as follows:
-[[StringTemplate-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-syslog/src/main/docs/syslog-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-syslog/src/main/docs/syslog-dataformat.adoc b/components/camel-syslog/src/main/docs/syslog-dataformat.adoc
index 8c985d7..c09d2ff 100644
--- a/components/camel-syslog/src/main/docs/syslog-dataformat.adoc
+++ b/components/camel-syslog/src/main/docs/syslog-dataformat.adoc
@@ -1,4 +1,4 @@
-# Syslog DataFormat
+## Syslog DataFormat
*Available as of Camel 2.6*
@@ -31,9 +31,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Syslog-RFC3164Syslogprotocol]]
-RFC3164 Syslog protocol
-^^^^^^^^^^^^^^^^^^^^^^^
+### RFC3164 Syslog protocol
Syslog uses the user datagram protocol (UDP)
https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=CAMEL&title=1&linkCreation=true&fromPageId=24185759[1]
@@ -46,9 +44,7 @@ where we just use the `Rfc3164SyslogDataFormat` to marshal and unmarshal
messages. Notice that from�*Camel 2.14* onwards the syslog dataformat is
renamed to `SyslogDataFormat`.
-[[Syslog-Dataformat-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The Syslog dataformat supports 1 options which are listed below.
@@ -64,9 +60,7 @@ The Syslog dataformat supports 1 options which are listed below.
{% endraw %}
// dataformat options: END
-[[Syslog-RFC5424Syslogprotocol]]
-RFC5424 Syslog protocol
-^^^^^^^^^^^^^^^^^^^^^^^
+### RFC5424 Syslog protocol
*Available as of Camel 2.14*
@@ -75,9 +69,7 @@ existing�link:mina.html[camel-mina]�component
or�link:netty.html[camel-netty]�where we just use
the�`SyslogDataFormat`�to marshal and unmarshal messages
-[[Syslog-ExposingaSysloglistener]]
-Exposing a Syslog listener
-++++++++++++++++++++++++++
+#### Exposing a Syslog listener
In our Spring XML file, we configure an endpoint to listen for udp
messages on port 10514, note that in netty we disable the defaultCodec,
@@ -121,9 +113,7 @@ The same route using link:mina.html[camel-mina]
</camelContext>
-------------------------------------------------------------------------
-[[Syslog-Sendingsyslogmessagestoaremotedestination]]
-Sending syslog messages to a remote destination
-+++++++++++++++++++++++++++++++++++++++++++++++
+#### Sending syslog messages to a remote destination
[source,xml]
-------------------------------------------------------------------------
@@ -142,12 +132,9 @@ Sending syslog messages to a remote destination
</camelContext>
-------------------------------------------------------------------------
-[[Syslog-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-tagsoup/src/main/docs/tidyMarkup-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-tagsoup/src/main/docs/tidyMarkup-dataformat.adoc b/components/camel-tagsoup/src/main/docs/tidyMarkup-dataformat.adoc
index d9a0c3e..999e675 100644
--- a/components/camel-tagsoup/src/main/docs/tidyMarkup-dataformat.adoc
+++ b/components/camel-tagsoup/src/main/docs/tidyMarkup-dataformat.adoc
@@ -1,4 +1,4 @@
-# TidyMarkup DataFormat
+## TidyMarkup DataFormat
TidyMarkup is a link:data-format.html[Data Format] that uses the
http://www.ccil.org/~cowan/XML/tagsoup/[TagSoup] to tidy up HTML. It can
@@ -15,9 +15,7 @@ link:tidymarkup.html[TidyMarkup] only supports the *unmarshal* operation
as we really don't want to turn well formed HTML into ugly HTML
image:https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png[(smile)]
-[[TidyMarkup-Options]]
-TidyMarkup Options
-^^^^^^^^^^^^^^^
+### TidyMarkup Options
@@ -40,9 +38,7 @@ The TidyMarkup dataformat supports 3 options which are listed below.
-[[TidyMarkup-JavaDSLExample]]
-Java DSL Example
-^^^^^^^^^^^^^^^^
+### Java DSL Example
An example where the consumer provides some HTML
@@ -51,9 +47,7 @@ An example where the consumer provides some HTML
from("file://site/inbox").unmarshal().tidyMarkup().to("file://site/blogs");
---------------------------------------------------------------------------
-[[TidyMarkup-SpringXMLExample]]
-Spring XML Example
-^^^^^^^^^^^^^^^^^^
+### Spring XML Example
The following example shows how to use link:tidymarkup.html[TidyMarkup]
to unmarshal using Spring
@@ -71,9 +65,7 @@ to unmarshal using Spring
</camelContext>
-----------------------------------------------------------------------
-[[TidyMarkup-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use TidyMarkup in your camel routes you need to add the a dependency
on *camel-tagsoup* which implements this data format.
@@ -89,4 +81,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-tagsoup</artifactId>
<version>x.x.x</version>
</dependency>
-----------------------------------------
+----------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-tarfile/src/main/docs/tarfile-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-tarfile/src/main/docs/tarfile-dataformat.adoc b/components/camel-tarfile/src/main/docs/tarfile-dataformat.adoc
index 0aa9699..92c1997 100644
--- a/components/camel-tarfile/src/main/docs/tarfile-dataformat.adoc
+++ b/components/camel-tarfile/src/main/docs/tarfile-dataformat.adoc
@@ -1,4 +1,4 @@
-# Tar File DataFormat
+## Tar File DataFormat
TIP:*Available since Camel 2.18.0*
@@ -10,9 +10,7 @@ entry can be unmarshalled (decompressed) to the original file contents.
There is also a aggregation strategy that can
aggregate multiple messages into a single Tar File.
-[[TarFile-Options]]
-TarFile Options
-^^^^^^^^^^^^^^^
+### TarFile Options
// dataformat options: START
@@ -31,9 +29,7 @@ The Tar File dataformat supports 2 options which are listed below.
// dataformat options: END
-[[TarFileDataFormat-Marshal]]
-Marshal
-^^^^^^^
+### Marshal
In this example we marshal a regular text/XML payload to a compressed
payload using Tar File compression, and send it to an ActiveMQ queue
@@ -74,9 +70,7 @@ from("direct:start").setHeader(Exchange.FILE_NAME, constant("report.txt")).marsh
This route would result in a Tar File named "report.txt.tar" in the
output directory, containing a single Tar entry named "report.txt".
-[[TarFileDataFormat-Unmarshal]]
-Unmarshal
-^^^^^^^^^
+### Unmarshal
In this example we unmarshal a Tar File payload from an ActiveMQ queue
called MY_QUEUE to its original format, and forward it for processing to
@@ -116,9 +110,7 @@ like this
----------------------------------------------------------------------------------------------------
-[[TarFileDataFormat-Aggregate]]
-Aggregate
-^^^^^^^^^
+### Aggregate
INFO:Please note that this aggregation strategy requires eager completion
check to work properly.
@@ -152,9 +144,7 @@ the�`CamelFileName`�header explicitly in your route:
.to("file:output/directory");
------------------------------------------------------------
-[[TarFileDataFormat-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Tar Files in your camel routes you need to add a dependency on
*camel-tarfile* which implements this data format.
@@ -171,4 +161,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-telegram/src/main/docs/telegram-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-telegram/src/main/docs/telegram-component.adoc b/components/camel-telegram/src/main/docs/telegram-component.adoc
index 625c579..b9bbb42 100644
--- a/components/camel-telegram/src/main/docs/telegram-component.adoc
+++ b/components/camel-telegram/src/main/docs/telegram-component.adoc
@@ -1,4 +1,4 @@
-# Telegram Component
+## Telegram Component
*Available as of Camel 2.18*
@@ -30,9 +30,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Telegram-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------------------------------
@@ -42,9 +40,7 @@ telegram:type/authorizationToken[?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Telegram-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The Telegram component supports 1 options which are listed below.
@@ -100,9 +96,7 @@ The Telegram component supports 24 endpoint options which are listed below:
-[[Telegram-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="20%,80%",options="header",]
|=======================================================================
@@ -122,16 +116,12 @@ for outgoing binary messages.
|=======================================================================
-[[Telegram-Usage]]
-Usage
-^^^^^
+### Usage
The Telegram component supports both consumer and producer endpoints.
It can also be used in *reactive chat-bot mode* (to consume, then produce messages).
-[[Telegram-ProducerExample]]
-Producer Example
-^^^^^^^^^^^^^^^^
+### Producer Example
The following is a basic example of how to send a message to a Telegram chat through the
Telegram Bot API.
@@ -172,9 +162,7 @@ The following message bodies are allowed for a producer endpoint (messages of ty
|===================================================
-[[Telegram-ConsumerExample]]
-Consumer Example
-^^^^^^^^^^^^^^^^
+### Consumer Example
The following is a basic example of how to receive all messages that telegram users are sending to the configured Bot.
In Java DSL
@@ -227,9 +215,7 @@ Supported types for incoming messages are
-[[Telegram-ReactiveChatBot]]
-Reactive Chat-Bot Example
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Reactive Chat-Bot Example
The reactive chat-bot mode is a simple way of using the Camel component to build a simple
chat bot that replies directly to chat messages received from the Telegram users.
@@ -278,9 +264,7 @@ public class ChatBotLogic {
Every non-null string returned by the `chatBotProcess` method is automatically routed to the
chat that originated the request (as the `CamelTelegramChatId` header is used to route the message).
-[[Telegram-GettingTheChatId]]
-Getting the Chat ID
-^^^^^^^^^^^^^^^^^^^
+### Getting the Chat ID
If you want to push messages to a specific Telegram chat when an event occurs, you need to
retrieve the corresponding chat ID. The chat ID is not currently shown in the telegram client,
@@ -306,4 +290,4 @@ from("timer:tick")
to("telegram:bots/123456789:AAE_dLq5C19xwGjw3yiC2NvEUrZcejK21-Q987654321:AAE_dLq5C19xwOmg5yiC2NvSrkT3wj5Q1-L?chatId=123456")
---------------------------------------------------------
-Note that the corresponding URI parameter is simply `chatId`.
+Note that the corresponding URI parameter is simply `chatId`.
\ No newline at end of file
[05/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-netty-http/src/main/docs/netty-http-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-netty-http/src/main/docs/netty-http-component.adoc b/components/camel-netty-http/src/main/docs/netty-http-component.adoc
index 03545f9..6fb6476 100644
--- a/components/camel-netty-http/src/main/docs/netty-http-component.adoc
+++ b/components/camel-netty-http/src/main/docs/netty-http-component.adoc
@@ -1,4 +1,4 @@
-# Netty HTTP Component
+## Netty HTTP Component
*Available as of Camel 2.12*
@@ -35,9 +35,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[NettyHTTP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
The URI scheme for a netty component is as follows
@@ -64,9 +62,7 @@ headers (like `CamelHttpQuery`). Endpoint options can be specified only
at the endpoint URI definition level (like `to` or `from` DSL elements).
-[[NettyHTTP-HTTPOptions]]
-HTTP Options
-^^^^^^^^^^^^
+### HTTP Options
INFO: *A lot more options*. *Important:* This component inherits all the options from
link:netty.html[Netty]. So make sure to look at the
@@ -200,9 +196,7 @@ The Netty HTTP component supports 82 endpoint options which are listed below:
-[[NettyHTTP-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
The following headers can be used on the producer to control the HTTP
request.
@@ -267,9 +261,7 @@ with the value `Basic`.
|`Content-Type` |`String` | The content type if provided. For example: `text/plain; charset="UTF-8"`.
|=======================================================================
-[[NettyHTTP-AccesstoNettytypes]]
-Access to Netty types
-^^^^^^^^^^^^^^^^^^^^^
+### Access to Netty types
This component uses the
`org.apache.camel.component.netty.http.NettyHttpMessage` as the message
@@ -283,9 +275,7 @@ accessible at all times.
org.jboss.netty.handler.codec.http.HttpRequest request = exchange.getIn(NettyHttpMessage.class).getHttpRequest();
-----------------------------------------------------------------------------------------------------------------
-[[NettyHTTP-Examples]]
-Examples
-^^^^^^^^
+### Examples
In the route below we use link:netty-http.html[Netty HTTP] as a HTTP
server, which returns back a hardcoded "Bye World" message.
@@ -307,9 +297,7 @@ link:producertemplate.html[ProducerTemplate] as shown below:
And we get back "Bye World" as the output.
-[[NettyHTTP-HowdoIletNettymatchwildcards]]
-How do I let Netty match wildcards
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How do I let Netty match wildcards
By default link:netty-http.html[Netty HTTP] will only match on exact
uri's. But you can instruct Netty to match prefixes. For example
@@ -340,9 +328,7 @@ To match *any* endpoint you can do:
from("netty-http:http://0.0.0.0:8123?matchOnUriPrefix=true").to("mock:foo");
----------------------------------------------------------------------------
-[[NettyHTTP-Usingmultiplerouteswithsameport]]
-Using multiple routes with same port
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using multiple routes with same port
In the same link:camelcontext.html[CamelContext] you can have multiple
routes from link:netty-http.html[Netty HTTP] that shares the same port
@@ -395,9 +381,7 @@ from("netty-http:http://0.0.0.0:{{port}}/bar?ssl=true")
.transform().constant("Bye Camel");
--------------------------------------------------------------------------------------
-[[NettyHTTP-Reusingsameserverbootstrapconfigurationwithmultipleroutes]]
-Reusing same server bootstrap configuration with multiple routes
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Reusing same server bootstrap configuration with multiple routes
By configuring the common server bootstrap option in an single instance
of a
@@ -435,16 +419,12 @@ And in the routes you refer to this option as shown below
</route>
---------------------------------------------------------------------------------------------------------
-[[NettyHTTP-ReusingsameserverbootstrapconfigurationwithmultipleroutesacrossmultiplebundlesinOSGicontainer]]
-Reusing same server bootstrap configuration with multiple routes across multiple bundles in OSGi container
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Reusing same server bootstrap configuration with multiple routes across multiple bundles in OSGi container
See the link:netty-http-server-example.html[Netty HTTP Server Example]
for more details and example how to do that.
-[[NettyHTTP-UsingHTTPBasicAuthentication]]
-Using HTTP Basic Authentication
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using HTTP Basic Authentication
The link:netty-http.html[Netty HTTP] consumer supports HTTP basic
authentication by specifying the security realm name to use, as shown
@@ -467,9 +447,7 @@ End user of Apache Karaf / ServiceMix has a karaf realm out of the box,
and hence why the example above would work out of the box in these
containers.
-[[NettyHTTP-SpecifyingACLonwebresources]]
-Specifying ACL on web resources
-+++++++++++++++++++++++++++++++
+#### Specifying ACL on web resources
The `org.apache.camel.component.netty.http.SecurityConstraint` allows to
define constrains on web resources. And the
@@ -521,9 +499,7 @@ below:
</route>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[NettyHTTP-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -532,5 +508,4 @@ See Also
* link:netty.html[Netty]
* link:netty-http-server-example.html[Netty HTTP Server Example]
-* link:jetty.html[Jetty]
-
+* link:jetty.html[Jetty]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-netty/src/main/docs/netty-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-netty/src/main/docs/netty-component.adoc b/components/camel-netty/src/main/docs/netty-component.adoc
index 57132d0..694e578 100644
--- a/components/camel-netty/src/main/docs/netty-component.adoc
+++ b/components/camel-netty/src/main/docs/netty-component.adoc
@@ -1,4 +1,4 @@
-# Netty Component
+## Netty Component
*Available as of Camel 2.3*
@@ -33,9 +33,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Netty-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
The URI scheme for a netty component is as follows
@@ -51,9 +49,7 @@ UDP.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Netty-Options]]
-Options
-^^^^^^^
+### Options
@@ -165,9 +161,7 @@ The Netty component supports 70 endpoint options which are listed below:
-[[Netty-RegistrybasedOptions]]
-Registry based Options
-^^^^^^^^^^^^^^^^^^^^^^
+### Registry based Options
Codec Handlers and SSL Keystores can be enlisted in the
link:registry.html[Registry], such as in the Spring XML file.
@@ -223,9 +217,7 @@ so Camel knows it should lookup.
*Important:* Read below about using non shareable encoders/decoders.
-[[Netty-Usingnonshareableencodersordecoders]]
-Using non shareable encoders or decoders
-++++++++++++++++++++++++++++++++++++++++
+#### Using non shareable encoders or decoders
If your encoders or decoders is not shareable (eg they have the
@Shareable class annotation), then your encoder/decoder must implement
@@ -239,13 +231,9 @@ The Netty component offers a
`org.apache.camel.component.netty.ChannelHandlerFactories` factory
class, that has a number of commonly used methods.
-[[Netty-SendingMessagestoandfromaNettyendpoint]]
-Sending Messages to/from a Netty endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending Messages to/from a Netty endpoint
-[[Netty-NettyProducer]]
-Netty Producer
-++++++++++++++
+#### Netty Producer
In Producer mode, the component provides the ability to send payloads to
a socket endpoint +
@@ -254,9 +242,7 @@ a socket endpoint +
The producer mode supports both one-way and request-response based
operations.
-[[Netty-NettyConsumer]]
-Netty Consumer
-++++++++++++++
+#### Netty Consumer
In Consumer mode, the component provides the ability to:
@@ -269,9 +255,7 @@ object based payloads and
The consumer mode supports both one-way and request-response based
operations.
-[[Netty-Headers]]
-Headers
-^^^^^^^
+### Headers
The following headers are filled for the exchanges created by the Netty
consumer:
@@ -292,13 +276,9 @@ netty.
|`NettyConstants.NETTY_LOCAL_ADDRESS` / `CamelNettyLocalAddress` |`java.net.SocketAddress` |Local address of the incoming socket connection.
|=======================================================================
-[[Netty-UsageSamples]]
-Usage Samples
-^^^^^^^^^^^^^
+### Usage Samples
-[[Netty-AUDPNettyendpointusingRequest-Replyandserializedobjectpayload]]
-A UDP Netty endpoint using Request-Reply and serialized object payload
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### A UDP Netty endpoint using Request-Reply and serialized object payload
[source,java]
------------------------------------------------------------------
@@ -316,9 +296,7 @@ RouteBuilder builder = new RouteBuilder() {
};
------------------------------------------------------------------
-[[Netty-ATCPbasedNettyconsumerendpointusingOne-waycommunication]]
-A TCP based Netty consumer endpoint using One-way communication
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### A TCP based Netty consumer endpoint using One-way communication
[source,java]
-------------------------------------------
@@ -330,9 +308,7 @@ RouteBuilder builder = new RouteBuilder() {
};
-------------------------------------------
-[[Netty-AnSSLTCPbasedNettyconsumerendpointusingRequest-Replycommunication]]
-An SSL/TCP based Netty consumer endpoint using Request-Reply communication
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### An SSL/TCP based Netty consumer endpoint using Request-Reply communication
[[Netty-UsingtheJSSEConfigurationUtility]]
Using the JSSE Configuration Utility
@@ -444,9 +420,7 @@ enriches the Camel link:message.html[Message] with headers having
details about the client certificate. For example the subject name is
readily available in the header `CamelNettySSLClientCertSubjectName`.
-[[Netty-UsingMultipleCodecs]]
-Using Multiple Codecs
-+++++++++++++++++++++
+#### Using Multiple Codecs
In certain cases it may be necessary to add chains of encoders and
decoders to the netty pipeline. To add multpile codecs to a camel netty
@@ -470,9 +444,7 @@ a comma separated list or contained in a List e.g.
or via spring.
-[[Netty-ClosingChannelWhenComplete]]
-Closing Channel When Complete
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Closing Channel When Complete
When acting as a server you sometimes want to close the channel when,
for example, a client conversion is finished. +
@@ -500,9 +472,7 @@ written the bye message back to the client:
});
--------------------------------------------------------------------------------------------------------
-[[Netty-Addingcustomchannelpipelinefactoriestogaincompletecontroloveracreatedpipeline]]
-Adding custom channel pipeline factories to gain complete control over a created pipeline
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Adding custom channel pipeline factories to gain complete control over a created pipeline
*Available as of Camel 2.5*
@@ -576,9 +546,7 @@ context.addRoutes(new RouteBuilder() {
});
-------------------------------------------------------------------
-[[Netty-ReusingNettybossandworkerthreadpools]]
-Reusing Netty boss and worker thread pools
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Reusing Netty boss and worker thread pools
*Available as of Camel 2.12*
@@ -637,9 +605,7 @@ And if we have another route we can refer to the shared worker pool:
... and so forth.
-[[Netty-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -647,5 +613,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:netty-http.html[Netty HTTP]
-* link:mina.html[MINA]
-
+* link:mina.html[MINA]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc b/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
index 79f724a..a90eb96 100644
--- a/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
+++ b/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
@@ -1,4 +1,4 @@
-# Netty4 HTTP Component
+## Netty4 HTTP Component
*Available as of Camel 2.14*
@@ -32,9 +32,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Netty4HTTP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
The URI scheme for a netty component is as follows
@@ -62,9 +60,7 @@ Keep also in mind that you cannot specify endpoint options using dynamic
headers (like `CamelHttpQuery`). Endpoint options can be specified only
at the endpoint URI definition level (like `to` or `from` DSL elements).
-[[Netty4HTTP-HTTPOptions]]
-HTTP Options
-^^^^^^^^^^^^
+### HTTP Options
INFO: *A lot more options*. *Important:* This component inherits all the options from
@@ -205,9 +201,7 @@ The Netty4 HTTP component supports 83 endpoint options which are listed below:
-[[Netty4HTTP-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
The following headers can be used on the producer to control the HTTP
request.
@@ -271,9 +265,7 @@ with the value `Basic`.
`text/plain; charset="UTF-8"`.
|=======================================================================
-[[Netty4HTTP-AccesstoNettytypes]]
-Access to Netty types
-^^^^^^^^^^^^^^^^^^^^^
+### Access to Netty types
This component uses the
`org.apache.camel.component.netty4.http.NettyHttpMessage` as the message
@@ -287,9 +279,7 @@ accessible at all times.
io.netty.handler.codec.http.HttpRequest request = exchange.getIn(NettyHttpMessage.class).getHttpRequest();
----------------------------------------------------------------------------------------------------------
-[[Netty4HTTP-Examples]]
-Examples
-^^^^^^^^
+### Examples
In the route below we use Netty4 HTTP as a HTTP server, which returns
back a hardcoded "Bye World" message.
@@ -311,9 +301,7 @@ link:producertemplate.html[ProducerTemplate] as shown below:
And we get back "Bye World" as the output.
-[[Netty4HTTP-HowdoIletNettymatchwildcards]]
-How do I let Netty match wildcards
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How do I let Netty match wildcards
By default Netty4 HTTP will only match on exact uri's. But you can
instruct Netty to match prefixes. For example
@@ -344,9 +332,7 @@ To match *any* endpoint you can do:
from("netty4-http:http://0.0.0.0:8123?matchOnUriPrefix=true").to("mock:foo");
-----------------------------------------------------------------------------
-[[Netty4HTTP-Usingmultiplerouteswithsameport]]
-Using multiple routes with same port
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using multiple routes with same port
In the same link:camelcontext.html[CamelContext] you can have multiple
routes from Netty4 HTTP that shares the same port (eg a
@@ -399,9 +385,7 @@ from("netty4-http:http://0.0.0.0:{{port}}/bar?ssl=true")
.transform().constant("Bye Camel");
--------------------------------------------------------------------------------------
-[[Netty4HTTP-Reusingsameserverbootstrapconfigurationwithmultipleroutes]]
-Reusing same server bootstrap configuration with multiple routes
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Reusing same server bootstrap configuration with multiple routes
By configuring the common server bootstrap option in an single instance
of a
@@ -438,16 +422,12 @@ And in the routes you refer to this option as shown below
</route>
----------------------------------------------------------------------------------------------------------
-[[Netty4HTTP-ReusingsameserverbootstrapconfigurationwithmultipleroutesacrossmultiplebundlesinOSGicontainer]]
-Reusing same server bootstrap configuration with multiple routes across multiple bundles in OSGi container
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Reusing same server bootstrap configuration with multiple routes across multiple bundles in OSGi container
See the link:netty-http-server-example.html[Netty HTTP Server Example]
for more details and example how to do that.
-[[Netty4HTTP-UsingHTTPBasicAuthentication]]
-Using HTTP Basic Authentication
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using HTTP Basic Authentication
The Netty HTTP consumer supports HTTP basic authentication by specifying
the security realm name to use, as shown below
@@ -469,9 +449,7 @@ End user of Apache Karaf / ServiceMix has a karaf realm out of the box,
and hence why the example above would work out of the box in these
containers.
-[[Netty4HTTP-SpecifyingACLonwebresources]]
-Specifying ACL on web resources
-+++++++++++++++++++++++++++++++
+#### Specifying ACL on web resources
The `org.apache.camel.component.netty4.http.SecurityConstraint` allows
to define constrains on web resources. And the
@@ -523,9 +501,7 @@ below:
</route>
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[Netty4HTTP-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -534,5 +510,4 @@ See Also
* link:netty.html[Netty]
* link:netty-http-server-example.html[Netty HTTP Server Example]
-* link:jetty.html[Jetty]
-
+* link:jetty.html[Jetty]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-netty4/src/main/docs/netty4-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-netty4/src/main/docs/netty4-component.adoc b/components/camel-netty4/src/main/docs/netty4-component.adoc
index d03e858..5b8da98 100644
--- a/components/camel-netty4/src/main/docs/netty4-component.adoc
+++ b/components/camel-netty4/src/main/docs/netty4-component.adoc
@@ -1,4 +1,4 @@
-# Netty4 Component
+## Netty4 Component
*Available as of Camel 2.14*
@@ -30,9 +30,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Netty4-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
The URI scheme for a netty component is as follows
@@ -48,9 +46,7 @@ UDP.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Netty4-Options]]
-Options
-^^^^^^^
+### Options
@@ -173,9 +169,7 @@ The Netty4 component supports 74 endpoint options which are listed below:
-[[Netty4-RegistrybasedOptions]]
-Registry based Options
-^^^^^^^^^^^^^^^^^^^^^^
+### Registry based Options
Codec Handlers and SSL Keystores can be enlisted in the
link:registry.html[Registry], such as in the Spring XML file.
@@ -231,9 +225,7 @@ so Camel knows it should lookup.
*Important:* Read below about using non shareable encoders/decoders.
-[[Netty4-Usingnonshareableencodersordecoders]]
-Using non shareable encoders or decoders
-++++++++++++++++++++++++++++++++++++++++
+#### Using non shareable encoders or decoders
If your encoders or decoders is not shareable (eg they have the
@Shareable class annotation), then your encoder/decoder must implement
@@ -247,13 +239,9 @@ The Netty component offers a
`org.apache.camel.component.netty.ChannelHandlerFactories` factory
class, that has a number of commonly used methods.
-[[Netty4-SendingMessagestofromaNettyendpoint]]
-Sending Messages to/from a Netty endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending Messages to/from a Netty endpoint
-[[Netty4-NettyProducer]]
-Netty Producer
-++++++++++++++
+#### Netty Producer
In Producer mode, the component provides the ability to send payloads to
a socket endpoint +
@@ -262,9 +250,7 @@ a socket endpoint +
The producer mode supports both one-way and request-response based
operations.
-[[Netty4-NettyConsumer]]
-Netty Consumer
-++++++++++++++
+#### Netty Consumer
In Consumer mode, the component provides the ability to:
@@ -277,13 +263,9 @@ object based payloads and
The consumer mode supports both one-way and request-response based
operations.
-[[Netty4-UsageSamples]]
-Usage Samples
-^^^^^^^^^^^^^
+### Usage Samples
-[[Netty4-AUDPNettyendpointusingRequest-Replyandserializedobjectpayload]]
-A UDP Netty endpoint using Request-Reply and serialized object payload
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### A UDP Netty endpoint using Request-Reply and serialized object payload
[source,java]
------------------------------------------------------------------
@@ -301,9 +283,7 @@ RouteBuilder builder = new RouteBuilder() {
};
------------------------------------------------------------------
-[[Netty4-ATCPbasedNettyconsumerendpointusingOne-waycommunication]]
-A TCP based Netty consumer endpoint using One-way communication
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### A TCP based Netty consumer endpoint using One-way communication
[source,java]
-------------------------------------------
@@ -315,9 +295,7 @@ RouteBuilder builder = new RouteBuilder() {
};
-------------------------------------------
-[[Netty4-AnSSLTCPbasedNettyconsumerendpointusingRequest-Replycommunication]]
-An SSL/TCP based Netty consumer endpoint using Request-Reply communication
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### An SSL/TCP based Netty consumer endpoint using Request-Reply communication
[[Netty4-UsingtheJSSEConfigurationUtility]]
Using the JSSE Configuration Utility
@@ -429,9 +407,7 @@ enriches the Camel link:message.html[Message] with headers having
details about the client certificate. For example the subject name is
readily available in the header `CamelNettySSLClientCertSubjectName`.
-[[Netty4-UsingMultipleCodecs]]
-Using Multiple Codecs
-+++++++++++++++++++++
+#### Using Multiple Codecs
In certain cases it may be necessary to add chains of encoders and
decoders to the netty pipeline. To add multpile codecs to a camel netty
@@ -538,9 +514,7 @@ or via spring.
</camelContext>
-------------------------------------------------------------------------------------------------------------
-[[Netty4-ClosingChannelWhenComplete]]
-Closing Channel When Complete
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Closing Channel When Complete
When acting as a server you sometimes want to close the channel when,
for example, a client conversion is finished. +
@@ -570,8 +544,7 @@ written the bye message back to the client:
[[Netty4-Addingcustomchannelpipelinefactoriestogaincompletecontroloveracreatedpipeline]]
Adding custom channel pipeline factories to gain complete control over a
-created pipeline
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### created pipeline
Custom channel pipelines provide complete control to the user over the
handler/interceptor chain by inserting custom handler(s), encoder(s) &
@@ -641,9 +614,7 @@ context.addRoutes(new RouteBuilder() {
});
----------------------------------------------------------------------
-[[Netty4-ReusingNettybossandworkerthreadpools]]
-Reusing Netty boss and worker thread pools
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Reusing Netty boss and worker thread pools
*Available as of Camel 2.12*
@@ -702,9 +673,7 @@ And if we have another route we can refer to the shared worker pool:
... and so forth.
-[[Netty4-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -712,4 +681,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:netty-http.html[Netty HTTP]
-* link:mina.html[MINA]
+* link:mina.html[MINA]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ognl/src/main/docs/ognl-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ognl/src/main/docs/ognl-language.adoc b/components/camel-ognl/src/main/docs/ognl-language.adoc
index afaa8b8..a189a74 100644
--- a/components/camel-ognl/src/main/docs/ognl-language.adoc
+++ b/components/camel-ognl/src/main/docs/ognl-language.adoc
@@ -1,4 +1,4 @@
-# OGNL Language
+## OGNL Language
Camel allows http://commons.apache.org/proper/commons-ognl/[OGNL] to be
used as an link:expression.html[Expression] or
@@ -21,9 +21,7 @@ you can construct the syntax as follows:
"getRequest().getBody().getFamilyName()"
----------------------------------------
-[[OGNL-Options]]
-OGNL Options
-^^^^^^^^^^^^
+### OGNL Options
// language options: START
@@ -42,9 +40,7 @@ The OGNL language supports 1 options which are listed below.
-[[OGNL-Variables]]
-Variables
-^^^^^^^^^
+### Variables
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -71,9 +67,7 @@ Variables
|property(name, type) |Type |the property by the given name as the given type
|=======================================================================
-[[OGNL-Samples]]
-Samples
-^^^^^^^
+### Samples
For example you could use OGNL inside a link:message-filter.html[Message
Filter] in XML
@@ -96,9 +90,7 @@ And the sample using Java DSL:
from("seda:foo").filter().ognl("request.headers.foo == 'bar'").to("seda:bar");
---------------------------------------------------------------------------------
-[[OGNL-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -112,9 +104,7 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").ognl("resource:classpath:myognl.txt")
------------------------------------------------------------
-[[OGNL-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use OGNL in your camel routes you need to add the a dependency on
*camel-ognl* which implements the OGNL language.
@@ -133,4 +123,4 @@ link:download.html[the download page for the latest versions]).
-------------------------------------
Otherwise, you'll also need
-http://repo2.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.ognl/2.7.3_4/org.apache.servicemix.bundles.ognl-2.7.3_4.jar[OGNL]
+http://repo2.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.ognl/2.7.3_4/org.apache.servicemix.bundles.ognl-2.7.3_4.jar[OGNL]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc b/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc
index 28a432c..50aa53a 100644
--- a/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc
+++ b/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc
@@ -1,4 +1,4 @@
-# Olingo2 Component
+## Olingo2 Component
*Available as of Camel 2.14*
@@ -30,18 +30,14 @@ for this component:
</dependency>
----------------------------------------------
-[[Olingo2-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------------------------
olingo2://endpoint/<resource-path>?[options]
------------------------------------------------
-[[Olingo2-Olingo2Component]]
-Olingo2 Options
-^^^^^^^^^^^^^^^
+### Olingo2 Options
@@ -93,9 +89,7 @@ The Olingo2 component supports 16 endpoint options which are listed below:
// endpoint options: END
-[[Olingo2-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Producer Endpoints
Producer endpoints can use endpoint names and options listed
next.�Producer endpoints can also use a special option�*`inBody`*�that
@@ -139,9 +133,7 @@ org.apache.olingo.odata2.api.commons.HttpStatusCodes for other OData resources
|update |data, resourcePath |PUT |org.apache.olingo.odata2.api.commons.HttpStatusCodes
|=======================================================================
-[[Olingo2-ODataResourceTypeMapping]]
-OData Resource Type Mapping
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### OData Resource Type Mapping
The result of *read* endpoint and data type of *data* option depends on
the OData resource being queried, created or modified.�
@@ -174,9 +166,7 @@ java.util.List<java.util.Map<String, Object>> containing list of key property na
|Count |<resource-uri>/$count |java.lang.Long
|=======================================================================
-[[Olingo2-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
Only the *read* endpoint can be used as a consumer endpoint. Consumer
endpoints can
@@ -187,16 +177,12 @@ collection will generate one exchange per element, and their routes will
be executed once for each exchange. This behavior can be disabled by
setting the endpoint property *consumer.splitResult=false*.�
-[[Olingo2-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Any URI option can be provided in a message header for producer
endpoints with a�*`CamelOlingo2.`*�prefix.
-[[Olingo2-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
All result message bodies utilize objects provided by the underlying
http://olingo.apache.org/javadoc/odata2/index.html[Apache Olingo 2.0
@@ -206,9 +192,7 @@ parameter. For endpoints that return an array or collection, a consumer
endpoint will map every element to distinct messages, unless
*consumer.splitResult* is set to *false*.
-[[Olingo2-Usecases]]
-Use cases
-^^^^^^^^^
+### Use cases
The following route reads top 5 entries from the Manufacturer feed
ordered by ascending Name property.�
@@ -265,5 +249,4 @@ consumer endpoint will produce an�*ODataFeed* value the first time, and
---------------------------------------------------------------------------------------------------------
from("olingo2://read/Manufacturers?queryParams=#paramsBean&consumer.timeUnit=SECONDS&consumer.delay=30")
.to("bean:blah");
----------------------------------------------------------------------------------------------------------
-
+---------------------------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openshift/src/main/docs/openshift-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openshift/src/main/docs/openshift-component.adoc b/components/camel-openshift/src/main/docs/openshift-component.adoc
index d68834a..6d36b61 100644
--- a/components/camel-openshift/src/main/docs/openshift-component.adoc
+++ b/components/camel-openshift/src/main/docs/openshift-component.adoc
@@ -1,4 +1,4 @@
-# OpenShift Component
+## OpenShift Component
*Available as of Camel 2.14*
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Openshift-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------
@@ -30,9 +28,7 @@ openshift:clientId[?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Openshift-Options]]
-Options
-^^^^^^^
+### Options
@@ -95,13 +91,9 @@ The OpenShift component supports 27 endpoint options which are listed below:
// endpoint options: END
-[[Openshift-Examples]]
-Examples
-^^^^^^^^
+### Examples
-[[Openshift-Listingallapplications]]
-Listing all applications
-++++++++++++++++++++++++
+#### Listing all applications
[source,java]
--------------------------------------------------------------------------
@@ -114,9 +106,7 @@ from("direct:apps")
In this case the information about all the applications is returned as
pojo. If you want a json response, then set mode=json.
-[[Openshift-Stoppinganapplication]]
-Stopping an application
-+++++++++++++++++++++++
+#### Stopping an application
[source,java]
---------------------------------------------------------------------------------------------
@@ -160,12 +150,9 @@ following headers is included.
|CamelOpenShiftEventNewState |No |The new state, for any of the event types
|=======================================================================
-[[Openshift-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-openstack/src/main/docs/openstack-cinder-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openstack/src/main/docs/openstack-cinder-component.adoc b/components/camel-openstack/src/main/docs/openstack-cinder-component.adoc
index 53d008d..f21dcc6 100644
--- a/components/camel-openstack/src/main/docs/openstack-cinder-component.adoc
+++ b/components/camel-openstack/src/main/docs/openstack-cinder-component.adoc
@@ -1,12 +1,10 @@
-# OpenStack Cinder Component
+## OpenStack Cinder Component
*Available as of Camel 2.19*
The openstack-cinder component allows messages to be sent to an OpenStack block storage services.
-[[openstack-cinder-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -24,9 +22,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel.
-[[openstack-cinder-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
----------------------------
@@ -36,9 +32,7 @@ openstack-cinder://hosturl[?options]
You can append query options to the URI in the following format
`?options=value&option2=value&...`
-[[openstack-cinder-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
The OpenStack Cinder component has no options.
@@ -66,17 +60,12 @@ The OpenStack Cinder component supports 10 endpoint options which are listed bel
// endpoint options: END
-[[openstack-cinder-Usage]]
-Usage
-^^^^^
+### Usage
You can use following settings for each subsystem:
-volumes
-~~~~~~~
+### volumes
-[[openstack-cinder-OperationsYouCanPerformWiththeVolumeProducer]]
-Operations you can perform with the Volume producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Volume producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -94,9 +83,7 @@ Operations you can perform with the Volume producer
|`delete` | Delete the volume.
|=========================================================================
-[[openstack-cinder-MessageheadersevaluatedbytheVolumeProducer]]
-Message headers evaluated by the Volume producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Volume producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -123,12 +110,9 @@ Message headers evaluated by the Volume producer
If you need more precise volume settings you can create new object of the type *org.openstack4j.model.storage.block.Volume* and send in the message body.
-snapshots
-~~~~~~~~~
+### snapshots
-[[openstack-cinder-OperationsYouCanPerformWiththeSnapshotProducer]]
-Operations you can perform with the Snapshot producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Snapshot producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -145,9 +129,7 @@ Operations you can perform with the Snapshot producer
|=========================================================================
-[[openstack-cinder-MessageheadersevaluatedbytheSnapshotProducer]]
-Message headers evaluated by the Snapshot producer
-++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Snapshot producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -169,14 +151,11 @@ Message headers evaluated by the Snapshot producer
If you need more precise server settings you can create new object of the type *org.openstack4j.model.storage.block.VolumeSnapshot* and send in the message body.
-[[CamelOpenstack-cinder-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:openstack.html[openstack Component]
-
+* link:openstack.html[openstack Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openstack/src/main/docs/openstack-glance-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openstack/src/main/docs/openstack-glance-component.adoc b/components/camel-openstack/src/main/docs/openstack-glance-component.adoc
index 168e4f8..db76a0c 100644
--- a/components/camel-openstack/src/main/docs/openstack-glance-component.adoc
+++ b/components/camel-openstack/src/main/docs/openstack-glance-component.adoc
@@ -1,12 +1,10 @@
-# OpenStack Glance Component
+## OpenStack Glance Component
*Available as of Camel 2.19*
The openstack-glance component allows messages to be sent to an OpenStack image services.
-[[openstack-glance-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -24,9 +22,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel.
-[[openstack-glance-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
----------------------------
@@ -36,9 +32,7 @@ openstack-glance://hosturl[?options]
You can append query options to the URI in the following format
`?options=value&option2=value&...`
-[[openstack-glance-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
The OpenStack Glance component has no options.
@@ -65,9 +59,7 @@ The OpenStack Glance component supports 9 endpoint options which are listed belo
// endpoint options: END
-[[openstack-glance-Usage]]
-Usage
-^^^^^
+### Usage
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
@@ -88,9 +80,7 @@ Usage
|`delete` | Delete the image.
|=========================================================================
-[[openstack-glance-MessageheadersevaluatedbytheGlanceProducer]]
-Message headers evaluated by the Glance producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Glance producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -121,14 +111,11 @@ Message headers evaluated by the Glance producer
|`properties` | `Map` | Image properties.
|=========================================================================
-[[CamelOpenstack-glance-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:openstack.html[openstack Component]
-
+* link:openstack.html[openstack Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openstack/src/main/docs/openstack-keystone-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openstack/src/main/docs/openstack-keystone-component.adoc b/components/camel-openstack/src/main/docs/openstack-keystone-component.adoc
index 4460243..6e1b10f 100644
--- a/components/camel-openstack/src/main/docs/openstack-keystone-component.adoc
+++ b/components/camel-openstack/src/main/docs/openstack-keystone-component.adoc
@@ -1,4 +1,4 @@
-# OpenStack Keystone Component
+## OpenStack Keystone Component
*Available as of Camel 2.19*
@@ -6,9 +6,7 @@ The openstack-keystone component allows messages to be sent to an OpenStack iden
*The openstack-keystone component supports only Identity API v3!*
-[[openstack-keystone-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -26,9 +24,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel.
-[[openstack-keystone-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
----------------------------
@@ -38,9 +34,7 @@ openstack-keystone://hosturl[?options]
You can append query options to the URI in the following format
`?options=value&option2=value&...`
-[[openstack-keystone-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
The OpenStack Keystone component has no options.
@@ -67,17 +61,12 @@ The OpenStack Keystone component supports 9 endpoint options which are listed be
// endpoint options: END
-[[openstack-keystone-Usage]]
-Usage
-^^^^^
+### Usage
You can use following settings for each subsystem:
-domains
-~~~~~~~
+### domains
-[[openstack-keystone-OperationsYouCanPerformWithDomainProducer]]
-Operations you can perform with the Domain producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Domain producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -93,9 +82,7 @@ Operations you can perform with the Domain producer
|`delete` | Delete the domain.
|=========================================================================
-[[openstack-keystone-MessageHeadersEvaluatedByTheDomainProducer]]
-Message headers evaluated by the Domain producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Domain producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -112,12 +99,9 @@ Message headers evaluated by the Domain producer
If you need more precise domain settings you can create new object of the type *org.openstack4j.model.identity.v3.Domain* and send in the message body.
-groups
-~~~~~~
+### groups
-[[openstack-keystone-OperationsYouCanPerformWithGroupProducer]]
-Operations you can perform with the Group producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Group producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -139,9 +123,7 @@ Operations you can perform with the Group producer
|`removeUserFromGroup` | Remove the user from the group.
|=========================================================================
-[[openstack-keystone-MessageHeadersEvaluatedByTheGroupProducer]]
-Message headers evaluated by the Group producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Group producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -162,12 +144,9 @@ Message headers evaluated by the Group producer
If you need more precise group settings you can create new object of the type *org.openstack4j.model.identity.v3.Group* and send in the message body.
-projects
-~~~~~~~~
+### projects
-[[openstack-keystone-OperationsYouCanPerformWithProjectProducer]]
-Operations you can perform with the Project producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Project producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -183,9 +162,7 @@ Operations you can perform with the Project producer
|`delete` | Delete the project.
|=========================================================================
-[[openstack-keystone-MessageHeadersEvaluatedByTheProjectProducer]]
-Message headers evaluated by the Project producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Project producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -206,12 +183,9 @@ Message headers evaluated by the Project producer
If you need more precise project settings you can create new object of the type *org.openstack4j.model.identity.v3.Project* and send in the message body.
-regions
-~~~~~~~
+### regions
-[[openstack-keystone-OperationsYouCanPerformWithRegionProducer]]
-Operations you can perform with the Region producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Region producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -227,9 +201,7 @@ Operations you can perform with the Region producer
|`delete` | Delete the region.
|=========================================================================
-[[openstack-keystone-MessageHeadersEvaluatedByTheRegionProducer]]
-Message headers evaluated by the Region producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Region producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -244,12 +216,9 @@ Message headers evaluated by the Region producer
If you need more precise region settings you can create new object of the type *org.openstack4j.model.identity.v3.Region* and send in the message body.
-users
-~~~~~
+### users
-[[openstack-keystone-OperationsYouCanPerformWithUserProducer]]
-Operations you can perform with the User producer
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the User producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -265,9 +234,7 @@ Operations you can perform with the User producer
|`delete` | Delete the user.
|=========================================================================
-[[openstack-keystone-MessageHeadersEvaluatedByTheUserProducer]]
-Message headers evaluated by the User producer
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the User producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -290,14 +257,11 @@ Message headers evaluated by the User producer
If you need more precise user settings you can create new object of the type *org.openstack4j.model.identity.v3.User* and send in the message body.
-[[CamelOpenstack-keystone-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:openstack.html[openstack Component]
-
+* link:openstack.html[openstack Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openstack/src/main/docs/openstack-neutron-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openstack/src/main/docs/openstack-neutron-component.adoc b/components/camel-openstack/src/main/docs/openstack-neutron-component.adoc
index 90e9ccd..61f0661 100644
--- a/components/camel-openstack/src/main/docs/openstack-neutron-component.adoc
+++ b/components/camel-openstack/src/main/docs/openstack-neutron-component.adoc
@@ -1,12 +1,10 @@
-# OpenStack Neutron Component
+## OpenStack Neutron Component
*Available as of Camel 2.19*
The openstack-neutron component allows messages to be sent to an OpenStack network services.
-[[openstack-neutron-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -24,9 +22,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel.
-[[openstack-neutron-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
----------------------------
@@ -36,9 +32,7 @@ openstack-neutron://hosturl[?options]
You can append query options to the URI in the following format
`?options=value&option2=value&...`
-[[openstack-neutron-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
The OpenStack Neutron component has no options.
@@ -66,17 +60,12 @@ The OpenStack Neutron component supports 10 endpoint options which are listed be
// endpoint options: END
-[[openstack-neutron-Usage]]
-Usage
-^^^^^
+### Usage
You can use following settings for each subsystem:
-networks
-~~~~~~~~
+### networks
-[[openstack-neutron-OperationsYouCanPerformWiththeNetworkProducer]]
-Operations you can perform with the Network producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Network producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -90,9 +79,7 @@ Operations you can perform with the Network producer
|`delete` | Delete the network.
|=========================================================================
-[[openstack-neutron-MessageheadersevaluatedbytheNetworkProducer]]
-Message headers evaluated by the Network producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Network producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -121,12 +108,9 @@ Message headers evaluated by the Network producer
If you need more precise network settings you can create new object of the type *org.openstack4j.model.network.Network* and send in the message body.
-subnets
-~~~~~~~
+### subnets
-[[openstack-neutron-OperationsYouCanPerformWiththeSubnetProducer]]
-Operations you can perform with the Subnet producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Subnet producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -142,9 +126,7 @@ Operations you can perform with the Subnet producer
|`action` | Perform an action on the subnet.
|=========================================================================
-[[openstack-neutron-MessageheadersevaluatedbytheSubnetProducer]]
-Message headers evaluated by the Subnet producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Subnet producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -165,12 +147,9 @@ Message headers evaluated by the Subnet producer
If you need more precise subnet settings you can create new object of the type *org.openstack4j.model.network.Subnet* and send in the message body.
-ports
-~~~~~
+### ports
-[[openstack-neutron-OperationsYouCanPerformWiththePortProducer]]
-Operations you can perform with the Port producer
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Port producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -187,9 +166,7 @@ Operations you can perform with the Port producer
|=========================================================================
-[[openstack-neutron-MessageheadersevaluatedbythePortProducer]]
-Message headers evaluated by the Port producer
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Port producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -208,12 +185,9 @@ Message headers evaluated by the Port producer
|`macAddress` | `String` | MAC address.
|=========================================================================
-routers
-~~~~~~~
+### routers
-[[openstack-neutron-OperationsYouCanPerformWiththeRouterProducer]]
-Operations you can perform with the Router producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Router producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -234,9 +208,7 @@ Operations you can perform with the Router producer
|=========================================================================
-[[openstack-neutron-MessageheadersevaluatedbytheRouterProducer]]
-Message headers evaluated by the Port producer
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Port producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -258,14 +230,11 @@ Message headers evaluated by the Port producer
|=========================================================================
-[[CamelOpenstack-neutron-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:openstack.html[openstack Component]
-
+* link:openstack.html[openstack Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openstack/src/main/docs/openstack-nova-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openstack/src/main/docs/openstack-nova-component.adoc b/components/camel-openstack/src/main/docs/openstack-nova-component.adoc
index f37d49c..743f328 100644
--- a/components/camel-openstack/src/main/docs/openstack-nova-component.adoc
+++ b/components/camel-openstack/src/main/docs/openstack-nova-component.adoc
@@ -1,12 +1,10 @@
-# OpenStack Nova Component
+## OpenStack Nova Component
*Available as of Camel 2.19*
The openstack-nova component allows messages to be sent to an OpenStack compute services.
-[[openstack-nova-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -24,9 +22,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel.
-[[openstack-nova-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
----------------------------
@@ -36,9 +32,7 @@ openstack-nova://hosturl[?options]
You can append query options to the URI in the following format
`?options=value&option2=value&...`
-[[openstack-nova-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
The OpenStack Nova component has no options.
@@ -66,17 +60,12 @@ The OpenStack Nova component supports 10 endpoint options which are listed below
// endpoint options: END
-[[openstack-nova-Usage]]
-Usage
-^^^^^
+### Usage
You can use following settings for each subsystem:
-flavors
-~~~~~~~
+### flavors
-[[openstack-nova-OperationsYouCanPerformWiththeFlavorProducer]]
-Operations you can perform with the Flavor producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Flavor producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -90,9 +79,7 @@ Operations you can perform with the Flavor producer
|`delete` | Delete the flavor.
|=========================================================================
-[[openstack-nova-MessageheadersevaluatedbytheFlavorProducer]]
-Message headers evaluated by the Flavor producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Flavor producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -117,12 +104,9 @@ Message headers evaluated by the Flavor producer
If you need more precise flavor settings you can create new object of the type *org.openstack4j.model.compute.Flavor* and send in the message body.
-servers
-~~~~~~~
+### servers
-[[openstack-nova-OperationsYouCanPerformWiththeServerProducer]]
-Operations you can perform with the Server producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Server producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -140,9 +124,7 @@ Operations you can perform with the Server producer
|`action` | Perform an action on the server.
|=========================================================================
-[[openstack-nova-MessageheadersevaluatedbytheServerProducer]]
-Message headers evaluated by the Server producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Server producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -169,12 +151,9 @@ Message headers evaluated by the Server producer
If you need more precise server settings you can create new object of the type *org.openstack4j.model.compute.ServerCreate* and send in the message body.
-keypairs
-~~~~~~~~
+### keypairs
-[[openstack-nova-OperationsYouCanPerformWiththeKeypairProducer]]
-Operations you can perform with the Keypair producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Keypair producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -189,9 +168,7 @@ Operations you can perform with the Keypair producer
|=========================================================================
-[[openstack-nova-MessageheadersevaluatedbytheKeypairProducer]]
-Message headers evaluated by the Keypair producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Keypair producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -203,14 +180,11 @@ Message headers evaluated by the Keypair producer
|=========================================================================
-[[CamelOpenstack-nova-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:openstack.html[openstack Component]
-
+* link:openstack.html[openstack Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openstack/src/main/docs/openstack-swift-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openstack/src/main/docs/openstack-swift-component.adoc b/components/camel-openstack/src/main/docs/openstack-swift-component.adoc
index e7581a0..f19769f 100644
--- a/components/camel-openstack/src/main/docs/openstack-swift-component.adoc
+++ b/components/camel-openstack/src/main/docs/openstack-swift-component.adoc
@@ -1,12 +1,10 @@
-# OpenStack Swift Component
+## OpenStack Swift Component
*Available as of Camel 2.19*
The openstack-swift component allows messages to be sent to an OpenStack object storage services.
-[[openstack-swift-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -24,9 +22,7 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel.
-[[openstack-swift-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
----------------------------
@@ -36,9 +32,7 @@ openstack-swift://hosturl[?options]
You can append query options to the URI in the following format
`?options=value&option2=value&...`
-[[openstack-swift-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
The OpenStack Swift component has no options.
@@ -66,17 +60,12 @@ The OpenStack Swift component supports 10 endpoint options which are listed belo
// endpoint options: END
-[[openstack-swift-Usage]]
-Usage
-^^^^^
+### Usage
You can use following settings for each subsystem:
-containers
-~~~~~~~~~~
+### containers
-[[openstack-swift-OperationsYouCanPerformWiththeContainerProducer]]
-Operations you can perform with the Container producer
-++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Container producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -98,9 +87,7 @@ Operations you can perform with the Container producer
|`deleteMetadata` | Delete metadata.
|=========================================================================
-[[openstack-swift-MessageheadersevaluatedbytheVolumeProducer]]
-Message headers evaluated by the Volume producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Volume producer
[width="100%",cols="20%,10%,70%",options="header",]
|=========================================================================
@@ -133,12 +120,9 @@ Message headers evaluated by the Volume producer
If you need more precise container settings you can create new object of the type *org.openstack4j.model.storage.object.options.CreateUpdateContainerOptions* (in case of create or update operation)
or *org.openstack4j.model.storage.object.options.ContainerListOptions* for listing containers and send in the message body.
-objects
-~~~~~~~
+### objects
-[[openstack-swift-OperationsYouCanPerformWiththeObjectsProducer]]
-Operations you can perform with the Object producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Object producer
[width="100%",cols="20%,80%",options="header",]
|=========================================================================
|Operation | Description
@@ -159,9 +143,7 @@ Operations you can perform with the Object producer
|=========================================================================
-[[openstack-swift-MessageheadersevaluatedbytheObjectProducer]]
-Message headers evaluated by the Object producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Object producer
[width="100%",cols="10%,10%,80%",options="header",]
|=========================================================================
@@ -175,14 +157,11 @@ Message headers evaluated by the Object producer
|=========================================================================
-[[CamelOpenstack-swift-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:openstack.html[openstack Component]
-
+* link:openstack.html[openstack Component]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-optaplanner/src/main/docs/optaplanner-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-optaplanner/src/main/docs/optaplanner-component.adoc b/components/camel-optaplanner/src/main/docs/optaplanner-component.adoc
index e1ffa11..eb72003 100644
--- a/components/camel-optaplanner/src/main/docs/optaplanner-component.adoc
+++ b/components/camel-optaplanner/src/main/docs/optaplanner-component.adoc
@@ -1,4 +1,4 @@
-# OptaPlanner Component
+## OptaPlanner Component
*Available as of Camel 2.13*
@@ -22,9 +22,7 @@ for this component:
</dependency>
------------------------------------------------------------------------------------
-[[OptaPlanner-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------------
@@ -37,9 +35,7 @@ example `/org/foo/barSolverConfig.xml`.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[OptaPlanner-URIOptions]]
-OptaPlanner Options
-^^^^^^^^^^^
+### OptaPlanner Options
// component options: START
@@ -68,9 +64,7 @@ The OptaPlanner component supports 8 endpoint options which are listed below:
// endpoint options: END
-[[OptaPlanner-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="10%,10%,10%,10%,60%",options="header",]
|=======================================================================
@@ -82,9 +76,7 @@ Message Headers
rather than blocking the current thread.
|=======================================================================
-[[OptaPlanner-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
Camel takes the planning problem for the IN body, solves it and returns
it on the OUT body. (since v 2.16) The IN body object supports the following use cases:
@@ -98,9 +90,7 @@ wait till isEveryProblemFactChangeProcessed before returning result.
* If the body is none of the above types, then the producer will return
the best result from the solver identified by solverId
-[[OptaPlanner-Termination]]
-Termination
-^^^^^^^^^^^
+### Termination
The solving will take as long as specified in the `solverConfig`.
@@ -120,9 +110,7 @@ The solving will take as long as specified in the `solverConfig`.
�
-[[OptaPlanner-Samples]]
-Samples
-+++++++
+#### Samples
Solve an planning problem that's on the ActiveMQ queue with OptaPlanner:
@@ -140,12 +128,9 @@ from("cxfrs:bean:rsServer?bindingStyle=SimpleConsumer")
.to("optaplanner:/org/foo/barSolverConfig.xml");
-------------------------------------------------------
-[[OptaPlanner-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-paho/src/main/docs/paho-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-paho/src/main/docs/paho-component.adoc b/components/camel-paho/src/main/docs/paho-component.adoc
index 1dda450..c1c4a55 100644
--- a/components/camel-paho/src/main/docs/paho-component.adoc
+++ b/components/camel-paho/src/main/docs/paho-component.adoc
@@ -1,4 +1,4 @@
-# Paho Component
+## Paho Component
INFO: Available as of Camel 2.16�
@@ -7,9 +7,7 @@ the https://eclipse.org/paho/[Eclipse Paho] library. Paho is one of the
most popular MQTT libraries, so if you would like to integrate it with
your Java project - Camel Paho connector is a way to go.
-[[Paho-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------
@@ -47,9 +45,7 @@ from("paho:some/queue?brokerUrl=tcp://iot.eclipse.org:1883").
�
-[[Paho-Addingthecomponenttotheproject]]
-Adding the component to the project
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Adding the component to the project
Maven users will need to add the following dependency to their `pom.xml`
for this component:
@@ -80,9 +76,7 @@ you need to add Eclipse Paho repository to your POM xml file:
</repositories>
--------------------------------------------------------------------------
-[[Paho-Defaultpayloadtype]]
-Default payload type
-^^^^^^^^^^^^^^^^^^^^
+### Default payload type
�
@@ -118,9 +112,7 @@ String payload = "message";
producerTemplate.sendBody("paho:topic", payload);
--------------------------------------------------------------------------
-[[Paho-URIOptions]]
-Paho Options
-^^^^^^^^^^^^
+### Paho Options
@@ -167,9 +159,7 @@ The Paho component supports 12 endpoint options which are listed below:
// endpoint options: END
-[[Paho-Headers]]
-Headers
-^^^^^^^
+### Headers
The following headers are recognized by the Paho component:
@@ -187,12 +177,9 @@ stored as a header but on the
|=======================================================================
�
-[[Paho-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-paxlogging/src/main/docs/paxlogging-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-paxlogging/src/main/docs/paxlogging-component.adoc b/components/camel-paxlogging/src/main/docs/paxlogging-component.adoc
index 2a6320f..024d3b2 100644
--- a/components/camel-paxlogging/src/main/docs/paxlogging-component.adoc
+++ b/components/camel-paxlogging/src/main/docs/paxlogging-component.adoc
@@ -1,4 +1,4 @@
-# OSGi PAX Logging Component
+## OSGi PAX Logging Component
*Available in Camel 2.6*
@@ -6,9 +6,7 @@ The `paxlogging` component can be used in an OSGi environment to receive
http://wiki.ops4j.org/display/paxlogging/Pax+Logging[PaxLogging] events
and process them.
-[[Pax-Logging-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users need to add the following dependency to their `pom.xml`
@@ -24,9 +22,7 @@ Maven users need to add the following dependency to their `pom.xml`
where `${camel-version`} must be replaced by the actual version of Camel
(2.6.0 or higher).
-[[Pax-Logging-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,xml]
-----------------------------
@@ -36,9 +32,7 @@ paxlogging:appender[?options]
where `appender` is the name of the pax appender that need to be
configured in the PaxLogging service configuration.
-[[Pax-Logging-URIoptions]]
-URI options
-^^^^^^^^^^^
+### URI options
@@ -76,15 +70,11 @@ The OSGi PAX Logging component supports 5 endpoint options which are listed belo
// endpoint options: END
-[[Pax-Logging-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
The `in` message body will be set to the received PaxLoggingEvent.
-[[Pax-Logging-Exampleusage]]
-Example usage
-^^^^^^^^^^^^^
+### Example usage
[source,xml]
----------------------------------
@@ -99,4 +89,4 @@ Configuration:
[source,java]
----------------------------------------------------------
log4j.rootLogger=INFO, out, osgi:VmLogAppender, osgi:camel
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-pdf/src/main/docs/pdf-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-pdf/src/main/docs/pdf-component.adoc b/components/camel-pdf/src/main/docs/pdf-component.adoc
index 052f899..6723202 100644
--- a/components/camel-pdf/src/main/docs/pdf-component.adoc
+++ b/components/camel-pdf/src/main/docs/pdf-component.adoc
@@ -1,4 +1,4 @@
-# PDF Component
+## PDF Component
**Available as of Camel 2.16.0**
@@ -22,9 +22,7 @@ following dependency to their�`pom.xml`:
</dependency>
------------------------------------------------------------
-[[PDF-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
The PDF component only supports producer endpoints.
@@ -33,9 +31,7 @@ The PDF component only supports producer endpoints.
pdf:operation[?options]
-----------------------
-[[PDF-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The PDF component has no options.
@@ -65,9 +61,7 @@ The PDF component supports 10 endpoint options which are listed below:
// endpoint options: END
-[[PDF-Headers]]
-Headers
-^^^^^^^
+### Headers
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
|Header |Description
@@ -86,9 +80,7 @@ ishttps://pdfbox.apache.org/docs/1.8.9/javadocs/org/apache/pdfbox/pdmodel/encryp
*Mandatory* header if PDF document is encrypted.
|=======================================================================
-[[PDF-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -97,4 +89,4 @@ See Also
-
�
--
+-
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-pgevent/src/main/docs/pgevent-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-pgevent/src/main/docs/pgevent-component.adoc b/components/camel-pgevent/src/main/docs/pgevent-component.adoc
index de2ef0b..6faaec4 100644
--- a/components/camel-pgevent/src/main/docs/pgevent-component.adoc
+++ b/components/camel-pgevent/src/main/docs/pgevent-component.adoc
@@ -1,4 +1,4 @@
-# PostgresSQL Event Component
+## PostgresSQL Event Component
This is a component for Apache Camel which allows for
Producing/Consuming PostgreSQL events related to the LISTEN/NOTIFY
@@ -31,9 +31,7 @@ pgevent://host:port/database/channel[?parameters]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[PGEvent-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -65,12 +63,9 @@ The PostgresSQL Event component supports 11 endpoint options which are listed be
// endpoint options: END
-[[PGEvent-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-printer/src/main/docs/lpr-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-printer/src/main/docs/lpr-component.adoc b/components/camel-printer/src/main/docs/lpr-component.adoc
index 8b07696..ecaf9b7 100644
--- a/components/camel-printer/src/main/docs/lpr-component.adoc
+++ b/components/camel-printer/src/main/docs/lpr-component.adoc
@@ -1,4 +1,4 @@
-# Printer Component
+## Printer Component
*Available as of Camel 2.1*
@@ -27,9 +27,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Printer-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
Since the URI scheme for a printer has not been standardized (the
nearest thing to a standard being the IETF print standard) and therefore
@@ -44,9 +42,7 @@ lpr://remotehost:port/path/to/printer[?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Printer-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -81,25 +77,17 @@ The Printer component supports 14 endpoint options which are listed below:
// endpoint options: END
-[[Printer-SendingMessagestoaPrinter]]
-Sending Messages to a Printer
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending Messages to a Printer
-[[Printer-PrinterProducer]]
-Printer Producer
-++++++++++++++++
+#### Printer Producer
Sending data to the printer is very straightforward and involves
creating a producer endpoint that can be sent message exchanges on in
route.
-[[Printer-UsageSamples]]
-Usage Samples
-^^^^^^^^^^^^^
+### Usage Samples
-[[Printer-Example1:PrintingtextbasedpayloadsonaDefaultprinterusingletterstationaryandone-sidedmode]]
-Example 1: Printing text based payloads on a Default printer using letter stationary and one-sided mode
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 1: Printing text based payloads on a Default printer using letter stationary and one-sided mode
[source,java]
-----------------------------------------------
@@ -114,9 +102,7 @@ RouteBuilder builder = new RouteBuilder() {
}};
-----------------------------------------------
-[[Printer-Example2:PrintingGIFbasedpayloadsonaRemoteprinterusingA4stationaryandone-sidedmode]]
-Example 2: Printing GIF based payloads on a Remote printer using A4 stationary and one-sided mode
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 2: Printing GIF based payloads on a Remote printer using A4 stationary and one-sided mode
[source,java]
--------------------------------------------------
@@ -130,9 +116,7 @@ RouteBuilder builder = new RouteBuilder() {
}};
--------------------------------------------------
-[[Printer-Example3:PrintingJPEGbasedpayloadsonaRemoteprinterusingJapanesePostcardstationaryandone-sidedmode]]
-Example 3: Printing JPEG based payloads on a Remote printer using Japanese Postcard stationary and one-sided mode
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 3: Printing JPEG based payloads on a Remote printer using Japanese Postcard stationary and one-sided mode
[source,java]
--------------------------------------------------
@@ -145,4 +129,4 @@ RouteBuilder builder = new RouteBuilder() {
"&mediaSize=JAPANESE_POSTCARD" +
"&flavor=DocFlavor.INPUT_STREAM")
}};
---------------------------------------------------
+--------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc b/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc
index f6610e4..abc66f6 100644
--- a/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc
+++ b/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc
@@ -1,4 +1,4 @@
-# Protobuf DataFormat
+## Protobuf DataFormat
[[Protobuf-Protobuf-ProtocolBuffers]]
Protobuf - Protocol Buffers
---------------------------
@@ -21,9 +21,7 @@ http://code.google.com/apis/protocolbuffers/[API Site] +
http://code.google.com/apis/protocolbuffers/docs/javatutorial.html[Protobuf
Java Tutorial]
-[[Protobuf-Options]]
-Protobuf Options
-^^^^^^^^^^^^^^^^
+### Protobuf Options
// dataformat options: START
The Protobuf dataformat supports 2 options which are listed below.
@@ -40,17 +38,13 @@ The Protobuf dataformat supports 2 options which are listed below.
{% endraw %}
// dataformat options: END
-[[Protobuf-Protobufoverview]]
-Protobuf overview
-~~~~~~~~~~~~~~~~~
+### Protobuf overview
This quick overview of how to use Protobuf. For more detail see the
http://code.google.com/apis/protocolbuffers/docs/javatutorial.html[complete
tutorial]
-[[Protobuf-Definingtheprotoformat]]
-Defining the proto format
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Defining the proto format
The first step is to define the format for the body of your exchange.
This is defined in a .proto file as so:
@@ -89,9 +83,7 @@ message AddressBook {
}
------------------------------------------------------------
-[[Protobuf-GeneratingJavaclasses]]
-Generating Java classes
-^^^^^^^^^^^^^^^^^^^^^^^
+### Generating Java classes
The Protobuf SDK provides a compiler which will generate the Java
classes for the format we defined in our .proto file. You can run the
@@ -110,9 +102,7 @@ to use a class that does not implement com.google.protobuf.Message. Use
the generated builders to translate the data from any of your existing
domain classes.
-[[Protobuf-JavaDSL]]
-Java DSL
-~~~~~~~~
+### Java DSL
You can use create the ProtobufDataFormat instance and pass it to Camel
DataFormat marshal and unmarsha API like this.
@@ -139,9 +129,7 @@ default instance class name like this.
from("direct:unmarshalB").unmarshal().protobuf(Person.getDefaultInstance()).to("mock:reverse");
--------------------------------------------------------------------------------------------------
-[[Protobuf-SpringDSL]]
-Spring DSL
-~~~~~~~~~~
+### Spring DSL
The following example shows how to use Castor to unmarshal using Spring
configuring the protobuf data type
@@ -159,9 +147,7 @@ configuring the protobuf data type
</camelContext>
----------------------------------------------------------------------------------------------------------
-[[Protobuf-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Protobuf in your camel routes you need to add the a dependency on
*camel-protobuf* which implements this data format.
@@ -177,4 +163,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-protobuf</artifactId>
<version>2.2.0</version>
</dependency>
------------------------------------------
+-----------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-quartz/src/main/docs/quartz-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-quartz/src/main/docs/quartz-component.adoc b/components/camel-quartz/src/main/docs/quartz-component.adoc
index a2c0df2..55ef207 100644
--- a/components/camel-quartz/src/main/docs/quartz-component.adoc
+++ b/components/camel-quartz/src/main/docs/quartz-component.adoc
@@ -1,4 +1,4 @@
-# Quartz Component
+## Quartz Component
The *quartz:* component provides a scheduled delivery of messages using
the http://www.quartz-scheduler.org/[Quartz Scheduler 1.x]. +
@@ -21,9 +21,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Quartz-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------------------------
@@ -41,9 +39,7 @@ name.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Quartz-Options]]
-Options
-^^^^^^^
+### Options
@@ -115,9 +111,7 @@ required by the `QuartzScheduler` in the OSGi container. If you do not
set any `id` on <camelContext> then +
a unique id is auto assigned, and there is no problem.
-[[Quartz-Configuringquartz.propertiesfile]]
-Configuring quartz.properties file
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring quartz.properties file
By default Quartz will look for a `quartz.properties` file in the
`org/quartz` directory of the classpath. If you are using WAR
@@ -145,9 +139,7 @@ To do this you can configure this in Spring XML as follows
</bean>
-------------------------------------------------------------------------------
-[[Quartz-EnablingQuartzschedulerinJMX]]
-Enabling Quartz scheduler in JMX
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling Quartz scheduler in JMX
You need to configure the quartz scheduler properties to enable JMX. +
That is typically setting the option
@@ -157,9 +149,7 @@ configuration file.
From Camel 2.13 onwards Camel will automatic set this option to true,
unless explicit disabled.
-[[Quartz-StartingtheQuartzscheduler]]
-Starting the Quartz scheduler
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Starting the Quartz scheduler
This is an example:
@@ -170,9 +160,7 @@ This is an example:
</bean>
----------------------------------------------------------------------------
-[[Quartz-Clustering]]
-Clustering
-^^^^^^^^^^
+### Clustering
*Available as of Camel 2.4*
@@ -184,9 +172,7 @@ allows the trigger to keep running on the other nodes in the cluster.
*Note*: When running in clustered node no checking is done to ensure
unique job name/group for endpoints.
-[[Quartz-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Camel adds the getters from the Quartz Execution Context as header
values. The following headers are added: +
@@ -198,9 +184,7 @@ values. The following headers are added: +
The `fireTime` header contains the `java.util.Date` of when the exchange
was fired.
-[[Quartz-UsingCronTriggers]]
-Using Cron Triggers
-^^^^^^^^^^^^^^^^^^^
+### Using Cron Triggers
Quartz supports
http://www.quartz-scheduler.org/documentation/quartz-2.1.x/tutorials/crontrigger[Cron-like
@@ -235,9 +219,7 @@ valid URI syntax:
|`+` | _Space_
|=======================================================================
-[[Quartz-Specifyingtimezone]]
-Specifying time zone
-^^^^^^^^^^^^^^^^^^^^
+### Specifying time zone
*Available as of Camel 2.8.1* +
The Quartz Scheduler allows you to configure time zone per trigger. For
@@ -256,9 +238,7 @@ Converter] to be able configure this from the endpoint uri. +
From Camel 2.8.1 onwards we have included such a
link:type-converter.html[Type Converter] in the camel-core.
-[[Quartz-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -266,5 +246,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:quartz2.html[Quartz2]
-* link:timer.html[Timer]
-
+* link:timer.html[Timer]
\ No newline at end of file
[07/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jms/src/main/docs/jms-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jms/src/main/docs/jms-component.adoc b/components/camel-jms/src/main/docs/jms-component.adoc
index c0bd57c..1596260 100644
--- a/components/camel-jms/src/main/docs/jms-component.adoc
+++ b/components/camel-jms/src/main/docs/jms-component.adoc
@@ -1,4 +1,4 @@
-# JMS Component
+## JMS Component
ifdef::env-github[]
:icon-smile: :smiley:
:caution-caption: :boom:
@@ -14,9 +14,7 @@ ifndef::env-github[]
endif::[]
-[[JMS-JMSComponent]]
-JMS Component
-~~~~~~~~~~~~~
+### JMS Component
[TIP]
====
@@ -66,9 +64,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[JMS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
--------------------------------------------
jms:[queue:|topic:]destinationName[?options]
@@ -99,13 +95,9 @@ jms:topic:Stocks.Prices
You append query options to the URI using the following format,
`?option=value&option=value&...`
-[[JMS-Notes]]
-Notes
-^^^^^
+### Notes
-[[JMS-UsingActiveMQ]]
-Using ActiveMQ
-++++++++++++++
+#### Using ActiveMQ
The JMS component reuses Spring 2's `JmsTemplate` for sending messages.
This is not ideal for use in a non-J2EE container and typically requires
@@ -120,9 +112,7 @@ then we recommend that you either:
optimized to use ActiveMQ efficiently
* Use the `PoolingConnectionFactory` in ActiveMQ.
-[[JMS-TransactionsandCacheLevels]]
-Transactions and Cache Levels
-+++++++++++++++++++++++++++++
+#### Transactions and Cache Levels
If you are consuming messages and using transactions
(`transacted=true`) then the default settings for cache level can impact
@@ -148,9 +138,7 @@ level accordingly to:
So you can say the default setting is conservative. Consider using
`cacheLevelName=CACHE_CONSUMER` if you are using non-XA transactions.
-[[JMS-DurableSubscriptions]]
-Durable Subscriptions
-+++++++++++++++++++++
+#### Durable Subscriptions
If you wish to use durable topic subscriptions, you need to specify both
`clientId` and `durableSubscriptionName`. The value of the `clientId`
@@ -160,9 +148,7 @@ http://activemq.apache.org/virtual-destinations.html[Virtual Topics]
instead to avoid this limitation. More background on durable messaging
http://activemq.apache.org/how-do-durable-queues-and-topics-work.html[here].
-[[JMS-MessageHeaderMapping]]
-Message Header Mapping
-++++++++++++++++++++++
+#### Message Header Mapping
When using message headers, the JMS specification states that header
names must be valid Java identifiers. So try to name your headers to be
@@ -185,9 +171,7 @@ Camel consume the message
* Hyphen is replaced by `_HYPHEN_` and the replacement is reversed when
Camel consumes the message
-[[JMS-Options]]
-Options
-^^^^^^^
+### Options
You can configure many different properties on the JMS endpoint which
map to properties on the
@@ -203,9 +187,7 @@ uses for sending and receiving messages. So you can get more information
about these properties by consulting the relevant Spring documentation.
====
-[[JMS-Componentoptions]]
-Component options
-+++++++++++++++++
+#### Component options
@@ -308,9 +290,7 @@ The JMS component supports 74 options which are listed below.
-[[JMS-Endpointoptions]]
-Endpoint options
-++++++++++++++++
+#### Endpoint options
@@ -425,9 +405,7 @@ The JMS component supports 86 endpoint options which are listed below:
-[[JMS-MessageMappingbetweenJMSandCamel]]
-Message Mapping between JMS and Camel
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Message Mapping between JMS and Camel
Camel automatically maps messages between `javax.jms.Message` and
`org.apache.camel.Message`.
@@ -470,9 +448,7 @@ following body type:
|`javax.jms.ObjectMessage` |`Object`
|=============================================
-[[JMS-Disablingauto-mappingofJMSmessages]]
-Disabling auto-mapping of JMS messages
-++++++++++++++++++++++++++++++++++++++
+#### Disabling auto-mapping of JMS messages
You can use the `mapJmsMessage` option to disable the auto-mapping
above. If disabled, Camel will not try to map the received JMS message,
@@ -481,9 +457,7 @@ the overhead of mapping and let Camel just pass through the JMS message.
For instance, it even allows you to route `javax.jms.ObjectMessage` JMS
messages with classes you do *not* have on the classpath.
-[[JMS-UsingacustomMessageConverter]]
-Using a custom MessageConverter
-+++++++++++++++++++++++++++++++
+#### Using a custom MessageConverter
You can use the `messageConverter` option to do the mapping yourself in
a Spring `org.springframework.jms.support.converter.MessageConverter`
@@ -500,9 +474,7 @@ from("file://inbox/order").to("jms:queue:order?messageConverter=#myMessageConver
You can also use a custom message converter when consuming from a JMS
destination.
-[[JMS-Controllingthemappingstrategyselected]]
-Controlling the mapping strategy selected
-+++++++++++++++++++++++++++++++++++++++++
+#### Controlling the mapping strategy selected
You can use the `jmsMessageType` option on the endpoint URL to force a
specific message type for all messages.
@@ -527,9 +499,7 @@ from("file://inbox/order").setHeader("CamelJmsMessageType", JmsMessageType.Text)
The possible values are defined in the `enum` class,
`org.apache.camel.jms.JmsMessageType`.
-[[JMS-Messageformatwhensending]]
-Message format when sending
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Message format when sending
The exchange that is sent over the JMS wire must conform to the
http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html[JMS Message
@@ -566,9 +536,7 @@ at *DEBUG* level if it drops a given header value. For example:
- Ignoring non primitive header: order of class: org.apache.camel.component.jms.issues.DummyOrder with value: DummyOrder{orderId=333, itemId=4444, quantity=2}
----------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[JMS-Messageformatwhenreceiving]]
-Message format when receiving
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Message format when receiving
Camel adds the following properties to the `Exchange` when it receives a
message:
@@ -614,9 +582,7 @@ As all the above information is standard JMS you can check the
http://java.sun.com/javaee/5/docs/api/javax/jms/Message.html[JMS
documentation] for further details.
-[[JMS-AboutusingCameltosendandreceivemessagesandJMSReplyTo]]
-About using Camel to send and receive messages and JMSReplyTo
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### About using Camel to send and receive messages and JMSReplyTo
The JMS component is complex and you have to pay close attention to how
it works in some cases. So this is a short summary of some of the
@@ -634,9 +600,7 @@ endpoint: `disableReplyTo`, `preserveMessageQos`, `explicitQosEnabled`.
All this can be a tad complex to understand and configure to support
your use case.
-[[JMS-JmsProducer]]
-JmsProducer
-+++++++++++
+#### JmsProducer
The `JmsProducer` behaves as follows, depending on configuration:
@@ -663,9 +627,7 @@ instruct Camel to keep the `JMSReplyTo`. In all situations the
sending the message.
|=======================================================================
-[[JMS-JmsConsumer]]
-JmsConsumer
-+++++++++++
+#### JmsConsumer
The `JmsConsumer` behaves as follows, depending on configuration:
@@ -695,9 +657,7 @@ from("activemq:queue:in")
.to("bean:handleOrder");
------------------------------------------------------
-[[JMS-Reuseendpointandsendtodifferentdestinationscomputedatruntime]]
-Reuse endpoint and send to different destinations computed at runtime
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Reuse endpoint and send to different destinations computed at runtime
If you need to send messages to a lot of different JMS destinations, it
makes sense to reuse a JMS endpoint and specify the real destination in
@@ -751,9 +711,7 @@ them to the created JMS message�in order to avoid the accidental loops
in the routes (in scenarios when the message will be forwarded to the
another JMS endpoint).
-[[JMS-ConfiguringdifferentJMSproviders]]
-Configuring different JMS providers
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring different JMS providers
You can configure your JMS provider in link:spring.html[Spring] XML as
follows:
@@ -774,9 +732,7 @@ spring context for the scheme name you use for
link:endpoint.html[Endpoint] link:uris.html[URIs] and having the
link:component.html[Component] resolve the endpoint URIs.
-[[JMS-UsingJNDItofindtheConnectionFactory]]
-Using JNDI to find the ConnectionFactory
-++++++++++++++++++++++++++++++++++++++++
+#### Using JNDI to find the ConnectionFactory
If you are using a J2EE container, you might need to look up JNDI to
find the JMS `ConnectionFactory` rather than use the usual `<bean>`
@@ -797,9 +753,7 @@ http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html
jee schema] in the Spring reference documentation for more details about
JNDI lookup.
-[[JMS-ConcurrentConsuming]]
-Concurrent Consuming
-^^^^^^^^^^^^^^^^^^^^
+### Concurrent Consuming
A common requirement with JMS is to consume messages concurrently in
multiple threads in order to make an application more responsive. You
@@ -818,9 +772,7 @@ You can configure this option in one of the following ways:
* On the endpoint URI or,
* By invoking `setConcurrentConsumers()` directly on the `JmsEndpoint`.
-[[JMS-ConcurrentConsumingwithasyncconsumer]]
-Concurrent Consuming with async consumer
-++++++++++++++++++++++++++++++++++++++++
+#### Concurrent Consuming with async consumer
Notice that each concurrent consumer will only pickup the next available
message from the JMS broker, when the current message has been fully
@@ -837,9 +789,7 @@ from("jms:SomeQueue?concurrentConsumers=20&asyncConsumer=true").
bean(MyClass.class);
----------------------------------------------------------------
-[[JMS-Request-replyoverJMS]]
-Request-reply over JMS
-^^^^^^^^^^^^^^^^^^^^^^
+### Request-reply over JMS
Camel supports link:request-reply.html[Request Reply] over JMS. In
essence the MEP of the Exchange should be `InOut` when you send a
@@ -945,9 +895,7 @@ from(xxx)
.to(zzz);
-------------------------------------------------------
-[[JMS-Request-replyoverJMSandusingasharedfixedreplyqueue]]
-Request-reply over JMS and using a shared fixed reply queue
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Request-reply over JMS and using a shared fixed reply queue
If you use a fixed reply queue when doing
link:request-reply.html[Request Reply] over JMS as shown in the example
@@ -981,9 +929,7 @@ Notice this will cause the Camel to send pull requests to the message
broker more frequent, and thus require more network traffic. +
It is generally recommended to use temporary queues if possible.
-[[JMS-Request-replyoverJMSandusinganexclusivefixedreplyqueue]]
-Request-reply over JMS and using an exclusive fixed reply queue
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Request-reply over JMS and using an exclusive fixed reply queue
*Available as of Camel 2.9*
@@ -1030,9 +976,7 @@ node in the cluster may pickup messages which was intended as a reply on
another node. For clustered environments its recommended to use shared
reply queues instead.
-[[JMS-Synchronizingclocksbetweensendersandreceivers]]
-Synchronizing clocks between senders and receivers
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Synchronizing clocks between senders and receivers
When doing messaging between systems, its desirable that the systems
have synchronized clocks. For example when sending a link:jms.html[JMS]
@@ -1044,9 +988,7 @@ clocks. If you are using http://activemq.apache.org/[ActiveMQ] then you
can use the http://activemq.apache.org/timestampplugin.html[timestamp
plugin] to synchronize clocks.
-[[JMS-Abouttimetolive]]
-About time to live
-^^^^^^^^^^^^^^^^^^
+### About time to live
Read first above about synchronized clocks.
@@ -1112,9 +1054,7 @@ example to indicate a 5 sec., you set `timeToLive=5000`. The option
also for InOnly messaging. The `requestTimeout` option is not being used
for InOnly messaging.
-[[JMS-EnablingTransactedConsumption]]
-Enabling Transacted Consumption
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling Transacted Consumption
A common requirement is to consume from a queue in a transaction and
then process the message using the Camel route. To do this, just ensure
@@ -1169,9 +1109,7 @@ http://tmielke.blogspot.com/2012/03/camel-jms-with-transactions-lessons.html[her
and
http://forum.springsource.org/showthread.php?123631-JMS-DMLC-not-caching%20connection-when-using-TX-despite-cacheLevel-CACHE_CONSUMER&p=403530&posted=1#post403530[here].
-[[JMS-UsingJMSReplyToforlatereplies]]
-Using JMSReplyTo for late replies
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using JMSReplyTo for late replies
When using Camel as a JMS listener, it sets an Exchange property with
the value of the ReplyTo `javax.jms.Destination` object, having the key
@@ -1210,25 +1148,19 @@ For example:
}
----------------------------------------------------------------------------------------------------------------------------------------
-[[JMS-Usingarequesttimeout]]
-Using a request timeout
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using a request timeout
In the sample below we send a link:request-reply.html[Request Reply]
style message link:exchange.html[Exchange] (we use the `requestBody`
method = `InOut`) to the slow queue for further processing in Camel and
we wait for a return reply:
-[[JMS-Samples]]
-Samples
-^^^^^^^
+### Samples
JMS is used in many examples for other components as well. But we
provide a few samples below to get started.
-[[JMS-ReceivingfromJMS]]
-Receiving from JMS
-++++++++++++++++++
+#### Receiving from JMS
In the following sample we configure a route that receives JMS messages
and routes the message to a POJO:
@@ -1250,9 +1182,7 @@ from("jms:topic:OrdersTopic").
to("jms:queue:BigSpendersQueue");
----------------------------------------------
-[[JMS-SendingtoJMS]]
-Sending to JMS
-++++++++++++++
+#### Sending to JMS
In the sample below we poll a file folder and send the file content to a
JMS topic. As we want the content of the file as a `TextMessage` instead
@@ -1265,16 +1195,12 @@ from("file://orders").
to("jms:topic:OrdersTopic");
------------------------------
-[[JMS-UsingAnnotations]]
-Using link:bean-integration.html[Annotations]
-+++++++++++++++++++++++++++++++++++++++++++++
+#### Using link:bean-integration.html[Annotations]
Camel also has annotations so you can use link:pojo-consuming.html[POJO
Consuming] and link:pojo-producing.html[POJO Producing].
-[[JMS-SpringDSLsample]]
-Spring DSL sample
-+++++++++++++++++
+#### Spring DSL sample
The preceding examples use the Java DSL. Camel also supports Spring XML
DSL. Here is the big spender sample using Spring DSL:
@@ -1290,9 +1216,7 @@ DSL. Here is the big spender sample using Spring DSL:
</route>
---------------------------------------------------
-[[JMS-Othersamples]]
-Other samples
-+++++++++++++
+#### Other samples
JMS appears in many of the examples for other components and EIP
patterns, as well in this Camel documentation. So feel free to browse
@@ -1300,9 +1224,7 @@ the documentation. If you have time, check out the this tutorial that
uses JMS but focuses on how well Spring Remoting and Camel works
together link:tutorial-jmsremoting.html[Tutorial-JmsRemoting].
-[[JMS-UsingJMSasaDeadLetterQueuestoringExchange]]
-Using JMS as a Dead Letter Queue storing Exchange
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using JMS as a Dead Letter Queue storing Exchange
Normally, when using link:jms.html[JMS] as the transport, it only
transfers the body and headers as the payload. If you want to use
@@ -1336,9 +1258,7 @@ Exception cause = exchange.getProperty(Exchange.EXCEPTION_CAUGHT, Exception.clas
String problem = cause.getMessage();
-----------------------------------------------------------------------------------
-[[JMS-UsingJMSasaDeadLetterChannelstoringerroronly]]
-Using JMS as a Dead Letter Channel storing error only
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using JMS as a Dead Letter Channel storing error only
You can use JMS to store the cause error message or to store a custom
body, which you can initialize yourself. The following example uses the
@@ -1360,9 +1280,7 @@ You can, however, use any link:expression.html[Expression] to send
whatever you like. For example, you can invoke a method on a Bean or use
a custom processor.
-[[JMS-SendinganInOnlymessageandkeepingtheJMSReplyToheader]]
-Sending an InOnly message and keeping the JMSReplyTo header
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending an InOnly message and keeping the JMSReplyTo header
When sending to a link:jms.html[JMS] destination using *camel-jms* the
producer will use the MEP to detect if its _InOnly_ or _InOut_ messaging.
@@ -1386,9 +1304,7 @@ For example to send an _InOnly_ message to the foo queue, but with a
Notice we use `preserveMessageQos=true` to instruct Camel to keep the
`JMSReplyTo` header.
-[[JMS-SettingJMSprovideroptionsonthedestination]]
-Setting JMS provider options on the destination
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting JMS provider options on the destination
Some JMS providers, like IBM's WebSphere MQ need options to be set on
the JMS destination. For example, you may need to specify the
@@ -1427,9 +1343,7 @@ wmq.setDestinationResolver(new DestinationResolver() {
});
----------------------------------------------------------------------------------------------------------------------------------
-[[JMS-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -1440,4 +1354,4 @@ See Also
* link:bean-integration.html[Bean Integration]
* link:tutorial-jmsremoting.html[Tutorial-JmsRemoting]
* http://activemq.apache.org/jmstemplate-gotchas.html[JMSTemplate
-gotchas]
+gotchas]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jmx/src/main/docs/jmx-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jmx/src/main/docs/jmx-component.adoc b/components/camel-jmx/src/main/docs/jmx-component.adoc
index 6d1aa8c..df88101 100644
--- a/components/camel-jmx/src/main/docs/jmx-component.adoc
+++ b/components/camel-jmx/src/main/docs/jmx-component.adoc
@@ -1,4 +1,4 @@
-# JMX Component
+## JMX Component
ifdef::env-github[]
:caution-caption: :boom:
:important-caption: :exclamation:
@@ -7,9 +7,7 @@ ifdef::env-github[]
:warning-caption: :warning:
endif::[]
-[[CamelJMX-CamelJMX]]
-Camel JMX
-~~~~~~~~~
+### Camel JMX
Apache Camel has extensive support for JMX to allow you to monitor and
control the Camel managed objects with a JMX client.
@@ -19,9 +17,7 @@ subscribe to MBean notifications. This page is about how to manage and
monitor Camel using JMX.
-[[CamelJMX-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The JMX component has no options.
@@ -68,9 +64,7 @@ The JMX component supports 30 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[CamelJMX-ActivatingJMXinCamel]]
-Activating JMX in Camel
-^^^^^^^^^^^^^^^^^^^^^^^
+### Activating JMX in Camel
[NOTE]
====
@@ -86,9 +80,7 @@ From *Camel 2.9* onwards, the Spring JARs are *no* longer required to
run Camel in JMX mode.
====
-[[CamelJMX-UsingJMXtomanageApacheCamel]]
-Using JMX to manage Apache Camel
-++++++++++++++++++++++++++++++++
+#### Using JMX to manage Apache Camel
By default, JMX instrumentation agent is enabled in Camel, which means
that Camel runtime creates and registers MBean management objects with a
@@ -131,9 +123,7 @@ Spring configuration:
Spring configuration always takes precedence over system properties when
they both present. It is true for all JMX related configurations.
-[[CamelJMX-DisablingJMXinstrumentationagentinCamel]]
-Disabling JMX instrumentation agent in Camel
-++++++++++++++++++++++++++++++++++++++++++++
+#### Disabling JMX instrumentation agent in Camel
You can disable JMX instrumentation agent by setting the Java VM system
property as follow:
@@ -165,9 +155,7 @@ CamelContext camel = new DefaultCamelContext();
camel.disableJMX();
----
-[[CamelJMX-LocatingaMBeanServerintheJavaVM]]
-Locating a MBeanServer in the Java VM
-+++++++++++++++++++++++++++++++++++++
+#### Locating a MBeanServer in the Java VM
Each CamelContext can have an instance of
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/InstrumentationAgent.html[`InstrumentationAgent`]
@@ -235,9 +223,7 @@ Spring configuration:
</camelContext>
----
-[[CamelJMX-CreatingJMXRMIConnectorServer]]
-Creating JMX RMI Connector Server
-+++++++++++++++++++++++++++++++++
+#### Creating JMX RMI Connector Server
JMX connector server enables MBeans to be remotely managed by a JMX
client such as JConsole; Camel JMX RMI connector server can be
@@ -260,9 +246,7 @@ Spring configuration:
</camelContext>
----
-[[CamelJMX-JMXServiceURL]]
-JMX Service URL
-+++++++++++++++
+#### JMX Service URL
The default JMX Service URL has the format:
@@ -357,9 +341,7 @@ When the connector port option is set, the JMX service URL will become:
service:jmx:rmi://localhost:<connectorPort>/jndi/rmi://localhost:<registryPort>/<serviceUrlPath>
----
-[[CamelJMX-TheSystemPropertiesforCamelJMXsupport]]
-The System Properties for Camel JMX support
-+++++++++++++++++++++++++++++++++++++++++++
+#### The System Properties for Camel JMX support
[width="100%",cols="1m,1,3",options="header",]
|=======================================================================
@@ -371,9 +353,7 @@ feature in Camel
See more system properties in this section below: _jmxAgent Properties
Reference_.
-[[CamelJMX-HowtouseauthenticationwithJMX]]
-How to use authentication with JMX
-++++++++++++++++++++++++++++++++++
+#### How to use authentication with JMX
JMX in the JDK have features for authentication and also for using
secure connections over SSL. You have to refer to the SUN documentation
@@ -382,13 +362,9 @@ how to use this:
* http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html
* http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html
-[[CamelJMX-JMXinsideanApplicationServer]]
-JMX inside an Application Server
-++++++++++++++++++++++++++++++++
+#### JMX inside an Application Server
-[[CamelJMX-Tomcat6]]
-Tomcat 6
-++++++++
+#### Tomcat 6
See http://tomcat.apache.org/tomcat-6.0-doc/monitoring.html[this page]
for details about enabling JMX in Tomcat.
@@ -404,9 +380,7 @@ set the following options...
-Dcom.sun.management.jmxremote.authenticate=false
----
-[[CamelJMX-JBossAS4]]
-JBoss AS 4
-++++++++++
+#### JBoss AS 4
By default JBoss creates its own `MBeanServer`. To allow Camel to expose
to the same server follow these steps:
@@ -426,9 +400,7 @@ Add the following property to your `JAVA_OPTS` by editing `run.sh` or
`run.conf` `-Djboss.platform.mbeanserver`. See
http://wiki.jboss.org/wiki/JBossMBeansInJConsole
-[[CamelJMX-WebSphere]]
-WebSphere
-+++++++++
+#### WebSphere
Alter the `mbeanServerDefaultDomain` to be `WebSphere`:
@@ -437,9 +409,7 @@ Alter the `mbeanServerDefaultDomain` to be `WebSphere`:
<camel:jmxAgent id="agent" createConnector="true" mbeanObjectDomainName="org.yourname" usePlatformMBeanServer="false" mbeanServerDefaultDomain="WebSphere"/>
----
-[[CamelJMX-OracleOC4j]]
-Oracle OC4j
-+++++++++++
+#### Oracle OC4j
The Oracle OC4J J2EE application server will not allow Camel to access
the platform `MBeanServer`. You can identify this in the log as Camel
@@ -456,17 +426,13 @@ java.lang.SecurityException: Unauthorized access from application: xx to MBean:
To resolve this you should disable the JMX agent in Camel, see section
_Disabling JMX instrumentation agent in Camel_.
-[[CamelJMX-AdvancedJMXConfiguration]]
-Advanced JMX Configuration
-++++++++++++++++++++++++++
+#### Advanced JMX Configuration
The Spring configuration file allows you to configure how Camel is
exposed to JMX for management. In some cases, you could specify more
information here, like the connector's port or the path name.
-[[CamelJMX-Example:]]
-Example:
-++++++++
+#### Example:
[source,xml]
----
@@ -499,9 +465,7 @@ SUNJMX=-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=1
for Camel, as additional startup parameters for the JVM. If you start
Camel directly, you'll have to pass these parameters yourself.)
-[[CamelJMX-jmxAgentPropertiesReference]]
-`jmxAgent` Properties Reference
-+++++++++++++++++++++++++++++++
+#### `jmxAgent` Properties Reference
[width="100%",cols="25%,25%,25%,25%",options="header",]
|=======================================================================
@@ -567,9 +531,7 @@ usage of each incoming and outgoing endpoints).
|=======================================================================
-[[CamelJMX-ConfiguringwhethertoregisterMBeansalways,fornewroutesorjustbydefault]]
-Configuring whether to register MBeans always, for new routes or just by default
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Configuring whether to register MBeans always, for new routes or just by default
*Available as of Camel 2.7*
@@ -600,13 +562,9 @@ also be registered. This could potential lead to system degration due
the rising number of mbeans in the registry. A MBean is not a
light-weight object and thus consumes memory.
-[[CamelJMX-MonitoringCamelusingJMX]]
-Monitoring Camel using JMX
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Monitoring Camel using JMX
-[[CamelJMX-UsingJConsoletomonitorCamel]]
-Using JConsole to monitor Camel
-+++++++++++++++++++++++++++++++
+#### Using JConsole to monitor Camel
The `CamelContext` should appear in the list of local connections, if
you are running JConsole on the same host as Camel.
@@ -619,9 +577,7 @@ Using the Apache Camel with JConsole:
image:camel-jmx.png[image]
-[[CamelJMX-Whichendpointsareregistered]]
-Which endpoints are registered
-++++++++++++++++++++++++++++++
+#### Which endpoints are registered
In *Camel 2.1* onwards *only* `singleton` endpoints are registered as
the overhead for non singleton will be substantial in cases where
@@ -629,15 +585,11 @@ thousands or millions of endpoints are used. This can happens when using
a link:recipient-list.html[Recipient List] EIP or from a
`ProducerTemplate` that sends a lot of messages.
-[[CamelJMX-Whichprocessorsareregistered]]
-Which processors are registered
-+++++++++++++++++++++++++++++++
+#### Which processors are registered
See link:why-is-my-processor-not-showing-up-in-jconsole.html[this FAQ].
-[[CamelJMX-HowtousetheJMXNotificationListenertolistenthecamelevents]]
-How to use the JMX NotificationListener to listen the camel events?
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### How to use the JMX NotificationListener to listen the camel events?
The Camel notification events give a coarse grained overview what is
happening. You can see lifecycle event from context and endpoints and
@@ -680,9 +632,7 @@ context.getManagementStrategy().getManagementAgent().getMBeanServer().addNotific
}, null);
----
-[[CamelJMX-UsingtheTracerMBeantogetfinegrainedtracing]]
-Using the Tracer MBean to get fine grained tracing
-++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using the Tracer MBean to get fine grained tracing
Additionally to the coarse grained notifications above *Camel 2.9.0*
support JMX Notification for fine grained trace events.
@@ -703,13 +653,9 @@ route with all exchange and message details:
image:jconsole_trace_notifications.png[image]
-[[CamelJMX-UsingJMXforyourownCamelCode]]
-Using JMX for your own Camel Code
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using JMX for your own Camel Code
-[[CamelJMX-RegisteringyourownManagedEndpoints]]
-Registering your own Managed Endpoints
-++++++++++++++++++++++++++++++++++++++
+#### Registering your own Managed Endpoints
*Available as of Camel 2.0* +
You can decorate your own endpoints with Spring managed annotations
@@ -764,9 +710,7 @@ Notice from *Camel 2.9* onwards its encouraged to use the
the `org.apache.camel.api.management` package. This allows your custom
code to not depend on Spring JARs.
-[[CamelJMX-ProgrammingyourownManagedServices]]
-Programming your own Managed Services
-+++++++++++++++++++++++++++++++++++++
+#### Programming your own Managed Services
*Available as of Camel 2.1*
@@ -820,9 +764,7 @@ types such as:
And in the future we will add additional wrappers for more EIP patterns.
-[[CamelJMX-ManagementNamingStrategy]]
-ManagementNamingStrategy
-++++++++++++++++++++++++
+#### ManagementNamingStrategy
*Available as of Camel 2.1*
@@ -831,9 +773,7 @@ Camel provides a pluggable API for naming strategy by
implementation is used to compute the MBean names that all MBeans are
registered with.
-[[CamelJMX-Managementnamingpattern]]
-Management naming pattern
-+++++++++++++++++++++++++
+#### Management naming pattern
*Available as of Camel 2.10*
@@ -975,9 +915,7 @@ install a 2nd Camel application that has the same `CamelContext` id and
`managementNamePattern` then Camel will fail upon starting, and report a
MBean already exists exception.
-[[CamelJMX-ManagementStrategy]]
-ManagementStrategy
-++++++++++++++++++
+#### ManagementStrategy
*Available as of Camel 2.1*
@@ -990,9 +928,7 @@ does, for example, is make it easier to provide an adapter for other
management products. In addition, it also allows you to provide more
details and features that are provided out of the box at Apache.
-[[CamelJMX-Configuringlevelofgranularityforperformancestatistics]]
-Configuring level of granularity for performance statistics
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Configuring level of granularity for performance statistics
*Available as of Camel 2.1*
@@ -1053,9 +989,7 @@ And from Spring DSL you do:
</camelContext>
----
-[[CamelJMX-Hidingsensitiveinformation]]
-Hiding sensitive information
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Hiding sensitive information
*Available as of Camel 2.12*
@@ -1087,9 +1021,7 @@ And from Spring DSL you do:
This will mask link:uris.html[URIs] having options such as password and
passphrase, and use `xxxxxx` as the replacement value.
-[[CamelJMX-DeclaringwhichJMXattributesandoperationstomask]]
-Declaring which JMX attributes and operations to mask
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Declaring which JMX attributes and operations to mask
On the `org.apache.camel.api.management.ManagedAttribute` and
`org.apache.camel.api.management.ManagedOperation`, the attribute `mask`
@@ -1107,10 +1039,8 @@ declared that the `EndpointUri` JMX attribute is masked:
String getEndpointUri();
----
-[[CamelJMX-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:management-example.html[Management Example]
* link:why-is-my-processor-not-showing-up-in-jconsole.html[Why is my
-processor not showing up in JConsole]
+processor not showing up in JConsole]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-johnzon/src/main/docs/json-johnzon-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-johnzon/src/main/docs/json-johnzon-dataformat.adoc b/components/camel-johnzon/src/main/docs/json-johnzon-dataformat.adoc
index 965e573..b10ebef 100644
--- a/components/camel-johnzon/src/main/docs/json-johnzon-dataformat.adoc
+++ b/components/camel-johnzon/src/main/docs/json-johnzon-dataformat.adoc
@@ -1,4 +1,4 @@
-# JSon Johnzon DataFormat
+## JSon Johnzon DataFormat
*Available as of Camel 2.18*
@@ -12,9 +12,7 @@ from("activemq:My.Queue").
to("mqseries:Another.Queue");
-------------------------------
-[[Johnzon-Options]]
-Johnzon Options
-^^^^^^^^^^^^^^^
+### Johnzon Options
@@ -50,9 +48,7 @@ The JSon Johnzon dataformat supports 17 options which are listed below.
-[[Johnzon-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Johnzon in your camel routes you need to add the dependency
on *camel-johnzon* which implements this data format.
@@ -69,4 +65,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-jolt/src/main/docs/jolt-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jolt/src/main/docs/jolt-component.adoc b/components/camel-jolt/src/main/docs/jolt-component.adoc
index ed25e5a..6011851 100644
--- a/components/camel-jolt/src/main/docs/jolt-component.adoc
+++ b/components/camel-jolt/src/main/docs/jolt-component.adoc
@@ -1,4 +1,4 @@
-# JOLT Component
+## JOLT Component
*Available as of Camel 2.16*
@@ -21,9 +21,7 @@ their�`pom.xml`�for this component:
�
-[[JOLT-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------
@@ -37,9 +35,7 @@ invoke; or the complete URL of the remote specification
You can append query options to the URI in the following
format,�`?option=value&option=value&...`
-[[JOLT-Options]]
-Options
-^^^^^^^
+### Options
@@ -82,9 +78,7 @@ The JOLT component supports 6 endpoint options which are listed below:
-[[JOLT-Samples]]
-Samples
-^^^^^^^
+### Samples
For example you could use something like
@@ -115,12 +109,9 @@ from("direct:in").
�
-[[JOLT-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-josql/src/main/docs/sql-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-josql/src/main/docs/sql-language.adoc b/components/camel-josql/src/main/docs/sql-language.adoc
index 7038d5f..502897f 100644
--- a/components/camel-josql/src/main/docs/sql-language.adoc
+++ b/components/camel-josql/src/main/docs/sql-language.adoc
@@ -1,4 +1,4 @@
-# SQL Language
+## SQL Language
The SQL support is added by http://josql.sourceforge.net/[JoSQL] and is
primarily used for performing SQL queries on in-memory objects. If you
@@ -53,9 +53,7 @@ And the spring DSL:
<to uri="queue:bar"/>
--------------------------------------
-[[SQL-Options]]
-Options
-^^^^^^^
+### Options
// language options: START
@@ -73,9 +71,7 @@ The SQL language supports 1 options which are listed below.
// language options: END
-[[SQL-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -87,4 +83,4 @@ eg to refer to a file on the classpath you can do:
[source,java]
----------------------------------------------------------
.setHeader("myHeader").sql("resource:classpath:mysql.sql")
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jpa/src/main/docs/jpa-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jpa/src/main/docs/jpa-component.adoc b/components/camel-jpa/src/main/docs/jpa-component.adoc
index e79d410..c8af852 100644
--- a/components/camel-jpa/src/main/docs/jpa-component.adoc
+++ b/components/camel-jpa/src/main/docs/jpa-component.adoc
@@ -1,4 +1,4 @@
-# JPA Component
+## JPA Component
The *jpa* component enables you to store and retrieve Java objects from
persistent storage using EJB 3's Java Persistence Architecture (JPA),
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[JPA-Sendingtotheendpoint]]
-Sending to the endpoint
-^^^^^^^^^^^^^^^^^^^^^^^
+### Sending to the endpoint
You can store a Java entity bean in a database by sending it to a JPA
producer endpoint. The body of the _In_ message is assumed to be an
@@ -36,9 +34,7 @@ If the body does not contain one of the previous listed types, put a
link:message-translator.html[Message Translator] in front of the
endpoint to perform the necessary conversion first.
-[[JPA-Consumingfromtheendpoint]]
-Consuming from the endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Consuming from the endpoint
Consuming messages from a JPA consumer endpoint removes (or updates)
entity beans in the database. This allows you to use a database table as
@@ -64,9 +60,7 @@ which will be invoked on your entity bean before it has been processed
If you are consuming a lot (100K+) of rows and experience OutOfMemory
problems you should set the maximumResults to sensible value.
-[[JPA-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------------
@@ -82,9 +76,7 @@ For consuming, the _entityClassName_ is mandatory.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[JPA-Options]]
-Options
-^^^^^^^
+### Options
@@ -170,9 +162,7 @@ The JPA component supports 42 endpoint options which are listed below:
-[[JPA-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Camel adds the following message headers to the exchange:
@@ -192,9 +182,7 @@ reason why the support for this header has been dropped.
|=======================================================================
-[[JPA-ConfiguringEntityManagerFactory]]
-Configuring EntityManagerFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring EntityManagerFactory
Its strongly advised to configure the JPA component to use a specific
`EntityManagerFactory` instance. If failed to do so each `JpaEndpoint`
@@ -217,9 +205,7 @@ you do not need to configure this on the `JpaComponent` as shown above.
You only need to do so if there is ambiguity, in which case Camel will
log a WARN.
-[[JPA-ConfiguringTransactionManager]]
-Configuring TransactionManager
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring TransactionManager
Since *Camel 2.3* the `JpaComponent` will auto lookup the
`TransactionManager` from the link:registry.html[Registry.] If Camel
@@ -244,9 +230,7 @@ explicitly configure a JPA component that references the
</bean>
-------------------------------------------------------------------
-[[JPA-Usingaconsumerwithanamedquery]]
-Using a consumer with a named query
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using a consumer with a named query
For consuming only selected entities, you can use the
`consumer.namedQuery` URI query option. First, you have to define the
@@ -269,9 +253,7 @@ from("jpa://org.apache.camel.examples.MultiSteps?consumer.namedQuery=step1")
.to("bean:myBusinessLogic");
----------------------------------------------------------------------------
-[[JPA-Usingaconsumerwithaquery]]
-Using a consumer with a query
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using a consumer with a query
For consuming only selected entities, you can use the `consumer.query`
URI query option. You only have to define the query option:
@@ -282,9 +264,7 @@ from("jpa://org.apache.camel.examples.MultiSteps?consumer.query=select o from or
.to("bean:myBusinessLogic");
---------------------------------------------------------------------------------------------------------------------------------------
-[[JPA-Usingaconsumerwithanativequery]]
-Using a consumer with a native query
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using a consumer with a native query
For consuming only selected entities, you can use the
`consumer.nativeQuery` URI query option. You only have to define the
@@ -299,16 +279,12 @@ from("jpa://org.apache.camel.examples.MultiSteps?consumer.nativeQuery=select * f
If you use the native query option, you will receive an object array in
the message body.
-[[JPA-Example]]
-Example
-^^^^^^^
+### Example
See link:tracer-example.html[Tracer Example] for an example using
link:jpa.html[JPA] to store traced messages into a database.
-[[JPA-UsingtheJPAbasedidempotentrepository]]
-Using the JPA based idempotent repository
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the JPA based idempotent repository
In this section we will use the JPA based idempotent repository.
@@ -380,14 +356,11 @@ argument to the JVM:
Then it will all become green again
image:https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png[(smile)]
-[[JPA-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:tracer-example.html[Tracer Example]
-
+* link:tracer-example.html[Tracer Example]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jsch/src/main/docs/scp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jsch/src/main/docs/scp-component.adoc b/components/camel-jsch/src/main/docs/scp-component.adoc
index c92cbf5..3d4b6c0 100644
--- a/components/camel-jsch/src/main/docs/scp-component.adoc
+++ b/components/camel-jsch/src/main/docs/scp-component.adoc
@@ -1,4 +1,4 @@
-# SCP Component
+## SCP Component
The *camel-jsch* component supports the
http://en.wikipedia.org/wiki/Secure_copy[SCP protocol] using the Client
@@ -19,9 +19,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Jsch-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------
@@ -35,9 +33,7 @@ The file name can be specified either in the <path> part of the URI or
as a "CamelFileName" header on the message (`Exchange.FILE_NAME` if used
in code).
-[[Jsch-Options]]
-Options
-^^^^^^^
+### Options
@@ -102,20 +98,15 @@ The SCP component supports 22 endpoint options which are listed below:
-[[Jsch-Limitations]]
-Limitations
-^^^^^^^^^^^
+### Limitations
Currently camel-jsch only supports a
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Producer.html[Producer]
(i.e. copy files to another host).�
-[[Jsch-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-jsonpath/src/main/docs/jsonpath-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc b/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
index 766cec4..57f6fec 100644
--- a/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
+++ b/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
@@ -1,4 +1,4 @@
-# JSonPath Language
+## JSonPath Language
*Available as of Camel 2.13*
@@ -18,9 +18,7 @@ from("queue:books.new")
.to("jms:queue:book.expensive")
-----------------------------------------------------
-[[JSonPath-Options]]
-JSonPath Options
-^^^^^^^^^^^^^^^^
+### JSonPath Options
// language options: START
@@ -42,9 +40,7 @@ The JSonPath language supports 4 options which are listed below.
-[[JSonPath-UsingXMLconfiguration]]
-Using XML configuration
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using XML configuration
If you prefer to configure your routes in your link:spring.html[Spring]
XML file then you can use link:jsonpath.html[JSonPath] expressions as
@@ -72,16 +68,12 @@ follows
</camelContext>
-------------------------------------------------------------------------
-[[JSonPath-Syntax]]
-Syntax
-^^^^^^
+### Syntax
See the https://code.google.com/p/json-path/[JSonPath] project page for
further examples.
-[[JSonPath-SupportedType]]
-Supported message body types
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Supported message body types
Camel JSonPath supports message body using the following types:
@@ -104,9 +96,7 @@ If a message body is of unsupported type then an exception is thrown by default,
can configure JSonPath to suppress exceptions (see below)
-[[JSonPath-Suppressexceptions]]
-Suppress exceptions
-~~~~~~~~~~~~~~~~~~~
+### Suppress exceptions
*Available as of Camel 2.16*
@@ -149,9 +139,7 @@ And in XML DSL:
This option is also available on the�`@JsonPath`�annotation.
-[[JSonPath-InlineSimple]]
-Inline Simple exceptions
-~~~~~~~~~~~~~~~~~~~~~~~~
+### Inline Simple exceptions
*Available as of Camel 2.18*
@@ -207,9 +195,7 @@ And in XML DSL:
--------------------------------------------------------------------------
-[[JSonPath-JSonPathinjection]]
-JSonPath injection
-~~~~~~~~~~~~~~~~~~
+### JSonPath injection
You can use link:bean-integration.html[Bean Integration] to invoke a
method on a bean and use various languages such as JSonPath to extract a
@@ -228,9 +214,7 @@ public class Foo {
}
---------------------------------------------------------------------------------------------------
-[[JSonPath-EncodingDetection]]
-Encoding Detection
-~~~~~~~~~~~~~~~~~~
+### Encoding Detection
*Since Camel version 2.16*, the encoding of the JSON document is
detected automatically, if the document is encoded in unicode �(UTF-8,
@@ -240,9 +224,7 @@ you enter the document in String format to the JSONPath component or you
can specify the encoding in the header�"*CamelJsonPathJsonEncoding*"
(JsonpathConstants.HEADER_JSON_ENCODING).
-[[JSonPath-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use JSonPath in your camel routes you need to add the a dependency on
*camel-jsonpath* which implements the JSonPath language.
@@ -258,4 +240,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-jsonpath</artifactId>
<version>x.x.x</version>
</dependency>
------------------------------------------
+-----------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jt400/src/main/docs/jt400-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jt400/src/main/docs/jt400-component.adoc b/components/camel-jt400/src/main/docs/jt400-component.adoc
index 1f0720c..84150ef 100644
--- a/components/camel-jt400/src/main/docs/jt400-component.adoc
+++ b/components/camel-jt400/src/main/docs/jt400-component.adoc
@@ -1,4 +1,4 @@
-# JT400 Component
+## JT400 Component
The *`jt400`* component allows you to exchanges messages with an AS/400
system using data queues.
@@ -16,9 +16,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[JT400-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------------------------------------------------
@@ -35,9 +33,7 @@ jt400://user:password@system/QSYS.LIB/LIBRARY.LIB/program.PGM[?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[JT400-options]]
-JT400 options
-^^^^^^^^^^^^^
+### JT400 options
// component options: START
The JT400 component supports 1 options which are listed below.
@@ -100,9 +96,7 @@ The JT400 component supports 34 endpoint options which are listed below:
// endpoint options: END
-[[JT400-Usage]]
-Usage
-^^^^^
+### Usage
When configured as a consumer endpoint, the endpoint will poll a data
queue on a remote system. For every entry on the data queue, a new
@@ -111,9 +105,7 @@ formatted either as a `String` or a `byte[]`, depending on the format.
For a provider endpoint, the _In_ message body contents will be put on
the data queue as either raw bytes or text.
-[[JT400-Connectionpool]]
-Connection pool
-^^^^^^^^^^^^^^^
+### Connection pool
*Available as of Camel 2.10*
@@ -121,9 +113,7 @@ Connection pooling is in use from Camel 2.10 onwards. You can explicit
configure a connection pool on the Jt400Component, or as an uri option
on the endpoint.
-[[JT400-Remoteprogramcall]]
-Remote program call (*Camel 2.7*)
-+++++++++++++++++++++++++++++++++
+#### Remote program call (*Camel 2.7*)
This endpoint expects the input to be either a String array or byte[]
array (depending on format) and handles all the CCSID handling through
@@ -134,9 +124,7 @@ String array or byte[] array with the values as they were returned by
the program (the input only parameters will contain the same data as the
beginning of the invocation). This endpoint does not implement a provider endpoint!
-[[JT400-Example]]
-Example
-^^^^^^^
+### Example
In the snippet below, the data for an exchange sent to the
`direct:george` endpoint will be put in the data queue `PENNYLANE` in
@@ -155,9 +143,7 @@ public class Jt400RouteBuilder extends RouteBuilder {
}
-------------------------------------------------------------------------------------------------------
-[[JT400-Remoteprogramcallexample]]
-Remote program call example (*Camel 2.7*)
-+++++++++++++++++++++++++++++++++++++++++
+#### Remote program call example (*Camel 2.7*)
In the snippet below, the data Exchange sent to the direct:work endpoint
will contain three string that will be used as the arguments for the
@@ -175,9 +161,7 @@ public class Jt400RouteBuilder extends RouteBuilder {
}
---------------------------------------------------------------------------------------------------------------------------------------------------------
-[[JT400-Writingtokeyeddataqueues]]
-Writing to keyed data queues
-++++++++++++++++++++++++++++
+#### Writing to keyed data queues
[source,java]
------------------------------------------------------------------------
@@ -185,9 +169,7 @@ from("jms:queue:input")
.to("jt400://username:password@system/lib.lib/MSGINDQ.DTAQ?keyed=true");
------------------------------------------------------------------------
-[[JT400-Readingfromkeyeddataqueues]]
-Reading from keyed data queues
-++++++++++++++++++++++++++++++
+#### Reading from keyed data queues
[source,java]
-------------------------------------------------------------------------------------------------------
@@ -195,12 +177,9 @@ from("jt400://username:password@system/lib.lib/MSGOUTDQ.DTAQ?keyed=true&searchKe
.to("jms:queue:output");
-------------------------------------------------------------------------------------------------------
-[[JT400-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-juel/src/main/docs/el-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-juel/src/main/docs/el-language.adoc b/components/camel-juel/src/main/docs/el-language.adoc
index 440d2a3..10a0679 100644
--- a/components/camel-juel/src/main/docs/el-language.adoc
+++ b/components/camel-juel/src/main/docs/el-language.adoc
@@ -1,4 +1,4 @@
-# EL Language
+## EL Language
[[EL-EL]]
EL
~~
@@ -42,9 +42,7 @@ link:message-filter.html[Message Filter] or as an
link:expression.html[Expression] for a
link:recipient-list.html[Recipient List]
-[[EL-Options]]
-EL Options
-^^^^^^^^^^
+### EL Options
@@ -64,9 +62,7 @@ The EL language supports 1 options which are listed below.
-[[EL-Variables]]
-Variables
-^^^^^^^^^
+### Variables
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -79,9 +75,7 @@ Variables
|out |Message |the exchange.out message
|=======================================================================
-[[EL-Samples]]
-Samples
-^^^^^^^
+### Samples
You can use EL dot notation to invoke operations. If you for instance
have a body that contains a POJO that has a `getFamiliyName` method then
@@ -92,9 +86,7 @@ you can construct the syntax as follows:
"${in.body.familyName}"
-----------------------
-[[EL-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use EL in your camel routes you need to add the a dependency on
*camel-juel* which implements the EL language.
@@ -113,4 +105,4 @@ link:download.html[the download page for the latest versions]).
-------------------------------------
Otherwise you'll also need to include
-http://repo2.maven.org/maven2/de/odysseus/juel/juel/2.1.3/juel-2.1.3.jar[JUEL].
+http://repo2.maven.org/maven2/de/odysseus/juel/juel/2.1.3/juel-2.1.3.jar[JUEL].
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jxpath/src/main/docs/jxpath-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jxpath/src/main/docs/jxpath-language.adoc b/components/camel-jxpath/src/main/docs/jxpath-language.adoc
index 3d6f0d8..de69ead 100644
--- a/components/camel-jxpath/src/main/docs/jxpath-language.adoc
+++ b/components/camel-jxpath/src/main/docs/jxpath-language.adoc
@@ -1,4 +1,4 @@
-# JXPath Language
+## JXPath Language
Camel supports http://commons.apache.org/jxpath/[JXPath] to allow
link:xpath.html[XPath] expressions to be used on beans in an
@@ -19,9 +19,7 @@ from("queue:foo").filter().
to("queue:bar")
---------------------------
-[[JXPath-Options]]
-JXPath Options
-^^^^^^^^^^^^^^
+### JXPath Options
// language options: START
@@ -41,9 +39,7 @@ The JXPath language supports 2 options which are listed below.
-[[JXPath-Variables]]
-Variables
-^^^^^^^^^
+### Variables
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -56,9 +52,7 @@ Variables
|out |Message |the exchange.out message
|=======================================================================
-[[JXPath-Options]]
-Options
-^^^^^^^
+### Options
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -72,9 +66,7 @@ http://commons.apache.org/proper/commons-jxpath//users-guide.html#Lenient_Mode[J
Documentation] This option is by default false.
|=======================================================================
-[[JXPath-UsingXMLconfiguration]]
-Using XML configuration
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using XML configuration
If you prefer to configure your routes in your link:spring.html[Spring]
XML file then you can use JXPath expressions as follows
@@ -99,18 +91,14 @@ XML file then you can use JXPath expressions as follows
</beans>
---------------------------------------------------------------------------------------------------------------
-[[JXPath-Examples]]
-Examples
-^^^^^^^^
+### Examples
Here is a simple
http://svn.apache.org/repos/asf/camel/trunk/components/camel-jxpath/src/test/java/org/apache/camel/language/jxpath/JXPathFilterTest.java[example]
using a JXPath expression as a predicate in a
link:message-filter.html[Message Filter]
-[[JXPath-JXPathinjection]]
-JXPath injection
-~~~~~~~~~~~~~~~~
+### JXPath injection
You can use link:bean-integration.html[Bean Integration] to invoke a
method on a bean and use various languages such as JXPath to extract a
@@ -129,9 +117,7 @@ public class Foo {
}
---------------------------------------------------------------------------------------------
-[[JXPath-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -145,9 +131,7 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").jxpath("resource:classpath:myjxpath.txt")
----------------------------------------------------------------
-[[JXPath-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use JXpath in your camel routes you need to add the a dependency on
*camel-jxpath* which implements the JXpath language.
@@ -167,4 +151,4 @@ link:download.html[the download page for the latest versions]).
Otherwise, you'll also need
http://repo2.maven.org/maven2/commons-jxpath/commons-jxpath/1.3/commons-jxpath-1.3.jar[Commons
-JXPath].
+JXPath].
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-kafka/src/main/docs/kafka-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-kafka/src/main/docs/kafka-component.adoc b/components/camel-kafka/src/main/docs/kafka-component.adoc
index 1700c0e..79b7c50 100644
--- a/components/camel-kafka/src/main/docs/kafka-component.adoc
+++ b/components/camel-kafka/src/main/docs/kafka-component.adoc
@@ -1,4 +1,4 @@
-# Kafka Component
+## Kafka Component
*Available as of Camel 2.13*
@@ -18,15 +18,11 @@ for this component.
</dependency>
------------------------------------------------------------
-[[Kafka-Camel2.17ornewer]]
-Camel 2.17 or newer
-+++++++++++++++++++
+#### Camel 2.17 or newer
Scala is no longer used, as we use the kafka java client.
-[[Kafka-Camel2.16orolder]]
-Camel 2.16 or older
-+++++++++++++++++++
+#### Camel 2.16 or older
And then the Scala libraries of choice. camel-kafka does not include
that dependency, but assumes it is provided. For example to use Scala
@@ -41,9 +37,7 @@ that dependency, but assumes it is provided. For example to use Scala
</dependency>
--------------------------------------------
-[[Kafka-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------
@@ -52,9 +46,7 @@ kafka:server:port[?options]
�
-[[Kafka-Options]]
-Options (Camel 2.16 or older)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Options (Camel 2.16 or older)
@@ -203,13 +195,9 @@ For more information about Producer/Consumer configuration:
http://kafka.apache.org/documentation.html#newconsumerconfigs[http://kafka.apache.org/documentation.html#newconsumerconfigs]
http://kafka.apache.org/documentation.html#producerconfigs[http://kafka.apache.org/documentation.html#producerconfigs]
-[[Kafka-Samples]]
-Samples
-^^^^^^^
+### Samples
-[[Kafka-Camel2.16orolder.1]]
-Camel 2.16 or older
-+++++++++++++++++++
+#### Camel 2.16 or older
Consuming messages:
@@ -222,9 +210,7 @@ Producing messages:
See unit tests of camel-kafka for more examples
-[[Kafka-Camel2.17ornewer]]
-Camel 2.17 or newer
-+++++++++++++++++++
+#### Camel 2.17 or newer
Consuming messages:
@@ -276,9 +262,7 @@ from("direct:start").process(new Processor() {
�
-[[Kafka-Endpoints]]
-Endpoints
-~~~~~~~~~
+### Endpoints
Camel supports the link:message-endpoint.html[Message Endpoint] pattern
using the
@@ -306,12 +290,9 @@ implements the link:polling-consumer.html[Polling Consumer] pattern for
consuming message exchanges from the endpoint via a
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/PollingConsumer.html[PollingConsumer]
-[[Kafka-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:message-endpoint.html[Message Endpoint] pattern
* link:uris.html[URIs]
-* link:writing-components.html[Writing Components]
-
+* link:writing-components.html[Writing Components]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-kestrel/src/main/docs/kestrel-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-kestrel/src/main/docs/kestrel-component.adoc b/components/camel-kestrel/src/main/docs/kestrel-component.adoc
index ba8d963..025a475 100644
--- a/components/camel-kestrel/src/main/docs/kestrel-component.adoc
+++ b/components/camel-kestrel/src/main/docs/kestrel-component.adoc
@@ -1,4 +1,4 @@
-# Kestrel Component
+## Kestrel Component
The Kestrel component allows messages to be sent to a
https://github.com/robey/kestrel[Kestrel] queue, or messages to be
@@ -10,9 +10,7 @@ WARNING: The kestrel project is inactive and the Camel team regard this
components as deprecated.
-[[Kestrel-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------------------
@@ -59,9 +57,7 @@ concurrently from a queue:
kestrel://kserver03:22133/massive?concurrentConsumers=25&waitTimeMs=500
-----------------------------------------------------------------------
-[[Kestrel-Options]]
-Options
-^^^^^^^
+### Options
@@ -108,9 +104,7 @@ The Kestrel component supports 8 endpoint options which are listed below:
-[[Kestrel-ConfiguringtheKestrelcomponentusingSpringXML]]
-Configuring the Kestrel component using Spring XML
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring the Kestrel component using Spring XML
The simplest form of explicit configuration is as follows:
@@ -162,13 +156,9 @@ can set up a KestrelConfiguration POJO as follows:
</beans>
---------------------------------------------------------------------------------------------------------------
-[[Kestrel-UsageExamples]]
-Usage Examples
-^^^^^^^^^^^^^^
+### Usage Examples
-[[Kestrel-Example1:Consuming]]
-Example 1: Consuming
-++++++++++++++++++++
+#### Example 1: Consuming
[source,java]
-------------------------------------------------------------------------------
@@ -185,9 +175,7 @@ public class MyConsumer {
}
-------------------------------------------
-[[Kestrel-Example2:Producing]]
-Example 2: Producing
-++++++++++++++++++++
+#### Example 2: Producing
[source,java]
------------------------------------------------------------------------------
@@ -201,9 +189,7 @@ public class MyProducer {
}
------------------------------------------------------------------------------
-[[Kestrel-Example3:SpringXMLConfiguration]]
-Example 3: Spring XML Configuration
-+++++++++++++++++++++++++++++++++++
+#### Example 3: Spring XML Configuration
[source,xml]
----------------------------------------------------------------------------------------
@@ -228,17 +214,13 @@ public class MyBean {
}
-------------------------------------------
-[[Kestrel-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
The Kestrel component has the following dependencies:
* `spymemcached` 2.5 (or greater)
-[[Kestrel-spymemcached]]
-spymemcached
-++++++++++++
+#### spymemcached
You *must* have the `spymemcached` jar on your classpath. Here is a
snippet you can use in your pom.xml:
@@ -273,12 +255,9 @@ you may need to set `enableAssertions` to `false`. Please refer to the
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html[surefire:test
reference] for details.
-[[Kestrel-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-krati/src/main/docs/krati-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-krati/src/main/docs/krati-component.adoc b/components/camel-krati/src/main/docs/krati-component.adoc
index 996356e..0268736 100644
--- a/components/camel-krati/src/main/docs/krati-component.adoc
+++ b/components/camel-krati/src/main/docs/krati-component.adoc
@@ -1,4 +1,4 @@
-# Krati Component
+## Krati Component
*Available as of Camel 2.9*
@@ -25,9 +25,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Krati-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------------------
@@ -40,9 +38,7 @@ krati will use for its datastore.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Krati-KratiOptions]]
-Krati Options
-^^^^^^^^^^^^^
+### Krati Options
// component options: START
@@ -107,9 +103,7 @@ krati:/tmp/krati?operation=CamelKratiGet&initialCapacity=10000&keySerializer=#my
For producer endpoint you can override all of the above URI options by
passing the appropriate headers to the message.
-[[Krati-MessageHeadersfordatastore]]
-Message Headers for datastore
-+++++++++++++++++++++++++++++
+#### Message Headers for datastore
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -123,13 +117,9 @@ CamelKratiDelete, CamelKratiDeleteAll
|`CamelKratiValue` |The value.
|=======================================================================
-[[Krati-UsageSamples]]
-Usage Samples
-^^^^^^^^^^^^^
+### Usage Samples
-[[Krati-Example1:Puttingtothedatastore.]]
-Example 1: Putting to the datastore.
-++++++++++++++++++++++++++++++++++++
+#### Example 1: Putting to the datastore.
This example will show you how you can store any message inside a
datastore.
@@ -152,9 +142,7 @@ route.
</route>
------------------------------------------------------------
-[[Krati-Example2:GettingReadingfromadatastore]]
-Example 2: Getting/Reading from a datastore
-+++++++++++++++++++++++++++++++++++++++++++
+#### Example 2: Getting/Reading from a datastore
This example will show you how you can read the contnet of a datastore.
@@ -178,9 +166,7 @@ route.
</route>
-----------------------------------------------------------------------------
-[[Krati-Example3:Consumingfromadatastore]]
-Example 3: Consuming from a datastore
-+++++++++++++++++++++++++++++++++++++
+#### Example 3: Consuming from a datastore
This example will consume all items that are under the specified
datastore.
@@ -201,9 +187,7 @@ You can achieve the same goal by using xml, as you can see below.
</route>
------------------------------------------------------
-[[Krati-IdempotentRepository]]
-Idempotent Repository
-^^^^^^^^^^^^^^^^^^^^^
+### Idempotent Repository
As already mentioned this component also offers and idemptonet
repository which can be used for filtering out duplicate messages.
@@ -213,8 +197,6 @@ repository which can be used for filtering out duplicate messages.
from("direct://in").idempotentConsumer(header("messageId"), new KratiIdempotentRepositroy("/tmp/idempotent").to("log://out");
-----------------------------------------------------------------------------------------------------------------------------
-[[Krati-Seealso]]
-See also
-++++++++
+#### See also
-http://sna-projects.com/krati/[Krati Website]
+http://sna-projects.com/krati/[Krati Website]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-kubernetes/src/main/docs/kubernetes-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-component.adoc
index 4978059..f7d30b7 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-component.adoc
@@ -1,4 +1,4 @@
-# Kubernetes Component
+## Kubernetes Component
*Available as of Camel 2.17*
@@ -18,9 +18,7 @@ their�`pom.xml`�for this component:
</dependency>
------------------------------------------------------------
-[[Kubernetes-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------
@@ -30,9 +28,7 @@ kubernetes:masterUrl[?options]
You can append query options to the URI in the following
format,�`?option=value&option=value&...`
-[[Kubernetes-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -91,9 +87,7 @@ The Kubernetes component supports 28 endpoint options which are listed below:
-[[Kubernetes-Headers]]
-Headers
-^^^^^^^
+### Headers
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -174,4 +168,4 @@ Headers
|CamelKubernetesConfigMapsLabels |Map |ConfigMap labels
|CamelKubernetesConfigData |Map |ConfigMap Data
-|=======================================================================
+|=======================================================================
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ldap/src/main/docs/ldap-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ldap/src/main/docs/ldap-component.adoc b/components/camel-ldap/src/main/docs/ldap-component.adoc
index 2489e78..b711cea 100644
--- a/components/camel-ldap/src/main/docs/ldap-component.adoc
+++ b/components/camel-ldap/src/main/docs/ldap-component.adoc
@@ -1,4 +1,4 @@
-# LDAP Component
+## LDAP Component
The *ldap* component allows you to perform searches in LDAP servers
using filters as the message payload. +
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[LDAP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------------
@@ -36,9 +34,7 @@ the start of a route.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[LDAP-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -67,16 +63,12 @@ The LDAP component supports 6 endpoint options which are listed below:
-[[LDAP-Result]]
-Result
-^^^^^^
+### Result
The result is returned in the Out body as a
`ArrayList<javax.naming.directory.SearchResult>` object.
-[[LDAP-DirContext]]
-DirContext
-^^^^^^^^^^
+### DirContext
The URI, `ldap:ldapserver`, references a Spring bean with the ID,
`ldapserver`. The `ldapserver` bean may be defined as follows:
@@ -104,9 +96,7 @@ or that the context supports concurrency. In the Spring framework,
`prototype` scoped objects are instantiated each time they are looked
up.
-[[LDAP-Samples]]
-Samples
-^^^^^^^
+### Samples
Following on from the Spring configuration above, the code sample below
sends an LDAP request to filter search a group for a member. The Common
@@ -145,9 +135,7 @@ if the LDAP entry has a Common Name, use a filter expression like:
(cn=*)
------
-[[LDAP-Bindingusingcredentials]]
-Binding using credentials
-+++++++++++++++++++++++++
+#### Binding using credentials
A Camel end user donated this sample code he used to bind to the ldap
server using credentials.
@@ -192,9 +180,7 @@ System.out.println(out.getOut().getBody());
context.stop();
---------------------------------------------------------------------------------------
-[[LDAP-ConfiguringSSL]]
-Configuring SSL
-^^^^^^^^^^^^^^^
+### Configuring SSL
All required is to create a custom socket factory and reference it in
the InitialDirContext bean - see below sample.
@@ -335,12 +321,9 @@ public class CustomSocketFactory extends SSLSocketFactory {
�
-[[LDAP-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-linkedin/camel-linkedin-component/src/main/docs/linkedin-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-linkedin/camel-linkedin-component/src/main/docs/linkedin-component.adoc b/components/camel-linkedin/camel-linkedin-component/src/main/docs/linkedin-component.adoc
index fa81b62..ca5c9dc 100644
--- a/components/camel-linkedin/camel-linkedin-component/src/main/docs/linkedin-component.adoc
+++ b/components/camel-linkedin/camel-linkedin-component/src/main/docs/linkedin-component.adoc
@@ -1,4 +1,4 @@
-# Linkedin Component
+## Linkedin Component
*Available as of Camel 2.14*
@@ -29,9 +29,7 @@ for this component:
</dependency>
-----------------------------------------------
-[[LinkedIn-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------------------------
@@ -48,9 +46,7 @@ Endpoint prefix can be one of:
* posts
* search
-[[LinkedIn-LinkedInComponent.1]]
-LinkedInComponent
-^^^^^^^^^^^^^^^^^
+### LinkedInComponent
@@ -101,9 +97,7 @@ The Linkedin component supports 16 endpoint options which are listed below:
// endpoint options: END
-[[LinkedIn-ProducerEndpoints:]]
-Producer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Producer Endpoints:
Producer endpoints can use endpoint prefixes followed by endpoint names
and associated options described next. A shorthand alias can be used for
@@ -125,9 +119,7 @@ For more information on the endpoints and options see LinkedIn REST API
documentation
at�https://developer.linkedin.com/rest[https://developer.linkedin.com/rest].�
-[[LinkedIn-Endpointprefixcomments]]
-Endpoint prefix�_comments_
-++++++++++++++++++++++++++
+#### Endpoint prefix�_comments_
The following endpoints can be invoked with the prefix�*comments*�as
follows:
@@ -158,9 +150,7 @@ URI Options for�_comments_
|fields |String
|=======================================================================
-[[LinkedIn-Endpointprefixcompanies]]
-Endpoint prefix�_companies_
-+++++++++++++++++++++++++++
+#### Endpoint prefix�_companies_
The following endpoints can be invoked with the prefix�*companies*�as
follows:
@@ -265,9 +255,7 @@ matching endpoints.
|updatecomment |org.apache.camel.component.linkedin.api.model.UpdateComment
|=======================================================================
-[[LinkedIn-Endpointprefixgroups]]
-Endpoint prefix�_groups_
-++++++++++++++++++++++++
+#### Endpoint prefix�_groups_
The following endpoints can be invoked with the prefix�*groups*�as
follows:
@@ -298,9 +286,7 @@ URI Options for�_groups_
|post |org.apache.camel.component.linkedin.api.model.Post
|=======================================================================
-[[LinkedIn-Endpointprefixjobs]]
-Endpoint prefix�_jobs_
-++++++++++++++++++++++
+#### Endpoint prefix�_jobs_
The following endpoints can be invoked with the prefix�*jobs*�as
follows:
@@ -339,9 +325,7 @@ URI Options for�_jobs_
|partner_job_id |Long
|=======================================================================
-[[LinkedIn-Endpointprefixpeople]]
-Endpoint prefix�_people_
-++++++++++++++++++++++++
+#### Endpoint prefix�_people_
The following endpoints can be invoked with the prefix�*people*�as
follows:
@@ -495,9 +479,7 @@ if other options do not satisfy matching endpoints.
|updatecomment |org.apache.camel.component.linkedin.api.model.UpdateComment
|=======================================================================
-[[LinkedIn-Endpointprefixposts]]
-Endpoint prefix�_posts_
-+++++++++++++++++++++++
+#### Endpoint prefix�_posts_
The following endpoints can be invoked with the prefix�*posts*�as
follows:
@@ -555,9 +537,7 @@ options do not satisfy matching endpoints.
|start |Long
|=======================================================================
-[[LinkedIn-Endpointprefixsearch]]
-Endpoint prefix�_search_
-++++++++++++++++++++++++
+#### Endpoint prefix�_search_
The following endpoints can be invoked with the prefix�*search*�as
follows:
@@ -637,9 +617,7 @@ satisfy matching endpoints.
|title |String
|=======================================================================
-[[LinkedIn-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
Any of the producer endpoints can be used as a consumer endpoint.
Consumer endpoints can
@@ -651,25 +629,19 @@ be executed once for each exchange. To change this behavior use the
property *consumer.splitResults=true* to return a single exchange for
the entire list or array.�
-[[LinkedIn-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Any URI option can be provided in a message header for producer
endpoints with a�*CamelLinkedIn.*�prefix.
-[[LinkedIn-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
All result message bodies utilize objects provided by the Camel LinkedIn
API SDK, which is built using Apache CXF JAX-RS. Producer endpoints can
specify the option name for incoming message body in the *inBody*
endpoint parameter.
-[[LinkedIn-Usecases]]
-Use cases
-^^^^^^^^^
+### Use cases
The following route gets user's profile:
@@ -697,4 +669,4 @@ The following route uses a producer with dynamic header options.�The
.setHeader("CamelLinkedIn.person_id", header("personId"))
.to("linkedin://people/connectionsById")
.to("bean://bar");
------------------------------------------------------------------
+-----------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-lucene/src/main/docs/lucene-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-lucene/src/main/docs/lucene-component.adoc b/components/camel-lucene/src/main/docs/lucene-component.adoc
index 289186d..4cccec4 100644
--- a/components/camel-lucene/src/main/docs/lucene-component.adoc
+++ b/components/camel-lucene/src/main/docs/lucene-component.adoc
@@ -1,4 +1,4 @@
-# Lucene Component
+## Lucene Component
*Available as of Camel 2.2*
@@ -33,9 +33,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Lucene-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------------
@@ -46,9 +44,7 @@ lucene:searcherName:query[?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Lucene-InsertOptions]]
-Insert Options
-^^^^^^^^^^^^^^
+### Insert Options
@@ -94,13 +90,9 @@ The Lucene component supports 7 endpoint options which are listed below:
-[[Lucene-Sending/ReceivingMessagestoFromthecache]]
-Sending/Receiving Messages to/from the cache
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending/Receiving Messages to/from the cache
-[[Lucene-MessageHeaders]]
-Message Headers
-+++++++++++++++
+#### Message Headers
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -113,9 +105,7 @@ wildcards and phrases
documentation when returning hit information.
|=======================================================================
-[[Lucene-LuceneProducers]]
-Lucene Producers
-++++++++++++++++
+#### Lucene Producers
This component supports 2 producer endpoints.
@@ -129,20 +119,14 @@ property name called 'QUERY'. The value of the header property 'QUERY'
is a Lucene Query. For more details on how to create Lucene Queries
check out http://lucene.apache.org/java/3_0_0/queryparsersyntax.html[http://lucene.apache.org/java/3_0_0/queryparsersyntax.html]
-[[Lucene-LuceneProcessor]]
-Lucene Processor
-++++++++++++++++
+#### Lucene Processor
There is a processor called LuceneQueryProcessor available to perform
queries against lucene without the need to create a producer.
-[[Lucene-LuceneUsageSamples]]
-Lucene Usage Samples
-^^^^^^^^^^^^^^^^^^^^
+### Lucene Usage Samples
-[[Lucene-Example1:CreatingaLuceneindex]]
-Example 1: Creating a Lucene index
-++++++++++++++++++++++++++++++++++
+#### Example 1: Creating a Lucene index
[source,java]
------------------------------------------------------------------------------------
@@ -156,9 +140,7 @@ RouteBuilder builder = new RouteBuilder() {
};
------------------------------------------------------------------------------------
-[[Lucene-Example2:LoadingpropertiesintotheJNDIregistryintheCamelContext]]
-Example 2: Loading properties into the JNDI registry in the Camel Context
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 2: Loading properties into the JNDI registry in the Camel Context
[source,java]
-----------------------------------------------------------------
@@ -177,9 +159,7 @@ protected JndiRegistry createRegistry() throws Exception {
CamelContext context = new DefaultCamelContext(createRegistry());
-----------------------------------------------------------------
-[[Lucene-Example2:PerformingsearchesusingaQueryProducer]]
-Example 2: Performing searches using a Query Producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 2: Performing searches using a Query Producer
[source,java]
----------------------------------------------------------------------------------------------------
@@ -210,9 +190,7 @@ RouteBuilder builder = new RouteBuilder() {
};
----------------------------------------------------------------------------------------------------
-[[Lucene-Example3:PerformingsearchesusingaQueryProcessor]]
-Example 3: Performing searches using a Query Processor
-++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 3: Performing searches using a Query Processor
[source,java]
-------------------------------------------------------------------------------------------------------
@@ -244,4 +222,4 @@ RouteBuilder builder = new RouteBuilder() {
}).to("mock:searchResult");
}
};
--------------------------------------------------------------------------------------------------------
+-------------------------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc b/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc
index 3f0ee80..b94c81c 100644
--- a/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc
+++ b/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc
@@ -1,4 +1,4 @@
-# Lumberjack Component
+## Lumberjack Component
*Available as of Camel 2.18*
@@ -20,9 +20,7 @@ Maven users will need to add the following dependency to their `pom.xml` for thi
</dependency>
------------------------------------------------------------
-[[Lumberjack-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------------
@@ -33,9 +31,7 @@ lumberjack:host:port
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Lumberjack-Options]]
-Options
-^^^^^^^
+### Options
@@ -82,19 +78,13 @@ The Lumberjack component supports 7 endpoint options which are listed below:
-[[Lumberjack-Result]]
-Result
-^^^^^^
+### Result
The result body is a `Map<String, Object>` object.
-[[Lumberjack-LumberjackUsageSamples]]
-Lumberjack Usage Samples
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Lumberjack Usage Samples
-[[Lumberjack-Example1:]]
-Example 1: Streaming the log messages
-+++++++++++++++++++++++++++++++++++++
+#### Example 1: Streaming the log messages
[source,java]
------------------------------------------------------------------------------------
@@ -105,5 +95,4 @@ RouteBuilder builder = new RouteBuilder() {
to("stream:out"); // Write it into the output stream
}
};
-------------------------------------------------------------------------------------
-
+------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-lzf/src/main/docs/lzf-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-lzf/src/main/docs/lzf-dataformat.adoc b/components/camel-lzf/src/main/docs/lzf-dataformat.adoc
index b873ceb..00e2fc7 100644
--- a/components/camel-lzf/src/main/docs/lzf-dataformat.adoc
+++ b/components/camel-lzf/src/main/docs/lzf-dataformat.adoc
@@ -1,4 +1,4 @@
-# LZF Deflate Compression DataFormat
+## LZF Deflate Compression DataFormat
The
LZF�https://cwiki.apache.org/confluence/display/CAMEL/Data+Format[Data
@@ -9,9 +9,7 @@ endpoint. The compression capability is quite useful when you deal with
large XML and Text based payloads or when you read messages previously
comressed using LZF algotithm.
-[[LZFDataFormat-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The LZF Deflate Compression dataformat supports 2 options which are listed below.
@@ -28,9 +26,7 @@ The LZF Deflate Compression dataformat supports 2 options which are listed below
{% endraw %}
// dataformat options: END
-[[LZFDataFormat-Marshal]]
-Marshal
-^^^^^^^
+### Marshal
In this example we marshal a regular text/XML payload to a compressed
payload employing LZF compression format and send it an ActiveMQ queue
@@ -41,9 +37,7 @@ called MY_QUEUE.
from("direct:start").marshal().lzf().to("activemq:queue:MY_QUEUE");
-------------------------------------------------------------------
-[[LZFDataFormat-Unmarshal]]
-Unmarshal
-^^^^^^^^^
+### Unmarshal
In this example we unmarshal�a LZF payload from an ActiveMQ queue called
MY_QUEUE�to its original format,�and forward it for�processing�to
@@ -54,9 +48,7 @@ the�`UnGZippedMessageProcessor`.
from("activemq:queue:MY_QUEUE").unmarshal().lzf().process(new UnCompressedMessageProcessor());
----------------------------------------------------------------------------------------------
-[[LZFDataFormat-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To useLZF compression in your camel routes you need to add a dependency
on�*camel-lzf*�which implements this data format.
@@ -74,4 +66,4 @@ 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
[09/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc b/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
index 83677bc..8163c28 100644
--- a/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
+++ b/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
@@ -1,10 +1,8 @@
-# Google Calendar Component
+## Google Calendar Component
*Available as of Camel 2.15*
-[[GoogleCalendar-ComponentDescription]]
-Component Description
-^^^^^^^^^^^^^^^^^^^^^
+### Component Description
The Google Calendar component provides access
to�http://google.com/calendar[Google Calendar]�via
@@ -33,9 +31,7 @@ for this component:
----------------------------------------------------------
-[[GoogleCalendar-options]]
-1. Google Calendar Options
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### 1. Google Calendar Options
@@ -90,9 +86,7 @@ The Google Calendar component supports 16 endpoint options which are listed belo
// endpoint options: END
-[[GoogleCalendar-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
The GoogleCalendar Component uses the following URI format:
@@ -112,9 +106,7 @@ Endpoint prefix can be one of:
* list
* settings
-[[GoogleCalendar-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Producer Endpoints
Producer endpoints can use endpoint prefixes followed by endpoint names
and associated options described next. A shorthand alias can be used for
@@ -133,9 +125,7 @@ overrides message header, i.e. the endpoint option `inBody=option` would
override a `CamelGoogleCalendar.option` header.
-[[GoogleCalendar-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
Any of the producer endpoints can be used as a consumer endpoint.
Consumer endpoints can use
@@ -145,19 +135,15 @@ invocation. Consumer endpoints that return an array or collection will
generate one exchange per element, and their routes will be executed
once for each exchange.
-[[GoogleCalendar-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Any URI option can be provided in a message header for producer
endpoints with a `CamelGoogleCalendar.` prefix.
-[[GoogleCalendar-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
All result message bodies utilize objects provided by the underlying
APIs used by the GoogleCalendarComponent. Producer endpoints can specify
the option name for incoming message body in the `inBody` endpoint URI
parameter. For endpoints that return an array or collection, a consumer
-endpoint will map every element to distinct messages. � ��
+endpoint will map every element to distinct messages. � ��
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-google-drive/src/main/docs/google-drive-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-drive/src/main/docs/google-drive-component.adoc b/components/camel-google-drive/src/main/docs/google-drive-component.adoc
index 39457d7..10feb33 100644
--- a/components/camel-google-drive/src/main/docs/google-drive-component.adoc
+++ b/components/camel-google-drive/src/main/docs/google-drive-component.adoc
@@ -1,4 +1,4 @@
-# Google Drive Component
+## Google Drive Component
*Available as of Camel 2.14*
@@ -28,9 +28,7 @@ for this component:
-------------------------------------------------------
-[[GoogleDrive-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
'''''
@@ -57,9 +55,7 @@ Endpoint prefix can be one of:
* drive-replies
* drive-revisions
-[[GoogleDrive-GoogleDriveComponent.1]]
-GoogleDriveComponent
-^^^^^^^^^^^^^^^^^^^^
+### GoogleDriveComponent
@@ -114,9 +110,7 @@ The Google Drive component supports 14 endpoint options which are listed below:
-[[GoogleDrive-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Producer Endpoints
Producer endpoints can use endpoint prefixes followed by endpoint names
and associated options described next. A shorthand alias can be used for
@@ -137,9 +131,7 @@ override a `CamelGoogleDrive.option` header.
For more information on the endpoints and options see API documentation
at:�https://developers.google.com/drive/v2/reference/[https://developers.google.com/drive/v2/reference/]
-[[GoogleDrive-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
Any of the producer endpoints can be used as a consumer endpoint.
Consumer endpoints can use
@@ -149,19 +141,15 @@ invocation. Consumer endpoints that return an array or collection will
generate one exchange per element, and their routes will be executed
once for each exchange.
-[[GoogleDrive-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Any URI option can be provided in a message header for producer
endpoints with a `CamelGoogleDrive.` prefix.
-[[GoogleDrive-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
All result message bodies utilize objects provided by the underlying
APIs used by the GoogleDriveComponent. Producer endpoints can specify
the option name for incoming message body in the `inBody` endpoint URI
parameter. For endpoints that return an array or collection, a consumer
-endpoint will map every element to distinct messages. � ��
+endpoint will map every element to distinct messages. � ��
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-google-mail/src/main/docs/google-mail-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-mail/src/main/docs/google-mail-component.adoc b/components/camel-google-mail/src/main/docs/google-mail-component.adoc
index 293b216..c39f83d 100644
--- a/components/camel-google-mail/src/main/docs/google-mail-component.adoc
+++ b/components/camel-google-mail/src/main/docs/google-mail-component.adoc
@@ -1,10 +1,8 @@
-# Google Mail Component
+## Google Mail Component
*Available as of Camel 2.15*
-[[GoogleMail-ComponentDescription]]
-Component Description
-^^^^^^^^^^^^^^^^^^^^^
+### Component Description
The Google Mail component provides access
to�http://gmail.com/[Gmail]�via
@@ -33,9 +31,7 @@ for this component:
------------------------------------------------------
-[[GoogleMail-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
The GoogleMail Component uses the following URI format:
@@ -54,9 +50,7 @@ Endpoint prefix can be one of:
* threads
* users
-[[GoogleMail-GoogleMailComponent.1]]
-GoogleMailComponent
-^^^^^^^^^^^^^^^^^^^
+### GoogleMailComponent
@@ -109,9 +103,7 @@ The Google Mail component supports 13 endpoint options which are listed below:
-[[GoogleMail-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Producer Endpoints
Producer endpoints can use endpoint prefixes followed by endpoint names
and associated options described next. A shorthand alias can be used for
@@ -132,9 +124,7 @@ override a `CamelGoogleMail.option` header.
For more information on the endpoints and options see API documentation
at:�https://developers.google.com/gmail/api/v1/reference/[https://developers.google.com/gmail/api/v1/reference/]
-[[GoogleMail-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
Any of the producer endpoints can be used as a consumer endpoint.
Consumer endpoints can use
@@ -144,19 +134,15 @@ invocation. Consumer endpoints that return an array or collection will
generate one exchange per element, and their routes will be executed
once for each exchange.
-[[GoogleMail-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Any URI option can be provided in a message header for producer
endpoints with a `CamelGoogleMail.` prefix.
-[[GoogleMail-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
All result message bodies utilize objects provided by the underlying
APIs used by the GoogleMailComponent. Producer endpoints can specify the
option name for incoming message body in the `inBody` endpoint URI
parameter. For endpoints that return an array or collection, a consumer
-endpoint will map every element to distinct messages. � ��
+endpoint will map every element to distinct messages. � ��
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc b/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc
index ddba59e..cdbb8f4 100644
--- a/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc
+++ b/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc
@@ -1,10 +1,8 @@
-# Google Pubsub Component
+## Google Pubsub Component
*Available as of Camel 2.19*
-[[GooglePubsub-ComponentDescription]]
-Component Description
-^^^^^^^^^^^^^^^^^^^^^
+### Component Description
The Google Pubsub component provides access
to https://cloud.google.com/pubsub/[Cloud Pub/Sub Infrastructure]�via
@@ -44,9 +42,7 @@ https://developers.google.com/identity/protocols/application-default-credentials
Service Account Email and Service Account Key can be found in the GCP JSON credentials file as client_email and private_key respectively.
-[[GooglePubsub-URIFormat]]
-URI Format
-^^^^^^^^^
+### URI Format
The GoogleMail Component uses the following URI format:
@@ -56,9 +52,7 @@ The GoogleMail Component uses the following URI format:
Destination Name can be either a topic or a subscription name.
-[[GooglePubsub-GooglePubsubComponent]]
-GooglePubsubComponent
-^^^^^^^^^^^^^^^^^^
+### GooglePubsubComponent
// component options: START
The Google Pubsub component supports 1 options which are listed below.
@@ -96,9 +90,7 @@ The Google Pubsub component supports 11 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[GooglePubsub-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Producer Endpoints
Producer endpoints can accept and deliver to PubSub individual and grouped
exchanges alike. Grouped exchanges have `Exchange.GROUPED_EXCHANGE` property set.
@@ -113,9 +105,7 @@ A Map set as message header `GooglePubsubConstants.ATTRIBUTES` will be sent as P
Once exchange has been delivered to PubSub the PubSub Message ID will be assigned to
the header `GooglePubsubConstants.MESSAGE_ID`.
-[[GooglePubsub-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
Google PubSub will redeliver the message if it has not been acknowledged within the time period set
as a configuration option on the subscription.
@@ -128,9 +118,7 @@ To ack/nack the message the component uses Acknowledgement ID stored as header `
If the header is removed or tampered with, the ack will fail and the message will be redelivered
again after the ack deadline.
-[[GooglePubsub-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^
+### Message Headers
Headers set by the consumer endpoints:
* GooglePubsubConstants.MESSAGE_ID
@@ -138,16 +126,12 @@ Headers set by the consumer endpoints:
* GooglePubsubConstants.PUBLISH_TIME
* GooglePubsubConstants.ACK_ID
-[[GooglePubsub-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
The consumer endpoint returns the content of the message as byte[] - exactly as the underlying system sends it.
It is up for the route to convert/unmarshall the contents.
-[[GooglePubsub-RollbackRedelivery]]
-Rollback and Redelivery
-^^^^^^^^^^^^
+### Rollback and Redelivery
The rollback for Google PubSub relies on the idea of the Acknowledgement Deadline - the time period where Google PubSub expects to receive the acknowledgement.
If the acknowledgement has not been received, the message is redelivered.
@@ -164,4 +148,4 @@ setting the message header
* GooglePubsubConstants.ACK_DEADLINE
-to the value in seconds.
+to the value in seconds.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-gora/src/main/docs/gora-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-gora/src/main/docs/gora-component.adoc b/components/camel-gora/src/main/docs/gora-component.adoc
index 7913685..f09fbb8 100644
--- a/components/camel-gora/src/main/docs/gora-component.adoc
+++ b/components/camel-gora/src/main/docs/gora-component.adoc
@@ -1,4 +1,4 @@
-# Gora Component
+## Gora Component
*Camel-Gora* is an http://camel.apache.org/[Apache Camel] component that
allows you to work with NoSQL databases using the
@@ -19,9 +19,7 @@ for this component:
</dependency>
---------------------------------------------------------
-[[Gora-ApacheGoraOverview]]
-Apache Gora Overview
-~~~~~~~~~~~~~~~~~~~~
+### Apache Gora Overview
The http://gora.apache.org/[Apache Gora] open source framework provides
an in-memory data model and persistence for big data. Gora supports
@@ -39,9 +37,7 @@ http://accumulo.apache.org/[Apache Accumulo],
http://aws.amazon.com/dynamodb/[Amazon DynamoDB] and SQL databases such
as http://hsqldb.org/[hsqldb], http://www.mysql.com/[MySQL] and more.
-[[Gora-URIformat]]
-URI format
-~~~~~~~~~~
+### URI format
[source,text]
---------------------------
@@ -64,9 +60,7 @@ _Java DSL_
to("gora:foobar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore")
-------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[Gora-Configuratiion]]
-Configuratiion
-~~~~~~~~~~~~~~
+### Configuratiion
Using camel-gora needs some configuration. This mainly involve to
configure the _AvroStore_ through the _gora.properties_ file and to
@@ -77,9 +71,7 @@ Extensive information for this configuration can be found in the apache
http://gora.apache.org/current/index.html[gora documentation] and the
http://gora.apache.org/current/gora-conf.html[gora-conf] page.
-[[Gora-Options]]
-Options
-~~~~~~~
+### Options
// component options: START
@@ -126,9 +118,7 @@ The Gora component supports 22 endpoint options which are listed below:
-[[Gora-SupportedGoraOperations]]
-Supported Gora Operations
-~~~~~~~~~~~~~~~~~~~~~~~~~
+### Supported Gora Operations
Supported operations include : *put*, *get*, *delete*, *getSchemaName*,
*deleteSchema*, *createSchema*, *query*, *deleteByQuery*,
@@ -166,9 +156,7 @@ hold the objects._
datastore._
|=======================================================================
-[[Gora-GoraHeaders]]
-Gora Headers
-^^^^^^^^^^^^
+### Gora Headers
[width="100%",cols="20%,80%",options="header",]
|=======================================================================
@@ -179,9 +167,7 @@ Gora Headers
|GoraKey | _Used in order to define the datum key for the operations need it._
|=======================================================================
-[[Gora-Usageexamples]]
-Usage examples
-^^^^^^^^^^^^^^
+### Usage examples
*Create Schema* _(XML DSL)_:
@@ -253,11 +239,9 @@ The full usage examples in the form of integration tests can be found at
https://github.com/ipolyzos/camel-gora-examples/[camel-gora-examples]
repository.
-[[Gora-Moreresources]]
-More resources
-^^^^^^^^^^^^^^
+### More resources
For more please information and in depth configuration refer to the
http://gora.apache.org/current/overview.html[Apache Gora Documentation]
and the http://gora.apache.org/current/tutorial.html[Apache Gora
-Tutorial].
+Tutorial].
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-grape/src/main/docs/grape-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-grape/src/main/docs/grape-component.adoc b/components/camel-grape/src/main/docs/grape-component.adoc
index 02b2b34..4cddf27 100644
--- a/components/camel-grape/src/main/docs/grape-component.adoc
+++ b/components/camel-grape/src/main/docs/grape-component.adoc
@@ -1,4 +1,4 @@
-# Grape Component
+## Grape Component
Available as of Camel 2.16�
@@ -9,9 +9,7 @@ can add new components, data formats and beans to your `CamelContext`
without the restart of the router.
-[[Grape-Options]]
-Grape options
-^^^^^^^^^^^^^
+### Grape options
// component options: START
The Grape component has no options.
@@ -34,9 +32,7 @@ The Grape component supports 3 endpoint options which are listed below:
-[[Grape-Settingupclassloader]]
-Setting up class loader
-^^^^^^^^^^^^^^^^^^^^^^^
+### Setting up class loader
Grape requires using Groovy class loader with the `CamelContext`. You
can enable Groovy class loading on the existing Camel Context using the
@@ -57,9 +53,7 @@ yourself:
camelContext.setApplicationContextClassLoader(new GroovyClassLoader(myClassLoader));
------------------------------------------------------------------------------------
-[[Grape-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
Grape component supports only producer endpoints.
@@ -86,9 +80,7 @@ from("direct:loadCamelFTP").
to("grape:defaultMavenCoordinates");
----------------------------------------------------------
-[[Grape-AddingtheGrapecomponenttotheproject]]
-Adding the Grape component to the project
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Adding the Grape component to the project
Maven users will need to add the following dependency to their `pom.xml`
for this component:
@@ -103,9 +95,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Grape-Defaultpayloadtype]]
-Default payload type
-^^^^^^^^^^^^^^^^^^^^
+### Default payload type
By default Camel Grape component operates on the String payloads:
@@ -126,9 +116,7 @@ String:
producerTemplate.sendBody("grape:defaultMavenCoordinates", "org.apache.camel/camel-ftp/2.15.2".getBytes());
-----------------------------------------------------------------------------------------------------------
-[[Grape-Headers]]
-Headers
-^^^^^^^
+### Headers
The following headers are recognized by the Grape component:
@@ -139,9 +127,7 @@ The following headers are recognized by the Grape component:
|`CamelGrapeCommand` |`GrapeConstants.GRAPE_COMMAND` |Producer |`org.apache.camel.component.grape.GrapeCommand` |The command to be performed by the Grape endpoint. Default to `grab`.
|=======================================================================
-[[Grape-Loadingcomponentsatruntime]]
-Loading components at runtime
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading components at runtime
In order to load the new component at the router runtime, just grab the
jar containing the given component:
@@ -153,9 +139,7 @@ template.sendBody("grape:grape", "org.apache.camel/camel-stream/2.15.2");
template.sendBody("stream:out", "msg");
-------------------------------------------------------------------------
-[[Grape-Loadingprocessorsbeanatruntime]]
-Loading processors�bean�at runtime
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading processors�bean�at runtime
In order to load the new processor�bean �with your custom business login
at the router runtime, just grab the jar containing the required bean:
@@ -170,9 +154,7 @@ int price = template.requestBody("bean:com.example.PricingBean?method=currentPro
�
-[[Grape-LoadingdeployedjarsafterCamelcontextrestart]]
-Loading deployed jars after Camel context restart
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading deployed jars after Camel context restart
After you download new jar, you usually would like to have it loaded by
the Camel again after the restart of the `CamelContext`. It is certainly
@@ -201,9 +183,7 @@ camelContext.addRoutes(
�
-[[Grape-Managingtheinstalledjars]]
-Managing the installed jars
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Managing the installed jars
If you would like to check what jars have been installed into the given
`CamelContext`, send message to the grape endpoint with
@@ -237,12 +217,9 @@ command:
setBody().constant("Installed patches have been deleted.");�
-----------------------------------------------------------------------------------------
-[[Grape-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-groovy/src/main/docs/groovy-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-groovy/src/main/docs/groovy-language.adoc b/components/camel-groovy/src/main/docs/groovy-language.adoc
index 1eca86d..58edbd6 100644
--- a/components/camel-groovy/src/main/docs/groovy-language.adoc
+++ b/components/camel-groovy/src/main/docs/groovy-language.adoc
@@ -1,4 +1,4 @@
-# Groovy Language
+## Groovy Language
Camel supports http://groovy.codehaus.org/[Groovy] among other
link:scripting-languages.html[Scripting Languages] to allow an
@@ -18,9 +18,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
Filter] or as an link:expression.html[Expression] for a
link:recipient-list.html[Recipient List]
-[[Groovy-Options]]
-Groovy Options
-^^^^^^^^^^^^^^
+### Groovy Options
@@ -40,9 +38,7 @@ The Groovy language supports 1 options which are listed below.
-[[Groovy-CustomizingGroovyShell]]
-Customizing Groovy Shell
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Customizing Groovy Shell
Sometimes you may need to use custom `GroovyShell` instance in your
Groovy expressions. To provide custom `GroovyShell`, add implementation
@@ -68,9 +64,7 @@ public class CustomGroovyShellFactory implements GroovyShellFactory {
...Camel will use your custom GroovyShell instance (containing your
custom static imports), instead of the default one.
-[[Groovy-Example]]
-Example
-^^^^^^^
+### Example
[source,java]
------------------------------------------------------------------------------------------------
@@ -91,9 +85,7 @@ And the Spring DSL:
</route>
-----------------------------------------------------------------------------
-[[Groovy-ScriptContext]]
-ScriptContext
-^^^^^^^^^^^^^
+### ScriptContext
The JSR-223 scripting languages ScriptContext is pre configured with the
following attributes all set at `ENGINE_SCOPE`:
@@ -121,9 +113,7 @@ further below for example.
See link:scripting-languages.html[Scripting Languages] for the list of
languages with explicit DSL support.
-[[Groovy-AdditionalargumentstoScriptingEngine]]
-Additional arguments to ScriptingEngine
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional arguments to ScriptingEngine
*Available as of Camel 2.8*
@@ -131,9 +121,7 @@ You can provide additional arguments to the `ScriptingEngine` using a
header on the Camel message with the key `CamelScriptArguments`. +
See this example:
-[[Groovy-Usingpropertiesfunction]]
-Using properties function
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using properties function
*Available as of Camel 2.9*
@@ -156,9 +144,7 @@ same example is simpler:
.setHeader("myHeader").groovy("properties.resolve(request.headers.get('foo'))")
---------------------------------------------------------------------------------------
-[[Groovy-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -172,9 +158,7 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").groovy("resource:classpath:mygroovy.groovy")
-------------------------------------------------------------------
-[[Groovy-Howtogettheresultfrommultiplestatementsscript]]
-How to get the result from multiple statements script
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get the result from multiple statements script
*Available as of Camel 2.14*
@@ -192,9 +176,7 @@ bar = "baz";
result = body * 2 + 1
-------------------------------------------------------------
-[[Groovy-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use scripting languages in your camel routes you need to add the a
dependency on *camel-script* which integrates the JSR-223 scripting
@@ -211,4 +193,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-script</artifactId>
<version>x.x.x</version>
</dependency>
----------------------------------------
+---------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-gson/src/main/docs/json-gson-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-gson/src/main/docs/json-gson-dataformat.adoc b/components/camel-gson/src/main/docs/json-gson-dataformat.adoc
index aabde3c..c0df1e6 100644
--- a/components/camel-gson/src/main/docs/json-gson-dataformat.adoc
+++ b/components/camel-gson/src/main/docs/json-gson-dataformat.adoc
@@ -1,4 +1,4 @@
-# JSon GSon DataFormat
+## JSon GSon DataFormat
*Available as of Camel 2.18*
@@ -12,9 +12,7 @@ from("activemq:My.Queue").
to("mqseries:Another.Queue");
-------------------------------
-[[Gson-Options]]
-Gson Options
-^^^^^^^^^^^^
+### Gson Options
// dataformat options: START
@@ -49,9 +47,7 @@ The JSon GSon dataformat supports 17 options which are listed below.
-[[Gson-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Gson in your camel routes you need to add the dependency
on *camel-gson* which implements this data format.
@@ -68,4 +64,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-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc b/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
index f796008..879c8c9 100644
--- a/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
+++ b/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
@@ -1,4 +1,4 @@
-# Guava EventBus Component
+## Guava EventBus Component
*Available since Camel 2.10.0*
@@ -27,9 +27,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[GuavaEventBus-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------------
@@ -40,9 +38,7 @@ Where *busName* represents the name of the
`com.google.common.eventbus.EventBus` instance located in the Camel
registry.
-[[GuavaEventBus-Options]]
-Options
-^^^^^^^
+### Options
@@ -87,9 +83,7 @@ The Guava EventBus component supports 7 endpoint options which are listed below:
-[[GuavaEventBus-Usage]]
-Usage
-^^^^^
+### Usage
Using `guava-eventbus` component on the consumer side of the route will
capture messages sent to the Guava `EventBus` and forward them to the
@@ -131,9 +125,7 @@ eventBus.register(new Object(){
});
----------------------------------------------------------------------
-[[GuavaEventBus-DeadEventconsiderations]]
-DeadEvent considerations
-^^^^^^^^^^^^^^^^^^^^^^^^
+### DeadEvent considerations
Keep in mind that due to the limitations caused by the design of the
Guava EventBus, you cannot specify event class to be received by the
@@ -182,9 +174,7 @@ follows.
from("guava-eventbus:busName?listenerInterface=com.example.CustomListener").to("seda:queue");
---------------------------------------------------------------------------------------------
-[[GuavaEventBus-Consumingmultipletypeofevents]]
-Consuming multiple type of events
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Consuming multiple type of events
In order to define multiple type of events to be consumed by Guava
EventBus consumer use `listenerInterface` endpoint option, as listener
@@ -212,4 +202,4 @@ follows.
[source,java]
-----------------------------------------------------------------------------------------------------
from("guava-eventbus:busName?listenerInterface=com.example.MultipleEventsListener").to("seda:queue");
------------------------------------------------------------------------------------------------------
+-----------------------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hazelcast/src/main/docs/hazelcast-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-component.adoc
index b042205..4873afa 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-component.adoc
@@ -1,4 +1,4 @@
-# Hazelcast Component
+## Hazelcast Component
*Available as of Camel 2.7*
@@ -28,9 +28,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[HazelcastComponent-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------------------------------------------------------------------------------------------------
@@ -42,9 +40,7 @@ hazelcast:[ map | multimap | queue | topic | seda | set | atomicvalue | instance
* RingBuffer support is available as of Camel 2.16.�*
-[[HazelcastComponent-Options]]
-Options
-^^^^^^^
+### Options
@@ -94,9 +90,7 @@ The Hazelcast component supports 13 endpoint options which are listed below:
-[[HazelcastComponent-Sections]]
-Sections
-^^^^^^^^
+### Sections
1. Usage of link:hazelcast-component.html[#map]
2. Usage of link:hazelcast-component.html[#multimap]
@@ -109,13 +103,9 @@ Sections
9. Usage of link:hazelcast-component.html[#replicatedmap]�
10. Usage of�link:hazelcast-component.html[#ringbuffer]�
-[[HazelcastComponent-UsageofMap]]
-Usage of Map
-^^^^^^^^^^^^
+### Usage of Map
-[[HazelcastComponent-mapcacheproducer-to-map]]
-Map cache producer - to("hazelcast:map:foo")
-++++++++++++++++++++++++++++++++++++++++++++
+#### Map cache producer - to("hazelcast:map:foo")
If you want to store a value in a map you can use the map cache
producer.
@@ -343,9 +333,7 @@ String q1 = "bar > 1000";
template.sendBodyAndHeader("direct:query", null, HazelcastConstants.QUERY, q1);
-------------------------------------------------------------------------------
-[[HazelcastComponent-mapcacheconsumer-from-map]]
-Map cache consumer - from("hazelcast:map:foo")
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Map cache consumer - from("hazelcast:map:foo")
Hazelcast provides event listeners on their data grid. If you want to be
notified if a cache will be manipulated, you can use the map consumer.
@@ -399,13 +387,9 @@ fromF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX)
.log("fail!");
--------------------------------------------------------------------------------------------
-[[HazelcastComponent-UsageofMultiMap]]
-Usage of Multi Map
-^^^^^^^^^^^^^^^^^^
+### Usage of Multi Map
-[[HazelcastComponent-multimapcacheproducer-to-multimap]]
-multimap cache producer - to("hazelcast:multimap:foo")
-++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### multimap cache producer - to("hazelcast:multimap:foo")
A multimap is a cache where you can store n values to one key. The
multimap producer provides 4 operations (put, get, removevalue, delete).
@@ -543,9 +527,7 @@ you can call them in your test class with:
template.sendBodyAndHeader("direct:[put|get|removevalue|delete]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");
------------------------------------------------------------------------------------------------------------------
-[[HazelcastComponent-multimapcacheconsumer-from-multimap]]
-multimap cache consumer - from("hazelcast:multimap:foo")
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### multimap cache consumer - from("hazelcast:multimap:foo")
For the multimap cache this component provides the same listeners /
variables as for the map cache consumer (except the update and enviction
@@ -589,13 +571,9 @@ Header Variables inside the response message:
|`CamelHazelcastCacheType` |`String` |the type of the cache - here multimap
|=======================================================================
-[[HazelcastComponent-UsageofQueue]]
-Usage of Queue
-^^^^^^^^^^^^^^
+### Usage of Queue
-[[HazelcastComponent-Queueproducer]]
-Queue producer \u2013 to(\u201chazelcast:queue:foo\u201d)
-++++++++++++++++++++++++++++++++++++++++++
+#### Queue producer \u2013 to(\u201chazelcast:queue:foo\u201d)
The queue producer provides 6 operations (add, put, poll, peek, offer,
removevalue).
@@ -660,9 +638,7 @@ from("direct:removevalue")
.toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
--------------------------------------------------------------------------------------------
-[[HazelcastComponent-Queueconsumer]]
-Queue consumer \u2013 from(\u201chazelcast:queue:foo\u201d)
-++++++++++++++++++++++++++++++++++++++++++++
+#### Queue consumer \u2013 from(\u201chazelcast:queue:foo\u201d)
The queue consumer provides 2 operations (add, remove).
@@ -683,13 +659,9 @@ fromF("hazelcast:%smm", HazelcastConstants.QUEUE_PREFIX)
[[HazelcastComponent-topic]]
-[[HazelcastComponent-UsageofTopic]]
-Usage of Topic
-^^^^^^^^^^^^^^
+### Usage of Topic
-[[HazelcastComponent-Topicproducer]]
-Topic producer \u2013 to(\u201chazelcast:topic:foo\u201d)
-++++++++++++++++++++++++++++++++++++++++++
+#### Topic producer \u2013 to(\u201chazelcast:topic:foo\u201d)
The topic producer provides only one operation (publish).
@@ -703,9 +675,7 @@ from("direct:add")
.toF("hazelcast:%sbar", HazelcastConstants.PUBLISH_OPERATION);
----------------------------------------------------------------------------------------
-[[HazelcastComponent-Topicconsumer]]
-Topic consumer \u2013 from(\u201chazelcast:topic:foo\u201d)
-++++++++++++++++++++++++++++++++++++++++++++
+#### Topic consumer \u2013 from(\u201chazelcast:topic:foo\u201d)
The topic consumer provides only one operation (received). This
component is supposed to support multiple consumption as it's expected
@@ -724,13 +694,9 @@ fromF("hazelcast:%sfoo", HazelcastConstants.TOPIC_PREFIX)
�
-[[HazelcastComponent-UsageofList]]
-Usage of List
-^^^^^^^^^^^^^
+### Usage of List
-[[HazelcastComponent-Listproducer]]
-List producer \u2013 to(\u201chazelcast:list:foo\u201d)
-++++++++++++++++++++++++++++++++++++++++
+#### List producer \u2013 to(\u201chazelcast:list:foo\u201d)
The list producer provides 4 operations (add, addAll, set, get,
removevalue, removeAll, clear).
@@ -779,9 +745,7 @@ from("direct:removevalue")
Note that�*CamelHazelcastObjectIndex* header is used for indexing
purpose.
-[[HazelcastComponent-Thelistconsumerprovides2operationsListconsumer]]
-The list consumer provides 2 operations (add, remove).List consumer \u2013 from(\u201chazelcast:list:foo\u201d)
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### The list consumer provides 2 operations (add, remove).List consumer \u2013 from(\u201chazelcast:list:foo\u201d)
[source,java]
-----------------------------------------------------------------------------------------------
@@ -798,17 +762,13 @@ fromF("hazelcast:%smm", HazelcastConstants.LIST_PREFIX)
.log("fail!");
-----------------------------------------------------------------------------------------------
-[[HazelcastComponent-UsageofSEDA]]
-Usage of SEDA
-^^^^^^^^^^^^^
+### Usage of SEDA
SEDA component differs from the rest components provided. It implements
a work-queue in order to support asynchronous SEDA architectures,
similar to the core "SEDA" component.
-[[HazelcastComponent-SEDAproducer]]
-SEDA producer \u2013 to(\u201chazelcast:seda:foo\u201d)
-++++++++++++++++++++++++++++++++++++++++
+#### SEDA producer \u2013 to(\u201chazelcast:seda:foo\u201d)
The SEDA producer provides no operations. You only send data to the
specified queue.
@@ -839,9 +799,7 @@ Spring DSL :
</route>
----------------------------------
-[[HazelcastComponent-SEDAconsumer]]
-SEDA consumer \u2013 from(\u201chazelcast:seda:foo\u201d)
-++++++++++++++++++++++++++++++++++++++++++
+#### SEDA consumer \u2013 from(\u201chazelcast:seda:foo\u201d)
The SEDA consumer provides no operations. You only retrieve data from
the specified queue.
@@ -889,15 +847,11 @@ Spring DSL:
</route>
-----------------------------------
-[[HazelcastComponent-UsageofAtomicNumber]]
-Usage of Atomic Number
-^^^^^^^^^^^^^^^^^^^^^^
+### Usage of Atomic Number
* There is no consumer for this endpoint! *
-[[HazelcastComponent-atomicnumberproducer]]
-atomic number producer - to("hazelcast:atomicnumber:foo")
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### atomic number producer - to("hazelcast:atomicnumber:foo")
An atomic number is an object that simply provides a grid wide number
(long). The operations for this producer are setvalue (set the number
@@ -1054,15 +1008,11 @@ Spring DSL:
</route>
-----------------------------------------------------------------------------------------------
-[[HazelcastComponent-clustersupport]]
-cluster support
-^^^^^^^^^^^^^^^
+### cluster support
* This endpoint provides no producer! *
-[[HazelcastComponent-instanceconsumer-from]]
-instance consumer - from("hazelcast:instance:foo")
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### instance consumer - from("hazelcast:instance:foo")
Hazelcast makes sense in one single "server node", but it's extremly
powerful in a clustered environment. The instance consumer fires if a
@@ -1103,13 +1053,9 @@ Header Variables inside the response message:
|`CamelHazelcastInstancePort` |`Integer` |port number of the instance
|=======================================================================
-[[HazelcastComponent-Usinghazelcastreference]]
-Using hazelcast reference
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using hazelcast reference
-[[HazelcastComponent-Byitsname]]
-By its name
-+++++++++++
+#### By its name
[source,xml]
--------------------------------------------------------------------------------------------------------
@@ -1144,9 +1090,7 @@ By its name
</camelContext>
--------------------------------------------------------------------------------------------------------
-[[HazelcastComponent-Byinstance]]
-By instance
-+++++++++++
+#### By instance
[source,xml]
------------------------------------------------------------------------------
@@ -1176,18 +1120,14 @@ By instance
</camelContext>
------------------------------------------------------------------------------
-[[HazelcastComponent-PublishinghazelcastinstanceasanOSGIservice]]
-Publishing hazelcast instance as an OSGI service
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Publishing hazelcast instance as an OSGI service
If operating in an OSGI container and you would want to use one instance
of hazelcast across all bundles in the same container. You can publish
the instance as an OSGI service and bundles using the cache al need is
to reference the service in the hazelcast endpoint.
-[[HazelcastComponent-BundleAcreateaninstanceandpublishesitasanOSGIservice]]
-Bundle A create an instance and publishes it as an OSGI service
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Bundle A create an instance and publishes it as an OSGI service
�
@@ -1205,9 +1145,7 @@ Bundle A create an instance and publishes it as an OSGI service
<service ref="hazelcastInstance" interface="com.hazelcast.core.HazelcastInstance" />
--------------------------------------------------------------------------------------------------------
-[[HazelcastComponent-BundleBusestheinstance]]
-Bundle B uses the instance
-++++++++++++++++++++++++++
+#### Bundle B uses the instance
[source,xml]
--------------------------------------------------------------------------------------
@@ -1234,15 +1172,11 @@ Bundle B uses the instance
</camelContext>
--------------------------------------------------------------------------------------
-[[HazelcastComponent-UsageofReplicatedmap]]
-Usage of Replicated map
-^^^^^^^^^^^^^^^^^^^^^^^
+### Usage of Replicated map
*Avalaible from Camel 2.16*
-[[HazelcastComponent-replicatedmapcacheproducer]]
-replicatedmap cache producer
-++++++++++++++++++++++++++++
+#### replicatedmap cache producer
A replicated map is a weakly consistent, distributed key-value data
structure with no data partition. The replicatedmap producer provides 4
@@ -1349,9 +1283,7 @@ you can call them in your test class with:
template.sendBodyAndHeader("direct:[put|get|delete|clear]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");
------------------------------------------------------------------------------------------------------------
-[[HazelcastComponent-replicatedmapcacheconsumer]]
-replicatedmap cache consumer
-++++++++++++++++++++++++++++
+#### replicatedmap cache consumer
For the multimap cache this component provides the same listeners /
variables as for the map cache consumer (except the update and enviction
@@ -1395,15 +1327,11 @@ Header Variables inside the response message:
|`CamelHazelcastCacheType` |`String` |the type of the cache - here replicatedmap
|=======================================================================
-[[HazelcastComponent-UsageofRingbuffer]]
-Usage of Ringbuffer
-^^^^^^^^^^^^^^^^^^^
+### Usage of Ringbuffer
*Avalaible from Camel 2.16*
-[[HazelcastComponent-ringbuffercacheproducer]]
-ringbuffer cache producer
-+++++++++++++++++++++++++
+#### ringbuffer cache producer
Ringbuffer is a distributed data structure where the data is stored in a
ring-like structure. You can think of it as a circular array with a
@@ -1459,4 +1387,4 @@ from("direct:get")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.READ_ONCE_HEAD_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.RINGBUFFER_PREFIX)
.to("seda:out");
------------------------------------------------------------------------------------------------
+-----------------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hbase/src/main/docs/hbase-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hbase/src/main/docs/hbase-component.adoc b/components/camel-hbase/src/main/docs/hbase-component.adoc
index e9caa6a..dfaa3ba 100644
--- a/components/camel-hbase/src/main/docs/hbase-component.adoc
+++ b/components/camel-hbase/src/main/docs/hbase-component.adoc
@@ -1,4 +1,4 @@
-# HBase Component
+## HBase Component
*Available as of Camel 2.10*
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[hbase-ApacheHBaseOverview]]
-Apache HBase Overview
-^^^^^^^^^^^^^^^^^^^^^
+### Apache HBase Overview
HBase is an open-source, distributed, versioned, column-oriented store
modeled after Google's Bigtable: A Distributed Storage System for
@@ -28,9 +26,7 @@ Structured Data. You can use HBase when you need random, realtime
read/write access to your Big Data. More information at
http://hbase.apache.org[Apache HBase].
-[[hbase-CamelandHBase]]
-Camel and HBase
-^^^^^^^^^^^^^^^
+### Camel and HBase
When using a datasotre inside a camel route, there is always the
chalenge of specifying how the camel message will stored to the
@@ -59,9 +55,7 @@ Regardless of the mapping strategy camel-hbase will convert a message
into an org.apache.camel.component.hbase.model.HBaseData object and use
that object for its internal operations.
-[[hbase-Configuringthecomponent]]
-Configuring the component
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring the component
The HBase component can be provided a custom HBaseConfiguration object
as a property or it can create an HBase configuration object on its own
@@ -81,9 +75,7 @@ You can find more information about how to configure HBase clients at:
http://archive.apache.org/dist/hbase/docs/client_dependencies.html[HBase
client configuration and dependencies]
-[[hbase-HBaseProducer]]
-HBase Producer
-^^^^^^^^^^^^^^
+### HBase Producer
As mentioned above camel provides produers endpoints for HBase. This
allows you to store, delete, retrieve or query data from HBase using
@@ -103,9 +95,7 @@ The supported operations are:
* Delete
* Scan
-[[hbase-SupportedURIoptions]]
-Supported URI options
-+++++++++++++++++++++
+#### Supported URI options
@@ -160,9 +150,7 @@ The HBase component supports 17 endpoint options which are listed below:
-[[hbase-PutOperations.]]
-Put Operations.
-+++++++++++++++
+#### Put Operations.
HBase is a column based store, which allows you to store data into a
specific column of a specific row. Columns are grouped into families, so
@@ -226,9 +214,7 @@ headers or a combination of both. It is recommended to specify constants
as part of the uri and dynamic values as headers. If something is
defined both as header and as part of the uri, the header will be used.
-[[hbase-GetOperations.]]
-Get Operations.
-+++++++++++++++
+#### Get Operations.
A Get Operation is an operation that is used to retrieve one or more
values from a specified HBase row. To specify what are the values that
@@ -251,9 +237,7 @@ message headers.
In the example above the result of the get operation will be stored as a
header with name CamelHBaseValue.
-[[hbase-DeleteOperations.]]
-Delete Operations.
-++++++++++++++++++
+#### Delete Operations.
You can also you camel-hbase to perform HBase delete operation. The
delete operation will remove an entire row. All that needs to be
@@ -271,9 +255,7 @@ specified is one or more rows as part of the message headers.
</route>
----------------------------------------------------------------
-[[hbase-ScanOperations.]]
-Scan Operations.
-++++++++++++++++
+#### Scan Operations.
A scan operation is the equivalent of a query in HBase. You can use the
scan operation to retrieve multiple rows. To specify what columns should
@@ -354,9 +336,7 @@ and will pass that model the the ModelAwareColumnMatchingFilter. The
filter will filter out any rows, that do not contain columns that match
the model. It is like query by example.
-[[hbase-HBaseConsumer]]
-HBase Consumer
-^^^^^^^^^^^^^^
+### HBase Consumer
The Camel HBase Consumer, will perform repeated scan on the specified
HBase table and will return the scan results as part of the message. You
@@ -382,9 +362,7 @@ specified fields and the scan results will populate the model object
with values. Finally the mapping strategy will be used to map this model
to the camel message.
-[[hbase-HBaseIdempotentrepository]]
-HBase Idempotent repository
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### HBase Idempotent repository
The camel-hbase component also provides an idempotent repository which
can be used when you want to make sure that each message is processed
@@ -402,18 +380,14 @@ from("direct:in")
.to("log:out);
------------------------------------------------------------------------------------------------------------------
-[[hbase-HBaseMapping]]
-HBase Mapping
-^^^^^^^^^^^^^
+### HBase Mapping
It was mentioned above that you the default mapping strategies are
*header* and *body* mapping. +
Below you can find some detailed examples of how each mapping strategy
works.
-[[hbase-HBaseHeadermappingExamples]]
-HBase Header mapping Examples
-+++++++++++++++++++++++++++++
+#### HBase Header mapping Examples
The header mapping is the default mapping.
To put the value "myvalue" into HBase row "myrow" and column
@@ -475,9 +449,7 @@ Please note that in order to avoid boilerplate headers that are
considered constant for all messages, you can also specify them as part
of the endpoint uri, as you will see below.
-[[hbase-BodymappingExamples]]
-Body mapping Examples
-+++++++++++++++++++++
+#### Body mapping Examples
In order to use the body mapping strategy you will have to specify the
option mappingStrategy as part of the uri, for example:
@@ -510,10 +482,7 @@ myvalue to the column myfamily:myqualifier. +
advantage it has over the header mapping strategy is that the HBaseData
object can be easily converted to or from xml/json.
-[[hbase-Seealso]]
-See also
-^^^^^^^^
+### See also
* link:polling-consumer.html[Polling Consumer]
-* http://hbase.apache.org[Apache HBase]
-
+* http://hbase.apache.org[Apache HBase]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hdfs/src/main/docs/hdfs-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hdfs/src/main/docs/hdfs-component.adoc b/components/camel-hdfs/src/main/docs/hdfs-component.adoc
index eb420d2..97170fb 100644
--- a/components/camel-hdfs/src/main/docs/hdfs-component.adoc
+++ b/components/camel-hdfs/src/main/docs/hdfs-component.adoc
@@ -1,4 +1,4 @@
-# HDFS Component
+## HDFS Component
*Available as of Camel 2.8*
@@ -19,9 +19,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[HDFS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------
@@ -51,9 +49,7 @@ fileMode=Append to append each of the chunks together.
�
-[[HDFS-Options]]
-Options
-^^^^^^^
+### Options
@@ -134,9 +130,7 @@ The HDFS component supports 41 endpoint options which are listed below:
-[[HDFS-KeyTypeandValueType]]
-KeyType and ValueType
-+++++++++++++++++++++
+#### KeyType and ValueType
* NULL it means that the key or the value is absent
* BYTE for writing a byte, the java Byte class is mapped into a BYTE
@@ -152,9 +146,7 @@ BYTES is also used with everything else, for example, in Camel a file is
sent around as an InputStream, int this case is written in a sequence
file or a map file as a sequence of bytes.
-[[HDFS-SplittingStrategy]]
-Splitting Strategy
-^^^^^^^^^^^^^^^^^^
+### Splitting Strategy
In the current version of Hadoop opening a file in append mode is
disabled since it's not very reliable. So, for the moment, it's only
@@ -197,15 +189,11 @@ than 1 second or if more than 5 bytes have been written. So, running
`hadoop fs -ls /tmp/simple-file` you'll see that multiple files have
been created.
-[[HDFS-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
The following headers are supported by this component:
-[[HDFS-Produceronly]]
-Producer only
-+++++++++++++
+#### Producer only
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -217,9 +205,7 @@ link:expression.html[Expression] object. Only relevant when not using a
split strategy.
|=======================================================================
-[[HDFS-Controllingtoclosefilestream]]
-Controlling to close file stream
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Controlling to close file stream
*Available as of Camel 2.10.4*
@@ -234,9 +220,7 @@ the stream should be closed or not.
Notice this does not apply if you use a split strategy, as there are
various strategies that can control when the stream is closed.
-[[HDFS-UsingthiscomponentinOSGi]]
-Using this component in OSGi
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using this component in OSGi
This component is fully functional in an OSGi environment, however, it
requires some actions from the user. Hadoop uses the thread context
@@ -245,4 +229,4 @@ classloader will be the bundle class loader of the bundle that contains
the routes. So, the default configuration files need to be visible from
the bundle class loader. A typical way to deal with it is to keep a copy
of core-default.xml in your bundle root. That file can be found in the
-hadoop-common.jar.
+hadoop-common.jar.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hdfs2/src/main/docs/hdfs2-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hdfs2/src/main/docs/hdfs2-component.adoc b/components/camel-hdfs2/src/main/docs/hdfs2-component.adoc
index e9ec68d..e08eb49 100644
--- a/components/camel-hdfs2/src/main/docs/hdfs2-component.adoc
+++ b/components/camel-hdfs2/src/main/docs/hdfs2-component.adoc
@@ -1,4 +1,4 @@
-# HDFS2 Component
+## HDFS2 Component
*Available as of Camel 2.13*
@@ -19,9 +19,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[HDFS2-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------------------
@@ -48,9 +46,7 @@ chunk using the chunkSize option. If you want to read from hdfs and
write to a regular file using the file component, then you can use the
fileMode=Append to append each of the chunks together.
-[[HDFS2-Options]]
-Options
-^^^^^^^
+### Options
@@ -130,9 +126,7 @@ The HDFS2 component supports 41 endpoint options which are listed below:
-[[HDFS2-KeyTypeandValueType]]
-KeyType and ValueType
-+++++++++++++++++++++
+#### KeyType and ValueType
* NULL it means that the key or the value is absent
* BYTE for writing a byte, the java Byte class is mapped into a BYTE
@@ -148,9 +142,7 @@ BYTES is also used with everything else, for example, in Camel a file is
sent around as an InputStream, int this case is written in a sequence
file or a map file as a sequence of bytes.
-[[HDFS2-SplittingStrategy]]
-Splitting Strategy
-^^^^^^^^^^^^^^^^^^
+### Splitting Strategy
In the current version of Hadoop opening a file in append mode is
disabled since it's not very reliable. So, for the moment, it's only
@@ -190,15 +182,11 @@ than 1 second or if more than 5 bytes have been written. So, running
`hadoop fs -ls /tmp/simple-file` you'll see that multiple files have
been created.
-[[HDFS2-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
The following headers are supported by this component:
-[[HDFS2-Produceronly]]
-Producer only
-+++++++++++++
+#### Producer only
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -210,9 +198,7 @@ link:expression.html[Expression] object. Only relevant when not using a
split strategy.
|=======================================================================
-[[HDFS2-Controllingtoclosefilestream]]
-Controlling to close file stream
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Controlling to close file stream
When using the link:hdfs2.html[HDFS2] producer *without* a split
strategy, then the file output stream is by default closed after the
@@ -225,9 +211,7 @@ the stream should be closed or not.
Notice this does not apply if you use a split strategy, as there are
various strategies that can control when the stream is closed.
-[[HDFS2-UsingthiscomponentinOSGi]]
-Using this component in OSGi
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using this component in OSGi
There are some quirks when running this component in an OSGi environment
related to the mechanism Hadoop 2.x uses to discover different
@@ -242,9 +226,7 @@ be visible from the bundle class loader. A typical way to deal with it
is to keep a copy of�`core-default.xml` (and e.g., `hdfs-default.xml`)
in your bundle root.
-[[HDFS2-Usingthiscomponentwithmanuallydefinedroutes]]
-Using this component with manually defined routes
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using this component with manually defined routes
There are two options:
@@ -265,9 +247,7 @@ FileSystem.get("hdfs://localhost:9000/", conf);
...
----------------------------------------------------------------------------------------------------
-[[HDFS2-UsingthiscomponentwithBlueprintcontainer]]
-Using this component with Blueprint container
-+++++++++++++++++++++++++++++++++++++++++++++
+#### Using this component with Blueprint container
Two options:
@@ -291,4 +271,4 @@ resource with bundle that contains blueprint definition.
------------------------------------------------------------------------------------------------------
This way Hadoop 2.x will have correct mapping of URI schemes to
-filesystem implementations.
+filesystem implementations.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hessian/src/main/docs/hessian-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hessian/src/main/docs/hessian-dataformat.adoc b/components/camel-hessian/src/main/docs/hessian-dataformat.adoc
index b2b7abb..a42c9c8 100644
--- a/components/camel-hessian/src/main/docs/hessian-dataformat.adoc
+++ b/components/camel-hessian/src/main/docs/hessian-dataformat.adoc
@@ -1,4 +1,4 @@
-# Hessian DataFormat
+## Hessian DataFormat
Hessian is Data Format for marshalling and unmarshalling messages using Caucho's Hessian format.
@@ -14,9 +14,7 @@ If you want to use Hessian Data Format from Maven, add the following dependency
</dependency>
------------------------------------------------------------
-[[HessianDataFormat-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The Hessian dataformat supports 1 options which are listed below.
@@ -32,9 +30,7 @@ The Hessian dataformat supports 1 options which are listed below.
{% endraw %}
// dataformat options: END
-[[hessian-UsingHessianDataFormat]]
-Using the Hessian data format in Java DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the Hessian data format in Java DSL
[source,java]
--------------------------------------------------------------------------------
@@ -42,9 +38,7 @@ Using the Hessian data format in Java DSL
.marshal().hessian();
--------------------------------------------------------------------------------
-[[hessian-UsingHessianDataFormatXml]]
-Using the Hessian data format in Spring DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the Hessian data format in Spring DSL
[source,xml]
--------------------------------------------------------------------------------
@@ -54,4 +48,4 @@ Using the Hessian data format in Spring DSL
<marshal ref="hessian"/>
</route>
</camelContext>
---------------------------------------------------------------------------------
+--------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hipchat/src/main/docs/hipchat-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hipchat/src/main/docs/hipchat-component.adoc b/components/camel-hipchat/src/main/docs/hipchat-component.adoc
index 067aef7..063a165 100644
--- a/components/camel-hipchat/src/main/docs/hipchat-component.adoc
+++ b/components/camel-hipchat/src/main/docs/hipchat-component.adoc
@@ -1,4 +1,4 @@
-# Hipchat Component
+## Hipchat Component
*Available as of Camel 2.15.0*
@@ -12,9 +12,7 @@ https://www.hipchat.com/account/api[personal access token] that you can
use to produce/consume messages.
-[[Hipchat-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
-------------------------------
@@ -24,9 +22,7 @@ hipchat://[host][:port]?options
You can append query options to the URI in the following format,
?options=value&option2=value&...
-[[Hipchat-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -78,9 +74,7 @@ The Hipchat component supports 24 endpoint options which are listed below:
-[[Hipchat-ScheduledPollConsumer]]
-Scheduled Poll Consumer
-^^^^^^^^^^^^^^^^^^^^^^^
+### Scheduled Poll Consumer
This component implements the
link:polling-consumer.html[ScheduledPollConsumer]. Only the last message
@@ -105,9 +99,7 @@ public void configure() throws Exception {
}
---------------------------------------------------------------------------------
-[[Hipchat-MessageheaderssetbytheHipchatconsumer]]
-Message headers set by the Hipchat consumer
-+++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the Hipchat consumer
[width="100%",cols="10%,10%,10%,70%",options="header",]
|=======================================================================
@@ -124,9 +116,7 @@ Hipchat https://www.hipchat.com/docs/apiv2/method/view_recent_privatechat_histor
The status of the API response received.
|=======================================================================
-[[Hipchat-HipchatProducer]]
-Hipchat Producer
-^^^^^^^^^^^^^^^^
+### Hipchat Producer
Producer can send messages to both Room's and User's simultaneously. The
body of the exchange is sent as message. Sample usage is shown below.
@@ -143,9 +133,7 @@ Appropriate headers needs to be set.
}
----------------------------------------------------------
-[[Hipchat-MessageheadersevaluatedbytheHipchatproducer]]
-Message headers evaluated by the Hipchat producer
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Hipchat producer
[width="100%",cols="10%,10%,10%,70%",options="header",]
|=======================================================================
@@ -166,9 +154,7 @@ a user notification (change the tab color, play a sound, notify mobile
phones, etc). *Default: 'false' (Room Only)*
|=======================================================================
-[[Hipchat-MessageheaderssetbytheHipchatproducer]]
-Message headers set by the Hipchat producer
-+++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the Hipchat producer
[width="100%",cols="10%,10%,10%,70%",options="header",]
|=======================================================================
@@ -181,9 +167,7 @@ The status of the API response received when message sent to the user.
|HipchatFromUserResponseStatus |HipchatConstants.TO_ROOM_RESPONSE_STATUS |_http://hc.apache.org/httpcomponents-core-4.2.x/httpcore/apidocs/org/apache/http/StatusLine.html[StatusLine]_ |The status of the API response received when message sent to the room.
|=======================================================================
-[[Hipchat-Dependencies]]
-Dependencies
-++++++++++++
+#### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -199,4 +183,4 @@ Maven users will need to add the following dependency to their pom.xml.
------------------------------------------
where�`${camel-version}` must be replaced by the actual version of Camel
-(2.15.0 or higher)
+(2.15.0 or higher)
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hl7/src/main/docs/hl7-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hl7/src/main/docs/hl7-dataformat.adoc b/components/camel-hl7/src/main/docs/hl7-dataformat.adoc
index cbdfcb1..6691468 100644
--- a/components/camel-hl7/src/main/docs/hl7-dataformat.adoc
+++ b/components/camel-hl7/src/main/docs/hl7-dataformat.adoc
@@ -1,4 +1,4 @@
-# HL7 DataFormat
+## HL7 DataFormat
The *HL7* component is used for working with the HL7 MLLP protocol and
http://www.hl7.org/implement/standards/product_brief.cfm?product_id=185[HL7
@@ -26,9 +26,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[HL7-HL7MLLPprotocol]]
-HL7 MLLP protocol
-^^^^^^^^^^^^^^^^^
+### HL7 MLLP protocol
HL7 is often used with the HL7 MLLP protocol, which is a text based TCP
socket based protocol. This component ships with a Mina and Netty4 Codec
@@ -66,9 +64,7 @@ the HL7 message content.
segment terminators. The HAPI library requires the use of `\r`.
|=======================================================================
-[[HL7-ExposinganHL7listenerusingMina]]
-Exposing an HL7 listener using Mina
-+++++++++++++++++++++++++++++++++++
+#### Exposing an HL7 listener using Mina
In the Spring XML file, we configure a mina2 endpoint to listen for HL7
requests using TCP on port `8888`:
@@ -128,9 +124,7 @@ public class PatientLookupService {
}
----------------------------------------------------------------------------------------------------
-[[HL7-ExposinganHL7listenerusingNetty]]
-Exposing an HL7 listener using Netty (available from Camel 2.15 onwards)
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Exposing an HL7 listener using Netty (available from Camel 2.15 onwards)
In the Spring XML file, we configure a netty4 endpoint to listen for HL7
requests using TCP on port `8888`:
@@ -160,9 +154,7 @@ consumer, as this Java DSL example illustrates:
from("hl7NettyListener").beanRef("patientLookupService");
-------------------------------------------------------------
-[[HL7-HL7Modelusingjava.lang.Stringorbyte]]
-HL7 Model using java.lang.String or byte[]
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### HL7 Model using java.lang.String or byte[]
The HL7 MLLP codec uses plain String as its data format. Camel uses its
link:type-converter.html[Type Converter] to convert to/from strings to
@@ -174,9 +166,7 @@ plain�`byte[]` as its data format by setting the `produceString`
property to false. The Type Converter is also capable of converting
the�`byte[]` to/from HAPI HL7 model objects.
-[[HL7-HL7v2ModelusingHAPI]]
-HL7v2 Model using HAPI
-^^^^^^^^^^^^^^^^^^^^^^
+### HL7v2 Model using HAPI
The HL7v2 model uses Java objects from the HAPI library. Using this
library, you can encode and decode from the EDI format (ER7) that is
@@ -212,9 +202,7 @@ QRY_A19 msg = exchange.getIn().getBody(QRY_A19.class);
String patientId = msg.getQRD().getWhoSubjectFilter(0).getIDNumber().getValue();
--------------------------------------------------------------------------------
-[[HL7-HL7DataFormat]]
-HL7 DataFormat
-^^^^^^^^^^^^^^
+### HL7 DataFormat
The link:hl7.html[HL7] component ships with a HL7 data format that can
be used to marshal or unmarshal HL7 model objects.
@@ -300,9 +288,7 @@ object:
from("jms:queue:hl7out").unmarshal().hl7().to("patientLookupService");
------------------------------------------------------------------------
-[[HL7-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
The unmarshal operation adds these fields from the MSH segment as
headers on the Camel message:
@@ -343,9 +329,7 @@ that was used to parse the message
All headers except�`CamelHL7Context `are `String` types. If a header
value is missing, its value is `null`.
-[[HL7-Options]]
-Options
-^^^^^^^
+### Options
The HL7 Data Format supports the following options:
@@ -369,9 +353,7 @@ custom ValidationContext etc. This gives you full control over the HL7
parsing and rendering process.
|=======================================================================
-[[HL7-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use HL7 in your Camel routes you'll need to add a dependency on
*camel-hl7* listed above, which implements this data format.
@@ -434,9 +416,7 @@ repository].
</dependency>
-------------------------------------------
-[[HL7-Terserlanguage]]
-Terser language
-^^^^^^^^^^^^^^^
+### Terser language
http://hl7api.sourceforge.net[HAPI] provides a
http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/util/Terser.html[Terser]
@@ -463,9 +443,7 @@ import static org.apache.camel.component.hl7.HL7.terser;
.to("mock:test2");
--------------------------------------------------------------------------------------------------
-[[HL7-HL7Validationpredicate]]
-HL7 Validation predicate
-^^^^^^^^^^^^^^^^^^^^^^^^
+### HL7 Validation predicate
Often it is preferable to first parse a HL7v2 message and in a separate
step validate it against a HAPI
@@ -488,9 +466,7 @@ import ca.uhn.hl7v2.validation.impl.DefaultValidation;
.to("mock:test1");
----------------------------------------------------------------------
-[[HL7-HL7ValidationpredicateusingtheHapiContext]]
-HL7 Validation predicate using the HapiContext (Camel 2.14)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### HL7 Validation predicate using the HapiContext (Camel 2.14)
The HAPI Context is always configured with a
http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/validation/ValidationContext.html[ValidationContext]
@@ -533,9 +509,7 @@ import static org.apache.camel.component.hl7.HL7.messageConforms
�
-[[HL7-HL7Acknowledgementexpression]]
-HL7 Acknowledgement expression
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### HL7 Acknowledgement expression
A common task in HL7v2 processing is to generate an acknowledgement
message as response to an incoming HL7v2 message, e.g. based on a
@@ -564,9 +538,7 @@ import ca.uhn.hl7v2.validation.impl.DefaultValidation;
.transform(ack())
------------------------------------------------------------------------------------------
-[[HL7-MoreSamples]]
-More Samples
-^^^^^^^^^^^^
+### More Samples
In the following example, a plain `String` HL7 request is sent to an HL7
listener that sends back a response:
@@ -584,12 +556,9 @@ the example above.
�
-[[HL7-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-hl7/src/main/docs/terser-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hl7/src/main/docs/terser-language.adoc b/components/camel-hl7/src/main/docs/terser-language.adoc
index c176659..8d9e340 100644
--- a/components/camel-hl7/src/main/docs/terser-language.adoc
+++ b/components/camel-hl7/src/main/docs/terser-language.adoc
@@ -1,7 +1,5 @@
-# HL7 Terser Language
-[[HL7-Terserlanguage]]
-Terser language
-^^^^^^^^^^^^^^^
+## HL7 Terser Language
+### Terser language
http://hl7api.sourceforge.net[HAPI] provides a
http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/util/Terser.html[Terser]
@@ -28,9 +26,7 @@ import static org.apache.camel.component.hl7.HL7.terser;
.to("mock:test2");
--------------------------------------------------------------------------------------------------
-[[HL7-Terserlanguage-options]]
-Terser Language options
-^^^^^^^^^^^^^^^^^^^^^^^
+### Terser Language options
// language options: START
The HL7 Terser language supports 1 options which are listed below.
@@ -44,5 +40,4 @@ The HL7 Terser language supports 1 options which are listed below.
| trim | true | Boolean | Whether to trim the value to remove leading and trailing whitespaces and line breaks
|=======================================================================
{% endraw %}
-// language options: END
-
+// language options: END
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-http/src/main/docs/http-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-http/src/main/docs/http-component.adoc b/components/camel-http/src/main/docs/http-component.adoc
index f1fe9a5..4f404ee 100644
--- a/components/camel-http/src/main/docs/http-component.adoc
+++ b/components/camel-http/src/main/docs/http-component.adoc
@@ -1,4 +1,4 @@
-# HTTP Component
+## HTTP Component
The *http:* component provides HTTP based link:endpoint.html[endpoints]
for consuming external HTTP resources (as a client to call external
@@ -17,9 +17,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[HTTP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------------------------------------------
@@ -37,9 +35,7 @@ route, you can use the link:jetty.html[Jetty Component] or the
link:servlet.html[Servlet Component]
-[[HTTP-Examples]]
-Examples
-^^^^^^^^
+### Examples
Call the url with the body using POST and return response as out
message. If body is null call URL using GET and return response as out
@@ -110,9 +106,7 @@ from("direct:start")
<to uri="mock:results"/>
----------------------------------------
-[[HTTP-HttpOptions]]
-Http Options
-^^^^^^^^^^^^
+### Http Options
@@ -186,9 +180,7 @@ The HTTP component supports 26 endpoint options which are listed below:
-[[HTTP-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -233,18 +225,14 @@ default value "HTTP/1.1"
The header name above are constants. For the spring DSL you have to use
the value of the constant instead of the name.
-[[HTTP-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
Camel will store the HTTP response from the external server on the OUT
body. All headers from the IN message will be copied to the OUT message,
so headers are preserved during routing. Additionally Camel will add the
HTTP response headers as well to the OUT message headers.
-[[HTTP-Responsecode]]
-Response code
-^^^^^^^^^^^^^
+### Response code
Camel will handle according to the HTTP response code:
@@ -264,9 +252,7 @@ codes. This allows you to get any response from the remote server. +
There is a sample below demonstrating this.
-[[HTTP-HttpOperationFailedException]]
-HttpOperationFailedException
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### HttpOperationFailedException
This exception contains the following information:
@@ -276,9 +262,7 @@ This exception contains the following information:
* Response body as a `java.lang.String`, if server provided a body as
response
-[[HTTP-CallingusingGETorPOST]]
-Calling using GET or POST
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Calling using GET or POST
The following algorithm is used to determine if either `GET` or `POST`
HTTP method should be used: +
@@ -288,9 +272,7 @@ HTTP method should be used: +
4. `POST` if there is data to send (body is not null). +
5. `GET` otherwise.
-[[HTTP-HowtogetaccesstoHttpServletRequestandHttpServletResponse]]
-How to get access to HttpServletRequest and HttpServletResponse
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get access to HttpServletRequest and HttpServletResponse
You can get access to these two using the Camel type converter system
using
@@ -301,20 +283,14 @@ HttpServletRequest request = exchange.getIn().getBody(HttpServletRequest.class);
HttpServletRequest response = exchange.getIn().getBody(HttpServletResponse.class);
----------------------------------------------------------------------------------
-[[HTTP-Usingclienttimeout-SO_TIMEOUT]]
-Using client timeout - SO_TIMEOUT
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using client timeout - SO_TIMEOUT
See the unit test in
http://svn.apache.org/viewvc?view=rev&revision=781775[this link]
-[[HTTP-MoreExamples]]
-More Examples
-~~~~~~~~~~~~~
+### More Examples
-[[HTTP-ConfiguringaProxy]]
-Configuring a Proxy
-^^^^^^^^^^^^^^^^^^^
+### Configuring a Proxy
Java DSL
@@ -327,9 +303,7 @@ from("direct:start")
There is also support for proxy authentication via the `proxyUsername`
and `proxyPassword` options.
-[[HTTP-UsingproxysettingsoutsideofURI]]
-Using proxy settings outside of URI
-+++++++++++++++++++++++++++++++++++
+#### Using proxy settings outside of URI
Java DSL
@@ -353,9 +327,7 @@ Spring DSL
Options on Endpoint will override options on the context.
-[[HTTP-Configuringcharset]]
-Configuring charset
-^^^^^^^^^^^^^^^^^^^
+### Configuring charset
If you are using `POST` to send data you can configure the `charset`
@@ -364,9 +336,7 @@ If you are using `POST` to send data you can configure the `charset`
setProperty(Exchange.CHARSET_NAME, "iso-8859-1");
-------------------------------------------------
-[[HTTP-Samplewithscheduledpoll]]
-Sample with scheduled poll
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sample with scheduled poll
The sample polls the Google homepage every 10 seconds and write the page
to the file `message.html`:
@@ -378,9 +348,7 @@ from("timer://foo?fixedRate=true&delay=0&period=10000")
.setHeader(FileComponent.HEADER_FILE_NAME, "message.html").to("file:target/google");
----------------------------------------------------------------------------------------
-[[HTTP-GettingtheResponseCode]]
-Getting the Response Code
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Getting the Response Code
You can get the HTTP response code from the HTTP component by getting
the value from the Out message header with
@@ -397,9 +365,7 @@ the value from the Out message header with
int responseCode = out.getHeader(Exchange.HTTP_RESPONSE_CODE, Integer.class);
----------------------------------------------------------------------------------------------
-[[HTTP-UsingthrowExceptionOnFailure=falsetogetanyresponseback]]
-Using `throwExceptionOnFailure=false` to get any response back
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using `throwExceptionOnFailure=false` to get any response back
In the route below we want to route a message that we
link:content-enricher.html[enrich] with data returned from a remote HTTP
@@ -408,25 +374,19 @@ call. As we want any response from the remote server, we set the
the `AggregationStrategy`. As the code is based on a unit test that
simulates a HTTP status code 404, there is some assertion code etc.
-[[HTTP-DisablingCookies]]
-Disabling Cookies
-^^^^^^^^^^^^^^^^^
+### Disabling Cookies
To disable cookies you can set the HTTP Client to ignore cookies by
adding this URI option: +
`httpClient.cookiePolicy=ignoreCookies`
-[[HTTP-AdvancedUsage]]
-Advanced Usage
-^^^^^^^^^^^^^^
+### Advanced Usage
If you need more control over the HTTP producer you should use the
`HttpComponent` where you can set various classes to give you custom
behavior.
-[[HTTP-SettingMaxConnectionsPerHost]]
-Setting MaxConnectionsPerHost
-+++++++++++++++++++++++++++++
+#### Setting MaxConnectionsPerHost
The link:http.html[HTTP] Component has a
`org.apache.commons.httpclient.HttpConnectionManager` where you can
@@ -445,9 +405,7 @@ connection to 5 instead of the default of 2.
And then we can just use it as we normally do in our routes:
-[[HTTP-Usingpreemptiveauthentication]]
-Using preemptive authentication
-+++++++++++++++++++++++++++++++
+#### Using preemptive authentication
An end user reported that he had problem with authenticating with HTTPS.
The problem was eventually resolved when he discovered the HTTPS server
@@ -455,18 +413,14 @@ did not return a HTTP code 401 Authorization Required. The solution was
to set the following URI option:
`httpClient.authenticationPreemptive=true`
-[[HTTP-Acceptingselfsignedcertificatesfromremoteserver]]
-Accepting self signed certificates from remote server
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Accepting self signed certificates from remote server
See this
http://www.nabble.com/Using-HTTPS-in-camel-http-when-remote-side-has-self-signed-cert-td25916878.html[link]
from a mailing list discussion with some code to outline how to do this
with the Apache Commons HTTP API.
-[[HTTP-SettingupSSLforHTTPClient]]
-Setting up SSL for HTTP Client
-++++++++++++++++++++++++++++++
+#### Setting up SSL for HTTP Client
[[HTTP-UsingtheJSSEConfigurationUtility]]
Using the JSSE Configuration Utility
@@ -559,14 +513,11 @@ If you are doing this using the Spring DSL, you can specify your
As long as you implement the HttpClientConfigurer and configure your
keystore and truststore as described above, it will work fine.
-[[HTTP-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:jetty.html[Jetty]
-
+* link:jetty.html[Jetty]
\ No newline at end of file
[10/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-cxf/src/main/docs/cxfrs-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-cxf/src/main/docs/cxfrs-component.adoc b/components/camel-cxf/src/main/docs/cxfrs-component.adoc
index d3b9e7d..d3ffe40 100644
--- a/components/camel-cxf/src/main/docs/cxfrs-component.adoc
+++ b/components/camel-cxf/src/main/docs/cxfrs-component.adoc
@@ -1,4 +1,4 @@
-# CXF-RS Component
+## CXF-RS Component
[Note]
====
@@ -29,9 +29,7 @@ for this component:
</dependency>
-------------------------------------------------------------------------------------
-[[CXFRS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------
@@ -55,9 +53,7 @@ For either style above, you can append options to the URI as follows:
cxfrs:bean:cxfEndpoint?resourceClasses=org.apache.camel.rs.Example
------------------------------------------------------------------
-[[CXFRS-Options]]
-Options
-^^^^^^^
+### Options
@@ -129,9 +125,7 @@ http://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/main/resour
file] and https://cwiki.apache.org/CXF20DOC/JAX-RS[CXF JAX-RS
documentation] for more information.
-[[CXFRS-HowtoconfiguretheRESTendpointinCamel]]
-How to configure the REST endpoint in Camel
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to configure the REST endpoint in Camel
In
http://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/main/resources/schema/cxfEndpoint.xsd[camel-cxf
@@ -139,9 +133,7 @@ schema file], there are two elements for the REST endpoint definition.
*cxf:rsServer* for REST consumer, *cxf:rsClient* for REST producer. +
You can find a Camel REST service route configuration example here.
-[[CXFRS-HowtooverridetheCXFproduceraddressfrommessageheader]]
-How to override the CXF producer address from message header
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to override the CXF producer address from message header
The�`camel-cxfrs`�producer supports to override the services address by
setting the message with the key of "CamelDestinationOverrideUrl".
@@ -152,9 +144,7 @@ setting the message with the key of "CamelDestinationOverrideUrl".
exchange.getIn().setHeader(Exchange.DESTINATION_OVERRIDE_URL, constant(getServiceAddress()));
----------------------------------------------------------------------------------------------
-[[CXFRS-ConsumingaRESTRequest-SimpleBindingStyle]]
-Consuming a REST Request - Simple Binding Style
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Consuming a REST Request - Simple Binding Style
*Available as of Camel 2.11*
@@ -192,9 +182,7 @@ respected and it becomes the final response.
* In all cases, Camel headers permitted by custom or default
`HeaderFilterStrategy` are added to the HTTP response.
-[[CXFRS-EnablingtheSimpleBindingStyle]]
-Enabling the Simple Binding Style
-+++++++++++++++++++++++++++++++++
+#### Enabling the Simple Binding Style
This binding style can be activated by setting the `bindingStyle`
parameter in the consumer endpoint to value `SimpleConsumer`:
@@ -205,9 +193,7 @@ parameter in the consumer endpoint to value `SimpleConsumer`:
.to("log:TEST?showAll=true");
---------------------------------------------------------
-[[CXFRS-Examplesofrequestbindingwithdifferentmethodsignatures]]
-Examples of request binding with different method signatures
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Examples of request binding with different method signatures
Below is a list of method signatures along with the expected result from
the Simple binding.
@@ -239,9 +225,7 @@ as the IN message body.
The DataHandler is unwrapped from the MessageContentsList and preserved
as the IN message body.
-[[CXFRS-MoreexamplesoftheSimpleBindingStyle]]
-More examples of the Simple Binding Style
-+++++++++++++++++++++++++++++++++++++++++
+#### More examples of the Simple Binding Style
Given a JAX-RS resource class with this method:
@@ -290,9 +274,7 @@ For more examples on how to process requests and write responses can be
found
https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/jaxrs/simplebinding/[here].
-[[CXFRS-ConsumingaRESTRequest-DefaultBindingStyle]]
-Consuming a REST Request - Default Binding Style
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Consuming a REST Request - Default Binding Style
The�https://cwiki.apache.org/CXF20DOC/JAX-RS[CXF JAXRS front end]
implements the https://jsr311.java.net/[JAX-RS (JSR-311) API], so we can
@@ -327,9 +309,7 @@ set on the Camel exchange and the route execution will continue as
usual. This can be useful for integrating the existing JAX-RS implementations into Camel routes and
for post-processing JAX-RS Responses in custom processors.
-[[CXFRS-HowtoinvoketheRESTservicethroughcamel-cxfrsproducer]]
-How to invoke the REST service through camel-cxfrs producer
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to invoke the REST service through camel-cxfrs producer
The�https://cwiki.apache.org/CXF20DOC/JAX-RS[CXF JAXRS front end]
implements
@@ -367,4 +347,4 @@ Index: 20, Size: 20
To support the Dynamical routing, you can override the URI's query
parameters by using the CxfConstants.CAMEL_CXF_RS_QUERY_MAP header to
-set the parameter map for it.
+set the parameter map for it.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-disruptor/src/main/docs/disruptor-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-disruptor/src/main/docs/disruptor-component.adoc b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
index f3d7bce..7d67f52 100644
--- a/components/camel-disruptor/src/main/docs/disruptor-component.adoc
+++ b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
@@ -1,4 +1,4 @@
-# Disruptor Component
+## Disruptor Component
*Available as of Camel 2.12*
@@ -61,9 +61,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Disruptor-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------------
@@ -88,9 +86,7 @@ across contexts in case of +
?option=value&option=value&\u2026
------------------------------
-[[Disruptor-Options]]
-Options
-^^^^^^^
+### Options
All the following options are valid for both the **disruptor:** and
**disruptor-vm:** components.
@@ -145,9 +141,7 @@ The Disruptor component supports 13 endpoint options which are listed below:
// endpoint options: END
-[[Disruptor-Waitstrategies]]
-Wait strategies
-^^^^^^^^^^^^^^^
+### Wait strategies
The wait strategy effects the type of waiting performed by the consumer
threads that are currently waiting for the next exchange to be
@@ -176,9 +170,7 @@ barrier after an initially spinning. |This strategy is a good compromise between
without incurring significant latency spikes.
|=======================================================================
-[[Disruptor-UseofRequestReply]]
-Use of Request Reply
-^^^^^^^^^^^^^^^^^^^^
+### Use of Request Reply
The Disruptor component supports using link:request-reply.html[Request
Reply], where the caller will wait for the Async route to complete. For
@@ -196,9 +188,7 @@ buffer. As it is a link:request-reply.html[Request Reply] message, we
wait for the response. When the consumer on the _disruptor:input_ buffer
is complete, it copies the response to the original message response.
-[[Disruptor-Concurrentconsumers]]
-Concurrent consumers
-^^^^^^^^^^^^^^^^^^^^
+### Concurrent consumers
By default, the Disruptor endpoint uses a single consumer thread, but
you can configure it to use concurrent consumer threads. So instead of
@@ -214,9 +204,7 @@ increase/shrink dynamically at runtime depending on load, whereas the
number of concurrent consumers is always fixed and supported by the
Disruptor internally so performance will be higher.
-[[Disruptor-Threadpools]]
-Thread pools
-^^^^^^^^^^^^
+### Thread pools
Be aware that adding a thread pool to a Disruptor endpoint by doing
something like:
@@ -233,9 +221,7 @@ of the performance gains achieved by using the Disruptor. Instead, it is
advices to directly configure number of threads that process messages on
a Disruptor endpoint using the concurrentConsumers option.
-[[Disruptor-Sample]]
-Sample
-^^^^^^
+### Sample
In the route below we use the Disruptor to send the request to this
async queue to be able to send a fire-and-forget message for further
@@ -268,9 +254,7 @@ another thread for further processing. Since this is from a unit test,
it will be sent to a mock endpoint where we can do assertions in the
unit test.
-[[Disruptor-UsingmultipleConsumers]]
-Using multipleConsumers
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using multipleConsumers
In this example we have defined two consumers and registered them as
spring beans.
@@ -309,9 +293,7 @@ public class FooEventConsumer {
}
-------------------------------------------
-[[Disruptor-Extractingdisruptorinformation]]
-Extracting disruptor information
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Extracting disruptor information
If needed, information such as buffer size, etc. can be obtained without
using JMX in this fashion:
@@ -320,4 +302,4 @@ using JMX in this fashion:
--------------------------------------------------------------------
DisruptorEndpoint disruptor = context.getEndpoint("disruptor:xxxx");
int size = disruptor.getBufferSize();
---------------------------------------------------------------------
+--------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-dns/src/main/docs/dns-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-dns/src/main/docs/dns-component.adoc b/components/camel-dns/src/main/docs/dns-component.adoc
index 1a0a1ec..1b232d9 100644
--- a/components/camel-dns/src/main/docs/dns-component.adoc
+++ b/components/camel-dns/src/main/docs/dns-component.adoc
@@ -1,4 +1,4 @@
-# DNS Component
+## DNS Component
*Available as of Camel 2.7*
@@ -31,9 +31,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[DNS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
The URI scheme for a DNS component is as follows
@@ -44,9 +42,7 @@ dns://operation[?options]
This component only supports producers.
-[[DNS-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -69,9 +65,7 @@ The DNS component supports 2 endpoint options which are listed below:
// endpoint options: END
-[[DNS-Headers]]
-Headers
-^^^^^^^
+### Headers
[width="100%",cols="10%,10%,10%,70%",options="header",]
|=======================================================================
@@ -93,13 +87,9 @@ Optional.
one specified by the OS will be used. Optional.
|=======================================================================
-[[DNS-Examples]]
-Examples
-^^^^^^^^
+### Examples
-[[DNS-IPlookup]]
-IP lookup
-+++++++++
+#### IP lookup
[source,xml]
--------------------------------------
@@ -114,9 +104,7 @@ This looks up a domain's IP. For example, www.example.com resolves to
The IP address to lookup must be provided in the header with key
`"dns.domain"`.
-[[DNS-DNSlookup]]
-DNS lookup
-++++++++++
+#### DNS lookup
[source,xml]
--------------------------------------
@@ -130,9 +118,7 @@ This returns a set of DNS records associated with a domain. +
The name to lookup must be provided in the header with key
`"dns.name"`.
-[[DNS-DNSDig]]
-DNS Dig
-+++++++
+#### DNS Dig
Dig is a Unix command-line utility to run DNS queries.
@@ -146,12 +132,9 @@ Dig is a Unix command-line utility to run DNS queries.
The query must be provided in the header with key `"dns.query"`.
-[[DNS-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-docker/src/main/docs/docker-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-docker/src/main/docs/docker-component.adoc b/components/camel-docker/src/main/docs/docker-component.adoc
index 41d634d..d0ab1f1 100644
--- a/components/camel-docker/src/main/docs/docker-component.adoc
+++ b/components/camel-docker/src/main/docs/docker-component.adoc
@@ -1,4 +1,4 @@
-# Docker Component
+## Docker Component
*Available as of Camel 2.15*
@@ -10,9 +10,7 @@ https://docs.docker.com/reference/api/docker_remote_api[Docker Remote
API].
-[[Docker-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------
@@ -21,9 +19,7 @@ docker://[operation]?[options]
Where *operation* is the specific action to perform on Docker.
-[[Docker-Options]]
-General Options
-^^^^^^^^^^^^^^^
+### General Options
// component options: START
The Docker component supports 1 options which are listed below.
@@ -71,9 +67,7 @@ The Docker component supports 20 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[Docker-HeaderStrategy]]
-Header Strategy
-^^^^^^^^^^^^^^^
+### Header Strategy
All URI option can be passed as Header properties. Values found in a
message header take precedence over URI parameters. A header property
@@ -88,9 +82,7 @@ below
|=======================================================================
-[[Docker-Examples]]
-Examples
-^^^^^^^^
+### Examples
The following example consumes events from Docker:
@@ -107,9 +99,7 @@ from("docker://info?host=192.168.59.103&port=2375").to("log:info");
-------------------------------------------------------------------
-[[Docker-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Docker in your Camel routes you need to add a dependency on
*camel-docker*, which implements the component.
@@ -125,4 +115,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-docker</artifactId>
<version>x.x.x</version>
</dependency>
--------------------------------------
+-------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-dozer/src/main/docs/dozer-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-dozer/src/main/docs/dozer-component.adoc b/components/camel-dozer/src/main/docs/dozer-component.adoc
index f29de89..f891716 100644
--- a/components/camel-dozer/src/main/docs/dozer-component.adoc
+++ b/components/camel-dozer/src/main/docs/dozer-component.adoc
@@ -1,4 +1,4 @@
-# Dozer Component
+## Dozer Component
The�*dozer:*�component provides the ability to map between Java beans
using the http://camel.apache.org/dozer-type-conversion.html[Dozer]
@@ -30,9 +30,7 @@ following dependency to their�`pom.xml`:
</dependency>
------------------------------------------------------------
-[[Dozer-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
The Dozer component only supports producer endpoints.
@@ -53,9 +51,7 @@ from("direct:orderInput").
to("direct:orderOutput");
---------------------------------------------------------------------------------------
-[[Dozer-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The Dozer component has no options.
@@ -80,9 +76,7 @@ The Dozer component supports 8 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[Dozer-UsingDataFormatswithDozer]]
-Using Data Formats with Dozer
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using Data Formats with Dozer
Dozer does not support non-Java sources and targets for mappings, so it
cannot, for example, map an XML document to a Java object on its own.
@@ -116,9 +110,7 @@ using a JAXB data format and marshal the mapping output using Jackson.
<endpoint uri="dozer:xml2json?marshalId=myjson&unmarshalId=myjaxb&targetModel=org.example.Order"/>
----------------------------------------------------------------------------------------------------------
-[[Dozer-ConfiguringDozer]]
-Configuring Dozer
-^^^^^^^^^^^^^^^^^
+### Configuring Dozer
All Dozer endpoints require a Dozer mapping configuration file which
defines mappings between source and target objects. �The component will
@@ -141,17 +133,13 @@ of�`org.apache.camel.converter.dozer.DozerBeanMapperConfiguration`.
</bean>
------------------------------------------------------------------------------------------
-[[Dozer-MappingExtensions]]
-Mapping Extensions
-^^^^^^^^^^^^^^^^^^
+### Mapping Extensions
The Dozer component implements a number of extensions to the Dozer
mapping framework as custom converters. �These converters implement
mapping functions that are not supported directly by Dozer itself.
-[[Dozer-VariableMappings]]
-Variable Mappings
-+++++++++++++++++
+#### Variable Mappings
Variable mappings allow you to map the value of a variable definition
within a Dozer configuration into a target field instead of using the
@@ -182,9 +170,7 @@ class into your target field of choice:
</mappings>
--------------------------------------------------------------------------------------------------------
-[[Dozer-CustomMappings]]
-Custom Mappings
-+++++++++++++++
+#### Custom Mappings
Custom mappings allow you to define your own logic for how a source
field is mapped to a target field. �They are similar in function to
@@ -235,9 +221,7 @@ public class CustomMapper {
</mappings>
--------------------------------------------------------------------------------------------------------
-[[Dozer-ExpressionMappings]]
-Expression Mappings
-+++++++++++++++++++
+#### Expression Mappings
Expression mappings allow you to use the powerful
http://camel.apache.org/languages.html[language] capabilities of Camel
@@ -273,5 +257,4 @@ An example of mapping a message header into a target field:
Note that any properties within your expression must be escaped with "\"
to prevent an error when Dozer attempts to resolve variable values
-defined using the EL.
-
+defined using the EL.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-drill/src/main/docs/drill-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-drill/src/main/docs/drill-component.adoc b/components/camel-drill/src/main/docs/drill-component.adoc
index 4577c31..375aeb6 100644
--- a/components/camel-drill/src/main/docs/drill-component.adoc
+++ b/components/camel-drill/src/main/docs/drill-component.adoc
@@ -1,4 +1,4 @@
-# Drill Component
+## Drill Component
*Available as of Camel 2.18*
@@ -19,9 +19,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Drill-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------------
@@ -31,15 +29,11 @@ drill://host[?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Drill-Producer]]
-Drill Producer
-^^^^^^^^^^^^^
+### Drill Producer
The producer execute query using *CamelDrillQuery* header and put results into body.
-[[Drill-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The Drill component has no options.
@@ -64,12 +58,9 @@ The Drill component supports 6 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[Drill-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-dropbox/src/main/docs/dropbox-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-dropbox/src/main/docs/dropbox-component.adoc b/components/camel-dropbox/src/main/docs/dropbox-component.adoc
index 5774154..950890e 100644
--- a/components/camel-dropbox/src/main/docs/dropbox-component.adoc
+++ b/components/camel-dropbox/src/main/docs/dropbox-component.adoc
@@ -1,4 +1,4 @@
-# Dropbox Component
+## Dropbox Component
*Available as of Camel 2.14*
@@ -26,9 +26,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Dropbox-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------
@@ -38,9 +36,7 @@ dropbox://[operation]?[options]
Where *operation* is the specific action (typically is a CRUD action) to
perform on Dropbox remote folder.
-[[Dropbox-Operations]]
-Operations
-^^^^^^^^^^
+### Operations
[width="100%",cols="40%,60%",options="header",]
|=======================================================================
@@ -60,9 +56,7 @@ Operations
*Operations* require additional options to work, some are mandatory for
the specific operation.
-[[Dropbox-Options]]
-Options
-^^^^^^^
+### Options
In order to work with Dropbox API you need to obtain an�*accessToken*
and a *clientIdentifier.* +
@@ -98,9 +92,7 @@ The Dropbox component supports 13 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[Dropbox-Deloperation]]
-Del operation
-^^^^^^^^^^^^^
+### Del operation
Delete files on Dropbox.
@@ -115,9 +107,7 @@ Below are listed the options for this operation:
|`remotePath` |`true` |Folder or file to delete on Dropbox
|=======================================================================
-[[Dropbox-Samples]]
-Samples
-+++++++
+#### Samples
[source,java]
-------------------------------
@@ -126,9 +116,7 @@ from("direct:start").to("dropbox://del?accessToken=XXX&clientIdentifier=XXX&remo
from("direct:start").to("dropbox://del?accessToken=XXX&clientIdentifier=XXX&remotePath=/root/folder1/file1.tar.gz").to("mock:result");
-------------------------------
-[[Dropbox-ResultMessageHeaders]]
-Result Message Headers
-++++++++++++++++++++++
+#### Result Message Headers
The following headers are set on message result:
@@ -139,9 +127,7 @@ The following headers are set on message result:
|`DELETED_PATH` |name of the path deleted on dropbox
|=======================================================================
-[[Dropbox-ResultMessageBody]]
-Result Message Body
-+++++++++++++++++++
+#### Result Message Body
The following objects are set on message body result:
@@ -152,9 +138,7 @@ The following objects are set on message body result:
|`String` |name of the path deleted on dropbox
|=======================================================================
-[[Dropbox-Getoperation]]
-Get (download) operation
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Get (download) operation
Download files from Dropbox.
@@ -169,9 +153,7 @@ Below are listed the options for this operation:
|`remotePath` |`true` |Folder or file to download from Dropbox
|=======================================================================
-[[Dropbox-Samples.1]]
-Samples
-+++++++
+#### Samples
[source,java]
-------------------------------
@@ -182,9 +164,7 @@ from("direct:start").to("dropbox://get?accessToken=XXX&clientIdentifier=XXX&remo
from("dropbox://get?accessToken=XXX&clientIdentifier=XXX&remotePath=/root/folder1").to("file:///home/kermit/");
-------------------------------
-[[Dropbox-ResultMessageHeaders.1]]
-Result Message Headers
-++++++++++++++++++++++
+#### Result Message Headers
The following headers are set on message result:
@@ -197,9 +177,7 @@ The following headers are set on message result:
|`DOWNLOADED_FILES` |in case of multiple files download, path of the remote files downloaded
|=======================================================================
-[[Dropbox-ResultMessageBody.1]]
-Result Message Body
-+++++++++++++++++++
+#### Result Message Body
The following objects are set on message body result:
@@ -214,9 +192,7 @@ remote file downloaded and as value the stream representing the file
downloaded
|=======================================================================
-[[Dropbox-Moveoperation]]
-Move operation
-^^^^^^^^^^^^^^
+### Move operation
Move files on Dropbox between one folder to another.
@@ -233,18 +209,14 @@ Below are listed the options for this operation:
|`newRemotePath` |`true` |Destination file or folder
|=======================================================================
-[[Dropbox-Samples.2]]
-Samples
-+++++++
+#### Samples
[source,java]
-------------------------------
from("direct:start").to("dropbox://move?accessToken=XXX&clientIdentifier=XXX&remotePath=/root/folder1&newRemotePath=/root/folder2").to("mock:result");
-------------------------------
-[[Dropbox-ResultMessageHeaders.2]]
-Result Message Headers
-++++++++++++++++++++++
+#### Result Message Headers
The following headers are set on message result:
@@ -255,9 +227,7 @@ The following headers are set on message result:
|`MOVED_PATH` |name of the path moved on dropbox
|=======================================================================
-[[Dropbox-ResultMessageBody.2]]
-Result Message Body
-+++++++++++++++++++
+#### Result Message Body
The following objects are set on message body result:
@@ -268,9 +238,7 @@ The following objects are set on message body result:
|`String` |name of the path moved on dropbox
|=======================================================================
-[[Dropbox-Putoperation]]
-Put (upload) operation
-^^^^^^^^^^^^^^^^^^^^^^
+### Put (upload) operation
Upload files on Dropbox.
@@ -293,9 +261,7 @@ dropbox, this will be overwritten.
will upload the file on a remote path equal to the local path.
|=======================================================================
-[[Dropbox-Samples.3]]
-Samples
-+++++++
+#### Samples
[source,java]
-------------------------------
@@ -304,9 +270,7 @@ from("direct:start").to("dropbox://put?accessToken=XXX&clientIdentifier=XXX&uplo
from("direct:start").to("dropbox://put?accessToken=XXX&clientIdentifier=XXX&uploadMode=add&localPath=/root/folder1&remotePath=/root/folder2").to("mock:result");
-------------------------------
-[[Dropbox-ResultMessageHeaders.3]]
-Result Message Headers
-++++++++++++++++++++++
+#### Result Message Headers
The following headers are set on message result:
@@ -319,9 +283,7 @@ The following headers are set on message result:
|`UPLOADED_FILES` |in case of multiple files upload, string with the remote paths uploaded
|=======================================================================
-[[Dropbox-ResultMessageBody.3]]
-Result Message Body
-+++++++++++++++++++
+#### Result Message Body
The following objects are set on message body result:
@@ -336,9 +298,7 @@ remote file uploaded and as value the result of the upload operation, OK
or KO
|=======================================================================
-[[Dropbox-Searchoperation]]
-Search operation
-^^^^^^^^^^^^^^^^
+### Search operation
Search inside a remote Dropbox folder including its sub directories.
@@ -357,9 +317,7 @@ if it contains all the sub-strings. If this option is not set, all files
will be matched.
|=======================================================================
-[[Dropbox-Samples.4]]
-Samples
-+++++++
+#### Samples
[source,java]
-------------------------------
@@ -368,9 +326,7 @@ from("dropbox://search?accessToken=XXX&clientIdentifier=XXX&remotePath=/XXX&quer
from("direct:start").to("dropbox://search?accessToken=XXX&clientIdentifier=XXX&remotePath=/XXX").to("mock:result");
-------------------------------
-[[Dropbox-ResultMessageHeaders.4]]
-Result Message Headers
-++++++++++++++++++++++
+#### Result Message Headers
The following headers are set on message result:
@@ -381,9 +337,7 @@ The following headers are set on message result:
|`FOUNDED_FILES` |list of file path founded
|=======================================================================
-[[Dropbox-ResultMessageBody.4]]
-Result Message Body
-+++++++++++++++++++
+#### Result Message Body
The following objects are set on message body result:
@@ -397,4 +351,4 @@ Dropbox documentation,
link:http://dropbox.github.io/dropbox-sdk-java/api-docs/v1.7.x/com/dropbox/core/DbxEntry.html[http://dropbox.github.io/dropbox-sdk-java/api-docs/v1.7.x/com/dropbox/core/DbxEntry.html]
-�
+�
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ehcache/src/main/docs/ehcache-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ehcache/src/main/docs/ehcache-component.adoc b/components/camel-ehcache/src/main/docs/ehcache-component.adoc
index 6292610..5cec94a 100644
--- a/components/camel-ehcache/src/main/docs/ehcache-component.adoc
+++ b/components/camel-ehcache/src/main/docs/ehcache-component.adoc
@@ -1,4 +1,4 @@
-# Ehcache Component
+## Ehcache Component
*Available as of Camel 2.18.x*
@@ -23,9 +23,7 @@ their�`pom.xml`�for this component:
</dependency>
------------------------------------------------------------
-[[Ehcache-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------------
@@ -35,9 +33,7 @@ ehcache://cacheName[?options]
You can append query options to the URI in the following
format,�`?option=value&option=#beanRef&...`
-[[Ehcache-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -74,9 +70,7 @@ The Ehcache component supports 16 endpoint options which are listed below:
// endpoint options: END
-[[Ehcache-MessageHeadersCamel]]
-Message Headers Camel�
-++++++++++++++++++++++
+#### Message Headers Camel�
�
[width="100%",cols="10%,10%,80%",options="header",]
@@ -115,9 +109,7 @@ Object used for comparison for actions like REPLACE
|CamelEhcacheEventType |EventType |The type of event received
|=======================================================================
-[[Ehcache-Ehcachebasedidempotentrepositoryexample:]]
-Ehcache based idempotent repository example:
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Ehcache based idempotent repository example:
[source,java]
------------------------------------------------------------------------------------------------
@@ -131,9 +123,7 @@ from("direct:in")
�
-[[Ehcache-Ehcachebasedaggregationrepositoryexample:]]
-Ehcache based aggregation repository example:
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Ehcache based aggregation repository example:
[source,java]
---------------------------------------------------------------------------------------------------------------------------------
@@ -204,4 +194,4 @@ public class EhcacheAggregationRepositoryRoutesTest extends CamelTestSupport {
return repository;
}
}
----------------------------------------------------------------------------------------------------------------------------------
+---------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ejb/src/main/docs/ejb-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ejb/src/main/docs/ejb-component.adoc b/components/camel-ejb/src/main/docs/ejb-component.adoc
index fb5059d..e807a0a 100644
--- a/components/camel-ejb/src/main/docs/ejb-component.adoc
+++ b/components/camel-ejb/src/main/docs/ejb-component.adoc
@@ -1,4 +1,4 @@
-# EJB Component
+## EJB Component
*Available as of Camel 2.4*
@@ -17,9 +17,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[EJB-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------
@@ -29,9 +27,7 @@ ejb:ejbName[?options]
Where *ejbName* can be any string which is used to look up the EJB in
the Application Server JNDI link:registry.html[Registry]
-[[EJB-Options]]
-Options
-^^^^^^^
+### Options
@@ -71,9 +67,7 @@ The EJB component supports 6 endpoint options which are listed below:
// endpoint options: END
-[[EJB-BeanBinding]]
-Bean Binding
-^^^^^^^^^^^^
+### Bean Binding
How bean methods to be invoked are chosen (if they are not specified
explicitly through the *method* parameter) and how parameter values are
@@ -82,9 +76,7 @@ link:bean-binding.html[Bean Binding] mechanism which is used throughout
all of the various link:bean-integration.html[Bean Integration]
mechanisms in Camel.
-[[EJB-Examples]]
-Examples
-^^^^^^^^
+### Examples
In the following examples we use the Greater EJB which is defined as
follows:
@@ -122,9 +114,7 @@ public class GreaterImpl implements GreaterLocal {
}
-------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[EJB-UsingJavaDSL]]
-Using Java DSL
-++++++++++++++
+#### Using Java DSL
In this example we want to invoke the `hello` method on the EJB. Since
this example is based on an unit test using Apache OpenEJB we have to
@@ -172,9 +162,7 @@ usually allows it to access the JNDI registry and lookup the
link:ejb.html[EJB]s. However if you need to access a application server on a remote JVM or
the likes, you have to prepare the properties beforehand.
-[[EJB-UsingSpringXML]]
-Using Spring XML
-++++++++++++++++
+#### Using Spring XML
And this is the same example using Spring XML instead:
@@ -207,9 +195,7 @@ Before we are ready to use link:ejb.html[EJB] in the Camel routes:
</camelContext>
-------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[EJB-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -217,5 +203,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:bean.html[Bean]
* link:bean-binding.html[Bean Binding]
-* link:bean-integration.html[Bean Integration]
-
+* link:bean-integration.html[Bean Integration]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-elasticsearch/src/main/docs/elasticsearch-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-elasticsearch/src/main/docs/elasticsearch-component.adoc b/components/camel-elasticsearch/src/main/docs/elasticsearch-component.adoc
index c7bbc39..650f41e 100644
--- a/components/camel-elasticsearch/src/main/docs/elasticsearch-component.adoc
+++ b/components/camel-elasticsearch/src/main/docs/elasticsearch-component.adoc
@@ -1,4 +1,4 @@
-# Elasticsearch Component
+## Elasticsearch Component
*Available as of Camel 2.11*
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[ElasticSearch-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------------
@@ -38,9 +36,7 @@ guide] for more details.
====
-[[ElasticSearch-EndpointOptions]]
-Endpoint Options
-^^^^^^^^^^^^^^^^
+### Endpoint Options
@@ -87,9 +83,7 @@ The Elasticsearch component supports 12 endpoint options which are listed below:
-[[ElasticSearch-MessageOperations]]
-Message Operations
-^^^^^^^^^^^^^^^^^^
+### Message Operations
The following ElasticSearch operations are currently supported. Simply
set an endpoint URI option or exchange header with a key of "operation"
@@ -131,9 +125,7 @@ returns a MultiSearchResponse object in the body
indexId in the body.
|=======================================================================
-[[ElasticSearch-IndexExample]]
-Index Example
-^^^^^^^^^^^^^
+### Index Example
Below is a simple INDEX example
@@ -161,21 +153,16 @@ map.put("content", "test");
String indexId = template.requestBody("direct:index", map, String.class);
-------------------------------------------------------------------------
-[[ElasticSearch-Formoreinformation,seetheseresources]]
-For more information, see these resources
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### For more information, see these resources
http://elasticsearch.org[ElasticSearch Main Site]
http://www.elasticsearch.org/guide/reference/java-api/[ElasticSearch
Java API]
-[[ElasticSearch-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-elsql/src/main/docs/elsql-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-elsql/src/main/docs/elsql-component.adoc b/components/camel-elsql/src/main/docs/elsql-component.adoc
index 035ff86..9d5582d 100644
--- a/components/camel-elsql/src/main/docs/elsql-component.adoc
+++ b/components/camel-elsql/src/main/docs/elsql-component.adoc
@@ -1,4 +1,4 @@
-# ElSQL Component
+## ElSQL Component
*Available as of Camel 2.16*
@@ -49,9 +49,7 @@ expression.
If a named parameter cannot be resolved, then an exception is thrown.
-[[ElSql-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The ElSQL component supports 4 options which are listed below.
@@ -129,9 +127,7 @@ The ElSQL component supports 48 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[ElSql-Resultofthequery]]
-Result of the query
-^^^^^^^^^^^^^^^^^^^
+### Result of the query
For `select` operations, the result is an instance of
`List<Map<String, Object>>` type, as returned by the
@@ -145,9 +141,7 @@ headers, it provides a concise syntax for querying a sequence or some
other small value into a header.� It is convenient to use outputHeader
and outputType together:
-[[ElSql-Headervalues]]
-Header values
-^^^^^^^^^^^^^
+### Header values
When performing `update` operations, the SQL Component stores the update
count in the following message headers:
@@ -163,9 +157,7 @@ count in the following message headers:
`Integer` object.
|=======================================================================
-[[ElSql-Sample]]
-Sample
-++++++
+#### Sample
In the given route below, we want to get all the projects from the
projects table. Notice the SQL query has 2 named parameters, :#lic and
@@ -217,9 +209,7 @@ assumes to have�`getLicense` and�`getMinimum` methods:
ORDER BY id
------------------------------------------------------------
-[[ElSql-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -228,5 +218,4 @@ See Also
* link:sql-component.html[SQL Component]
* link:mybatis.html[MyBatis]
-* link:jdbc.html[JDBC]
-
+* link:jdbc.html[JDBC]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-etcd/src/main/docs/etcd-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-etcd/src/main/docs/etcd-component.adoc b/components/camel-etcd/src/main/docs/etcd-component.adoc
index b5eb922..a76c186 100644
--- a/components/camel-etcd/src/main/docs/etcd-component.adoc
+++ b/components/camel-etcd/src/main/docs/etcd-component.adoc
@@ -1,4 +1,4 @@
-# etcd Component
+## etcd Component
+[[Etcd-Etcd]]
+Etcd
@@ -70,6 +70,4 @@ The etcd component supports 31 endpoint options which are listed below:
// component options: START
The etcd component has no options.
-// component options: END
-
-
+// component options: END
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc b/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc
index 9f67187..b056b18 100644
--- a/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc
+++ b/components/camel-eventadmin/src/main/docs/eventadmin-component.adoc
@@ -1,13 +1,11 @@
-# OSGi EventAdmin Component
+## OSGi EventAdmin Component
*Available in Camel 2.6*
The `eventadmin` component can be used in an OSGi environment to receive
OSGi EventAdmin events and process them.
-[[EventAdmin-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users need to add the following dependency to their `pom.xml`
@@ -23,9 +21,7 @@ Maven users need to add the following dependency to their `pom.xml`
where `${camel-version`} must be replaced by the actual version of Camel
(2.6.0 or higher).
-[[EventAdmin-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,xml]
--------------------------
@@ -34,9 +30,7 @@ eventadmin:topic[?options]
where `topic` is the name of the topic to listen too.
-[[EventAdmin-URIoptions]]
-URI options
-^^^^^^^^^^^
+### URI options
// component options: START
The OSGi EventAdmin component supports 1 options which are listed below.
@@ -69,24 +63,18 @@ The OSGi EventAdmin component supports 6 endpoint options which are listed below
{% endraw %}
// endpoint options: END
-[[EventAdmin-Messageheaders]]
-Message headers
-^^^^^^^^^^^^^^^
+### Message headers
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
|Name |Type |Message |Description
|=======================================================================
-[[EventAdmin-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
The `in` message body will be set to the received Event.
-[[EventAdmin-Exampleusage]]
-Example usage
-^^^^^^^^^^^^^
+### Example usage
[source,xml]
------------------------------
@@ -94,4 +82,4 @@ Example usage
<from uri="eventadmin:*"/>
<to uri="stream:out"/>
</route>
-------------------------------
+------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-exec/src/main/docs/exec-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-exec/src/main/docs/exec-component.adoc b/components/camel-exec/src/main/docs/exec-component.adoc
index ef9533f..9024ad2 100644
--- a/components/camel-exec/src/main/docs/exec-component.adoc
+++ b/components/camel-exec/src/main/docs/exec-component.adoc
@@ -1,12 +1,10 @@
-# Exec Component
+## Exec Component
*Available in Camel 2.3*
The `exec` component can be used to execute system commands.
-[[Exec-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users need to add the following dependency to their `pom.xml`
@@ -22,9 +20,7 @@ Maven users need to add the following dependency to their `pom.xml`
where `${camel-version`} must be replaced by the actual version of Camel
(2.3.0 or higher).
-[[Exec-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,xml]
---------------------------
@@ -35,9 +31,7 @@ where `executable` is the name, or file path, of the system command that
will be executed. If executable name is used (e.g. `exec:java`), the
executable must in the system path.
-[[Exec-URIoptions]]
-URI options
-^^^^^^^^^^^
+### URI options
// component options: START
The Exec component has no options.
@@ -63,9 +57,7 @@ The Exec component supports 9 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[Exec-Messageheaders]]
-Message headers
-^^^^^^^^^^^^^^^
+### Message headers
The supported headers are defined in
`org.apache.camel.component.exec.ExecBinding`.
@@ -107,9 +99,7 @@ Camel Message Body with `stderr`. This behavior is disabled (`false`) by
default.
|=======================================================================
-[[Exec-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
If the `Exec` component receives an `in` message body that is
convertible to `java.io.InputStream`, it is used to feed input to the
@@ -141,13 +131,9 @@ this component will convert the stdout of the process to the target
type. For more details, please refer to the link:exec.html[usage
examples] below.
-[[Exec-Usageexamples]]
-Usage examples
-^^^^^^^^^^^^^^
+### Usage examples
-[[Exec-Executingwordcount]]
-Executing word count (Linux)
-++++++++++++++++++++++++++++
+#### Executing word count (Linux)
The example below executes `wc` (word count, Linux) to count the words
in file `/usr/share/dict/words`. The word count (output) is written to
@@ -169,9 +155,7 @@ from("direct:exec")
});
--------------------------------------------------------------------------------------
-[[Exec-Executingjava]]
-Executing `java`
-++++++++++++++++
+#### Executing `java`
The example below executes `java` with 2 arguments: `-server` and
`-version`, provided that `java` is in the system path.
@@ -191,9 +175,7 @@ from("direct:exec")
.to("exec:c:/program files/jdk/bin/java?args=-server -version -Duser.name=Camel&workingDir=c:/temp")
----------------------------------------------------------------------------------------------------
-[[Exec-ExecutingAntscripts]]
-Executing Ant scripts
-+++++++++++++++++++++
+#### Executing Ant scripts
The following example executes http://ant.apache.org/[Apache Ant]
(Windows only) with the build file `CamelExecBuildFile.xml`, provided
@@ -225,9 +207,7 @@ from("direct:exec")
});
-------------------------------------------------------------------------------------------------------
-[[Exec-Executingecho]]
-Executing `echo` (Windows)
-++++++++++++++++++++++++++
+#### Executing `echo` (Windows)
Commands such as `echo` and `dir` can be executed only with the command
interpreter of the operating system. This example shows how to execute
@@ -238,12 +218,9 @@ such a command - `echo` - in Windows.
from("direct:exec").to("exec:cmd?args=/C echo echoString")
----------------------------------------------------------
-[[Exec-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-facebook/src/main/docs/facebook-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-facebook/src/main/docs/facebook-component.adoc b/components/camel-facebook/src/main/docs/facebook-component.adoc
index b22f442..e082551 100644
--- a/components/camel-facebook/src/main/docs/facebook-component.adoc
+++ b/components/camel-facebook/src/main/docs/facebook-component.adoc
@@ -1,4 +1,4 @@
-# Facebook Component
+## Facebook Component
*Available as of Camel 2.12*
@@ -32,18 +32,14 @@ for this component:
</dependency>
-----------------------------------------------
-[[Facebook-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------
facebook://[endpoint]?[options]
---------------------------------
-[[Facebook-FacebookComponent.1]]
-FacebookComponent
-^^^^^^^^^^^^^^^^^
+### FacebookComponent
The facebook component can be configured with the Facebook account
settings below, which are mandatory. The values can be provided to the
@@ -188,9 +184,7 @@ The Facebook component supports 103 endpoint options which are listed below:
// endpoint options: END
-[[Facebook-ProducerEndpoints:]]
-Producer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Producer Endpoints:
Producer endpoints can use endpoint names and options from the table
below. Endpoints can also use the short name without the *get* or
@@ -224,9 +218,7 @@ return a boolean, return true for success and false otherwise. In case
of Facebook API errors the endpoint will throw a RuntimeCamelException
with a facebook4j.FacebookException cause.
-[[Facebook-ConsumerEndpoints:]]
-Consumer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints:
Any of the producer endpoints that take a
https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=CAMEL&title=reading&linkCreation=true&fromPageId=34020899[reading#reading]
@@ -241,9 +233,7 @@ camel-facebook creates one route exchange per returned object. As an
example, if *"facebook://home"* results in five posts, the route will be
executed five times (once for each Post).
-[[Facebook-ReadingOptions]]
-Reading Options
-^^^^^^^^^^^^^^^
+### Reading Options
The *reading* option of type *facebook4j.Reading* adds support for
reading parameters, which allow selecting specific fields, limits the
@@ -261,18 +251,14 @@ The reading option can be a reference or value of type
options in either the endpoint URI or exchange header with
*CamelFacebook.* prefix.
-[[Facebook-Messageheader]]
-Message header
-^^^^^^^^^^^^^^
+### Message header
Any of the
https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=CAMEL&title=URI+options&linkCreation=true&fromPageId=34020899[URI
options#urioptions] can be provided in a message header for producer
endpoints with *CamelFacebook.* prefix.
-[[Facebook-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
All result message bodies utilize objects provided by the Facebook4J
API. Producer endpoints can specify the option name for incoming message
@@ -282,9 +268,7 @@ For endpoints that return an array, or *facebook4j.ResponseList*, or
*java.util.List*, a consumer endpoint will map every elements in the
list to distinct messages.
-[[Facebook-Usecases]]
-Use cases
-^^^^^^^^^
+### Use cases
To create a post within your Facebook profile, send this producer a
facebook4j.PostUpdate body.
@@ -316,4 +300,4 @@ CamelFacebook.query header.
from("direct:foo")
.setHeader("CamelFacebook.query", header("bar"))
.to("facebook://posts");
---------------------------------------------------------
+--------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-flatpack/src/main/docs/flatpack-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-flatpack/src/main/docs/flatpack-component.adoc b/components/camel-flatpack/src/main/docs/flatpack-component.adoc
index ca73ca4..9d0e5d4 100644
--- a/components/camel-flatpack/src/main/docs/flatpack-component.adoc
+++ b/components/camel-flatpack/src/main/docs/flatpack-component.adoc
@@ -1,4 +1,4 @@
-# Flatpack Component
+## Flatpack Component
The Flatpack component supports fixed width and delimited file parsing
via the http://flatpack.sourceforge.net[FlatPack library]. +
@@ -19,9 +19,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Flatpack-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------------------------
@@ -38,9 +36,7 @@ flatpack:someName[?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Flatpack-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
The Flatpack component has no options.
@@ -84,9 +80,7 @@ The Flatpack component supports 27 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[Flatpack-Examples]]
-Examples
-^^^^^^^^
+### Examples
* `flatpack:fixed:foo.pzmap.xml` creates a fixed-width endpoint using
the `foo.pzmap.xml` file configuration.
@@ -95,9 +89,7 @@ the `foo.pzmap.xml` file configuration.
* `flatpack:foo` creates a delimited endpoint called `foo` with no file
configuration.
-[[Flatpack-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Camel will store the following headers on the IN message:
@@ -109,9 +101,7 @@ Camel will store the following headers on the IN message:
number of rows.
|=======================================================================
-[[Flatpack-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
The component delivers the data in the IN message as a
`org.apache.camel.component.flatpack.DataSetList` object that has
@@ -140,9 +130,7 @@ However, you can also always get it as a `List` (even for
String firstName = row.get("FIRSTNAME");
---------------------------------------------------
-[[Flatpack-HeaderandTrailerrecords]]
-Header and Trailer records
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Header and Trailer records
The header and trailer notions in Flatpack are supported. However, you
*must* use fixed record IDs:
@@ -173,9 +161,7 @@ trailer. You can omit one or both of them if not needed.
</RECORD>
---------------------------------------------------------------------------
-[[Flatpack-Usingtheendpoint]]
-Using the endpoint
-^^^^^^^^^^^^^^^^^^
+### Using the endpoint
A common use case is sending a file to this endpoint for further
processing in a separate route. For example:
@@ -198,9 +184,7 @@ processing in a separate route. For example:
You can also convert the payload of each message created to a `Map` for
easy link:bean-integration.html[Bean Integration]
-[[Flatpack-FlatpackDataFormat]]
-Flatpack DataFormat
-~~~~~~~~~~~~~~~~~~~
+### Flatpack DataFormat
The link:flatpack.html[Flatpack] component ships with the Flatpack data
format that can be used to format between fixed width or delimited text
@@ -218,9 +202,7 @@ link:splitter.html[Splitter].
*Notice:* The Flatpack library does currently not support header and
trailers for the marshal operation.
-[[Flatpack-Options]]
-Options
-^^^^^^^
+### Options
The data format has the following options:
@@ -249,9 +231,7 @@ expected and ignores the extra characters.
expected and ignores the extra characters.
|=======================================================================
-[[Flatpack-Usage]]
-Usage
-^^^^^
+### Usage
To use the data format, simply instantiate an instance and invoke the
marshal or unmarshal operation in the route builder:
@@ -286,9 +266,7 @@ in Java code from e.g. a processor. We marshal the data according to the
Flatpack format and convert the result as a `String` object and store it
on a JMS queue.
-[[Flatpack-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Flatpack in your camel routes you need to add the a dependency on
*camel-flatpack* which implements this data format.
@@ -306,12 +284,9 @@ link:download.html[the download page for the latest versions]).
</dependency>
-----------------------------------------
-[[Flatpack-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-flatpack/src/main/docs/flatpack-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-flatpack/src/main/docs/flatpack-dataformat.adoc b/components/camel-flatpack/src/main/docs/flatpack-dataformat.adoc
index 57c7909..e9fcb6c 100644
--- a/components/camel-flatpack/src/main/docs/flatpack-dataformat.adoc
+++ b/components/camel-flatpack/src/main/docs/flatpack-dataformat.adoc
@@ -1,4 +1,4 @@
-# Flatpack DataFormat
+## Flatpack DataFormat
The link:flatpack.html[Flatpack] component ships with the Flatpack data
format that can be used to format between fixed width or delimited text
@@ -16,9 +16,7 @@ link:splitter.html[Splitter].
*Notice:* The Flatpack library does currently not support header and
trailers for the marshal operation.
-[[FlatpackDataFormat-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The Flatpack dataformat supports 9 options which are listed below.
@@ -42,9 +40,7 @@ The Flatpack dataformat supports 9 options which are listed below.
{% endraw %}
// dataformat options: END
-[[FlatpackDataFormat-Usage]]
-Usage
-^^^^^
+### Usage
To use the data format, simply instantiate an instance and invoke the
marshal or unmarshal operation in the route builder:
@@ -79,9 +75,7 @@ in Java code from e.g. a processor. We marshal the data according to the
Flatpack format and convert the result as a `String` object and store it
on a JMS queue.
-[[FlatpackDataFormat-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Flatpack in your camel routes you need to add the a dependency on
*camel-flatpack* which implements this data format.
@@ -97,4 +91,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-flatpack</artifactId>
<version>x.x.x</version>
</dependency>
------------------------------------------
+-----------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-flink/src/main/docs/flink-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-flink/src/main/docs/flink-component.adoc b/components/camel-flink/src/main/docs/flink-component.adoc
index 03d0404..61b0218 100644
--- a/components/camel-flink/src/main/docs/flink-component.adoc
+++ b/components/camel-flink/src/main/docs/flink-component.adoc
@@ -1,4 +1,4 @@
-# Apache Flink Component
+## Apache Flink Component
*Available as of Camel 2.18*
@@ -23,9 +23,7 @@ their�`pom.xml`�for this component:
</dependency>
------------------------------------------------------------
-[[camel-flink-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
Currently, the Flink Component supports only Producers. One can create DataSet, DataStream jobs.
@@ -60,9 +58,7 @@ The Apache Flink component supports 7 endpoint options which are listed below:
-[[Flink-FlinkComponentOptions]]
-FlinkComponent Options
-^^^^^^^^^^^^^^^^^^^^
+### FlinkComponent Options
@@ -88,8 +84,7 @@ The Apache Flink component supports 4 options which are listed below.
-Flink DataSet Callback
-^^^^^^^^^^^^^^^^^^^^^^
+### Flink DataSet Callback
[source,java]
-----------------------------------
@@ -108,8 +103,7 @@ public DataSetCallback<Long> dataSetCallback() {
}
-----------------------------------
-Flink DataStream Callback
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Flink DataStream Callback
[source,java]
---------------------------
@@ -126,8 +120,7 @@ public VoidDataStreamCallback dataStreamCallback() {
}
---------------------------
-Camel-Flink Producer call
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Camel-Flink Producer call
[source,java]
-----------------------------------
@@ -144,11 +137,9 @@ try {
}
-----------------------------------
-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-fop/src/main/docs/fop-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-fop/src/main/docs/fop-component.adoc b/components/camel-fop/src/main/docs/fop-component.adoc
index c005633..74cc968 100644
--- a/components/camel-fop/src/main/docs/fop-component.adoc
+++ b/components/camel-fop/src/main/docs/fop-component.adoc
@@ -1,4 +1,4 @@
-# FOP Component
+## FOP Component
*Available as of Camel 2.10*
@@ -18,18 +18,14 @@ for this component:
</dependency>
------------------------------------------------------------
-[[FOP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------
fop://outputFormat?[options]
----------------------------
-[[FOP-OutputFormats]]
-Output Formats
-^^^^^^^^^^^^^^
+### Output Formats
The primary output format is PDF but other output
http://xmlgraphics.apache.org/fop/0.95/output.html[formats] are also
@@ -63,9 +59,7 @@ supported:
The complete list of valid output formats can be found
http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/src/java/org/apache/xmlgraphics/util/MimeConstants.java[here]
-[[FOP-EndpointOptions]]
-Endpoint Options
-^^^^^^^^^^^^^^^^
+### Endpoint Options
// component options: START
The FOP component has no options.
@@ -103,9 +97,7 @@ fopFactory
Allows to use a custom configured or implementation of
`org.apache.fop.apps.FopFactory`.
-[[FOP-MessageOperations]]
-Message Operations
-^^^^^^^^^^^^^^^^^^
+### Message Operations
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -140,9 +132,7 @@ Message Operations
|CamelFop.Render.keywords | | Set of keywords applicable to this document
|=======================================================================
-[[FOP-Example]]
-Example
-^^^^^^^
+### Example
Below is an example route that renders PDFs from xml data and xslt
template and saves the PDF files in target folder:
@@ -157,12 +147,9 @@ from("file:source/data/xml")
For more information, see these resources...
-[[FOP-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-freemarker/src/main/docs/freemarker-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-freemarker/src/main/docs/freemarker-component.adoc b/components/camel-freemarker/src/main/docs/freemarker-component.adoc
index 931104c..2f2d55e 100644
--- a/components/camel-freemarker/src/main/docs/freemarker-component.adoc
+++ b/components/camel-freemarker/src/main/docs/freemarker-component.adoc
@@ -1,4 +1,4 @@
-# Freemarker Component
+## Freemarker Component
The *freemarker:* component allows for processing a message using a
http://freemarker.org/[FreeMarker] template. This can be ideal when
@@ -17,9 +17,7 @@ for this component:
</dependency>
-------------------------------------------------------------------------------------
-[[FreeMarker-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------
@@ -33,9 +31,7 @@ file://folder/myfile.ftl[file://folder/myfile.ftl]).
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[FreeMarker-Options]]
-Options
-^^^^^^^
+### Options
@@ -77,9 +73,7 @@ The Freemarker component supports 6 endpoint options which are listed below:
-[[FreeMarker-Headers]]
-Headers
-^^^^^^^
+### Headers
Headers set during the FreeMarker evaluation are returned to the message
and added as headers. This provides a mechanism for the FreeMarker
@@ -94,9 +88,7 @@ ${request.setHeader('fruit', 'Apple')}
The header, `fruit`, is now accessible from the `message.out.headers`.
-[[FreeMarker-FreeMarkerContext]]
-FreeMarker Context
-^^^^^^^^^^^^^^^^^^
+### FreeMarker Context
Camel will provide exchange information in the FreeMarker context (just
a `Map`). The `Exchange` is transferred as:
@@ -132,18 +124,14 @@ variableMap.put("exchange", exchange);
exchange.getIn().setHeader("CamelFreemarkerDataModel", variableMap);
--------------------------------------------------------------------
-[[FreeMarker-Hotreloading]]
-Hot reloading
-^^^^^^^^^^^^^
+### Hot reloading
The FreeMarker template resource is by default *not* hot reloadable for
both file and classpath resources (expanded jar). If you set
`contentCache=false`, then Camel will not cache the resource and hot
reloading is thus enabled. This scenario can be used in development.
-[[FreeMarker-Dynamictemplates]]
-Dynamic templates
-^^^^^^^^^^^^^^^^^
+### Dynamic templates
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these
@@ -162,9 +150,7 @@ configured. | >= 2.1
|FreemarkerConstants.FREEMARKER_TEMPLATE |String |The template to use instead of the endpoint configured. | >= 2.1
|=======================================================================
-[[FreeMarker-Samples]]
-Samples
-^^^^^^^
+### Samples
For example you could use something like:
@@ -216,9 +202,7 @@ from("direct:in").
to("freemarker:dummy");
---------------------------------------------------------------------------------------------
-[[FreeMarker-TheEmailSample]]
-The Email Sample
-^^^^^^^^^^^^^^^^
+### The Email Sample
In this sample we want to use FreeMarker templating for an order
confirmation email. The email template is laid out in FreeMarker as:
@@ -235,12 +219,9 @@ ${body}
And the java code:
-[[FreeMarker-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-ftp/src/main/docs/ftp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ftp/src/main/docs/ftp-component.adoc b/components/camel-ftp/src/main/docs/ftp-component.adoc
index 2d70f23..502eb94 100644
--- a/components/camel-ftp/src/main/docs/ftp-component.adoc
+++ b/components/camel-ftp/src/main/docs/ftp-component.adoc
@@ -1,4 +1,4 @@
-# FTP Component
+## FTP Component
This component provides access to remote file systems over the FTP and
SFTP protocols.
@@ -46,9 +46,7 @@ further below for details related to consuming files.
====
-[[FTP2-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------------------------
@@ -89,9 +87,7 @@ The FTPS component is only available in Camel 2.2 or newer. +
support for the Transport Layer Security (TLS) and the Secure Sockets
Layer (SSL) cryptographic protocols.
-[[FTP2-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
The options below are exclusive for the FTP component.
@@ -304,9 +300,7 @@ url.
from("ftp://foo@myserver?password=secret&ftpClientConfig=#myConfig").to("bean:foo");
------------------------------------------------------------------------------------
-[[FTP2-MoreURIoptions]]
-More URI options
-^^^^^^^^^^^^^^^^
+### More URI options
[Info]
====
@@ -317,9 +311,7 @@ this component.
====
-[[FTP2-Examples]]
-Examples
-^^^^^^^^
+### Examples
`ftp://someone@someftpserver.com/public/upload/images/holiday2008?password=secret&binary=true` +
@@ -349,9 +341,7 @@ component page.
====
-[[FTP2-Defaultwhenconsumingfiles]]
-Default when consuming files
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Default when consuming files
The link:ftp2.html[FTP] consumer will by default leave the consumed
files untouched on the remote FTP server. You have to configure it
@@ -364,9 +354,7 @@ default move files to a `.camel` sub directory. The reason Camel does
*not* do this by default for the FTP consumer is that it may lack
permissions by default to be able to move or delete files.
-[[FTP2-limitations]]
-limitations
-+++++++++++
+#### limitations
The option *readLock* can be used to force Camel *not* to consume files
that is currently in the progress of being written. However, this option
@@ -382,9 +370,7 @@ restricted to the FTP_ROOT folder. That prevents you from moving files
outside the FTP area. If you want to move files to another area you can
use soft links and move files into a soft linked folder.
-[[FTP2-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
The following message headers can be used to affect the behavior of the
component
@@ -423,9 +409,7 @@ In addition the FTP/FTPS consumer and producer will enrich the Camel
|`CamelFtpReplyString` | *Camel 2.11.1:* The FTP client reply string
|=======================================================================
-[[FTP2-Abouttimeouts]]
-About timeouts
-^^^^^^^^^^^^^^
+### About timeouts
The two set of libraries (see top) has different API for setting
timeout. You can use the `connectTimeout` option for both of them to set
@@ -436,9 +420,7 @@ a timeout in millis to establish a network connection. An individual
for FTP/FTSP as the data timeout, which corresponds to the
`ftpClient.dataTimeout` value. All timeout values are in millis.
-[[FTP2-UsingLocalWorkDirectory]]
-Using Local Work Directory
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using Local Work Directory
Camel supports consuming from remote FTP servers and downloading the
files directly into a local work directory. This avoids reading the
@@ -474,9 +456,7 @@ copy, as the work file is meant to be deleted anyway.
====
-[[FTP2-Stepwisechangingdirectories]]
-Stepwise changing directories
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Stepwise changing directories
Camel link:ftp2.html[FTP] can operate in two modes in terms of
traversing directories when consuming files (eg downloading) or
@@ -518,9 +498,7 @@ FTP server we need to traverse and download files:
And that we have a file in each of sub-a (a.txt) and sub-b (b.txt)
folder.
-[[FTP2-Usingstepwise]]
-Using stepwise=true (default mode)
-++++++++++++++++++++++++++++++++++
+#### Using stepwise=true (default mode)
[source,java]
----------------------------------------------------------
@@ -610,9 +588,7 @@ disconnected.
As you can see when stepwise is enabled, it will traverse the directory
structure using CD xxx.
-[[FTP2-Notusingstepwise]]
-Using stepwise=false
-++++++++++++++++++++
+#### Using stepwise=false
[source,java]
-------------------------------------------
@@ -659,9 +635,7 @@ disconnected.
As you can see when not using stepwise, there are no CD operation
invoked at all.
-[[FTP2-Samples]]
-Samples
-^^^^^^^
+### Samples
In the sample below we set up Camel to download all the reports from the
FTP server once every hour (60 min) as BINARY content and store it as
@@ -677,9 +651,7 @@ And the route using Spring DSL:
</route>
------------------------------------------------------------------------------------------------------
-[[FTP2-ConsumingaremoteFTPSserverimplicitSSLandclientauthentication]]
-Consuming a remote FTPS server (implicit SSL) and client authentication
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Consuming a remote FTPS server (implicit SSL) and client authentication
[source,java]
--------------------------------------------------------------------------------------------------
@@ -689,9 +661,7 @@ from("ftps://admin@localhost:2222/public/camel?password=admin&securityProtocol=S
.to("bean:foo");
--------------------------------------------------------------------------------------------------
-[[FTP2-ConsumingaremoteFTPSserverexplicitTLSandacustomtruststoreconfiguration]]
-Consuming a remote FTPS server (explicit TLS) and a custom trust store configuration
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Consuming a remote FTPS server (explicit TLS) and a custom trust store configuration
[source,java]
----------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -699,9 +669,7 @@ from("ftps://admin@localhost:2222/public/camel?password=admin&ftpClient.trustSto
.to("bean:foo");
----------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[FTP2-Filterusingorg.apache.camel.component.file.GenericFileFilter]]
-Filter using `org.apache.camel.component.file.GenericFileFilter`
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Filter using `org.apache.camel.component.file.GenericFileFilter`
Camel supports pluggable filtering strategies. This strategy it to use
the build in `org.apache.camel.component.file.GenericFileFilter` in
@@ -726,9 +694,7 @@ spring XML file:
</route>
---------------------------------------------------------------------------------------
-[[FTP2-FilteringusingANTpathmatcher]]
-Filtering using ANT path matcher
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Filtering using ANT path matcher
The ANT path matcher is a filter that is shipped out-of-the-box in the
*camel-spring* jar. So you need to depend on *camel-spring* if you are
@@ -745,9 +711,7 @@ The file paths are matched with the following rules:
The sample below demonstrates how to use it:
-[[FTP2-UsingaproxywithSFTP]]
-Using a proxy with SFTP
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using a proxy with SFTP
To use an HTTP proxy to connect to your remote host, you can configure
your route in the following way:
@@ -770,9 +734,7 @@ You can also assign a user name and password to the proxy, if necessary.
Please consult the documentation for `com.jcraft.jsch.Proxy` to discover
all options.
-[[FTP2-SettingpreferredSFTPauthenticationmethod]]
-Setting preferred SFTP authentication method
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting preferred SFTP authentication method
If you want to explicitly specify the list of authentication methods
that should be used by `sftp` component, use `preferredAuthentications`
@@ -787,9 +749,7 @@ from("sftp://localhost:9999/root?username=admin&password=admin&preferredAuthenti
to("bean:processFile");
-------------------------------------------------------------------------------------------------------------
-[[FTP2-Consumingasinglefileusingafixedname]]
-Consuming a single file using a fixed name
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Consuming a single file using a fixed name
When you want to download a single file and knows the file name, you can
use `fileName=myFileName.txt` to tell Camel the name of the file to
@@ -824,21 +784,16 @@ single file (if it exists) and grab the file content as a String type:
String data = template.retrieveBodyNoWait("ftp://admin@localhost:21/nolist/?password=admin&stepwise=false&useList=false&ignoreFileNotFoundOrPermissionError=true&fileName=report.txt&delete=true", String.class);
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[FTP2-Debuglogging]]
-Debug logging
-^^^^^^^^^^^^^
+### Debug logging
This component has log level *TRACE* that can be helpful if you have
problems.
-[[FTP2-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:file2.html[File2]
-
+* link:file2.html[File2]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ftp/src/main/docs/ftps-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ftp/src/main/docs/ftps-component.adoc b/components/camel-ftp/src/main/docs/ftps-component.adoc
index e8b325b..946f961 100644
--- a/components/camel-ftp/src/main/docs/ftps-component.adoc
+++ b/components/camel-ftp/src/main/docs/ftps-component.adoc
@@ -1,4 +1,4 @@
-# FTPS Component
+## FTPS Component
This component provides access to remote file systems over the FTP and
SFTP protocols.
@@ -18,9 +18,7 @@ for this component:
For more information you can look at link:ftp.html[FTP component]
-[[FTPS-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
The options below are exclusive for the FTPS component.
@@ -151,5 +149,4 @@ The FTPS component supports 113 endpoint options which are listed below:
| username | security | | String | Username to use for login
|=======================================================================
{% endraw %}
-// endpoint options: END
-
+// endpoint options: END
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ftp/src/main/docs/sftp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ftp/src/main/docs/sftp-component.adoc b/components/camel-ftp/src/main/docs/sftp-component.adoc
index 3147a51..6d052c7 100644
--- a/components/camel-ftp/src/main/docs/sftp-component.adoc
+++ b/components/camel-ftp/src/main/docs/sftp-component.adoc
@@ -1,4 +1,4 @@
-# SFTP Component
+## SFTP Component
This component provides access to remote file systems over the FTP and
SFTP protocols.
@@ -18,9 +18,7 @@ for this component:
For more information you can look at link:ftp.html[FTP component]
-[[SFTP-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
The options below are exclusive for the FTPS component.
@@ -150,4 +148,4 @@ The SFTP component supports 112 endpoint options which are listed below:
| useUserKnownHostsFile | security | true | boolean | If knownHostFile has not been explicit configured then use the host file from System.getProperty(user.home)/.ssh/known_hosts
|=======================================================================
{% endraw %}
-// endpoint options: END
+// endpoint options: END
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ganglia/src/main/docs/ganglia-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ganglia/src/main/docs/ganglia-component.adoc b/components/camel-ganglia/src/main/docs/ganglia-component.adoc
index 2ee0a56..33e4d54 100644
--- a/components/camel-ganglia/src/main/docs/ganglia-component.adoc
+++ b/components/camel-ganglia/src/main/docs/ganglia-component.adoc
@@ -1,8 +1,6 @@
-# Ganglia Component
+## Ganglia Component
-[[Ganglia-AvailableasofCamel2.15.0]]
-Available as of Camel 2.15.0
-++++++++++++++++++++++++++++
+#### Available as of Camel 2.15.0
Provides a mechanism to send a value (the message body) as a metric to
the http://ganglia.info[Ganglia] monitoring system.� Uses the gmetric4j
@@ -35,9 +33,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Ganglia-URIformat]]
-URI format
-~~~~~~~~~~
+### URI format
[source,java]
------------------------------
@@ -47,9 +43,7 @@ ganglia:address:port[?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Ganglia-GangliacomponentandendpointURIoptions]]
-Ganglia component and endpoint URI options
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Ganglia component and endpoint URI options
@@ -102,27 +96,19 @@ The Ganglia component supports 15 endpoint options which are listed below:
-[[Ganglia-Messagebody]]
-Message body
-~~~~~~~~~~~~
+### Message body
Any value (such as a string or numeric type) in the body is sent to the
Ganglia system.
-[[Ganglia-ReturnvalueAndResponse]]
-Return value / response
-~~~~~~~~~~~~~~~~~~~~~~~
+### Return value / response
Ganglia sends metrics using unidirectional UDP or multicast.� There is
no response or change to the message body.
-[[Ganglia-Examples]]
-Examples
-~~~~~~~~
+### Examples
-[[Ganglia-SendingaStringmetric]]
-Sending a String metric
-^^^^^^^^^^^^^^^^^^^^^^^
+### Sending a String metric
The message body will be converted to a String and sent as a metric
value.� Unlike numeric metrics, String values can't be charted but
@@ -140,9 +126,7 @@ from("direct:ganglia.tx")
.to("ganglia:239.2.11.71:8649?mode=MULTICAST&prefix=test");
------------------------------------------------------------------------
-[[Ganglia-Sendinganumericmetric]]
-Sending a numeric metric
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending a numeric metric
[source,java]
------------------------------------------------------------------------
@@ -154,4 +138,4 @@ from("direct:value.for.ganglia")
from("direct:ganglia.tx")
.to("ganglia:239.2.11.71:8649?mode=MULTICAST&prefix=test");
-------------------------------------------------------------------------
+------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-geocoder/src/main/docs/geocoder-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-geocoder/src/main/docs/geocoder-component.adoc b/components/camel-geocoder/src/main/docs/geocoder-component.adoc
index a4c78d9..9459e53 100644
--- a/components/camel-geocoder/src/main/docs/geocoder-component.adoc
+++ b/components/camel-geocoder/src/main/docs/geocoder-component.adoc
@@ -1,4 +1,4 @@
-# Geocoder Component
+## Geocoder Component
*Available as of Camel 2.12*
@@ -20,9 +20,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Geocoder-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------------------------
@@ -30,9 +28,7 @@ geocoder:address:name[?options]
geocoder:latlng:latitude,longitude[?options]
--------------------------------------------
-[[Geocoder-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -71,9 +67,7 @@ The Geocoder component supports 16 endpoint options which are listed below:
-[[Geocoder-Exchangedataformat]]
-Exchange data format
-^^^^^^^^^^^^^^^^^^^^
+### Exchange data format
Camel will deliver the body as a
`com.google.code.geocoder.model.GeocodeResponse` type. +
@@ -84,9 +78,7 @@ If the option `headersOnly` is set to `true` then the message body is
left as-is, and only headers will be added to the
link:exchange.html[Exchange].
-[[Geocoder-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="50%,50%",options="header",]
|=======================================================================
@@ -117,9 +109,7 @@ Message Headers
Notice not all headers may be provided depending on available data and
mode in use (address vs latlng).
-[[Geocoder-Samples]]
-Samples
-^^^^^^^
+### Samples
In the example below we get the latitude and longitude for Paris, France
@@ -161,4 +151,4 @@ shown:
-----------------------------------
from("direct:start")
.to("geocoder:address:current")
------------------------------------
+-----------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-git/src/main/docs/git-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-git/src/main/docs/git-component.adoc b/components/camel-git/src/main/docs/git-component.adoc
index a67a841..6f3cc8d 100644
--- a/components/camel-git/src/main/docs/git-component.adoc
+++ b/components/camel-git/src/main/docs/git-component.adoc
@@ -1,4 +1,4 @@
-# Git Component
+## Git Component
*Available as of Camel 2.16*
@@ -21,9 +21,7 @@ The�*git:*�component allows you to work with a generic Git repository.�
git://localRepositoryPath[?options]
-----------------------------------
-[[Git-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
The producer allows to do operations on a specific repository. +
The consumer allows consuming commits, tags and branches on a specific
@@ -65,9 +63,7 @@ The Git component supports 14 endpoint options which are listed below:
-[[Git-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="10%,10%,10%,20%,50%",options="header",]
|=======================================================================
@@ -89,9 +85,7 @@ Message Headers
|=======================================================================
-[[Git-ProducerExample]]
-Producer Example
-^^^^^^^^^^^^^^^^
+### Producer Example
Below is an example route of a producer that add a file test.java to a
local repository, commit it with a specific message on master branch and
@@ -107,9 +101,7 @@ from("direct:start")
.to("git:///tmp/testRepo?operation=push&remotePath=https://foo.com/test/test.git&username=xxx&password=xxx")
--------------------------------------------------------------------------------------------------------------------
-[[Git-ConsumerExample]]
-Consumer Example
-^^^^^^^^^^^^^^^^
+### Consumer Example
Below is an example route of a consumer that consumes commit:
@@ -117,4 +109,4 @@ Below is an example route of a consumer that consumes commit:
---------------------------------------
from("git:///tmp/testRepo?type=commit")
.to(....)
----------------------------------------
+---------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-github/src/main/docs/github-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-github/src/main/docs/github-component.adoc b/components/camel-github/src/main/docs/github-component.adoc
index 362f28f..1ed6623 100644
--- a/components/camel-github/src/main/docs/github-component.adoc
+++ b/components/camel-github/src/main/docs/github-component.adoc
@@ -1,4 +1,4 @@
-# GitHub Component
+## GitHub Component
*Available as of Camel 2.15*
@@ -32,18 +32,14 @@ for this component:
</dependency>
-----------------------------------------
-[[GitHub-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,text]
---------------------------
github://endpoint[?options]
---------------------------
-[[GitHub-MandatoryOptions:]]
-Mandatory Options:
-^^^^^^^^^^^^^^^^^^
+### Mandatory Options:
Note that these can be configured directly through the endpoint.
@@ -81,9 +77,7 @@ The GitHub component supports 14 endpoint options which are listed below:
-[[GitHub-ConsumerEndpoints:]]
-Consumer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints:
[width="100%",cols="20%,20%,60%",options="header",]
|=======================================================================
@@ -100,9 +94,7 @@ request discussion) or org.eclipse.egit.github.core.CommitComment
|commit |polling |org.eclipse.egit.github.core.RepositoryCommit
|=======================================================================
-[[GitHub-ProducerEndpoints:]]
-Producer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Producer Endpoints:
[width="100%",cols="20%,20%,60%",options="header",]
|=======================================================================
@@ -117,4 +109,4 @@ pull request discussion is assumed.
|closePullRequest |none | - GitHubPullRequest (integer) (REQUIRED): Pull request number.
|createIssue (From Camel 2.18) |String (issue body text) | - GitHubIssueTitle (String) (REQUIRED): Issue Title.
-|=======================================================================
+|=======================================================================
\ No newline at end of file
[02/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
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
[11/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-box/src/main/docs/box-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-box/src/main/docs/box-component.adoc b/components/camel-box/src/main/docs/box-component.adoc
index aaa4c04..ce82195 100644
--- a/components/camel-box/src/main/docs/box-component.adoc
+++ b/components/camel-box/src/main/docs/box-component.adoc
@@ -1,4 +1,4 @@
-# Box Component
+## Box Component
*Available as of Camel 2.14*
@@ -31,9 +31,7 @@ for this component:
</dependency>
-------------------------------------------
-[[Box-Options]]
-Box Options
-^^^^^^^^^^^
+### Box Options
@@ -93,9 +91,7 @@ The Box component supports 21 endpoint options which are listed below:
-[[Box-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------------------------
@@ -118,9 +114,7 @@ Endpoint prefix can be one of:
* shared-items
* users
-[[Box-BoxComponent.1]]
-BoxComponent
-^^^^^^^^^^^^
+### BoxComponent
The Box Component can be configured with the options below. These
options can be provided using the component's bean
@@ -172,9 +166,7 @@ sharedLink
returns null on first call
|=======================================================================
-[[Box-ProducerEndpoints:]]
-Producer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Producer Endpoints:
Producer endpoints can use endpoint prefixes followed by endpoint names
and associated options described next. A shorthand alias can be used for
@@ -202,9 +194,7 @@ RuntimeCamelException with a
*com.box.restclientv2.exceptions.BoxSDKException*�derived exception
cause.
-[[Box-EndpointPrefixcollaborations]]
-Endpoint Prefix�_collaborations_
-++++++++++++++++++++++++++++++++
+#### Endpoint Prefix�_collaborations_
For more information on Box collaborations see
https://developers.box.com/docs/#collaborations[https://developers.box.com/docs/#collaborations].�The
@@ -250,9 +240,7 @@ URI Options for�_collaborations_
|getAllCollabsRequest |com.box.boxjavalibv2.requests.requestobjects.BoxGetAllCollabsRequestObject
|=======================================================================
-[[Box-EndpointPrefixevents]]
-Endpoint Prefix�_events_
-++++++++++++++++++++++++
+#### Endpoint Prefix�_events_
For more information on Box events see
https://developers.box.com/docs/#events[https://developers.box.com/docs/#events].
@@ -287,9 +275,7 @@ URI Options for�_events_
|eventRequest |com.box.boxjavalibv2.requests.requestobjects.BoxEventRequestObject
|=======================================================================
-[[Box-EndpointPrefixgroups]]
-Endpoint Prefix�_groups_
-++++++++++++++++++++++++
+#### Endpoint Prefix�_groups_
For more information on Box groups see
https://developers.box.com/docs/#groups[https://developers.box.com/docs/#groups].
@@ -351,9 +337,7 @@ URI Options for�_groups_
|=======================================================================
-[[Box-EndpointPrefixsearch]]
-Endpoint Prefix�_search_
-++++++++++++++++++++++++
+#### Endpoint Prefix�_search_
For more information on Box search API see
https://developers.box.com/docs/#search[https://developers.box.com/docs/#search].�The
@@ -384,9 +368,7 @@ URI Options for�_search_
|searchQuery |String
|=======================================================================
-[[Box-EndpointPrefixcommentsandshared-comments]]
-Endpoint Prefix _comments_ and�_shared-comments_
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Endpoint Prefix _comments_ and�_shared-comments_
For more information on Box comments see
https://developers.box.com/docs/#comments[https://developers.box.com/docs/#comments].
@@ -433,9 +415,7 @@ URI Options for _comments_ and�_shared-comments_
|message |String
|=======================================================================
-[[Box-EndpointPrefixfilesandshared-files]]
-Endpoint Prefix�_files_ and�_shared-files_
-++++++++++++++++++++++++++++++++++++++++++
+#### Endpoint Prefix�_files_ and�_shared-files_
For more information on Box files see
https://developers.box.com/docs/#files[https://developers.box.com/docs/#files].
@@ -512,9 +492,7 @@ URI Options for _files_ and�_shared-files_
|sharedLinkRequest |com.box.boxjavalibv2.requests.requestobjects.BoxSharedLinkRequestObject
|=======================================================================
-[[Box-EndpointPrefixfoldersandshared-folders]]
-Endpoint Prefix _folders_ and�_shared-folders_
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Endpoint Prefix _folders_ and�_shared-folders_
For more information on Box folders see
https://developers.box.com/docs/#folders[https://developers.box.com/docs/#folders].
@@ -571,9 +549,7 @@ URI Options for _folders_ or�_shared-folders_
|sharedLinkRequest |com.box.boxjavalibv2.requests.requestobjects.BoxSharedLinkRequestObject
|=======================================================================
-[[Box-EndpointPrefixshared-items]]
-Endpoint Prefix�_shared-items_
-++++++++++++++++++++++++++++++
+#### Endpoint Prefix�_shared-items_
For more information on Box shared items see
https://developers.box.com/docs/#shared-items[https://developers.box.com/docs/#shared-items].
@@ -602,9 +578,7 @@ URI Options for�_shared-items_
|defaultRequest |com.box.restclientv2.requestsbase.BoxDefaultRequestObject
|=======================================================================
-[[Box-EndpointPrefixusers]]
-Endpoint Prefix�_users_
-+++++++++++++++++++++++
+#### Endpoint Prefix�_users_
For information on Box users see
https://developers.box.com/docs/#users[https://developers.box.com/docs/#users].
@@ -669,9 +643,7 @@ URI Options for�_users_
|userUpdateLoginRequest |com.box.boxjavalibv2.requests.requestobjects.BoxUserUpdateLoginRequestObject
|=======================================================================
-[[Box-ConsumerEndpoints:]]
-Consumer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints:
For more information on Box events see
https://developers.box.com/docs/#events[https://developers.box.com/docs/#events]�and
@@ -714,24 +686,18 @@ URI Options for�_poll-events_
|splitResult |boolean
|=======================================================================
-[[Box-Messageheader]]
-Message header
-^^^^^^^^^^^^^^
+### Message header
Any of the options�can be provided in a message header for producer
endpoints with *CamelBox.* prefix.
-[[Box-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
All result message bodies utilize objects provided by the Box Java SDK.
Producer endpoints can specify the option name for incoming message body
in the *inBody* endpoint parameter.
-[[Box-TypeConverter]]
-Type Converter
-^^^^^^^^^^^^^^
+### Type Converter
The Box component also provides a Camel type converter to convert
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/file/GenericFile.html[GenericFile]
@@ -742,9 +708,7 @@ specified in the exchange property�*CamelBox.folderId*. If the exchange
property is not specified the value defaults to *"**0"* for the root
folder ID.�
-[[Box-Usecases]]
-Use cases
-^^^^^^^^^
+### Use cases
The following route uploads new files to the user's root folder:
@@ -772,4 +736,4 @@ The following route uses a producer with dynamic header options.�The
.setHeader("CamelBox.fileId", header("fileId"))
.to("box://files/download")
.to("file://...");
--------------------------------------------------------
+-------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-braintree/src/main/docs/braintree-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-braintree/src/main/docs/braintree-component.adoc b/components/camel-braintree/src/main/docs/braintree-component.adoc
index 0abfc9a..3e5b994 100644
--- a/components/camel-braintree/src/main/docs/braintree-component.adoc
+++ b/components/camel-braintree/src/main/docs/braintree-component.adoc
@@ -1,4 +1,4 @@
-# Braintree Component
+## Braintree Component
*Available as of Camel 2.17*
@@ -29,9 +29,7 @@ for this component:
�
-[[Braintree-Options]]
-Braintree Options
-^^^^^^^^^^^^^^^^^
+### Braintree Options
@@ -81,9 +79,7 @@ The Braintree component supports 15 endpoint options which are listed below:
// endpoint options: END
-[[Braintree-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
�
@@ -113,9 +109,7 @@ Endpoint prefix can be one of:
�
-[[Braintree-BraintreeComponent.1]]
-BraintreeComponent
-^^^^^^^^^^^^^^^^^^
+### BraintreeComponent
The Braintree Component can be configured with the options below. These
options can be provided using the component's bean
@@ -139,9 +133,7 @@ shared \u2013 even with us!
All the options above are provided by Braintree Payments
-[[Braintree-ProducerEndpoints:]]
-Producer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Producer Endpoints:
Producer endpoints can use endpoint prefixes followed by endpoint names
and associated options described next. A shorthand alias can be used for
@@ -165,9 +157,7 @@ at�https://developers.braintreepayments.com/reference/overview[https://develope
�
-[[Braintree-EndpointprefixaddOn]]
-Endpoint prefix�_addOn_
-+++++++++++++++++++++++
+#### Endpoint prefix�_addOn_
The following endpoints can be invoked with the prefix�*addOn*�as
follows:
@@ -185,9 +175,7 @@ braintree://addOn/endpoint
|all |� |� |List<com.braintreegateway.Addon>
|====================================================
-[[Braintree-Endpointprefixaddress]]
-Endpoint prefix�_address_
-+++++++++++++++++++++++++
+#### Endpoint prefix�_address_
The following endpoints can be invoked with the prefix�*address*�as
follows:
@@ -225,9 +213,7 @@ URI Options for�_address_
|id |String
|============================================
-[[Braintree-EndpointprefixclientToken]]
-Endpoint prefix�_clientToken_
-+++++++++++++++++++++++++++++
+#### Endpoint prefix�_clientToken_
The following endpoints can be invoked with the prefix�*clientToken*�as
follows:
@@ -254,9 +240,7 @@ URI Options for�_clientToken_
|request |com.braintreegateway.ClientTokenrequest
|================================================
-[[Braintree-EndpointprefixcreditCardVerification]]
-Endpoint prefix�_creditCardVerification_
-++++++++++++++++++++++++++++++++++++++++
+#### Endpoint prefix�_creditCardVerification_
The following endpoints can be invoked with the
prefix�*creditCardverification*�as follows:
@@ -287,9 +271,7 @@ URI Options for�_creditCardVerification_
|query |com.braintreegateway.CreditCardVerificationSearchRequest
|===============================================================
-[[Braintree-Endpointprefixcustomer]]
-Endpoint prefix�_customer_
-++++++++++++++++++++++++++
+#### Endpoint prefix�_customer_
The following endpoints can be invoked with the prefix�*customer*�as
follows:
@@ -332,9 +314,7 @@ URI Options for�_customer_
|query |com.braintreegateway.CustomerSearchRequest
|=================================================
-[[Braintree-Endpointprefixdiscount]]
-Endpoint prefix�_discount_
-++++++++++++++++++++++++++
+#### Endpoint prefix�_discount_
The following endpoints can be invoked with the prefix�*discount*�as
follows:
@@ -356,9 +336,7 @@ braintree://discount/endpoint
+
-[[Braintree-EndpointprefixmerchantAccount]]
-Endpoint prefix�_merchantAccount_
-+++++++++++++++++++++++++++++++++
+#### Endpoint prefix�_merchantAccount_
The following endpoints can be invoked with the
prefix�*merchantAccount*�as follows:
@@ -392,9 +370,7 @@ URI Options for�_merchantAccount_
|request |com.braintreegateway.MerchantAccountRequest
|====================================================
-[[Braintree-EndpointprefixpaymentMethod]]
-Endpoint prefix�_paymentMethod_
-+++++++++++++++++++++++++++++++
+#### Endpoint prefix�_paymentMethod_
The following endpoints can be invoked with the
prefix�*paymentMethod*�as follows:
@@ -431,9 +407,7 @@ URI Options for�_paymentMethod_
|request |com.braintreegateway.PaymentMethodRequest
|==================================================
-[[Braintree-EndpointprefixpaymentMethodNonce]]
-Endpoint prefix�_paymentMethodNonce_
-++++++++++++++++++++++++++++++++++++
+#### Endpoint prefix�_paymentMethodNonce_
The following endpoints can be invoked with the
prefix�*paymentMethodNonce*�as follows:
@@ -464,9 +438,7 @@ URI Options for�_paymentMethodNonce_
|paymentMethodNonce |String
|==========================
-[[Braintree-Endpointprefixplan]]
-Endpoint prefix�_plan_
-++++++++++++++++++++++
+#### Endpoint prefix�_plan_
The following endpoints can be invoked with the prefix�*plan*�as
follows:
@@ -486,9 +458,7 @@ braintree://plan/endpoint
�
-[[Braintree-EndpointprefixsettlementBatchSummary]]
-Endpoint prefix�_settlementBatchSummary_
-++++++++++++++++++++++++++++++++++++++++
+#### Endpoint prefix�_settlementBatchSummary_
The following endpoints can be invoked with the
prefix�*settlementBatchSummary*�as follows:
@@ -517,9 +487,7 @@ URI Options for�_settlementBatchSummary_
|groupByCustomField |String
|==========================
-[[Braintree-Endpointprefixsubscription]]
-Endpoint prefix�_subscription_
-++++++++++++++++++++++++++++++
+#### Endpoint prefix�_subscription_
The following endpoints can be invoked with the prefix�*subscription*�as
follows:
@@ -571,9 +539,7 @@ URI Options for�_subscription_
�
-[[Braintree-Endpointprefixtransaction]]
-Endpoint prefix�_transaction_
-+++++++++++++++++++++++++++++
+#### Endpoint prefix�_transaction_
The following endpoints can be invoked with the prefix�*transaction*�as
follows:
@@ -637,9 +603,7 @@ URI Options for�_transaction_
|query |com.braintreegateway.TransactionSearchRequest
|==========================================================
-[[Braintree-EndpointprefixwebhookNotification]]
-Endpoint prefix�_webhookNotification_
-+++++++++++++++++++++++++++++++++++++
+#### Endpoint prefix�_webhookNotification_
The following endpoints can be invoked with the
prefix�*webhookNotification*�as follows:
@@ -671,9 +635,7 @@ URI Options for�_webhookNotification_
�
-[[Braintree-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
Any of the producer endpoints can be used as a consumer endpoint.
Consumer endpoints can
@@ -685,16 +647,12 @@ be executed once for each exchange. To change this behavior use the
property�*consumer.splitResults=true*�to return a single exchange for
the entire list or array.�
-[[Braintree-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Any URI option can be provided in a message header for producer
endpoints with a�*CamelBraintree.*�prefix.
-[[Braintree-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
All result message bodies utilize objects provided by the Braintree Java
SDK. Producer endpoints can specify the option name for incoming message
@@ -704,9 +662,7 @@ body in the�*inBody*�endpoint parameter.
�
-[[Braintree-Examples]]
-Examples
-^^^^^^^^
+### Examples
*Blueprint*
@@ -746,9 +702,7 @@ Examples
</blueprint>
--------------------------------------------------------------------------------------------------------------------------------------------
-[[Braintree-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
*
https://cwiki.apache.org/confluence/display/CAMEL/Configuring+Camel[Configuring
@@ -761,4 +715,4 @@ Started]
�
-https://cwiki.apache.org/confluence/display/CAMEL/AMQP[�]
+https://cwiki.apache.org/confluence/display/CAMEL/AMQP[�]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-cache/src/main/docs/cache-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-cache/src/main/docs/cache-component.adoc b/components/camel-cache/src/main/docs/cache-component.adoc
index 379c0a8..b5ef8a2 100644
--- a/components/camel-cache/src/main/docs/cache-component.adoc
+++ b/components/camel-cache/src/main/docs/cache-component.adoc
@@ -1,4 +1,4 @@
-# EHCache Component
+## EHCache Component
*Available as of Camel 2.1*
@@ -27,9 +27,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Cache-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------
@@ -39,9 +37,7 @@ cache://cacheName[?options]
You can append query options to the URI in the following format,
`?option=value&option=#beanRef&...`
-[[Cache-Options]]
-Options
-^^^^^^^
+### Options
@@ -100,13 +96,9 @@ The EHCache component supports 20 endpoint options which are listed below:
// endpoint options: END
-[[Cache-SendingReceivingMessagestofromthecache]]
-Sending/Receiving Messages to/from the cache
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending/Receiving Messages to/from the cache
-[[Cache-MessageHeadersuptoCamel2.7]]
-Message Headers up to Camel 2.7
-+++++++++++++++++++++++++++++++
+#### Message Headers up to Camel 2.7
[width="100%",cols="20%,80%",options="header",]
|=======================================================================
@@ -125,9 +117,7 @@ Message Headers up to Camel 2.7
|`CACHE_KEY` |The cache key used to store the Message in the cache. The cache key is
optional if the CACHE_OPERATION is DELETEALL
|=======================================================================
-[[Cache-MessageHeadersCamel2.8]]
-Message Headers Camel 2.8+
-++++++++++++++++++++++++++
+#### Message Headers Camel 2.8+
[Info]
====
@@ -173,9 +163,7 @@ headers:
|`CamelCacheEternal` |`Boolean` |*Camel 2.11:* Whether the content is eternal.
|=======================================================================
-[[Cache-CacheProducer]]
-Cache Producer
-++++++++++++++
+#### Cache Producer
Sending data to the cache involves the ability to direct payloads in
exchanges to be stored in a pre-existing or created-on-demand cache. The
@@ -185,9 +173,7 @@ mechanics of doing this involve
* ensuring that the Message Exchange Body contains the message directed
to the cache
-[[Cache-CacheConsumer]]
-Cache Consumer
-++++++++++++++
+#### Cache Consumer
Receiving data from the cache involves the ability of the CacheConsumer
to listen on a pre-existing or created-on-demand Cache using an event
@@ -201,9 +187,7 @@ Body containing the just added/updated payload is placed and sent.
* in case of a CamelCacheDeleteAll operation, the Message Exchange
Header CamelCacheKey and the Message Exchange Body are not populated.
-[[Cache-CacheProcessors]]
-Cache Processors
-++++++++++++++++
+#### Cache Processors
There are a set of nice processors with the ability to perform cache
lookups and selectively replace payload content at the
@@ -212,13 +196,9 @@ lookups and selectively replace payload content at the
* token
* xpath level
-[[Cache-CacheUsageSamples]]
-Cache Usage Samples
-^^^^^^^^^^^^^^^^^^^
+### Cache Usage Samples
-[[Cache-Example1:Configuringthecache]]
-Example 1: Configuring the cache
-++++++++++++++++++++++++++++++++
+#### Example 1: Configuring the cache
[source,java]
-------------------------------------------------
@@ -234,9 +214,7 @@ from("cache://MyApplicationCache" +
"&diskExpiryThreadIntervalSeconds=300")
-------------------------------------------------
-[[Cache-Example2:Addingkeystothecache]]
-Example 2: Adding keys to the cache
-+++++++++++++++++++++++++++++++++++
+#### Example 2: Adding keys to the cache
[source,java]
---------------------------------------------------------------------------------------------
@@ -250,9 +228,7 @@ RouteBuilder builder = new RouteBuilder() {
};
---------------------------------------------------------------------------------------------
-[[Cache-Example2:Updatingexistingkeysinacache]]
-Example 2: Updating existing keys in a cache
-++++++++++++++++++++++++++++++++++++++++++++
+#### Example 2: Updating existing keys in a cache
[source,java]
------------------------------------------------------------------------------------------------
@@ -266,9 +242,7 @@ RouteBuilder builder = new RouteBuilder() {
};
------------------------------------------------------------------------------------------------
-[[Cache-Example3:Deletingexistingkeysinacache]]
-Example 3: Deleting existing keys in a cache
-++++++++++++++++++++++++++++++++++++++++++++
+#### Example 3: Deleting existing keys in a cache
[source,java]
--------------------------------------------------------------------------------------
@@ -282,9 +256,7 @@ RouteBuilder builder = new RouteBuilder() {
};
--------------------------------------------------------------------------------------
-[[Cache-Example4:Deletingallexistingkeysinacache]]
-Example 4: Deleting all existing keys in a cache
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 4: Deleting all existing keys in a cache
[source,java]
-----------------------------------------------------------------------------------------
@@ -297,9 +269,7 @@ RouteBuilder builder = new RouteBuilder() {
};
-----------------------------------------------------------------------------------------
-[[Cache-Example5:NotifyinganychangesregisteringinaCachetoProcessorsandotherProducers]]
-Example 5: Notifying any changes registering in a Cache to Processors and other Producers
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 5: Notifying any changes registering in a Cache to Processors and other Producers
[source,java]
--------------------------------------------------------------------------------------------------
@@ -319,9 +289,7 @@ RouteBuilder builder = new RouteBuilder() {
};
--------------------------------------------------------------------------------------------------
-[[Cache-Example6:UsingProcessorstoselectivelyreplacepayloadwithcachevalues]]
-Example 6: Using Processors to selectively replace payload with cache values
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 6: Using Processors to selectively replace payload with cache values
[source,java]
---------------------------------------------------------------------------------------
@@ -351,9 +319,7 @@ RouteBuilder builder = new RouteBuilder() {
};
---------------------------------------------------------------------------------------
-[[Cache-Example7:GettinganentryfromtheCache]]
-Example 7: Getting an entry from the Cache
-++++++++++++++++++++++++++++++++++++++++++
+#### Example 7: Getting an entry from the Cache
[source,java]
------------------------------------------------------------------------------------------------
@@ -373,9 +339,7 @@ from("direct:start")
.to("direct:nextPhase");
------------------------------------------------------------------------------------------------
-[[Cache-Example8:CheckingforanentryintheCache]]
-Example 8: Checking for an entry in the Cache
-+++++++++++++++++++++++++++++++++++++++++++++
+#### Example 8: Checking for an entry in the Cache
Note: The CHECK command tests existence of an entry in the cache but
doesn't place a message in the body.
@@ -397,9 +361,7 @@ from("direct:start")
.end();
------------------------------------------------------------------------------------------------
-[[Cache-ManagementofEHCache]]
-Management of EHCache
-^^^^^^^^^^^^^^^^^^^^^
+### Management of EHCache
http://ehcache.org/[EHCache] has its own statistics and management from
link:camel-jmx.html[JMX].
@@ -433,9 +395,7 @@ ManagementService.registerMBeans(CacheManager.getInstance(), mbeanServer, true,
You can get cache hits, misses, in-memory hits, disk hits, size stats
this way. You can also change CacheConfiguration parameters on the fly.
-[[Cache-CachereplicationCamel2.8]]
-Cache replication Camel 2.8
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Cache replication Camel 2.8
The Camel Cache component is able to distribute a cache across server
nodes using several different replication mechanisms including: RMI,
@@ -474,12 +434,9 @@ mechanism.
====
-[[Cache-Example:JMScachereplication]]
-Example: JMS cache replication
-++++++++++++++++++++++++++++++
+#### Example: JMS cache replication
JMS replication is the most powerful and secured replication method.
Used together with Camel Cache replication makes it also rather
simple. An example is available on link:cachereplicationjmsexample.html[a
-separate page].
-
+separate page].
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-cassandraql/src/main/docs/cql-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-cassandraql/src/main/docs/cql-component.adoc b/components/camel-cassandraql/src/main/docs/cql-component.adoc
index 7339d21..3241c79 100644
--- a/components/camel-cassandraql/src/main/docs/cql-component.adoc
+++ b/components/camel-cassandraql/src/main/docs/cql-component.adoc
@@ -1,4 +1,4 @@
-# Cassandra CQL Component
+## Cassandra CQL Component
[[Cassandra-CamelCassandraComponent]]
Camel Cassandra Component
-------------------------
@@ -33,9 +33,7 @@ Maven users will need to add the following dependency to their
</dependency>
------------------------------------------------------------
-[[Cassandra-URIformat]]
-URI format
-~~~~~~~~~~
+### URI format
The endpoint can initiate the Cassandra connection or use an existing
one.
@@ -55,9 +53,7 @@ To fine tune the Cassandra connection (SSL options, pooling options,
load balancing policy, retry policy, reconnection policy...), create
your own Cluster instance and give it to the Camel endpoint.
-[[Cassandra-Options]]
-Cassandra Options
-~~~~~~~~~~~~~~~~~
+### Cassandra Options
// component options: START
@@ -96,13 +92,9 @@ The Cassandra CQL component supports 18 endpoint options which are listed below:
// endpoint options: END
-[[Cassandra-Messages]]
-Messages
-~~~~~~~~
+### Messages
-[[Cassandra-IncomingMessage]]
-Incoming Message
-^^^^^^^^^^^^^^^^
+### Incoming Message
The Camel Cassandra endpoint expects a bunch of simple objects (`Object`
or `Object[]` or `Collection<Object>`) which will be bound to the CQL
@@ -114,9 +106,7 @@ Headers:
* `CamelCqlQuery` (optional, `String` or `RegularStatement`): CQL query
either as a plain String or built using the `QueryBuilder`.
-[[Cassandra-OutgoingMessage]]
-Outgoing Message
-^^^^^^^^^^^^^^^^
+### Outgoing Message
The Camel Cassandra endpoint produces one or many a Cassandra Row
objects depending on the�`resultSetConversionStrategy`:
@@ -129,9 +119,7 @@ objects depending on the�`resultSetConversionStrategy`:
* Anything else, if `resultSetConversionStrategy` is a custom
implementation of the `ResultSetConversionStrategy`
-[[Cassandra-Repositories]]
-Repositories
-~~~~~~~~~~~~
+### Repositories
Cassandra can be used to store message keys or messages for the
idempotent and aggregation EIP.
@@ -142,9 +130,7 @@ anti-patterns queues and queue like datasets]. It's advised to use
LeveledCompaction and a small GC grace setting for these tables to allow
tombstoned rows to be removed quickly.
-[[Cassandra-Idempotentrepository]]
-Idempotent repository
-^^^^^^^^^^^^^^^^^^^^^
+### Idempotent repository
The `NamedCassandraIdempotentRepository` stores messages keys in a
Cassandra table like this:
@@ -186,9 +172,7 @@ Alternatively, the `CassandraIdempotentRepository` does not have a
`LOCAL_QUORUM`\u2026
|=======================================================================
-[[Cassandra-Aggregationrepository]]
-Aggregation repository
-^^^^^^^^^^^^^^^^^^^^^^
+### Aggregation repository
The `NamedCassandraAggregationRepository` stores exchanges by
correlation key in a Cassandra table like this:
@@ -231,4 +215,4 @@ Alternatively, the `CassandraAggregationRepository` does not have a
|`readConsistencyLevel` | | Consistency level used to read/check exchange: `ONE`, `TWO`, `QUORUM`,
`LOCAL_QUORUM`\u2026
-|=======================================================================
+|=======================================================================
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-castor/src/main/docs/castor-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-castor/src/main/docs/castor-dataformat.adoc b/components/camel-castor/src/main/docs/castor-dataformat.adoc
index bbf4b00..abf7192 100644
--- a/components/camel-castor/src/main/docs/castor-dataformat.adoc
+++ b/components/camel-castor/src/main/docs/castor-dataformat.adoc
@@ -1,4 +1,4 @@
-# Castor DataFormat
+## Castor DataFormat
*Available as of Camel 2.1*
@@ -9,9 +9,7 @@ into Java objects or to marshal Java objects into an XML payload.
As usually you can use either Java DSL or Spring XML to work with Castor
Data Format.
-[[Castor-UsingtheJavaDSL]]
-Using the Java DSL
-^^^^^^^^^^^^^^^^^^
+### Using the Java DSL
[source,java]
-----------------------------
@@ -60,9 +58,7 @@ castor.getMarshaller();
castor.getUnmarshaller();
-------------------------
-[[Castor-UsingSpringXML]]
-Using Spring XML
-^^^^^^^^^^^^^^^^
+### Using Spring XML
The following example shows how to use Castor to unmarshal using Spring
configuring the castor data type
@@ -106,9 +102,7 @@ on multiple routes. You have to set the <castor> element directly in
</camelContext>
-----------------------------------------------------------------------
-[[Castor-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The Castor dataformat supports 6 options which are listed below.
@@ -129,9 +123,7 @@ The Castor dataformat supports 6 options which are listed below.
{% endraw %}
// dataformat options: END
-[[Castor-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Castor in your camel routes you need to add the a dependency on
*camel-castor* which implements this data format.
@@ -147,4 +139,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-castor</artifactId>
<version>x.x.x</version>
</dependency>
----------------------------------------
+---------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-chronicle/src/main/docs/chronicle-engine-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-chronicle/src/main/docs/chronicle-engine-component.adoc b/components/camel-chronicle/src/main/docs/chronicle-engine-component.adoc
index 39520e7..ffbb797 100644
--- a/components/camel-chronicle/src/main/docs/chronicle-engine-component.adoc
+++ b/components/camel-chronicle/src/main/docs/chronicle-engine-component.adoc
@@ -1,4 +1,4 @@
-# Chronicle Engine Component
+## Chronicle Engine Component
// component options: START
The Chronicle Engine component has no options.
@@ -28,5 +28,4 @@ The Chronicle Engine component supports 13 endpoint options which are listed bel
| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
|=======================================================================
{% endraw %}
-// endpoint options: END
-
+// endpoint options: END
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-chunk/src/main/docs/chunk-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-chunk/src/main/docs/chunk-component.adoc b/components/camel-chunk/src/main/docs/chunk-component.adoc
index 2d6e261..71b6750 100644
--- a/components/camel-chunk/src/main/docs/chunk-component.adoc
+++ b/components/camel-chunk/src/main/docs/chunk-component.adoc
@@ -1,4 +1,4 @@
-# Chunk Component
+## Chunk Component
*Available as of Camel 2.15*
@@ -19,9 +19,7 @@ their�`pom.xml`�for this component:
</dependency>
---------------------------------------------------------------------------------
-[[Chunk-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------
@@ -34,9 +32,7 @@ invoke.
You can append query options to the URI in the following
format,�`?option=value&option=value&...`
-[[Chunk-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -70,9 +66,7 @@ with extensions _.chtml_ or _.cxml.�_If you need to specify a different
folder or extensions, you will need to use the specific options listed
above.
-[[Chunk-ChunkContext]]
-Chunk Context
-^^^^^^^^^^^^^
+### Chunk Context
Camel will provide exchange information in the Chunk context (just
a�`Map`). The�`Exchange`�is transferred as:
@@ -97,9 +91,7 @@ a�`Map`). The�`Exchange`�is transferred as:
|`response` |The Out message (only for InOut message exchange pattern).
|=======================================================================
-[[Chunk-Dynamictemplates]]
-Dynamic templates
-^^^^^^^^^^^^^^^^^
+### Dynamic templates
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these
@@ -116,9 +108,7 @@ configured. |
|ChunkConstants.CHUNK_TEMPLATE |String |The template to use instead of the endpoint configured. |
|=======================================================================
-[[Chunk-Samples]]
-Samples
-^^^^^^^
+### Samples
For example you could use something like:
@@ -162,9 +152,7 @@ to("chunk:file_example?themeFolder=template&themeSubfolder=subfolder&extension=c
In this example Chunk component will look for the file
_file_example.chunk_ in the folder _template/subfolder._
-[[Chunk-TheEmailSample]]
-The Email Sample
-^^^^^^^^^^^^^^^^
+### The Email Sample
In this sample we want to use Chunk templating for an order confirmation
email. The email template is laid out in Chunk as:
@@ -180,12 +168,9 @@ Regards Camel Riders Bookstore
{$body}
----------------------------------------------
-[[Chunk-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-cm-sms/src/main/docs/cm-sms-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-cm-sms/src/main/docs/cm-sms-component.adoc b/components/camel-cm-sms/src/main/docs/cm-sms-component.adoc
index 3597945..7d60904 100644
--- a/components/camel-cm-sms/src/main/docs/cm-sms-component.adoc
+++ b/components/camel-cm-sms/src/main/docs/cm-sms-component.adoc
@@ -1,4 +1,4 @@
-# CM SMS Gateway Component
+## CM SMS Gateway Component
*Available as of Camel 2.18*
@@ -27,9 +27,7 @@ for this component:
</dependency>
---------------------------------------------------------
-[[CM-SMS-Options]]
-Options
-~~~~~~~
+### Options
// component options: START
@@ -56,8 +54,6 @@ The CM SMS Gateway component supports 6 endpoint options which are listed below:
// endpoint options: END
-[[CM-SMS-Sample]]
-Sample
-~~~~~~
+### Sample
-You can try https://github.com/oalles/camel-cm-sample[this project] to see how camel-cm-sms can be integrated in a camel route.
+You can try https://github.com/oalles/camel-cm-sample[this project] to see how camel-cm-sms can be integrated in a camel route.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-cmis/src/main/docs/cmis-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-cmis/src/main/docs/cmis-component.adoc b/components/camel-cmis/src/main/docs/cmis-component.adoc
index a57e5d1..1abc87e 100644
--- a/components/camel-cmis/src/main/docs/cmis-component.adoc
+++ b/components/camel-cmis/src/main/docs/cmis-component.adoc
@@ -1,4 +1,4 @@
-# CMIS Component
+## CMIS Component
*Available as of Camel 2.11* +
The cmis component uses the
@@ -6,9 +6,7 @@ http://chemistry.apache.org/java/opencmis.html[Apache Chemistry] client
API and allows you to add/read nodes to/from a CMIS compliant content
repositories.
-[[CMIS-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
[source,java]
------------------------------
@@ -18,9 +16,7 @@ cmis://cmisServerUrl[?options]
You can append query options to the URI in the following format,
?options=value&option2=value&...
-[[CMIS-URIOptions]]
-CMIS Options
-^^^^^^^^^^^^
+### CMIS Options
// component options: START
@@ -65,13 +61,9 @@ The CMIS component supports 14 endpoint options which are listed below:
// endpoint options: END
-[[CMIS-Usage]]
-Usage
-^^^^^
+### Usage
-[[CMIS-Messageheadersevaluatedbytheproducer]]
-Message headers evaluated by the producer
-+++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the producer
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -96,9 +88,7 @@ the node from this cmis property and it is path
|`cmis:contentStreamMimeType` |`null` |The mimetype to set for a document
|=======================================================================
-[[CMIS-MessageheaderssetduringqueryingProduceroperation]]
-Message headers set during querying Producer operation
-++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set during querying Producer operation
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -112,9 +102,7 @@ map is cmis property and its value. If `CamelCMISRetrieveContent` header is set
entry in the map with key `CamelCMISContent` will contain `InputStream`
of the document type of nodes.
-[[CMIS-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
Maven users will need to add the following dependency to their pom.xml.
@@ -132,12 +120,9 @@ Maven users will need to add the following dependency to their pom.xml.
where `${camel-version`} must be replaced by the actual version of Camel
(2.11 or higher).
-[[CMIS-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-coap/src/main/docs/coap-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-coap/src/main/docs/coap-component.adoc b/components/camel-coap/src/main/docs/coap-component.adoc
index 111cc7c..e7719c4 100644
--- a/components/camel-coap/src/main/docs/coap-component.adoc
+++ b/components/camel-coap/src/main/docs/coap-component.adoc
@@ -1,4 +1,4 @@
-# CoAP Component
+## CoAP Component
*Camel-CoAP* is an http://camel.apache.org/[Apache Camel] component that
allows you to work with CoAP, a lightweight REST-type protocol for machine-to-machine operation.
@@ -20,9 +20,7 @@ for this component:
</dependency>
---------------------------------------------------------
-[[CoAP-Options]]
-Options
-~~~~~~~
+### Options
// component options: START
@@ -47,6 +45,4 @@ The CoAP component supports 6 endpoint options which are listed below:
| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
|=======================================================================
{% endraw %}
-// endpoint options: END
-
-
+// endpoint options: END
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-cometd/src/main/docs/cometd-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-cometd/src/main/docs/cometd-component.adoc b/components/camel-cometd/src/main/docs/cometd-component.adoc
index 0e651fb..1ab0cf7 100644
--- a/components/camel-cometd/src/main/docs/cometd-component.adoc
+++ b/components/camel-cometd/src/main/docs/cometd-component.adoc
@@ -1,4 +1,4 @@
-# CometD Component
+## CometD Component
The *cometd:* component is a transport for working with the
http://www.mortbay.org/jetty[jetty] implementation of the
@@ -21,9 +21,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Cometd-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------------------
@@ -33,9 +31,7 @@ cometd://host:port/channelName[?options]
The *channelName* represents a topic that can be subscribed to by the
Camel endpoints.
-[[Cometd-Examples]]
-Examples
-^^^^^^^^
+### Examples
------------------------------------------
cometd://localhost:8080/service/mychannel
@@ -44,9 +40,7 @@ cometds://localhost:8443/service/mychannel
where `cometds:` represents an SSL configured endpoint.
-[[Cometd-Options]]
-Options
-^^^^^^^
+### Options
@@ -118,9 +112,7 @@ For file (for webapp resources located in the Web Application directory
the webapp folder -->
cometd://localhost:8080?resourceBase=classpath:webapp
-[[Cometd-Authentication]]
-Authentication
-^^^^^^^^^^^^^^
+### Authentication
*Available as of Camel 2.8*
@@ -128,13 +120,9 @@ You can configure custom `SecurityPolicy` and `Extension`'s to the
`CometdComponent` which allows you to use authentication as
http://cometd.org/documentation/howtos/authentication[documented here]
-[[Cometd-SettingupSSLforCometdComponent]]
-Setting up SSL for Cometd Component
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting up SSL for Cometd Component
-[[Cometd-UsingtheJSSEConfigurationUtility]]
-Using the JSSE Configuration Utility
-++++++++++++++++++++++++++++++++++++
+#### Using the JSSE Configuration Utility
As of Camel 2.9, the Cometd component supports SSL/TLS configuration
through the link:camel-configuration-utilities.html[Camel JSSE
@@ -196,12 +184,9 @@ Spring DSL based configuration of endpoint
<to uri="cometds://127.0.0.1:443/service/test?baseResource=file:./target/test-classes/webapp&timeout=240000&interval=0&maxInterval=30000&multiFrameInterval=1500&jsonCommented=true&logLevel=2"/>...
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[Cometd-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-consul/src/main/docs/consul-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-consul/src/main/docs/consul-component.adoc b/components/camel-consul/src/main/docs/consul-component.adoc
index 5f8b92d..6cb0fe0 100644
--- a/components/camel-consul/src/main/docs/consul-component.adoc
+++ b/components/camel-consul/src/main/docs/consul-component.adoc
@@ -1,4 +1,4 @@
-# Consul Component
+## Consul Component
*Available as of Camel 2.18*
@@ -16,9 +16,7 @@ for this component:
</dependency>
-------------------------------------------------
-[[Consul-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------
@@ -31,9 +29,7 @@ You can append query options to the URI in the following format:
?option=value&option=value&...
---------------------------------------
-[[Consul-Options]]
-Options
-^^^^^^^
+### Options
@@ -83,9 +79,7 @@ The Consul component supports 22 endpoint options which are listed below:
-[[Consul-Headers]]
-Headers
-^^^^^^^
+### Headers
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -107,4 +101,4 @@ Headers
|CamelConsulResult|boolean|true if the response has a result
|CamelConsulSession|String|The session id
|CamelConsulValueAsString|boolean|To transform values retrieved from Consul i.e. on KV endpoint to string.
-|=======================================================================
+|=======================================================================
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-context/src/main/docs/context-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-context/src/main/docs/context-component.adoc b/components/camel-context/src/main/docs/context-component.adoc
index ec848d7..c903519 100644
--- a/components/camel-context/src/main/docs/context-component.adoc
+++ b/components/camel-context/src/main/docs/context-component.adoc
@@ -1,4 +1,4 @@
-# Camel Context Component
+## Camel Context Component
*Available as of Camel 2.7*
@@ -25,9 +25,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Context-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
--------------------------------------------------
@@ -70,16 +68,12 @@ The Camel Context component supports 6 endpoint options which are listed below:
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Context-Example]]
-Example
-^^^^^^^
+### Example
In this example we'll create a black box context, then we'll use it from
another CamelContext.
-[[Context-Definingthecontextcomponent]]
-Defining the context component
-++++++++++++++++++++++++++++++
+#### Defining the context component
First you need to create a CamelContext, add some routes in it, start it
and then register the CamelContext into the link:registry.html[Registry]
@@ -125,9 +119,7 @@ ID. We can do the same thing in Spring via
</camelContext>
--------------------------------------------------------------------------
-[[Context-Usingthecontextcomponent]]
-Using the context component
-+++++++++++++++++++++++++++
+#### Using the context component
Then in another CamelContext we can then refer to this "accounts black
box" by just sending to *accounts:purchaseOrder* and consuming from
@@ -158,9 +150,7 @@ middleware (outside of the black box) we can do things like...
</camelContext>
--------------------------------------------------------------------------------
-[[Context-Namingendpoints]]
-Naming endpoints
-++++++++++++++++
+#### Naming endpoints
A context component instance can have many public input and output
endpoints that can be accessed from outside it's CamelContext. When
@@ -169,4 +159,4 @@ hide the middleware as shown above.
However when there is only one input, output or error/dead letter
endpoint in a component we recommend using the common posix shell names
-*in*, *out* and *err*
+*in*, *out* and *err*
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-couchdb/src/main/docs/couchdb-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-couchdb/src/main/docs/couchdb-component.adoc b/components/camel-couchdb/src/main/docs/couchdb-component.adoc
index 07d8827..14ada92 100644
--- a/components/camel-couchdb/src/main/docs/couchdb-component.adoc
+++ b/components/camel-couchdb/src/main/docs/couchdb-component.adoc
@@ -1,4 +1,4 @@
-# CouchDB Component
+## CouchDB Component
*Available as of Camel 2.11*
@@ -31,9 +31,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[CouchDB-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------------------------
@@ -43,9 +41,7 @@ couchdb:http://hostname[:port]/database?[options]
Where *hostname* is the hostname of the running couchdb instance. Port
is optional and if not specified then defaults to 5984.
-[[CouchDB-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The CouchDB component has no options.
@@ -77,9 +73,7 @@ The CouchDB component supports 15 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[CouchDB-Headers]]
-Headers
-^^^^^^^
+### Headers
The following headers are set on exchanges during message transport.
@@ -105,9 +99,7 @@ ignored. That means for example, if you set CouchDbId as a header, it
will not be used as the id for insertion, the id of the document will
still be used.
-[[CouchDB-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
The component will use the message body as the document to be inserted.
If the body is an instance of String, then it will be marshalled into a
@@ -116,9 +108,7 @@ or the insert / update will fail. If the body is an instance of a
com.google.gson.JsonElement then it will be inserted as is. Otherwise
the producer will throw an exception of unsupported body type.
-[[CouchDB-Samples]]
-Samples
-^^^^^^^
+### Samples
For example if you wish to consume all inserts, updates and deletes from
a CouchDB instance running locally, on port 9999 then you could use the
@@ -142,4 +132,4 @@ exchange is used
[source,java]
----------------------------------------------------------------------------------------
from("someProducingEndpoint").process(someProcessor).to("couchdb:http://localhost:9999")
-----------------------------------------------------------------------------------------
+----------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-crypto/src/main/docs/crypto-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-crypto/src/main/docs/crypto-component.adoc b/components/camel-crypto/src/main/docs/crypto-component.adoc
index d9ed64f..1550211 100644
--- a/components/camel-crypto/src/main/docs/crypto-component.adoc
+++ b/components/camel-crypto/src/main/docs/crypto-component.adoc
@@ -1,4 +1,4 @@
-# Crypto (JCE) Component
+## Crypto (JCE) Component
*Available as of Camel 2.3*
*PGP Available as of Camel 2.9*
@@ -11,9 +11,7 @@ encryption to cyphertext and unmarshalling to mean decryption back to
the original plaintext. This data format implements only symmetric
(shared-key) encryption and decyption.
-[[Crypto-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
The Crypto (JCE) component supports 1 options which are listed below.
@@ -61,9 +59,7 @@ The Crypto (JCE) component supports 21 endpoint options which are listed below:
{% endraw %}
// endpoint options: END
-[[Crypto-BasicUsage]]
-Basic Usage
-^^^^^^^^^^^
+### Basic Usage
At its most basic all that is required to encrypt/decrypt an exchange is
a shared secret key. If one or more instances of the Crypto data format
@@ -90,9 +86,7 @@ In Spring the dataformat is configured first and then used in routes
</camelContext>
-----------------------------------------------------------------------
-[[Crypto-SpecifyingtheEncryptionAlgorithm]]
-Specifying the Encryption Algorithm
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Specifying the Encryption Algorithm
Changing the algorithm is a matter of supplying the JCE algorithm name.
If you change the algorithm you will need to use a compatible key.
@@ -101,9 +95,7 @@ A list of the available algorithms in Java 7 is available via the
http://docs.oracle.com/javase/7/docs/technotes/guides/security/StandardNames.html[Java
Cryptography Architecture Standard Algorithm Name Documentation].
-[[Crypto-SpecifyinganInitializationVector]]
-Specifying an Initialization Vector
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Specifying an Initialization Vector
Some crypto algorithms, particularly block algorithms, require
configuration with an initial block of data known as an Initialization
@@ -130,9 +122,7 @@ http://www.herongyang.com/Cryptography/[http://www.herongyang.com/Cryptography/]
*
http://en.wikipedia.org/wiki/Block_cipher_modes_of_operation[http://en.wikipedia.org/wiki/Block_cipher_modes_of_operation]
-[[Crypto-HashedMessageAuthenticationCodes(HMAC)]]
-Hashed Message Authentication Codes (HMAC)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Hashed Message Authentication Codes (HMAC)
To avoid attacks against the encrypted data while it is in transit the
CryptoDataFormat can also calculate a Message Authentication Code for
@@ -155,9 +145,7 @@ security providers
or with spring.
-[[Crypto-SupplyingKeysDynamically]]
-Supplying Keys Dynamically
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Supplying Keys Dynamically
When using a Recipient list or similar EIP the recipient of an exchange
can vary dynamically. Using the same key across all recipients may
@@ -171,9 +159,7 @@ allow for keys to be supplied dynamically via the message headers below
or with spring.
-[[Crypto-PGPMessage]]
-PGP Message
-^^^^^^^^^^^
+### PGP Message
The PGP Data Formater can create and decrypt/verify PGP Messages of the
following PGP packet structure (entries in brackets are optional and
@@ -189,9 +175,7 @@ was mandatory.
�
-[[Crypto-PGPDataFormatOptions]]
-PGPDataFormat Options
-^^^^^^^^^^^^^^^^^^^^^
+### PGPDataFormat Options
[width="70%",cols="10%,10%,10%,70%",options="header",]
|=======================================================================
|Name |Type |Default |Description
@@ -320,9 +304,7 @@ then no Compressed Data packet is added and the compressionAlgorithm
value is ignored. Only used for marshaling.
|=======================================================================
-[[Crypto-PGPDataFormatMessageHeaders]]
-PGPDataFormat Message Headers
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### PGPDataFormat Message Headers
You can override the PGPDataFormat options by applying below headers
into message dynamically.
@@ -377,9 +359,7 @@ symmectric key, set by PGPDataFormat during encryptiion process
signatures, set by PGPDataFormat during signing process
|=======================================================================
-[[Crypto-EncryptingwithPGPDataFormat]]
-Encrypting with PGPDataFormat
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Encrypting with PGPDataFormat
The following sample uses the popular PGP format for
encrypting/decrypting files using the
@@ -391,9 +371,7 @@ encryption, but you can obviously use different keys:
Or using Spring:
-[[Crypto-Toworkwiththepreviousexampleyouneedthefollowing]]
-To work with the previous example you need the following
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### To work with the previous example you need the following
* A public keyring file which contains the public keys used to encrypt
the data
@@ -401,9 +379,7 @@ the data
data
* The keyring password
-[[Crypto-Managingyourkeyring]]
-Managing your keyring
-+++++++++++++++++++++
+#### Managing your keyring
To manage the keyring, I use the command line tools, I find this to be
the simplest approach in managing the keys. There are also Java
@@ -440,8 +416,7 @@ ls -l ~/.gnupg/pubring.gpg ~/.gnupg/secring.gpg
[[Crypto-PGPDecrypting/VerifyingofMessagesEncrypted/SignedbyDifferentPrivate/PublicKeys]]
PGP Decrypting/Verifying of Messages Encrypted/Signed by Different
-Private/Public Keys
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Private/Public Keys
Since *Camel 2.12.2*.
@@ -486,9 +461,7 @@ same mechanism is also used to locate the public key for verifying a
signature. Therefore you no longer must specify User IDs for the
unmarshaling.
-[[Crypto-RestrictingtheSignerIdentitiesduringPGPSignatureVerification]]
-Restricting the Signer Identities during PGP Signature Verification
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Restricting the Signer Identities during PGP Signature Verification
Since�*Camel 2.12.3.*
@@ -525,9 +498,7 @@ successful as soon as one signature can be verified.
then do not specify the signature key User IDs. In this case all public
keys in the public keyring are taken into account.
-[[Crypto-SeveralSignaturesinOnePGPDataFormat]]
-Several Signatures in One PGP Data Format
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Several Signatures in One PGP Data Format
Since�*Camel 2.12.3.*
@@ -557,9 +528,7 @@ from("direct:start")
...
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[Crypto-SupportofSub-KeysandKeyFlagsinPGPDataFormatMarshaler]]
-Support of Sub-Keys and Key Flags in PGP Data Format Marshaler
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Support of Sub-Keys and Key Flags in PGP Data Format Marshaler
Since�*Camel 2.12.3. +
*An https://tools.ietf.org/html/rfc4880#section-12.1[OpenPGP V4 key] can
@@ -574,9 +543,7 @@ these Key Flags of the primary key and sub-keys in order to determine
the right key for signing and encryption. This is necessary because the
primary key and its sub-keys have the same User IDs.
-[[Crypto-SupportofCustomKeyAccessors]]
-Support of Custom Key Accessors
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Support of Custom Key Accessors
Since *Camel 2.13.0. +
*You can implement custom key accessors for encryption/signing. The
@@ -600,9 +567,7 @@ PGPKeyAccessDataFormat has the same options as PGPDataFormat except
password, keyFileName, encryptionKeyRing, signaturePassword,
signatureKeyFileName, and signatureKeyRing.
-[[Crypto-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use the link:crypto.html[Crypto] dataformat in your camel routes you
need to add the following dependency to your pom.
@@ -617,11 +582,8 @@ need to add the following dependency to your pom.
</dependency>
----------------------------------------------------------
-[[Crypto-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:data-format.html[Data Format]
* link:crypto-digital-signatures.html[Crypto (Digital Signatures)]
-* http://www.bouncycastle.org/java.html[http://www.bouncycastle.org/java.html]
-
+* http://www.bouncycastle.org/java.html[http://www.bouncycastle.org/java.html]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-crypto/src/main/docs/crypto-dataformat.adoc b/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
index 3217a2b..11aab01 100644
--- a/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
+++ b/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
@@ -1,4 +1,4 @@
-# Crypto (Java Cryptographic Extension) DataFormat
+## Crypto (Java Cryptographic Extension) DataFormat
The Crypto link:data-format.html[Data Format] integrates the Java
Cryptographic Extension into Camel, allowing simple and flexible
@@ -8,9 +8,7 @@ encryption to cyphertext and unmarshalling to mean decryption back to
the original plaintext. This data format implements only symmetric
(shared-key) encryption and decyption.
-[[Crypto-PGPDataFormatOptions]]
-CryptoDataFormat Options
-^^^^^^^^^^^^^^^^^^^^^^^^
+### CryptoDataFormat Options
// dataformat options: START
The Crypto (Java Cryptographic Extension) dataformat supports 10 options which are listed below.
@@ -36,9 +34,7 @@ The Crypto (Java Cryptographic Extension) dataformat supports 10 options which a
// dataformat options: END
-[[Basic Usage]]
-Basic Usage
-^^^^^^^^^^^
+### Basic Usage
At its most basic all that is required to encrypt/decrypt an exchange is a shared secret key.
If one or more instances of the Crypto data format are configured with this key the format can
@@ -79,8 +75,7 @@ In Spring the dataformat is configured first and then used in routes
----------------------------------------------------------
-Specifying the Encryption Algorithm
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Specifying the Encryption Algorithm
Changing the algorithm is a matter of supplying the JCE algorithm name. If you change the algorithm you will need to use a compatible key.
@@ -102,8 +97,7 @@ from("direct:hmac-algorithm")
A list of the available algorithms in Java 7 is available via the Java Cryptography Architecture Standard Algorithm Name Documentation.
-Specifying an Initialization Vector
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Specifying an Initialization Vector
Some crypto algorithms, particularly block algorithms, require configuration with an initial block of data known as an Initialization Vector.
In the JCE this is passed as an AlgorithmParameterSpec when the Cipher is initialized.
@@ -171,8 +165,7 @@ For more information of the use of Initialization Vectors, consult
* http://en.wikipedia.org/wiki/Block_cipher_modes_of_operation
-Hashed Message Authentication Codes (HMAC)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Hashed Message Authentication Codes (HMAC)
To avoid attacks against the encrypted data while it is in transit the CryptoDataFormat can also calculate a Message Authentication
Code for the encrypted exchange contents based on a configurable MAC algorithm. The calculated HMAC is appended to the stream after encryption.
It is separated from the stream in the decryption phase. The MAC is recalculated and verified against the transmitted version to insure nothing
@@ -225,8 +218,7 @@ or with spring.
----------------------------------------------------------
-Supplying Keys Dynamically
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Supplying Keys Dynamically
When using a Recipient list or similar EIP the recipient of an exchange can vary dynamically.
Using the same key across all recipients may neither be feasible or desirable. It would be useful to be able to specify
@@ -267,9 +259,7 @@ or with spring.
----------------------------------------------------------
-[[Crypto-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use the link:crypto.html[Crypto] dataformat in your camel routes you
need to add the following dependency to your pom.
@@ -284,11 +274,8 @@ need to add the following dependency to your pom.
</dependency>
----------------------------------------------------------
-[[Crypto-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:data-format.html[Data Format]
* link:crypto-digital-signatures.html[Crypto (Digital Signatures)]
-* http://www.bouncycastle.org/java.html[http://www.bouncycastle.org/java.html]
-
+* http://www.bouncycastle.org/java.html[http://www.bouncycastle.org/java.html]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-crypto/src/main/docs/pgp-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-crypto/src/main/docs/pgp-dataformat.adoc b/components/camel-crypto/src/main/docs/pgp-dataformat.adoc
index 8706510..71a2596 100644
--- a/components/camel-crypto/src/main/docs/pgp-dataformat.adoc
+++ b/components/camel-crypto/src/main/docs/pgp-dataformat.adoc
@@ -1,4 +1,4 @@
-# PGP DataFormat
+## PGP DataFormat
The PGP link:data-format.html[Data Format] integrates the Java
Cryptographic Extension into Camel, allowing simple and flexible
@@ -8,9 +8,7 @@ encryption to cyphertext and unmarshalling to mean decryption back to
the original plaintext. This data format implements only symmetric
(shared-key) encryption and decyption.
-[[Crypto-PGPDataFormatOptions]]
-PGPDataFormat Options
-^^^^^^^^^^^^^^^^^^^^^
+### PGPDataFormat Options
// dataformat options: START
The PGP dataformat supports 15 options which are listed below.
@@ -40,9 +38,7 @@ The PGP dataformat supports 15 options which are listed below.
{% endraw %}
// dataformat options: END
-[[Crypto-PGPDataFormatMessageHeaders]]
-PGPDataFormat Message Headers
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### PGPDataFormat Message Headers
You can override the PGPDataFormat options by applying below headers
into message dynamically.
@@ -97,9 +93,7 @@ symmectric key, set by PGPDataFormat during encryptiion process
signatures, set by PGPDataFormat during signing process
|=======================================================================
-[[Crypto-EncryptingwithPGPDataFormat]]
-Encrypting with PGPDataFormat
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Encrypting with PGPDataFormat
The following sample uses the popular PGP format for
encrypting/decrypting files using the
@@ -111,9 +105,7 @@ encryption, but you can obviously use different keys:
Or using Spring:
-[[Crypto-Toworkwiththepreviousexampleyouneedthefollowing]]
-To work with the previous example you need the following
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### To work with the previous example you need the following
* A public keyring file which contains the public keys used to encrypt
the data
@@ -121,9 +113,7 @@ the data
data
* The keyring password
-[[Crypto-Managingyourkeyring]]
-Managing your keyring
-+++++++++++++++++++++
+#### Managing your keyring
To manage the keyring, I use the command line tools, I find this to be
the simplest approach in managing the keys. There are also Java
@@ -160,8 +150,7 @@ ls -l ~/.gnupg/pubring.gpg ~/.gnupg/secring.gpg
[[Crypto-PGPDecrypting/VerifyingofMessagesEncrypted/SignedbyDifferentPrivate/PublicKeys]]
PGP Decrypting/Verifying of Messages Encrypted/Signed by Different
-Private/Public Keys
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Private/Public Keys
Since *Camel 2.12.2*.
@@ -206,9 +195,7 @@ same mechanism is also used to locate the public key for verifying a
signature. Therefore you no longer must specify User IDs for the
unmarshaling.
-[[Crypto-RestrictingtheSignerIdentitiesduringPGPSignatureVerification]]
-Restricting the Signer Identities during PGP Signature Verification
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Restricting the Signer Identities during PGP Signature Verification
Since�*Camel 2.12.3.*
@@ -245,9 +232,7 @@ successful as soon as one signature can be verified.
then do not specify the signature key User IDs. In this case all public
keys in the public keyring are taken into account.
-[[Crypto-SeveralSignaturesinOnePGPDataFormat]]
-Several Signatures in One PGP Data Format
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Several Signatures in One PGP Data Format
Since�*Camel 2.12.3.*
@@ -277,9 +262,7 @@ from("direct:start")
...
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[Crypto-SupportofSub-KeysandKeyFlagsinPGPDataFormatMarshaler]]
-Support of Sub-Keys and Key Flags in PGP Data Format Marshaler
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Support of Sub-Keys and Key Flags in PGP Data Format Marshaler
Since�*Camel 2.12.3. +
*An https://tools.ietf.org/html/rfc4880#section-12.1[OpenPGP V4 key] can
@@ -294,9 +277,7 @@ these Key Flags of the primary key and sub-keys in order to determine
the right key for signing and encryption. This is necessary because the
primary key and its sub-keys have the same User IDs.
-[[Crypto-SupportofCustomKeyAccessors]]
-Support of Custom Key Accessors
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Support of Custom Key Accessors
Since *Camel 2.13.0. +
*You can implement custom key accessors for encryption/signing. The
@@ -320,9 +301,7 @@ PGPKeyAccessDataFormat has the same options as PGPDataFormat except
password, keyFileName, encryptionKeyRing, signaturePassword,
signatureKeyFileName, and signatureKeyRing.
-[[Crypto-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use the PGP dataformat in your camel routes you
need to add the following dependency to your pom.
@@ -337,11 +316,8 @@ need to add the following dependency to your pom.
</dependency>
----------------------------------------------------------
-[[Crypto-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:data-format.html[Data Format]
* link:crypto-digital-signatures.html[Crypto (Digital Signatures)]
-* http://www.bouncycastle.org/java.html[http://www.bouncycastle.org/java.html]
-
+* http://www.bouncycastle.org/java.html[http://www.bouncycastle.org/java.html]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-csv/src/main/docs/csv-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-csv/src/main/docs/csv-dataformat.adoc b/components/camel-csv/src/main/docs/csv-dataformat.adoc
index 34b71d3..c909525 100644
--- a/components/camel-csv/src/main/docs/csv-dataformat.adoc
+++ b/components/camel-csv/src/main/docs/csv-dataformat.adoc
@@ -1,4 +1,4 @@
-# CSV DataFormat
+## CSV DataFormat
The CSV link:data-format.html[Data Format] uses
http://commons.apache.org/proper/commons-csv/[Apache Commons CSV] to
@@ -6,9 +6,7 @@ handle CSV payloads (Comma Separated Values) such as those
exported/imported by Excel.
-[[CSV-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The CSV dataformat supports 24 options which are listed below.
@@ -49,9 +47,7 @@ The CSV dataformat supports 24 options which are listed below.
-[[CSV-MarshallingaMaptoCSV]]
-Marshalling a Map to CSV
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Marshalling a Map to CSV
The component allows you to marshal a Java Map (or any other message
type that can be link:type-converter.html[converted] in a Map) into a
@@ -95,9 +91,7 @@ then it will produce
abc,123
-------------------------------------------------------
-[[CSV-UnmarshallingaCSVmessageintoaJavaList]]
-Unmarshalling a CSV message into a Java List
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Unmarshalling a CSV message into a Java List
Unmarshalling will transform a CSV messsage into a Java List with CSV
file lines (containing another List with all the field values).
@@ -133,9 +127,7 @@ for (List<String> line : data) {
}
--------------------------------------------------------------------------------------------------------------
-[[CSV-MarshallingaList<Map>toCSV]]
-Marshalling a List<Map> to CSV
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Marshalling a List<Map> to CSV
*Available as of Camel 2.1*
@@ -144,9 +136,7 @@ format you can now store the message payload as a
`List<Map<String, Object>>` object where the list contains a Map for
each row.
-[[CSV-FilePollerofCSV,thenunmarshaling]]
-File Poller of CSV, then unmarshaling
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### File Poller of CSV, then unmarshaling
Given a bean which can handle the incoming data...
@@ -173,9 +163,7 @@ public void doHandleCsvData(List<List<String>> csvData)
</route>
------------------------------------------------------------------------------------------------
-[[CSV-Marshalingwithapipeasdelimiter]]
-Marshaling with a pipe as delimiter
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Marshaling with a pipe as delimiter
Considering the following body
[source,java]
@@ -224,8 +212,7 @@ abc|123
[[CSV-UsingautogenColumns,configRefandstrategyRefattributesinsideXMLDSL]]
Using autogenColumns, configRef and strategyRef attributes inside XML
-DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### DSL
*Available as of Camel 2.9.2 / 2.10 and deleted for Camel 2.15*
@@ -264,9 +251,7 @@ should illustrate this customization.
</bean>
-----------------------------------------------------------------------------------------------------------------------------
-[[CSV-UsingskipFirstLineoptionwhileunmarshaling]]
-Using skipFirstLine option while unmarshaling
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using skipFirstLine option while unmarshaling
*Available as of Camel 2.10 and deleted for Camel 2.15*
@@ -296,9 +281,7 @@ from("direct:start")
.to("bean:myCsvHandler?method=doHandleCsv");
--------------------------------------------
-[[CSV-Unmarshalingwithapipeasdelimiter]]
-Unmarshaling with a pipe as delimiter
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Unmarshaling with a pipe as delimiter
Using the Spring/XML DSL:
@@ -361,9 +344,7 @@ csvConfig.setDelimiter(';');
doesn't work. You have to set the delimiter as a String!
-[[CSV-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use CSV in your Camel routes you need to add a dependency on
*camel-csv*, which implements this data format.
@@ -379,4 +360,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-csv</artifactId>
<version>x.x.x</version>
</dependency>
--------------------------------------
+-------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-cxf/src/main/docs/cxf-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-cxf/src/main/docs/cxf-component.adoc b/components/camel-cxf/src/main/docs/cxf-component.adoc
index ce2f27e..fc32eb8 100644
--- a/components/camel-cxf/src/main/docs/cxf-component.adoc
+++ b/components/camel-cxf/src/main/docs/cxf-component.adoc
@@ -1,4 +1,4 @@
-# CXF Component
+## CXF Component
NOTE:When using CXF as a consumer, the link:cxf-bean-component.html[CXF Bean
Component] allows you to factor out how message payloads are received
@@ -87,9 +87,7 @@ If you want to learn about CXF dependencies you can checkout the
====
-[[CXF-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------
@@ -115,9 +113,7 @@ For either style above, you can append options to the URI as follows:
cxf:bean:cxfEndpoint?wsdlURL=wsdl/hello_world.wsdl&dataFormat=PAYLOAD
---------------------------------------------------------------------
-[[CXF-Options]]
-Options
-^^^^^^^
+### Options
@@ -193,9 +189,7 @@ http://en.wikipedia.org/wiki/QName[QNames], so if you provide them be
sure to prefix them with their \{namespace} as shown in the examples
above.
-[[CXF-Thedescriptionsofthedataformats]]
-The descriptions of the dataformats
-+++++++++++++++++++++++++++++++++++
+#### The descriptions of the dataformats
[width="100%",cols="50%,50%",options="header",]
|=======================================================================
@@ -253,9 +247,7 @@ following is an example.
</cxf:cxfEndpoint>
-------------------------------------------------------------------------------------------------------
-[[CXF-DescriptionofrelayHeadersoption]]
-Description of relayHeaders option
-++++++++++++++++++++++++++++++++++
+#### Description of relayHeaders option
There are _in-band_ and _out-of-band_ on-the-wire headers from the
perspective of a JAXWS WSDL-first developer.
@@ -398,9 +390,7 @@ value is `false`, it will throw an exception
_Default_: `false`
|=======================================================================
-[[CXF-ConfiguretheCXFendpointswithSpring]]
-Configure the CXF endpoints with Spring
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configure the CXF endpoints with Spring
You can configure the CXF endpoint with the Spring configuration file
shown below, and you can also embed the endpoint into the `camelContext`
@@ -531,9 +521,7 @@ and setDefaultBus properties from spring configuration file.
</cxf:cxfEndpoint>
-------------------------------------------------------------------------
-[[CXF-ConfiguringtheCXFEndpointswithApacheAriesBlueprint.]]
-Configuring the CXF Endpoints with Apache Aries Blueprint.
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring the CXF Endpoints with Apache Aries Blueprint.
Since camel 2.8 there is support for utilizing aries blueprint
dependency injection for your CXF endpoints.
@@ -609,9 +597,7 @@ You can also use the bean references just as in spring
</blueprint>
----------------------------------------------------------------------------------------------------------------
-[[CXF-Howtomakethecamel-cxfcomponentuselog4jinsteadofjava.util.logging]]
-How to make the camel-cxf component use log4j instead of java.util.logging
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to make the camel-cxf component use log4j instead of java.util.logging
CXF's default logger is `java.util.logging`. If you want to change it to
log4j, proceed as follows. Create a file, in the classpath, named
@@ -620,9 +606,7 @@ fully-qualified name of the class,
`org.apache.cxf.common.logging.Log4jLogger`, with no comments, on a
single line.
-[[CXF-Howtoletcamel-cxfresponsemessagewithxmlstartdocument]]
-How to let camel-cxf response message with xml start document
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to let camel-cxf response message with xml start document
If you are using some SOAP client such as PHP, you will get this kind of
error, because CXF doesn't add the XML start document "<?xml
@@ -650,9 +634,7 @@ Or adding a message header for it like this if you are using *Camel
exchange.getOut().setHeader(Client.RESPONSE_CONTEXT, map);
-------------------------------------------------------------------
-[[CXF-HowtooverridetheCXFproduceraddressfrommessageheader]]
-How to override the CXF producer address from message header
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to override the CXF producer address from message header
The�`camel-cxf`�producer supports to override the services address by
setting the message with the key of "CamelDestinationOverrideUrl".
@@ -663,9 +645,7 @@ setting the message with the key of "CamelDestinationOverrideUrl".
exchange.getIn().setHeader(Exchange.DESTINATION_OVERRIDE_URL, constant(getServiceAddress()));
----------------------------------------------------------------------------------------------
-[[CXF-Howtoconsumeamessagefromacamel-cxfendpointinPOJOdataformat]]
-How to consume a message from a camel-cxf endpoint in POJO data format
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to consume a message from a camel-cxf endpoint in POJO data format
The `camel-cxf` endpoint consumer POJO data format is based on the
http://cwiki.apache.org/CXF20DOC/invokers.html[cxf invoker], so the
@@ -673,9 +653,7 @@ message header has a property with the name of
`CxfConstants.OPERATION_NAME` and the message body is a list of the SEI
method parameters.
-[[CXF-Howtopreparethemessageforthecamel-cxfendpointinPOJOdataformat]]
-How to prepare the message for the camel-cxf endpoint in POJO data format
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to prepare the message for the camel-cxf endpoint in POJO data format
The `camel-cxf` endpoint producer is based on the
https://svn.apache.org/repos/asf/cxf/trunk/api/src/main/java/org/apache/cxf/endpoint/Client.java[cxf
@@ -693,9 +671,7 @@ list.
If you want to get the object array from the message body, you can get
the body using `message.getbody(Object[].class)`, as follows:
-[[CXF-Howtodealwiththemessageforacamel-cxfendpointinPAYLOADdataformat]]
-How to deal with the message for a camel-cxf endpoint in PAYLOAD data format
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to deal with the message for a camel-cxf endpoint in PAYLOAD data format
`PAYLOAD` means that you process the payload message from the SOAP
envelope. You can use the `Header.HEADER_LIST` as the key to set or get
@@ -706,9 +682,7 @@ elements.
for SOAP message headers and Body elements. This change enables
decoupling the native CXF message from the Camel message.
-[[CXF-HowtogetandsetSOAPheadersinPOJOmode]]
-How to get and set SOAP headers in POJO mode
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get and set SOAP headers in POJO mode
`POJO` means that the data format is a "list of Java objects" when the
Camel-cxf endpoint produces or consumes Camel exchanges. Even though
@@ -737,9 +711,7 @@ InsertResponseOutHeaderProcessor and InsertRequestOutHeaderProcessor are
actually the same. The only difference between the two processors is
setting the direction of the inserted SOAP header.
-[[CXF-HowtogetandsetSOAPheadersinPAYLOADmode]]
-How to get and set SOAP headers in PAYLOAD mode
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get and set SOAP headers in PAYLOAD mode
We've already shown how to access SOAP message (CxfPayload object) in
PAYLOAD mode (See "How to deal with the message for a camel-cxf endpoint
@@ -760,16 +732,12 @@ forwarded to the CXF service. If you do not want that these headers are
forwarded you have to remove them in the Camel header
"org.apache.cxf.headers.Header.list".
-[[CXF-SOAPheadersarenotavailableinMESSAGEmode]]
-SOAP headers are not available in MESSAGE mode
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### SOAP headers are not available in MESSAGE mode
SOAP headers are not available in MESSAGE mode as SOAP processing is
skipped.
-[[CXF-HowtothrowaSOAPFaultfromCamel]]
-How to throw a SOAP Fault from Camel
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to throw a SOAP Fault from Camel
If you are using a `camel-cxf` endpoint to consume the SOAP request, you
may need to throw the SOAP Fault from the camel context. +
@@ -786,9 +754,7 @@ code in the message header.
Same for using POJO data format. You can set the SOAPFault on the out
body and also indicate it's a fault by calling Message.setFault(true):
-[[CXF-Howtopropagateacamel-cxfendpointrequestandresponsecontext]]
-How to propagate a camel-cxf endpoint's request and response context
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to propagate a camel-cxf endpoint's request and response context
https://svn.apache.org/repos/asf/cxf/trunk/api/src/main/java/org/apache/cxf/endpoint/Client.java[cxf
client API] provides a way to invoke the operation with request and
@@ -821,9 +787,7 @@ response context with the following code:
responseContext.get("javax.xml.ws.wsdl.operation").toString());
-------------------------------------------------------------------------------------------------------------
-[[CXF-AttachmentSupport]]
-Attachment Support
-^^^^^^^^^^^^^^^^^^
+### Attachment Support
*POJO Mode:* Both SOAP with Attachment and MTOM are supported (see
example in Payload Mode for enabling MTOM).� However, SOAP with
@@ -864,9 +828,7 @@ you require just the SOAP XML as a String, you can set the message body
with message.getSOAPPart(), and Camel convert can do the rest of work
for you.
-[[CXF-StreamingSupportinPAYLOADmode]]
-Streaming Support in PAYLOAD mode
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Streaming Support in PAYLOAD mode
In 2.8.2, the camel-cxf component now supports streaming of incoming
messages when using PAYLOAD mode. Previously, the incoming messages
@@ -898,9 +860,7 @@ Global system property: you can add a system property of
That sets the global default, but setting the endpoint property above
will override this value for that endpoint.
-[[CXF-UsingthegenericCXFDispatchmode]]
-Using the generic CXF Dispatch mode
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the generic CXF Dispatch mode
From 2.8.0, the camel-cxf component supports the generic
https://cxf.apache.org/docs/jax-ws-dispatch-api.html[CXF dispatch
@@ -924,12 +884,9 @@ the key SOAPAction (case-insensitive).
�
-[[CXF-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
[06/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mail/src/main/docs/mail-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mail/src/main/docs/mail-component.adoc b/components/camel-mail/src/main/docs/mail-component.adoc
index 177051c..c1a3199 100644
--- a/components/camel-mail/src/main/docs/mail-component.adoc
+++ b/components/camel-mail/src/main/docs/mail-component.adoc
@@ -1,4 +1,4 @@
-# Mail Component
+## Mail Component
The mail component provides access to Email via Spring's Mail support
and the underlying JavaMail system.
@@ -44,9 +44,7 @@ environments where you need to send mails to a real mail server. Just
the presence of the mock-javamail.jar on the classpath means that it
will kick in and avoid sending the mails.
-[[Mail-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
Mail endpoints can have one of the following URI formats (for the
protocols, SMTP, POP3, or IMAP, respectively):
@@ -73,8 +71,7 @@ You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Mail-Component-Options]]
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[Mail-Component-Options]]
// component options: START
@@ -94,8 +91,7 @@ The Mail component supports 2 options which are listed below.
-[[Mail-Endpoint-Options]]
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[Mail-Endpoint-Options]]
// endpoint options: START
@@ -175,9 +171,7 @@ The Mail component supports 63 endpoint options which are listed below:
-[[Mail-Sampleendpoints]]
-Sample endpoints
-++++++++++++++++
+#### Sample endpoints
Typically, you specify a URI with login credentials as follows (taking
SMTP as an example):
@@ -202,9 +196,7 @@ For example:
smtp://mycompany.mailserver:30?password=tiger&username=scott
------------------------------------------------------------
-[[Mail-Components]]
-Components
-^^^^^^^^^^
+### Components
- link:imap.html[IMAP]
- link:imaps.html[IMAPs]
@@ -213,9 +205,7 @@ Components
- link:smtp.html[STMP]
- link:smtps.html[SMTPs]
-[[Mail-DefaultPortsDefaultports]]
-Default ports
-+++++++++++++
+#### Default ports
Default port numbers are supported. If the port number is omitted, Camel
determines the port number to use based on the protocol.
@@ -231,9 +221,7 @@ determines the port number to use based on the protocol.
|`IMAPS` |`993`
|=======================================================================
-[[Mail-SSLsupport]]
-SSL support
-^^^^^^^^^^^
+### SSL support
The underlying mail framework is responsible for providing SSL support.
�You may either configure SSL/TLS support by completely specifying the
@@ -241,9 +229,7 @@ necessary Java Mail API configuration options, or you may provide a
configured SSLContextParameters through the component or endpoint
configuration.
-[[Mail-UsingtheJSSEConfigurationUtility]]
-Using the JSSE Configuration Utility
-++++++++++++++++++++++++++++++++++++
+#### Using the JSSE Configuration Utility
As of *Camel 2.10*, the mail component supports SSL/TLS configuration
through the link:camel-configuration-utilities.html[Camel JSSE
@@ -286,9 +272,7 @@ Spring DSL based configuration of endpoint
<to uri="smtps://smtp.google.com?username=user@gmail.com&password=password&sslContextParameters=#sslContextParameters"/>...
---------------------------------------------------------------------------------------------------------------------------
-[[Mail-ConfiguringJavaMailDirectly]]
-Configuring JavaMail Directly
-+++++++++++++++++++++++++++++
+#### Configuring JavaMail Directly
Camel uses SUN JavaMail, which only trusts certificates issued by well
known Certificate Authorities (the default JVM trust configuration). If
@@ -296,9 +280,7 @@ you issue your own certificates, you have to import the CA certificates
into the JVM's Java trust/key store files, override the default JVM
trust/key store files (see `SSLNOTES.txt` in JavaMail for details).
-[[Mail-MailMessageContent]]
-Mail Message Content
-^^^^^^^^^^^^^^^^^^^^
+### Mail Message Content
Camel uses the message exchange's IN body as the
http://java.sun.com/javaee/5/docs/api/javax/mail/internet/MimeMessage.html[MimeMessage]
@@ -321,9 +303,7 @@ server, you should be able to get the message id of the
http://java.sun.com/javaee/5/docs/api/javax/mail/internet/MimeMessage.html[MimeMessage]
with the key `CamelMailMessageId` from the Camel message header.
-[[Mail-Headerstakeprecedenceoverpre-configuredrecipients]]
-Headers take precedence over pre-configured recipients
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Headers take precedence over pre-configured recipients
The recipients specified in the message headers always take precedence
over recipients pre-configured in the endpoint URI. The idea is that if
@@ -349,9 +329,7 @@ pre-configured settings.
template.sendBodyAndHeaders("smtp://admin@localhost?to=info@mycompany.com", "Hello World", headers);
------------------------------------------------------------------------------------------------------------
-[[Mail-Multiplerecipientsforeasierconfiguration]]
-Multiple recipients for easier configuration
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Multiple recipients for easier configuration
It is possible to set multiple recipients using a comma-separated or a
semicolon-separated list. This applies both to header settings and to
@@ -365,9 +343,7 @@ settings in an endpoint URI. For example:
The preceding example uses a semicolon, `;`, as the separator character.
-[[Mail-Settingsendernameandemail]]
-Setting sender name and email
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting sender name and email
You can specify recipients in the format, `name <email>`, to include
both the name and the email address of the recipient.
@@ -383,9 +359,7 @@ map.put("From", "James Strachan <js...@apache.org>");
map.put("Subject", "Camel is cool");
---------------------------------------------------------
-[[Mail-JavaMailAPI(exSUNJavaMail)]]
-JavaMail API (ex SUN JavaMail)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### JavaMail API (ex SUN JavaMail)
https://java.net/projects/javamail/pages/Home[JavaMail API] is used
under the hood for consuming and producing mails. +
@@ -401,9 +375,7 @@ IMAP API]
https://javamail.java.net/nonav/docs/api/javax/mail/Flags.html[MAIL
Flags]
-[[Mail-Samples]]
-Samples
-^^^^^^^
+### Samples
We start with a simple route that sends the messages received from a JMS
queue as emails. The email account is the `admin` account on
@@ -427,9 +399,7 @@ from("imap://admin@mymailserver.com
In this sample we want to send a mail to multiple recipients:
-[[Mail-Sendingmailwithattachmentsample]]
-Sending mail with attachment sample
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending mail with attachment sample
WARNING: *Attachments are not support by all Camel components*
@@ -445,9 +415,7 @@ The mail component supports attachments. In the sample below, we send a
mail message containing a plain text message with a logo file
attachment.
-[[Mail-SSLsample]]
-SSL sample
-^^^^^^^^^^
+### SSL sample
In this sample, we want to poll our Google mail inbox for mails. To
download mail onto a local mail client, Google mail requires you to
@@ -476,9 +444,7 @@ progress in the logs:
2008-05-08 06:32:12,187 INFO newmail - Exchange[MailMessage: messageNumber=[332], from=[James Bond <00...@mi5.co.uk>], to=YOUR_USERNAME@gmail.com], subject=[...
------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[Mail-Consumingmailswithattachmentsample]]
-Consuming mails with attachment sample
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Consuming mails with attachment sample
In this sample we poll a mailbox and store all attachments from the
mails as files. First, we define a route to poll the mailbox. As this
@@ -523,9 +489,7 @@ As you can see the API to handle attachments is a bit clunky but it's
there so you can get the `javax.activation.DataHandler` so you can
handle the attachments using standard API.
-[[Mail-Howtosplitamailmessagewithattachments]]
-How to split a mail message with attachments
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to split a mail message with attachments
In this example we consume mail messages which may have a number of
attachments. What we want to do is to use the
@@ -570,9 +534,7 @@ SplitAttachmentsExpression split = SplitAttachmentsExpression(true);
And then use the expression with the splitter eip.
-[[Mail-UsingcustomSearchTerm]]
-Using custom SearchTerm
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using custom SearchTerm
*Available as of Camel 2.11*
@@ -660,12 +622,9 @@ builder.unseen().body(Op.not, "Spam").subject(Op.not, "Spam")
SearchTerm term = builder.build();
--------------------------------------------------------------
-[[Mail-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-mail/src/main/docs/mime-multipart-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mail/src/main/docs/mime-multipart-dataformat.adoc b/components/camel-mail/src/main/docs/mime-multipart-dataformat.adoc
index 80c6498..52f3675 100644
--- a/components/camel-mail/src/main/docs/mime-multipart-dataformat.adoc
+++ b/components/camel-mail/src/main/docs/mime-multipart-dataformat.adoc
@@ -1,4 +1,4 @@
-# MIME Multipart DataFormat
+## MIME Multipart DataFormat
*Available as of Camel 2.17*
@@ -40,9 +40,7 @@ empty message. Up to Camel version 2.17.1 this will happen all message
bodies that do not contain a MIME multipart message regardless of body
type and stream cache setting.
-[[MIME-Multipart-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The MIME Multipart dataformat supports 6 options which are listed below.
@@ -63,9 +61,7 @@ The MIME Multipart dataformat supports 6 options which are listed below.
{% endraw %}
// dataformat options: END
-[[MIME-Multipart-MessageHeadersmarshal]]
-Message Headers (marshal)
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Message Headers (marshal)
[width="100%",cols="20%,20%,60%",options="header",]
|=======================================================================
@@ -89,9 +85,7 @@ body part. Furthermore the given charset is applied for text to binary
conversions.
|=======================================================================
-[[MIME-Multipart-MessageHeadersunmarshal]]
-Message Headers (unmarshal)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Message Headers (unmarshal)
[width="100%",cols="20%,20%,60%",options="header",]
|=======================================================================
@@ -111,9 +105,7 @@ from MIME endoding descriptor to Java encoding descriptor)
MIME multipart. The header is removed afterwards
|=======================================================================
-[[MIME-Multipart-Examples]]
-Examples
-^^^^^^^^
+### Examples
[source,java]
-----------------------------------
@@ -191,9 +183,7 @@ Content-Disposition: attachment; filename="Attachment File Name"
------=_Part_0_1134128170.1447659361365
----------------------------------------------------------------
-[[MIME-Multipart-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use MIME-Multipart in your Camel routes you need to add a dependency
on *camel-mail* which implements this data format.
@@ -207,4 +197,4 @@ If you use Maven you can just add the following to your pom.xml:
<artifactId>camel-mail</artifactId>
<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-metrics/src/main/docs/metrics-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-metrics/src/main/docs/metrics-component.adoc b/components/camel-metrics/src/main/docs/metrics-component.adoc
index cec5e5f..1e14bbc 100644
--- a/components/camel-metrics/src/main/docs/metrics-component.adoc
+++ b/components/camel-metrics/src/main/docs/metrics-component.adoc
@@ -1,4 +1,4 @@
-# Metrics Component
+## Metrics Component
ifdef::env-github[]
:caution-caption: :boom:
:important-caption: :exclamation:
@@ -7,9 +7,7 @@ ifdef::env-github[]
:warning-caption: :warning:
endif::[]
-[[MetricsComponent-MetricsComponent]]
-Metrics Component
-~~~~~~~~~~~~~~~~~
+### Metrics Component
*Available as of Camel 2.14*
@@ -36,18 +34,14 @@ for this component:
</dependency>
----
-[[MetricsComponent-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source]
----
metrics:[ meter | counter | histogram | timer | gauge ]:metricname[?options]
----
-[[MetricsComponent-options]]
-Options
-^^^^^^^
+### Options
// component options: START
The Metrics component supports 1 options which are listed below.
@@ -86,9 +80,7 @@ The Metrics component supports 9 endpoint options which are listed below:
-[[MetricsComponent-registryMetricRegistry]]
-[[MetricsComponent-registry]]Metric Registry
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[MetricsComponent-registry]]Metric Registry
Camel Metrics component uses by default a `MetricRegistry` instance with
a `Slf4jReporter` that has a 60 second reporting interval.
@@ -150,9 +142,7 @@ public API in version DropWizard `3.0.1` for users to clean up on exit. Thus usi
Camel Metrics Component leads to Java classloader leak and my cause
`OutOfMemoryErrors` in some cases.
-[[MetricsComponent-Usage]]
-Usage
-^^^^^
+### Usage
Each metric has type and name. Supported types are
link:#MetricsComponent-counter[counter],
@@ -160,9 +150,7 @@ link:#MetricsComponent-histogram[histogram],�link:#MetricsComponent-meter[meter
link:#MetricsComponent-timer[timer] and link:#MetricsComponent-gauge[gauge].
Metric name is simple string. If metric type is not provided then type meter is used by default.
-[[MetricsComponent-Headers]]
-Headers
-+++++++
+#### Headers
Metric name defined in URI can be overridden by using header with name
`CamelMetricsName`.
@@ -184,18 +172,14 @@ endpoint finishes processing of exchange. While processing exchange
Metrics endpoint will catch all exceptions and write log entry using
level `warn`.
-[[MetricsComponent-counterMetricstypecounter]]
-[[MetricsComponent-counter]]Metrics type counter
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[MetricsComponent-counter]]Metrics type counter
[source]
----
metrics:counter:metricname[?options]
----
-[[MetricsComponent-Options]]
-Options
-+++++++
+#### Options
[width="100%",cols="10%,10%,80%",options="header",]
|=====================================================
@@ -232,9 +216,7 @@ from("direct:in")
.to("direct:out");
----
-[[MetricsComponent-Headers.1]]
-Headers
-+++++++
+#### Headers
Message headers can be used to override `increment` and `decrement`
values specified in Metrics component URI.
@@ -265,18 +247,14 @@ from("direct:in")
----
-[[MetricsComponent-histogramMetrictypehistogram]]
-[[MetricsComponent-histogram]]Metric type histogram
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[MetricsComponent-histogram]]Metric type histogram
[source]
----
metrics:histogram:metricname[?options]
----
-[[MetricsComponent-Options.1]]
-Options
-+++++++
+#### Options
[width="100%",cols="10%,10%,80%",options="header",]
|===================================
@@ -304,9 +282,7 @@ from("direct:in")
----
-[[MetricsComponent-Headers.2]]
-Headers
-+++++++
+#### Headers
Message header can be used to override value specified in Metrics
component URI.
@@ -327,18 +303,14 @@ from("direct:in")
----
-[[MetricsComponent-meterMetrictypemeter]]
-[[MetricsComponent-meter]]Metric type meter
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[MetricsComponent-meter]]Metric type meter
[source]
----
metrics:meter:metricname[?options]
----
-[[MetricsComponent-Options.2]]
-Options
-+++++++
+#### Options
[width="100%",cols="10%,10%,80%",options="header",]
|===================================
@@ -364,9 +336,7 @@ from("direct:in")
.to("direct:out");
----
-[[MetricsComponent-Headers.3]]
-Headers
-+++++++
+#### Headers
Message header can be used to override `mark` value specified in Metrics
component URI.
@@ -386,18 +356,14 @@ from("direct:in")
.to("direct:out");
----
-[[MetricsComponent-timerMetricstypetimer]]
-[[MetricsComponent-timer]]Metrics type timer
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[MetricsComponent-timer]]Metrics type timer
[source]
----
metrics:timer:metricname[?options]
----
-[[MetricsComponent-Options.3]]
-Options
-+++++++
+#### Options
[width="100%",cols="10%,10%,80%",options="header",]
|==========================
@@ -422,9 +388,7 @@ from("direct:in")
`TimerContext` objects are stored as Exchange properties between
different Metrics component calls.
-[[MetricsComponent-Headers.4]]
-Headers
-+++++++
+#### Headers
Message header can be used to override action value specified in Metrics
component URI.
@@ -445,18 +409,14 @@ from("direct:in")
.to("direct:out");
----
-[[MetricsComponent-gaugeMetrictypegauge]]
-[[MetricsComponent-gauge]]Metric type gauge
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[MetricsComponent-gauge]]Metric type gauge
[source]
----
metrics:gauge:metricname[?options]
----
-[[MetricsComponent-Options.4]]
-Options
-+++++++
+#### Options
[width="100%",cols="10%,10%,80%",options="header",]
|=====================================================
@@ -474,9 +434,7 @@ from("direct:in")
.to("direct:out");
----
-[[MetricsComponent-Headers.5]]
-Headers
-+++++++
+#### Headers
Message headers can be used to override `subject` values specified in Metrics component URI.
Note: if `CamelMetricsName` header is specified, then new gauge is registered in addition to
@@ -497,9 +455,7 @@ from("direct:in")
.to("direct:out");
----
-[[MetricsComponent-MetricsRoutePolicyFactory]]
-MetricsRoutePolicyFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### MetricsRoutePolicyFactory
This factory allows to add a�link:routepolicy.html[RoutePolicy] for each
route which exposes route utilization statistics using Dropwizard metrics.
@@ -577,9 +533,7 @@ if (registryService != null) {
}
----
-[[MetricsComponent-MetricsMessageHistoryFactory]]
-MetricsMessageHistoryFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### MetricsMessageHistoryFactory
*Available as of Camel 2.17*
@@ -655,9 +609,7 @@ String json = service.dumpStatisticsAsJson();
And the JMX API the MBean is registered in the�`type=services` tree
with�`name=MetricsMessageHistoryService`.
-[[MetricsComponent-InstrumentedThreadPoolFactory]]
-InstrumentedThreadPoolFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### InstrumentedThreadPoolFactory
*Available as of Camel 2.18*
@@ -666,9 +618,7 @@ which collects information from inside of Camel.
See more details at link:advanced-configuration-of-camelcontext-using-spring.html[Advanced configuration of CamelContext using Spring]
-[[MetricsComponent-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* The `camel-example-cdi-metrics` example that illustrates the integration
- between Camel, Metrics and CDI.
+ between Camel, Metrics and CDI.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mina/src/main/docs/mina-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mina/src/main/docs/mina-component.adoc b/components/camel-mina/src/main/docs/mina-component.adoc
index 47e641b..05c3854 100644
--- a/components/camel-mina/src/main/docs/mina-component.adoc
+++ b/components/camel-mina/src/main/docs/mina-component.adoc
@@ -1,4 +1,4 @@
-# Mina Component
+## Mina Component
*Deprecated*
@@ -21,9 +21,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[MINA-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------------
@@ -57,9 +55,7 @@ exchange itself over the wire. See options below.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[MINA-Options]]
-Options
-^^^^^^^
+### Options
@@ -124,9 +120,7 @@ The Mina component supports 24 endpoint options which are listed below:
-[[MINA-Usingacustomcodec]]
-Using a custom codec
-^^^^^^^^^^^^^^^^^^^^
+### Using a custom codec
See the http://mina.apache.org/tutorial-on-protocolcodecfilter.html[Mina
documentation] how to write your own codec. To use your custom codec
@@ -135,9 +129,7 @@ link:registry.html[Registry]; for example, by creating a bean in the
Spring XML file. Then use the `codec` option to specify the bean ID of
your codec. See link:hl7.html[HL7] that has a custom codec.
-[[MINA-Samplewithsync=false]]
-Sample with sync=false
-^^^^^^^^^^^^^^^^^^^^^^
+### Sample with sync=false
In this sample, Camel exposes a service that listens for TCP connections
on port 6200. We use the *textline* codec. In our route, we create a
@@ -146,9 +138,7 @@ Mina consumer endpoint that listens on port 6200:
As the sample is part of a unit test, we test it by sending some data to
it on port 6200.
-[[MINA-Samplewithsync=true]]
-Sample with sync=true
-^^^^^^^^^^^^^^^^^^^^^
+### Sample with sync=true
In the next sample, we have a more common use case where we expose a TCP
service on port 6201 also use the textline codec. However, this time we
@@ -160,9 +150,7 @@ using the `template.requestBody()` method. As we know the response is a
`String`, we cast it to `String` and can assert that the response is, in
fact, something we have dynamically set in our processor code logic.
-[[MINA-SamplewithSpringDSL]]
-Sample with Spring DSL
-^^^^^^^^^^^^^^^^^^^^^^
+### Sample with Spring DSL
Spring DSL can, of course, also be used for link:mina.html[MINA]. In the
sample below we expose a TCP server on port 5555:
@@ -188,9 +176,7 @@ could be implemented as follows:
}
-----------------------------------------------
-[[MINA-ConfiguringMinaendpointsusingSpringbeanstyle]]
-Configuring Mina endpoints using Spring bean style
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring Mina endpoints using Spring bean style
Configuration of Mina endpoints is possible using regular Spring bean
style configuration in the Spring DSL.
@@ -206,9 +192,7 @@ The sample below shows the factory approach:
And then we can refer to our endpoint directly in the route, as follows:
-[[MINA-ClosingSessionWhenComplete]]
-Closing Session When Complete
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Closing Session When Complete
When acting as a server you sometimes want to close the session when,
for example, a client conversion is finished. To instruct Camel to close
@@ -229,9 +213,7 @@ written the `bye` message back to the client:
});
--------------------------------------------------------------------------------------------------
-[[MINA-GettheIoSessionformessage]]
-Get the IoSession for message
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Get the IoSession for message
*Available since Camel 2.1*
You can get the IoSession from the message header with this key
@@ -239,9 +221,7 @@ MinaEndpoint.HEADER_MINA_IOSESSION, and also get the local host address
with the key MinaEndpoint.HEADER_LOCAL_ADDRESS and remote host address
with the key MinaEndpoint.HEADER_REMOTE_ADDRESS.
-[[MINA-ConfiguringMinafilters]]
-Configuring Mina filters
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring Mina filters
Filters permit you to use some Mina Filters, such as `SslFilter`. You
can also implement some customized filters. Please note that `codec` and
@@ -334,9 +314,7 @@ Then, you can configure your endpoint using Spring DSL:
</bean>
----------------------------------------------------------------------------------
-[[MINA-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -344,5 +322,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:mina2.html[MINA2]
-* link:netty.html[Netty]
-
+* link:netty.html[Netty]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mina2/src/main/docs/mina2-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mina2/src/main/docs/mina2-component.adoc b/components/camel-mina2/src/main/docs/mina2-component.adoc
index 1975038..ab73083 100644
--- a/components/camel-mina2/src/main/docs/mina2-component.adoc
+++ b/components/camel-mina2/src/main/docs/mina2-component.adoc
@@ -1,4 +1,4 @@
-# Mina2 Component
+## Mina2 Component
*Available as of Camel 2.10*
@@ -24,9 +24,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[MINA2-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------------
@@ -58,9 +56,7 @@ exchange itself over the wire. See options below.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[MINA2-Options]]
-Options
-^^^^^^^
+### Options
@@ -130,9 +126,7 @@ The Mina2 component supports 29 endpoint options which are listed below:
-[[MINA2-Usingacustomcodec]]
-Using a custom codec
-^^^^^^^^^^^^^^^^^^^^
+### Using a custom codec
See the Mina how to write your own codec. To use your custom codec with
`camel-mina`, you should register your codec in the
@@ -140,9 +134,7 @@ link:registry.html[Registry]; for example, by creating a bean in the
Spring XML file. Then use the `codec` option to specify the bean ID of
your codec. See link:hl7.html[HL7] that has a custom codec.
-[[MINA2-Samplewithsyncfalse]]
-Sample with sync=false
-^^^^^^^^^^^^^^^^^^^^^^
+### Sample with sync=false
In this sample, Camel exposes a service that listens for TCP connections
on port 6200. We use the *textline* codec. In our route, we create a
@@ -166,9 +158,7 @@ template.sendBody("mina2:tcp://localhost:" + port1 + "?textline=true&sync=false"
assertMockEndpointsSatisfied();
-------------------------------------------------------------------------------------------------
-[[MINA2-Samplewithsynctrue]]
-Sample with sync=true
-^^^^^^^^^^^^^^^^^^^^^
+### Sample with sync=true
In the next sample, we have a more common use case where we expose a TCP
service on port 6201 also use the textline codec. However, this time we
@@ -196,9 +186,7 @@ String response = (String)template.requestBody("mina2:tcp://localhost:" + port2
assertEquals("Bye World", response);
-----------------------------------------------------------------------------------------------------------------------
-[[MINA2-SamplewithSpringDSL]]
-Sample with Spring DSL
-^^^^^^^^^^^^^^^^^^^^^^
+### Sample with Spring DSL
Spring DSL can, of course, also be used for link:mina.html[MINA]. In the
sample below we expose a TCP server on port 5555:
@@ -224,9 +212,7 @@ could be implemented as follows:
}
-----------------------------------------------
-[[MINA2-ClosingSessionWhenComplete]]
-Closing Session When Complete
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Closing Session When Complete
When acting as a server you sometimes want to close the session when,
for example, a client conversion is finished. To instruct Camel to close
@@ -247,18 +233,14 @@ written the `bye` message back to the client:
});
---------------------------------------------------------------------------------------------------
-[[MINA2-GettheIoSessionformessage]]
-Get the IoSession for message
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Get the IoSession for message
You can get the IoSession from the message header with this key
`Mina2Constants.MINA_IOSESSION`, and also get the local host address
with the key `Mina2Constants.MINA_LOCAL_ADDRESS` and remote host address
with the key `Mina2Constants.MINA_REMOTE_ADDRESS`.
-[[MINA2-ConfiguringMinafilters]]
-Configuring Mina filters
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring Mina filters
Filters permit you to use some Mina Filters, such as `SslFilter`. You
can also implement some customized filters. Please note that `codec` and
@@ -266,9 +248,7 @@ can also implement some customized filters. Please note that `codec` and
filters you may define are appended to the end of the filter chain; that
is, after `codec` and `logger`.
-[[MINA2-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:component.html[Component]
@@ -276,5 +256,4 @@ See Also
* link:getting-started.html[Getting Started]
* link:mina.html[MINA]
-* link:netty.html[Netty]
-
+* link:netty.html[Netty]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mllp/src/main/docs/mllp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mllp/src/main/docs/mllp-component.adoc b/components/camel-mllp/src/main/docs/mllp-component.adoc
index f9875bc..fe9d081 100644
--- a/components/camel-mllp/src/main/docs/mllp-component.adoc
+++ b/components/camel-mllp/src/main/docs/mllp-component.adoc
@@ -1,4 +1,4 @@
-# MLLP Component
+## MLLP Component
*available as of Camel 2.17*
@@ -35,9 +35,7 @@ for this component:
</dependency>
---------------------------------------------------------
-[[MLLP-MLLPOptions]]
-MLLP Options
-~~~~~~~~~~~~
+### MLLP Options
@@ -93,9 +91,7 @@ The MLLP component supports 24 endpoint options which are listed below:
-[[MLLP-MLLPConsumer]]
-MLLP Consumer
-~~~~~~~~~~~~~
+### MLLP Consumer
The MLLP Consumer supports receiving MLLP-framed messages and sending
HL7 Acknowledgements. �The MLLP Consumer can automatically generate the
@@ -105,9 +101,7 @@ the�CamelMllpAcknowledgement exchange property. �Additionally, the type
of acknowledgement that will be generated can be controlled by setting
the CamelMllpAcknowledgementType exchange property.
-[[MLLP-MessageHeaders]]
-*Message Headers*
-^^^^^^^^^^^^^^^^^
+### *Message Headers*
The MLLP Consumer adds these headers on the Camel message:
@@ -134,9 +128,7 @@ The MLLP Consumer adds these headers on the Camel message:
All headers�are�String�types. If a header value is missing, its value
is�null.
-[[MLLP-ExchangeProperties]]
-*Exchange Properties*
-^^^^^^^^^^^^^^^^^^^^^
+### *Exchange Properties*
The type of acknowledgment the MLLP Consumer generates can be controlled
by these properties on the Camel exchange:
@@ -151,13 +143,9 @@ by these properties on the Camel exchange:
All headers�are�String�types. If a header value is missing, its value
is�null.
-[[MLLP-ConsumerConfiguration]]
-Consumer Configuration
-^^^^^^^^^^^^^^^^^^^^^^
+### Consumer Configuration
-[[MLLP-MLLPProducer]]
-MLLP Producer
-~~~~~~~~~~~~~
+### MLLP Producer
The MLLP Producer supports sending MLLP-framed messages and receiving
HL7 Acknowledgements. �The MLLP Producer interrogates the HL7
@@ -165,9 +153,7 @@ Acknowledgments and raises exceptions if a negative acknowledgement is
received. �The received acknowledgement is interrogated and an exception
is raised in the event of a negative acknowledgement.
-[[MLLP-MessageHeaders.1]]
-*Message Headers*
-^^^^^^^^^^^^^^^^^
+### *Message Headers*
The MLLP Producer adds these headers on the Camel message:
@@ -181,7 +167,4 @@ The MLLP Producer adds these headers on the Camel message:
|===================================
All headers�are�String�types. If a header value is missing, its value
-is�null.
-
-
-
+is�null.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mongodb-gridfs/src/main/docs/gridfs-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mongodb-gridfs/src/main/docs/gridfs-component.adoc b/components/camel-mongodb-gridfs/src/main/docs/gridfs-component.adoc
index f66c8af..67525ea 100644
--- a/components/camel-mongodb-gridfs/src/main/docs/gridfs-component.adoc
+++ b/components/camel-mongodb-gridfs/src/main/docs/gridfs-component.adoc
@@ -1,4 +1,4 @@
-# MongoDBGridFS Component
+## MongoDBGridFS Component
*Available as of Camel 2.17*
@@ -15,18 +15,14 @@ for this component:
</dependency>
------------------------------------------------------------
-[[MongoDBGridFS-URIformat]]
-URI format
-~~~~~~~~~~
+### URI format
[source,java]
------------------------------------------------------------------------------
gridfs:connectionBean?database=databaseName&bucket=bucketName[&moreOptions...]
------------------------------------------------------------------------------
-[[MongoDBGridFS-options]]
-MongoDB GridFS options
-~~~~~~~~~~~~~~~~~~~~~~
+### MongoDB GridFS options
// component options: START
@@ -67,9 +63,7 @@ The MongoDBGridFS component supports 18 endpoint options which are listed below:
-[[MongoDBGridFS-ConfigurationofdatabaseinSpringXML]]
-Configuration of database in Spring XML
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Configuration of database in Spring XML
The following Spring XML creates a bean defining the connection to a
MongoDB instance.
@@ -86,9 +80,7 @@ MongoDB instance.
</beans>
----------------------------------------------------------------------------------------------------------------------------------
-[[MongoDBGridFS-Sampleroute]]
-Sample route
-^^^^^^^^^^^^
+### Sample route
The following route defined in Spring XML executes the operation
link:mongodb-gridfs.html[*findOne*] on a collection.
@@ -107,13 +99,9 @@ link:mongodb-gridfs.html[*findOne*] on a collection.
�
-[[MongoDBGridFS-GridFSoperations-producerendpoint]]
-GridFS operations - producer endpoint
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### GridFS operations - producer endpoint
-[[MongoDBGridFS-count]]
-count
-+++++
+#### count
Returns the total number of file in the collection, returning an Integer
as the OUT message body. +
@@ -136,9 +124,7 @@ headers.put(Exchange.FILE_NAME, "filename.txt");
Integer count = template.requestBodyAndHeaders("direct:count", query, headers);
-------------------------------------------------------------------------------
-[[MongoDBGridFS-listAll]]
-listAll
-+++++++
+#### listAll
Returns an Reader that lists all the filenames and their IDs in a tab
separated stream.
@@ -154,9 +140,7 @@ filename2.txt 2897651254
�
-[[MongoDBGridFS-findOne]]
-*findOne*
-+++++++++
+#### *findOne*
Finds a file in the GridFS system and sets the body to an InputStream of
the content. � Also provides the metadata has headers. �It uses
@@ -173,9 +157,7 @@ InputStream result = template.requestBodyAndHeaders("direct:findOne", "irrelevan
�
-[[MongoDBGridFS-create]]
-create
-++++++
+#### create
Creates a new file in the GridFs database. It uses the
Exchange.FILE_NAME from the incoming headers for the name and the body
@@ -190,9 +172,7 @@ InputStream stream = ... the data for the file ...
template.requestBodyAndHeaders("direct:create", stream, headers);
------------------------------------------------------------------------
-[[MongoDBGridFS-remove]]
-remove
-++++++
+#### remove
Removes a file from the GridFS database.
@@ -204,9 +184,7 @@ headers.put(Exchange.FILE_NAME, "filename.txt");
template.requestBodyAndHeaders("direct:remove", "", headers);
------------------------------------------------------------------------
-[[MongoDBGridFS-GridFSConsumer]]
-GridFS Consumer
-^^^^^^^^^^^^^^^
+### GridFS Consumer
See also
@@ -216,5 +194,4 @@ See also
current version]
*
http://svn.apache.org/viewvc/camel/trunk/components/camel-mongodb/src/test/[Unit
-tests] for more examples of usage
-
+tests] for more examples of usage
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mongodb/src/main/docs/mongodb-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mongodb/src/main/docs/mongodb-component.adoc b/components/camel-mongodb/src/main/docs/mongodb-component.adoc
index ff04df5..e3c5222 100644
--- a/components/camel-mongodb/src/main/docs/mongodb-component.adoc
+++ b/components/camel-mongodb/src/main/docs/mongodb-component.adoc
@@ -1,4 +1,4 @@
-# MongoDB Component
+## MongoDB Component
*Available as of Camel 2.10*
@@ -40,18 +40,14 @@ for this component:
</dependency>
------------------------------------------------------------
-[[MongoDB-URIformat]]
-URI format
-~~~~~~~~~~
+### URI format
[source,java]
---------------------------------------------------------------------------------------------------------------
mongodb:connectionBean?database=databaseName&collection=collectionName&operation=operationName[&moreOptions...]
---------------------------------------------------------------------------------------------------------------
-[[MongoDB-options]]
-MongoDB options
-~~~~~~~~~~~~~~~
+### MongoDB options
// component options: START
@@ -103,9 +99,7 @@ The MongoDB component supports 24 endpoint options which are listed below:
-[[MongoDB-ConfigurationofdatabaseinSpringXML]]
-Configuration of database in Spring XML
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Configuration of database in Spring XML
The following Spring XML creates a bean defining the connection to a
MongoDB instance.
@@ -123,9 +117,7 @@ MongoDB instance.
</beans>
----------------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-Sampleroute]]
-Sample route
-^^^^^^^^^^^^
+### Sample route
The following route defined in Spring XML executes the operation
link:mongodb.html[*dbStats*] on a collection.
@@ -142,17 +134,11 @@ link:mongodb.html[*dbStats*] on a collection.
</route>
---------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-MongoDBoperations-producerendpoints]]
-MongoDB operations - producer endpoints
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### MongoDB operations - producer endpoints
-[[MongoDB-Queryoperations]]
-Query operations
-^^^^^^^^^^^^^^^^
+### Query operations
-[[MongoDB-findById]]
-findById
-++++++++
+#### findById
This operation retrieves only one element from the collection whose _id
field matches the content of the IN message body. The incoming object
@@ -172,9 +158,7 @@ from("direct:findById")
TIP: *Supports optional parameters*. This operation supports specifying a fields filter. See
link:mongodb.html[Specifying optional parameters].
-[[MongoDB-findOneByQuery]]
-findOneByQuery
-++++++++++++++
+#### findOneByQuery
Use this operation to retrieve just one element from the collection that
matches a MongoDB query. *The query object is extracted from the IN
@@ -204,9 +188,7 @@ from("direct:findOneByQuery")
TIP: *Supports optional parameters*. This operation supports specifying a fields filter and/or a sort clause. See
link:mongodb.html[Specifying optional parameters].
-[[MongoDB-findAll]]
-findAll
-+++++++
+#### findAll
The `findAll` operation returns all documents matching a query, or none
at all, in which case all documents contained in the collection are
@@ -276,9 +258,7 @@ consideration. |int/Integer
TIP: *Supports optional parameters*. This operation supports specifying a fields filter and/or a sort clause. See
link:mongodb.html[Specifying optional parameters].
-[[MongoDB-count]]
-count
-+++++
+#### count
Returns the total number of objects in a collection, returning a Long as
the OUT message body. +
@@ -307,9 +287,7 @@ DBObject query = ...
Long count = template.requestBodyAndHeader("direct:count", query, MongoDbConstants.COLLECTION, "dynamicCollectionName");
------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-Specifyingoptionalparameters]]
-Specifying a fields filter (projection)
-+++++++++++++++++++++++++++++++++++++++
+#### Specifying a fields filter (projection)
Query operations will, by default, return the matching objects in their
entirety (with all their fields). If your documents are large and you
@@ -330,8 +308,7 @@ DBObject fieldFilter = BasicDBObjectBuilder.start().add("_id", 0).add("boringFie
Object result = template.requestBodyAndHeader("direct:findAll", (Object) null, MongoDbConstants.FIELDS_FILTER, fieldFilter);
----------------------------------------------------------------------------------------------------------------------------
-Specifying a sort clause
-++++++++++++++++++++++++
+#### Specifying a sort clause
There is a often a requirement to fetch the min/max record from a
collection based on sorting by a particular field. In Mongo the
@@ -364,13 +341,9 @@ to a single field, based on the `documentTimestamp` field:
----------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-Create/updateoperations]]
-Create/update operations
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Create/update operations
-[[MongoDB-insert]]
-insert
-++++++
+#### insert
Inserts an new object into the MongoDB collection, taken from the IN
message body. Type conversion is attempted to turn it into `DBObject` or
@@ -417,9 +390,7 @@ constant). The value stored is�`org.bson.types.ObjectId` for single
insert or `java.util.List<org.bson.types.ObjectId>` if multiple records
have been inserted.
-[[MongoDB-save]]
-save
-++++
+#### save
The save operation is equivalent to an _upsert_ (UPdate, inSERT)
operation, where the record will be updated, and if it doesn't exist, it
@@ -449,9 +420,7 @@ from("direct:insert")
.to("mongodb:myDb?database=flights&collection=tickets&operation=save");
---------------------------------------------------------------------------
-[[MongoDB-update]]
-update
-++++++
+#### update
Update one or multiple records on the collection. Requires a
List<DBObject> as the IN message body containing exactly 2 elements:
@@ -495,13 +464,9 @@ DBObject updateObj = new BasicDBObject("$set", new BasicDBObject("scientist", "D
Object result = template.requestBodyAndHeader("direct:update", new Object[] {filterField, updateObj}, MongoDbConstants.MULTIUPDATE, true);
------------------------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-Deleteoperations]]
-Delete operations
-^^^^^^^^^^^^^^^^^
+### Delete operations
-[[MongoDB-remove]]
-remove
-++++++
+#### remove
Remove matching records from the collection. The IN message body will
act as the removal filter query, and is expected to be of type
@@ -522,13 +487,9 @@ A header with key `CamelMongoDbRecordsAffected` is returned
containing the number of records deleted (copied from
`WriteResult.getN()`).
-[[MongoDB-Otheroperations]]
-Other operations
-^^^^^^^^^^^^^^^^
+### Other operations
-[[MongoDB-aggregate]]
-aggregate
-+++++++++
+#### aggregate
*Available as of Camel 2.14*
@@ -546,9 +507,7 @@ from("direct:aggregate")
.to("mock:resultAggregate");
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-getDbStats]]
-getDbStats
-++++++++++
+#### getDbStats
Equivalent of running the `db.stats()` command in the MongoDB shell,
which displays useful statistic figures about the database. +
@@ -585,9 +544,7 @@ assertTrue("Result is not of type DBObject", result instanceof DBObject);
The operation will return a data structure similar to the one displayed
in the shell, in the form of a `DBObject` in the OUT message body.
-[[MongoDB-getColStats]]
-getColStats
-+++++++++++
+#### getColStats
Equivalent of running the `db.collection.stats()` command in the MongoDB
shell, which displays useful statistic figures about the collection. +
@@ -627,9 +584,7 @@ assertTrue("Result is not of type DBObject", result instanceof DBObject);
The operation will return a data structure similar to the one displayed
in the shell, in the form of a `DBObject` in the OUT message body.
-[[MongoDB-command]]
-command
-+++++++
+#### command
*Available as of Camel 2.15*
@@ -645,9 +600,7 @@ DBObject commandBody = new BasicDBObject("hostInfo", "1");
Object result = template.requestBody("direct:command", commandBody);
--------------------------------------------------------------------------------
-[[MongoDB-Dynamicoperations]]
-Dynamic operations
-^^^^^^^^^^^^^^^^^^
+### Dynamic operations
An Exchange can override the endpoint's fixed operation by setting the
`CamelMongoDbOperation` header, defined by the
@@ -665,9 +618,7 @@ Object result = template.requestBodyAndHeader("direct:insert", "irrelevantBody",
assertTrue("Result is not of type Long", result instanceof Long);
-----------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-TailableCursorConsumer]]
-Tailable Cursor Consumer
-~~~~~~~~~~~~~~~~~~~~~~~~
+### Tailable Cursor Consumer
MongoDB offers a mechanism to instantaneously consume ongoing data from
a collection, by keeping the cursor open just like the `tail -f` command
@@ -689,9 +640,7 @@ new objects are inserted, MongoDB will push them as DBObjects in natural
order to your tailable cursor consumer, who will transform them to an
Exchange and will trigger your route logic.
-[[MongoDB-Howthetailablecursorconsumerworks]]
-How the tailable cursor consumer works
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How the tailable cursor consumer works
To turn a cursor into a tailable cursor, a few special flags are to be
signalled to MongoDB when first generating the cursor. Once created, the
@@ -742,9 +691,7 @@ The above route will consume from the "flights.cancellations" capped
collection, using "departureTime" as the increasing field, with a
default regeneration cursor delay of 1000ms.
-[[MongoDB-Persistenttailtracking]]
-Persistent tail tracking
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Persistent tail tracking
Standard tail tracking is volatile and the last value is only kept in
memory. However, in practice you will need to restart your Camel
@@ -764,9 +711,7 @@ persisting at regular intervals too in the future (flush every 5
seconds) for added robustness if the demand is there. To request this
feature, please open a ticket in the Camel JIRA.
-[[MongoDB-Enablingpersistenttailtracking]]
-Enabling persistent tail tracking
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling persistent tail tracking
To enable this function, set at least the following options on the
endpoint URI:
@@ -812,9 +757,7 @@ from("mongodb:myDb?database=flights&collection=cancellations&tailTrackIncreasing
.to("mock:test");
-----------------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-TailtrackingOnOplog]]
-Oplog Tail Tracking
-^^^^^^^^^^^^^^^^^^^
+### Oplog Tail Tracking
The *oplog* collection tracking feature allows to implement trigger like functionality in MongoDB.
In order to activate this collection you will have first to activate a replica set. For more
@@ -928,9 +871,7 @@ public class MongoDbTracker {
-----------------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-Typeconversions]]
-Type conversions
-~~~~~~~~~~~~~~~~
+### Type conversions
The `MongoDbBasicConverters` type converter included with the
camel-mongodb component provides the following conversions:
@@ -954,9 +895,7 @@ object to a `Map`, which is in turn used to initialise a new
This type converter is auto-discovered, so you don't need to configure
anything manually.
-[[MongoDB-Seealso]]
-See also
-~~~~~~~~
+### See also
* http://www.mongodb.org/[MongoDB website]
* http://en.wikipedia.org/wiki/NoSQL[NoSQL Wikipedia article]
@@ -964,5 +903,4 @@ See also
current version]
*
http://svn.apache.org/viewvc/camel/trunk/components/camel-mongodb/src/test/[Unit
-tests] for more examples of usage
-
+tests] for more examples of usage
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mongodb3/src/main/docs/mongodb3-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mongodb3/src/main/docs/mongodb3-component.adoc b/components/camel-mongodb3/src/main/docs/mongodb3-component.adoc
index 7d9f61a..5d069ff 100644
--- a/components/camel-mongodb3/src/main/docs/mongodb3-component.adoc
+++ b/components/camel-mongodb3/src/main/docs/mongodb3-component.adoc
@@ -1,4 +1,4 @@
-# MongoDB Component
+## MongoDB Component
*Available as of Camel 2.19*
@@ -42,18 +42,14 @@ for this component:
</dependency>
------------------------------------------------------------
-[[MongoDB-URIformat]]
-URI format
-~~~~~~~~~~
+### URI format
[source,java]
---------------------------------------------------------------------------------------------------------------
mongodb3:connectionBean?database=databaseName&collection=collectionName&operation=operationName[&moreOptions...]
---------------------------------------------------------------------------------------------------------------
-[[MongoDB-options]]
-MongoDB options
-~~~~~~~~~~~~~~~
+### MongoDB options
// component options: START
@@ -106,9 +102,7 @@ readPreference *Remove in camel 2.19.* See Mongo client options <<MongoDB-Config
-[[MongoDB-ConfigurationofdatabaseinSpringXML]]
-Configuration of database in Spring XML
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Configuration of database in Spring XML
The following Spring XML creates a bean defining the connection to a
MongoDB instance.
@@ -134,9 +128,7 @@ xsi:schemaLocation="http://www.springframework.org/schema/context
</beans>
----------------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-Sampleroute]]
-Sample route
-^^^^^^^^^^^^
+### Sample route
The following route defined in Spring XML executes the operation
link:mongodb3.html[*dbStats*] on a collection.
@@ -153,17 +145,11 @@ link:mongodb3.html[*dbStats*] on a collection.
</route>
---------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-MongoDBoperations-producerendpoints]]
-MongoDB operations - producer endpoints
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### MongoDB operations - producer endpoints
-[[MongoDB-Queryoperations]]
-Query operations
-^^^^^^^^^^^^^^^^
+### Query operations
-[[MongoDB-findById]]
-findById
-++++++++
+#### findById
This operation retrieves only one element from the collection whose _id
field matches the content of the IN message body. The incoming object
@@ -183,9 +169,7 @@ from("direct:findById")
TIP: *Supports optional parameters*. This operation supports specifying a fields filter. See
link:mongodb3.html[Specifying optional parameters].
-[[MongoDB-findOneByQuery]]
-findOneByQuery
-++++++++++++++
+#### findOneByQuery
Use this operation to retrieve just one element (the first) from the collection that
matches a MongoDB query. *The query object is extracted `CamelMongoDbCriteria` header*.
@@ -216,9 +200,7 @@ from("direct:findOneByQuery")
TIP: *Supports optional parameters*. This operation supports specifying a fields projection and/or a sort clause. See
link:mongodb3.html[Specifying optional parameters].
-[[MongoDB-findAll]]
-findAll
-+++++++
+#### findAll
The `findAll` operation returns all documents matching a query, or none
at all, in which case all documents contained in the collection are
@@ -290,9 +272,7 @@ consideration. |int/Integer
TIP: *Supports optional parameters*. This operation supports specifying a fields projection and/or a sort clause. See
link:mongodb3.html[Specifying optional parameters].
-[[MongoDB-count]]
-count
-+++++
+#### count
Returns the total number of objects in a collection, returning a Long as
the OUT message body. +
@@ -322,9 +302,7 @@ Document query = ...
Long count = template.requestBodyAndHeader("direct:count", query, MongoDbConstants.COLLECTION, "dynamicCollectionName");
------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-Specifyingoptionalparameters]]
-Specifying a fields filter (projection)
-+++++++++++++++++++++++++++++++++++++++
+#### Specifying a fields filter (projection)
Query operations will, by default, return the matching objects in their
entirety (with all their fields). If your documents are large and you
@@ -356,8 +334,7 @@ Bson fieldProjection = Projection.exclude("_id", "boringField");
Object result = template.requestBodyAndHeader("direct:findAll", ObjectUtils.NULL, MongoDbConstants.FIELDS_PROJECTION, fieldProjection);
----------------------------------------------------------------------------------------------------------------------------
-Specifying a sort clause
-++++++++++++++++++++++++
+#### Specifying a sort clause
There is a often a requirement to fetch the min/max record from a
collection based on sorting by a particular field
@@ -391,13 +368,9 @@ to a single field, based on the `documentTimestamp` field:
;
----------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-Create/updateoperations]]
-Create/update operations
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Create/update operations
-[[MongoDB-insert]]
-insert
-++++++
+#### insert
Inserts an new object into the MongoDB collection, taken from the IN
message body. Type conversion is attempted to turn it into `Document` or
@@ -444,9 +417,7 @@ have been inserted.
In MongoDB Java Driver 3.x the insertOne and insertMany operation return void.
The Camel insert operation return the Document or List of Documents inserted. Note that each Documents are Updated by a new OID if need.
-[[MongoDB-save]]
-save
-++++
+#### save
The save operation is equivalent to an _upsert_ (UPdate, inSERT)
operation, where the record will be updated, and if it doesn't exist, it
@@ -478,9 +449,7 @@ from("direct:insert")
.to("mongodb3:myDb?database=flights&collection=tickets&operation=save");
---------------------------------------------------------------------------
-[[MongoDB-update]]
-update
-++++++
+#### update
Update one or multiple records on the collection. Requires a filter query and
a update rules.
@@ -549,13 +518,9 @@ Object result = template.requestBodyAndHeader("direct:update", updateObj, MongoD
------------------------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-Deleteoperations]]
-Delete operations
-^^^^^^^^^^^^^^^^^
+### Delete operations
-[[MongoDB-remove]]
-remove
-++++++
+#### remove
Remove matching records from the collection. The IN message body will
act as the removal filter query, and is expected to be of type
@@ -576,13 +541,9 @@ A header with key `CamelMongoDbRecordsAffected` is returned
containing the number of records deleted (copied from
`WriteResult.getN()`).
-[[MongoDB-Otheroperations]]
-Other operations
-^^^^^^^^^^^^^^^^
+### Other operations
-[[MongoDB-aggregate]]
-aggregate
-+++++++++
+#### aggregate
Perform a aggregation with the given pipeline contained in the
body.�*Aggregations could be long and heavy operations. Use with care.*
@@ -600,9 +561,7 @@ from("direct:aggregate")
.to("mock:resultAggregate");
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-getDbStats]]
-getDbStats
-++++++++++
+#### getDbStats
Equivalent of running the `db.stats()` command in the MongoDB shell,
which displays useful statistic figures about the database. +
@@ -639,9 +598,7 @@ assertTrue("Result is not of type Document", result instanceof Document);
The operation will return a data structure similar to the one displayed
in the shell, in the form of a `Document` in the OUT message body.
-[[MongoDB-getColStats]]
-getColStats
-+++++++++++
+#### getColStats
Equivalent of running the `db.collection.stats()` command in the MongoDB
shell, which displays useful statistic figures about the collection. +
@@ -681,9 +638,7 @@ assertTrue("Result is not of type Document", result instanceof Document);
The operation will return a data structure similar to the one displayed
in the shell, in the form of a `Document` in the OUT message body.
-[[MongoDB-command]]
-command
-+++++++
+#### command
Run the body as a command on database. Usefull for admin operation as
getting host informations, replication or sharding status.
@@ -697,9 +652,7 @@ DBObject commandBody = new BasicDBObject("hostInfo", "1");
Object result = template.requestBody("direct:command", commandBody);
--------------------------------------------------------------------------------
-[[MongoDB-Dynamicoperations]]
-Dynamic operations
-^^^^^^^^^^^^^^^^^^
+### Dynamic operations
An Exchange can override the endpoint's fixed operation by setting the
`CamelMongoDbOperation` header, defined by the
@@ -717,9 +670,7 @@ Object result = template.requestBodyAndHeader("direct:insert", "irrelevantBody",
assertTrue("Result is not of type Long", result instanceof Long);
-----------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-TailableCursorConsumer]]
-Tailable Cursor Consumer
-~~~~~~~~~~~~~~~~~~~~~~~~
+### Tailable Cursor Consumer
MongoDB offers a mechanism to instantaneously consume ongoing data from
a collection, by keeping the cursor open just like the `tail -f` command
@@ -741,9 +692,7 @@ new objects are inserted, MongoDB will push them as `Document` in natural
order to your tailable cursor consumer, who will transform them to an
Exchange and will trigger your route logic.
-[[MongoDB-Howthetailablecursorconsumerworks]]
-How the tailable cursor consumer works
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How the tailable cursor consumer works
To turn a cursor into a tailable cursor, a few special flags are to be
signalled to MongoDB when first generating the cursor. Once created, the
@@ -794,9 +743,7 @@ The above route will consume from the "flights.cancellations" capped
collection, using "departureTime" as the increasing field, with a
default regeneration cursor delay of 1000ms.
-[[MongoDB-Persistenttailtracking]]
-Persistent tail tracking
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Persistent tail tracking
Standard tail tracking is volatile and the last value is only kept in
memory. However, in practice you will need to restart your Camel
@@ -816,9 +763,7 @@ persisting at regular intervals too in the future (flush every 5
seconds) for added robustness if the demand is there. To request this
feature, please open a ticket in the Camel JIRA.
-[[MongoDB-Enablingpersistenttailtracking]]
-Enabling persistent tail tracking
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling persistent tail tracking
To enable this function, set at least the following options on the
endpoint URI:
@@ -864,9 +809,7 @@ from("mongodb3:myDb?database=flights&collection=cancellations&tailTrackIncreasin
.to("mock:test");
-----------------------------------------------------------------------------------------------------------------------------------
-[[MongoDB-Typeconversions]]
-Type conversions
-~~~~~~~~~~~~~~~~
+### Type conversions
The `MongoDbBasicConverters` type converter included with the
camel-mongodb component provides the following conversions:
@@ -887,9 +830,7 @@ object to a `Map`, which is in turn used to initialise a new
This type converter is auto-discovered, so you don't need to configure
anything manually.
-[[MongoDB-Seealso]]
-See also
-~~~~~~~~
+### See also
* http://www.mongodb.org/[MongoDB website]
* http://en.wikipedia.org/wiki/NoSQL[NoSQL Wikipedia article]
@@ -897,5 +838,4 @@ See also
current version]
*
http://svn.apache.org/viewvc/camel/trunk/components/camel-mongodb/src/test/[Unit
-tests] for more examples of usage
-
+tests] for more examples of usage
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mqtt/src/main/docs/mqtt-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mqtt/src/main/docs/mqtt-component.adoc b/components/camel-mqtt/src/main/docs/mqtt-component.adoc
index c950628..f813c9d 100644
--- a/components/camel-mqtt/src/main/docs/mqtt-component.adoc
+++ b/components/camel-mqtt/src/main/docs/mqtt-component.adoc
@@ -1,4 +1,4 @@
-# MQTT Component
+## MQTT Component
*Available as of Camel 2.10*
@@ -20,9 +20,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[MQTT-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------
@@ -31,9 +29,7 @@ mqtt://name[?options]
Where *name* is the name you want to assign the component.
-[[MQTT-Options]]
-Options
-^^^^^^^
+### Options
@@ -112,9 +108,7 @@ The MQTT component supports 40 endpoint options which are listed below:
-[[MQTT-Samples]]
-Samples
-^^^^^^^
+### Samples
Sending messages:
@@ -130,9 +124,7 @@ Consuming messages:
from("mqtt:bar?subscribeTopicName=test.mqtt.topic").transform(body().convertToString()).to("mock:result")
---------------------------------------------------------------------------------------------------------
-[[MQTT-Endpoints]]
-Endpoints
-~~~~~~~~~
+### Endpoints
Camel supports the link:message-endpoint.html[Message Endpoint] pattern
using the
@@ -158,12 +150,9 @@ implements the link:polling-consumer.html[Polling Consumer] pattern for
consuming message exchanges from the endpoint via a
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/PollingConsumer.html[PollingConsumer]
-[[MQTT-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
* link:configuring-camel.html[Configuring Camel]
* link:message-endpoint.html[Message Endpoint] pattern
* link:uris.html[URIs]
-* link:writing-components.html[Writing Components]
-
+* link:writing-components.html[Writing Components]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-msv/src/main/docs/msv-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-msv/src/main/docs/msv-component.adoc b/components/camel-msv/src/main/docs/msv-component.adoc
index 07e354b..6c843c2 100644
--- a/components/camel-msv/src/main/docs/msv-component.adoc
+++ b/components/camel-msv/src/main/docs/msv-component.adoc
@@ -1,4 +1,4 @@
-# MSV Component
+## MSV Component
The MSV component performs XML validation of the message body using the
https://msv.dev.java.net/[MSV Library] and any of the supported XML
@@ -22,9 +22,7 @@ Note that the link:jing.html[Jing] component also supports
http://relaxng.org/compact-tutorial-20030326.html[RelaxNG Compact
Syntax]
-[[MSV-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------
@@ -45,9 +43,7 @@ msv:http://acme.com/cheese.rng
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[MSV-Options]]
-Options
-^^^^^^^
+### Options
@@ -97,9 +93,7 @@ The MSV component supports 12 endpoint options which are listed below:
-[[MSV-Example]]
-Example
-^^^^^^^
+### Example
The following
http://svn.apache.org/repos/asf/camel/trunk/components/camel-msv/src/test/resources/org/apache/camel/component/validator/msv/camelContext.xml[example]
@@ -109,12 +103,9 @@ based on whether or not the XML matches the given
http://relaxng.org/[RelaxNG XML Schema] (which is supplied on the
classpath).
-[[MSV-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-mustache/src/main/docs/mustache-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mustache/src/main/docs/mustache-component.adoc b/components/camel-mustache/src/main/docs/mustache-component.adoc
index 5b5e778..a6ad9ce 100644
--- a/components/camel-mustache/src/main/docs/mustache-component.adoc
+++ b/components/camel-mustache/src/main/docs/mustache-component.adoc
@@ -1,4 +1,4 @@
-# Mustache Component
+## Mustache Component
*Available as of Camel 2.12*
@@ -19,9 +19,7 @@ for this component:
</dependency>
---------------------------------------------------------------------------------
-[[Mustache-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------
@@ -35,9 +33,7 @@ file://folder/myfile.mustache[file://folder/myfile.mustache]).
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Mustache-Options]]
-Options
-^^^^^^^
+### Options
{% raw %}
@@ -84,9 +80,7 @@ The Mustache component supports 6 endpoint options which are listed below:
{% endraw %}
-[[Mustache-MustacheContext]]
-Mustache Context
-^^^^^^^^^^^^^^^^
+### Mustache Context
Camel will provide exchange information in the Mustache context (just a
`Map`). The `Exchange` is transferred as:
@@ -110,9 +104,7 @@ Camel will provide exchange information in the Mustache context (just a
|`response` |The Out message (only for InOut message exchange pattern).
|=======================================================================
-[[Mustache-Dynamictemplates]]
-Dynamic templates
-^^^^^^^^^^^^^^^^^
+### Dynamic templates
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these
@@ -129,9 +121,7 @@ configured. |
|MustacheConstants.MUSTACHE_TEMPLATE |String |The template to use instead of the endpoint configured. |
|=======================================================================
-[[Mustache-Samples]]
-Samples
-^^^^^^^
+### Samples
For example you could use something like:
@@ -164,9 +154,7 @@ setHeader(MustacheConstants.MUSTACHE_RESOURCE_URI).constant("path/to/my/template
to("mustache:dummy");
--------------------------------------------------------------------------------------------
-[[Mustache-TheEmailSample]]
-The Email Sample
-^^^^^^^^^^^^^^^^
+### The Email Sample
In this sample we want to use Mustache templating for an order
confirmation email. The email template is laid out in Mustache as:
@@ -181,12 +169,9 @@ Regards Camel Riders Bookstore
{{body}}
-------------------------------------------------
-[[Mustache-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-mvel/src/main/docs/mvel-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mvel/src/main/docs/mvel-component.adoc b/components/camel-mvel/src/main/docs/mvel-component.adoc
index bdd5e38..2207c65 100644
--- a/components/camel-mvel/src/main/docs/mvel-component.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-component.adoc
@@ -1,4 +1,4 @@
-# MVEL Component
+## MVEL Component
*Available as of Camel 2.12*
@@ -19,9 +19,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[MVELComponent-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------
@@ -35,9 +33,7 @@ file://folder/myfile.mvel[file://folder/myfile.mvel]).
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[MVELComponent-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -64,9 +60,7 @@ The MVEL component supports 4 endpoint options which are listed below:
-[[MVELComponent-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
The mvel component sets a couple headers on the message.
@@ -77,9 +71,7 @@ The mvel component sets a couple headers on the message.
|`CamelMvelResourceUri` |The *templateName* as a `String` object.
|=======================================================================
-[[MVELComponent-MVELContext]]
-MVEL Context
-^^^^^^^^^^^^
+### MVEL Context
Camel will provide exchange information in the MVEL context (just a
`Map`). The `Exchange` is transfered as:
@@ -107,9 +99,7 @@ Camel will provide exchange information in the MVEL context (just a
|`response` |The Out message (only for InOut message exchange pattern).
|=======================================================================
-[[MVELComponent-Hotreloading]]
-Hot reloading
-^^^^^^^^^^^^^
+### Hot reloading
The mvel template resource is, by default, hot reloadable for both file
and classpath resources (expanded jar). If you set `contentCache=true`,
@@ -117,9 +107,7 @@ Camel will only load the resource once, and thus hot reloading is not
possible. This scenario can be used in production, when the resource
never changes.
-[[MVELComponent-Dynamictemplates]]
-Dynamic templates
-^^^^^^^^^^^^^^^^^
+### Dynamic templates
Camel provides two headers by which you can define a different resource
location for a template or the template content itself. If any of these
@@ -136,9 +124,7 @@ configured.
|CamelMvelTemplate |String |The template to use instead of the endpoint configured.
|=======================================================================
-[[MVELComponent-Samples]]
-Samples
-^^^^^^^
+### Samples
For example you could use something like
@@ -171,12 +157,9 @@ from("direct:in").
to("velocity:dummy");
------------------------------------------------------------------------------------------
-[[MVELComponent-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-mvel/src/main/docs/mvel-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mvel/src/main/docs/mvel-language.adoc b/components/camel-mvel/src/main/docs/mvel-language.adoc
index 15d4549..a38222e 100644
--- a/components/camel-mvel/src/main/docs/mvel-language.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-language.adoc
@@ -1,4 +1,4 @@
-# MVEL Language
+## MVEL Language
Camel allows Mvel to be used as an link:expression.html[Expression] or
link:predicate.html[Predicate] the link:dsl.html[DSL] or
@@ -20,9 +20,7 @@ you can construct the syntax as follows:
"getRequest().getBody().getFamilyName()"
----------------------------------------
-[[Mvel-Options]]
-Mvel Options
-^^^^^^^^^^^^
+### Mvel Options
// language options: START
The MVEL language supports 1 options which are listed below.
@@ -38,9 +36,7 @@ The MVEL language supports 1 options which are listed below.
{% endraw %}
// language options: END
-[[Mvel-Variables]]
-Variables
-^^^^^^^^^
+### Variables
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -67,9 +63,7 @@ Variables
|property(name, type) |Type |the property by the given name as the given type
|=======================================================================
-[[Mvel-Samples]]
-Samples
-^^^^^^^
+### Samples
For example you could use Mvel inside a link:message-filter.html[Message
Filter] in XML
@@ -92,9 +86,7 @@ And the sample using Java DSL:
from("seda:foo").filter().mvel("request.headers.foo == 'bar'").to("seda:bar");
---------------------------------------------------------------------------------
-[[Mvel-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
*Available as of Camel 2.11*
@@ -108,9 +100,7 @@ eg to refer to a file on the classpath you can do:
.setHeader("myHeader").mvel("resource:classpath:script.mvel")
-------------------------------------------------------------
-[[Mvel-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Mvel in your camel routes you need to add the a dependency on
*camel-mvel* which implements the Mvel language.
@@ -126,4 +116,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-mvel</artifactId>
<version>x.x.x</version>
</dependency>
--------------------------------------
+-------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mybatis/src/main/docs/mybatis-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mybatis/src/main/docs/mybatis-component.adoc b/components/camel-mybatis/src/main/docs/mybatis-component.adoc
index a22f25a..92e3567 100644
--- a/components/camel-mybatis/src/main/docs/mybatis-component.adoc
+++ b/components/camel-mybatis/src/main/docs/mybatis-component.adoc
@@ -1,4 +1,4 @@
-# MyBatis Component
+## MyBatis Component
*Available as of Camel 2.7*
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[MyBatis-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------
@@ -40,9 +38,7 @@ the root of the classpath with the expected name of
If the file is located in another location, you will need to configure
the `configurationUri` option on the `MyBatisComponent` component.
-[[MyBatis-Options]]
-Options
-^^^^^^^
+### Options
@@ -110,9 +106,7 @@ The MyBatis component supports 30 endpoint options which are listed below:
-[[MyBatis-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Camel will populate the result message, either IN or OUT with a header
with the statement used:
@@ -128,9 +122,7 @@ instance an `INSERT` could return the auto-generated key, or number of
rows etc.
|=======================================================================
-[[MyBatis-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
The response from MyBatis will only be set as the body if it's a
`SELECT` statement. That means, for example, for `INSERT` statements
@@ -138,9 +130,7 @@ Camel will not replace the body. This allows you to continue routing and
keep the original body. The response from MyBatis is always stored in
the header with the key `CamelMyBatisResult`.
-[[MyBatis-Samples]]
-Samples
-^^^^^^^
+### Samples
For example if you wish to consume beans from a JMS queue and insert
them into a database you could do the following:
@@ -172,9 +162,7 @@ Where *insertAccount* is the MyBatis ID in the SQL mapping file:
</insert>
------------------------------------------------------------
-[[MyBatis-UsingStatementTypeforbettercontrolofMyBatis]]
-Using StatementType for better control of MyBatis
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using StatementType for better control of MyBatis
When routing to an MyBatis endpoint you will want more fine grained
control so you can control whether the SQL statement to be executed is a
@@ -192,9 +180,7 @@ We can do the same for some of the other operations, such as
And the same for `UPDATE`, where we can send an `Account` object as the
IN body to MyBatis:
-[[MyBatis-UsingInsertListStatementType]]
-Using InsertList StatementType
-++++++++++++++++++++++++++++++
+#### Using InsertList StatementType
*Available as of Camel 2.10*
@@ -206,9 +192,7 @@ Then you can insert multiple rows, by sending a Camel message to the
`mybatis` endpoint which uses the `InsertList` statement type, as shown
below:
-[[MyBatis-UsingUpdateListStatementType]]
-Using UpdateList StatementType
-++++++++++++++++++++++++++++++
+#### Using UpdateList StatementType
*Available as of Camel 2.11*
@@ -240,9 +224,7 @@ from("direct:start")
.to("mock:result");
--------------------------------------------------------------
-[[MyBatis-UsingDeleteListStatementType]]
-Using DeleteList StatementType
-++++++++++++++++++++++++++++++
+#### Using DeleteList StatementType
*Available as of Camel 2.11*
@@ -273,18 +255,14 @@ from("direct:start")
.to("mock:result");
--------------------------------------------------------------
-[[MyBatis-NoticeonInsertList,UpdateListandDeleteListStatementTypes]]
-Notice on InsertList, UpdateList and DeleteList StatementTypes
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Notice on InsertList, UpdateList and DeleteList StatementTypes
Parameter of any type (List, Map, etc.) can be passed to mybatis and an
end user is responsible for handling it as required +
with the help of http://www.mybatis.org/core/dynamic-sql.html[mybatis
dynamic queries] capabilities.
-[[MyBatis-Scheduledpollingexample]]
-Scheduled polling example
-+++++++++++++++++++++++++
+#### Scheduled polling example
This component supports scheduled polling and can therefore be used as
a�link:polling-consumer.html[Polling Consumer]. For example to poll the
@@ -319,9 +297,7 @@ And the MyBatis SQL mapping file used:
</select>
----------------------------------------------------------------------------
-[[MyBatis-UsingonConsume]]
-Using onConsume
-+++++++++++++++
+#### Using onConsume
This component supports executing statements *after* data have been
consumed and processed by Camel. This allows you to do post updates in
@@ -335,9 +311,7 @@ database to processed, so we avoid consuming it twice or more.
And the statements in the sqlmap file:
-[[MyBatis-Participatingintransactions]]
-Participating in transactions
-+++++++++++++++++++++++++++++
+#### Participating in transactions
Setting up a transaction manager under camel-mybatis can be a little bit
fiddly, as it involves externalising the database configuration outside
@@ -420,12 +394,9 @@ usual:
</camelContext>
------------------------------------------------------------------------------------------------
-[[MyBatis-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-nagios/src/main/docs/nagios-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-nagios/src/main/docs/nagios-component.adoc b/components/camel-nagios/src/main/docs/nagios-component.adoc
index 36677bb..e608975 100644
--- a/components/camel-nagios/src/main/docs/nagios-component.adoc
+++ b/components/camel-nagios/src/main/docs/nagios-component.adoc
@@ -1,4 +1,4 @@
-# Nagios Component
+## Nagios Component
*Available as of Camel 2.3*
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Nagios-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------
@@ -33,9 +31,7 @@ its endpoint. +
Camel also provides a link:camel-jmx.html[EventNotifer] which allows
you to send notifications to Nagios.
-[[Nagios-Options]]
-Options
-^^^^^^^
+### Options
@@ -82,9 +78,7 @@ The Nagios component supports 8 endpoint options which are listed below:
-[[Nagios-Sendingmessageexamples]]
-Sending message examples
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending message examples
You can send a message to Nagios where the message payload contains the
message. By default it will be `OK` level and use the
@@ -111,9 +105,7 @@ To send a `CRITICAL` message you can send the headers such as:
template.sendBodyAndHeaders("direct:start", "Hello Nagios", headers);
-----------------------------------------------------------------------------
-[[Nagios-UsingNagiosEventNotifer]]
-Using `NagiosEventNotifer`
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using `NagiosEventNotifer`
The link:nagios.html[Nagios] component also provides an
link:camel-jmx.html[EventNotifer] which you can use to send events to
@@ -136,12 +128,9 @@ In Spring XML its just a matter of defining a Spring bean with the type
link:advanced-configuration-of-camelcontext-using-spring.html[Advanced
configuration of CamelContext using Spring].
-[[Nagios-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-nats/src/main/docs/nats-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-nats/src/main/docs/nats-component.adoc b/components/camel-nats/src/main/docs/nats-component.adoc
index a1b45b8..d92076e 100644
--- a/components/camel-nats/src/main/docs/nats-component.adoc
+++ b/components/camel-nats/src/main/docs/nats-component.adoc
@@ -1,4 +1,4 @@
-# Nats Component
+## Nats Component
*Available since Camel 2.17.0*
@@ -17,9 +17,7 @@ their�`pom.xml`�for this component.
</dependency>
------------------------------------------------------------
-[[NATS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------
@@ -28,9 +26,7 @@ nats:servers[?options]
Where�*servers*�represents the list of NATS servers.
-[[NATS-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -78,9 +74,7 @@ The Nats component supports 23 endpoint options which are listed below:
-[[NATS-Headers]]
-Headers
-^^^^^^^
+### Headers
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -105,4 +99,4 @@ from("direct:send").to("nats://localhost:4222?topic=test");
[source,java]
----------------------------------------------------------------------------------------
from("nats://localhost:4222?topic=test&maxMessages=5&queueName=test").to("mock:result");
-----------------------------------------------------------------------------------------
+----------------------------------------------------------------------------------------
\ No newline at end of file
[08/14] camel git commit: Use single line header for adoc files
Posted by da...@apache.org.
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-http4/src/main/docs/http4-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-http4/src/main/docs/http4-component.adoc b/components/camel-http4/src/main/docs/http4-component.adoc
index 8e3076b..318b596 100644
--- a/components/camel-http4/src/main/docs/http4-component.adoc
+++ b/components/camel-http4/src/main/docs/http4-component.adoc
@@ -1,4 +1,4 @@
-# HTTP4 Component
+## HTTP4 Component
*Available as of Camel 2.3*
@@ -26,9 +26,7 @@ Camel-http4 uses http://hc.apache.org/httpcomponents-client-ga/[Apache
HttpClient 4.x] while camel-http uses
http://hc.apache.org/httpclient-3.x/[Apache HttpClient 3.x].
-[[HTTP4-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------------
@@ -47,9 +45,7 @@ Therefore it should never be used as input into your Camel Routes. To
bind/expose an HTTP endpoint via a HTTP server as input to a Camel
route, use the link:jetty.html[Jetty Component] instead.
-[[HTTP4-HttpOptions]]
-Http4 Component Options
-^^^^^^^^^^^^^^^^^^^^^^^
+### Http4 Component Options
@@ -138,9 +134,7 @@ The HTTP4 component supports 32 endpoint options which are listed below:
-[[HTTP4-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="10%,20%,70%",options="header",]
|=======================================================================
@@ -171,9 +165,7 @@ a content type, such as `text/html`.
provide a content encoding, such as `gzip`.
|=======================================================================
-[[HTTP4-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
Camel will store the HTTP response from the external server on the OUT
body. All headers from the IN message will be copied to the OUT message,
@@ -183,9 +175,7 @@ HTTP response headers as well to the OUT message headers.
�
-[[HTTP4-UsingSystemProperties]]
-Using System Properties
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using System Properties
When setting useSystemProperties to true, the HTTP Client will look for
the following System Properties and it will use it:
@@ -207,9 +197,7 @@ the following System Properties and it will use it:
* http.keepAlive
* http.maxConnections
-[[HTTP4-Responsecode]]
-Response code
-^^^^^^^^^^^^^
+### Response code
Camel will handle according to the HTTP response code:
@@ -227,9 +215,7 @@ the `HttpOperationFailedException` from being thrown for failed response
codes. This allows you to get any response from the remote server. +
There is a sample below demonstrating this.
-[[HTTP4-HttpOperationFailedException]]
-HttpOperationFailedException
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### HttpOperationFailedException
This exception contains the following information:
@@ -239,9 +225,7 @@ This exception contains the following information:
* Response body as a `java.lang.String`, if server provided a body as
response
-[[HTTP4-CallingusingGETorPOST]]
-Calling using GET or POST
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Calling using GET or POST
The following algorithm is used to determine whether the `GET` or `POST`
HTTP method should be used: +
@@ -251,9 +235,7 @@ HTTP method should be used: +
4. `POST` if there is data to send (body is not null). +
5. `GET` otherwise.
-[[HTTP4-HowtogetaccesstoHttpServletRequestandHttpServletResponse]]
-How to get access to HttpServletRequest and HttpServletResponse
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get access to HttpServletRequest and HttpServletResponse
You can get access to these two using the Camel type converter system
using +
@@ -266,9 +248,7 @@ HttpServletRequest request = exchange.getIn().getBody(HttpServletRequest.class);
HttpServletRequest response = exchange.getIn().getBody(HttpServletResponse.class);
----------------------------------------------------------------------------------
-[[HTTP4-ConfiguringURItocall]]
-Configuring URI to call
-^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring URI to call
You can set the HTTP producer's URI directly form the endpoint URI. In
the route below, Camel will call out to the external server, `oldhost`,
@@ -307,9 +287,7 @@ endpoint is configured with http4://oldhost. +
If the http4 endpoint is working in bridge mode, it will ignore the
message header of `Exchange.HTTP_URI`.
-[[HTTP4-ConfiguringURIParameters]]
-Configuring URI Parameters
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring URI Parameters
The *http* producer supports URI parameters to be sent to the HTTP
server. The URI parameters can either be set directly on the endpoint
@@ -330,9 +308,7 @@ from("direct:start")
.to("http4://oldhost");
---------------------------------------------------------------------
-[[HTTP4-HowtosetthehttpmethodtotheHTTPproducer]]
-How to set the http method (GET/PATCH/POST/PUT/DELETE/HEAD/OPTIONS/TRACE) to the HTTP producer
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to set the http method (GET/PATCH/POST/PUT/DELETE/HEAD/OPTIONS/TRACE) to the HTTP producer
*Using the http PATCH method*
@@ -372,9 +348,7 @@ And the equivalent Spring sample:
</camelContext>
---------------------------------------------------------------------
-[[HTTP4-Usingclienttimeout-SO_TIMEOUT]]
-Using client timeout - SO_TIMEOUT
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using client timeout - SO_TIMEOUT
See the
https://svn.apache.org/repos/asf/camel/trunk/components/camel-http4/src/test/java/org/apache/camel/component/http4/HttpSOTimeoutTest.java[HttpSOTimeoutTest]
@@ -384,9 +358,7 @@ unit test.
https://github.com/apache/camel/blob/master/components/camel-http4/src/test/java/org/apache/camel/component/http4/HttpSOTimeoutTest.java[HttpSOTimeoutTest]
unit test.
-[[HTTP4-ConfiguringaProxy]]
-Configuring a Proxy
-^^^^^^^^^^^^^^^^^^^
+### Configuring a Proxy
The HTTP4 component provides a way to configure a proxy.
@@ -399,9 +371,7 @@ from("direct:start")
There is also support for proxy authentication via the
`proxyAuthUsername` and `proxyAuthPassword` options.
-[[HTTP4-UsingproxysettingsoutsideofURI]]
-Using proxy settings outside of URI
-+++++++++++++++++++++++++++++++++++
+#### Using proxy settings outside of URI
To avoid System properties conflicts, you can set proxy configuration
only from the CamelContext or URI. +
@@ -432,9 +402,7 @@ Properties and then the endpoint proxy options if provided. +
Notice in *Camel 2.8* there is also a `http.proxyScheme` property you
can set to explicit configure the scheme to use.
-[[HTTP4-Configuringcharset]]
-Configuring charset
-^^^^^^^^^^^^^^^^^^^
+### Configuring charset
If you are using `POST` to send data you can configure the `charset`
using the `Exchange` property:
@@ -444,9 +412,7 @@ using the `Exchange` property:
exchange.setProperty(Exchange.CHARSET_NAME, "ISO-8859-1");
----------------------------------------------------------
-[[HTTP4-Samplewithscheduledpoll]]
-Sample with scheduled poll
-++++++++++++++++++++++++++
+#### Sample with scheduled poll
This sample polls the Google homepage every 10 seconds and write the
page to the file `message.html`:
@@ -459,9 +425,7 @@ from("timer://foo?fixedRate=true&delay=0&period=10000")
.to("file:target/google");
------------------------------------------------------------
-[[HTTP4-URIParametersfromtheendpointURI]]
-URI Parameters from the endpoint URI
-++++++++++++++++++++++++++++++++++++
+#### URI Parameters from the endpoint URI
In this sample we have the complete URI endpoint that is just what you
would have typed in a web browser. Multiple URI parameters can of course
@@ -474,9 +438,7 @@ web browser. Camel does no tricks here.
template.sendBody("http4://www.google.com/search?q=Camel", null);
-----------------------------------------------------------------
-[[HTTP4-URIParametersfromtheMessage]]
-URI Parameters from the Message
-+++++++++++++++++++++++++++++++
+#### URI Parameters from the Message
[source,java]
------------------------------------------------------------------
@@ -489,9 +451,7 @@ template.sendBody("http4://www.google.com/search", null, headers);
In the header value above notice that it should *not* be prefixed with
`?` and you can separate parameters as usual with the `&` char.
-[[HTTP4-GettingtheResponseCode]]
-Getting the Response Code
-+++++++++++++++++++++++++
+#### Getting the Response Code
You can get the HTTP response code from the HTTP4 component by getting
the value from the Out message header with
@@ -508,25 +468,19 @@ Message out = exchange.getOut();
int responseCode = out.getHeader(Exchange.HTTP_RESPONSE_CODE, Integer.class);
------------------------------------------------------------------------------------
-[[HTTP4-DisablingCookies]]
-Disabling Cookies
-^^^^^^^^^^^^^^^^^
+### Disabling Cookies
To disable cookies you can set the HTTP Client to ignore cookies by
adding this URI option: +
`httpClient.cookiePolicy=ignoreCookies`
-[[HTTP4-AdvancedUsage]]
-Advanced Usage
-^^^^^^^^^^^^^^
+### Advanced Usage
If you need more control over the HTTP producer you should use the
`HttpComponent` where you can set various classes to give you custom
behavior.
-[[HTTP4-SettingupSSLforHTTPClient]]
-Setting up SSL for HTTP Client
-++++++++++++++++++++++++++++++
+#### Setting up SSL for HTTP Client
[[HTTP4-UsingtheJSSEConfigurationUtility]]
Using the JSSE Configuration Utility
@@ -696,4 +650,4 @@ property.
<property name="sslContextParameters" ref="sslContextParams2"/>
<property name="x509HostnameVerifier" ref="hostnameVerifier"/>
</bean>
-----------------------------------------------------------------------------
+----------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ibatis/src/main/docs/ibatis-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ibatis/src/main/docs/ibatis-component.adoc b/components/camel-ibatis/src/main/docs/ibatis-component.adoc
index 0203cc2..ddedce8 100644
--- a/components/camel-ibatis/src/main/docs/ibatis-component.adoc
+++ b/components/camel-ibatis/src/main/docs/ibatis-component.adoc
@@ -1,4 +1,4 @@
-# iBatis Component
+## iBatis Component
The *ibatis:* component allows you to query, poll, insert, update and
delete data in a relational database using
@@ -27,9 +27,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[iBATIS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
------------------------------
@@ -50,9 +48,7 @@ the root of the classpath and expected named as `SqlMapConfig.xml`. +
In Camel 2.2 you can configure this on the iBatisComponent with the
`setSqlMapConfig(String)` method.
-[[iBATIS-Options]]
-Options
-^^^^^^^
+### Options
@@ -123,9 +119,7 @@ The iBatis component supports 28 endpoint options which are listed below:
-[[iBATIS-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Camel will populate the result message, either IN or OUT with a header
with the operationName used:
@@ -141,9 +135,7 @@ instance an `INSERT` could return the auto-generated key, or number of
rows etc.
|=======================================================================
-[[iBATIS-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
The response from iBatis will only be set as body if it's a `SELECT`
statement. That means, for example, for `INSERT` statements Camel will
@@ -151,9 +143,7 @@ not replace the body. This allows you to continue routing and keep the
original body. The response from iBatis is always stored in the header
with the key `CamelIBatisResult`.
-[[iBATIS-Samples]]
-Samples
-^^^^^^^
+### Samples
For example if you wish to consume beans from a JMS queue and insert
them into a database you could do the following:
@@ -185,9 +175,7 @@ Where *insertAccount* is the iBatis ID in the SQL map file:
</insert>
------------------------------------------------------------
-[[iBATIS-UsingStatementTypeforbettercontrolofIBatis]]
-Using StatementType for better control of IBatis
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using StatementType for better control of IBatis
When routing to an iBatis endpoint you want more fine grained control so
you can control whether the SQL statement to be executed is a `SELEECT`,
@@ -205,9 +193,7 @@ We can do the same for some of the other operations, such as
And the same for `UPDATE`, where we can send an `Account` object as IN
body to iBatis:
-[[iBATIS-Scheduledpollingexample]]
-Scheduled polling example
-+++++++++++++++++++++++++
+#### Scheduled polling example
Since this component does not support scheduled polling, you need to use
another mechanism for triggering the scheduled polls, such as the
@@ -231,9 +217,7 @@ And the iBatis SQL map file used:
</select>
----------------------------------------------------------------------------
-[[iBATIS-UsingonConsume]]
-Using onConsume
-+++++++++++++++
+#### Using onConsume
This component supports executing statements *after* data have been
consumed and processed by Camel. This allows you to do post updates in
@@ -247,14 +231,11 @@ database to processed, so we avoid consuming it twice or more.
And the statements in the sqlmap file:
-[[iBATIS-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:mybatis.html[MyBatis]
-
+* link:mybatis.html[MyBatis]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ical/src/main/docs/ical-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ical/src/main/docs/ical-dataformat.adoc b/components/camel-ical/src/main/docs/ical-dataformat.adoc
index 39128d5..ceb68c8 100644
--- a/components/camel-ical/src/main/docs/ical-dataformat.adoc
+++ b/components/camel-ical/src/main/docs/ical-dataformat.adoc
@@ -1,4 +1,4 @@
-# iCal DataFormat
+## iCal DataFormat
*Available as of Camel 2.11.1*
@@ -26,9 +26,7 @@ END:VEVENT
END:VCALENDAR
----------------------------------------------------------------------
-[[ICal-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The iCal dataformat supports 2 options which are listed below.
@@ -45,9 +43,7 @@ The iCal dataformat supports 2 options which are listed below.
{% endraw %}
// dataformat options: END
-[[ICal-BasicUsage]]
-Basic Usage
-^^^^^^^^^^^
+### Basic Usage
To unmarshal and marshal the message shown above, your route will look
like the following:
@@ -74,12 +70,9 @@ for this component:
</dependency>
------------------------------------------------------------
-[[ICal-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-infinispan/src/main/docs/infinispan-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-infinispan/src/main/docs/infinispan-component.adoc b/components/camel-infinispan/src/main/docs/infinispan-component.adoc
index bb014c1..6031c7d 100644
--- a/components/camel-infinispan/src/main/docs/infinispan-component.adoc
+++ b/components/camel-infinispan/src/main/docs/infinispan-component.adoc
@@ -1,4 +1,4 @@
-# Infinispan Component
+## Infinispan Component
*Available as of Camel 2.13.0*
@@ -22,18 +22,14 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Infinispan-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------
infinispan://hostName?[options]
-------------------------------
-[[Infinispan-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
The producer allows sending messages to a local infinispan cache
configured in the registry, or to a remote cache using the HotRod
@@ -76,9 +72,7 @@ The Infinispan component supports 15 endpoint options which are listed below:
-[[Infinispan-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="10%,10%,10%,10%,60%",options="header",]
|=======================================================================
@@ -123,9 +117,7 @@ present the command defaults to InifinispanConfiguration's one
operation returning something is ignored by the client application
|=======================================================================
-[[Infinispan-Example]]
-Example
-^^^^^^^
+### Example
Below is an example route that retrieves a value from the cache for a
specific key:
@@ -138,9 +130,7 @@ from("direct:start")
.to("infinispan://localhost?cacheContainer=#cacheContainer");
------------------------------------------------------------------------------------
-[[Infinispan-UsingtheInfinispanbasedidempotentrepository]]
-Using the Infinispan based idempotent repository
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the Infinispan based idempotent repository
In this section we will use the Infinispan based idempotent repository.
@@ -178,12 +168,9 @@ XML file as well:
For more information, see these resources...
-[[Infinispan-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-influxdb/src/main/docs/influxdb-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-influxdb/src/main/docs/influxdb-component.adoc b/components/camel-influxdb/src/main/docs/influxdb-component.adoc
index d171c5f..e8a7689 100644
--- a/components/camel-influxdb/src/main/docs/influxdb-component.adoc
+++ b/components/camel-influxdb/src/main/docs/influxdb-component.adoc
@@ -1,4 +1,4 @@
-# InfluxDB Component
+## InfluxDB Component
*Available as of Camel 2.18.0*
@@ -26,18 +26,14 @@ for this component:
</dependency>
------------------------------------------------------------
-[[InfluxDb-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------
influxdb://beanName?[options]
-------------------------------
-[[InfluxDb-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
The producer allows sending messages to a influxdb
configured in the registry, using the native java driver.
@@ -72,9 +68,7 @@ The InfluxDB component supports 7 endpoint options which are listed below:
-[[InfluxDb-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="10%,10%,10%,10%,60%",options="header",]
|=======================================================================
@@ -83,9 +77,7 @@ Message Headers
|=======================================================================
-[[InfluxDb-Example]]
-Example
-^^^^^^^
+### Example
Below is an example route that stores a point into the db (taking the db name from the URI)
@@ -106,12 +98,9 @@ from("direct:start")
For more information, see these resources...
-[[InfluxDb-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-irc/src/main/docs/irc-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-irc/src/main/docs/irc-component.adoc b/components/camel-irc/src/main/docs/irc-component.adoc
index 2ae82e3..af4a499 100644
--- a/components/camel-irc/src/main/docs/irc-component.adoc
+++ b/components/camel-irc/src/main/docs/irc-component.adoc
@@ -1,4 +1,4 @@
-# IRC Component
+## IRC Component
The *irc* component implements an
http://en.wikipedia.org/wiki/Internet_Relay_Chat[IRC] (Internet Relay
@@ -17,9 +17,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[IRC-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------------------------------------
@@ -30,9 +28,7 @@ irc:nick@host[:port]?channels=#channel1,#channel2,#channel3[?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[IRC-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -87,13 +83,9 @@ The IRC component supports 26 endpoint options which are listed below:
-[[IRC-SSLSupport]]
-SSL Support
-^^^^^^^^^^^
+### SSL Support
-[[IRC-UsingtheJSSEConfigurationUtility]]
-Using the JSSE Configuration Utility
-++++++++++++++++++++++++++++++++++++
+#### Using the JSSE Configuration Utility
As of Camel 2.9, the IRC component supports SSL/TLS configuration
through the link:camel-configuration-utilities.html[Camel JSSE
@@ -144,9 +136,7 @@ Spring DSL based configuration of endpoint
<to uri="ircs://camel-prd-user@server:6669/#camel-test?nickname=camel-prd&password=password&sslContextParameters=#sslContextParameters"/>...
----------------------------------------------------------------------------------------------------------------------------------------------
-[[IRC-Usingthelegacybasicconfigurationoptions]]
-Using the legacy basic configuration options
-++++++++++++++++++++++++++++++++++++++++++++
+#### Using the legacy basic configuration options
You can also connect to an SSL enabled IRC server, as follows:
@@ -165,9 +155,7 @@ If you need to provide your own custom trust manager, use the
ircs:host[:port]/#room?username=user&password=pass&trustManager=#referenceToMyTrustManagerBean
----------------------------------------------------------------------------------------------
-[[IRC-Usingkeys]]
-Using keys
-^^^^^^^^^^
+### Using keys
*Available as of Camel 2.2*
@@ -181,8 +169,7 @@ For example we join 3 channels where as only channel 1 and 3 uses a key.
irc:nick@irc.server.org?channels=#chan1,#chan2,#chan3&keys=chan1Key,,chan3key
-----------------------------------------------------------------------------
-Getting a list of users of the channel
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Getting a list of users of the channel
Using the `namesOnJoin` option one can invoke the IRC-`NAMES` command after the component has joined a channel.
The server will reply with `irc.num = 353`. So in order to process the result the property `onReply` has to be `true`.
@@ -199,12 +186,9 @@ from("ircs:nick@myserver:1234/#mychannelname?listOnJoin=true&onReply=true")
.to("mock:result").stop();
-----------------------------------------------------------------------------
-[[IRC-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-ironmq/src/main/docs/ironmq-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ironmq/src/main/docs/ironmq-component.adoc b/components/camel-ironmq/src/main/docs/ironmq-component.adoc
index 088c78b..18032c0 100644
--- a/components/camel-ironmq/src/main/docs/ironmq-component.adoc
+++ b/components/camel-ironmq/src/main/docs/ironmq-component.adoc
@@ -1,4 +1,4 @@
-# ironmq Component
+## ironmq Component
*Available as of Camel 2.17*
@@ -23,9 +23,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[IronMQ-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------------
@@ -33,9 +31,7 @@ URI format
-----------------------------
Where **queueName** identifies the IronMQ queue you want to publish or consume messages from.
-[[IronMQ-Options]]
-Options
-^^^^^^^
+### Options
@@ -90,9 +86,7 @@ The ironmq component supports 31 endpoint options which are listed below:
-[[IronMQ-IronMQComponentOptions]]
-IronMQComponent Options
-^^^^^^^^^^^^^^^^^^^^^^^
+### IronMQComponent Options
@@ -105,14 +99,10 @@ The ironmq component has no options.
-[[IronMQ-Messagebody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
Should be either a String or a array of Strings. In the latter case the batch of strings will be send to IronMQ as one request, creating one message pr. element in the array.
-[[IronMQ-MessageHeaders]]
-Producer message headers
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Producer message headers
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -121,8 +111,7 @@ Producer message headers
|CamelIronMQMessageId |String or io.iron.ironmq.Ids|The id of the IronMQ message as a String when sending a single message, or a Ids object when sending a array of strings.
|=======================================================================
-Consumer message headers
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Consumer message headers
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -133,8 +122,7 @@ Consumer message headers
|=======================================================================
-Consumer example
-^^^^^^^^^^^^^^^^
+### Consumer example
Consume 50 messages pr. poll from the queue 'testqueue' on aws eu, and save the messages to files.
@@ -144,12 +132,11 @@ from("ironmq:testqueue?ironMQCloud=https://mq-aws-eu-west-1-1.iron.io&projectId=
.to("file:somefolder");
--------------------------------------------------
-Producer example
-^^^^^^^^^^^^^^^^
+### Producer example
Dequeue from activemq jms and enqueue the messages on IronMQ.
[source,java]
--------------------------------------------------
from("activemq:foo")
.to("ironmq:testqueue?projectId=myIronMQProjectid&token=myIronMQToken");
---------------------------------------------------
+--------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jackson/src/main/docs/json-jackson-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jackson/src/main/docs/json-jackson-dataformat.adoc b/components/camel-jackson/src/main/docs/json-jackson-dataformat.adoc
index 5f9980d..5bdfa56 100644
--- a/components/camel-jackson/src/main/docs/json-jackson-dataformat.adoc
+++ b/components/camel-jackson/src/main/docs/json-jackson-dataformat.adoc
@@ -1,4 +1,4 @@
-# JSon Jackson DataFormat
+## JSon Jackson DataFormat
*Available as of Camel 2.18*
@@ -12,9 +12,7 @@ from("activemq:My.Queue").
to("mqseries:Another.Queue");
-------------------------------
-[[Jackson-Options]]
-Jackson Options
-^^^^^^^^^^^^^^^
+### Jackson Options
@@ -50,9 +48,7 @@ The JSon Jackson dataformat supports 17 options which are listed below.
-[[Jackson-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Jackson in your camel routes you need to add the dependency
on *camel-jackson* which implements this data format.
@@ -69,4 +65,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-jacksonxml/src/main/docs/jacksonxml-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jacksonxml/src/main/docs/jacksonxml-dataformat.adoc b/components/camel-jacksonxml/src/main/docs/jacksonxml-dataformat.adoc
index 45c89d5..874aa46 100644
--- a/components/camel-jacksonxml/src/main/docs/jacksonxml-dataformat.adoc
+++ b/components/camel-jacksonxml/src/main/docs/jacksonxml-dataformat.adoc
@@ -1,4 +1,4 @@
-# JacksonXML DataFormat
+## JacksonXML DataFormat
*Available as of Camel 2.16*
@@ -27,9 +27,7 @@ from("activemq:My.Queue").
to("mqseries:Another.Queue");
-------------------------------
-[[JacksonXML-Options]]
-JacksonXML Options
-^^^^^^^^^^^^^^^^^^
+### JacksonXML Options
@@ -62,9 +60,7 @@ The JacksonXML dataformat supports 15 options which are listed below.
// dataformat options: END
-[[JacksonXML-UsingJacksonXMLinSpringDSL]]
-Using Jackson XML in Spring DSL
-+++++++++++++++++++++++++++++++
+#### Using Jackson XML in Spring DSL
When using�link:data-format.html[Data Format]�in Spring DSL you need to
declare the data formats first. This is done in the�*DataFormats*�XML
@@ -90,9 +86,7 @@ And then you can refer to this id in the route:
</route>
-------------------------------------
-[[JacksonXML-ExcludingPOJOfieldsfrommarshalling]]
-Excluding POJO fields from marshalling
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Excluding POJO fields from marshalling
When marshalling a POJO to XML you might want to exclude certain fields
from the XML output. With Jackson you can
@@ -112,9 +106,7 @@ Note that the weight field is missing in the resulting XML:
<pojo age="30" weight="70"/>
----------------------------
-[[JacksonXML-Include/ExcludefieldsusingthejsonViewattributewithJacksonXMLDataFormat]]
-Include/Exclude fields using the�`jsonView`�attribute with�`JacksonXML`DataFormat
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Include/Exclude fields using the�`jsonView`�attribute with�`JacksonXML`DataFormat
As an example of using this attribute you can instead of:
@@ -144,9 +136,7 @@ And the same in XML DSL:
</marshal>
---------------------------------------------------------------------------------------------------------------------------------------------------
-[[JacksonXML-Settingserializationincludeoption]]
-Setting serialization include option
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting serialization include option
If you want to marshal a pojo to XML, and the pojo has some fields with
null values. And you want to skip these null values, then you need to
@@ -179,9 +169,7 @@ Or from XML DSL you configure this as
</dataFormats>
------------------------------------------------------
-[[JacksonXML-UnmarshallingfromXMLtoPOJOwithdynamicclassname]]
-Unmarshalling from XML to POJO with dynamic class name
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Unmarshalling from XML to POJO with dynamic class name
If you use jackson to unmarshal XML to POJO, then you can now specify a
header in the message that indicate which class name to unmarshal to. +
@@ -208,9 +196,7 @@ Or from XML DSL you configure this as
</dataFormats>
-------------------------------------------------------
-[[JacksonXML-UnmarshallingfromXMLtoListMaporListPojo]]
-Unmarshalling from XML�to List<Map> or List<pojo>
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Unmarshalling from XML�to List<Map> or List<pojo>
If you are using Jackson to unmarshal XML to a list of map/pojo, you can
now specify this by setting�`useList="true"`�or use
@@ -246,9 +232,7 @@ And you can specify the pojo type also
</dataFormats>
-------------------------------------------------------------------------------
-[[JacksonXML-UsingcustomJacksonmodules]]
-Using custom Jackson modules
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using custom Jackson modules
You can use custom Jackson modules by specifying the class names of
those using the moduleClassNames option as shown below.
@@ -280,9 +264,7 @@ to the module as shown below:
�Multiple modules can be specified separated by comma, such as
moduleRefs="myJacksonModule,myOtherModule"
-[[JacksonXML-EnablingordisablefeaturesusingJackson]]
-Enabling or disable features using Jackson
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling or disable features using Jackson
Jackson has a number of features you can enable or disable, which its
ObjectMapper uses. For example to disable failing on unknown properties
@@ -315,9 +297,7 @@ df.disableFeature(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES);
df.disableFeature(DeserializationFeature.FAIL_ON_NULL_FOR_PRIMITIVES);
----------------------------------------------------------------------
-[[JacksonXML-ConvertingMapstoPOJOusingJackson]]
-Converting Maps to POJO using Jackson
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Converting Maps to POJO using Jackson
Jackson�`ObjectMapper`�can be used to convert maps to POJO objects.
Jackson component comes with the data converter that can be used to
@@ -338,9 +318,7 @@ If there is a single�`ObjectMapper`�instance available in the Camel
registry, it will used by the converter to perform the conversion.
Otherwise the default mapper will be used. �
-[[JacksonXML-FormattedXMLmarshallingpretty-printing]]
-Formatted XML marshalling (pretty-printing)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Formatted XML marshalling (pretty-printing)
Using the�`prettyPrint`�option�one can output a well formatted XML�while
marshalling:
@@ -363,9 +341,7 @@ Please note that there are 5 different overloaded�`jacksonxml()`�DSL
methods which support the�`prettyPrint`�option in combination with other
settings for�`unmarshalType`,�`jsonView`�etc.�
-[[JacksonXML-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use Jackson XML in your camel routes you need to add the dependency
on *camel-jacksonxml* which implements this data format.
@@ -382,4 +358,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-javaspace/src/main/docs/javaspace-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-javaspace/src/main/docs/javaspace-component.adoc b/components/camel-javaspace/src/main/docs/javaspace-component.adoc
index ffe4cf5..141e93b 100644
--- a/components/camel-javaspace/src/main/docs/javaspace-component.adoc
+++ b/components/camel-javaspace/src/main/docs/javaspace-component.adoc
@@ -1,4 +1,4 @@
-# JavaSpace Component
+## JavaSpace Component
*Available as of Camel 2.1*
@@ -34,9 +34,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[JavaSpace-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------
@@ -46,9 +44,7 @@ javaspace:jini://host[?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[JavaSpace-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -82,13 +78,9 @@ The JavaSpace component supports 11 endpoint options which are listed below:
-[[JavaSpace-Examples]]
-Examples
-^^^^^^^^
+### Examples
-[[JavaSpace-SendingandReceivingEntries]]
-Sending and Receiving Entries
-+++++++++++++++++++++++++++++
+#### Sending and Receiving Entries
[source,java]
--------------------------------------------------------------------------------------------------------
@@ -104,9 +96,7 @@ from("javaspace:jini://localhost?spaceName=mySpace&templateId=template&verb=take
In this case the payload can be any object that inherits from the Jini
`Entry` type.
-[[JavaSpace-Sendingandreceivingserializableobjects]]
-Sending and receiving serializable objects
-++++++++++++++++++++++++++++++++++++++++++
+#### Sending and receiving serializable objects
Using the preceding routes, it is also possible to send and receive any
serializable object. The JavaSpace component detects that the payload is
@@ -114,9 +104,7 @@ not a Jini `Entry` and then it automatically wraps the payload with a
Camel Jini `Entry`. In this way, a JavaSpace can be used as a generic
transport mechanism.
-[[JavaSpace-UsingJavaSpaceasaremoteinvocationtransport]]
-Using JavaSpace as a remote invocation transport
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using JavaSpace as a remote invocation transport
The JavaSpace component has been tailored to work in combination with
the Camel bean component. It is therefore possible to call a remote POJO
@@ -138,12 +126,9 @@ realize the master/worker pattern. The idea is to use the POJO to
provide the business logic and rely on Camel for sending/receiving
requests/replies with the proper correlation.
-[[JavaSpace-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-jaxb/src/main/docs/jaxb-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc b/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
index ccbd16f..05b260b 100644
--- a/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
+++ b/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
@@ -1,13 +1,11 @@
-# JAXB DataFormat
+## JAXB DataFormat
JAXB is a link:data-format.html[Data Format] which uses the JAXB2 XML
marshalling standard which is included in Java 6 to unmarshal an XML
payload into Java objects or to marshal Java objects into an XML
payload.
-[[JAXB-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The JAXB dataformat supports 17 options which are listed below.
@@ -39,9 +37,7 @@ The JAXB dataformat supports 17 options which are listed below.
{% endraw %}
// dataformat options: END
-[[JAXB-UsingtheJavaDSL]]
-Using the Java DSL
-^^^^^^^^^^^^^^^^^^
+### Using the Java DSL
For example the following uses a named DataFormat of _jaxb_ which is
configured with a number of Java package names to initialize the
@@ -67,9 +63,7 @@ from("activemq:My.Queue").
to("mqseries:Another.Queue");
-------------------------------
-[[JAXB-UsingSpringXML]]
-Using Spring XML
-^^^^^^^^^^^^^^^^
+### Using Spring XML
The following example shows how to use JAXB to unmarshal using
link:spring.html[Spring] configuring the jaxb data type
@@ -84,9 +78,7 @@ You can specify context path using `:` as separator, for example
`com.mycompany:com.mycompany2`. Note that this is handled by JAXB
implementation and might change if you use different vendor than RI.
-[[JAXB-Partialmarshalling/unmarshalling]]
-Partial marshalling/unmarshalling
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Partial marshalling/unmarshalling
*This feature is new to Camel 2.2.0.* +
JAXB 2 supports marshalling and unmarshalling XML tree fragments. By
@@ -101,9 +93,7 @@ to JAXB's unmarshaler.
For marshalling you have to add `partNamespace` attribute with QName of
destination namespace. Example of Spring DSL you can find above.
-[[JAXB-Fragment]]
-Fragment
-^^^^^^^^
+### Fragment
*This feature is new to Camel 2.8.0.* +
JaxbDataFormat has new property fragment which can set the the
@@ -112,9 +102,7 @@ you don't want the JAXB Marshaller to generate the XML declaration, you
can set this option to be true. The default value of this property is
false.
-[[JAXB-IgnoringtheNonXMLCharacter]]
-Ignoring the NonXML Character
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Ignoring the NonXML Character
*This feature is new to Camel 2.2.0.* +
JaxbDataFromat supports to ignore the
@@ -159,9 +147,7 @@ Camel's NonXML filtering:
<jaxb filterNonXmlChars="true" contextPath="org.apache.camel.foo.bar" xmlStreamWriterWrapper="#testXmlStreamWriterWrapper" />
------------------------------------------------------------------------------------------------------------------------------
-[[JAXB-WorkingwiththeObjectFactory]]
-Working with the ObjectFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Working with the ObjectFactory
If you use XJC to create the java class from the schema, you will get an
ObjectFactory for you JAXB context. Since the ObjectFactory uses
@@ -174,9 +160,7 @@ unmarshaled message body. +
body, you need to set the JaxbDataFormat object's ignoreJAXBElement
property to be false.
-[[JAXB-Settingencoding]]
-Setting encoding
-^^^^^^^^^^^^^^^^
+### Setting encoding
You can set the *encoding* option to use when marshalling. Its the
`Marshaller.JAXB_ENCODING` encoding property on the JAXB Marshaller. +
@@ -187,9 +171,7 @@ property will overrule the encoding set on the JAXB data format.
In this Spring DSL we have defined to use `iso-8859-1` as the encoding:
-[[JAXB-Controllingnamespaceprefixmapping]]
-Controlling namespace prefix mapping
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Controlling namespace prefix mapping
*Available as of Camel 2.11*
@@ -227,9 +209,7 @@ with the id "myMap", which was what we defined above.
</marshal>
----------------------------------------------------------------------------------------
-[[JAXB-Schemavalidation]]
-Schema validation
-^^^^^^^^^^^^^^^^^
+### Schema validation
*Available as of Camel 2.11*
@@ -276,9 +256,7 @@ JaxbDataFormat jaxbDataFormat = new JaxbDataFormat();
jaxbDataFormat.setSchemaFactory(thradSafeSchemaFactory);
--------------------------------------------------------
-[[JAXB-SchemaLocation]]
-Schema Location
-^^^^^^^^^^^^^^^
+### Schema Location
*Available as of Camel 2.14*
@@ -303,9 +281,7 @@ You can do the same using the XML DSL:
</marshal>
--------------------------------------------------------
-[[JAXB-MarshaldatathatisalreadyXML]]
-Marshal data that is already XML
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Marshal data that is already XML
*Available as of Camel 2.14.1*
@@ -318,9 +294,7 @@ the JAXB marshaller only attempts to marshal JAXBElements
(javax.xml.bind.JAXBIntrospector#isElement returns true). And in those
situations the marshaller fallbacks to marshal the message body as-is.
-[[JAXB-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use JAXB in your camel routes you need to add the a dependency on
*camel-jaxb* which implements this data format.
@@ -336,4 +310,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-jaxb</artifactId>
<version>x.x.x</version>
</dependency>
--------------------------------------
+-------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jbpm/src/main/docs/jbpm-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jbpm/src/main/docs/jbpm-component.adoc b/components/camel-jbpm/src/main/docs/jbpm-component.adoc
index e4554ff..3100600 100644
--- a/components/camel-jbpm/src/main/docs/jbpm-component.adoc
+++ b/components/camel-jbpm/src/main/docs/jbpm-component.adoc
@@ -1,4 +1,4 @@
-# JBPM Component
+## JBPM Component
*Available as of Camel 2.16*
@@ -19,18 +19,14 @@ for this component:
</dependency>
------------------------------------------------------------------------------------
-[[jBPM-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
---------------------------------------------
jbpm::hostName[:port][/resourceUri][?options]
---------------------------------------------
-[[jBPM-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
// component options: START
@@ -81,9 +77,7 @@ The JBPM component supports 26 endpoint options which are listed below:
-[[jBPM-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
[width="100%",cols="10%,10%,10%,70%",options="header",]
|=======================================================================
@@ -131,9 +125,7 @@ org.infinispan.notifications.cachelistener.event.Event.Type
|CamelJBPMStatusList |null |List<Status> |The list of status to use when filtering tasks
|=======================================================================
-[[jBPM-Example]]
-Example
-^^^^^^^
+### Example
Below is an example route that starts a business process with id
project1.integration-test and deploymentId
@@ -147,13 +139,11 @@ from("direct:start")
�+ "&deploymentId=org.kie.example:project1:1.0.0-SNAPSHOT");
----------------------------------------------------------------------------------------------
-[[jBPM-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]
-�
+�
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jcache/src/main/docs/jcache-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jcache/src/main/docs/jcache-component.adoc b/components/camel-jcache/src/main/docs/jcache-component.adoc
index e7c737a..bae1e38 100644
--- a/components/camel-jcache/src/main/docs/jcache-component.adoc
+++ b/components/camel-jcache/src/main/docs/jcache-component.adoc
@@ -1,4 +1,4 @@
-# JCache Component
+## JCache Component
@@ -48,6 +48,4 @@ The JCache component supports 23 endpoint options which are listed below:
// component options: START
The JCache component has no options.
-// component options: END
-
-
+// component options: END
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jclouds/src/main/docs/jclouds-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jclouds/src/main/docs/jclouds-component.adoc b/components/camel-jclouds/src/main/docs/jclouds-component.adoc
index 81e67b7..6515e92 100644
--- a/components/camel-jclouds/src/main/docs/jclouds-component.adoc
+++ b/components/camel-jclouds/src/main/docs/jclouds-component.adoc
@@ -1,4 +1,4 @@
-# JClouds Component
+## JClouds Component
*Available as of Camel 2.9*
@@ -33,9 +33,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[jclouds-Configuringthecomponent]]
-Configuring the component
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring the component
The camel jclouds component will make use of multiple jclouds blobstores
and compute services as long as they are passed to the component during
@@ -84,9 +82,7 @@ As you can see the component is capable of handling multiple blobstores
and compute services. The actual implementation that will be used by
each endpoint is specified by passing the provider inside the URI.
-[[jclouds-Options]]
-Jclouds Options
-^^^^^^^^^^^^^^^
+### Jclouds Options
[source,java]
-----------------------------------------
@@ -100,9 +96,7 @@ target service (_e.g. aws-s3 or aws_ec2_).
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[jclouds-BlobstoreURIOptions]]
-Blobstore URI Options
-^^^^^^^^^^^^^^^^^^^^^
+### Blobstore URI Options
@@ -167,9 +161,7 @@ jclouds:blobstore:aws-s3?operation=CamelJcloudsGet&container=mycontainer&blobNam
For producer endpoint you can override all of the above URI options by
passing the appropriate headers to the message.
-[[jclouds-MessageHeadersforblobstore]]
-Message Headers for blobstore
-+++++++++++++++++++++++++++++
+#### Message Headers for blobstore
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -184,13 +176,9 @@ Message Headers for blobstore
|`CamelJcloudsBlobName` |The name of the blob.
|=======================================================================
-[[jclouds-BlobstoreUsageSamples]]
-Blobstore Usage Samples
-^^^^^^^^^^^^^^^^^^^^^^^
+### Blobstore Usage Samples
-[[jclouds-Example1:Puttingtotheblob]]
-Example 1: Putting to the blob
-++++++++++++++++++++++++++++++
+#### Example 1: Putting to the blob
This example will show you how you can store any message inside a blob
using the jclouds component.
@@ -217,9 +205,7 @@ route.
</route>
--------------------------------------------------------------------------------------------
-[[jclouds-Example2:GettingReadingfromablob]]
-Example 2: Getting/Reading from a blob
-++++++++++++++++++++++++++++++++++++++
+#### Example 2: Getting/Reading from a blob
This example will show you how you can read the contnet of a blob using
the jclouds component.
@@ -246,9 +232,7 @@ route.
</route>
--------------------------------------------------------------------------------------------
-[[jclouds-Example3:Consumingablob]]
-Example 3: Consuming a blob
-+++++++++++++++++++++++++++
+#### Example 3: Consuming a blob
This example will consume all blob that are under the specified
container. The generated exchange will contain the payload of the blob
@@ -278,16 +262,12 @@ You can achieve the same goal by using xml, as you can see below.
jclouds:compute:aws-ec2?operation=CamelJcloudsCreateNode&imageId=AMI_XXXXX&locationId=eu-west-1&group=mygroup
-------------------------------------------------------------------------------------------------------------
-[[jclouds-ComputeUsageSamples]]
-Compute Usage Samples
-^^^^^^^^^^^^^^^^^^^^^
+### Compute Usage Samples
Below are some examples that demonstrate the use of jclouds compute
producer in java dsl and spring/blueprint xml.
-[[jclouds-Example1:Listingtheavailableimages.]]
-Example 1: Listing the available images.
-++++++++++++++++++++++++++++++++++++++++
+#### Example 1: Listing the available images.
[source,java]
--------------------------------------------
@@ -307,9 +287,7 @@ its body. You can also do the same using xml.
</route>
--------------------------------------------------------------------------
-[[jclouds-Example2:Createanewnode.]]
-Example 2: Create a new node.
-+++++++++++++++++++++++++++++
+#### Example 2: Create a new node.
[source,java]
---------------------------------------------
@@ -334,9 +312,7 @@ spring xml.
</route>
-------------------------------------------------------------------------------------------------------------------------
-[[jclouds-Example3:Runashellscriptonrunningnode.]]
-Example 3: Run a shell script on running node.
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 3: Run a shell script on running node.
[source,java]
--------------------------------------------
@@ -369,9 +345,7 @@ Here is the same using spring xml.
</route>
----------------------------------------------------------------------------------------------
-[[jclouds-Seealso]]
-See also
-++++++++
+#### See also
If you want to find out more about jclouds here is list of interesting
resources
@@ -380,4 +354,4 @@ http://jclouds.incubator.apache.org/documentation/userguide/blobstore-guide/[Jcl
Blobstore wiki]
http://jclouds.incubator.apache.org/documentation/userguide/compute/[Jclouds
-Compute wiki]
+Compute wiki]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jcr/src/main/docs/jcr-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jcr/src/main/docs/jcr-component.adoc b/components/camel-jcr/src/main/docs/jcr-component.adoc
index 7f54eba..150546d 100644
--- a/components/camel-jcr/src/main/docs/jcr-component.adoc
+++ b/components/camel-jcr/src/main/docs/jcr-component.adoc
@@ -1,4 +1,4 @@
-# JCR Component
+## JCR Component
The *`jcr`* component allows you to add/read nodes to/from a JCR
compliant content repository (for example,
@@ -18,9 +18,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[JCR-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-------------------------------------------
@@ -32,16 +30,12 @@ jcr://user:password@repository/path/to/node
From *Camel 2.10* onwards you can use consumer as an EventListener in
JCR or a producer to read a node by identifier.
-[[JCR-Usage]]
-Usage
-^^^^^
+### Usage
The `repository` element of the URI is used to look up the JCR
`Repository` object in the Camel context registry.
-[[JCR-Options]]
-JCR Options
-+++++++++++
+#### JCR Options
// component options: START
@@ -86,9 +80,7 @@ message headers in Camel versions earlier than 2.12.3. See
https://issues.apache.org/jira/browse/CAMEL-7067[https://issues.apache.org/jira/browse/CAMEL-7067]
for more details.
-[[JCR-Example]]
-Example
-^^^^^^^
+### Example
The snippet below creates a node named `node` under the `/home/test`
node in the content repository. One additional property is added to the
@@ -117,12 +109,9 @@ all the children.
</route>
---------------------------------------------------------------------------------------------
-[[JCR-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-jdbc/src/main/docs/jdbc-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jdbc/src/main/docs/jdbc-component.adoc b/components/camel-jdbc/src/main/docs/jdbc-component.adoc
index 6219831..2a7849f 100644
--- a/components/camel-jdbc/src/main/docs/jdbc-component.adoc
+++ b/components/camel-jdbc/src/main/docs/jdbc-component.adoc
@@ -1,4 +1,4 @@
-# JDBC Component
+## JDBC Component
The *jdbc* component enables you to access databases through JDBC, where
SQL queries (SELECT) and operations (INSERT, UPDATE, etc) are sent in
@@ -22,9 +22,7 @@ for this component:
This component can only be used to define producer endpoints, which
means that you cannot use the JDBC component in a `from()` statement.
-[[JDBC-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------------
@@ -36,9 +34,7 @@ This component only supports producer endpoints.
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[JDBC-Options]]
-Options
-^^^^^^^
+### Options
@@ -89,9 +85,7 @@ The JDBC component supports 14 endpoint options which are listed below:
-[[JDBC-Result]]
-Result
-^^^^^^
+### Result
By default the result is returned in the OUT body as an
`ArrayList<HashMap<String, Object>>`. The `List` object contains the
@@ -102,9 +96,7 @@ the result.
*Note:* This component fetches `ResultSetMetaData` to be able to return
the column name as the key in the `Map`.
-[[JDBC-MessageHeaders]]
-Message Headers
-+++++++++++++++
+#### Message Headers
[width="100%",cols="10%,90%",options="header",]
|=======================================================================
@@ -128,9 +120,7 @@ type.
`useHeadersAsParameters` has been enabled.
|=======================================================================
-[[JDBC-Generatedkeys]]
-Generated keys
-^^^^^^^^^^^^^^
+### Generated keys
*Available as of Camel 2.10*
@@ -147,9 +137,7 @@ test].
Using generated keys does not work with together with named parameters.
-[[JDBC-Usingnamedparameters]]
-Using named parameters
-^^^^^^^^^^^^^^^^^^^^^^
+### Using named parameters
*Available as of Camel 2.12*
@@ -172,9 +160,7 @@ Notice in the example above we set two headers with constant value +
You can also store the header values in a `java.util.Map` and store the
map on the headers with the key `CamelJdbcParameters`.
-[[JDBC-Samples]]
-Samples
-^^^^^^^
+### Samples
In the following example, we fetch the rows from the customer table.
@@ -210,9 +196,7 @@ from("direct:hello")
.to("mock:result");
-------------------------------------------------------------------------------------------------
-[[JDBC-Sample-Pollingthedatabaseeveryminute]]
-Sample - Polling the database every minute
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sample - Polling the database every minute
If we want to poll a database using the JDBC component, we need to
combine it with a polling scheduler such as the link:timer.html[Timer]
@@ -224,9 +208,7 @@ data from the database every 60 seconds:
from("timer://foo?period=60000").setBody(constant("select * from customer")).to("jdbc:testdb").to("activemq:queue:customers");
------------------------------------------------------------------------------------------------------------------------------
-[[JDBC-Sample-MoveDataBetweenDataSources]]
-Sample - Move Data Between Data Sources +
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sample - Move Data Between Data Sources +
A common use case is to query for data, process it and move it to
another data source (ETL operations). In the following example, we
@@ -246,14 +228,11 @@ from("timer://MoveNewCustomersEveryHour?period=3600000")
�
-[[JDBC-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:sql.html[SQL]
-
+* link:sql.html[SQL]
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jetty9/src/main/docs/jetty-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jetty9/src/main/docs/jetty-component.adoc b/components/camel-jetty9/src/main/docs/jetty-component.adoc
index fc6ced7..8bc5d3b 100644
--- a/components/camel-jetty9/src/main/docs/jetty-component.adoc
+++ b/components/camel-jetty9/src/main/docs/jetty-component.adoc
@@ -1,4 +1,4 @@
-# Jetty 9 Component
+## Jetty 9 Component
The *jetty* component provides HTTP-based link:endpoint.html[endpoints]
for consuming and producing HTTP requests. That is, the Jetty component
@@ -31,9 +31,7 @@ for this component:
</dependency>
------------------------------------------------------------
-[[Jetty-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
----------------------------------------------------
@@ -43,9 +41,7 @@ jetty:http://hostname[:port][/resourceUri][?options]
You can append query options to the URI in the following format,
`?option=value&option=value&...`
-[[Jetty-Options]]
-Options
-^^^^^^^
+### Options
@@ -172,9 +168,7 @@ The Jetty 9 component supports 54 endpoint options which are listed below:
-[[Jetty-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
Camel uses the same message headers as the link:http.html[HTTP]
component.
@@ -190,17 +184,13 @@ header named `orderid` with the value 123.
Starting with Camel 2.2.0, you can get the request.parameter from the
message header not only from Get Method, but also other HTTP method.
-[[Jetty-Usage]]
-Usage
-^^^^^
+### Usage
The Jetty component supports both consumer and producer endpoints.
Another option for producing to other HTTP endpoints, is to use the
link:http.html[HTTP Component]
-[[Jetty-ProducerExample]]
-Producer Example
-^^^^^^^^^^^^^^^^
+### Producer Example
The following is a basic example of how to send an HTTP request to an
existing HTTP endpoint.
@@ -222,9 +212,7 @@ or in Spring XML
<route>
---------------------------------------------
-[[Jetty-ConsumerExample]]
-Consumer Example
-^^^^^^^^^^^^^^^^
+### Consumer Example
In this sample we define a route that exposes a HTTP service at
`http://localhost:8080/myapp/myservice`:
@@ -267,9 +255,7 @@ link:simple.html[Simple]�(such as link:el.html[EL] or
link:ognl.html[OGNL])�we could also test for the parameter value and do
routing based on the header value as well.
-[[Jetty-SessionSupport]]
-Session Support
-^^^^^^^^^^^^^^^
+### Session Support
The session support option, `sessionSupport`, can be used to enable a
`HttpSession` object and access the session object while processing the
@@ -302,9 +288,7 @@ public void process(Exchange exchange) throws Exception {
}
--------------------------------------------------------------------------------------
-[[Jetty-SSLSupport(HTTPS)]]
-SSL Support (HTTPS)
-^^^^^^^^^^^^^^^^^^^
+### SSL Support (HTTPS)
[[Jetty-UsingtheJSSEConfigurationUtility]]
Using the JSSE Configuration Utility
@@ -475,9 +459,7 @@ difference between the various Camel versions:
The value you use as keys in the above map is the port you configure
Jetty to listen on.
-[[Jetty-ConfiguringgeneralSSLproperties]]
-Configuring general SSL properties
-++++++++++++++++++++++++++++++++++
+#### Configuring general SSL properties
*Available as of Camel 2.5*
@@ -501,9 +483,7 @@ the port number as entry).
</bean>
-----------------------------------------------------------------------------
-[[Jetty-HowtoobtainreferencetotheX509Certificate]]
-How to obtain reference to the X509Certificate
-++++++++++++++++++++++++++++++++++++++++++++++
+#### How to obtain reference to the X509Certificate
Jetty stores a reference to the certificate in the HttpServletRequest
which you can access from code as follows:
@@ -514,9 +494,7 @@ HttpServletRequest req = exchange.getIn().getBody(HttpServletRequest.class);
X509Certificate cert = (X509Certificate) req.getAttribute("javax.servlet.request.X509Certificate")
--------------------------------------------------------------------------------------------------
-[[Jetty-ConfiguringgeneralHTTPproperties]]
-Configuring general HTTP properties
-+++++++++++++++++++++++++++++++++++
+#### Configuring general HTTP properties
*Available as of Camel 2.5*
@@ -537,9 +515,7 @@ the port number as entry).
</bean>
-----------------------------------------------------------------------------
-[[Jetty-ObtainingX-Forwarded-ForheaderwithHttpServletRequest.getRemoteAddr]]
-Obtaining X-Forwarded-For header with HttpServletRequest.getRemoteAddr()
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Obtaining X-Forwarded-For header with HttpServletRequest.getRemoteAddr()
If the HTTP requests are handled by an Apache server and forwarded to
jetty with mod_proxy, the original client IP address is in the
@@ -571,9 +547,7 @@ This is particularly useful when an existing Apache server handles TLS
connections for a domain and proxies them to application servers
internally.
-[[Jetty-DefaultbehaviorforreturningHTTPstatuscodes]]
-Default behavior for returning HTTP status codes
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Default behavior for returning HTTP status codes
The default behavior of HTTP status codes is defined by the
`org.apache.camel.component.http.DefaultHttpBinding` class, which
@@ -586,9 +560,7 @@ returned, and the stacktrace is returned in the body. If you want to
specify which HTTP status code to return, set the code in the
`Exchange.HTTP_RESPONSE_CODE` header of the OUT message.
-[[Jetty-CustomizingHttpBinding]]
-Customizing HttpBinding
-^^^^^^^^^^^^^^^^^^^^^^^
+### Customizing HttpBinding
By default, Camel uses the
`org.apache.camel.component.http.DefaultHttpBinding` to handle how a
@@ -614,9 +586,7 @@ And then we can reference this binding when we define the route:
<route><from uri="jetty:http://0.0.0.0:8080/myapp/myservice?httpBindingRef=mybinding"/><to uri="bean:doSomething"/></route>
---------------------------------------------------------------------------------------------------------------------------
-[[Jetty-Jettyhandlersandsecurityconfiguration]]
-Jetty handlers and security configuration
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Jetty handlers and security configuration
You can configure a list of Jetty handlers on the endpoint, which can be
useful for enabling advanced Jetty security features. These handlers are
@@ -686,9 +656,7 @@ from("jetty:http://0.0.0.0:9080/myservice?handlers=securityHandler")
If you need more handlers, set the `handlers` option equal to a
comma-separated list of bean IDs.
-[[Jetty-HowtoreturnacustomHTTP500replymessage]]
-How to return a custom HTTP 500 reply message
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to return a custom HTTP 500 reply message
You may want to return a custom reply message when something goes wrong,
instead of the default reply message Camel link:jetty.html[Jetty]
@@ -699,9 +667,7 @@ link:exception-clause.html[Exception Clause] to construct the custom
reply message. For example as show here, where we return
`Dude something went wrong` with HTTP error code 500:
-[[Jetty-Multi-partFormsupport]]
-Multi-part Form support
-^^^^^^^^^^^^^^^^^^^^^^^
+### Multi-part Form support
From Camel 2.3.0, camel-jetty support to multipart form post out of box.
The submitted form-data are mapped into the message header. Camel-jetty
@@ -713,9 +679,7 @@ of the attachment file name. You can find the example here.
earlier versions you receive the temporary file name for the attachment
instead*
-[[Jetty-JettyJMXsupport]]
-Jetty JMX support
-^^^^^^^^^^^^^^^^^
+### Jetty JMX support
From Camel 2.3.0, camel-jetty supports the enabling of Jetty's JMX
capabilities at the component and endpoint level with the endpoint
@@ -746,14 +710,11 @@ sharing the same MBeanServer between the instances, you can provide both
instances with a reference to the same MBeanContainer in order to avoid
name collisions when registering Jetty MBeans.
-[[Jetty-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: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-jgroups/src/main/docs/jgroups-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jgroups/src/main/docs/jgroups-component.adoc b/components/camel-jgroups/src/main/docs/jgroups-component.adoc
index d381aa2..384a3b3 100644
--- a/components/camel-jgroups/src/main/docs/jgroups-component.adoc
+++ b/components/camel-jgroups/src/main/docs/jgroups-component.adoc
@@ -1,4 +1,4 @@
-# JGroups Component
+## JGroups Component
*Available since Camel 2.10.0*
@@ -33,9 +33,7 @@ Camel *2.13.0* or higher, please use the following POM entry instead.
</dependency>
------------------------------------------------------------
-[[JGroups-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,java]
-----------------------------
@@ -45,9 +43,7 @@ jgroups:clusterName[?options]
Where *clusterName* represents the name of the JGroups cluster the
component should connect to.
-[[JGroups-Options]]
-Options
-^^^^^^^
+### Options
@@ -93,9 +89,7 @@ The JGroups component supports 7 endpoint options which are listed below:
-[[JGroups-Headers]]
-Headers
-^^^^^^^
+### Headers
[width="100%",cols="10%,10%,10%,70%",options="header",]
|=======================================================================
@@ -116,9 +110,7 @@ consumed message has been extracted.
endpoint.
|=======================================================================
�
-[[JGroups-Usage]]
-Usage
-^^^^^
+### Usage
Using `jgroups` component on the consumer side of the route will capture
messages received by the `JChannel` associated with the endpoint and
@@ -143,9 +135,7 @@ endpoint.
from("direct:start").to("jgroups:clusterName");
--------------------------------------------------
-[[JGroups-Predefinedfilters]]
-Predefined filters
-^^^^^^^^^^^^^^^^^^
+### Predefined filters
Starting from version *2.13.0* of Camel, JGroups component comes with
predefined filters factory class named `JGroupsFilters.`
@@ -168,9 +158,7 @@ from("jgroups:clusterName?enableViewMessages=true").
to("seda:masterNodeEventsQueue");
----------------------------------------------------------------------------------------
-[[JGroups-Predefinedexpressions]]
-Predefined expressions
-^^^^^^^^^^^^^^^^^^^^^^
+### Predefined expressions
Starting from version *2.13.0* of Camel, JGroups component comes with
predefined expressions factory class named `JGroupsExpressions.`
@@ -208,13 +196,9 @@ from("jgroups:clusterName?enableViewMessages=true").
from("timer://master?repeatCount=1").routeId("masterRoute").autoStartup(false).to(masterMockUri);�
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
-[[JGroups-Examples]]
-Examples
-^^^^^^^^
+### Examples
-[[JGroups-SendingreceivingmessagestofromtheJGroupscluster]]
-Sending (receiving) messages to (from) the JGroups cluster
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Sending (receiving) messages to (from) the JGroups cluster
In order to send message to the JGroups cluster use producer endpoint,
just as demonstrated on the snippet below.
@@ -240,9 +224,7 @@ from("jgroups:myCluster").to("mock:messagesFromTheCluster");
mockEndpoint.assertIsSatisfied();
------------------------------------------------------------
-[[JGroups-Receiveclusterviewchangenotifications]]
-Receive cluster view change notifications
-+++++++++++++++++++++++++++++++++++++++++
+#### Receive cluster view change notifications
The snippet below demonstrates how to create the consumer endpoint
listening to the�notifications regarding cluster membership changes. By
@@ -258,9 +240,7 @@ from("jgroups:clusterName?enableViewMessages=true").to(mockEndpoint);
mockEndpoint.assertIsSatisfied();
---------------------------------------------------------------------
-[[JGroups-Keepingsingletonroutewithinthecluster]]
-Keeping singleton route within the cluster
-++++++++++++++++++++++++++++++++++++++++++
+#### Keeping singleton route within the cluster
The snippet below demonstrates how to keep the singleton consumer route
in the cluster of Camel Contexts. As soon as the master node dies, one
@@ -281,4 +261,4 @@ from("jgroups:clusterName?enableViewMessages=true").
�to("controlbus:route?routeId=masterRoute&action=start&async=true");
from("jetty:http://localhost:8080/orders").routeId("masterRoute").autoStartup(false).to("jms:orders");�
------------------------------------------------------------------------------------------------------------------------------------------------------------------
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jibx/src/main/docs/jibx-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jibx/src/main/docs/jibx-dataformat.adoc b/components/camel-jibx/src/main/docs/jibx-dataformat.adoc
index ec98de0..a322bcb 100644
--- a/components/camel-jibx/src/main/docs/jibx-dataformat.adoc
+++ b/components/camel-jibx/src/main/docs/jibx-dataformat.adoc
@@ -1,4 +1,4 @@
-# JiBX DataFormat
+## JiBX DataFormat
*Available as of Camel 2.6*
@@ -26,9 +26,7 @@ from("mqseries:Another.Queue").
to("activemq:My.Queue");
-------------------------------------------
-[[JiBX-Options]]
-Options
-^^^^^^^
+### Options
// dataformat options: START
The JiBX dataformat supports 3 options which are listed below.
@@ -47,9 +45,7 @@ The JiBX dataformat supports 3 options which are listed below.
// dataformat options: END
-[[JiBX-JiBXSpringDSL]]
-JiBX Spring DSL
-^^^^^^^^^^^^^^^
+### JiBX Spring DSL
JiBX data format is also supported by Camel Spring DSL.
@@ -79,9 +75,7 @@ JiBX data format is also supported by Camel Spring DSL.
</camelContext>
--------------------------------------------------------------------------------------
-[[JiBX-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
To use JiBX in your camel routes you need to add the a dependency on
*camel-jibx* which implements this data format.
@@ -97,4 +91,4 @@ link:download.html[the download page for the latest versions]).
<artifactId>camel-jibx</artifactId>
<version>2.6.0</version>
</dependency>
--------------------------------------
+-------------------------------------
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jing/src/main/docs/jing-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jing/src/main/docs/jing-component.adoc b/components/camel-jing/src/main/docs/jing-component.adoc
index 2c4a649..8510f3e 100644
--- a/components/camel-jing/src/main/docs/jing-component.adoc
+++ b/components/camel-jing/src/main/docs/jing-component.adoc
@@ -1,4 +1,4 @@
-# Jing Component
+## Jing Component
The Jing component uses the
http://www.thaiopensource.com/relaxng/jing.html[Jing Library] to perform
@@ -24,9 +24,7 @@ for this component:
Note that the link:msv.html[MSV] component can also support RelaxNG XML
syntax.
-[[Jing-URIformatCamel2.16]]
-URI format Camel 2.16
-^^^^^^^^^^^^^^^^^^^^^
+### URI format Camel 2.16
[source,java]
------------------------------
@@ -36,9 +34,7 @@ jing:someLocalOrRemoteResource
From Camel 2.16 the component use jing as name, and you can use the
option compactSyntax to turn on either RNG or RNC mode.
-[[Jing-Options]]
-Options
-^^^^^^^
+### Options
// component options: START
@@ -64,9 +60,7 @@ The Jing component supports 3 endpoint options which are listed below:
-[[Jing-Example]]
-Example
-^^^^^^^
+### Example
The following
http://svn.apache.org/repos/asf/camel/trunk/components/camel-jing/src/test/resources/org/apache/camel/component/validator/jing/rnc-context.xml[example]
@@ -76,12 +70,9 @@ based on whether or not the XML matches the given
http://relaxng.org/compact-tutorial-20030326.html[RelaxNG Compact
Syntax] schema (which is supplied on the classpath).
-[[Jing-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-jira/src/main/docs/jira-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jira/src/main/docs/jira-component.adoc b/components/camel-jira/src/main/docs/jira-component.adoc
index 28abb51..7ca42ac 100644
--- a/components/camel-jira/src/main/docs/jira-component.adoc
+++ b/components/camel-jira/src/main/docs/jira-component.adoc
@@ -1,4 +1,4 @@
-# JIRA Component
+## JIRA Component
*Available as of Camel 2.15*
@@ -31,18 +31,14 @@ for this component:
</dependency>
---------------------------------------
-[[JIRA-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
[source,text]
-------------------------
jira://endpoint[?options]
-------------------------
-[[JIRA-Options:]]
-JIRA Options
-^^^^^^^^^^^^^
+### JIRA Options
// component options: START
@@ -75,9 +71,7 @@ The JIRA component supports 10 endpoint options which are listed below:
-[[JIRA-JQL:]]
-JQL:
-^^^^
+### JQL:
The JQL URI option is used by both consumer endpoints. �Theoretically,
items like "project key", etc. could be URI options themselves.
@@ -107,4 +101,4 @@ delay, etc. �Example:
[source,text]
----------------------------------------------------------------------------------------------------------------------------------------------
jira://[endpoint]?[required options]&jql=RAW(project=[project key] AND status in (Open, \"Coding In Progress\") AND \"Number of comments\">0)"
-----------------------------------------------------------------------------------------------------------------------------------------------
+----------------------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file