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

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-spring-boot.git


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

commit 01a074b7ed37f26fa3a4ed1c69afce9dae55e500
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Wed Sep 16 14:59:56 2020 +0200

    Regen
---
 core/camel-spring-boot/src/main/docs/spring-boot.adoc | 16 ++++++++--------
 docs/modules/ROOT/pages/spring-boot.adoc              | 18 +++++++++---------
 2 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/core/camel-spring-boot/src/main/docs/spring-boot.adoc 
b/core/camel-spring-boot/src/main/docs/spring-boot.adoc
index 4685be6..6b43056 100644
--- a/core/camel-spring-boot/src/main/docs/spring-boot.adoc
+++ b/core/camel-spring-boot/src/main/docs/spring-boot.adoc
@@ -176,13 +176,13 @@ The component supports 157 options, which are listed 
below.
 | *camel.springboot.jmx-enabled* | Enable JMX in your Camel application. | 
true | Boolean
 | *camel.springboot.jmx-management-name-pattern* | The naming pattern for 
creating the CamelContext JMX management name. The default pattern is #name# | 
#name# | String
 | *camel.springboot.jmx-management-statistics-level* | Sets the JMX statistics 
level The level can be set to Extended to gather additional information The 
default value is Default. |  | ManagementStatisticsLevel
-| *camel.springboot.lightweight* | Experimental: Configure the context to be 
lightweight. This will trigger some optimizations and memory reduction options. 
Lightweight context have some limitations. At this moment, dynamic endpoint 
destinations are not supported. | false | Boolean
+| *camel.springboot.lightweight* | Experimental: Configure the context to be 
lightweight. This will trigger some optimizations and memory reduction options. 
Lightweight context has some limitations. At this moment, dynamic endpoint 
destinations are not supported. | false | Boolean
 | *camel.springboot.load-type-converters* | Whether to load custom type 
converters by scanning classpath. This is used for backwards compatibility with 
Camel 2.x. Its recommended to migrate to use fast type converter loading by 
setting <tt>@Converter(generateLoader = true)</tt> on your custom type 
converter classes. | true | Boolean
 | *camel.springboot.log-debug-max-chars* | Is used to limit the maximum length 
of the logging Camel message bodies. If the message body is longer than the 
limit, the log message is clipped. Use -1 to have unlimited length. Use for 
example 1000 to log at most 1000 characters. | 0 | Integer
 | *camel.springboot.log-exhausted-message-body* | Sets whether to log 
exhausted message body with message history. Default is false. | false | Boolean
 | *camel.springboot.log-mask* | Sets whether log mask is enabled or not. 
Default is false. | false | Boolean
 | *camel.springboot.main-run-controller* | Whether to use the main run 
controller to ensure the Spring-Boot application keeps running until being 
stopped or the JVM terminated. You typically only need this if you run 
Spring-Boot standalone. If you run Spring-Boot with spring-boot-starter-web 
then the web container keeps the JVM running. | false | Boolean
-| *camel.springboot.mdc-logging-keys-pattern* | Sets the pattern used for 
determine which custom MDC keys to propagate during message routing when the 
routing engine continues routing asynchronously for the given message. Setting 
this pattern to * will propagate all custom keys. Or setting the pattern to 
foo*,bar* will propagate any keys starting with either foo or bar. Notice that 
a set of standard Camel MDC keys are always propagated which starts with camel. 
as key name. The match rule [...]
+| *camel.springboot.mdc-logging-keys-pattern* | Sets the pattern used for 
determining which custom MDC keys to propagate during message routing when the 
routing engine continues routing asynchronously for the given message. Setting 
this pattern to * will propagate all custom keys. Or setting the pattern to 
foo*,bar* will propagate any keys starting with either foo or bar. Notice that 
a set of standard Camel MDC keys are always propagated which starts with camel. 
as key name. The match ru [...]
 | *camel.springboot.message-history* | Sets whether message history is enabled 
or not. Default is true. | true | Boolean
 | *camel.springboot.name* | Sets the name of the CamelContext. |  | String
 | *camel.springboot.producer-template-cache-size* | Producer template 
endpoints cache size. | 1000 | Integer
@@ -195,11 +195,11 @@ The component supports 157 options, which are listed 
below.
 | *camel.springboot.route-controller-include-routes* | Pattern for filtering 
