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.git
The following commit(s) were added to refs/heads/master by this push:
new 0f7664d Regen docs of camel-core
0f7664d is described below
commit 0f7664d8b886a756647a20d9ce72d4b71f72423a
Author: Andrea Cosentino <[email protected]>
AuthorDate: Tue Feb 20 12:37:08 2018 +0100
Regen docs of camel-core
---
camel-core/src/main/docs/eips/aggregate-eip.adoc | 24 ++++++++++----------
camel-core/src/main/docs/eips/bean-eip.adoc | 4 ++--
camel-core/src/main/docs/eips/claimCheck-eip.adoc | 4 ++--
.../src/main/docs/eips/dynamicRouter-eip.adoc | 4 ++--
camel-core/src/main/docs/eips/enrich-eip.adoc | 8 +++----
camel-core/src/main/docs/eips/hystrix-eip.adoc | 4 ++--
.../main/docs/eips/hystrixConfiguration-eip.adoc | 16 ++++++-------
.../src/main/docs/eips/idempotentConsumer-eip.adoc | 4 ++--
camel-core/src/main/docs/eips/loop-eip.adoc | 4 ++--
camel-core/src/main/docs/eips/multicast-eip.adoc | 20 ++++++++---------
.../src/main/docs/eips/recipientList-eip.adoc | 26 +++++++++++-----------
camel-core/src/main/docs/eips/routingSlip-eip.adoc | 4 ++--
camel-core/src/main/docs/eips/saga-eip.adoc | 12 +++++-----
camel-core/src/main/docs/eips/sample-eip.adoc | 4 ++--
camel-core/src/main/docs/eips/split-eip.adoc | 22 +++++++++---------
.../src/main/docs/eips/stream-config-eip.adoc | 4 ++--
camel-core/src/main/docs/eips/threads-eip.adoc | 2 +-
camel-core/src/main/docs/eips/wireTap-eip.adoc | 6 ++---
18 files changed, 86 insertions(+), 86 deletions(-)
diff --git a/camel-core/src/main/docs/eips/aggregate-eip.adoc
b/camel-core/src/main/docs/eips/aggregate-eip.adoc
index 3f3ed1b..4df466c 100644
--- a/camel-core/src/main/docs/eips/aggregate-eip.adoc
+++ b/camel-core/src/main/docs/eips/aggregate-eip.adoc
@@ -24,28 +24,28 @@ The Aggregate EIP supports 24 options which are listed
below:
|===
| Name | Description | Default | Type
| *correlationExpression* | *Required* The expression used to calculate the
correlation key to use for aggregation. The Exchange which has the same
correlation key is aggregated together. If the correlation key could not be
evaluated an Exception is thrown. You can disable this by using the
ignoreBadCorrelationKeys option. | | NamespaceAware Expression
-| *completionPredicate* | A Predicate to indicate when an aggregated exchange
is complete. If this is not specified and the AggregationStrategy object
implements Predicate the aggregationStrategy object will be used as the
completionPredicate. | | NamespaceAware Expression
-| *completionTimeout* | Time in millis that an aggregated exchange should be
inactive before its complete (timeout). This option can be set as either a
fixed value or using an Expression which allows you to evaluate a timeout
dynamically - will use Long as result. If both are set Camel will fallback to
use the fixed value if the Expression result was null or 0. You cannot use this
option together with completionInterval only one of the two can be used. By
default the timeout checker runs [...]
+| *completionPredicate* | A Predicate to indicate when an aggregated exchange
is complete. If this is not specified and the AggregationStrategy object
implements Predicate, the aggregationStrategy object will be used as the
completionPredicate. | | NamespaceAware Expression
+| *completionTimeout* | Time in millis that an aggregated exchange should be
inactive before its complete (timeout). This option can be set as either a
fixed value or using an Expression which allows you to evaluate a timeout
dynamically - will use Long as result. If both are set Camel will fallback to
use the fixed value if the Expression result was null or 0. You cannot use this
option together with completionInterval, only one of the two can be used. By
default the timeout checker run [...]
| *completionSize* | Number of messages aggregated before the aggregation is
complete. This option can be set as either a fixed value or using an Expression
which allows you to evaluate a size dynamically - will use Integer as result.
If both are set Camel will fallback to use the fixed value if the Expression
result was null or 0. | | Integer
| *optimisticLockRetryPolicy* | Allows to configure retry settings when using
optimistic locking. | | OptimisticLockRetry PolicyDefinition
| *parallelProcessing* | When aggregated are completed they are being send out
of the aggregator. This option indicates whether or not Camel should use a
thread pool with multiple threads for concurrency. If no custom thread pool has
been specified then Camel creates a default pool with 10 concurrent threads. |
false | Boolean
-| *optimisticLocking* | Turns on using optimistic locking which requires the
aggregationRepository being used is supporting this by implementing
org.apache.camel.spi.OptimisticLockingAggregationRepository. | false | Boolean
+| *optimisticLocking* | Turns on using optimistic locking, which requires the
aggregationRepository being used, is supporting this by implementing
org.apache.camel.spi.OptimisticLockingAggregationRepository. | false | Boolean
| *executorServiceRef* | If using parallelProcessing you can specify a custom
thread pool to be used. In fact also if you are not using parallelProcessing
this custom thread pool is used to send out aggregated exchanges as well. | |
String
-| *timeoutCheckerExecutor ServiceRef* | If using either of the
completionTimeout completionTimeoutExpression or completionInterval options a
background thread is created to check for the completion for every aggregator.
Set this option to provide a custom thread pool to be used rather than creating
a new thread for every aggregator. | | String
+| *timeoutCheckerExecutor ServiceRef* | If using either of the
completionTimeout, completionTimeoutExpression, or completionInterval options a
background thread is created to check for the completion for every aggregator.
Set this option to provide a custom thread pool to be used rather than creating
a new thread for every aggregator. | | String
| *aggregationRepositoryRef* | Sets the custom aggregate repository to use
Will by default use
org.apache.camel.processor.aggregate.MemoryAggregationRepository | | String
-| *strategyRef* | A reference to lookup the AggregationStrategy in the
Registry. Configuring an AggregationStrategy is required and is used to merge
the incoming Exchange with the existing already merged exchanges. At first call
the oldExchange parameter is null. On subsequent invocations the oldExchange
contains the merged exchanges and newExchange is of course the new incoming
Exchange. | | String
-| *strategyMethodName* | This option can be used to explicit declare the
method name to use when using POJOs as the AggregationStrategy. | | String
-| *strategyMethodAllowNull* | If this option is false then the aggregate
method is not used for the very first aggregation. If this option is true then
null values is used as the oldExchange (at the very first aggregation) when
using POJOs as the AggregationStrategy. | false | Boolean
-| *completionInterval* | A repeating period in millis by which the aggregator
will complete all current aggregated exchanges. Camel has a background task
which is triggered every period. You cannot use this option together with
completionTimeout only one of them can be used. | | Long
+| *strategyRef* | A reference to lookup the AggregationStrategy in the
Registry. Configuring an AggregationStrategy is required, and is used to merge
the incoming Exchange with the existing already merged exchanges. At first call
the oldExchange parameter is null. On subsequent invocations the oldExchange
contains the merged exchanges and newExchange is of course the new incoming
Exchange. | | String
+| *strategyMethodName* | This option can be used to explicit declare the
method name to use, when using POJOs as the AggregationStrategy. | | String
+| *strategyMethodAllowNull* | If this option is false then the aggregate
method is not used for the very first aggregation. If this option is true then
null values is used as the oldExchange (at the very first aggregation), when
using POJOs as the AggregationStrategy. | false | Boolean
+| *completionInterval* | A repeating period in millis by which the aggregator
will complete all current aggregated exchanges. Camel has a background task
which is triggered every period. You cannot use this option together with
completionTimeout, only one of them can be used. | | Long
| *completionTimeoutChecker Interval* | Interval in millis that is used by the
background task that checks for timeouts (org.apache.camel.TimeoutMap). By
default the timeout checker runs every second. The timeout is an approximation
and there is no guarantee that the a timeout is triggered exactly after the
timeout value. It is not recommended to use very low timeout values or checker
intervals. | 1000 | Long
| *completionFromBatchConsumer* | Enables the batch completion mode where we
aggregate from a org.apache.camel.BatchConsumer and aggregate the total number
of exchanges the org.apache.camel.BatchConsumer has reported as total by
checking the exchange property link org.apache.camel.ExchangeBATCH_COMPLETE
when its complete. | false | Boolean
-| *groupExchanges* | *Deprecated* Enables grouped exchanges so the aggregator
will group all aggregated exchanges into a single combined Exchange holding all
the aggregated exchanges in a java.util.List. | false | Boolean
+| *groupExchanges* | *Deprecated* Enables grouped exchanges, so the aggregator
will group all aggregated exchanges into a single combined Exchange holding all
the aggregated exchanges in a java.util.List. | false | Boolean
| *eagerCheckCompletion* | Use eager completion checking which means that the
completionPredicate will use the incoming Exchange. As opposed to without eager
completion checking the completionPredicate will use the aggregated Exchange. |
false | Boolean
| *ignoreInvalidCorrelation Keys* | If a correlation key cannot be
successfully evaluated it will be ignored by logging a DEBUG and then just
ignore the incoming Exchange. | false | Boolean
-| *closeCorrelationKeyOn Completion* | Closes a correlation key when its
complete. Any late received exchanges which has a correlation key that has been
closed it will be defined and a ClosedCorrelationKeyException is thrown. | |
Integer
+| *closeCorrelationKeyOn Completion* | Closes a correlation key when its
complete. Any late received exchanges which has a correlation key that has been
closed, it will be defined and a ClosedCorrelationKeyException is thrown. | |
Integer
| *discardOnCompletionTimeout* | Discards the aggregated message on completion
timeout. This means on timeout the aggregated message is dropped and not sent
out of the aggregator. | false | Boolean
| *forceCompletionOnStop* | Indicates to complete all current aggregated
exchanges when the context is stopped | false | Boolean
-| *completeAllOnStop* | Indicates to wait to complete all current and partial
(pending) aggregated exchanges when the context is stopped. This also means
that we will wait for all pending exchanges which are stored in the aggregation
repository to complete so the repository is empty before we can stop. You may
want to enable this when using the memory based aggregation repository that is
memory based only and do not store data on disk. When this option is enabled
then the aggregator is w [...]
+| *completeAllOnStop* | Indicates to wait to complete all current and partial
(pending) aggregated exchanges when the context is stopped. This also means
that we will wait for all pending exchanges which are stored in the aggregation
repository to complete so the repository is empty before we can stop. You may
want to enable this when using the memory based aggregation repository that is
memory based only, and do not store data on disk. When this option is enabled,
then the aggregator is [...]
| *aggregateControllerRef* | To use a
org.apache.camel.processor.aggregate.AggregateController to allow external
sources to control this aggregator. | | String
|===
// eip options: END
@@ -657,4 +657,4 @@ public static final class MyUserAppender {
Notice that the return type is a List which we want to contain the user
names. The 1st parameter is the list of names, and then notice the 2nd
-parameter is the incoming `com.foo.User` type.
\ No newline at end of file
+parameter is the incoming `com.foo.User` type.
diff --git a/camel-core/src/main/docs/eips/bean-eip.adoc
b/camel-core/src/main/docs/eips/bean-eip.adoc
index 6745e0b..0ed7c71 100644
--- a/camel-core/src/main/docs/eips/bean-eip.adoc
+++ b/camel-core/src/main/docs/eips/bean-eip.adoc
@@ -25,7 +25,7 @@ The Bean EIP supports 5 options which are listed below:
| *ref* | Sets a reference to a bean to use | | String
| *method* | Sets the method name on the bean to use | | String
| *beanType* | Sets the Class of the bean | | String
-| *cache* | Caches the bean lookup to avoid lookup up bean on every usage. |
true | Boolean
+| *cache* | Caches the bean lookup, to avoid lookup up bean on every usage. |
true | Boolean
| *multiParameterArray* | *Deprecated* Whether the message body is an array
type. | false | Boolean
|===
// eip options: END
@@ -88,4 +88,4 @@ mechanisms in Camel.
* <<class-component,Class>> component
* link:bean-binding.html[Bean Binding]
-* link:bean-integration.html[Bean Integration]
\ No newline at end of file
+* link:bean-integration.html[Bean Integration]
diff --git a/camel-core/src/main/docs/eips/claimCheck-eip.adoc
b/camel-core/src/main/docs/eips/claimCheck-eip.adoc
index 8e8af58..7ee469e 100644
--- a/camel-core/src/main/docs/eips/claimCheck-eip.adoc
+++ b/camel-core/src/main/docs/eips/claimCheck-eip.adoc
@@ -22,9 +22,9 @@ The Claim Check EIP supports 5 options which are listed below:
| Name | Description | Default | Type
| *operation* | *Required* The claim check operation to use. The following
operations is supported: Get - Gets (does not remove) the claim check by the
given key. GetAndRemove - Gets and remove the claim check by the given key. Set
- Sets a new (will override if key already exists) claim check with the given
key. Push - Sets a new claim check on the stack (does not use key). Pop - Gets
the latest claim check from the stack (does not use key). | |
ClaimCheckOperation
| *key* | To use a specific key for claim check id. | | String
-| *filter* | Specified a filter to control what data gets merging data back
from the claim check repository. The following syntax is supported: body - to
aggregate the message body attachments - to aggregate all the message
attachments headers - to aggregate all the message headers header:pattern - to
aggregate all the message headers that matches the pattern. The pattern syntax
is documented by: link EndpointHelpermatchPattern(String String). You can
specify multiple rules separated by [...]
+| *filter* | Specified a filter to control what data gets merging data back
from the claim check repository. The following syntax is supported: body - to
aggregate the message body attachments - to aggregate all the message
attachments headers - to aggregate all the message headers header:pattern - to
aggregate all the message headers that matches the pattern. The pattern syntax
is documented by: link EndpointHelpermatchPattern(String, String). You can
specify multiple rules separated by [...]
| *strategyRef* | To use a custom AggregationStrategy instead of the default
implementation. Notice you cannot use both custom aggregation strategy and
configure data at the same time. | | String
-| *strategyMethodName* | This option can be used to explicit declare the
method name to use when using POJOs as the AggregationStrategy. | | String
+| *strategyMethodName* | This option can be used to explicit declare the
method name to use, when using POJOs as the AggregationStrategy. | | String
|===
// eip options: END
diff --git a/camel-core/src/main/docs/eips/dynamicRouter-eip.adoc
b/camel-core/src/main/docs/eips/dynamicRouter-eip.adoc
index e0535cb..673303e 100644
--- a/camel-core/src/main/docs/eips/dynamicRouter-eip.adoc
+++ b/camel-core/src/main/docs/eips/dynamicRouter-eip.adoc
@@ -24,7 +24,7 @@ The Dynamic Router EIP supports 3 options which are listed
below:
| Name | Description | Default | Type
| *uriDelimiter* | Sets the uri delimiter to use | , | String
| *ignoreInvalidEndpoints* | Ignore the invalidate endpoint exception when try
to create a producer with that endpoint | false | Boolean
-| *cacheSize* | Sets the maximum size used by the
org.apache.camel.impl.ProducerCache which is used to cache and reuse producers
when using this dynamic router when uris are reused. | | Integer
+| *cacheSize* | Sets the maximum size used by the
org.apache.camel.impl.ProducerCache which is used to cache and reuse producers
when using this dynamic router, when uris are reused. | | Integer
|===
// eip options: END
@@ -158,4 +158,4 @@ public class MyDynamicRouter {
// return the next endpoint uri, where to go. Return null to indicate
the end.
}
}
-----
\ No newline at end of file
+----
diff --git a/camel-core/src/main/docs/eips/enrich-eip.adoc
b/camel-core/src/main/docs/eips/enrich-eip.adoc
index e705d2b..ac1dece 100644
--- a/camel-core/src/main/docs/eips/enrich-eip.adoc
+++ b/camel-core/src/main/docs/eips/enrich-eip.adoc
@@ -255,9 +255,9 @@ The Enrich EIP supports 7 options which are listed below:
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *strategyRef* | Refers to an AggregationStrategy to be used to merge the
reply from the external service into a single outgoing message. By default
Camel will use the reply from the external service as outgoing message. | |
String
-| *strategyMethodName* | This option can be used to explicit declare the
method name to use when using POJOs as the AggregationStrategy. | | String
-| *strategyMethodAllowNull* | If this option is false then the aggregate
method is not used if there was no data to enrich. If this option is true then
null values is used as the oldExchange (when no data to enrich) when using
POJOs as the AggregationStrategy. | false | Boolean
+| *strategyRef* | Refers to an AggregationStrategy to be used to merge the
reply from the external service, into a single outgoing message. By default
Camel will use the reply from the external service as outgoing message. | |
String
+| *strategyMethodName* | This option can be used to explicit declare the
method name to use, when using POJOs as the AggregationStrategy. | | String
+| *strategyMethodAllowNull* | If this option is false then the aggregate
method is not used if there was no data to enrich. If this option is true then
null values is used as the oldExchange (when no data to enrich), when using
POJOs as the AggregationStrategy. | false | Boolean
| *aggregateOnException* | If this option is false then the aggregate method
is not used if there was an exception thrown while trying to retrieve the data
to enrich from the resource. Setting this option to true allows end users to
control what to do if there was an exception in the aggregate method. For
example to suppress the exception or set a custom message body etc. | false |
Boolean
| *shareUnitOfWork* | Shares the org.apache.camel.spi.UnitOfWork with the
parent and the resource exchange. Enrich will by default not share unit of work
between the parent exchange and the resource exchange. This means the resource
exchange has its own individual unit of work. | false | Boolean
| *cacheSize* | Sets the maximum size used by the
org.apache.camel.impl.ProducerCache which is used to cache and reuse producer
when uris are reused. | | Integer
@@ -366,4 +366,4 @@ And in XML DSL
</pollEnrich>
<to uri="direct:result"/>
</route>
-----
\ No newline at end of file
+----
diff --git a/camel-core/src/main/docs/eips/hystrix-eip.adoc
b/camel-core/src/main/docs/eips/hystrix-eip.adoc
index fd598ad..ca90c92 100644
--- a/camel-core/src/main/docs/eips/hystrix-eip.adoc
+++ b/camel-core/src/main/docs/eips/hystrix-eip.adoc
@@ -25,7 +25,7 @@ The Hystrix EIP supports 2 options which are listed below:
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *hystrixConfiguration* | Configures the Hystrix EIP Use end when
configuration is complete to return back to the Hystrix EIP. | |
HystrixConfiguration Definition
+| *hystrixConfiguration* | Configures the Hystrix EIP Use end when
configuration is complete, to return back to the Hystrix EIP. | |
HystrixConfiguration Definition
| *hystrixConfigurationRef* | Refers to a Hystrix configuration to use for
configuring the Hystrix EIP. | | String
|===
// eip options: END
@@ -133,4 +133,4 @@ You can also configure Hystrix globally and then refer to
that configuration:
=== Other examples
-You can find an example with the source code:
link:https://github.com/apache/camel/tree/master/examples/camel-example-hystrix[camel-example-hystrix].
\ No newline at end of file
+You can find an example with the source code:
link:https://github.com/apache/camel/tree/master/examples/camel-example-hystrix[camel-example-hystrix].
diff --git a/camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc
b/camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc
index 7a04bd8..4160adc 100644
--- a/camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc
+++ b/camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc
@@ -11,16 +11,16 @@ The Hystrix Configuration EIP supports 31 options which are
listed below:
| Name | Description | Default | Type
| *groupKey* | Sets the group key to use. The default value is CamelHystrix. |
CamelHystrix | String
| *threadPoolKey* | Sets the thread pool key to use. Will by default use the
same value as groupKey has been configured to use. | CamelHystrix | String
-| *circuitBreakerEnabled* | Whether to use a HystrixCircuitBreaker or not. If
false no circuit-breaker logic will be used and all requests permitted. This is
similar in effect to circuitBreakerForceClosed() except that continues tracking
metrics and knowing whether it should be open/closed this property results in
not even instantiating a circuit-breaker. | true | Boolean
+| *circuitBreakerEnabled* | Whether to use a HystrixCircuitBreaker or not. If
false no circuit-breaker logic will be used and all requests permitted. This is
similar in effect to circuitBreakerForceClosed() except that continues tracking
metrics and knowing whether it should be open/closed, this property results in
not even instantiating a circuit-breaker. | true | Boolean
| *circuitBreakerError ThresholdPercentage* | Error percentage threshold (as
whole number such as 50) at which point the circuit breaker will trip open and
reject requests. It will stay tripped for the duration defined in
circuitBreakerSleepWindowInMilliseconds; The error percentage this is compared
against comes from HystrixCommandMetrics.getHealthCounts(). | 50 | Integer
| *circuitBreakerForceClosed* | If true the
HystrixCircuitBreakerallowRequest() will always return true to allow requests
regardless of the error percentage from
HystrixCommandMetrics.getHealthCounts(). The circuitBreakerForceOpen() property
takes precedence so if it set to true this property does nothing. | false |
Boolean
-| *circuitBreakerForceOpen* | If true the HystrixCircuitBreaker.allowRequest()
will always return false causing the circuit to be open (tripped) and reject
all requests. This property takes precedence over circuitBreakerForceClosed();
| false | Boolean
+| *circuitBreakerForceOpen* | If true the HystrixCircuitBreaker.allowRequest()
will always return false, causing the circuit to be open (tripped) and reject
all requests. This property takes precedence over circuitBreakerForceClosed();
| false | Boolean
| *circuitBreakerRequestVolume Threshold* | Minimum number of requests in the
metricsRollingStatisticalWindowInMilliseconds() that must exist before the
HystrixCircuitBreaker will trip. If below this number the circuit will not trip
regardless of error percentage. | 20 | Integer
| *circuitBreakerSleepWindow InMilliseconds* | The time in milliseconds after
a HystrixCircuitBreaker trips open that it should wait before trying requests
again. | 5000 | Integer
| *executionIsolationSemaphore MaxConcurrentRequests* | Number of concurrent
requests permitted to HystrixCommand.run(). Requests beyond the concurrent
limit will be rejected. Applicable only when executionIsolationStrategy ==
SEMAPHORE. | 20 | Integer
| *executionIsolationStrategy* | What isolation strategy HystrixCommand.run()
will be executed with. If THREAD then it will be executed on a separate thread
and concurrent requests limited by the number of threads in the thread-pool. If
SEMAPHORE then it will be executed on the calling thread and concurrent
requests limited by the semaphore count. | THREAD | String
| *executionIsolationThread InterruptOnTimeout* | Whether the execution thread
should attempt an interrupt (using link Futurecancel) when a thread times out.
Applicable only when executionIsolationStrategy() == THREAD. | true | Boolean
-| *executionTimeoutIn Milliseconds* | Time in milliseconds at which point the
command will timeout and halt execution. If link
executionIsolationThreadInterruptOnTimeout == true and the command is
thread-isolated the executing thread will be interrupted. If the command is
semaphore-isolated and a HystrixObservableCommand that command will get
unsubscribed. | 1000 | Integer
+| *executionTimeoutIn Milliseconds* | Time in milliseconds at which point the
command will timeout and halt execution. If link
executionIsolationThreadInterruptOnTimeout == true and the command is
thread-isolated, the executing thread will be interrupted. If the command is
semaphore-isolated and a HystrixObservableCommand, that command will get
unsubscribed. | 1000 | Integer
| *executionTimeoutEnabled* | Whether the timeout mechanism is enabled for
this command | true | Boolean
| *fallbackIsolationSemaphore MaxConcurrentRequests* | Number of concurrent
requests permitted to HystrixCommand.getFallback(). Requests beyond the
concurrent limit will fail-fast and not attempt retrieving a fallback. | 10 |
Integer
| *fallbackEnabled* | Whether HystrixCommand.getFallback() should be attempted
when failure occurs. | true | Boolean
@@ -29,16 +29,16 @@ The Hystrix Configuration EIP supports 31 options which are
listed below:
| *metricsRollingPercentile Enabled* | Whether percentile metrics should be
captured using HystrixRollingPercentile inside HystrixCommandMetrics. | true |
Boolean
| *metricsRollingPercentile WindowInMilliseconds* | Duration of percentile
rolling window in milliseconds. This is passed into HystrixRollingPercentile
inside HystrixCommandMetrics. | 10000 | Integer
| *metricsRollingPercentile WindowBuckets* | Number of buckets the rolling
percentile window is broken into. This is passed into HystrixRollingPercentile
inside HystrixCommandMetrics. | 6 | Integer
-| *metricsRollingStatistical WindowInMilliseconds* | This property sets the
duration of the statistical rolling window in milliseconds. This is how long
metrics are kept for the thread pool. The window is divided into buckets and
rolls by those increments. | 10000 | Integer
+| *metricsRollingStatistical WindowInMilliseconds* | This property sets the
duration of the statistical rolling window, in milliseconds. This is how long
metrics are kept for the thread pool. The window is divided into buckets and
rolls by those increments. | 10000 | Integer
| *metricsRollingStatistical WindowBuckets* | Number of buckets the rolling
statistical window is broken into. This is passed into HystrixRollingNumber
inside HystrixCommandMetrics. | 10 | Integer
| *requestLogEnabled* | Whether HystrixCommand execution and events should be
logged to HystrixRequestLog. | true | Boolean
| *corePoolSize* | Core thread-pool size that gets passed to link
java.util.concurrent.ThreadPoolExecutorsetCorePoolSize(int) | 10 | Integer
| *maximumSize* | Maximum thread-pool size that gets passed to link
ThreadPoolExecutorsetMaximumPoolSize(int). This is the maximum amount of
concurrency that can be supported without starting to reject HystrixCommands.
Please note that this setting only takes effect if you also set
allowMaximumSizeToDivergeFromCoreSize | 10 | Integer
-| *keepAliveTime* | Keep-alive time in minutes that gets passed to link
ThreadPoolExecutorsetKeepAliveTime(long TimeUnit) | 1 | Integer
-| *maxQueueSize* | Max queue size that gets passed to BlockingQueue in
HystrixConcurrencyStrategy.getBlockingQueue(int) This should only affect the
instantiation of a threadpool - it is not eliglible to change a queue size on
the fly. For that use queueSizeRejectionThreshold(). | -1 | Integer
+| *keepAliveTime* | Keep-alive time in minutes that gets passed to link
ThreadPoolExecutorsetKeepAliveTime(long, TimeUnit) | 1 | Integer
+| *maxQueueSize* | Max queue size that gets passed to BlockingQueue in
HystrixConcurrencyStrategy.getBlockingQueue(int) This should only affect the
instantiation of a threadpool - it is not eliglible to change a queue size on
the fly. For that, use queueSizeRejectionThreshold(). | -1 | Integer
| *queueSizeRejectionThreshold* | Queue size rejection threshold is an
artificial max size at which rejections will occur even if link maxQueueSize
has not been reached. This is done because the link maxQueueSize of a
BlockingQueue can not be dynamically changed and we want to support dynamically
changing the queue size that affects rejections. This is used by HystrixCommand
when queuing a thread for execution. | 5 | Integer
| *threadPoolRollingNumber StatisticalWindowIn Milliseconds* | Duration of
statistical rolling window in milliseconds. This is passed into
HystrixRollingNumber inside each HystrixThreadPoolMetrics instance. | 10000 |
Integer
| *threadPoolRollingNumber StatisticalWindowBuckets* | Number of buckets the
rolling statistical window is broken into. This is passed into
HystrixRollingNumber inside each HystrixThreadPoolMetrics instance. | 10 |
Integer
-| *allowMaximumSizeToDiverge FromCoreSize* | Allows the configuration for
maximumSize to take effect. That value can then be equal to or higher than
coreSize | false | Boolean
+| *allowMaximumSizeToDiverge FromCoreSize* | Allows the configuration for
maximumSize to take effect. That value can then be equal to, or higher, than
coreSize | false | Boolean
|===
-// eip options: END
\ No newline at end of file
+// eip options: END
diff --git a/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
b/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
index ffd38e4..18cfef2 100644
--- a/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
+++ b/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
@@ -46,8 +46,8 @@ The Idempotent Consumer EIP supports 5 options which are
listed below:
| Name | Description | Default | Type
| *messageIdRepositoryRef* | *Required* Sets the reference name of the message
id repository | | String
| *eager* | Sets whether to eagerly add the key to the idempotent repository
or wait until the exchange is complete. Eager is default enabled. | true |
Boolean
-| *completionEager* | Sets whether to complete the idempotent consumer eager
or when the exchange is done. If this option is true to complete eager then the
idempotent consumer will trigger its completion when the exchange reached the
end of the block of the idempotent consumer pattern. So if the exchange is
continued routed after the block ends then whatever happens there does not
affect the state. If this option is false (default) to not complete eager then
the idempotent consumer will [...]
+| *completionEager* | Sets whether to complete the idempotent consumer eager
or when the exchange is done. If this option is true to complete eager, then
the idempotent consumer will trigger its completion when the exchange reached
the end of the block of the idempotent consumer pattern. So if the exchange is
continued routed after the block ends, then whatever happens there does not
affect the state. If this option is false (default) to not complete eager, then
the idempotent consumer w [...]
| *skipDuplicate* | Sets whether to skip duplicates or not. The default
behavior is to skip duplicates. A duplicate message would have the Exchange
property link org.apache.camel.ExchangeDUPLICATE_MESSAGE set to a link
BooleanTRUE value. A none duplicate message will not have this property set. |
true | Boolean
| *removeOnFailure* | Sets whether to remove or keep the key on failure. The
default behavior is to remove the key on failure. | true | Boolean
|===
-// eip options: END
\ No newline at end of file
+// eip options: END
diff --git a/camel-core/src/main/docs/eips/loop-eip.adoc
b/camel-core/src/main/docs/eips/loop-eip.adoc
index 7abee7f..070b2e0 100644
--- a/camel-core/src/main/docs/eips/loop-eip.adoc
+++ b/camel-core/src/main/docs/eips/loop-eip.adoc
@@ -18,7 +18,7 @@ The Loop EIP supports 2 options which are listed below:
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *copy* | If the copy attribute is true a copy of the input Exchange is used
for each iteration. That means each iteration will start from a copy of the
same message. By default loop will loop the same exchange all over so each
iteration may have different message content. | false | Boolean
+| *copy* | If the copy attribute is true, a copy of the input Exchange is used
for each iteration. That means each iteration will start from a copy of the
same message. By default loop will loop the same exchange all over, so each
iteration may have different message content. | false | Boolean
| *doWhile* | Enables the while loop that loops until the predicate evaluates
to false or null. | false | Boolean
|===
// eip options: END
@@ -170,4 +170,4 @@ And the same example in XML:
</route>
----
-Notice in XML that the while loop is turned on using the *doWhile* attribute.
\ No newline at end of file
+Notice in XML that the while loop is turned on using the *doWhile* attribute.
diff --git a/camel-core/src/main/docs/eips/multicast-eip.adoc
b/camel-core/src/main/docs/eips/multicast-eip.adoc
index 159b5d3..7727f95 100644
--- a/camel-core/src/main/docs/eips/multicast-eip.adoc
+++ b/camel-core/src/main/docs/eips/multicast-eip.adoc
@@ -15,18 +15,18 @@ The Multicast EIP supports 12 options which are listed
below:
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *parallelProcessing* | If enabled then sending messages to the multicasts
occurs concurrently. Note the caller thread will still wait until all messages
has been fully processed before it continues. Its only the sending and
processing the replies from the multicasts which happens concurrently. | false
| Boolean
-| *strategyRef* | Refers to an AggregationStrategy to be used to assemble the
replies from the multicasts into a single outgoing message from the Multicast.
By default Camel will use the last reply as the outgoing message. You can also
use a POJO as the AggregationStrategy | | String
-| *strategyMethodName* | This option can be used to explicit declare the
method name to use when using POJOs as the AggregationStrategy. | | String
-| *strategyMethodAllowNull* | If this option is false then the aggregate
method is not used if there was no data to enrich. If this option is true then
null values is used as the oldExchange (when no data to enrich) when using
POJOs as the AggregationStrategy | false | Boolean
-| *executorServiceRef* | Refers to a custom Thread Pool to be used for
parallel processing. Notice if you set this option then parallel processing is
automatic implied and you do not have to enable that option as well. | | String
-| *streaming* | If enabled then Camel will process replies out-of-order eg in
the order they come back. If disabled Camel will process replies in the same
order as defined by the multicast. | false | Boolean
-| *stopOnException* | Will now stop further processing if an exception or
failure occurred during processing of an org.apache.camel.Exchange and the
caused exception will be thrown. Will also stop if processing the exchange
failed (has a fault message) or an exception was thrown and handled by the
error handler (such as using onException). In all situations the multicast will
stop further processing. This is the same behavior as in pipeline which is used
by the routing engine. The defaul [...]
-| *timeout* | Sets a total timeout specified in millis when using parallel
processing. If the Multicast hasn't been able to send and process all replies
within the given timeframe then the timeout triggers and the Multicast breaks
out and continues. Notice if you provide a TimeoutAwareAggregationStrategy then
the timeout method is invoked before breaking out. If the timeout is reached
with running tasks still remaining certain tasks for which it is difficult for
Camel to shut down in a g [...]
-| *onPrepareRef* | Uses the Processor when preparing the
org.apache.camel.Exchange to be send. This can be used to deep-clone messages
that should be send or any custom logic needed before the exchange is send. |
| String
+| *parallelProcessing* | If enabled then sending messages to the multicasts
occurs concurrently. Note the caller thread will still wait until all messages
has been fully processed, before it continues. Its only the sending and
processing the replies from the multicasts which happens concurrently. | false
| Boolean
+| *strategyRef* | Refers to an AggregationStrategy to be used to assemble the
replies from the multicasts, into a single outgoing message from the Multicast.
By default Camel will use the last reply as the outgoing message. You can also
use a POJO as the AggregationStrategy | | String
+| *strategyMethodName* | This option can be used to explicit declare the
method name to use, when using POJOs as the AggregationStrategy. | | String
+| *strategyMethodAllowNull* | If this option is false then the aggregate
method is not used if there was no data to enrich. If this option is true then
null values is used as the oldExchange (when no data to enrich), when using
POJOs as the AggregationStrategy | false | Boolean
+| *executorServiceRef* | Refers to a custom Thread Pool to be used for
parallel processing. Notice if you set this option, then parallel processing is
automatic implied, and you do not have to enable that option as well. | |
String
+| *streaming* | If enabled then Camel will process replies out-of-order, eg in
the order they come back. If disabled, Camel will process replies in the same
order as defined by the multicast. | false | Boolean
+| *stopOnException* | Will now stop further processing if an exception or
failure occurred during processing of an org.apache.camel.Exchange and the
caused exception will be thrown. Will also stop if processing the exchange
failed (has a fault message) or an exception was thrown and handled by the
error handler (such as using onException). In all situations the multicast will
stop further processing. This is the same behavior as in pipeline, which is
used by the routing engine. The defau [...]
+| *timeout* | Sets a total timeout specified in millis, when using parallel
processing. If the Multicast hasn't been able to send and process all replies
within the given timeframe, then the timeout triggers and the Multicast breaks
out and continues. Notice if you provide a TimeoutAwareAggregationStrategy then
the timeout method is invoked before breaking out. If the timeout is reached
with running tasks still remaining, certain tasks for which it is difficult for
Camel to shut down in [...]
+| *onPrepareRef* | Uses the Processor when preparing the
org.apache.camel.Exchange to be send. This can be used to deep-clone messages
that should be send, or any custom logic needed before the exchange is send. |
| String
| *shareUnitOfWork* | Shares the org.apache.camel.spi.UnitOfWork with the
parent and each of the sub messages. Multicast will by default not share unit
of work between the parent exchange and each multicasted exchange. This means
each sub exchange has its own individual unit of work. | false | Boolean
| *parallelAggregate* | If enabled then the aggregate method on
AggregationStrategy can be called concurrently. Notice that this would require
the implementation of AggregationStrategy to be implemented as thread-safe. By
default this is false meaning that Camel synchronizes the call to the aggregate
method. Though in some use-cases this can be used to archive higher performance
when the AggregationStrategy is implemented as thread-safe. | false | Boolean
-| *stopOnAggregateException* | If enabled unwind exceptions occurring at
aggregation time to the error handler when parallelProcessing is used.
Currently aggregation time exceptions do not stop the route processing when
parallelProcessing is used. Enabling this option allows to work around this
behavior. The default value is false for the sake of backward compatibility. |
false | Boolean
+| *stopOnAggregateException* | If enabled, unwind exceptions occurring at
aggregation time to the error handler when parallelProcessing is used.
Currently, aggregation time exceptions do not stop the route processing when
parallelProcessing is used. Enabling this option allows to work around this
behavior. The default value is false for the sake of backward compatibility. |
false | Boolean
|===
// eip options: END
diff --git a/camel-core/src/main/docs/eips/recipientList-eip.adoc
b/camel-core/src/main/docs/eips/recipientList-eip.adoc
index 9382324..6f23a84 100644
--- a/camel-core/src/main/docs/eips/recipientList-eip.adoc
+++ b/camel-core/src/main/docs/eips/recipientList-eip.adoc
@@ -15,21 +15,21 @@ The Recipient List EIP supports 15 options which are listed
below:
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *delimiter* | Delimiter used if the Expression returned multiple endpoints.
Can be turned off using the value false. The default value is | , | String
-| *parallelProcessing* | If enabled then sending messages to the recipients
occurs concurrently. Note the caller thread will still wait until all messages
has been fully processed before it continues. Its only the sending and
processing the replies from the recipients which happens concurrently. | false
| Boolean
-| *strategyRef* | Sets a reference to the AggregationStrategy to be used to
assemble the replies from the recipients into a single outgoing message from
the RecipientList. By default Camel will use the last reply as the outgoing
message. You can also use a POJO as the AggregationStrategy | | String
-| *strategyMethodName* | This option can be used to explicit declare the
method name to use when using POJOs as the AggregationStrategy. | | String
-| *strategyMethodAllowNull* | If this option is false then the aggregate
method is not used if there was no data to enrich. If this option is true then
null values is used as the oldExchange (when no data to enrich) when using
POJOs as the AggregationStrategy | false | Boolean
-| *executorServiceRef* | Refers to a custom Thread Pool to be used for
parallel processing. Notice if you set this option then parallel processing is
automatic implied and you do not have to enable that option as well. | | String
-| *stopOnException* | Will now stop further processing if an exception or
failure occurred during processing of an org.apache.camel.Exchange and the
caused exception will be thrown. Will also stop if processing the exchange
failed (has a fault message) or an exception was thrown and handled by the
error handler (such as using onException). In all situations the recipient list
will stop further processing. This is the same behavior as in pipeline which is
used by the routing engine. The d [...]
+| *delimiter* | Delimiter used if the Expression returned multiple endpoints.
Can be turned off using the value false. The default value is , | , | String
+| *parallelProcessing* | If enabled then sending messages to the recipients
occurs concurrently. Note the caller thread will still wait until all messages
has been fully processed, before it continues. Its only the sending and
processing the replies from the recipients which happens concurrently. | false
| Boolean
+| *strategyRef* | Sets a reference to the AggregationStrategy to be used to
assemble the replies from the recipients, into a single outgoing message from
the RecipientList. By default Camel will use the last reply as the outgoing
message. You can also use a POJO as the AggregationStrategy | | String
+| *strategyMethodName* | This option can be used to explicit declare the
method name to use, when using POJOs as the AggregationStrategy. | | String
+| *strategyMethodAllowNull* | If this option is false then the aggregate
method is not used if there was no data to enrich. If this option is true then
null values is used as the oldExchange (when no data to enrich), when using
POJOs as the AggregationStrategy | false | Boolean
+| *executorServiceRef* | Refers to a custom Thread Pool to be used for
parallel processing. Notice if you set this option, then parallel processing is
automatic implied, and you do not have to enable that option as well. | |
String
+| *stopOnException* | Will now stop further processing if an exception or
failure occurred during processing of an org.apache.camel.Exchange and the
caused exception will be thrown. Will also stop if processing the exchange
failed (has a fault message) or an exception was thrown and handled by the
error handler (such as using onException). In all situations the recipient list
will stop further processing. This is the same behavior as in pipeline, which
is used by the routing engine. The [...]
| *ignoreInvalidEndpoints* | Ignore the invalidate endpoint exception when try
to create a producer with that endpoint | false | Boolean
-| *streaming* | If enabled then Camel will process replies out-of-order eg in
the order they come back. If disabled Camel will process replies in the same
order as defined by the recipient list. | false | Boolean
-| *timeout* | Sets a total timeout specified in millis when using parallel
processing. If the Recipient List hasn't been able to send and process all
replies within the given timeframe then the timeout triggers and the Recipient
List breaks out and continues. Notice if you provide a
TimeoutAwareAggregationStrategy then the timeout method is invoked before
breaking out. If the timeout is reached with running tasks still remaining
certain tasks for which it is difficult for Camel to shut d [...]
-| *onPrepareRef* | Uses the Processor when preparing the
org.apache.camel.Exchange to be send. This can be used to deep-clone messages
that should be send or any custom logic needed before the exchange is send. |
| String
+| *streaming* | If enabled then Camel will process replies out-of-order, eg in
the order they come back. If disabled, Camel will process replies in the same
order as defined by the recipient list. | false | Boolean
+| *timeout* | Sets a total timeout specified in millis, when using parallel
processing. If the Recipient List hasn't been able to send and process all
replies within the given timeframe, then the timeout triggers and the Recipient
List breaks out and continues. Notice if you provide a
TimeoutAwareAggregationStrategy then the timeout method is invoked before
breaking out. If the timeout is reached with running tasks still remaining,
certain tasks for which it is difficult for Camel to shu [...]
+| *onPrepareRef* | Uses the Processor when preparing the
org.apache.camel.Exchange to be send. This can be used to deep-clone messages
that should be send, or any custom logic needed before the exchange is send. |
| String
| *shareUnitOfWork* | Shares the org.apache.camel.spi.UnitOfWork with the
parent and each of the sub messages. Recipient List will by default not share
unit of work between the parent exchange and each recipient exchange. This
means each sub exchange has its own individual unit of work. | false | Boolean
-| *cacheSize* | Sets the maximum size used by the
org.apache.camel.impl.ProducerCache which is used to cache and reuse producers
when using this recipient list when uris are reused. | | Integer
+| *cacheSize* | Sets the maximum size used by the
org.apache.camel.impl.ProducerCache which is used to cache and reuse producers
when using this recipient list, when uris are reused. | | Integer
| *parallelAggregate* | If enabled then the aggregate method on
AggregationStrategy can be called concurrently. Notice that this would require
the implementation of AggregationStrategy to be implemented as thread-safe. By
default this is false meaning that Camel synchronizes the call to the aggregate
method. Though in some use-cases this can be used to archive higher performance
when the AggregationStrategy is implemented as thread-safe. | false | Boolean
-| *stopOnAggregateException* | If enabled unwind exceptions occurring at
aggregation time to the error handler when parallelProcessing is used.
Currently aggregation time exceptions do not stop the route processing when
parallelProcessing is used. Enabling this option allows to work around this
behavior. The default value is false for the sake of backward compatibility. |
false | Boolean
+| *stopOnAggregateException* | If enabled, unwind exceptions occurring at
aggregation time to the error handler when parallelProcessing is used.
Currently, aggregation time exceptions do not stop the route processing when
parallelProcessing is used. Enabling this option allows to work around this
behavior. The default value is false for the sake of backward compatibility. |
false | Boolean
|===
// eip options: END
@@ -373,4 +373,4 @@ be `InOnly` when the message is routed to the `file:outbox
endpoint`.
If you want to alter the exchange pattern permanently then use the
`.setExchangePattern` option.
See more details at Request Reply and Event Message EIPs.
-====
\ No newline at end of file
+====
diff --git a/camel-core/src/main/docs/eips/routingSlip-eip.adoc
b/camel-core/src/main/docs/eips/routingSlip-eip.adoc
index 4115457..ed253f0 100644
--- a/camel-core/src/main/docs/eips/routingSlip-eip.adoc
+++ b/camel-core/src/main/docs/eips/routingSlip-eip.adoc
@@ -16,7 +16,7 @@ The Routing Slip EIP supports 3 options which are listed
below:
| Name | Description | Default | Type
| *uriDelimiter* | Sets the uri delimiter to use | , | String
| *ignoreInvalidEndpoints* | Ignore the invalidate endpoint exception when try
to create a producer with that endpoint | false | Boolean
-| *cacheSize* | Sets the maximum size used by the
org.apache.camel.impl.ProducerCache which is used to cache and reuse producers
when using this routing slip when uris are reused. | | Integer
+| *cacheSize* | Sets the maximum size used by the
org.apache.camel.impl.ProducerCache which is used to cache and reuse producers
when using this routing slip, when uris are reused. | | Integer
|===
// eip options: END
@@ -111,4 +111,4 @@ And in Spring XML its an attribute on the recipient list
tag.
For further examples of this pattern in use you could look at the routing slip
test cases.
=== 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
+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.
diff --git a/camel-core/src/main/docs/eips/saga-eip.adoc
b/camel-core/src/main/docs/eips/saga-eip.adoc
index db7ade9..3c503f5 100644
--- a/camel-core/src/main/docs/eips/saga-eip.adoc
+++ b/camel-core/src/main/docs/eips/saga-eip.adoc
@@ -29,11 +29,11 @@ The Saga EIP supports 6 options which are listed below:
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *propagation* | Set the Saga propagation mode (REQUIRED REQUIRES_NEW
MANDATORY SUPPORTS NOT_SUPPORTED NEVER). | REQUIRED | SagaPropagation
-| *completionMode* | Determine how the saga should be considered complete.
When set to AUTO the saga is completed when the exchange that initiates the
saga is processed successfully or compensated when it completes exceptionally.
When set to MANUAL the user must complete or compensate the saga using the
saga:complete or saga:compensate endpoints. | AUTO | SagaCompletionMode
-| *timeoutInMilliseconds* | Set the maximum amount of time for the Saga. After
the timeout is expired the saga will be compensated automatically (unless a
different decision has been taken in the meantime). | | Long
-| *compensation* | The compensation endpoint URI that must be called to
compensate all changes done in the route. The route corresponding to the
compensation URI must perform compensation and complete without error. If
errors occur during compensation the saga service may call again the
compensation URI to retry. | | SagaActionUri Definition
-| *completion* | The completion endpoint URI that will be called when the Saga
is completed successfully. The route corresponding to the completion URI must
perform completion tasks and terminate without error. If errors occur during
completion the saga service may call again the completion URI to retry. | |
SagaActionUri Definition
+| *propagation* | Set the Saga propagation mode (REQUIRED, REQUIRES_NEW,
MANDATORY, SUPPORTS, NOT_SUPPORTED, NEVER). | REQUIRED | SagaPropagation
+| *completionMode* | Determine how the saga should be considered complete.
When set to AUTO, the saga is completed when the exchange that initiates the
saga is processed successfully, or compensated when it completes exceptionally.
When set to MANUAL, the user must complete or compensate the saga using the
saga:complete or saga:compensate endpoints. | AUTO | SagaCompletionMode
+| *timeoutInMilliseconds* | Set the maximum amount of time for the Saga. After
the timeout is expired, the saga will be compensated automatically (unless a
different decision has been taken in the meantime). | | Long
+| *compensation* | The compensation endpoint URI that must be called to
compensate all changes done in the route. The route corresponding to the
compensation URI must perform compensation and complete without error. If
errors occur during compensation, the saga service may call again the
compensation URI to retry. | | SagaActionUri Definition
+| *completion* | The completion endpoint URI that will be called when the Saga
is completed successfully. The route corresponding to the completion URI must
perform completion tasks and terminate without error. If errors occur during
completion, the saga service may call again the completion URI to retry. | |
SagaActionUri Definition
| *option* | Allows to save properties of the current exchange in order to
re-use them in a compensation/completion callback route. Options are usually
helpful e.g. to store and retrieve identifiers of objects that should be
deleted in compensating actions. Option values will be transformed into input
headers of the compensation/completion exchange. | | List
|===
// eip options: END
@@ -448,4 +448,4 @@ The following snipped shows an example:
<to uri="direct:action1" />
<to uri="direct:action2" />
</route>
-----
\ No newline at end of file
+----
diff --git a/camel-core/src/main/docs/eips/sample-eip.adoc
b/camel-core/src/main/docs/eips/sample-eip.adoc
index 8b3dd80..cbd4263 100644
--- a/camel-core/src/main/docs/eips/sample-eip.adoc
+++ b/camel-core/src/main/docs/eips/sample-eip.adoc
@@ -16,7 +16,7 @@ The Sample EIP supports 3 options which are listed below:
| Name | Description | Default | Type
| *samplePeriod* | Sets the sample period during which only a single Exchange
will pass through. | 1 | Long
| *messageFrequency* | Sets the sample message count which only a single
Exchange will pass through after this many received. | | Long
-| *units* | Sets the time units for the sample period defaulting to seconds. |
SECONDS | TimeUnit
+| *units* | Sets the time units for the sample period, defaulting to seconds.
| SECONDS | TimeUnit
|===
// eip options: END
@@ -83,4 +83,4 @@ And since it uses a default of 1 second you can omit this
configuration in case
<to uri="mock:result"/>
</sample>
</route>
-----
\ No newline at end of file
+----
diff --git a/camel-core/src/main/docs/eips/split-eip.adoc
b/camel-core/src/main/docs/eips/split-eip.adoc
index 5735ef3..5050542 100644
--- a/camel-core/src/main/docs/eips/split-eip.adoc
+++ b/camel-core/src/main/docs/eips/split-eip.adoc
@@ -15,18 +15,18 @@ The Split EIP supports 12 options which are listed below:
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *parallelProcessing* | If enabled then processing each splitted messages
occurs concurrently. Note the caller thread will still wait until all messages
has been fully processed before it continues. Its only processing the sub
messages from the splitter which happens concurrently. | false | Boolean
-| *strategyRef* | Sets a reference to the AggregationStrategy to be used to
assemble the replies from the splitted messages into a single outgoing message
from the Splitter. By default Camel will use the original incoming message to
the splitter (leave it unchanged). You can also use a POJO as the
AggregationStrategy | | String
-| *strategyMethodName* | This option can be used to explicit declare the
method name to use when using POJOs as the AggregationStrategy. | | String
-| *strategyMethodAllowNull* | If this option is false then the aggregate
method is not used if there was no data to enrich. If this option is true then
null values is used as the oldExchange (when no data to enrich) when using
POJOs as the AggregationStrategy | false | Boolean
-| *executorServiceRef* | Refers to a custom Thread Pool to be used for
parallel processing. Notice if you set this option then parallel processing is
automatic implied and you do not have to enable that option as well. | | String
-| *streaming* | When in streaming mode then the splitter splits the original
message on-demand and each splitted message is processed one by one. This
reduces memory usage as the splitter do not split all the messages first but
then we do not know the total size and therefore the link
org.apache.camel.ExchangeSPLIT_SIZE is empty. In non-streaming mode (default)
the splitter will split each message first to know the total size and then
process each message one by one. This requires to kee [...]
-| *stopOnException* | Will now stop further processing if an exception or
failure occurred during processing of an org.apache.camel.Exchange and the
caused exception will be thrown. Will also stop if processing the exchange
failed (has a fault message) or an exception was thrown and handled by the
error handler (such as using onException). In all situations the splitter will
stop further processing. This is the same behavior as in pipeline which is used
by the routing engine. The default [...]
-| *timeout* | Sets a total timeout specified in millis when using parallel
processing. If the Splitter hasn't been able to split and process all the sub
messages within the given timeframe then the timeout triggers and the Splitter
breaks out and continues. Notice if you provide a
TimeoutAwareAggregationStrategy then the timeout method is invoked before
breaking out. If the timeout is reached with running tasks still remaining
certain tasks for which it is difficult for Camel to shut dow [...]
-| *onPrepareRef* | Uses the Processor when preparing the
org.apache.camel.Exchange to be send. This can be used to deep-clone messages
that should be send or any custom logic needed before the exchange is send. |
| String
+| *parallelProcessing* | If enabled then processing each splitted messages
occurs concurrently. Note the caller thread will still wait until all messages
has been fully processed, before it continues. Its only processing the sub
messages from the splitter which happens concurrently. | false | Boolean
+| *strategyRef* | Sets a reference to the AggregationStrategy to be used to
assemble the replies from the splitted messages, into a single outgoing message
from the Splitter. By default Camel will use the original incoming message to
the splitter (leave it unchanged). You can also use a POJO as the
AggregationStrategy | | String
+| *strategyMethodName* | This option can be used to explicit declare the
method name to use, when using POJOs as the AggregationStrategy. | | String
+| *strategyMethodAllowNull* | If this option is false then the aggregate
method is not used if there was no data to enrich. If this option is true then
null values is used as the oldExchange (when no data to enrich), when using
POJOs as the AggregationStrategy | false | Boolean
+| *executorServiceRef* | Refers to a custom Thread Pool to be used for
parallel processing. Notice if you set this option, then parallel processing is
automatic implied, and you do not have to enable that option as well. | |
String
+| *streaming* | When in streaming mode, then the splitter splits the original
message on-demand, and each splitted message is processed one by one. This
reduces memory usage as the splitter do not split all the messages first, but
then we do not know the total size, and therefore the link
org.apache.camel.ExchangeSPLIT_SIZE is empty. In non-streaming mode (default)
the splitter will split each message first, to know the total size, and then
process each message one by one. This requires [...]
+| *stopOnException* | Will now stop further processing if an exception or
failure occurred during processing of an org.apache.camel.Exchange and the
caused exception will be thrown. Will also stop if processing the exchange
failed (has a fault message) or an exception was thrown and handled by the
error handler (such as using onException). In all situations the splitter will
stop further processing. This is the same behavior as in pipeline, which is
used by the routing engine. The defaul [...]
+| *timeout* | Sets a total timeout specified in millis, when using parallel
processing. If the Splitter hasn't been able to split and process all the sub
messages within the given timeframe, then the timeout triggers and the Splitter
breaks out and continues. Notice if you provide a
TimeoutAwareAggregationStrategy then the timeout method is invoked before
breaking out. If the timeout is reached with running tasks still remaining,
certain tasks for which it is difficult for Camel to shut [...]
+| *onPrepareRef* | Uses the Processor when preparing the
org.apache.camel.Exchange to be send. This can be used to deep-clone messages
that should be send, or any custom logic needed before the exchange is send. |
| String
| *shareUnitOfWork* | Shares the org.apache.camel.spi.UnitOfWork with the
parent and each of the sub messages. Splitter will by default not share unit of
work between the parent exchange and each splitted exchange. This means each
splitted exchange has its own individual unit of work. | false | Boolean
| *parallelAggregate* | If enabled then the aggregate method on
AggregationStrategy can be called concurrently. Notice that this would require
the implementation of AggregationStrategy to be implemented as thread-safe. By
default this is false meaning that Camel synchronizes the call to the aggregate
method. Though in some use-cases this can be used to archive higher performance
when the AggregationStrategy is implemented as thread-safe. | false | Boolean
-| *stopOnAggregateException* | If enabled unwind exceptions occurring at
aggregation time to the error handler when parallelProcessing is used.
Currently aggregation time exceptions do not stop the route processing when
parallelProcessing is used. Enabling this option allows to work around this
behavior. The default value is false for the sake of backward compatibility. |
false | Boolean
+| *stopOnAggregateException* | If enabled, unwind exceptions occurring at
aggregation time to the error handler when parallelProcessing is used.
Currently, aggregation time exceptions do not stop the route processing when
parallelProcessing is used. Enabling this option allows to work around this
behavior. The default value is false for the sake of backward compatibility. |
false | Boolean
|===
// eip options: END
@@ -685,4 +685,4 @@ Using this from XML DSL is just as easy as you just have to
set the `shareUnitOf
.Implementation of shared unit of work
====
So in reality the unit of work is not shared as a single object instance.
Instead `SubUnitOfWork` is attached to their parent, and issues callback to the
parent about their status (commit or rollback). This may be refactored in Camel
3.0 where larger API changes can be done.
-====
\ No newline at end of file
+====
diff --git a/camel-core/src/main/docs/eips/stream-config-eip.adoc
b/camel-core/src/main/docs/eips/stream-config-eip.adoc
index 23ffa7e..3dcb73b 100644
--- a/camel-core/src/main/docs/eips/stream-config-eip.adoc
+++ b/camel-core/src/main/docs/eips/stream-config-eip.adoc
@@ -14,6 +14,6 @@ The Stream-config EIP supports 6 options which are listed
below:
| *deliveryAttemptInterval* | Sets the interval in milli seconds the stream
resequencer will at most wait while waiting for condition of being able to
deliver. | 1000 | Long
| *ignoreInvalidExchanges* | Whether to ignore invalid exchanges | false |
Boolean
| *comparatorRef* | To use a custom comparator | | String
-| *rejectOld* | If true throws an exception when messages older than the last
delivered message are processed | false | Boolean
+| *rejectOld* | If true, throws an exception when messages older than the last
delivered message are processed | false | Boolean
|===
-// eip options: END
\ No newline at end of file
+// eip options: END
diff --git a/camel-core/src/main/docs/eips/threads-eip.adoc
b/camel-core/src/main/docs/eips/threads-eip.adoc
index 8a5e71e..c64bed3 100644
--- a/camel-core/src/main/docs/eips/threads-eip.adoc
+++ b/camel-core/src/main/docs/eips/threads-eip.adoc
@@ -20,7 +20,7 @@ The Threads EIP supports 10 options which are listed below:
| *allowCoreThreadTimeOut* | Whether idle core threads is allowed to timeout
and therefore can shrink the pool size below the core pool size Is by default
false | false | Boolean
| *threadName* | Sets the thread name to use. | Threads | String
| *rejectedPolicy* | Sets the handler for tasks which cannot be executed by
the thread pool. | | ThreadPoolRejected Policy
-| *callerRunsWhenRejected* | Whether or not to use as caller runs as fallback
when a task is rejected being added to the thread pool (when its full). This is
only used as fallback if no rejectedPolicy has been configured or the thread
pool has no configured rejection handler. Is by default true | true | Boolean
+| *callerRunsWhenRejected* | Whether or not to use as caller runs as fallback
when a task is rejected being added to the thread pool (when its full). This is
only used as fallback if no rejectedPolicy has been configured, or the thread
pool has no configured rejection handler. Is by default true | true | Boolean
|===
// eip options: END
diff --git a/camel-core/src/main/docs/eips/wireTap-eip.adoc
b/camel-core/src/main/docs/eips/wireTap-eip.adoc
index 1c1b5d8..5551d34 100644
--- a/camel-core/src/main/docs/eips/wireTap-eip.adoc
+++ b/camel-core/src/main/docs/eips/wireTap-eip.adoc
@@ -28,8 +28,8 @@ The Wire Tap EIP supports 10 options which are listed below:
| *body* | Uses the expression for creating a new body as the message to use
for wire tapping | | NamespaceAware Expression
| *executorServiceRef* | Uses a custom thread pool | | String
| *copy* | Uses a copy of the original exchange | true | Boolean
-| *dynamicUri* | Whether the uri is dynamic or static. If the uri is dynamic
then the simple language is used to evaluate a dynamic uri to use as the
wire-tap destination for each incoming message. This works similar to how the
toD EIP pattern works. If static then the uri is used as-is as the wire-tap
destination. | true | Boolean
-| *onPrepareRef* | Uses the Processor when preparing the
org.apache.camel.Exchange to be send. This can be used to deep-clone messages
that should be send or any custom logic needed before the exchange is send. |
| String
+| *dynamicUri* | Whether the uri is dynamic or static. If the uri is dynamic
then the simple language is used to evaluate a dynamic uri to use as the
wire-tap destination, for each incoming message. This works similar to how the
toD EIP pattern works. If static then the uri is used as-is as the wire-tap
destination. | true | Boolean
+| *onPrepareRef* | Uses the Processor when preparing the
org.apache.camel.Exchange to be send. This can be used to deep-clone messages
that should be send, or any custom logic needed before the exchange is send. |
| String
| *uri* | *Required* The uri of the endpoint to send to. The uri can be
dynamic computed using the org.apache.camel.language.simple.SimpleLanguage
expression. | | String
| *pattern* | Sets the optional ExchangePattern used to invoke this endpoint |
| ExchangePattern
| *cacheSize* | Sets the maximum size used by the
org.apache.camel.impl.ConsumerCache which is used to cache and reuse producers.
| | Integer
@@ -211,4 +211,4 @@ The following example sends a new message which has
See details at link:multicast.html[Multicast]
-link:using-this-pattern.html[Using This Pattern]
\ No newline at end of file
+link:using-this-pattern.html[Using This Pattern]
--
To stop receiving notification emails like this one, please contact
[email protected].
