This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
     new 991c4d7  Regen docs
991c4d7 is described below

commit 991c4d7ba06e1eb3402bd6821ad9d4b153003b2f
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Sun Feb 4 16:08:26 2018 +0100

    Regen docs
---
 camel-core/src/main/docs/eips/aggregate-eip.adoc            | 5 ++---
 camel-core/src/main/docs/eips/batch-config-eip.adoc         | 3 ++-
 camel-core/src/main/docs/eips/bean-eip.adoc                 | 4 ++--
 camel-core/src/main/docs/eips/choice-eip.adoc               | 4 ++--
 camel-core/src/main/docs/eips/circuitBreaker-eip.adoc       | 4 ++--
 camel-core/src/main/docs/eips/convertBodyTo-eip.adoc        | 3 ++-
 camel-core/src/main/docs/eips/customLoadBalancer-eip.adoc   | 3 ++-
 camel-core/src/main/docs/eips/delay-eip.adoc                | 3 ++-
 camel-core/src/main/docs/eips/dynamicRouter-eip.adoc        | 4 ++--
 camel-core/src/main/docs/eips/enrich-eip.adoc               | 4 ++--
 camel-core/src/main/docs/eips/filter-eip.adoc               | 3 ++-
 camel-core/src/main/docs/eips/hystrix-eip.adoc              | 3 ++-
 camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc | 3 ++-
 camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc   | 3 ++-
 camel-core/src/main/docs/eips/loadBalance-eip.adoc          | 3 ++-
 camel-core/src/main/docs/eips/log-eip.adoc                  | 4 ++--
 camel-core/src/main/docs/eips/loop-eip.adoc                 | 4 ++--
 camel-core/src/main/docs/eips/random-eip.adoc               | 3 ++-
 camel-core/src/main/docs/eips/recipientList-eip.adoc        | 3 ++-
 camel-core/src/main/docs/eips/resequence-eip.adoc           | 4 ++--
 camel-core/src/main/docs/eips/routingSlip-eip.adoc          | 3 ++-
 camel-core/src/main/docs/eips/saga-eip.adoc                 | 3 ++-
 camel-core/src/main/docs/eips/sample-eip.adoc               | 4 ++--
 camel-core/src/main/docs/eips/script-eip.adoc               | 4 ++--
 camel-core/src/main/docs/eips/serviceCall-eip.adoc          | 3 ++-
 camel-core/src/main/docs/eips/sort-eip.adoc                 | 3 ++-
 camel-core/src/main/docs/eips/split-eip.adoc                | 4 ++--
 camel-core/src/main/docs/eips/stream-config-eip.adoc        | 3 ++-
 camel-core/src/main/docs/eips/throttle-eip.adoc             | 3 ++-
 camel-core/src/main/docs/eips/validate-eip.adoc             | 3 ++-
 camel-core/src/main/docs/eips/wireTap-eip.adoc              | 3 ++-
 31 files changed, 62 insertions(+), 44 deletions(-)

diff --git a/camel-core/src/main/docs/eips/aggregate-eip.adoc 
b/camel-core/src/main/docs/eips/aggregate-eip.adoc
index 59b8866..e484b9f 100644
--- a/camel-core/src/main/docs/eips/aggregate-eip.adoc
+++ b/camel-core/src/main/docs/eips/aggregate-eip.adoc
@@ -1,3 +1,4 @@
+[[aggregate-eip]]
 == Aggregate EIP
 
 The
