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 c465ed9 Regen
c465ed9 is described below
commit c465ed933c5ba356380af533c419c767805b38b6
Author: Claus Ibsen <[email protected]>
AuthorDate: Wed Mar 31 14:31:49 2021 +0200
Regen
---
.../apache/camel/catalog/docs/kafka-component.adoc | 2 +-
.../apache/camel/catalog/docs/seda-component.adoc | 31 +++++++++++++++++++---
.../main/camel-main-configuration-metadata.json | 1 +
.../modules/ROOT/pages/kafka-component.adoc | 2 +-
.../modules/ROOT/pages/seda-component.adoc | 31 +++++++++++++++++++---
docs/components/modules/others/pages/main.adoc | 1 +
6 files changed, 58 insertions(+), 10 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/kafka-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/kafka-component.adoc
index b53610f..397f064 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/kafka-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/kafka-component.adoc
@@ -585,7 +585,7 @@ on the `KafkaComponent` that creates instances of your
custom implementation.
When consuming messages from Kafka, headers will be propagated to camel
exchange headers automatically.
Producing flow backed by same behaviour - camel headers of particular exchange
will be propagated to kafka message headers.
-Since kafka headers allows only `byte[]` values, in order camel exchnage
header to be propagated its value should be serialized to `bytes[]`,
+Since kafka headers allows only `byte[]` values, in order camel exchange
header to be propagated its value should be serialized to `bytes[]`,
otherwise header will be skipped.
Following header value types are supported: `String`, `Integer`, `Long`,
`Double`, `Boolean`, `byte[]`.
Note: all headers propagated *from* kafka *to* camel exchange will contain
`byte[]` value by default.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/seda-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/seda-component.adoc
index 6557138..71e3810 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/seda-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/seda-component.adoc
@@ -265,16 +265,39 @@ unit test.
*Since Camel 2.2*
-In this example we have defined two consumers and registered them as
-spring beans.
+In this example we have defined two consumers.
+
+[source,java]
+----
+ @Test
+ public void testSameOptionsProducerStillOkay() throws Exception {
+ getMockEndpoint("mock:foo").expectedBodiesReceived("Hello World");
+ getMockEndpoint("mock:bar").expectedBodiesReceived("Hello World");
+
+ template.sendBody("seda:foo", "Hello World");
+
+ assertMockEndpointsSatisfied();
+ }
+
+ @Override
+ protected RouteBuilder createRouteBuilder() throws Exception {
+ return new RouteBuilder() {
+ @Override
+ public void configure() throws Exception {
+
from("seda:foo?multipleConsumers=true").routeId("foo").to("mock:foo");
+
from("seda:foo?multipleConsumers=true").routeId("bar").to("mock:bar");
+ }
+ };
+ }
+----
+
Since we have specified *multipleConsumers=true* on the seda foo
endpoint we can have those two consumers receive their own copy of the
message as a kind of pub-sub style messaging.
As the beans are part of an unit test they simply send the message to a
-mock endpoint, but notice how we can use @Consume to consume from the
-seda queue.
+mock endpoint.
== Extracting queue information.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/main/camel-main-configuration-metadata.json
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/main/camel-main-configuration-metadata.json
index b6089dc..953a13e 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/main/camel-main-configuration-metadata.json
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/main/camel-main-configuration-metadata.json
@@ -30,6 +30,7 @@
{ "name": "camel.main.durationMaxIdleSeconds", "description": "To specify
for how long time in seconds Camel can be idle before automatic terminating the
JVM. You can use this to run Camel for a short while.", "sourceType":
"org.apache.camel.main.DefaultConfigurationProperties", "type": "integer",
"javaType": "int" },
{ "name": "camel.main.durationMaxMessages", "description": "To specify how
many messages to process by Camel before automatic terminating the JVM. You can
use this to run Camel for a short while.", "sourceType":
"org.apache.camel.main.DefaultConfigurationProperties", "type": "integer",
"javaType": "int" },
{ "name": "camel.main.durationMaxSeconds", "description": "To specify for
how long time in seconds to keep running the JVM before automatic terminating
the JVM. You can use this to run Camel for a short while.", "sourceType":
"org.apache.camel.main.DefaultConfigurationProperties", "type": "integer",
"javaType": "int" },
+ { "name": "camel.main.eagerClassloading", "description": "Whether to eager
load a common set of Camel classes that would otherwise first be loaded on
processing the first message. By eager loading these classes then the JVM has
already loaded the classes during build phase, which allows Camel to process
the first message faster.", "sourceType":
"org.apache.camel.main.DefaultConfigurationProperties", "type": "boolean",
"javaType": "boolean" },
{ "name": "camel.main.endpointBridgeErrorHandler", "description": "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\/ERROR level and ignored. The default va [...]
{ "name": "camel.main.endpointLazyStartProducer", "description": "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 mes [...]
{ "name": "camel.main.endpointRuntimeStatisticsEnabled", "description":
"Sets whether endpoint runtime statistics is enabled (gathers runtime usage of
each incoming and outgoing endpoints). The default value is false.",
"sourceType": "org.apache.camel.main.DefaultConfigurationProperties", "type":
"boolean", "javaType": "boolean" },
diff --git a/docs/components/modules/ROOT/pages/kafka-component.adoc
b/docs/components/modules/ROOT/pages/kafka-component.adoc
index bdf6e94..fab600d 100644
--- a/docs/components/modules/ROOT/pages/kafka-component.adoc
+++ b/docs/components/modules/ROOT/pages/kafka-component.adoc
@@ -587,7 +587,7 @@ on the `KafkaComponent` that creates instances of your
custom implementation.
When consuming messages from Kafka, headers will be propagated to camel
exchange headers automatically.
Producing flow backed by same behaviour - camel headers of particular exchange
will be propagated to kafka message headers.
-Since kafka headers allows only `byte[]` values, in order camel exchnage
header to be propagated its value should be serialized to `bytes[]`,
+Since kafka headers allows only `byte[]` values, in order camel exchange
header to be propagated its value should be serialized to `bytes[]`,
otherwise header will be skipped.
Following header value types are supported: `String`, `Integer`, `Long`,
`Double`, `Boolean`, `byte[]`.
Note: all headers propagated *from* kafka *to* camel exchange will contain
`byte[]` value by default.
diff --git a/docs/components/modules/ROOT/pages/seda-component.adoc
b/docs/components/modules/ROOT/pages/seda-component.adoc
index 092f30d..a07c5df 100644
--- a/docs/components/modules/ROOT/pages/seda-component.adoc
+++ b/docs/components/modules/ROOT/pages/seda-component.adoc
@@ -267,16 +267,39 @@ unit test.
*Since Camel 2.2*
-In this example we have defined two consumers and registered them as
-spring beans.
+In this example we have defined two consumers.
+
+[source,java]
+----
+ @Test
+ public void testSameOptionsProducerStillOkay() throws Exception {
+ getMockEndpoint("mock:foo").expectedBodiesReceived("Hello World");
+ getMockEndpoint("mock:bar").expectedBodiesReceived("Hello World");
+
+ template.sendBody("seda:foo", "Hello World");
+
+ assertMockEndpointsSatisfied();
+ }
+
+ @Override
+ protected RouteBuilder createRouteBuilder() throws Exception {
+ return new RouteBuilder() {
+ @Override
+ public void configure() throws Exception {
+
from("seda:foo?multipleConsumers=true").routeId("foo").to("mock:foo");
+
from("seda:foo?multipleConsumers=true").routeId("bar").to("mock:bar");
+ }
+ };
+ }
+----
+
Since we have specified *multipleConsumers=true* on the seda foo
endpoint we can have those two consumers receive their own copy of the
message as a kind of pub-sub style messaging.
As the beans are part of an unit test they simply send the message to a
-mock endpoint, but notice how we can use @Consume to consume from the
-seda queue.
+mock endpoint.
== Extracting queue information.
diff --git a/docs/components/modules/others/pages/main.adoc
b/docs/components/modules/others/pages/main.adoc
index ac05dab..6a099e6 100644
--- a/docs/components/modules/others/pages/main.adoc
+++ b/docs/components/modules/others/pages/main.adoc
@@ -44,6 +44,7 @@ The following table lists all the options:
| *camel.main.durationMaxIdle{zwsp}Seconds* | To specify for how long time in
seconds Camel can be idle before automatic terminating the JVM. You can use
this to run Camel for a short while. | | int
| *camel.main.durationMaxMessages* | To specify how many messages to process
by Camel before automatic terminating the JVM. You can use this to run Camel
for a short while. | | int
| *camel.main.durationMaxSeconds* | To specify for how long time in seconds to
keep running the JVM before automatic terminating the JVM. You can use this to
run Camel for a short while. | | int
+| *camel.main.eagerClassloading* | Whether to eager load a common set of Camel
classes that would otherwise first be loaded on processing the first message.
By eager loading these classes then the JVM has already loaded the classes
during build phase, which allows Camel to process the first message faster. |
| boolean
| *camel.main.endpointBridgeError{zwsp}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/ERROR level and ignored. The
default value is false. | | boolean
| *camel.main.endpointLazyStart{zwsp}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.main.endpointRuntime{zwsp}StatisticsEnabled* | Sets whether endpoint
runtime statistics is enabled (gathers runtime usage of each incoming and
outgoing endpoints). The default value is false. | | boolean
