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 fd62f60 Regen
fd62f60 is described below
commit fd62f608b78ba169fe675023cde11ad0c3e7d5d9
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Wed Jun 17 06:50:41 2020 +0200
Regen
---
.../component/ComponentsBuilderFactory.java | 4 ++--
.../dsl/WorkdayComponentBuilderFactory.java | 6 ++---
.../src/generated/resources/metadata.json | 4 ++--
.../builder/endpoint/StaticEndpointBuilders.java | 8 +++----
.../dsl/WorkdayEndpointBuilderFactory.java | 10 ++++----
.../modules/ROOT/pages/as2-component.adoc | 2 +-
.../modules/ROOT/pages/beanstalk-component.adoc | 2 +-
.../modules/ROOT/pages/cmis-component.adoc | 2 +-
.../modules/ROOT/pages/flink-component.adoc | 3 +--
.../ROOT/pages/guava-eventbus-component.adoc | 2 +-
.../modules/ROOT/pages/hdfs-component.adoc | 4 ++--
.../modules/ROOT/pages/ignite-cache-component.adoc | 6 ++---
.../ROOT/pages/ignite-compute-component.adoc | 6 ++---
.../ROOT/pages/ignite-events-component.adoc | 6 ++---
.../modules/ROOT/pages/ignite-idgen-component.adoc | 6 ++---
.../ROOT/pages/ignite-messaging-component.adoc | 6 ++---
.../modules/ROOT/pages/ignite-queue-component.adoc | 6 ++---
.../modules/ROOT/pages/ignite-set-component.adoc | 6 ++---
.../modules/ROOT/pages/milo-server-component.adoc | 20 ++++++++--------
.../modules/ROOT/pages/mongodb-component.adoc | 2 +-
.../modules/ROOT/pages/resteasy-component.adoc | 27 ++++------------------
.../modules/ROOT/pages/slack-component.adoc | 2 +-
.../modules/ROOT/pages/workday-component.adoc | 2 +-
23 files changed, 61 insertions(+), 81 deletions(-)
diff --git
a/core/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/ComponentsBuilderFactory.java
b/core/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/ComponentsBuilderFactory.java
index 2efd3a2..3467d7d 100644
---
a/core/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/ComponentsBuilderFactory.java
+++
b/core/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/ComponentsBuilderFactory.java
@@ -3820,9 +3820,9 @@ public interface ComponentsBuilderFactory {
}
/**
* Workday (camel-workday)
- * Represents a Workday endpoint.
+ * Detect and parse documents using Workday.
*
- * Category: hcm
+ * Category: cloud,api,hcm
* Since: 3.1
* Maven coordinates: org.apache.camel:camel-workday
*/
diff --git
a/core/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/WorkdayComponentBuilderFactory.java
b/core/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/WorkdayComponentBuilderFactory.java
index ba2c67a..763e64d 100644
---
a/core/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/WorkdayComponentBuilderFactory.java
+++
b/core/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/dsl/WorkdayComponentBuilderFactory.java
@@ -23,7 +23,7 @@ import org.apache.camel.builder.component.ComponentBuilder;
import org.apache.camel.component.workday.WorkdayComponent;
/**
- * Represents a Workday endpoint.
+ * Detect and parse documents using Workday.
*
* Generated by camel-package-maven-plugin - do not edit this file!
*/
@@ -32,9 +32,9 @@ public interface WorkdayComponentBuilderFactory {
/**
* Workday (camel-workday)
- * Represents a Workday endpoint.
+ * Detect and parse documents using Workday.
*
- * Category: hcm
+ * Category: cloud,api,hcm
* Since: 3.1
* Maven coordinates: org.apache.camel:camel-workday
*/
diff --git a/core/camel-componentdsl/src/generated/resources/metadata.json
b/core/camel-componentdsl/src/generated/resources/metadata.json
index 605b41d..28dae62 100644
--- a/core/camel-componentdsl/src/generated/resources/metadata.json
+++ b/core/camel-componentdsl/src/generated/resources/metadata.json
@@ -7127,10 +7127,10 @@
"kind": "component",
"name": "workday",
"title": "Workday",
- "description": "Represents a Workday endpoint.",
+ "description": "Detect and parse documents using Workday.",
"deprecated": false,
"firstVersion": "3.1.0",
- "label": "hcm",
+ "label": "cloud,api,hcm",
"javaType": "org.apache.camel.component.workday.WorkdayComponent",
"supportLevel": "Stable",
"groupId": "org.apache.camel",
diff --git
a/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/StaticEndpointBuilders.java
b/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/StaticEndpointBuilders.java
index e37e7e5..0e31f9a 100644
---
a/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/StaticEndpointBuilders.java
+++
b/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/StaticEndpointBuilders.java
@@ -14787,9 +14787,9 @@ public class StaticEndpointBuilders {
}
/**
* Workday (camel-workday)
- * Represents a Workday endpoint.
+ * Detect and parse documents using Workday.
*
- * Category: hcm
+ * Category: cloud,api,hcm
* Since: 3.1
* Maven coordinates: org.apache.camel:camel-workday
*
@@ -14810,9 +14810,9 @@ public class StaticEndpointBuilders {
}
/**
* Workday (camel-workday)
- * Represents a Workday endpoint.
+ * Detect and parse documents using Workday.
*
- * Category: hcm
+ * Category: cloud,api,hcm
* Since: 3.1
* Maven coordinates: org.apache.camel:camel-workday
*
diff --git
a/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/WorkdayEndpointBuilderFactory.java
b/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/WorkdayEndpointBuilderFactory.java
index 2f39722..9a27063 100644
---
a/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/WorkdayEndpointBuilderFactory.java
+++
b/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/WorkdayEndpointBuilderFactory.java
@@ -22,7 +22,7 @@ import org.apache.camel.builder.EndpointProducerBuilder;
import org.apache.camel.builder.endpoint.AbstractEndpointBuilder;
/**
- * Represents a Workday endpoint.
+ * Detect and parse documents using Workday.
*
* Generated by camel build tools - do NOT edit this file!
*/
@@ -247,9 +247,9 @@ public interface WorkdayEndpointBuilderFactory {
public interface WorkdayBuilders {
/**
* Workday (camel-workday)
- * Represents a Workday endpoint.
+ * Detect and parse documents using Workday.
*
- * Category: hcm
+ * Category: cloud,api,hcm
* Since: 3.1
* Maven coordinates: org.apache.camel:camel-workday
*
@@ -269,9 +269,9 @@ public interface WorkdayEndpointBuilderFactory {
}
/**
* Workday (camel-workday)
- * Represents a Workday endpoint.
+ * Detect and parse documents using Workday.
*
- * Category: hcm
+ * Category: cloud,api,hcm
* Since: 3.1
* Maven coordinates: org.apache.camel:camel-workday
*
diff --git a/docs/components/modules/ROOT/pages/as2-component.adoc
b/docs/components/modules/ROOT/pages/as2-component.adoc
index 1792a73..0ce32bf 100644
--- a/docs/components/modules/ROOT/pages/as2-component.adoc
+++ b/docs/components/modules/ROOT/pages/as2-component.adoc
@@ -58,10 +58,10 @@ The AS2 component supports 4 options, which are listed
below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *configuration* (common) | To use the shared configuration | |
AS2Configuration
| *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
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
+| *configuration* (advanced) | Component configuration | | AS2Configuration
|===
// component options: END
diff --git a/docs/components/modules/ROOT/pages/beanstalk-component.adoc
b/docs/components/modules/ROOT/pages/beanstalk-component.adoc
index a182bd2..f369a23 100644
--- a/docs/components/modules/ROOT/pages/beanstalk-component.adoc
+++ b/docs/components/modules/ROOT/pages/beanstalk-component.adoc
@@ -74,10 +74,10 @@ The Beanstalk component supports 4 options, which are
listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *connectionSettingsFactory* (common) | Custom ConnectionSettingsFactory.
Specify which ConnectionSettingsFactory to use to make connections to
Beanstalkd. Especially useful for unit testing without beanstalkd daemon (you
can mock ConnectionSettings) | | ConnectionSettingsFactory
| *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
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
+| *connectionSettingsFactory* (advanced) | Custom ConnectionSettingsFactory.
Specify which ConnectionSettingsFactory to use to make connections to
Beanstalkd. Especially useful for unit testing without beanstalkd daemon (you
can mock ConnectionSettings) | | ConnectionSettingsFactory
|===
// component options: END
diff --git a/docs/components/modules/ROOT/pages/cmis-component.adoc
b/docs/components/modules/ROOT/pages/cmis-component.adoc
index b57674b..766aee2 100644
--- a/docs/components/modules/ROOT/pages/cmis-component.adoc
+++ b/docs/components/modules/ROOT/pages/cmis-component.adoc
@@ -39,10 +39,10 @@ The CMIS component supports 4 options, which are listed
below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *sessionFacadeFactory* (common) | To use a custom CMISSessionFacadeFactory
to create the CMISSessionFacade instances | | CMISSessionFacadeFactory
| *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
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
+| *sessionFacadeFactory* (advanced) | To use a custom CMISSessionFacadeFactory
to create the CMISSessionFacade instances | | CMISSessionFacadeFactory
|===
// component options: END
diff --git a/docs/components/modules/ROOT/pages/flink-component.adoc
b/docs/components/modules/ROOT/pages/flink-component.adoc
index 33ae7e9..e58fab4 100644
--- a/docs/components/modules/ROOT/pages/flink-component.adoc
+++ b/docs/components/modules/ROOT/pages/flink-component.adoc
@@ -97,14 +97,13 @@ with the following path and query parameters:
// component options: START
-The Flink component supports 6 options, which are listed below.
+The Flink component supports 5 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *dataSet* (producer) | DataSet to compute against. | | DataSet
| *dataSetCallback* (producer) | Function performing action against a DataSet.
| | DataSetCallback
| *dataStream* (producer) | DataStream to compute against. | | DataStream
| *dataStreamCallback* (producer) | Function performing action against a
DataStream. | | DataStreamCallback
diff --git a/docs/components/modules/ROOT/pages/guava-eventbus-component.adoc
b/docs/components/modules/ROOT/pages/guava-eventbus-component.adoc
index eb4a0f0..35c8a08 100644
--- a/docs/components/modules/ROOT/pages/guava-eventbus-component.adoc
+++ b/docs/components/modules/ROOT/pages/guava-eventbus-component.adoc
@@ -64,8 +64,8 @@ The Guava EventBus component supports 5 options, which are
listed below.
|===
| Name | Description | Default | Type
| *eventBus* (common) | To use the given Guava EventBus instance | | EventBus
-| *listenerInterface* (common) | The interface with method(s) marked with the
Subscribe annotation. Dynamic proxy will be created over the interface so it
could be registered as the EventBus listener. Particularly useful when creating
multi-event listeners and for handling DeadEvent properly. This option cannot
be used together with eventClass option. | | Class
| *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
+| *listenerInterface* (consumer) | The interface with method(s) marked with
the Subscribe annotation. Dynamic proxy will be created over the interface so
it could be registered as the EventBus listener. Particularly useful when
creating multi-event listeners and for handling DeadEvent properly. This option
cannot be used together with eventClass option. | | Class
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
|===
diff --git a/docs/components/modules/ROOT/pages/hdfs-component.adoc
b/docs/components/modules/ROOT/pages/hdfs-component.adoc
index 0b76061..666a280 100644
--- a/docs/components/modules/ROOT/pages/hdfs-component.adoc
+++ b/docs/components/modules/ROOT/pages/hdfs-component.adoc
@@ -71,11 +71,11 @@ The HDFS component supports 5 options, which are listed
below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *jAASConfiguration* (common) | To use the given configuration for security
with JAAS. | | Configuration
-| *kerberosConfigFile* (common) | To use kerberos authentication, set the
value of the 'java.security.krb5.conf' environment variable to an existing
file. If the environment variable is already set, warn if different than the
specified parameter | | String
| *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
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
+| *jAASConfiguration* (security) | To use the given configuration for security
with JAAS. | | Configuration
+| *kerberosConfigFile* (security) | To use kerberos authentication, set the
value of the 'java.security.krb5.conf' environment variable to an existing
file. If the environment variable is already set, warn if different than the
specified parameter | | String
|===
// component options: END
diff --git a/docs/components/modules/ROOT/pages/ignite-cache-component.adoc
b/docs/components/modules/ROOT/pages/ignite-cache-component.adoc
index 3f95295..48f0701 100644
--- a/docs/components/modules/ROOT/pages/ignite-cache-component.adoc
+++ b/docs/components/modules/ROOT/pages/ignite-cache-component.adoc
@@ -32,9 +32,9 @@ The Ignite Cache component supports 6 options, which are
listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *configurationResource* (common) | Resource from where to load
configuration. | | Object
-| *ignite* (common) | Ignite instance. | | Ignite
-| *igniteConfiguration* (common) | Ignite configuration. | |
IgniteConfiguration
+| *configurationResource* (common) | The resource from where to load the
configuration. It can be a: URL, String or InputStream type. | | Object
+| *ignite* (common) | To use an existing Ignite instance. | | Ignite
+| *igniteConfiguration* (common) | Allows the user to set a programmatic
ignite configuration. | | IgniteConfiguration
| *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
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
diff --git a/docs/components/modules/ROOT/pages/ignite-compute-component.adoc
b/docs/components/modules/ROOT/pages/ignite-compute-component.adoc
index 761f053..c33cd56 100644
--- a/docs/components/modules/ROOT/pages/ignite-compute-component.adoc
+++ b/docs/components/modules/ROOT/pages/ignite-compute-component.adoc
@@ -33,9 +33,9 @@ The Ignite Compute component supports 5 options, which are
listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *configurationResource* (producer) | Resource from where to load
configuration. | | Object
-| *ignite* (producer) | Ignite instance. | | Ignite
-| *igniteConfiguration* (producer) | Ignite configuration. | |
IgniteConfiguration
+| *configurationResource* (producer) | The resource from where to load the
configuration. It can be a: URL, String or InputStream type. | | Object
+| *ignite* (producer) | To use an existing Ignite instance. | | Ignite
+| *igniteConfiguration* (producer) | Allows the user to set a programmatic
ignite configuration. | | IgniteConfiguration
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
|===
diff --git a/docs/components/modules/ROOT/pages/ignite-events-component.adoc
b/docs/components/modules/ROOT/pages/ignite-events-component.adoc
index 211d60d..d191a30 100644
--- a/docs/components/modules/ROOT/pages/ignite-events-component.adoc
+++ b/docs/components/modules/ROOT/pages/ignite-events-component.adoc
@@ -31,9 +31,9 @@ The Ignite Events component supports 5 options, which are
listed below.
|===
| Name | Description | Default | Type
| *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
-| *configurationResource* (consumer) | Resource from where to load
configuration. | | Object
-| *ignite* (consumer) | Ignite instance. | | Ignite
-| *igniteConfiguration* (consumer) | Ignite configuration. | |
IgniteConfiguration
+| *configurationResource* (consumer) | The resource from where to load the
configuration. It can be a: URL, String or InputStream type. | | Object
+| *ignite* (consumer) | To use an existing Ignite instance. | | Ignite
+| *igniteConfiguration* (consumer) | Allows the user to set a programmatic
ignite configuration. | | IgniteConfiguration
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
|===
// component options: END
diff --git a/docs/components/modules/ROOT/pages/ignite-idgen-component.adoc
b/docs/components/modules/ROOT/pages/ignite-idgen-component.adoc
index 41af17b..d0d0e2d 100644
--- a/docs/components/modules/ROOT/pages/ignite-idgen-component.adoc
+++ b/docs/components/modules/ROOT/pages/ignite-idgen-component.adoc
@@ -29,9 +29,9 @@ The Ignite ID Generator component supports 5 options, which
are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *configurationResource* (producer) | Resource from where to load
configuration. | | Object
-| *ignite* (producer) | Ignite instance. | | Ignite
-| *igniteConfiguration* (producer) | Ignite configuration. | |
IgniteConfiguration
+| *configurationResource* (producer) | The resource from where to load the
configuration. It can be a: URL, String or InputStream type. | | Object
+| *ignite* (producer) | To use an existing Ignite instance. | | Ignite
+| *igniteConfiguration* (producer) | Allows the user to set a programmatic
ignite configuration. | | IgniteConfiguration
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
|===
diff --git a/docs/components/modules/ROOT/pages/ignite-messaging-component.adoc
b/docs/components/modules/ROOT/pages/ignite-messaging-component.adoc
index 6b35770..cb7b8c2 100644
--- a/docs/components/modules/ROOT/pages/ignite-messaging-component.adoc
+++ b/docs/components/modules/ROOT/pages/ignite-messaging-component.adoc
@@ -29,9 +29,9 @@ The Ignite Messaging component supports 6 options, which are
listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *configurationResource* (common) | Resource from where to load
configuration. | | Object
-| *ignite* (common) | Ignite instance. | | Ignite
-| *igniteConfiguration* (common) | Ignite configuration. | |
IgniteConfiguration
+| *configurationResource* (common) | The resource from where to load the
configuration. It can be a: URL, String or InputStream type. | | Object
+| *ignite* (common) | To use an existing Ignite instance. | | Ignite
+| *igniteConfiguration* (common) | Allows the user to set a programmatic
ignite configuration. | | IgniteConfiguration
| *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
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
diff --git a/docs/components/modules/ROOT/pages/ignite-queue-component.adoc
b/docs/components/modules/ROOT/pages/ignite-queue-component.adoc
index 7332933..a4acaa2 100644
--- a/docs/components/modules/ROOT/pages/ignite-queue-component.adoc
+++ b/docs/components/modules/ROOT/pages/ignite-queue-component.adoc
@@ -29,9 +29,9 @@ The Ignite Queues component supports 5 options, which are
listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *configurationResource* (producer) | Resource from where to load
configuration. | | Object
-| *ignite* (producer) | Ignite instance. | | Ignite
-| *igniteConfiguration* (producer) | Ignite configuration. | |
IgniteConfiguration
+| *configurationResource* (producer) | The resource from where to load the
configuration. It can be a: URL, String or InputStream type. | | Object
+| *ignite* (producer) | To use an existing Ignite instance. | | Ignite
+| *igniteConfiguration* (producer) | Allows the user to set a programmatic
ignite configuration. | | IgniteConfiguration
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
|===
diff --git a/docs/components/modules/ROOT/pages/ignite-set-component.adoc
b/docs/components/modules/ROOT/pages/ignite-set-component.adoc
index 277f232..19d9946 100644
--- a/docs/components/modules/ROOT/pages/ignite-set-component.adoc
+++ b/docs/components/modules/ROOT/pages/ignite-set-component.adoc
@@ -29,9 +29,9 @@ The Ignite Sets component supports 5 options, which are
listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *configurationResource* (producer) | Resource from where to load
configuration. | | Object
-| *ignite* (producer) | Ignite instance. | | Ignite
-| *igniteConfiguration* (producer) | Ignite configuration. | |
IgniteConfiguration
+| *configurationResource* (producer) | The resource from where to load the
configuration. It can be a: URL, String or InputStream type. | | Object
+| *ignite* (producer) | To use an existing Ignite instance. | | Ignite
+| *igniteConfiguration* (producer) | Allows the user to set a programmatic
ignite configuration. | | IgniteConfiguration
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
|===
diff --git a/docs/components/modules/ROOT/pages/milo-server-component.adoc
b/docs/components/modules/ROOT/pages/milo-server-component.adoc
index c36e3c5..ea92cff 100644
--- a/docs/components/modules/ROOT/pages/milo-server-component.adoc
+++ b/docs/components/modules/ROOT/pages/milo-server-component.adoc
@@ -47,22 +47,22 @@ The OPC UA Server component supports 20 options, which are
listed below.
| *applicationUri* (common) | The application URI | | String
| *bindAddresses* (common) | Set the addresses of the local addresses the
server should bind to | | String
| *buildInfo* (common) | Server build info | | BuildInfo
-| *certificate* (common) | Server certificate | | X509Certificate
-| *certificateManager* (common) | Server certificate manager | |
CertificateManager
-| *certificateValidator* (common) | Validator for client certificates | |
CertificateValidator
-| *defaultCertificateValidator* (common) | Validator for client certificates
using default file based approach | | String
-| *enableAnonymousAuthentication* (common) | Enable anonymous authentication,
disabled by default | false | boolean
-| *namespaceUri* (common) | The URI of the namespace, defaults to
urn:org:apache:camel | | String
+| *namespaceUri* (common) | The URI of the namespace, defaults to
urn:org:apache:camel | urn:org:apache:camel | String
| *path* (common) | The path to be appended to the end of the endpoint url.
(doesn't need to start with '/') | | String
| *port* (common) | The TCP port the server binds to | | int
| *productUri* (common) | The product URI | | String
-| *securityPolicies* (common) | Security policies | | Set
-| *securityPoliciesById* (common) | Security policies by URI or name. Multiple
policies can be separated by comma. | | String
-| *userAuthenticationCredentials* (common) | Set user password combinations in
the form of user1:pwd1,user2:pwd2 Usernames and passwords will be URL decoded |
| String
-| *usernameSecurityPolicyUri* (common) | Set the UserTokenPolicy used when.
The value can be one of: None, Basic128Rsa15, Basic256, Basic256Sha256,
Aes128_Sha256_RsaOaep, Aes256_Sha256_RsaPss | | SecurityPolicy
| *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
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
+| *certificate* (security) | Server certificate | | X509Certificate
+| *certificateManager* (security) | Server certificate manager | |
CertificateManager
+| *certificateValidator* (security) | Validator for client certificates | |
CertificateValidator
+| *defaultCertificateValidator* (security) | Validator for client certificates
using default file based approach | | String
+| *enableAnonymousAuthentication* (security) | Enable anonymous
authentication, disabled by default | false | boolean
+| *securityPolicies* (security) | Security policies | | Set
+| *securityPoliciesById* (security) | Security policies by URI or name.
Multiple policies can be separated by comma. | | String
+| *userAuthenticationCredentials* (security) | Set user password combinations
in the form of user1:pwd1,user2:pwd2 Usernames and passwords will be URL
decoded | | String
+| *usernameSecurityPolicyUri* (security) | Set the UserTokenPolicy used when.
The value can be one of: None, Basic128Rsa15, Basic256, Basic256Sha256,
Aes128_Sha256_RsaOaep, Aes256_Sha256_RsaPss | | SecurityPolicy
|===
// component options: END
diff --git a/docs/components/modules/ROOT/pages/mongodb-component.adoc
b/docs/components/modules/ROOT/pages/mongodb-component.adoc
index 8c36181..165262b 100644
--- a/docs/components/modules/ROOT/pages/mongodb-component.adoc
+++ b/docs/components/modules/ROOT/pages/mongodb-component.adoc
@@ -74,7 +74,7 @@ The MongoDB component supports 4 options, which are listed
below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *mongoConnection* (common) | A connection client provided externally | |
MongoClient
+| *mongoConnection* (common) | Shared client used for connection. All
endpoints generated from the component will share this connection client. | |
MongoClient
| *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
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
diff --git a/docs/components/modules/ROOT/pages/resteasy-component.adoc
b/docs/components/modules/ROOT/pages/resteasy-component.adoc
index 787e6f7..905b9c9 100644
--- a/docs/components/modules/ROOT/pages/resteasy-component.adoc
+++ b/docs/components/modules/ROOT/pages/resteasy-component.adoc
@@ -43,35 +43,23 @@ You can append query options to the URI in the following
format:
=== Options
// component options: START
-The Resteasy component supports 22 options, which are listed below.
+The Resteasy component supports 10 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *httpRegistry* (common) | Sets httpRegistry which can be externalized to be
used by camel | | HttpRegistry
-| *proxyConsumersClasses* (common) | Sets the proxy class for consumer
enpoints | | String
| *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
-| *cookieStore* (producer) | To use a custom
org.apache.http.client.CookieStore. By default the
org.apache.http.impl.client.BasicCookieStore is used which is an in-memory only
cookie store. Notice if bridgeEndpoint=true then the cookie store is forced to
be a noop cookie store as cookie shouldn't be stored as we are just bridging
(eg acting as a proxy). | | CookieStore
+| *proxyConsumersClasses* (consumer) | Proxy classes for consumer endpoints.
Multiple classes can be separated by comma. | | 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 [...]
| *allowJavaSerializedObject* (advanced) | Whether to allow java serialization
when a request uses context-type=application/x-java-serialized-object. This is
by default turned off. If you enable this then be aware that Java will
deserialize the incoming data from the request to Java and that can be a
potential security risk. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
-| *clientConnectionManager* (advanced) | To use a custom and shared
HttpClientConnectionManager to manage connections. If this has been configured
then this is always used for all endpoints created by this component. | |
HttpClientConnectionManager
-| *connectionsPerRoute* (advanced) | The maximum number of connections per
route. | 20 | int
-| *connectionTimeToLive* (advanced) | The time for connection to live, the
time unit is millisecond, the default value is always keep alive. | | long
-| *httpBinding* (advanced) | To use a custom HttpBinding to control the
mapping between Camel message and HttpClient. | | HttpBinding
-| *httpClientConfigurer* (advanced) | To use the custom HttpClientConfigurer
to perform configuration of the HttpClient that will be used. | |
HttpClientConfigurer
-| *httpConfiguration* (advanced) | To use the shared HttpConfiguration as base
configuration. | | HttpConfiguration
-| *httpContext* (advanced) | To use a custom
org.apache.http.protocol.HttpContext when executing requests. | | HttpContext
-| *maxTotalConnections* (advanced) | The maximum number of connections. | 200
| int
+| *resteasyHttpBinding* (advanced) | To use a custom ResteasyHttpBinding | |
ResteasyHttpBinding
| *headerFilterStrategy* (filter) | To use a custom
org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel
message. | | HeaderFilterStrategy
| *sslContextParameters* (security) | To configure security using
SSLContextParameters. Important: Only one instance of
org.apache.camel.support.jsse.SSLContextParameters is supported per
HttpComponent. If you need to use 2 or more different instances, you need to
define a new HttpComponent per instance you need. | | SSLContextParameters
| *useGlobalSslContextParameters* (security) | Enable usage of global SSL
context parameters. | false | boolean
| *x509HostnameVerifier* (security) | To use a custom X509HostnameVerifier
such as DefaultHostnameVerifier or NoopHostnameVerifier. | | HostnameVerifier
-| *connectionRequestTimeout* (timeout) | The timeout in milliseconds used when
requesting a connection from the connection manager. A timeout value of zero is
interpreted as an infinite timeout. A timeout value of zero is interpreted as
an infinite timeout. A negative value is interpreted as undefined (system
default). | -1 | int
-| *connectTimeout* (timeout) | Determines the timeout in milliseconds until a
connection is established. A timeout value of zero is interpreted as an
infinite timeout. A timeout value of zero is interpreted as an infinite
timeout. A negative value is interpreted as undefined (system default). | -1 |
int
-| *socketTimeout* (timeout) | Defines the socket timeout in milliseconds,
which is the timeout for waiting for data or, put differently, a maximum period
inactivity between two consecutive data packets). A timeout value of zero is
interpreted as an infinite timeout. A negative value is interpreted as
undefined (system default). | -1 | int
|===
// component options: END
@@ -95,7 +83,7 @@ with the following path and query parameters:
|===
-=== Query Parameters (73 parameters):
+=== Query Parameters (66 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -107,7 +95,6 @@ with the following path and query parameters:
| *resteasyMethod* (common) | Sets the resteasy method to process the request
| GET | String
| *servletName* (common) | Sets the servlet name | | String
| *transferException* (common) | If enabled and an Exchange failed processing
on the consumer side, and if the caused Exception was send back serialized in
the response as a application/x-java-serialized-object content type. On the
producer side the exception will be deserialized and thrown as is, instead of
the HttpOperationFailedException. The caused exception is required to be
serialized. This is by default turned off. If you enable this then be aware
that Java will deserialize the in [...]
-| *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
| *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
| *httpMethodRestrict* (consumer) | Used to only allow consuming if the
HttpMethod matches, such as GET/POST/PUT etc. Multiple methods can be specified
separated by comma. | | String
@@ -130,23 +117,17 @@ with the following path and query parameters:
| *preserveHostHeader* (producer) | If the option is true, HttpProducer will
set the Host header to the value contained in the current exchange Host header,
useful in reverse proxy applications where you want the Host header received by
the downstream server to reflect the URL called by the upstream client, this
allows applications which use the Host header to generate accurate URL's for a
proxied service | false | boolean
| *throwExceptionOnFailure* (producer) | Option to disable throwing the
HttpOperationFailedException in case of failed responses from the remote
server. This allows you to get all responses regardless of the HTTP status
code. | true | boolean
| *cookieHandler* (producer) | Configure a cookie handler to maintain a HTTP
session | | CookieHandler
-| *cookieStore* (producer) | To use a custom CookieStore. By default the
BasicCookieStore is used which is an in-memory only cookie store. Notice if
bridgeEndpoint=true then the cookie store is forced to be a noop cookie store
as cookie shouldn't be stored as we are just bridging (eg acting as a proxy).
If a cookieHandler is set then the cookie store is also forced to be a noop
cookie store as cookie handling is then performed by the cookieHandler. | |
CookieStore
| *deleteWithBody* (producer) | Whether the HTTP DELETE should include the
message body or not. By default HTTP DELETE do not include any HTTP body.
However in some rare cases users may need to be able to include the message
body. | false | boolean
| *getWithBody* (producer) | Whether the HTTP GET should include the message
body or not. By default HTTP GET do not include any HTTP body. However in some
rare cases users may need to be able to include the message body. | false |
boolean
| *okStatusCodeRange* (producer) | The status codes which are considered a
success response. The values are inclusive. Multiple ranges can be defined,
separated by comma, e.g. 200-204,209,301-304. Each range must be a single
number or from-to with the dash included. | 200-299 | String
| *basicPropertyBinding* (advanced) | Whether the endpoint should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
| *clientBuilder* (advanced) | Provide access to the http client request
parameters used on new RequestConfig instances used by producers or consumers
of this endpoint. | | HttpClientBuilder
-| *clientConnectionManager* (advanced) | To use a custom
HttpClientConnectionManager to manage connections | |
HttpClientConnectionManager
-| *connectionsPerRoute* (advanced) | The maximum number of connections per
route. | 20 | int
| *headerFilterStrategy* (advanced) | To use a custom HeaderFilterStrategy to
filter header to and from Camel message. | | HeaderFilterStrategy
| *httpClient* (advanced) | Sets a custom HttpClient to be used by the
producer | | HttpClient
-| *httpClientConfigurer* (advanced) | Register a custom configuration strategy
for new HttpClient instances created by producers or consumers such as to
configure authentication mechanisms etc. | | HttpClientConfigurer
| *httpClientOptions* (advanced) | To configure the HttpClient using the
key/values from the Map. | | Map
-| *httpContext* (advanced) | To use a custom HttpContext instance | |
HttpContext
| *mapHttpMessageBody* (advanced) | If this option is true then IN exchange
Body of the exchange will be mapped to HTTP body. Setting this to false will
avoid the HTTP mapping. | true | boolean
| *mapHttpMessageFormUrlEncoded Body* (advanced) | If this option is true then
IN exchange Form Encoded body of the exchange will be mapped to HTTP. Setting
this to false will avoid the HTTP Form Encoded body mapping. | true | boolean
| *mapHttpMessageHeaders* (advanced) | If this option is true then IN exchange
Headers of the exchange will be mapped to HTTP headers. Setting this to false
will avoid the HTTP Headers mapping. | true | boolean
-| *maxTotalConnections* (advanced) | The maximum number of connections. | 200
| int
| *setHttpResponseDuring Processing* (advanced) | Sets the flag to use the
endpoint where you can either populate camel exchange from servlet response or
use request itself which may be thought as if it is a proxy. | | Boolean
| *skipServletProcessing* (advanced) | Sets the flag to use skip servlet
processing and let camel take over processing | | Boolean
| *synchronous* (advanced) | Sets whether synchronous processing should be
strictly used, or Camel is allowed to use asynchronous processing (if
supported). | false | boolean
diff --git a/docs/components/modules/ROOT/pages/slack-component.adoc
b/docs/components/modules/ROOT/pages/slack-component.adoc
index f1c4e10..91e836b 100644
--- a/docs/components/modules/ROOT/pages/slack-component.adoc
+++ b/docs/components/modules/ROOT/pages/slack-component.adoc
@@ -60,10 +60,10 @@ The Slack component supports 4 options, which are listed
below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
-| *webhookUrl* (common) | The incoming webhook URL | | String
| *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
| *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 [...]
| *basicPropertyBinding* (advanced) | Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
+| *webhookUrl* (webhook) | The incoming webhook URL | | String
|===
// component options: END
diff --git a/docs/components/modules/ROOT/pages/workday-component.adoc
b/docs/components/modules/ROOT/pages/workday-component.adoc
index 993975a..a8fbe33 100644
--- a/docs/components/modules/ROOT/pages/workday-component.adoc
+++ b/docs/components/modules/ROOT/pages/workday-component.adoc
@@ -4,7 +4,7 @@
:page-source: components/camel-workday/src/main/docs/workday-component.adoc
:docTitle: Workday
:artifactId: camel-workday
-:description: Represents a Workday endpoint.
+:description: Detect and parse documents using Workday.
:since: 3.1
:supportLevel: Stable
:component-header: Only producer is supported