routes to be excluded as supervised. The pattern is matching on route id, and 
endpoint uri for the route. Multiple patterns can be separated by comma. For 
example to exclude all JMS routes, you can say <tt>jms:*</tt>. And to exclude 
routes with specific route ids <tt>mySpecialRoute,myOtherSpecialRoute</tt>. The 
pattern supports wildcards and uses the matcher from 
org.apache.camel.support.PatternHelper#matchPatte [...]
 | *camel.springboot.route-controller-initial-delay* | Initial delay in milli 
seconds before the route controller starts, after CamelContext has been 
started. | 0 | Long
 | *camel.springboot.route-controller-route-startup-logging-level* | Sets the 
logging level used for logging route startup activity. By default INFO level is 
used. You can use this to change the level for example to OFF if this kind of 
logging is not wanted. |  | LoggingLevel
-| *camel.springboot.route-controller-supervise-enabled* | To enable using 
supervising route controller which allows Camel to startup and then the 
controller takes care of starting the routes in a safe manner. This can be used 
when you want to startup Camel despite a route may otherwise fail fast during 
startup and cause Camel to fail to startup as well. By delegating the route 
startup to the supervising route controller then its manages the startup using 
a background thread. The controll [...]
+| *camel.springboot.route-controller-supervise-enabled* | To enable using 
supervising route controller which allows Camel to startup and then the 
controller takes care of starting the routes in a safe manner. This can be used 
when you want to startup Camel despite a route may otherwise fail fast during 
startup and cause Camel to fail to startup as well. By delegating the route 
startup to the supervising route controller then it manages the startup using a 
background thread. The controlle [...]
 | *camel.springboot.route-controller-thread-pool-size* | The number of threads 
used by the route controller scheduled thread pool that are used for restarting 
routes. The pool uses 1 thread by default, but you can increase this to allow 
the controller to concurrently attempt to restart multiple routes in case more 
than one route has problems starting. | 1 | Integer
 | *camel.springboot.route-controller-unhealthy-on-exhausted* | Whether to mark 
the route as unhealthy (down) when all restarting attempts (backoff) have 
failed and the route is not successfully started and the route manager is 
giving up. Setting this to true allows health checks to know about this and can 
report the Camel application as DOWN. The default is false. | false | Boolean
 | *camel.springboot.route-filter-exclude-pattern* | Used for filtering routes 
routes matching the given pattern, which follows the following rules: - Match 
by route id - Match by route input endpoint uri The matching is using exact 
match, by wildcard and regular expression. For example to only include routes 
which starts with foo in their route id's, use: include=foo&#42; And to exclude 
routes which starts from JMS endpoints, use: exclude=jms:&#42; Multiple 
patterns can be separated by c [...]
-| *camel.springboot.route-filter-include-pattern* | Used for filtering routes 
routes matching the given pattern, which follows the following rules: - Match 
by route id - Match by route input endpoint uri The matching is using exact 
match, by wildcard and regular expression. For example to only include routes 
which starts with foo in their route id's, use: include=foo&#42; And to exclude 
routes which starts from JMS endpoints, use: exclude=jms:&#42; Multiple 
patterns can be separated by c [...]
+| *camel.springboot.route-filter-include-pattern* | Used for filtering routes 
matching the given pattern, which follows the following rules: - Match by route 
id - Match by route input endpoint uri The matching is using exact match, by 
wildcard and regular expression. For example to only include routes which 
starts with foo in their route id's, use: include=foo&#42; And to exclude 
routes which starts from JMS endpoints, use: exclude=jms:&#42; Multiple 
patterns can be separated by comma, f [...]
 | *camel.springboot.routes-collector-enabled* | Whether the routes collector 