@@ -656,6 +657,4 @@ public static final class MyUserAppender {
 
 Notice that the return type is a List which we want to contain the user
 names. The 1st parameter is the list of names, and then notice the 2nd
-parameter is the incoming `com.foo.User` type.
-
-
+parameter is the incoming `com.foo.User` type.
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/batch-config-eip.adoc 
b/camel-core/src/main/docs/eips/batch-config-eip.adoc
index 6dd7b42..47dc2cd 100644
--- a/camel-core/src/main/docs/eips/batch-config-eip.adoc
+++ b/camel-core/src/main/docs/eips/batch-config-eip.adoc
@@ -1,3 +1,4 @@
+[[batch-config-eip]]
 == Batch-config EIP
 
 
@@ -14,4 +15,4 @@ The Batch-config EIP supports 5 options which are listed 
below:
 | *reverse* | Whether to reverse the ordering. | false | Boolean
 | *ignoreInvalidExchanges* | Whether to ignore invalid exchanges | false | 
Boolean
 |===
-// eip options: END
+// eip options: END
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/bean-eip.adoc 
b/camel-core/src/main/docs/eips/bean-eip.adoc
index 54d298a..18f1ca2 100644
--- a/camel-core/src/main/docs/eips/bean-eip.adoc
+++ b/camel-core/src/main/docs/eips/bean-eip.adoc
@@ -1,3 +1,4 @@
+[[bean-eip]]
 == Bean EIP
 
 The *bean:* EIP binds beans to Camel message exchanges.
@@ -87,5 +88,4 @@ mechanisms in Camel.
 
 * 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
diff --git a/camel-core/src/main/docs/eips/choice-eip.adoc 
b/camel-core/src/main/docs/eips/choice-eip.adoc
index 26ab08d..c8da828 100644
--- a/camel-core/src/main/docs/eips/choice-eip.adoc
+++ b/camel-core/src/main/docs/eips/choice-eip.adoc
@@ -1,3 +1,4 @@
+[[choice-eip]]
 == Choice EIP
 
 The
@@ -70,5 +71,4 @@ And the same example using XML:
         </choice>
     </route>
 </camelContext>
-----
-
+----
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/circuitBreaker-eip.adoc 
b/camel-core/src/main/docs/eips/circuitBreaker-eip.adoc
index afa4e8b..d50f185 100644
--- a/camel-core/src/main/docs/eips/circuitBreaker-eip.adoc
+++ b/camel-core/src/main/docs/eips/circuitBreaker-eip.adoc
@@ -1,3 +1,4 @@
+[[circuitBreaker-eip]]
 == Circuit Breaker EIP (deprecated)
 
 The Circuit Breaker load balancer is a stateful pattern that monitors all 
calls for certain exceptions. Initially the Circuit Breaker is in closed state 
and passes all messages. If there are failures and the threshold is reached, it 
moves to open state and rejects all calls until halfOpenAfter timeout is 
reached. After this timeout is reached, if there is a new call, it will pass 
and if the result is success the Circuit Breaker will move to closed state, or 
to open state if there was an error.
@@ -50,5 +51,4 @@ And the same example using Spring XML:
         </loadBalance>
     </route>
 </camelContext>
-----
-
+----
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/convertBodyTo-eip.adoc 
b/camel-core/src/main/docs/eips/convertBodyTo-eip.adoc
index fb9f43c..4389938 100644
--- a/camel-core/src/main/docs/eips/convertBodyTo-eip.adoc
+++ b/camel-core/src/main/docs/eips/convertBodyTo-eip.adoc
@@ -1,3 +1,4 @@
+[[convertBodyTo-eip]]
 == Convert Body To EIP
 
 
@@ -11,4 +12,4 @@ The Convert Body To EIP supports 2 options which are listed 
below:
 | *type* | *Required* The java type to convert to |  | String
 | *charset* | To use a specific charset when converting |  | String
 |===
-// eip options: END
+// eip options: END
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/customLoadBalancer-eip.adoc 
b/camel-core/src/main/docs/eips/customLoadBalancer-eip.adoc
index 89b2b0a..beca447 100644
--- a/camel-core/src/main/docs/eips/customLoadBalancer-eip.adoc
+++ b/camel-core/src/main/docs/eips/customLoadBalancer-eip.adoc
@@ -1,3 +1,4 @@
+[[customLoadBalancer-eip]]
 == Custom Load Balancer EIP
 
 You can use a custom load balancer (eg your own implementation) also.
@@ -78,4 +79,4 @@ public static class MyLoadBalancer extends 
LoadBalancerSupport {
         return true;
     }
 }
-----
+----
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/delay-eip.adoc 
b/camel-core/src/main/docs/eips/delay-eip.adoc
index e53a137..47fcb08 100644
--- a/camel-core/src/main/docs/eips/delay-eip.adoc
+++ b/camel-core/src/main/docs/eips/delay-eip.adoc
@@ -1,3 +1,4 @@
+[[delay-eip]]
 == Delay EIP
 The Delayer Pattern allows you to delay the delivery of messages to some 
destination.
 
