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-spring-boot.git
The following commit(s) were added to refs/heads/master by this push:
new f570be4 Regen
f570be4 is described below
commit f570be494c8da3c1b3569086ad90295f06c07b2e
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Sun Feb 16 14:39:40 2020 +0100
Regen
---
docs/modules/ROOT/pages/mail-starter.adoc | 3 +--
docs/modules/ROOT/pages/undertow-starter.adoc | 11 +++++------
docs/modules/ROOT/pages/yammer-starter.adoc | 7 +++----
3 files changed, 9 insertions(+), 12 deletions(-)
diff --git a/docs/modules/ROOT/pages/mail-starter.adoc
b/docs/modules/ROOT/pages/mail-starter.adoc
index 50040ba..933a05d 100644
--- a/docs/modules/ROOT/pages/mail-starter.adoc
+++ b/docs/modules/ROOT/pages/mail-starter.adoc
@@ -17,7 +17,7 @@ When using mail with Spring Boot make sure to use the
following Maven dependency
----
-The component supports 50 options, which are listed below.
+The component supports 49 options, which are listed below.
@@ -52,7 +52,6 @@ The component supports 50 options, which are listed below.
| *camel.component.mail.configuration.password* | The password for login | |
String
| *camel.component.mail.configuration.peek* | Will mark the javax.mail.Message
as peeked before processing the mail message. This applies to IMAPMessage
messages types only. By using peek the mail will not be eager marked as SEEN on
the mail server, which allows us to rollback the mail message if there is an
error processing in Camel. | true | Boolean
| *camel.component.mail.configuration.port* | The port number of the mail
server | | Integer
-| *camel.component.mail.configuration.protocol* | | | String
| *camel.component.mail.configuration.reply-to* | The Reply-To recipients (the
receivers of the response mail). Separate multiple email addresses with a
comma. | | String
| *camel.component.mail.configuration.session* | Specifies the mail session
that camel should use for all mail interactions. Useful in scenarios where mail
sessions are created and managed by some other resource, such as a JavaEE
container. When using a custom mail session, then the hostname and port from
the mail session will be used (if configured on the session). | | Session
| *camel.component.mail.configuration.skip-failed-message* | If the mail
consumer cannot retrieve a given mail message, then this option allows to skip
the message and move on to retrieve the next mail message. The default behavior
would be the consumer throws an exception and no mails from the batch would be
able to be routed by Camel. | false | Boolean
diff --git a/docs/modules/ROOT/pages/undertow-starter.adoc
b/docs/modules/ROOT/pages/undertow-starter.adoc
index d4ce27c..8f3effc 100644
--- a/docs/modules/ROOT/pages/undertow-starter.adoc
+++ b/docs/modules/ROOT/pages/undertow-starter.adoc
@@ -27,16 +27,15 @@ The component supports 13 options, which are listed below.
| *camel.component.undertow.basic-property-binding* | Whether the component
should use basic property binding (Camel 2.x) or the newer property binding
with additional capabilities | false | Boolean
| *camel.component.undertow.bridge-error-handler* | 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
| *camel.component.undertow.enabled* | Whether to enable auto configuration of
the undertow component. This is enabled by default. | | Boolean
-| *camel.component.undertow.host-options.buffer-size* | | | Integer
-| *camel.component.undertow.host-options.direct-buffers* | | | Boolean
-| *camel.component.undertow.host-options.http2-enabled* | | | Boolean
-| *camel.component.undertow.host-options.io-threads* | | | Integer
-| *camel.component.undertow.host-options.worker-threads* | | | Integer
+| *camel.component.undertow.host-options.buffer-size* | The buffer size of the
Undertow host. | | Integer
+| *camel.component.undertow.host-options.direct-buffers* | Set if the Undertow
host should use direct buffers. | | Boolean
+| *camel.component.undertow.host-options.http2-enabled* | Set if the Undertow
host should use http2 protocol. | | Boolean
+| *camel.component.undertow.host-options.io-threads* | The number of io
threads to use in a Undertow host. | | Integer
+| *camel.component.undertow.host-options.worker-threads* | The number of
worker threads to use in a Undertow host. | | Integer
| *camel.component.undertow.lazy-start-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 t [...]
| *camel.component.undertow.mute-exception* | If enabled and an Exchange
failed processing on the consumer side the response's body won't contain the
exception's stack trace. | false | Boolean
| *camel.component.undertow.ssl-context-parameters* | To configure security
using SSLContextParameters. The option is a
org.apache.camel.support.jsse.SSLContextParameters type. | | String
| *camel.component.undertow.undertow-http-binding* | To use a custom
HttpBinding to control the mapping between Camel message and HttpClient. The
option is a org.apache.camel.component.undertow.UndertowHttpBinding type. | |
String
| *camel.component.undertow.use-global-ssl-context-parameters* | Enable usage
of global SSL context parameters. | false | Boolean
|===
-
// spring-boot-auto-configure options: END
diff --git a/docs/modules/ROOT/pages/yammer-starter.adoc
b/docs/modules/ROOT/pages/yammer-starter.adoc
index 04febd1..a070ec2 100644
--- a/docs/modules/ROOT/pages/yammer-starter.adoc
+++ b/docs/modules/ROOT/pages/yammer-starter.adoc
@@ -31,12 +31,11 @@ The component supports 20 options, which are listed below.
| *camel.component.yammer.config.consumer-key* | The consumer key | | String
| *camel.component.yammer.config.consumer-secret* | The consumer secret | |
String
| *camel.component.yammer.config.delay* | Delay between polling in millis |
5000 | Long
-| *camel.component.yammer.config.function* | The function to use | | String
-| *camel.component.yammer.config.function-type* | | | YammerFunctionType
+| *camel.component.yammer.config.function* | The function to use | |
YammerFunctionType
| *camel.component.yammer.config.limit* | Return only the specified number of
messages. Works for threaded=true and threaded=extended. | -1 | Integer
| *camel.component.yammer.config.newer-than* | Returns messages newer than the
message ID specified as a numeric string. This should be used when polling for
new messages. If you're looking at messages, and the most recent message
returned is 3516, you can make a request with the parameter newerThan=3516 to
ensure that you do not get duplicate copies of messages already on your page. |
-1 | Long
| *camel.component.yammer.config.older-than* | Returns messages older than the
message ID specified as a numeric string. This is useful for paginating
messages. For example, if you're currently viewing 20 messages and the oldest
is number 2912, you could append olderThan=2912 to your request to get the 20
messages prior to those you're seeing. | -1 | Long
-| *camel.component.yammer.config.requestor* | | | ApiRequestor
+| *camel.component.yammer.config.requestor* | To use a specific requester to
communicate with Yammer. | | ApiRequestor
| *camel.component.yammer.config.threaded* | threaded=true will only return
the first message in each thread. This parameter is intended for apps which
display message threads collapsed. threaded=extended will return the thread
starter messages in order of most recently active as well as the two most
recent messages, as they are viewed in the default view on the Yammer web
interface. | | String
| *camel.component.yammer.config.use-json* | Set to true if you want to use
raw JSON rather than converting to POJOs. | false | Boolean
| *camel.component.yammer.config.user-id* | The user id | | String
@@ -44,6 +43,6 @@ The component supports 20 options, which are listed below.
| *camel.component.yammer.consumer-secret* | The consumer secret | | String
| *camel.component.yammer.enabled* | Whether to enable auto configuration of
the yammer component. This is enabled by default. | | Boolean
| *camel.component.yammer.lazy-start-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 the [...]
+| *camel.component.yammer.requestor* | To use a specific requester to
communicate with Yammer. The option is a
org.apache.camel.component.yammer.ApiRequestor type. | | String
|===
-
// spring-boot-auto-configure options: END
