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 c81e5bb Fixed adoc indent level issues
c81e5bb is described below
commit c81e5bb43ae15be70db593365754d756aa9becc9
Author: Claus Ibsen <[email protected]>
AuthorDate: Tue Feb 5 07:50:39 2019 +0100
Fixed adoc indent level issues
---
components/camel-kura/src/main/docs/kura.adoc | 2 +-
components/camel-leveldb/src/main/docs/leveldb.adoc | 10 +++++-----
components/camel-script/src/main/docs/script.adoc | 16 +++-------------
components/camel-shiro/src/main/docs/shiro.adoc | 16 ++++++++--------
.../src/main/docs/spring-cloud.adoc | 2 +-
.../src/main/docs/spring-javaconfig.adoc | 6 +++---
.../camel-test-cdi/src/main/docs/test-cdi.adoc | 20 ++++++++++----------
components/camel-test/src/main/docs/test.adoc | 8 ++++----
8 files changed, 35 insertions(+), 45 deletions(-)
diff --git a/components/camel-kura/src/main/docs/kura.adoc
b/components/camel-kura/src/main/docs/kura.adoc
index f818f2e..fe61437 100644
--- a/components/camel-kura/src/main/docs/kura.adoc
+++ b/components/camel-kura/src/main/docs/kura.adoc
@@ -13,7 +13,7 @@ services and finally forward the current temperature value to
your data
center service using Camel EIP and components.
[[Kura-KuraRouteractivator]]
-==== KuraRouter activator
+=== KuraRouter activator
Bundles deployed to the Eclipse Kura are usually
http://eclipse.github.io/kura/doc/hello-example.html#create-java-class[developed
diff --git a/components/camel-leveldb/src/main/docs/leveldb.adoc
b/components/camel-leveldb/src/main/docs/leveldb.adoc
index c8ef295..df1866b 100644
--- a/components/camel-leveldb/src/main/docs/leveldb.adoc
+++ b/components/camel-leveldb/src/main/docs/leveldb.adoc
@@ -13,7 +13,7 @@ Current features it provides:
* LevelDBAggregationRepository
[[LevelDB-UsingLevelDBAggregationRepository]]
-==== Using LevelDBAggregationRepository
+=== Using LevelDBAggregationRepository
`LevelDBAggregationRepository` is an `AggregationRepository` which on
the fly persists the aggregated messages. This ensures that you will not
@@ -120,18 +120,18 @@
https://svn.apache.org/repos/asf/camel/trunk/components/camel-leveldb/src/test/j
test].
[[LevelDB-UsingLevelDBAggregationRepositoryinJavaDSL]]
-===== Using LevelDBAggregationRepository in Java DSL
+=== Using LevelDBAggregationRepository in Java DSL
In this example we want to persist aggregated messages in the
`target/data/leveldb.dat` file.
[[LevelDB-UsingLevelDBAggregationRepositoryinSpringXML]]
-===== Using LevelDBAggregationRepository in Spring XML
+=== Using LevelDBAggregationRepository in Spring XML
The same example but using Spring XML instead:
[[LevelDB-Dependencies]]
-==== Dependencies
+=== Dependencies
To use LevelDB in your camel routes you need to add
the a dependency on *camel-leveldb*.
@@ -150,7 +150,7 @@ the download page for the latest versions).
----------------------------------------
[[LevelDB-SeeAlso]]
-==== See Also
+=== See Also
* Configuring Camel
* Component
diff --git a/components/camel-script/src/main/docs/script.adoc
b/components/camel-script/src/main/docs/script.adoc
index 7aa0c14..021e6cc 100644
--- a/components/camel-script/src/main/docs/script.adoc
+++ b/components/camel-script/src/main/docs/script.adoc
@@ -14,7 +14,7 @@ return value should be used as a changed message body then
use Message Translator EIP instead.
[[Script-UsingfromJavaDSL]]
-==== Using from Java DSL
+=== Using from Java DSL
The route below will read the file contents and validate them against a
regular expression.
@@ -27,7 +27,7 @@ from("file://inbox")
---------------------------------------------------
[[Script-UsingfromSpringDSL]]
-==== Using from Spring DSL
+=== Using from Spring DSL
And from XML its easy as well
@@ -84,14 +84,4 @@ prefix the value with *resource:* as shown:
You can also refer to the script from the file system with file: instead
of classpath: such as file:/var/myscript.groovy
-
-
-[[Script-UsingThisPattern]]
-===== 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.
+
\ No newline at end of file
diff --git a/components/camel-shiro/src/main/docs/shiro.adoc
b/components/camel-shiro/src/main/docs/shiro.adoc
index 7a77ed4..7d777a6 100644
--- a/components/camel-shiro/src/main/docs/shiro.adoc
+++ b/components/camel-shiro/src/main/docs/shiro.adoc
@@ -37,7 +37,7 @@ for this component:
------------------------------------------------------------
[[ShiroSecurity-ShiroSecurityBasics]]
-==== Shiro Security Basics
+=== Shiro Security Basics
To employ Shiro security on a camel route, a ShiroSecurityPolicy object
must be instantiated with security configuration details (including
@@ -74,7 +74,7 @@ sec-level1 = zone1:readonly:*
------------------------------------------------------------------
[[ShiroSecurity-InstantiatingaShiroSecurityPolicyObject]]
-==== Instantiating a ShiroSecurityPolicy Object
+=== Instantiating a ShiroSecurityPolicy Object
A ShiroSecurityPolicy object is instantiated as follows
@@ -95,7 +95,7 @@ A ShiroSecurityPolicy object is instantiated as follows
----------------------------------------------------------------------------------------
[[ShiroSecurity-ShiroSecurityPolicyOptions]]
-==== ShiroSecurityPolicy Options
+=== ShiroSecurityPolicy Options
[width="100%",cols="10%,10%,10%,90%",options="header",]
|=======================================================================
@@ -144,7 +144,7 @@ require all of the roles to be met.
|=======================================================================
[[ShiroSecurity-ApplyingShiroAuthenticationonaCamelRoute]]
-==== Applying Shiro Authentication on a Camel Route
+=== Applying Shiro Authentication on a Camel Route
The ShiroSecurityPolicy, tests and permits incoming message exchanges
containing a encrypted SecurityToken in the Message Header to proceed
@@ -214,7 +214,7 @@ permission set, the request is not authorized to continue
any further.
-------------------------------------------------------------------------------------------
[[ShiroSecurity-CreatingaShiroSecurityTokenandinjectingitintoaMessageExchange]]
-==== Creating a ShiroSecurityToken and injecting it into a Message Exchange
+=== Creating a ShiroSecurityToken and injecting it into a Message Exchange
A ShiroSecurityToken object may be created and injected into a Message
Exchange using a Shiro Processor called ShiroSecurityTokenInjector. An
@@ -233,7 +233,7 @@ ShiroSecurityTokenInjector in the client is shown below
-------------------------------------------------------------------------------------
[[ShiroSecurity-SendingMessagestoroutessecuredbyaShiroSecurityPolicy]]
-==== Sending Messages to routes secured by a ShiroSecurityPolicy
+=== Sending Messages to routes secured by a ShiroSecurityPolicy
Messages and Message Exchanges sent along the camel route where the
security policy is applied need to be accompanied by a SecurityToken in
@@ -267,13 +267,13 @@ ProducerTemplate in Camel along with a SecurityToken
-------------------------------------------------------------------------------------------------
[[ShiroSecurity-SendingMessagestoroutessecuredbyaShiroSecurityPolicymucheasierfromCamel2.12onwards]]
-==== Sending Messages to routes secured by a ShiroSecurityPolicy (much easier
from Camel 2.12 onwards)
+=== Sending Messages to routes secured by a ShiroSecurityPolicy (much easier
from Camel 2.12 onwards)
From *Camel 2.12* onwards its even easier as you can provide the subject
in two different ways.
[[ShiroSecurity-UsingShiroSecurityToken]]
-===== Using ShiroSecurityToken
+=== Using ShiroSecurityToken
You can send a message to a Camel route with a header of key
`ShiroSecurityConstants.SHIRO_SECURITY_TOKEN` of the type
diff --git a/components/camel-spring-cloud/src/main/docs/spring-cloud.adoc
b/components/camel-spring-cloud/src/main/docs/spring-cloud.adoc
index adde971..10bebec 100644
--- a/components/camel-spring-cloud/src/main/docs/spring-cloud.adoc
+++ b/components/camel-spring-cloud/src/main/docs/spring-cloud.adoc
@@ -22,7 +22,7 @@ soon as you add that dependency into your classpath, Spring
Boot will
automatically auto-configure Camel for you.
[[SpringCloud-CamelSpringCloudStarter]]
-==== Camel Spring Cloud Starter
+=== Camel Spring Cloud Starter
*Available as of Camel 2.19*
diff --git
a/components/camel-spring-javaconfig/src/main/docs/spring-javaconfig.adoc
b/components/camel-spring-javaconfig/src/main/docs/spring-javaconfig.adoc
index 3daebcb..be18e71 100644
--- a/components/camel-spring-javaconfig/src/main/docs/spring-javaconfig.adoc
+++ b/components/camel-spring-javaconfig/src/main/docs/spring-javaconfig.adoc
@@ -10,7 +10,7 @@ You can use either the XML or Java config approaches with
Camel; its
your choice really on which you prefer.
[[SpringJavaConfig-UsingSpringJavaConfig]]
-==== Using Spring Java Config
+=== Using Spring Java Config
To use Spring Java Config in your Camel project the easiest thing to do
is add the following to your pom.xml
@@ -31,7 +31,7 @@ Note that this library is totally optional; you could just
wire Camel
together yourself with Java Config.
[[SpringJavaConfig-Configuration]]
-==== Configuration
+=== Configuration
The most common case of using JavaConfig with Camel would be to create
configuration with defined list of routes to be used by router.
@@ -67,7 +67,7 @@ public class MyRouteConfiguration extends CamelConfiguration {
--------------------------------------------------------------
[[SpringJavaConfig-Testing]]
-==== Testing
+=== Testing
Since *Camel 2.11.0* you can use the `CamelSpringJUnit4ClassRunner` with
`CamelSpringDelegatingTestContextLoader`. This is the recommended way to
diff --git a/components/camel-test-cdi/src/main/docs/test-cdi.adoc
b/components/camel-test-cdi/src/main/docs/test-cdi.adoc
index f79649e..aae3a9c 100644
--- a/components/camel-test-cdi/src/main/docs/test-cdi.adoc
+++ b/components/camel-test-cdi/src/main/docs/test-cdi.adoc
@@ -65,7 +65,7 @@ containers].
|=======================================================================
[[CDITesting-CamelCDITest]]
-==== Camel CDI Test
+=== Camel CDI Test
With this approach, your test classes use the JUnit runner provided in
Camel CDI test. This runner manages the lifecycle of a standalone CDI
@@ -201,7 +201,7 @@ public class CamelCdiTest {
----
[[CDITesting-Arquillian]]
-==== Arquillian
+=== Arquillian
With this approach, you use the JUnit runner or TestNG support provided
by Arquillian to delegate the bootstrap of the CDI container. You need
@@ -366,7 +366,7 @@ for a complete working example of testing a Camel CDI
application using
the REST DSL and deployed as a WAR in Jetty.
[[CDITesting-PAXExam]]
-==== PAX Exam
+=== PAX Exam
If you target OSGi as runtime environment for your Camel CDI
applications, you can use PAX Exam to automate the deployment of your
@@ -424,7 +424,7 @@ complete working example of testing a Camel CDI application
deployed in
an OSGi container using PAX Exam.
[[CDITesting-TestingPatterns]]
-==== Testing Patterns
+=== Testing Patterns
You can see the tests in the `camel-example-cdi-test` example for a
thorough overview of the following testing patterns for Camel CDI
@@ -435,7 +435,7 @@ module, they should equally work with Arquillian and PAX
Exam unless
otherwise stated or illustrated with a specific example.
[[CDITesting-Testroutes]]
-===== Test routes
+=== Test routes
You may want to add some Camel routes to your Camel CDI applications for
testing purpose. For example to route some exchanges to a `MockEndpoint`
@@ -482,7 +482,7 @@ public class CamelCdiTest {
----
[[CDITesting-Beanalternatives]]
-===== Bean alternatives
+=== Bean alternatives
You may want to replace a bean that is used in your Camel routes by
another bean for testing purpose, for example to mock it or change the
@@ -595,7 +595,7 @@ public class CamelCdiTest {
----
[[CDITesting-Camelcontextcustomization]]
-===== Camel context customization
+=== Camel context customization
You may need to customize your Camel contexts for testing purpose, for
example disabling JMX management to avoid TCP port allocation conflict.
@@ -625,7 +625,7 @@ class will be used during the test execution instead of the
default
Camel context bean provided by the Camel CDI component.
[[CDITesting-RoutesadvisingwithadviceWith]]
-===== Routes advising with `adviceWith`
+=== Routes advising with `adviceWith`
`AdviceWith` is used for testing Camel routes where you
can _advice_ an existing route before its being tested. It allows to
@@ -659,7 +659,7 @@ public class CamelCdiTest {
----
[[CDITesting-JUnitrules]]
-===== JUnit rules
+=== JUnit rules
Camel CDI test starts the CDI container after all the JUnit class rules
have executed.
@@ -727,7 +727,7 @@ public class CamelCdiTest {
----
[[CDITesting-SeeAlso]]
-==== See Also
+=== See Also
* CDI component
* http://arquillian.org[Arquillian Web site]
diff --git a/components/camel-test/src/main/docs/test.adoc
b/components/camel-test/src/main/docs/test.adoc
index ad5e5cc..5f2256d 100644
--- a/components/camel-test/src/main/docs/test.adoc
+++ b/components/camel-test/src/main/docs/test.adoc
@@ -39,7 +39,7 @@ From Camel 2.9 onwards the <<test-component,Test>> component
is provided
directly in the camel-core.
[[Test-URIformat]]
-==== URI format
+=== URI format
[source,java]
--------------------------------
@@ -51,7 +51,7 @@ Component URI that the expected message bodies are
pulled from before starting the test.
[[Test-URIOptions]]
-==== URI Options
+=== URI Options
[width="100%",cols="10%,10%,80%",options="header",]
|=======================================================================
@@ -75,7 +75,7 @@ expression.
|=======================================================================
[[Test-Example]]
-==== Example
+=== Example
For example, you could write a test case as follows:
@@ -93,7 +93,7 @@ To see how you can set other expectations on the test
endpoint, see the
<<mock-component,Mock>> component.
[[Test-SeeAlso]]
-==== See Also
+=== See Also
* Configuring Camel
* Component