@@ -175,4 +176,4 @@ public class SomeBean {
 
 === See Also
 
-- Delay Interceptor
+- Delay Interceptor
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/dynamicRouter-eip.adoc 
b/camel-core/src/main/docs/eips/dynamicRouter-eip.adoc
index 8aca048..e0535cb 100644
--- a/camel-core/src/main/docs/eips/dynamicRouter-eip.adoc
+++ b/camel-core/src/main/docs/eips/dynamicRouter-eip.adoc
@@ -1,3 +1,4 @@
+[[dynamicRouter-eip]]
 == Dynamic Router EIP
 
 The 
link:http://www.enterpriseintegrationpatterns.com/DynamicRouter.html[Dynamic 
Router] from the link:../../../../readme-eip.adoc[EIP patterns] allows you to 
route messages while avoiding the dependency of the router on all possible 
destinations while maintaining its efficiency.
@@ -157,5 +158,4 @@ public class MyDynamicRouter {
         // return the next endpoint uri, where to go. Return null to indicate 
the end.
     }
 }
-----
-
+----
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/enrich-eip.adoc 
b/camel-core/src/main/docs/eips/enrich-eip.adoc
index a93e811..e705d2b 100644
--- a/camel-core/src/main/docs/eips/enrich-eip.adoc
+++ b/camel-core/src/main/docs/eips/enrich-eip.adoc
@@ -1,3 +1,4 @@
+[[enrich-eip]]
 == Enrich EIP
 
 Camel supports the Content Enricher from the EIP patterns using a Message 
Translator, an arbitrary Processor in the routing logic, or using the enrich 
DSL element to enrich the message.
@@ -365,5 +366,4 @@ And in XML DSL
   </pollEnrich>
   <to uri="direct:result"/>
 </route>
-----
-
+----
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/filter-eip.adoc 
b/camel-core/src/main/docs/eips/filter-eip.adoc
index c4db1ab..351e583 100644
--- a/camel-core/src/main/docs/eips/filter-eip.adoc
+++ b/camel-core/src/main/docs/eips/filter-eip.adoc
@@ -1,3 +1,4 @@
+[[filter-eip]]
 == Filter EIP
 
 The http://www.enterpriseintegrationpatterns.com/Filter.html[Message
@@ -98,4 +99,4 @@ link:predicate.html[Predicate] matches (value set to `true`), 
and to the
 steps immediately following the link:message-filter.html[Message Filter]
 with the value set based on the results of the last
 link:message-filter.html[Message Filter] link:predicate.html[Predicate]
-evaluated.
+evaluated.
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/hystrix-eip.adoc 
b/camel-core/src/main/docs/eips/hystrix-eip.adoc
index cac9da1..3cfd897 100644
--- a/camel-core/src/main/docs/eips/hystrix-eip.adoc
+++ b/camel-core/src/main/docs/eips/hystrix-eip.adoc
@@ -1,3 +1,4 @@
+[[hystrix-eip]]
 == Hystrix EIP
 
 Available as of Camel 2.18
@@ -132,4 +133,4 @@ You can also configure Hystrix globally and then refer to 
that configuration:
 
 === Other examples
 
-You can find an example with the source code: 
link:https://github.com/apache/camel/tree/master/examples/camel-example-hystrix[camel-example-hystrix].
+You can find an example with the source code: 
link:https://github.com/apache/camel/tree/master/examples/camel-example-hystrix[camel-example-hystrix].
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc 
b/camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc
index 3963833..7a04bd8 100644
--- a/camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc
+++ b/camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc
@@ -1,3 +1,4 @@
+[[hystrixConfiguration-eip]]
 == Hystrix Configuration EIP
 
 
@@ -40,4 +41,4 @@ The Hystrix Configuration EIP supports 31 options which are 
listed below:
 | *threadPoolRollingNumber StatisticalWindowBuckets* | Number of buckets the 
rolling statistical window is broken into. This is passed into 
HystrixRollingNumber inside each HystrixThreadPoolMetrics instance. | 10 | 
Integer
 | *allowMaximumSizeToDiverge FromCoreSize* | Allows the configuration for 
maximumSize to take effect. That value can then be equal to or higher than 
coreSize | false | Boolean
 |===
-// eip options: END
+// eip options: END
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc 
b/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
index d4eea3e..f5cb3f4 100644
--- a/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
+++ b/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
@@ -1,3 +1,4 @@
+[[idempotentConsumer-eip]]
 == Idempotent Consumer EIP
 
 The
@@ -49,4 +50,4 @@ The Idempotent Consumer EIP supports 5 options which are 
listed below:
 | *skipDuplicate* | Sets whether to skip duplicates or not. The default 
behavior is to skip duplicates. A duplicate message would have the Exchange 
property link org.apache.camel.ExchangeDUPLICATE_MESSAGE set to a link 
BooleanTRUE value. A none duplicate message will not have this property set. | 
true | Boolean
 | *removeOnFailure* | Sets whether to remove or keep the key on failure. The 