is enabled or not. When enabled Camel will auto-discover routes (RouteBuilder 
instances from the registry and also load additional XML routes from the file 
system. The routes collector is default enabled. | true | Boolean
 | *camel.springboot.shutdown-log-inflight-exchanges-on-timeout* | Sets whether 
to log information about the inflight Exchanges which are still running during 
a shutdown which didn't complete without the given timeout. This requires to 
enable the option inflightRepositoryExchangeEnabled. | true | Boolean
 | *camel.springboot.shutdown-now-on-timeout* | Sets whether to force shutdown 
of all consumers when a timeout occurred and thus not all consumers was 
shutdown within that period. You should have good reasons to set this option to 
false as it means that the routes keep running and is halted abruptly when 
CamelContext has been shutdown. | true | Boolean
@@ -220,12 +220,12 @@ The component supports 157 options, which are listed 
below.
 | *camel.springboot.tracing* | Sets whether tracing is enabled or not. Default 
is false. | false | Boolean
 | *camel.springboot.tracing-pattern* | Tracing pattern to match which node 
EIPs to trace. For example to match all To EIP nodes, use to*. The pattern 
matches by node and route id's Multiple patterns can be separated by comma. |  
| String
 | *camel.springboot.use-breadcrumb* | Set whether breadcrumb is enabled. The 
default value is false. | false | Boolean
-| *camel.springboot.use-data-type* | Whether to enable using data type on 
Camel messages. Data type are automatic turned on if one ore more routes has 
been explicit configured with input and output types. Otherwise data type is 
default off. | false | Boolean
+| *camel.springboot.use-data-type* | Whether to enable using data type on 
Camel messages. Data type are automatic turned on if one or more routes has 
been explicit configured with input and output types. Otherwise data type is 
default off. | false | Boolean
 | *camel.springboot.use-mdc-logging* | To turn on MDC logging | false | Boolean
 | *camel.springboot.warn-on-early-shutdown* | Whether to log a WARN if Camel 
on Spring Boot was immediately shutdown after starting which very likely is 
because there is no JVM thread to keep the application running. | true | Boolean
-| *camel.springboot.xml-rests* | Directory to scan for adding additional XML 
rests. You can turn this off by setting the value to false. Files can be loaded 
from either classpath or file by prefixing with classpath: or file: Wildcards 
is supported using a ANT pattern style paths, such as 
classpath:&#42;&#42;/&#42;camel&#42;.xml Multiple directories can be specified 
and separated by comma, such as: 
file:/myapp/mycamel/&#42;.xml,file:/myapp/myothercamel/&#42;.xml | 
classpath:camel-rest/*.x [...]
-| *camel.springboot.xml-route-templates* | Directory to scan for adding 
additional XML route templates. You can turn this off by setting the value to 
false. Files can be loaded from either classpath or file by prefixing with 
classpath: or file: Wildcards is supported using a ANT pattern style paths, 
such as classpath:&#42;&#42;/&#42;template-&#42;.xml Notice when using 
wildcards, then there is additional overhead as the classpath is scanned, where 
as if you specific the exact name for ea [...]
-| *camel.springboot.xml-routes* | Directory to scan for adding additional XML 
routes. You can turn this off by setting the value to false. Files can be 
loaded from either classpath or file by prefixing with classpath: or file: 
Wildcards is supported using a ANT pattern style paths, such as 
classpath:&#42;&#42;/&#42;camel&#42;.xml Multiple directories can be specified 
and separated by comma, such as: 
file:/myapp/mycamel/&#42;.xml,file:/myapp/myothercamel/&#42;.xml | 
classpath:camel/*.xml  [...]
+| *camel.springboot.xml-rests* | Directory to scan for adding additional XML 
rests. You can turn this off by setting the value to false. Files can be loaded 
from either classpath or file by prefixing with classpath: or file: Wildcards 
is supported using an ANT pattern style paths, such as 
classpath:&#42;&#42;/&#42;camel&#42;.xml Multiple directories can be specified 
and separated by comma, such as: 
file:/myapp/mycamel/&#42;.xml,file:/myapp/myothercamel/&#42;.xml | 
classpath:camel-rest/*. [...]
+| *camel.springboot.xml-route-templates* | Directory to scan for adding 
additional XML route templates. You can turn this off by setting the value to 
false. Files can be loaded from either classpath or file by prefixing with 
classpath: or file: Wildcards is supported using an ANT pattern style paths, 
such as classpath:&#42;&#42;/&#42;template-&#42;.xml Notice when using 
wildcards, then there is additional overhead as the classpath is scanned, where 
as if you specific the exact name for e [...]
+| *camel.springboot.xml-routes* | Directory to scan for adding additional XML 
routes. You can turn this off by setting the value to false. Files can be 
loaded from either classpath or file by prefixing with classpath: or file: 
Wildcards is supported using an ANT pattern style paths, such as 
classpath:&#42;&#42;/&#42;camel&#42;.xml Multiple directories can be specified 
and separated by comma, such as: 
file:/myapp/mycamel/&#42;.xml,file:/myapp/myothercamel/&#42;.xml | 
classpath:camel/*.xml [...]
 | *camel.ssl.cert-alias* | An optional certificate alias to use. This is 
useful when the keystore has multiple certificates. |  | String
 | *camel.ssl.cipher-suites* | The optional explicitly configured cipher suites 
for this configuration. |  | CipherSuitesParameters
 | *camel.ssl.cipher-suites-filter* | The optional cipher suite filter 
configuration for this configuration. |  | FilterParameters
diff --git a/docs/modules/ROOT/pages/spring-boot.adoc 
b/docs/modules/ROOT/pages/spring-boot.adoc
index eefbd5f..6b43056 100644
--- a/docs/modules/ROOT/pages/spring-boot.adoc
+++ b/docs/modules/ROOT/pages/spring-boot.adoc
@@ -176,13 +176,13 @@ The component supports 157 options, which are listed 
below.
 | *camel.springboot.jmx-enabled* | Enable JMX in your Camel application. | 
true | Boolean
 | *camel.springboot.jmx-management-name-pattern* | The naming pattern for 
creating the CamelContext JMX management name. The default pattern is #name# | 
#name# | String
 | *camel.springboot.jmx-management-statistics-level* | Sets the JMX statistics 
level The level can be set to Extended to gather additional information The 
default value is Default. |  | ManagementStatisticsLevel
-| *camel.springboot.lightweight* | Experimental: Configure the context to be 
lightweight. This will trigger some optimizations and memory reduction options. 
Lightweight context have some limitations. At this moment, dynamic endpoint 
destinations are not supported. | false | Boolean
+| *camel.springboot.lightweight* | Experimental: Configure the context to be 
lightweight. This will trigger some optimizations and memory reduction options. 
Lightweight context has some limitations. At this moment, dynamic endpoint 
destinations are not supported. | false | Boolean
 | *camel.springboot.load-type-converters* | Whether to load custom type 
converters by scanning classpath. This is used for backwards compatibility with 
Camel 2.x. Its recommended to migrate to use fast type converter loading by 
setting <tt>@Converter(generateLoader = true)</tt> on your custom type 
converter classes. | true | Boolean
 | *camel.springboot.log-debug-max-chars* | Is used to limit the maximum length 
of the logging Camel message bodies. If the message body is longer than the 
limit, the log message is clipped. Use -1 to have unlimited length. Use for 
example 1000 to log at most 1000 characters. | 0 | Integer
 | *camel.springboot.log-exhausted-message-body* | Sets whether to log 
exhausted message body with message history. Default is false. | false | Boolean
 | *camel.springboot.log-mask* | Sets whether log mask is enabled or not. 
Default is false. | false | Boolean
 | *camel.springboot.main-run-controller* | Whether to use the main run 
controller to ensure the Spring-Boot application keeps running until being 
stopped or the JVM terminated. You typically only need this if you run 
Spring-Boot standalone. If you run Spring-Boot with spring-boot-starter-web 
then the web container keeps the JVM running. | false | Boolean
-| *camel.springboot.mdc-logging-keys-pattern* | Sets the pattern used for 
determine which custom MDC keys to propagate during message routing when the 
routing engine continues routing asynchronously for the given message. Setting 
this pattern to * will propagate all custom keys. Or setting the pattern to 
foo*,bar* will propagate any keys starting with either foo or bar. Notice that 
a set of standard Camel MDC keys are always propagated which starts with camel. 
as key name. The match rule [...]
+| *camel.springboot.mdc-logging-keys-pattern* | Sets the pattern used for 
determining which custom MDC keys to propagate during message routing when the 
routing engine continues routing asynchronously for the given message. Setting 
this pattern to * will propagate all custom keys. Or setting the pattern to 
foo*,bar* will propagate any keys starting with either foo or bar. Notice that 
a set of standard Camel MDC keys are always propagated which starts with camel. 
as key name. The match ru [...]
 | *camel.springboot.message-history* | Sets whether message history is enabled 
or not. Default is true. | true | Boolean
 | *camel.springboot.name* | Sets the name of the CamelContext. |  | String
 | *camel.springboot.producer-template-cache-size* | Producer template 
endpoints cache size. | 1000 | Integer
@@ -195,11 +195,11 @@ The component supports 157 options, which are listed 
below.
 | *camel.springboot.route-controller-include-routes* | Pattern for filtering 
routes to be excluded as supervised. The pattern is matching on route id, and 
endpoint uri for the route. Multiple patterns can be separated by comma. For 
example to exclude all JMS routes, you can say <tt>jms:*</tt>. And to exclude 
routes with specific route ids <tt>mySpecialRoute,myOtherSpecialRoute</tt>. The 
pattern supports wildcards and uses the matcher from 
org.apache.camel.support.PatternHelper#matchPatte [...]
 | *camel.springboot.route-controller-initial-delay* | Initial delay in milli 
seconds before the route controller starts, after CamelContext has been 
started. | 0 | Long
 | *camel.springboot.route-controller-route-startup-logging-level* | Sets the 
logging level used for logging route startup activity. By default INFO level is 
used. You can use this to change the level for example to OFF if this kind of 
logging is not wanted. |  | LoggingLevel
-| *camel.springboot.route-controller-supervise-enabled* | To enable using 
supervising route controller which allows Camel to startup and then the 
controller takes care of starting the routes in a safe manner. This can be used 
when you want to startup Camel despite a route may otherwise fail fast during 
startup and cause Camel to fail to startup as well. By delegating the route 
startup to the supervising route controller then its manages the startup using 
a background thread. The controll [...]
+| *camel.springboot.route-controller-supervise-enabled* | To enable using 
supervising route controller which allows Camel to startup and then the 
controller takes care of starting the routes in a safe manner. This can be used 
when you want to startup Camel despite a route may otherwise fail fast during 
startup and cause Camel to fail to startup as well. By delegating the route 
startup to the supervising route controller then it manages the startup using a 
background thread. The controlle [...]
 | *camel.springboot.route-controller-thread-pool-size* | The number of threads 
used by the route controller scheduled thread pool that are used for restarting 
routes. The pool uses 1 thread by default, but you can increase this to allow 
the controller to concurrently attempt to restart multiple routes in case more 
than one route has problems starting. | 1 | Integer
 | *camel.springboot.route-controller-unhealthy-on-exhausted* | Whether to mark 
the route as unhealthy (down) when all restarting attempts (backoff) have 
failed and the route is not successfully started and the route manager is 
giving up. Setting this to true allows health checks to know about this and can 
report the Camel application as DOWN. The default is false. | false | Boolean
 | *camel.springboot.route-filter-exclude-pattern* | Used for filtering routes 
routes matching the given pattern, which follows the following rules: - Match 
by route id - Match by route input endpoint uri The matching is using exact 
match, by wildcard and regular expression. For example to only include routes 
which starts with foo in their route id's, use: include=foo&#42; And to exclude 
routes which starts from JMS endpoints, use: exclude=jms:&#42; Multiple 
patterns can be separated by c [...]
-| *camel.springboot.route-filter-include-pattern* | Used for filtering routes 
routes matching the given pattern, which follows the following rules: - Match 
by route id - Match by route input endpoint uri The matching is using exact 
match, by wildcard and regular expression. For example to only include routes 
which starts with foo in their route id's, use: include=foo&#42; And to exclude 
routes which starts from JMS endpoints, use: exclude=jms:&#42; Multiple 
patterns can be separated by c [...]
+| *camel.springboot.route-filter-include-pattern* | Used for filtering routes 
matching the given pattern, which follows the following rules: - Match by route 
id - Match by route input endpoint uri The matching is using exact match, by 
wildcard and regular expression. For example to only include routes which 
starts with foo in their route id's, use: include=foo&#42; And to exclude 
routes which starts from JMS endpoints, use: exclude=jms:&#42; Multiple 
patterns can be separated by comma, f [...]
 | *camel.springboot.routes-collector-enabled* | Whether the routes collector 
is enabled or not. When enabled Camel will auto-discover routes (RouteBuilder 
instances from the registry and also load additional XML routes from the file 
system. The routes collector is default enabled. | true | Boolean
 | *camel.springboot.shutdown-log-inflight-exchanges-on-timeout* | Sets whether 
to log information about the inflight Exchanges which are still running during 
a shutdown which didn't complete without the given timeout. This requires to 
enable the option inflightRepositoryExchangeEnabled. | true | Boolean
 | *camel.springboot.shutdown-now-on-timeout* | Sets whether to force shutdown 
of all consumers when a timeout occurred and thus not all consumers was 
shutdown within that period. You should have good reasons to set this option to 
false as it means that the routes keep running and is halted abruptly when 
CamelContext has been shutdown. | true | Boolean
@@ -220,12 +220,12 @@ The component supports 157 options, which are listed 
below.
 | *camel.springboot.tracing* | Sets whether tracing is enabled or not. Default 
is false. | false | Boolean
 | *camel.springboot.tracing-pattern* | Tracing pattern to match which node 
EIPs to trace. For example to match all To EIP nodes, use to*. The pattern 
matches by node and route id's Multiple patterns can be separated by comma. |  
| String
 | *camel.springboot.use-breadcrumb* | Set whether breadcrumb is enabled. The 
default value is false. | false | Boolean
-| *camel.springboot.use-data-type* | Whether to enable using data type on 
Camel messages. Data type are automatic turned on if one ore more routes has 
been explicit configured with input and output types. Otherwise data type is 
default off. | false | Boolean
+| *camel.springboot.use-data-type* | Whether to enable using data type on 
Camel messages. Data type are automatic turned on if one or more routes has 
been explicit configured with input and output types. Otherwise data type is 
default off. | false | Boolean
 | *camel.springboot.use-mdc-logging* | To turn on MDC logging | false | Boolean
 | *camel.springboot.warn-on-early-shutdown* | Whether to log a WARN if Camel 
on Spring Boot was immediately shutdown after starting which very likely is 
because there is no JVM thread to keep the application running. | true | Boolean
-| *camel.springboot.xml-rests* | Directory to scan for adding additional XML 
rests. You can turn this off by setting the value to false. Files can be loaded 
from either classpath or file by prefixing with classpath: or file: Wildcards 
is supported using a ANT pattern style paths, such as 
classpath:&#42;&#42;/&#42;camel&#42;.xml Multiple directories can be specified 
and separated by comma, such as: 
file:/myapp/mycamel/&#42;.xml,file:/myapp/myothercamel/&#42;.xml | 
classpath:camel-rest/*.x [...]
-| *camel.springboot.xml-route-templates* | Directory to scan for adding 
additional XML route templates. You can turn this off by setting the value to 
false. Files can be loaded from either classpath or file by prefixing with 
classpath: or file: Wildcards is supported using a ANT pattern style paths, 
such as classpath:&#42;&#42;/&#42;template-&#42;.xml Notice when using 
wildcards, then there is additional overhead as the classpath is scanned, where 
as if you specific the exact name for ea [...]
-| *camel.springboot.xml-routes* | Directory to scan for adding additional XML 
routes. You can turn this off by setting the value to false. Files can be 
loaded from either classpath or file by prefixing with classpath: or file: 
Wildcards is supported using a ANT pattern style paths, such as 
classpath:&#42;&#42;/&#42;camel&#42;.xml Multiple directories can be specified 
and separated by comma, such as: 
file:/myapp/mycamel/&#42;.xml,file:/myapp/myothercamel/&#42;.xml | 
classpath:camel/*.xml  [...]
+| *camel.springboot.xml-rests* | Directory to scan for adding additional XML 
rests. You can turn this off by setting the value to false. Files can be loaded 
from either classpath or file by prefixing with classpath: or file: Wildcards 
is supported using an ANT pattern style paths, such as 
classpath:&#42;&#42;/&#42;camel&#42;.xml Multiple directories can be specified 
and separated by comma, such as: 
file:/myapp/mycamel/&#42;.xml,file:/myapp/myothercamel/&#42;.xml | 
classpath:camel-rest/*. [...]
+| *camel.springboot.xml-route-templates* | Directory to scan for adding 
additional XML route templates. You can turn this off by setting the value to 
false. Files can be loaded from either classpath or file by prefixing with 
classpath: or file: Wildcards is supported using an ANT pattern style paths, 
such as classpath:&#42;&#42;/&#42;template-&#42;.xml Notice when using 
wildcards, then there is additional overhead as the classpath is scanned, where 
as if you specific the exact name for e [...]
+| *camel.springboot.xml-routes* | Directory to scan for adding additional XML 
routes. You can turn this off by setting the value to false. Files can be 
loaded from either classpath or file by prefixing with classpath: or file: 
Wildcards is supported using an ANT pattern style paths, such as 
classpath:&#42;&#42;/&#42;camel&#42;.xml Multiple directories can be specified 
and separated by comma, such as: 
file:/myapp/mycamel/&#42;.xml,file:/myapp/myothercamel/&#42;.xml | 
classpath:camel/*.xml [...]
 | *camel.ssl.cert-alias* | An optional certificate alias to use. This is 
useful when the keystore has multiple certificates. |  | String
 | *camel.ssl.cipher-suites* | The optional explicitly configured cipher suites 
for this configuration. |  | CipherSuitesParameters
 | *camel.ssl.cipher-suites-filter* | The optional cipher suite filter 
configuration for this configuration. |  | FilterParameters
@@ -689,7 +689,7 @@ You can also use xref:manual::spring-testing.adoc[Camel 
Spring test annotations]
 [source,java]
 ----
 @CamelSpringBootTest
-@SpringBootTest
+@SpringBootApplication
 @MockEndpoints("direct:end")
 public class MyApplicationTest {
 

Reply via email to