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 e6eee6f Regen
e6eee6f is described below
commit e6eee6f42d9bbcb0888dfbfb997598484e5dc9ce
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Thu Dec 12 05:27:49 2019 +0100
Regen
---
components/camel-ehcache/src/main/docs/ehcache-component.adoc | 2 +-
docs/components/modules/ROOT/pages/ehcache-component.adoc | 4 ++--
docs/components/modules/ROOT/pages/jcache-component.adoc | 2 +-
docs/components/modules/ROOT/pages/jira-component.adoc | 2 +-
docs/components/modules/ROOT/pages/xchange-component.adoc | 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/components/camel-ehcache/src/main/docs/ehcache-component.adoc
b/components/camel-ehcache/src/main/docs/ehcache-component.adoc
index efb73b9..78a42bd 100644
--- a/components/camel-ehcache/src/main/docs/ehcache-component.adoc
+++ b/components/camel-ehcache/src/main/docs/ehcache-component.adoc
@@ -148,7 +148,7 @@ The component supports 27 options, which are listed below.
| *camel.component.ehcache.configuration.create-cache-if-not-exist* |
Configure if a cache need to be created if it does exist or can't be
pre-configured. | true | Boolean
| *camel.component.ehcache.configuration.event-firing* | Set the delivery mode
(synchronous, asynchronous) | | EventFiring
| *camel.component.ehcache.configuration.event-ordering* | Set the delivery
mode (ordered, unordered) | | EventOrdering
-| *camel.component.ehcache.configuration.event-types* | Set the type of events
to listen for | | Set
+| *camel.component.ehcache.configuration.event-types* | Set the type of events
to listen for (EVICTED,EXPIRED,REMOVED,CREATED,UPDATED). You can specify
multiple entries separated by comma. | | String
| *camel.component.ehcache.configuration.key* | To configure the default
action key. If a key is set in the message header, then the key from the header
takes precedence. | | Object
| *camel.component.ehcache.configuration.key-type* | The cache key type,
default "java.lang.Object" | | String
| *camel.component.ehcache.configuration.value-type* | The cache value type,
default "java.lang.Object" | | String
diff --git a/docs/components/modules/ROOT/pages/ehcache-component.adoc
b/docs/components/modules/ROOT/pages/ehcache-component.adoc
index b490430..ffe94b7 100644
--- a/docs/components/modules/ROOT/pages/ehcache-component.adoc
+++ b/docs/components/modules/ROOT/pages/ehcache-component.adoc
@@ -96,7 +96,7 @@ with the following path and query parameters:
| *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
| *eventFiring* (consumer) | Set the delivery mode (synchronous, asynchronous)
| ASYNCHRONOUS | EventFiring
| *eventOrdering* (consumer) | Set the delivery mode (ordered, unordered) |
ORDERED | EventOrdering
-| *eventTypes* (consumer) | Set the type of events to listen for |
EVICTED,EXPIRED,REMOVED,CREATED,UPDATED | Set
+| *eventTypes* (consumer) | Set the type of events to listen for
(EVICTED,EXPIRED,REMOVED,CREATED,UPDATED). You can specify multiple entries
separated by comma. | | String
| *exceptionHandler* (consumer) | To let the consumer use a custom
ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this
option is not in use. By default the consumer will deal with exceptions, that
will be logged at WARN or ERROR level and ignored. | | ExceptionHandler
| *exchangePattern* (consumer) | Sets the exchange pattern when the consumer
creates an exchange. | | ExchangePattern
| *action* (producer) | To configure the default cache action. If an action is
set in the message header, then the operation from the header takes precedence.
| | String
@@ -149,7 +149,7 @@ The component supports 27 options, which are listed below.
| *camel.component.ehcache.configuration.create-cache-if-not-exist* |
Configure if a cache need to be created if it does exist or can't be
pre-configured. | true | Boolean
| *camel.component.ehcache.configuration.event-firing* | Set the delivery mode
(synchronous, asynchronous) | | EventFiring
| *camel.component.ehcache.configuration.event-ordering* | Set the delivery
mode (ordered, unordered) | | EventOrdering
-| *camel.component.ehcache.configuration.event-types* | Set the type of events
to listen for | | Set
+| *camel.component.ehcache.configuration.event-types* | Set the type of events
to listen for (EVICTED,EXPIRED,REMOVED,CREATED,UPDATED). You can specify
multiple entries separated by comma. | | String
| *camel.component.ehcache.configuration.key* | To configure the default
action key. If a key is set in the message header, then the key from the header
takes precedence. | | Object
| *camel.component.ehcache.configuration.key-type* | The cache key type,
default "java.lang.Object" | | String
| *camel.component.ehcache.configuration.value-type* | The cache value type,
default "java.lang.Object" | | String
diff --git a/docs/components/modules/ROOT/pages/jcache-component.adoc
b/docs/components/modules/ROOT/pages/jcache-component.adoc
index fb5fe24..fb9eb77 100644
--- a/docs/components/modules/ROOT/pages/jcache-component.adoc
+++ b/docs/components/modules/ROOT/pages/jcache-component.adoc
@@ -54,7 +54,7 @@ with the following path and query parameters:
| *storeByValue* (common) | If cache should use store-by-value or
store-by-reference semantics | true | boolean
| *writeThrough* (common) | If write-through caching should be used | false |
boolean
| *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
-| *filteredEvents* (consumer) | Events a consumer should filter. If using
filteredEvents option, then eventFilters one will be ignored | | List
+| *filteredEvents* (consumer) | Events a consumer should filter (multiple
events can be separated by comma). If using filteredEvents option, then
eventFilters one will be ignored | | String
| *oldValueRequired* (consumer) | if the old value is required for events |
false | boolean
| *synchronous* (consumer) | if the event listener should block the thread
causing the event | false | boolean
| *eventFilters* (consumer) | The CacheEntryEventFilter. If using eventFilters
option, then filteredEvents one will be ignored | | List
diff --git a/docs/components/modules/ROOT/pages/jira-component.adoc
b/docs/components/modules/ROOT/pages/jira-component.adoc
index e3530de..0447126 100644
--- a/docs/components/modules/ROOT/pages/jira-component.adoc
+++ b/docs/components/modules/ROOT/pages/jira-component.adoc
@@ -54,7 +54,7 @@ The Jira component supports 4 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *configuration* (advanced) | The JiraConfiguration parameters | |
JiraConfiguration
+| *configuration* (advanced) | To use a shared base jira configuration. | |
JiraConfiguration
| *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/xchange-component.adoc
b/docs/components/modules/ROOT/pages/xchange-component.adoc
index 6cf8b11..e9c9a05 100644
--- a/docs/components/modules/ROOT/pages/xchange-component.adoc
+++ b/docs/components/modules/ROOT/pages/xchange-component.adoc
@@ -75,7 +75,7 @@ with the following path and query parameters:
|===
| Name | Description | Default | Type
| *currency* (producer) | The currency | | Currency
-| *currencyPair* (producer) | The currency pair | | CurrencyPair
+| *currencyPair* (producer) | The currency pair | | String
| *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 [...]
| *method* (producer) | *Required* The method to execute | | XChangeMethod
| *service* (producer) | *Required* The service to call | | XChangeService