default behavior is to remove the key on failure. | true | Boolean
 |===
-// eip options: END
+// eip options: END
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/loadBalance-eip.adoc 
b/camel-core/src/main/docs/eips/loadBalance-eip.adoc
index ca3f174..871c9b5 100644
--- a/camel-core/src/main/docs/eips/loadBalance-eip.adoc
+++ b/camel-core/src/main/docs/eips/loadBalance-eip.adoc
@@ -1,3 +1,4 @@
+[[loadBalance-eip]]
 == Load Balance EIP
 
 The Load Balancer Pattern allows you to delegate to one of a number of 
endpoints using a variety of different load balancing policies.
@@ -243,4 +244,4 @@ And the same example using Spring XML:
       <to uri="mock:z"/>
   </loadBalance>
 </route>
-----
+----
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/log-eip.adoc 
b/camel-core/src/main/docs/eips/log-eip.adoc
index 153229f..3756f79 100644
--- a/camel-core/src/main/docs/eips/log-eip.adoc
+++ b/camel-core/src/main/docs/eips/log-eip.adoc
@@ -1,3 +1,4 @@
+[[log-eip]]
 == Log EIP
 
 How can I log the processing of a link:message.html[Message]?
@@ -200,5 +201,4 @@ And in XML:
 
 `org.apache.camel.processor.DefaultMaskingFormatter` is used for the masking 
by default.
 If you want to use a custom masking formatter, put it into registry with the 
name `CamelCustomLogMask`.
-Note that the masking formatter must implement 
`org.apache.camel.spi.MaskingFormatter`.
-
+Note that the masking formatter must implement 
`org.apache.camel.spi.MaskingFormatter`.
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/loop-eip.adoc 
b/camel-core/src/main/docs/eips/loop-eip.adoc
index 6a80cd2..7abee7f 100644
--- a/camel-core/src/main/docs/eips/loop-eip.adoc
+++ b/camel-core/src/main/docs/eips/loop-eip.adoc
@@ -1,3 +1,4 @@
+[[loop-eip]]
 == Loop EIP
 
 The Loop allows for processing a message a number of times, possibly in a 
different way for each iteration. Useful mostly during testing.
@@ -169,5 +170,4 @@ And the same example in XML:
 </route>
 ----
 
-Notice in XML that the while loop is turned on using the *doWhile* attribute.
-
+Notice in XML that the while loop is turned on using the *doWhile* attribute.
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/random-eip.adoc 
b/camel-core/src/main/docs/eips/random-eip.adoc
index 597bac0..a24cf64 100644
--- a/camel-core/src/main/docs/eips/random-eip.adoc
+++ b/camel-core/src/main/docs/eips/random-eip.adoc
@@ -1,6 +1,7 @@
+[[random-eip]]
 == Random EIP
 
 
 // eip options: START
 The Random EIP supports 0 options which are listed below:
-// eip options: END
+// eip options: END
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/recipientList-eip.adoc 
b/camel-core/src/main/docs/eips/recipientList-eip.adoc
index c2dac10..9382324 100644
--- a/camel-core/src/main/docs/eips/recipientList-eip.adoc
+++ b/camel-core/src/main/docs/eips/recipientList-eip.adoc
@@ -1,3 +1,4 @@
+[[recipientList-eip]]
 == Recipient List EIP
 The 
link:http://www.enterpriseintegrationpatterns.com/RecipientList.html[Recipient 
List] from the EIP patterns allows you to route messages to a number of 
dynamically specified recipients.
 
@@ -372,4 +373,4 @@ be `InOnly` when the message is routed to the `file:outbox 
endpoint`.
 If you want to alter the exchange pattern permanently then use the 
`.setExchangePattern` option.
 
 See more details at Request Reply and Event Message EIPs.
-====
+====
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/resequence-eip.adoc 
b/camel-core/src/main/docs/eips/resequence-eip.adoc
index 69a52d7..a456aea 100644
--- a/camel-core/src/main/docs/eips/resequence-eip.adoc
+++ b/camel-core/src/main/docs/eips/resequence-eip.adoc
@@ -1,3 +1,4 @@
+[[resequence-eip]]
 == Resequence EIP
 
 The 
link:http://www.enterpriseintegrationpatterns.com/Resequencer.html[Resequencer] 
from the link:https://camel.apache.org/enterprise-integration-patterns.html[EIP 
patterns] allows you to reorganise messages based on some comparator. +
@@ -240,5 +241,4 @@ And an example in XML
     </resequence>
   </route>
 </camelContext>
