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 57a3925 Regen
57a3925 is described below
commit 57a392597d08149bf0d7cbc02b21038182562271
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Sat Aug 3 09:43:37 2019 +0200
Regen
---
docs/components/modules/ROOT/pages/dataset-component.adoc | 3 ++-
docs/components/modules/ROOT/pages/dataset-test-component.adoc | 3 ++-
docs/components/modules/ROOT/pages/jetty-component.adoc | 2 +-
3 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/docs/components/modules/ROOT/pages/dataset-component.adoc
b/docs/components/modules/ROOT/pages/dataset-component.adoc
index 0abd769..d9fc80c 100644
--- a/docs/components/modules/ROOT/pages/dataset-component.adoc
+++ b/docs/components/modules/ROOT/pages/dataset-component.adoc
@@ -78,7 +78,7 @@ with the following path and query parameters:
|===
-=== Query Parameters (18 parameters):
+=== Query Parameters (19 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -92,6 +92,7 @@ with the following path and query parameters:
| *consumeDelay* (producer) | Allows a delay to be specified which causes a
delay when a message is consumed by the producer (to simulate slow processing)
| 0 | long
| *assertPeriod* (producer) | Sets a grace period after which the mock
endpoint will re-assert to ensure the preliminary assertion is still valid.
This is used for example to assert that exactly a number of messages arrives.
For example if expectedMessageCount(int) was set to 5, then the assertion is
satisfied when 5 or more message arrives. To ensure that exactly 5 messages
arrives, then you would need to wait a little period to ensure no further
message arrives. This is what you can us [...]
| *expectedCount* (producer) | Specifies the expected number of message
exchanges that should be received by this endpoint. Beware: If you want to
expect that 0 messages, then take extra care, as 0 matches when the tests
starts, so you need to set a assert period time to let the test run for a while
to make sure there are still no messages arrived; for that use
setAssertPeriod(long). An alternative is to use NotifyBuilder, and use the
notifier to know when Camel is done routing some mess [...]
+| *failFast* (producer) | Sets whether assertIsSatisfied() should fail fast at
the first detected failed expectation while it may otherwise wait for all
expected messages to arrive before performing expectations verifications. Is by
default true. Set to false to use behavior as in Camel 2.x. | 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 [...]
| *reportGroup* (producer) | A number that is used to turn on throughput
logging based on groups of the size. | | int
| *resultMinimumWaitTime* (producer) | Sets the minimum expected amount of
time (in millis) the assertIsSatisfied() will wait on a latch until it is
satisfied | 0 | long
diff --git a/docs/components/modules/ROOT/pages/dataset-test-component.adoc
b/docs/components/modules/ROOT/pages/dataset-test-component.adoc
index 78f9597..82cca82 100644
--- a/docs/components/modules/ROOT/pages/dataset-test-component.adoc
+++ b/docs/components/modules/ROOT/pages/dataset-test-component.adoc
@@ -73,7 +73,7 @@ with the following path and query parameters:
|===
-=== Query Parameters (16 parameters):
+=== Query Parameters (17 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -85,6 +85,7 @@ with the following path and query parameters:
| *timeout* (producer) | The timeout to use when polling for message bodies
from the URI | 2000 | long
| *assertPeriod* (producer) | Sets a grace period after which the mock
endpoint will re-assert to ensure the preliminary assertion is still valid.
This is used for example to assert that exactly a number of messages arrives.
For example if expectedMessageCount(int) was set to 5, then the assertion is
satisfied when 5 or more message arrives. To ensure that exactly 5 messages
arrives, then you would need to wait a little period to ensure no further
message arrives. This is what you can us [...]
| *expectedCount* (producer) | Specifies the expected number of message
exchanges that should be received by this endpoint. Beware: If you want to
expect that 0 messages, then take extra care, as 0 matches when the tests
starts, so you need to set a assert period time to let the test run for a while
to make sure there are still no messages arrived; for that use
setAssertPeriod(long). An alternative is to use NotifyBuilder, and use the
notifier to know when Camel is done routing some mess [...]
+| *failFast* (producer) | Sets whether assertIsSatisfied() should fail fast at
the first detected failed expectation while it may otherwise wait for all
expected messages to arrive before performing expectations verifications. Is by
default true. Set to false to use behavior as in Camel 2.x. | 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 [...]
| *reportGroup* (producer) | A number that is used to turn on throughput
logging based on groups of the size. | | int
| *resultMinimumWaitTime* (producer) | Sets the minimum expected amount of
time (in millis) the assertIsSatisfied() will wait on a latch until it is
satisfied | 0 | long
diff --git a/docs/components/modules/ROOT/pages/jetty-component.adoc
b/docs/components/modules/ROOT/pages/jetty-component.adoc
index c3d1349..1095244 100644
--- a/docs/components/modules/ROOT/pages/jetty-component.adoc
+++ b/docs/components/modules/ROOT/pages/jetty-component.adoc
@@ -126,7 +126,7 @@ with the following path and query parameters:
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *disableStreamCache* (common) | Determines whether or not the raw input
stream from Servlet is cached or not (Camel will read the stream into a in
memory/overflow to file, Stream caching) cache. By default Camel will cache the
Servlet input stream to support reading it multiple times to ensure it Camel
can retrieve all data from the stream. However you can set this option to true
when you for example need to access the raw stream, such as streaming it
directly to a file or other persis [...]
+| *disableStreamCache* (common) | Determines whether or not the raw input
stream from Servlet is cached or not (Camel will read the stream into a in
memory/overflow to file, Stream caching) cache. By default Camel will cache the
Servlet input stream to support reading it multiple times to ensure it Camel
can retrieve all data from the stream. However you can set this option to true
when you for example need to access the raw stream, such as streaming it
directly to a file or other persis [...]
| *headerFilterStrategy* (common) | To use a custom HeaderFilterStrategy to
filter header to and from Camel message. | | HeaderFilterStrategy
| *httpBinding* (common) | To use a custom HttpBinding to control the mapping
between Camel message and HttpClient. | | HttpBinding
| *async* (consumer) | Configure the consumer to work in async mode | false |
boolean
