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
commit e507e5cfd5adc415b6f464de4d755eb0426ea8de
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Thu Jan 16 19:40:11 2020 +0100
Regen
---
components/camel-thrift/src/main/docs/thrift-component.adoc | 2 +-
docs/components/modules/ROOT/pages/thrift-component.adoc | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/components/camel-thrift/src/main/docs/thrift-component.adoc
b/components/camel-thrift/src/main/docs/thrift-component.adoc
index 80e7f50..5d59ecc 100644
--- a/components/camel-thrift/src/main/docs/thrift-component.adoc
+++ b/components/camel-thrift/src/main/docs/thrift-component.adoc
@@ -40,7 +40,7 @@ The Thrift component supports 4 options, which are listed
below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *useGlobalSslContext Parameters* (security) | Determine if the thrift
component is using global SSL context parameters | false | boolean
+| *useGlobalSslContextParameters* (security) | Determine if the thrift
component is using global SSL context parameters | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
| *lazyStartProducer* (producer) | Whether the producer should be started lazy
(on the first message). By starting lazy you can use this to allow CamelContext
and routes to startup in situations where a producer may otherwise fail during
starting and cause the route to fail being started. By deferring this startup
to be lazy then the startup failure can be handled during routing messages via
Camel's routing error handlers. Beware that when the first message is processed
then creating and [...]
| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the
Camel routing Error Handler, which mean any exceptions occurred while the
consumer is trying to pickup incoming messages, or the likes, will now be
processed as a message and handled by the routing Error Handler. By default the
consumer will use the org.apache.camel.spi.ExceptionHandler to deal with
exceptions, that will be logged at WARN or ERROR level and ignored. | false |
boolean
diff --git a/docs/components/modules/ROOT/pages/thrift-component.adoc
b/docs/components/modules/ROOT/pages/thrift-component.adoc
index 748e572..2b59365 100644
--- a/docs/components/modules/ROOT/pages/thrift-component.adoc
+++ b/docs/components/modules/ROOT/pages/thrift-component.adoc
@@ -41,7 +41,7 @@ The Thrift component supports 4 options, which are listed
below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *useGlobalSslContext Parameters* (security) | Determine if the thrift
component is using global SSL context parameters | false | boolean
+| *useGlobalSslContextParameters* (security) | Determine if the thrift
component is using global SSL context parameters | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
| *lazyStartProducer* (producer) | Whether the producer should be started lazy
(on the first message). By starting lazy you can use this to allow CamelContext
and routes to startup in situations where a producer may otherwise fail during
starting and cause the route to fail being started. By deferring this startup
to be lazy then the startup failure can be handled during routing messages via
Camel's routing error handlers. Beware that when the first message is processed
then creating and [...]
| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the
Camel routing Error Handler, which mean any exceptions occurred while the
consumer is trying to pickup incoming messages, or the likes, will now be
processed as a message and handled by the routing Error Handler. By default the
consumer will use the org.apache.camel.spi.ExceptionHandler to deal with
exceptions, that will be logged at WARN or ERROR level and ignored. | false |
boolean