-----
-
+----
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/routingSlip-eip.adoc 
b/camel-core/src/main/docs/eips/routingSlip-eip.adoc
index ed20268..4115457 100644
--- a/camel-core/src/main/docs/eips/routingSlip-eip.adoc
+++ b/camel-core/src/main/docs/eips/routingSlip-eip.adoc
@@ -1,3 +1,4 @@
+[[routingSlip-eip]]
 == Routing Slip EIP
 The Routing Slip from the 
link:https://camel.apache.org/enterprise-integration-patterns.html[EIP 
patterns] allows you to route a message consecutively through a series of 
processing steps where the sequence of steps is not known at design time and 
can vary for each message.
 
@@ -110,4 +111,4 @@ And in Spring XML its an attribute on the recipient list 
tag.
 For further examples of this pattern in use you could look at the routing slip 
test cases.
 
 === Using This Pattern
-If you would like to use this EIP Pattern then please read the Getting 
Started, you may also find the Architecture useful particularly the description 
of Endpoint and URIs. Then you could try out some of the Examples first before 
trying this pattern out.
+If you would like to use this EIP Pattern then please read the Getting 
Started, you may also find the Architecture useful particularly the description 
of Endpoint and URIs. Then you could try out some of the Examples first before 
trying this pattern out.
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/saga-eip.adoc 
b/camel-core/src/main/docs/eips/saga-eip.adoc
index 935baed..db7ade9 100644
--- a/camel-core/src/main/docs/eips/saga-eip.adoc
+++ b/camel-core/src/main/docs/eips/saga-eip.adoc
@@ -1,3 +1,4 @@
+[[saga-eip]]
 == Saga EIP
 
 *Available as of Camel 2.21*
@@ -447,4 +448,4 @@ The following snipped shows an example:
   <to uri="direct:action1" />
   <to uri="direct:action2" />
 </route>
-----
+----
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/sample-eip.adoc 
b/camel-core/src/main/docs/eips/sample-eip.adoc
index 10787cb..8b3dd80 100644
--- a/camel-core/src/main/docs/eips/sample-eip.adoc
+++ b/camel-core/src/main/docs/eips/sample-eip.adoc
@@ -1,3 +1,4 @@
+[[sample-eip]]
 == Sample EIP
 *Available as of Camel 2.1*
 
@@ -82,5 +83,4 @@ And since it uses a default of 1 second you can omit this 
configuration in case
         <to uri="mock:result"/>
     </sample>
 </route>
-----
-
+----
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/script-eip.adoc 
b/camel-core/src/main/docs/eips/script-eip.adoc
index 8f08f25..abe4e92 100644
--- a/camel-core/src/main/docs/eips/script-eip.adoc
+++ b/camel-core/src/main/docs/eips/script-eip.adoc
@@ -1,3 +1,4 @@
+[[script-eip]]
 == Script EIP
 *Available as of Camel 2.16*
 
@@ -72,5 +73,4 @@ For example to load a groovy script from the classpath you 
need to prefix the va
 ----
 
 You can also refer to the script from the file system with `file:` instead of 
`classpath:`
-such as `file:/var/myscript.groovy`
-
+such as `file:/var/myscript.groovy`
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/serviceCall-eip.adoc 
b/camel-core/src/main/docs/eips/serviceCall-eip.adoc
index b904604..735ff29 100644
--- a/camel-core/src/main/docs/eips/serviceCall-eip.adoc
+++ b/camel-core/src/main/docs/eips/serviceCall-eip.adoc
@@ -1,3 +1,4 @@
+[[serviceCall-eip]]
 == Service Call EIP
 *Available as of Camel 2.18*
 
@@ -608,4 +609,4 @@ If you are using Camel in an application based on Spring 
Cloud, you can leverage
     <!-- use the same version as your Camel core version -->
     <version>x.y.z</version>
 </dependency>
-----
+----
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/sort-eip.adoc 
b/camel-core/src/main/docs/eips/sort-eip.adoc
index f6ce6a5..b435a4c 100644
--- a/camel-core/src/main/docs/eips/sort-eip.adoc
+++ b/camel-core/src/main/docs/eips/sort-eip.adoc
@@ -1,3 +1,4 @@
+[[sort-eip]]
 == Sort EIP
 
 Sort can be used to sort a message. Imagine you consume text files and before 
processing each file you want to be sure the content is sorted.
@@ -66,4 +67,4 @@ And to use our own comparator we can refer to it as a spring 
bean:
 <bean id="myReverseComparator" class="com.mycompany.MyReverseComparator"/>
 ----
 
-Besides `<simple>`, you can supply an expression using any language you like, 
so long as it returns a list.
+Besides `<simple>`, you can supply an expression using any language you like, 
so long as it returns a list.
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/split-eip.adoc 
b/camel-core/src/main/docs/eips/split-eip.adoc
index c49ef55..5735ef3 100644
--- a/camel-core/src/main/docs/eips/split-eip.adoc
+++ b/camel-core/src/main/docs/eips/split-eip.adoc
@@ -1,3 +1,4 @@
+[[split-eip]]
 == Split EIP
 
 The 
link:http://www.enterpriseintegrationpatterns.com/patterns/messaging/Sequencer.html[Splitter]
 from the link:enterprise-integration-patterns.html[EIP patterns] allows you 
split a message into a number of pieces and process them individually.
@@ -684,5 +685,4 @@ Using this from XML DSL is just as easy as you just have to 
set the `shareUnitOf
 .Implementation of shared unit of work
 ====
 So in reality the unit of work is not shared as a single object instance. 
Instead `SubUnitOfWork` is attached to their parent, and issues callback to the 
parent about their status (commit or rollback). This may be refactored in Camel 
3.0 where larger API changes can be done.
-====
-
+====
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/stream-config-eip.adoc 
b/camel-core/src/main/docs/eips/stream-config-eip.adoc
index 53cdd07..23ffa7e 100644
--- a/camel-core/src/main/docs/eips/stream-config-eip.adoc
+++ b/camel-core/src/main/docs/eips/stream-config-eip.adoc
@@ -1,3 +1,4 @@
+[[stream-config-eip]]
 == Stream-config EIP
 
 
@@ -15,4 +16,4 @@ The Stream-config EIP supports 6 options which are listed 
below:
 | *comparatorRef* | To use a custom comparator |  | String
 | *rejectOld* | If true throws an exception when messages older than the last 
delivered message are processed | false | Boolean
 |===
-// eip options: END
+// eip options: END
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/throttle-eip.adoc 
b/camel-core/src/main/docs/eips/throttle-eip.adoc
index b9d3d4c..3c2be63 100644
--- a/camel-core/src/main/docs/eips/throttle-eip.adoc
+++ b/camel-core/src/main/docs/eips/throttle-eip.adoc
@@ -1,3 +1,4 @@
+[[throttle-eip]]
 == Throttle EIP
 
 The Throttler Pattern allows you to ensure that a specific endpoint does not 
get overloaded, or that we don't exceed an agreed SLA with some external 
service.
@@ -80,4 +81,4 @@ You can let the Throttler use non blocking asynchronous 
delaying, which means Ca
 from("seda:a")
   .throttle(100).asyncDelayed()
   .to("seda:b");
----------------------
+---------------------
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/validate-eip.adoc 
b/camel-core/src/main/docs/eips/validate-eip.adoc
index cd3cb2c..a782636 100644
--- a/camel-core/src/main/docs/eips/validate-eip.adoc
+++ b/camel-core/src/main/docs/eips/validate-eip.adoc
@@ -1,3 +1,4 @@
+[[validate-eip]]
 == Validate EIP
 *Available as of Camel 2.3* +
 
@@ -70,4 +71,4 @@ The XML DSL to validate the message header would looks like 
this:
 </route>
 
 <bean id="myServiceBean" class="com.mycompany.MyServiceBean"/>
-----
+----
\ No newline at end of file
diff --git a/camel-core/src/main/docs/eips/wireTap-eip.adoc 
b/camel-core/src/main/docs/eips/wireTap-eip.adoc
index 56ec216..1c1b5d8 100644
--- a/camel-core/src/main/docs/eips/wireTap-eip.adoc
+++ b/camel-core/src/main/docs/eips/wireTap-eip.adoc
@@ -1,3 +1,4 @@
+[[wireTap-eip]]
 == Wire Tap EIP
 
 http://www.enterpriseintegrationpatterns.com/WireTap.html[Wire Tap]
@@ -210,4 +211,4 @@ The following example sends a new message which has
 
 See details at link:multicast.html[Multicast]
 
-link:using-this-pattern.html[Using This Pattern]
+link:using-this-pattern.html[Using This Pattern]
\ No newline at end of file

-- 
To stop receiving notification emails like this one, please contact
davscl...@apache.org.

Reply via email to