Upload folder using huggingface_hub

camel-activemq.md

@@ -0,0 +1,276 @@
+# Activemq
+
+**Since Camel 1.0**
+
+**Both producer and consumer are supported**
+
+The ActiveMQ component is an extension to the JMS component and has been
+pre-configured for using Apache ActiveMQ 5.x (not Artemis). Users of
+Apache ActiveMQ Artemis should use the JMS component.
+
+The camel-activemq component is best intended for ActiveMQ 5.x classic
+brokers. If you use ActiveMQ 6.x brokers, then use the camel-activemq6
+component instead.
+
+**More documentation**
+
+See the JMS component for more documentation and examples
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-activemq</artifactId>
+        <version>x.x.x</version>
+        <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# URI format
+
+    activemq:[queue:|topic:]destinationName[?options]
+
+Where `destinationName` is a JMS queue or topic name. By default, the
+`destinationName` is interpreted as a queue name. For example, to
+connect to the queue, `foo` use:
+
+    activemq:foo
+
+# Examples
+
+You’ll need to provide a connectionFactory to the ActiveMQ Component, to
+have the following examples working.
+
+## Producer Example
+
+    from("timer:mytimer?period=5000")
+            .setBody(constant("HELLO from Camel!"))
+            .to("activemq:queue:HELLO.WORLD");
+
+## Consumer Example
+
+    from("activemq:queue:HELLO.WORLD")
+            .log("Received a message - ${body}");
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|brokerURL|Sets the broker URL to use to connect to ActiveMQ. If none configured then localhost:61616 is used by default (however can be overridden by configuration from environment variables)||string|
+|clientId|Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions with JMS 1.1.||string|
+|connectionFactory|The connection factory to be use. A connection factory must be configured either on the component or endpoint.||object|
+|disableReplyTo|Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different message brokers and you want to route message from one system to another.|false|boolean|
+|durableSubscriptionName|The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.||string|
+|embedded|Use an embedded in-memory (non-persistent) ActiveMQ broker for development and testing purposes. You must have activemq-broker JAR on the classpath.|false|boolean|
+|jmsMessageType|Allows you to force the use of a specific jakarta.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it.||object|
+|replyTo|Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer).||string|
+|testConnectionOnStartup|Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well.|false|boolean|
+|usePooledConnection|Enables or disables whether a PooledConnectionFactory will be used so that when messages are sent to ActiveMQ from outside a message consuming thread, pooling will be used rather than the default with the Spring JmsTemplate which will create a new connection, session, producer for each message then close them all down again. The default value is true.|true|boolean|
+|useSingleConnection|Enables or disables whether a Spring SingleConnectionFactory will be used so that when messages are sent to ActiveMQ from outside a message consuming thread, pooling will be used rather than the default with the Spring JmsTemplate which will create a new connection, session, producer for each message then close them all down again. The default value is false and a pooled connection is used by default.|false|boolean|
+|acknowledgementModeName|The JMS acknowledgement name, which is one of: SESSION\_TRANSACTED, CLIENT\_ACKNOWLEDGE, AUTO\_ACKNOWLEDGE, DUPS\_OK\_ACKNOWLEDGE|AUTO\_ACKNOWLEDGE|string|
+|artemisConsumerPriority|Consumer priorities allow you to ensure that high priority consumers receive messages while they are active. Normally, active consumers connected to a queue receive messages from it in a round-robin fashion. When consumer priorities are in use, messages are delivered round-robin if multiple active consumers exist with the same high priority. Messages will only going to lower priority consumers when the high priority consumers do not have credit available to consume the message, or those high priority consumers have declined to accept the message (for instance because it does not meet the criteria of any selectors associated with the consumer).||integer|
+|asyncConsumer|Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note if transacted has been enabled, then asyncConsumer=true does not run asynchronously, as transaction must be executed synchronously (Camel 3.0 may support async transactions).|false|boolean|
+|autoStartup|Specifies whether the consumer container should auto-startup.|true|boolean|
+|cacheLevel|Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.||integer|
+|cacheLevelName|Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE\_AUTO, CACHE\_CONNECTION, CACHE\_CONSUMER, CACHE\_NONE, and CACHE\_SESSION. The default setting is CACHE\_AUTO. See the Spring documentation and Transactions Cache Levels for more information.|CACHE\_AUTO|string|
+|concurrentConsumers|Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.|1|integer|
+|maxConcurrentConsumers|Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.||integer|
+|replyToDeliveryPersistent|Specifies whether to use persistent delivery by default for replies.|true|boolean|
+|selector|Sets the JMS selector to use||string|
+|subscriptionDurable|Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well.|false|boolean|
+|subscriptionName|Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS 2.0).||string|
+|subscriptionShared|Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined with subscriptionDurable as well. Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well. Requires a JMS 2.0 compatible message broker.|false|boolean|
+|acceptMessagesWhileStopping|Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option.|false|boolean|
+|allowReplyManagerQuickStop|Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag.|false|boolean|
+|consumerType|The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.|Default|object|
+|defaultTaskExecutorType|Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached thread-pool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of ThreadPool is recommended to reduce thread trash in elastic configurations with dynamically increasing and decreasing concurrent consumers.||object|
+|eagerLoadingOfProperties|Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody.|false|boolean|
+|eagerPoisonBody|If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties.|Poison JMS message due to ${exception.message}|string|
+|exposeListenerSession|Specifies whether the listener session should be exposed when consuming messages.|false|boolean|
+|replyToConsumerType|The consumer type of the reply consumer (when doing request/reply), which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.|Default|object|
+|replyToSameDestinationAllowed|Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself.|false|boolean|
+|taskExecutor|Allows you to specify a custom task executor for consuming messages.||object|
+|deliveryDelay|Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker.|-1|integer|
+|deliveryMode|Specifies the delivery mode to be used. Possible values are those defined by jakarta.jms.DeliveryMode. NON\_PERSISTENT = 1 and PERSISTENT = 2.||integer|
+|deliveryPersistent|Specifies whether persistent delivery is used by default.|true|boolean|
+|explicitQosEnabled|Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers.|false|boolean|
+|formatDateHeadersToIso8601|Sets whether JMS date properties should be formatted according to the ISO 8601 standard.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|preserveMessageQos|Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explicitQosEnabled option, by contrast, will only use options set on the endpoint, and not values from the message header.|false|boolean|
+|priority|Values greater than 1 specify the message priority when sending (where 1 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect.|4|integer|
+|replyToConcurrentConsumers|Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.|1|integer|
+|replyToMaxConcurrentConsumers|Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.||integer|
+|replyToOnTimeoutMaxConcurrentConsumers|Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS.|1|integer|
+|replyToOverride|Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination.||string|
+|replyToType|Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications if running in a clustered environment, and the fact that Shared reply queues has lower performance than its alternatives Temporary and Exclusive.||object|
+|requestTimeout|The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option.|20000|duration|
+|timeToLive|When sending messages, specifies the time-to-live of the message (in milliseconds).|-1|integer|
+|allowAdditionalHeaders|This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example, some message systems, such as WMQ, do this with header names using prefix JMS\_IBM\_MQMD\_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching.||string|
+|allowNullBody|Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.|true|boolean|
+|alwaysCopyMessage|If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set)|false|boolean|
+|correlationProperty|When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel.||string|
+|disableTimeToLive|Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. Then the message will not expire on the receiver system. See below in section About time to live for more details.|false|boolean|
+|forceSendOriginalMessage|When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received.|false|boolean|
+|includeSentJMSMessageID|Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination.|false|boolean|
+|replyToCacheLevelName|Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE\_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE\_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE\_NONE to work. Note: If using temporary queues then CACHE\_NONE is not allowed, and you must use a higher value such as CACHE\_CONSUMER or CACHE\_SESSION.||string|
+|replyToDestinationSelectorName|Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue).||string|
+|streamMessageTypeEnabled|Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessage until no more data.|false|boolean|
+|allowAutoWiredConnectionFactory|Whether to auto-discover ConnectionFactory from the registry, if no connection factory has been configured. If only one instance of ConnectionFactory is found then it will be used. This is enabled by default.|true|boolean|
+|allowAutoWiredDestinationResolver|Whether to auto-discover DestinationResolver from the registry, if no destination resolver has been configured. If only one instance of DestinationResolver is found then it will be used. This is enabled by default.|true|boolean|
+|allowSerializedHeaders|Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level.|false|boolean|
+|artemisStreamingEnabled|Whether optimizing for Apache Artemis streaming mode. This can reduce memory overhead when using Artemis with JMS StreamMessage types. This option must only be enabled if Apache Artemis is being used.|false|boolean|
+|asyncStartListener|Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or fail-over. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used, then beware that if the connection could not be established, then an exception is logged at WARN level, and the consumer will not be able to receive messages; You can then restart the route to retry.|false|boolean|
+|asyncStopListener|Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|configuration|To use a shared JMS configuration||object|
+|destinationResolver|A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry).||object|
+|errorHandler|Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom errorHandler.||object|
+|exceptionListener|Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.||object|
+|idleConsumerLimit|Specify the limit for the number of consumers that are allowed to be idle at any given time.|1|integer|
+|idleTaskExecutionLimit|Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring.|1|integer|
+|includeAllJMSXProperties|Whether to include all JMSX prefixed properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply.|false|boolean|
+|includeCorrelationIDAsBytes|Whether the JMS consumer should include JMSCorrelationIDAsBytes as a header on the Camel Message.|true|boolean|
+|jmsKeyFormatStrategy|Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation.||object|
+|mapJmsMessage|Specifies whether Camel should auto map the received JMS message to a suited payload type, such as jakarta.jms.TextMessage to a String etc.|true|boolean|
+|maxMessagesPerTask|The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required.|-1|integer|
+|messageConverter|To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a jakarta.jms.Message.||object|
+|messageCreatedStrategy|To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of jakarta.jms.Message objects when Camel is sending a JMS message.||object|
+|messageIdEnabled|When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value.|true|boolean|
+|messageListenerContainerFactory|Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom.||object|
+|messageTimestampEnabled|Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value.|true|boolean|
+|pubSubNoLocal|Specifies whether to inhibit the delivery of messages published by its own connection.|false|boolean|
+|queueBrowseStrategy|To use a custom QueueBrowseStrategy when browsing queues||object|
+|receiveTimeout|The timeout for receiving messages (in milliseconds).|1000|duration|
+|recoveryInterval|Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds.|5000|duration|
+|requestTimeoutCheckerInterval|Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout.|1000|duration|
+|serviceLocationEnabled|Whether to detect the network address location of the JMS broker on startup. This information is gathered via reflection on the ConnectionFactory, and is vendor specific. This option can be used to turn this off.|true|boolean|
+|synchronous|Sets whether synchronous processing should be strictly used|false|boolean|
+|temporaryQueueResolver|A pluggable TemporaryQueueResolver that allows you to use your own resolver for creating temporary queues (some messaging systems has special requirements for creating temporary queues).||object|
+|transferException|If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a jakarta.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option takes precedence. The caught exception is required to be serializable. The original Exception on the consumer side can be wrapped in an outer exception such as org.apache.camel.RuntimeCamelException when returned to the producer. Use this with caution as the data is using Java Object serialization and requires the received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer!|false|boolean|
+|transferExchange|You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloads is an Exchange and not a regular payload. Use this with caution as the data is using Java Object serialization and requires the receiver to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumers having to use compatible Camel versions!|false|boolean|
+|trustAllPackages|Define if all Java packages are trusted or not (for Java object JMS message types). Notice its not recommended practice to send Java serialized objects over network. Setting this to true can expose security risks, so use this with care.|false|boolean|
+|useMessageIDAsCorrelationID|Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.|false|boolean|
+|waitForProvisionCorrelationToBeUpdatedCounter|Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled.|50|integer|
+|waitForProvisionCorrelationToBeUpdatedThreadSleepingTime|Interval in millis to sleep each time while waiting for provisional correlation id to be updated.|100|duration|
+|waitForTemporaryReplyToToBeUpdatedCounter|Number of times to wait for temporary replyTo queue to be created and ready when doing request/reply over JMS.|200|integer|
+|waitForTemporaryReplyToToBeUpdatedThreadSleepingTime|Interval in millis to sleep each time while waiting for temporary replyTo queue to be ready.|100|duration|
+|headerFilterStrategy|To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.||object|
+|errorHandlerLoggingLevel|Allows to configure the default errorHandler logging level for logging uncaught exceptions.|WARN|object|
+|errorHandlerLogStackTrace|Allows to control whether stack-traces should be logged or not, by the default errorHandler.|true|boolean|
+|password|Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.||string|
+|username|Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.||string|
+|transacted|Specifies whether to use transacted mode|false|boolean|
+|transactedInOut|Specifies whether InOut operations (request reply) default to using transacted mode If this flag is set to true, then Spring JmsTemplate will have sessionTransacted set to true, and the acknowledgeMode as transacted on the JmsTemplate used for InOut operations. Note from Spring JMS: that within a JTA transaction, the parameters passed to createQueue, createTopic methods are not taken into account. Depending on the Java EE transaction context, the container makes its own decisions on these values. Analogously, these parameters are not taken into account within a locally managed transaction either, since Spring JMS operates on an existing JMS Session in this case. Setting this flag to true will use a short local JMS transaction when running outside of a managed transaction, and a synchronized local JMS transaction in case of a managed transaction (other than an XA transaction) being present. This has the effect of a local JMS transaction being managed alongside the main transaction (which might be a native JDBC transaction), with the JMS transaction committing right after the main transaction.|false|boolean|
+|lazyCreateTransactionManager|If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.|true|boolean|
+|transactionManager|The Spring transaction manager to use.||object|
+|transactionName|The name of the transaction to use.||string|
+|transactionTimeout|The timeout value of the transaction (in seconds), if using transacted mode.|-1|integer|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|destinationType|The kind of destination to use|queue|string|
+|destinationName|Name of the queue or topic to use as destination||string|
+|clientId|Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions with JMS 1.1.||string|
+|connectionFactory|The connection factory to be use. A connection factory must be configured either on the component or endpoint.||object|
+|disableReplyTo|Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different message brokers and you want to route message from one system to another.|false|boolean|
+|durableSubscriptionName|The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.||string|
+|jmsMessageType|Allows you to force the use of a specific jakarta.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it.||object|
+|replyTo|Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer).||string|
+|testConnectionOnStartup|Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well.|false|boolean|
+|acknowledgementModeName|The JMS acknowledgement name, which is one of: SESSION\_TRANSACTED, CLIENT\_ACKNOWLEDGE, AUTO\_ACKNOWLEDGE, DUPS\_OK\_ACKNOWLEDGE|AUTO\_ACKNOWLEDGE|string|
+|artemisConsumerPriority|Consumer priorities allow you to ensure that high priority consumers receive messages while they are active. Normally, active consumers connected to a queue receive messages from it in a round-robin fashion. When consumer priorities are in use, messages are delivered round-robin if multiple active consumers exist with the same high priority. Messages will only going to lower priority consumers when the high priority consumers do not have credit available to consume the message, or those high priority consumers have declined to accept the message (for instance because it does not meet the criteria of any selectors associated with the consumer).||integer|
+|asyncConsumer|Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note if transacted has been enabled, then asyncConsumer=true does not run asynchronously, as transaction must be executed synchronously (Camel 3.0 may support async transactions).|false|boolean|
+|autoStartup|Specifies whether the consumer container should auto-startup.|true|boolean|
+|cacheLevel|Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.||integer|
+|cacheLevelName|Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE\_AUTO, CACHE\_CONNECTION, CACHE\_CONSUMER, CACHE\_NONE, and CACHE\_SESSION. The default setting is CACHE\_AUTO. See the Spring documentation and Transactions Cache Levels for more information.|CACHE\_AUTO|string|
+|concurrentConsumers|Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.|1|integer|
+|maxConcurrentConsumers|Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.||integer|
+|replyToDeliveryPersistent|Specifies whether to use persistent delivery by default for replies.|true|boolean|
+|selector|Sets the JMS selector to use||string|
+|subscriptionDurable|Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well.|false|boolean|
+|subscriptionName|Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS 2.0).||string|
+|subscriptionShared|Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined with subscriptionDurable as well. Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well. Requires a JMS 2.0 compatible message broker.|false|boolean|
+|acceptMessagesWhileStopping|Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option.|false|boolean|
+|allowReplyManagerQuickStop|Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag.|false|boolean|
+|consumerType|The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.|Default|object|
+|defaultTaskExecutorType|Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached thread-pool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of ThreadPool is recommended to reduce thread trash in elastic configurations with dynamically increasing and decreasing concurrent consumers.||object|
+|destinationOptions|Destination Options are a way to provide extended configuration options to a JMS consumer without having to extend the JMS API. The options are encoded using URL query syntax in the destination name that the consumer is created on. See more details at https://activemq.apache.org/destination-options.||object|
+|eagerLoadingOfProperties|Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody.|false|boolean|
+|eagerPoisonBody|If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties.|Poison JMS message due to ${exception.message}|string|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|exposeListenerSession|Specifies whether the listener session should be exposed when consuming messages.|false|boolean|
+|replyToConsumerType|The consumer type of the reply consumer (when doing request/reply), which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.|Default|object|
+|replyToSameDestinationAllowed|Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself.|false|boolean|
+|taskExecutor|Allows you to specify a custom task executor for consuming messages.||object|
+|deliveryDelay|Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker.|-1|integer|
+|deliveryMode|Specifies the delivery mode to be used. Possible values are those defined by jakarta.jms.DeliveryMode. NON\_PERSISTENT = 1 and PERSISTENT = 2.||integer|
+|deliveryPersistent|Specifies whether persistent delivery is used by default.|true|boolean|
+|explicitQosEnabled|Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers.|false|boolean|
+|formatDateHeadersToIso8601|Sets whether JMS date properties should be formatted according to the ISO 8601 standard.|false|boolean|
+|preserveMessageQos|Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explicitQosEnabled option, by contrast, will only use options set on the endpoint, and not values from the message header.|false|boolean|
+|priority|Values greater than 1 specify the message priority when sending (where 1 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect.|4|integer|
+|replyToConcurrentConsumers|Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.|1|integer|
+|replyToMaxConcurrentConsumers|Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.||integer|
+|replyToOnTimeoutMaxConcurrentConsumers|Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS.|1|integer|
+|replyToOverride|Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination.||string|
+|replyToType|Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications if running in a clustered environment, and the fact that Shared reply queues has lower performance than its alternatives Temporary and Exclusive.||object|
+|requestTimeout|The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option.|20000|duration|
+|timeToLive|When sending messages, specifies the time-to-live of the message (in milliseconds).|-1|integer|
+|allowAdditionalHeaders|This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example, some message systems, such as WMQ, do this with header names using prefix JMS\_IBM\_MQMD\_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching.||string|
+|allowNullBody|Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.|true|boolean|
+|alwaysCopyMessage|If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set)|false|boolean|
+|correlationProperty|When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel.||string|
+|disableTimeToLive|Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. Then the message will not expire on the receiver system. See below in section About time to live for more details.|false|boolean|
+|forceSendOriginalMessage|When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received.|false|boolean|
+|includeSentJMSMessageID|Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|replyToCacheLevelName|Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE\_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE\_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE\_NONE to work. Note: If using temporary queues then CACHE\_NONE is not allowed, and you must use a higher value such as CACHE\_CONSUMER or CACHE\_SESSION.||string|
+|replyToDestinationSelectorName|Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue).||string|
+|streamMessageTypeEnabled|Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessage until no more data.|false|boolean|
+|allowSerializedHeaders|Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level.|false|boolean|
+|artemisStreamingEnabled|Whether optimizing for Apache Artemis streaming mode. This can reduce memory overhead when using Artemis with JMS StreamMessage types. This option must only be enabled if Apache Artemis is being used.|false|boolean|
+|asyncStartListener|Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or fail-over. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used, then beware that if the connection could not be established, then an exception is logged at WARN level, and the consumer will not be able to receive messages; You can then restart the route to retry.|false|boolean|
+|asyncStopListener|Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.|false|boolean|
+|destinationResolver|A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry).||object|
+|errorHandler|Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom errorHandler.||object|
+|exceptionListener|Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.||object|
+|headerFilterStrategy|To use a custom HeaderFilterStrategy to filter header to and from Camel message.||object|
+|idleConsumerLimit|Specify the limit for the number of consumers that are allowed to be idle at any given time.|1|integer|
+|idleTaskExecutionLimit|Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring.|1|integer|
+|includeAllJMSXProperties|Whether to include all JMSX prefixed properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply.|false|boolean|
+|jmsKeyFormatStrategy|Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation.||object|
+|mapJmsMessage|Specifies whether Camel should auto map the received JMS message to a suited payload type, such as jakarta.jms.TextMessage to a String etc.|true|boolean|
+|maxMessagesPerTask|The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required.|-1|integer|
+|messageConverter|To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a jakarta.jms.Message.||object|
+|messageCreatedStrategy|To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of jakarta.jms.Message objects when Camel is sending a JMS message.||object|
+|messageIdEnabled|When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value.|true|boolean|
+|messageListenerContainerFactory|Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom.||object|
+|messageTimestampEnabled|Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value.|true|boolean|
+|pubSubNoLocal|Specifies whether to inhibit the delivery of messages published by its own connection.|false|boolean|
+|receiveTimeout|The timeout for receiving messages (in milliseconds).|1000|duration|
+|recoveryInterval|Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds.|5000|duration|
+|requestTimeoutCheckerInterval|Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout.|1000|duration|
+|synchronous|Sets whether synchronous processing should be strictly used|false|boolean|
+|temporaryQueueResolver|A pluggable TemporaryQueueResolver that allows you to use your own resolver for creating temporary queues (some messaging systems has special requirements for creating temporary queues).||object|
+|transferException|If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a jakarta.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option takes precedence. The caught exception is required to be serializable. The original Exception on the consumer side can be wrapped in an outer exception such as org.apache.camel.RuntimeCamelException when returned to the producer. Use this with caution as the data is using Java Object serialization and requires the received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer!|false|boolean|
+|transferExchange|You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloads is an Exchange and not a regular payload. Use this with caution as the data is using Java Object serialization and requires the receiver to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumers having to use compatible Camel versions!|false|boolean|
+|useMessageIDAsCorrelationID|Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.|false|boolean|
+|waitForProvisionCorrelationToBeUpdatedCounter|Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled.|50|integer|
+|waitForProvisionCorrelationToBeUpdatedThreadSleepingTime|Interval in millis to sleep each time while waiting for provisional correlation id to be updated.|100|duration|
+|waitForTemporaryReplyToToBeUpdatedCounter|Number of times to wait for temporary replyTo queue to be created and ready when doing request/reply over JMS.|200|integer|
+|waitForTemporaryReplyToToBeUpdatedThreadSleepingTime|Interval in millis to sleep each time while waiting for temporary replyTo queue to be ready.|100|duration|
+|errorHandlerLoggingLevel|Allows to configure the default errorHandler logging level for logging uncaught exceptions.|WARN|object|
+|errorHandlerLogStackTrace|Allows to control whether stack-traces should be logged or not, by the default errorHandler.|true|boolean|
+|password|Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.||string|
+|username|Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.||string|
+|transacted|Specifies whether to use transacted mode|false|boolean|
+|transactedInOut|Specifies whether InOut operations (request reply) default to using transacted mode If this flag is set to true, then Spring JmsTemplate will have sessionTransacted set to true, and the acknowledgeMode as transacted on the JmsTemplate used for InOut operations. Note from Spring JMS: that within a JTA transaction, the parameters passed to createQueue, createTopic methods are not taken into account. Depending on the Java EE transaction context, the container makes its own decisions on these values. Analogously, these parameters are not taken into account within a locally managed transaction either, since Spring JMS operates on an existing JMS Session in this case. Setting this flag to true will use a short local JMS transaction when running outside of a managed transaction, and a synchronized local JMS transaction in case of a managed transaction (other than an XA transaction) being present. This has the effect of a local JMS transaction being managed alongside the main transaction (which might be a native JDBC transaction), with the JMS transaction committing right after the main transaction.|false|boolean|
+|lazyCreateTransactionManager|If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.|true|boolean|
+|transactionManager|The Spring transaction manager to use.||object|
+|transactionName|The name of the transaction to use.||string|
+|transactionTimeout|The timeout value of the transaction (in seconds), if using transacted mode.|-1|integer|

camel-activemq6.md

@@ -0,0 +1,276 @@
+# Activemq6
+
+**Since Camel 4.7**
+
+**Both producer and consumer are supported**
+
+The ActiveMQ component is an extension to the JMS component and has been
+pre-configured for using Apache ActiveMQ 6.x (not Artemis). Users of
+Apache ActiveMQ Artemis should use the JMS component.
+
+The camel-activemq component is best intended for ActiveMQ 6.x brokers.
+If you use ActiveMQ 5.x brokers, then use the camel-activemq 5.x
+component instead.
+
+**More documentation**
+
+See the JMS component for more documentation and examples
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-activemq</artifactId>
+        <version>x.x.x</version>
+        <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# URI format
+
+    activemq:[queue:|topic:]destinationName[?options]
+
+Where `destinationName` is a JMS queue or topic name. By default, the
+`destinationName` is interpreted as a queue name. For example, to
+connect to the queue, `foo` use:
+
+    activemq:foo
+
+# Examples
+
+You’ll need to provide a connectionFactory to the ActiveMQ Component, to
+have the following examples working.
+
+## Producer Example
+
+    from("timer:mytimer?period=5000")
+            .setBody(constant("HELLO from Camel!"))
+            .to("activemq:queue:HELLO.WORLD");
+
+## Consumer Example
+
+    from("activemq:queue:HELLO.WORLD")
+            .log("Received a message - ${body}");
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|brokerURL|Sets the broker URL to use to connect to ActiveMQ. If none configured then localhost:61616 is used by default (however can be overridden by configuration from environment variables)||string|
+|clientId|Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions with JMS 1.1.||string|
+|connectionFactory|The connection factory to be use. A connection factory must be configured either on the component or endpoint.||object|
+|disableReplyTo|Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different message brokers and you want to route message from one system to another.|false|boolean|
+|durableSubscriptionName|The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.||string|
+|embedded|Use an embedded in-memory (non-persistent) ActiveMQ broker for development and testing purposes. You must have activemq-broker JAR on the classpath.|false|boolean|
+|jmsMessageType|Allows you to force the use of a specific jakarta.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it.||object|
+|replyTo|Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer).||string|
+|testConnectionOnStartup|Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well.|false|boolean|
+|usePooledConnection|Enables or disables whether a PooledConnectionFactory will be used so that when messages are sent to ActiveMQ from outside a message consuming thread, pooling will be used rather than the default with the Spring JmsTemplate which will create a new connection, session, producer for each message then close them all down again. The default value is true.|true|boolean|
+|useSingleConnection|Enables or disables whether a Spring SingleConnectionFactory will be used so that when messages are sent to ActiveMQ from outside a message consuming thread, pooling will be used rather than the default with the Spring JmsTemplate which will create a new connection, session, producer for each message then close them all down again. The default value is false and a pooled connection is used by default.|false|boolean|
+|acknowledgementModeName|The JMS acknowledgement name, which is one of: SESSION\_TRANSACTED, CLIENT\_ACKNOWLEDGE, AUTO\_ACKNOWLEDGE, DUPS\_OK\_ACKNOWLEDGE|AUTO\_ACKNOWLEDGE|string|
+|artemisConsumerPriority|Consumer priorities allow you to ensure that high priority consumers receive messages while they are active. Normally, active consumers connected to a queue receive messages from it in a round-robin fashion. When consumer priorities are in use, messages are delivered round-robin if multiple active consumers exist with the same high priority. Messages will only going to lower priority consumers when the high priority consumers do not have credit available to consume the message, or those high priority consumers have declined to accept the message (for instance because it does not meet the criteria of any selectors associated with the consumer).||integer|
+|asyncConsumer|Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note if transacted has been enabled, then asyncConsumer=true does not run asynchronously, as transaction must be executed synchronously (Camel 3.0 may support async transactions).|false|boolean|
+|autoStartup|Specifies whether the consumer container should auto-startup.|true|boolean|
+|cacheLevel|Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.||integer|
+|cacheLevelName|Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE\_AUTO, CACHE\_CONNECTION, CACHE\_CONSUMER, CACHE\_NONE, and CACHE\_SESSION. The default setting is CACHE\_AUTO. See the Spring documentation and Transactions Cache Levels for more information.|CACHE\_AUTO|string|
+|concurrentConsumers|Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.|1|integer|
+|maxConcurrentConsumers|Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.||integer|
+|replyToDeliveryPersistent|Specifies whether to use persistent delivery by default for replies.|true|boolean|
+|selector|Sets the JMS selector to use||string|
+|subscriptionDurable|Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well.|false|boolean|
+|subscriptionName|Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS 2.0).||string|
+|subscriptionShared|Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined with subscriptionDurable as well. Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well. Requires a JMS 2.0 compatible message broker.|false|boolean|
+|acceptMessagesWhileStopping|Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option.|false|boolean|
+|allowReplyManagerQuickStop|Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag.|false|boolean|
+|consumerType|The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.|Default|object|
+|defaultTaskExecutorType|Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached thread-pool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of ThreadPool is recommended to reduce thread trash in elastic configurations with dynamically increasing and decreasing concurrent consumers.||object|
+|eagerLoadingOfProperties|Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody.|false|boolean|
+|eagerPoisonBody|If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties.|Poison JMS message due to ${exception.message}|string|
+|exposeListenerSession|Specifies whether the listener session should be exposed when consuming messages.|false|boolean|
+|replyToConsumerType|The consumer type of the reply consumer (when doing request/reply), which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.|Default|object|
+|replyToSameDestinationAllowed|Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself.|false|boolean|
+|taskExecutor|Allows you to specify a custom task executor for consuming messages.||object|
+|deliveryDelay|Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker.|-1|integer|
+|deliveryMode|Specifies the delivery mode to be used. Possible values are those defined by jakarta.jms.DeliveryMode. NON\_PERSISTENT = 1 and PERSISTENT = 2.||integer|
+|deliveryPersistent|Specifies whether persistent delivery is used by default.|true|boolean|
+|explicitQosEnabled|Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers.|false|boolean|
+|formatDateHeadersToIso8601|Sets whether JMS date properties should be formatted according to the ISO 8601 standard.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|preserveMessageQos|Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explicitQosEnabled option, by contrast, will only use options set on the endpoint, and not values from the message header.|false|boolean|
+|priority|Values greater than 1 specify the message priority when sending (where 1 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect.|4|integer|
+|replyToConcurrentConsumers|Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.|1|integer|
+|replyToMaxConcurrentConsumers|Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.||integer|
+|replyToOnTimeoutMaxConcurrentConsumers|Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS.|1|integer|
+|replyToOverride|Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination.||string|
+|replyToType|Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications if running in a clustered environment, and the fact that Shared reply queues has lower performance than its alternatives Temporary and Exclusive.||object|
+|requestTimeout|The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option.|20000|duration|
+|timeToLive|When sending messages, specifies the time-to-live of the message (in milliseconds).|-1|integer|
+|allowAdditionalHeaders|This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example, some message systems, such as WMQ, do this with header names using prefix JMS\_IBM\_MQMD\_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching.||string|
+|allowNullBody|Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.|true|boolean|
+|alwaysCopyMessage|If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set)|false|boolean|
+|correlationProperty|When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel.||string|
+|disableTimeToLive|Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. Then the message will not expire on the receiver system. See below in section About time to live for more details.|false|boolean|
+|forceSendOriginalMessage|When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received.|false|boolean|
+|includeSentJMSMessageID|Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination.|false|boolean|
+|replyToCacheLevelName|Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE\_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE\_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE\_NONE to work. Note: If using temporary queues then CACHE\_NONE is not allowed, and you must use a higher value such as CACHE\_CONSUMER or CACHE\_SESSION.||string|
+|replyToDestinationSelectorName|Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue).||string|
+|streamMessageTypeEnabled|Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessage until no more data.|false|boolean|
+|allowAutoWiredConnectionFactory|Whether to auto-discover ConnectionFactory from the registry, if no connection factory has been configured. If only one instance of ConnectionFactory is found then it will be used. This is enabled by default.|true|boolean|
+|allowAutoWiredDestinationResolver|Whether to auto-discover DestinationResolver from the registry, if no destination resolver has been configured. If only one instance of DestinationResolver is found then it will be used. This is enabled by default.|true|boolean|
+|allowSerializedHeaders|Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level.|false|boolean|
+|artemisStreamingEnabled|Whether optimizing for Apache Artemis streaming mode. This can reduce memory overhead when using Artemis with JMS StreamMessage types. This option must only be enabled if Apache Artemis is being used.|false|boolean|
+|asyncStartListener|Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or fail-over. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used, then beware that if the connection could not be established, then an exception is logged at WARN level, and the consumer will not be able to receive messages; You can then restart the route to retry.|false|boolean|
+|asyncStopListener|Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|configuration|To use a shared JMS configuration||object|
+|destinationResolver|A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry).||object|
+|errorHandler|Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom errorHandler.||object|
+|exceptionListener|Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.||object|
+|idleConsumerLimit|Specify the limit for the number of consumers that are allowed to be idle at any given time.|1|integer|
+|idleTaskExecutionLimit|Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring.|1|integer|
+|includeAllJMSXProperties|Whether to include all JMSX prefixed properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply.|false|boolean|
+|includeCorrelationIDAsBytes|Whether the JMS consumer should include JMSCorrelationIDAsBytes as a header on the Camel Message.|true|boolean|
+|jmsKeyFormatStrategy|Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation.||object|
+|mapJmsMessage|Specifies whether Camel should auto map the received JMS message to a suited payload type, such as jakarta.jms.TextMessage to a String etc.|true|boolean|
+|maxMessagesPerTask|The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required.|-1|integer|
+|messageConverter|To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a jakarta.jms.Message.||object|
+|messageCreatedStrategy|To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of jakarta.jms.Message objects when Camel is sending a JMS message.||object|
+|messageIdEnabled|When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value.|true|boolean|
+|messageListenerContainerFactory|Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom.||object|
+|messageTimestampEnabled|Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value.|true|boolean|
+|pubSubNoLocal|Specifies whether to inhibit the delivery of messages published by its own connection.|false|boolean|
+|queueBrowseStrategy|To use a custom QueueBrowseStrategy when browsing queues||object|
+|receiveTimeout|The timeout for receiving messages (in milliseconds).|1000|duration|
+|recoveryInterval|Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds.|5000|duration|
+|requestTimeoutCheckerInterval|Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout.|1000|duration|
+|serviceLocationEnabled|Whether to detect the network address location of the JMS broker on startup. This information is gathered via reflection on the ConnectionFactory, and is vendor specific. This option can be used to turn this off.|true|boolean|
+|synchronous|Sets whether synchronous processing should be strictly used|false|boolean|
+|temporaryQueueResolver|A pluggable TemporaryQueueResolver that allows you to use your own resolver for creating temporary queues (some messaging systems has special requirements for creating temporary queues).||object|
+|transferException|If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a jakarta.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option takes precedence. The caught exception is required to be serializable. The original Exception on the consumer side can be wrapped in an outer exception such as org.apache.camel.RuntimeCamelException when returned to the producer. Use this with caution as the data is using Java Object serialization and requires the received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer!|false|boolean|
+|transferExchange|You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloads is an Exchange and not a regular payload. Use this with caution as the data is using Java Object serialization and requires the receiver to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumers having to use compatible Camel versions!|false|boolean|
+|trustAllPackages|Define if all Java packages are trusted or not (for Java object JMS message types). Notice its not recommended practice to send Java serialized objects over network. Setting this to true can expose security risks, so use this with care.|false|boolean|
+|useMessageIDAsCorrelationID|Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.|false|boolean|
+|waitForProvisionCorrelationToBeUpdatedCounter|Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled.|50|integer|
+|waitForProvisionCorrelationToBeUpdatedThreadSleepingTime|Interval in millis to sleep each time while waiting for provisional correlation id to be updated.|100|duration|
+|waitForTemporaryReplyToToBeUpdatedCounter|Number of times to wait for temporary replyTo queue to be created and ready when doing request/reply over JMS.|200|integer|
+|waitForTemporaryReplyToToBeUpdatedThreadSleepingTime|Interval in millis to sleep each time while waiting for temporary replyTo queue to be ready.|100|duration|
+|headerFilterStrategy|To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.||object|
+|errorHandlerLoggingLevel|Allows to configure the default errorHandler logging level for logging uncaught exceptions.|WARN|object|
+|errorHandlerLogStackTrace|Allows to control whether stack-traces should be logged or not, by the default errorHandler.|true|boolean|
+|password|Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.||string|
+|username|Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.||string|
+|transacted|Specifies whether to use transacted mode|false|boolean|
+|transactedInOut|Specifies whether InOut operations (request reply) default to using transacted mode If this flag is set to true, then Spring JmsTemplate will have sessionTransacted set to true, and the acknowledgeMode as transacted on the JmsTemplate used for InOut operations. Note from Spring JMS: that within a JTA transaction, the parameters passed to createQueue, createTopic methods are not taken into account. Depending on the Java EE transaction context, the container makes its own decisions on these values. Analogously, these parameters are not taken into account within a locally managed transaction either, since Spring JMS operates on an existing JMS Session in this case. Setting this flag to true will use a short local JMS transaction when running outside of a managed transaction, and a synchronized local JMS transaction in case of a managed transaction (other than an XA transaction) being present. This has the effect of a local JMS transaction being managed alongside the main transaction (which might be a native JDBC transaction), with the JMS transaction committing right after the main transaction.|false|boolean|
+|lazyCreateTransactionManager|If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.|true|boolean|
+|transactionManager|The Spring transaction manager to use.||object|
+|transactionName|The name of the transaction to use.||string|
+|transactionTimeout|The timeout value of the transaction (in seconds), if using transacted mode.|-1|integer|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|destinationType|The kind of destination to use|queue|string|
+|destinationName|Name of the queue or topic to use as destination||string|
+|clientId|Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions with JMS 1.1.||string|
+|connectionFactory|The connection factory to be use. A connection factory must be configured either on the component or endpoint.||object|
+|disableReplyTo|Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different message brokers and you want to route message from one system to another.|false|boolean|
+|durableSubscriptionName|The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.||string|
+|jmsMessageType|Allows you to force the use of a specific jakarta.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it.||object|
+|replyTo|Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer).||string|
+|testConnectionOnStartup|Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well.|false|boolean|
+|acknowledgementModeName|The JMS acknowledgement name, which is one of: SESSION\_TRANSACTED, CLIENT\_ACKNOWLEDGE, AUTO\_ACKNOWLEDGE, DUPS\_OK\_ACKNOWLEDGE|AUTO\_ACKNOWLEDGE|string|
+|artemisConsumerPriority|Consumer priorities allow you to ensure that high priority consumers receive messages while they are active. Normally, active consumers connected to a queue receive messages from it in a round-robin fashion. When consumer priorities are in use, messages are delivered round-robin if multiple active consumers exist with the same high priority. Messages will only going to lower priority consumers when the high priority consumers do not have credit available to consume the message, or those high priority consumers have declined to accept the message (for instance because it does not meet the criteria of any selectors associated with the consumer).||integer|
+|asyncConsumer|Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note if transacted has been enabled, then asyncConsumer=true does not run asynchronously, as transaction must be executed synchronously (Camel 3.0 may support async transactions).|false|boolean|
+|autoStartup|Specifies whether the consumer container should auto-startup.|true|boolean|
+|cacheLevel|Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.||integer|
+|cacheLevelName|Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE\_AUTO, CACHE\_CONNECTION, CACHE\_CONSUMER, CACHE\_NONE, and CACHE\_SESSION. The default setting is CACHE\_AUTO. See the Spring documentation and Transactions Cache Levels for more information.|CACHE\_AUTO|string|
+|concurrentConsumers|Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.|1|integer|
+|maxConcurrentConsumers|Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.||integer|
+|replyToDeliveryPersistent|Specifies whether to use persistent delivery by default for replies.|true|boolean|
+|selector|Sets the JMS selector to use||string|
+|subscriptionDurable|Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well.|false|boolean|
+|subscriptionName|Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS 2.0).||string|
+|subscriptionShared|Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined with subscriptionDurable as well. Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well. Requires a JMS 2.0 compatible message broker.|false|boolean|
+|acceptMessagesWhileStopping|Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option.|false|boolean|
+|allowReplyManagerQuickStop|Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag.|false|boolean|
+|consumerType|The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.|Default|object|
+|defaultTaskExecutorType|Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached thread-pool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of ThreadPool is recommended to reduce thread trash in elastic configurations with dynamically increasing and decreasing concurrent consumers.||object|
+|destinationOptions|Destination Options are a way to provide extended configuration options to a JMS consumer without having to extend the JMS API. The options are encoded using URL query syntax in the destination name that the consumer is created on. See more details at https://activemq.apache.org/destination-options.||object|
+|eagerLoadingOfProperties|Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody.|false|boolean|
+|eagerPoisonBody|If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties.|Poison JMS message due to ${exception.message}|string|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|exposeListenerSession|Specifies whether the listener session should be exposed when consuming messages.|false|boolean|
+|replyToConsumerType|The consumer type of the reply consumer (when doing request/reply), which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.|Default|object|
+|replyToSameDestinationAllowed|Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself.|false|boolean|
+|taskExecutor|Allows you to specify a custom task executor for consuming messages.||object|
+|deliveryDelay|Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker.|-1|integer|
+|deliveryMode|Specifies the delivery mode to be used. Possible values are those defined by jakarta.jms.DeliveryMode. NON\_PERSISTENT = 1 and PERSISTENT = 2.||integer|
+|deliveryPersistent|Specifies whether persistent delivery is used by default.|true|boolean|
+|explicitQosEnabled|Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers.|false|boolean|
+|formatDateHeadersToIso8601|Sets whether JMS date properties should be formatted according to the ISO 8601 standard.|false|boolean|
+|preserveMessageQos|Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explicitQosEnabled option, by contrast, will only use options set on the endpoint, and not values from the message header.|false|boolean|
+|priority|Values greater than 1 specify the message priority when sending (where 1 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect.|4|integer|
+|replyToConcurrentConsumers|Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.|1|integer|
+|replyToMaxConcurrentConsumers|Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.||integer|
+|replyToOnTimeoutMaxConcurrentConsumers|Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS.|1|integer|
+|replyToOverride|Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination.||string|
+|replyToType|Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications if running in a clustered environment, and the fact that Shared reply queues has lower performance than its alternatives Temporary and Exclusive.||object|
+|requestTimeout|The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option.|20000|duration|
+|timeToLive|When sending messages, specifies the time-to-live of the message (in milliseconds).|-1|integer|
+|allowAdditionalHeaders|This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example, some message systems, such as WMQ, do this with header names using prefix JMS\_IBM\_MQMD\_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching.||string|
+|allowNullBody|Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.|true|boolean|
+|alwaysCopyMessage|If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set)|false|boolean|
+|correlationProperty|When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel.||string|
+|disableTimeToLive|Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. Then the message will not expire on the receiver system. See below in section About time to live for more details.|false|boolean|
+|forceSendOriginalMessage|When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received.|false|boolean|
+|includeSentJMSMessageID|Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|replyToCacheLevelName|Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE\_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE\_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE\_NONE to work. Note: If using temporary queues then CACHE\_NONE is not allowed, and you must use a higher value such as CACHE\_CONSUMER or CACHE\_SESSION.||string|
+|replyToDestinationSelectorName|Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue).||string|
+|streamMessageTypeEnabled|Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessage until no more data.|false|boolean|
+|allowSerializedHeaders|Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level.|false|boolean|
+|artemisStreamingEnabled|Whether optimizing for Apache Artemis streaming mode. This can reduce memory overhead when using Artemis with JMS StreamMessage types. This option must only be enabled if Apache Artemis is being used.|false|boolean|
+|asyncStartListener|Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or fail-over. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used, then beware that if the connection could not be established, then an exception is logged at WARN level, and the consumer will not be able to receive messages; You can then restart the route to retry.|false|boolean|
+|asyncStopListener|Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.|false|boolean|
+|destinationResolver|A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry).||object|
+|errorHandler|Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom errorHandler.||object|
+|exceptionListener|Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.||object|
+|headerFilterStrategy|To use a custom HeaderFilterStrategy to filter header to and from Camel message.||object|
+|idleConsumerLimit|Specify the limit for the number of consumers that are allowed to be idle at any given time.|1|integer|
+|idleTaskExecutionLimit|Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring.|1|integer|
+|includeAllJMSXProperties|Whether to include all JMSX prefixed properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply.|false|boolean|
+|jmsKeyFormatStrategy|Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation.||object|
+|mapJmsMessage|Specifies whether Camel should auto map the received JMS message to a suited payload type, such as jakarta.jms.TextMessage to a String etc.|true|boolean|
+|maxMessagesPerTask|The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required.|-1|integer|
+|messageConverter|To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a jakarta.jms.Message.||object|
+|messageCreatedStrategy|To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of jakarta.jms.Message objects when Camel is sending a JMS message.||object|
+|messageIdEnabled|When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value.|true|boolean|
+|messageListenerContainerFactory|Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom.||object|
+|messageTimestampEnabled|Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value.|true|boolean|
+|pubSubNoLocal|Specifies whether to inhibit the delivery of messages published by its own connection.|false|boolean|
+|receiveTimeout|The timeout for receiving messages (in milliseconds).|1000|duration|
+|recoveryInterval|Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds.|5000|duration|
+|requestTimeoutCheckerInterval|Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout.|1000|duration|
+|synchronous|Sets whether synchronous processing should be strictly used|false|boolean|
+|temporaryQueueResolver|A pluggable TemporaryQueueResolver that allows you to use your own resolver for creating temporary queues (some messaging systems has special requirements for creating temporary queues).||object|
+|transferException|If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a jakarta.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option takes precedence. The caught exception is required to be serializable. The original Exception on the consumer side can be wrapped in an outer exception such as org.apache.camel.RuntimeCamelException when returned to the producer. Use this with caution as the data is using Java Object serialization and requires the received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer!|false|boolean|
+|transferExchange|You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloads is an Exchange and not a regular payload. Use this with caution as the data is using Java Object serialization and requires the receiver to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumers having to use compatible Camel versions!|false|boolean|
+|useMessageIDAsCorrelationID|Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.|false|boolean|
+|waitForProvisionCorrelationToBeUpdatedCounter|Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled.|50|integer|
+|waitForProvisionCorrelationToBeUpdatedThreadSleepingTime|Interval in millis to sleep each time while waiting for provisional correlation id to be updated.|100|duration|
+|waitForTemporaryReplyToToBeUpdatedCounter|Number of times to wait for temporary replyTo queue to be created and ready when doing request/reply over JMS.|200|integer|
+|waitForTemporaryReplyToToBeUpdatedThreadSleepingTime|Interval in millis to sleep each time while waiting for temporary replyTo queue to be ready.|100|duration|
+|errorHandlerLoggingLevel|Allows to configure the default errorHandler logging level for logging uncaught exceptions.|WARN|object|
+|errorHandlerLogStackTrace|Allows to control whether stack-traces should be logged or not, by the default errorHandler.|true|boolean|
+|password|Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.||string|
+|username|Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.||string|
+|transacted|Specifies whether to use transacted mode|false|boolean|
+|transactedInOut|Specifies whether InOut operations (request reply) default to using transacted mode If this flag is set to true, then Spring JmsTemplate will have sessionTransacted set to true, and the acknowledgeMode as transacted on the JmsTemplate used for InOut operations. Note from Spring JMS: that within a JTA transaction, the parameters passed to createQueue, createTopic methods are not taken into account. Depending on the Java EE transaction context, the container makes its own decisions on these values. Analogously, these parameters are not taken into account within a locally managed transaction either, since Spring JMS operates on an existing JMS Session in this case. Setting this flag to true will use a short local JMS transaction when running outside of a managed transaction, and a synchronized local JMS transaction in case of a managed transaction (other than an XA transaction) being present. This has the effect of a local JMS transaction being managed alongside the main transaction (which might be a native JDBC transaction), with the JMS transaction committing right after the main transaction.|false|boolean|
+|lazyCreateTransactionManager|If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.|true|boolean|
+|transactionManager|The Spring transaction manager to use.||object|
+|transactionName|The name of the transaction to use.||string|
+|transactionTimeout|The timeout value of the transaction (in seconds), if using transacted mode.|-1|integer|

camel-amqp.md

@@ -0,0 +1,337 @@
+# Amqp
+
+**Since Camel 1.2**
+
+**Both producer and consumer are supported**
+
+The AMQP component supports the [AMQP 1.0
+protocol](http://www.amqp.org/) using the JMS Client API of the
+[Qpid](http://qpid.apache.org/) project.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-amqp</artifactId>
+        <version>${camel.version}</version> <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# URI format
+
+    amqp:[queue:|topic:]destinationName[?options]
+
+# Usage
+
+As AMQP component is inherited from JMS component, the usage of the
+former is almost identical to the latter:
+
+**Using AMQP component**
+
+    // Consuming from AMQP queue
+    from("amqp:queue:incoming").
+      to(...);
+    
+    // Sending messages to the AMQP topic
+    from(...).
+      to("amqp:topic:notify");
+
+# Configuring AMQP component
+
+**Creating AMQP 1.0 component**
+
+    AMQPComponent amqp = AMQPComponent.amqpComponent("amqp://localhost:5672");
+    
+    AMQPComponent authorizedAmqp = AMQPComponent.amqpComponent("amqp://localhost:5672", "user", "password");
+
+You can also add an instance of
+`org.apache.camel.component.amqp.AMQPConnectionDetails` to the registry
+to automatically configure the AMQP component. For example, for Spring
+Boot, you have to define bean:
+
+**AMQP connection details auto-configuration**
+
+    @Bean
+    AMQPConnectionDetails amqpConnection() {
+      return new AMQPConnectionDetails("amqp://localhost:5672");
+    }
+    
+    @Bean
+    AMQPConnectionDetails securedAmqpConnection() {
+      return new AMQPConnectionDetails("amqp://localhost:5672", "username", "password");
+    }
+
+Likewise, you can also use CDI producer methods when using Camel-CDI
+
+**AMQP connection details auto-configuration for CDI**
+
+    @Produces
+    AMQPConnectionDetails amqpConnection() {
+      return new AMQPConnectionDetails("amqp://localhost:5672");
+    }
+
+You can also rely on the [Camel properties](#properties-component.adoc)
+to read the AMQP connection details. Factory method
+`AMQPConnectionDetails.discoverAMQP()` attempts to read Camel properties
+in a Kubernetes-like convention, just as demonstrated on the snippet
+below:
+
+**AMQP connection details auto-configuration**
+
+    export AMQP_SERVICE_HOST = "mybroker.com"
+    export AMQP_SERVICE_PORT = "6666"
+    export AMQP_SERVICE_USERNAME = "username"
+    export AMQP_SERVICE_PASSWORD = "password"
+    
+    ...
+    
+    @Bean
+    AMQPConnectionDetails amqpConnection() {
+      return AMQPConnectionDetails.discoverAMQP();
+    }
+
+**Enabling AMQP specific options**
+
+If you, for example, need to enable `amqp.traceFrames` you can do that
+by appending the option to your URI, like the following example:
+
+    AMQPComponent amqp = AMQPComponent.amqpComponent("amqp://localhost:5672?amqp.traceFrames=true");
+
+For reference, take a look at the [QPID JMS client
+configuration](https://qpid.apache.org/releases/qpid-jms-1.7.0/docs/index.html)
+
+# Using topics
+
+To have using topics working with `camel-amqp` you need to configure the
+component to use `topic://` as topic prefix, as shown below:
+
+     <bean id="amqp" class="org.apache.camel.component.amqp.AmqpComponent">
+       <property name="connectionFactory">
+         <bean class="org.apache.qpid.jms.JmsConnectionFactory" factory-method="createFromURL">
+           <property name="remoteURI" value="amqp://localhost:5672" />
+           <property name="topicPrefix" value="topic://" />  <!-- only necessary when connecting to ActiveMQ over AMQP 1.0 -->
+         </bean>
+       </property>
+     </bean>
+
+Keep in mind that both `AMQPComponent#amqpComponent()` methods and
+`AMQPConnectionDetails` pre-configure the component with the topic
+prefix, so you don’t have to configure it explicitly.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|clientId|Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions with JMS 1.1.||string|
+|connectionFactory|The connection factory to be use. A connection factory must be configured either on the component or endpoint.||object|
+|disableReplyTo|Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different message brokers and you want to route message from one system to another.|false|boolean|
+|durableSubscriptionName|The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.||string|
+|includeAmqpAnnotations|Whether to include AMQP annotations when mapping from AMQP to Camel Message. Setting this to true maps AMQP message annotations that contain a JMS\_AMQP\_MA\_ prefix to message headers. Due to limitations in Apache Qpid JMS API, currently delivery annotations are ignored.|false|boolean|
+|jmsMessageType|Allows you to force the use of a specific jakarta.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it.||object|
+|replyTo|Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer).||string|
+|testConnectionOnStartup|Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well.|false|boolean|
+|acknowledgementModeName|The JMS acknowledgement name, which is one of: SESSION\_TRANSACTED, CLIENT\_ACKNOWLEDGE, AUTO\_ACKNOWLEDGE, DUPS\_OK\_ACKNOWLEDGE|AUTO\_ACKNOWLEDGE|string|
+|artemisConsumerPriority|Consumer priorities allow you to ensure that high priority consumers receive messages while they are active. Normally, active consumers connected to a queue receive messages from it in a round-robin fashion. When consumer priorities are in use, messages are delivered round-robin if multiple active consumers exist with the same high priority. Messages will only going to lower priority consumers when the high priority consumers do not have credit available to consume the message, or those high priority consumers have declined to accept the message (for instance because it does not meet the criteria of any selectors associated with the consumer).||integer|
+|asyncConsumer|Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note if transacted has been enabled, then asyncConsumer=true does not run asynchronously, as transaction must be executed synchronously (Camel 3.0 may support async transactions).|false|boolean|
+|autoStartup|Specifies whether the consumer container should auto-startup.|true|boolean|
+|cacheLevel|Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.||integer|
+|cacheLevelName|Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE\_AUTO, CACHE\_CONNECTION, CACHE\_CONSUMER, CACHE\_NONE, and CACHE\_SESSION. The default setting is CACHE\_AUTO. See the Spring documentation and Transactions Cache Levels for more information.|CACHE\_AUTO|string|
+|concurrentConsumers|Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.|1|integer|
+|maxConcurrentConsumers|Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.||integer|
+|replyToDeliveryPersistent|Specifies whether to use persistent delivery by default for replies.|true|boolean|
+|selector|Sets the JMS selector to use||string|
+|subscriptionDurable|Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well.|false|boolean|
+|subscriptionName|Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS 2.0).||string|
+|subscriptionShared|Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined with subscriptionDurable as well. Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well. Requires a JMS 2.0 compatible message broker.|false|boolean|
+|acceptMessagesWhileStopping|Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option.|false|boolean|
+|allowReplyManagerQuickStop|Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag.|false|boolean|
+|consumerType|The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.|Default|object|
+|defaultTaskExecutorType|Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached thread-pool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of ThreadPool is recommended to reduce thread trash in elastic configurations with dynamically increasing and decreasing concurrent consumers.||object|
+|eagerLoadingOfProperties|Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody.|false|boolean|
+|eagerPoisonBody|If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties.|Poison JMS message due to ${exception.message}|string|
+|exposeListenerSession|Specifies whether the listener session should be exposed when consuming messages.|false|boolean|
+|replyToConsumerType|The consumer type of the reply consumer (when doing request/reply), which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.|Default|object|
+|replyToSameDestinationAllowed|Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself.|false|boolean|
+|taskExecutor|Allows you to specify a custom task executor for consuming messages.||object|
+|deliveryDelay|Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker.|-1|integer|
+|deliveryMode|Specifies the delivery mode to be used. Possible values are those defined by jakarta.jms.DeliveryMode. NON\_PERSISTENT = 1 and PERSISTENT = 2.||integer|
+|deliveryPersistent|Specifies whether persistent delivery is used by default.|true|boolean|
+|explicitQosEnabled|Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers.|false|boolean|
+|formatDateHeadersToIso8601|Sets whether JMS date properties should be formatted according to the ISO 8601 standard.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|preserveMessageQos|Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explicitQosEnabled option, by contrast, will only use options set on the endpoint, and not values from the message header.|false|boolean|
+|priority|Values greater than 1 specify the message priority when sending (where 1 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect.|4|integer|
+|replyToConcurrentConsumers|Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.|1|integer|
+|replyToMaxConcurrentConsumers|Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.||integer|
+|replyToOnTimeoutMaxConcurrentConsumers|Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS.|1|integer|
+|replyToOverride|Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination.||string|
+|replyToType|Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications if running in a clustered environment, and the fact that Shared reply queues has lower performance than its alternatives Temporary and Exclusive.||object|
+|requestTimeout|The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option.|20000|duration|
+|timeToLive|When sending messages, specifies the time-to-live of the message (in milliseconds).|-1|integer|
+|allowAdditionalHeaders|This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example, some message systems, such as WMQ, do this with header names using prefix JMS\_IBM\_MQMD\_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching.||string|
+|allowNullBody|Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.|true|boolean|
+|alwaysCopyMessage|If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set)|false|boolean|
+|correlationProperty|When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel.||string|
+|disableTimeToLive|Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. Then the message will not expire on the receiver system. See below in section About time to live for more details.|false|boolean|
+|forceSendOriginalMessage|When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received.|false|boolean|
+|includeSentJMSMessageID|Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination.|false|boolean|
+|replyToCacheLevelName|Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE\_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE\_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE\_NONE to work. Note: If using temporary queues then CACHE\_NONE is not allowed, and you must use a higher value such as CACHE\_CONSUMER or CACHE\_SESSION.||string|
+|replyToDestinationSelectorName|Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue).||string|
+|streamMessageTypeEnabled|Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessage until no more data.|false|boolean|
+|allowAutoWiredConnectionFactory|Whether to auto-discover ConnectionFactory from the registry, if no connection factory has been configured. If only one instance of ConnectionFactory is found then it will be used. This is enabled by default.|true|boolean|
+|allowAutoWiredDestinationResolver|Whether to auto-discover DestinationResolver from the registry, if no destination resolver has been configured. If only one instance of DestinationResolver is found then it will be used. This is enabled by default.|true|boolean|
+|allowSerializedHeaders|Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level.|false|boolean|
+|artemisStreamingEnabled|Whether optimizing for Apache Artemis streaming mode. This can reduce memory overhead when using Artemis with JMS StreamMessage types. This option must only be enabled if Apache Artemis is being used.|false|boolean|
+|asyncStartListener|Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or fail-over. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used, then beware that if the connection could not be established, then an exception is logged at WARN level, and the consumer will not be able to receive messages; You can then restart the route to retry.|false|boolean|
+|asyncStopListener|Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|configuration|To use a shared JMS configuration||object|
+|destinationResolver|A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry).||object|
+|errorHandler|Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom errorHandler.||object|
+|exceptionListener|Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.||object|
+|idleConsumerLimit|Specify the limit for the number of consumers that are allowed to be idle at any given time.|1|integer|
+|idleTaskExecutionLimit|Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring.|1|integer|
+|includeAllJMSXProperties|Whether to include all JMSX prefixed properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply.|false|boolean|
+|includeCorrelationIDAsBytes|Whether the JMS consumer should include JMSCorrelationIDAsBytes as a header on the Camel Message.|true|boolean|
+|jmsKeyFormatStrategy|Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation.||object|
+|mapJmsMessage|Specifies whether Camel should auto map the received JMS message to a suited payload type, such as jakarta.jms.TextMessage to a String etc.|true|boolean|
+|maxMessagesPerTask|The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required.|-1|integer|
+|messageConverter|To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a jakarta.jms.Message.||object|
+|messageCreatedStrategy|To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of jakarta.jms.Message objects when Camel is sending a JMS message.||object|
+|messageIdEnabled|When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value.|true|boolean|
+|messageListenerContainerFactory|Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom.||object|
+|messageTimestampEnabled|Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value.|true|boolean|
+|pubSubNoLocal|Specifies whether to inhibit the delivery of messages published by its own connection.|false|boolean|
+|queueBrowseStrategy|To use a custom QueueBrowseStrategy when browsing queues||object|
+|receiveTimeout|The timeout for receiving messages (in milliseconds).|1000|duration|
+|recoveryInterval|Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds.|5000|duration|
+|requestTimeoutCheckerInterval|Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout.|1000|duration|
+|serviceLocationEnabled|Whether to detect the network address location of the JMS broker on startup. This information is gathered via reflection on the ConnectionFactory, and is vendor specific. This option can be used to turn this off.|true|boolean|
+|synchronous|Sets whether synchronous processing should be strictly used|false|boolean|
+|temporaryQueueResolver|A pluggable TemporaryQueueResolver that allows you to use your own resolver for creating temporary queues (some messaging systems has special requirements for creating temporary queues).||object|
+|transferException|If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a jakarta.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option takes precedence. The caught exception is required to be serializable. The original Exception on the consumer side can be wrapped in an outer exception such as org.apache.camel.RuntimeCamelException when returned to the producer. Use this with caution as the data is using Java Object serialization and requires the received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer!|false|boolean|
+|transferExchange|You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloads is an Exchange and not a regular payload. Use this with caution as the data is using Java Object serialization and requires the receiver to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumers having to use compatible Camel versions!|false|boolean|
+|useMessageIDAsCorrelationID|Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.|false|boolean|
+|waitForProvisionCorrelationToBeUpdatedCounter|Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled.|50|integer|
+|waitForProvisionCorrelationToBeUpdatedThreadSleepingTime|Interval in millis to sleep each time while waiting for provisional correlation id to be updated.|100|duration|
+|waitForTemporaryReplyToToBeUpdatedCounter|Number of times to wait for temporary replyTo queue to be created and ready when doing request/reply over JMS.|200|integer|
+|waitForTemporaryReplyToToBeUpdatedThreadSleepingTime|Interval in millis to sleep each time while waiting for temporary replyTo queue to be ready.|100|duration|
+|headerFilterStrategy|To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.||object|
+|errorHandlerLoggingLevel|Allows to configure the default errorHandler logging level for logging uncaught exceptions.|WARN|object|
+|errorHandlerLogStackTrace|Allows to control whether stack-traces should be logged or not, by the default errorHandler.|true|boolean|
+|password|Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.||string|
+|username|Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.||string|
+|transacted|Specifies whether to use transacted mode|false|boolean|
+|transactedInOut|Specifies whether InOut operations (request reply) default to using transacted mode If this flag is set to true, then Spring JmsTemplate will have sessionTransacted set to true, and the acknowledgeMode as transacted on the JmsTemplate used for InOut operations. Note from Spring JMS: that within a JTA transaction, the parameters passed to createQueue, createTopic methods are not taken into account. Depending on the Java EE transaction context, the container makes its own decisions on these values. Analogously, these parameters are not taken into account within a locally managed transaction either, since Spring JMS operates on an existing JMS Session in this case. Setting this flag to true will use a short local JMS transaction when running outside of a managed transaction, and a synchronized local JMS transaction in case of a managed transaction (other than an XA transaction) being present. This has the effect of a local JMS transaction being managed alongside the main transaction (which might be a native JDBC transaction), with the JMS transaction committing right after the main transaction.|false|boolean|
+|lazyCreateTransactionManager|If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.|true|boolean|
+|transactionManager|The Spring transaction manager to use.||object|
+|transactionName|The name of the transaction to use.||string|
+|transactionTimeout|The timeout value of the transaction (in seconds), if using transacted mode.|-1|integer|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|destinationType|The kind of destination to use|queue|string|
+|destinationName|Name of the queue or topic to use as destination||string|
+|clientId|Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions with JMS 1.1.||string|
+|connectionFactory|The connection factory to be use. A connection factory must be configured either on the component or endpoint.||object|
+|disableReplyTo|Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different message brokers and you want to route message from one system to another.|false|boolean|
+|durableSubscriptionName|The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.||string|
+|jmsMessageType|Allows you to force the use of a specific jakarta.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it.||object|
+|replyTo|Provides an explicit ReplyTo destination (overrides any incoming value of Message.getJMSReplyTo() in consumer).||string|
+|testConnectionOnStartup|Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well.|false|boolean|
+|acknowledgementModeName|The JMS acknowledgement name, which is one of: SESSION\_TRANSACTED, CLIENT\_ACKNOWLEDGE, AUTO\_ACKNOWLEDGE, DUPS\_OK\_ACKNOWLEDGE|AUTO\_ACKNOWLEDGE|string|
+|artemisConsumerPriority|Consumer priorities allow you to ensure that high priority consumers receive messages while they are active. Normally, active consumers connected to a queue receive messages from it in a round-robin fashion. When consumer priorities are in use, messages are delivered round-robin if multiple active consumers exist with the same high priority. Messages will only going to lower priority consumers when the high priority consumers do not have credit available to consume the message, or those high priority consumers have declined to accept the message (for instance because it does not meet the criteria of any selectors associated with the consumer).||integer|
+|asyncConsumer|Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note if transacted has been enabled, then asyncConsumer=true does not run asynchronously, as transaction must be executed synchronously (Camel 3.0 may support async transactions).|false|boolean|
+|autoStartup|Specifies whether the consumer container should auto-startup.|true|boolean|
+|cacheLevel|Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.||integer|
+|cacheLevelName|Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE\_AUTO, CACHE\_CONNECTION, CACHE\_CONSUMER, CACHE\_NONE, and CACHE\_SESSION. The default setting is CACHE\_AUTO. See the Spring documentation and Transactions Cache Levels for more information.|CACHE\_AUTO|string|
+|concurrentConsumers|Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.|1|integer|
+|maxConcurrentConsumers|Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.||integer|
+|replyToDeliveryPersistent|Specifies whether to use persistent delivery by default for replies.|true|boolean|
+|selector|Sets the JMS selector to use||string|
+|subscriptionDurable|Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well.|false|boolean|
+|subscriptionName|Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS 2.0).||string|
+|subscriptionShared|Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined with subscriptionDurable as well. Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well. Requires a JMS 2.0 compatible message broker.|false|boolean|
+|acceptMessagesWhileStopping|Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option.|false|boolean|
+|allowReplyManagerQuickStop|Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag.|false|boolean|
+|consumerType|The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.|Default|object|
+|defaultTaskExecutorType|Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached thread-pool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of ThreadPool is recommended to reduce thread trash in elastic configurations with dynamically increasing and decreasing concurrent consumers.||object|
+|eagerLoadingOfProperties|Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody.|false|boolean|
+|eagerPoisonBody|If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties.|Poison JMS message due to ${exception.message}|string|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|exposeListenerSession|Specifies whether the listener session should be exposed when consuming messages.|false|boolean|
+|replyToConsumerType|The consumer type of the reply consumer (when doing request/reply), which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.|Default|object|
+|replyToSameDestinationAllowed|Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself.|false|boolean|
+|taskExecutor|Allows you to specify a custom task executor for consuming messages.||object|
+|deliveryDelay|Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker.|-1|integer|
+|deliveryMode|Specifies the delivery mode to be used. Possible values are those defined by jakarta.jms.DeliveryMode. NON\_PERSISTENT = 1 and PERSISTENT = 2.||integer|
+|deliveryPersistent|Specifies whether persistent delivery is used by default.|true|boolean|
+|explicitQosEnabled|Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers.|false|boolean|
+|formatDateHeadersToIso8601|Sets whether JMS date properties should be formatted according to the ISO 8601 standard.|false|boolean|
+|preserveMessageQos|Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explicitQosEnabled option, by contrast, will only use options set on the endpoint, and not values from the message header.|false|boolean|
+|priority|Values greater than 1 specify the message priority when sending (where 1 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect.|4|integer|
+|replyToConcurrentConsumers|Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.|1|integer|
+|replyToMaxConcurrentConsumers|Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.||integer|
+|replyToOnTimeoutMaxConcurrentConsumers|Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS.|1|integer|
+|replyToOverride|Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination.||string|
+|replyToType|Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications if running in a clustered environment, and the fact that Shared reply queues has lower performance than its alternatives Temporary and Exclusive.||object|
+|requestTimeout|The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option.|20000|duration|
+|timeToLive|When sending messages, specifies the time-to-live of the message (in milliseconds).|-1|integer|
+|allowAdditionalHeaders|This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example, some message systems, such as WMQ, do this with header names using prefix JMS\_IBM\_MQMD\_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching.||string|
+|allowNullBody|Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.|true|boolean|
+|alwaysCopyMessage|If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set)|false|boolean|
+|correlationProperty|When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel.||string|
+|disableTimeToLive|Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. Then the message will not expire on the receiver system. See below in section About time to live for more details.|false|boolean|
+|forceSendOriginalMessage|When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received.|false|boolean|
+|includeSentJMSMessageID|Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|replyToCacheLevelName|Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE\_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE\_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE\_NONE to work. Note: If using temporary queues then CACHE\_NONE is not allowed, and you must use a higher value such as CACHE\_CONSUMER or CACHE\_SESSION.||string|
+|replyToDestinationSelectorName|Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue).||string|
+|streamMessageTypeEnabled|Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessage until no more data.|false|boolean|
+|allowSerializedHeaders|Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level.|false|boolean|
+|artemisStreamingEnabled|Whether optimizing for Apache Artemis streaming mode. This can reduce memory overhead when using Artemis with JMS StreamMessage types. This option must only be enabled if Apache Artemis is being used.|false|boolean|
+|asyncStartListener|Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or fail-over. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used, then beware that if the connection could not be established, then an exception is logged at WARN level, and the consumer will not be able to receive messages; You can then restart the route to retry.|false|boolean|
+|asyncStopListener|Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.|false|boolean|
+|destinationResolver|A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry).||object|
+|errorHandler|Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom errorHandler.||object|
+|exceptionListener|Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.||object|
+|headerFilterStrategy|To use a custom HeaderFilterStrategy to filter header to and from Camel message.||object|
+|idleConsumerLimit|Specify the limit for the number of consumers that are allowed to be idle at any given time.|1|integer|
+|idleTaskExecutionLimit|Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring.|1|integer|
+|includeAllJMSXProperties|Whether to include all JMSX prefixed properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply.|false|boolean|
+|jmsKeyFormatStrategy|Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation.||object|
+|mapJmsMessage|Specifies whether Camel should auto map the received JMS message to a suited payload type, such as jakarta.jms.TextMessage to a String etc.|true|boolean|
+|maxMessagesPerTask|The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required.|-1|integer|
+|messageConverter|To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a jakarta.jms.Message.||object|
+|messageCreatedStrategy|To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of jakarta.jms.Message objects when Camel is sending a JMS message.||object|
+|messageIdEnabled|When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value.|true|boolean|
+|messageListenerContainerFactory|Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom.||object|
+|messageTimestampEnabled|Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value.|true|boolean|
+|pubSubNoLocal|Specifies whether to inhibit the delivery of messages published by its own connection.|false|boolean|
+|receiveTimeout|The timeout for receiving messages (in milliseconds).|1000|duration|
+|recoveryInterval|Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds.|5000|duration|
+|requestTimeoutCheckerInterval|Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout.|1000|duration|
+|synchronous|Sets whether synchronous processing should be strictly used|false|boolean|
+|temporaryQueueResolver|A pluggable TemporaryQueueResolver that allows you to use your own resolver for creating temporary queues (some messaging systems has special requirements for creating temporary queues).||object|
+|transferException|If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a jakarta.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option takes precedence. The caught exception is required to be serializable. The original Exception on the consumer side can be wrapped in an outer exception such as org.apache.camel.RuntimeCamelException when returned to the producer. Use this with caution as the data is using Java Object serialization and requires the received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer!|false|boolean|
+|transferExchange|You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloads is an Exchange and not a regular payload. Use this with caution as the data is using Java Object serialization and requires the receiver to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumers having to use compatible Camel versions!|false|boolean|
+|useMessageIDAsCorrelationID|Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.|false|boolean|
+|waitForProvisionCorrelationToBeUpdatedCounter|Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled.|50|integer|
+|waitForProvisionCorrelationToBeUpdatedThreadSleepingTime|Interval in millis to sleep each time while waiting for provisional correlation id to be updated.|100|duration|
+|waitForTemporaryReplyToToBeUpdatedCounter|Number of times to wait for temporary replyTo queue to be created and ready when doing request/reply over JMS.|200|integer|
+|waitForTemporaryReplyToToBeUpdatedThreadSleepingTime|Interval in millis to sleep each time while waiting for temporary replyTo queue to be ready.|100|duration|
+|errorHandlerLoggingLevel|Allows to configure the default errorHandler logging level for logging uncaught exceptions.|WARN|object|
+|errorHandlerLogStackTrace|Allows to control whether stack-traces should be logged or not, by the default errorHandler.|true|boolean|
+|password|Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.||string|
+|username|Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.||string|
+|transacted|Specifies whether to use transacted mode|false|boolean|
+|transactedInOut|Specifies whether InOut operations (request reply) default to using transacted mode If this flag is set to true, then Spring JmsTemplate will have sessionTransacted set to true, and the acknowledgeMode as transacted on the JmsTemplate used for InOut operations. Note from Spring JMS: that within a JTA transaction, the parameters passed to createQueue, createTopic methods are not taken into account. Depending on the Java EE transaction context, the container makes its own decisions on these values. Analogously, these parameters are not taken into account within a locally managed transaction either, since Spring JMS operates on an existing JMS Session in this case. Setting this flag to true will use a short local JMS transaction when running outside of a managed transaction, and a synchronized local JMS transaction in case of a managed transaction (other than an XA transaction) being present. This has the effect of a local JMS transaction being managed alongside the main transaction (which might be a native JDBC transaction), with the JMS transaction committing right after the main transaction.|false|boolean|
+|lazyCreateTransactionManager|If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true.|true|boolean|
+|transactionManager|The Spring transaction manager to use.||object|
+|transactionName|The name of the transaction to use.||string|
+|transactionTimeout|The timeout value of the transaction (in seconds), if using transacted mode.|-1|integer|

camel-arangodb.md

@@ -0,0 +1,93 @@
+# Arangodb
+
+**Since Camel 3.5**
+
+**Only producer is supported**
+
+The ArangoDb component is client for ArangoDb that uses the [arango java
+driver](https://github.com/arangodb/arangodb-java-driver) to perform
+queries on collections and graphs in the ArangoDb database.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-arangodb</artifactId>
+        <version>x.x.x</version>
+      <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# URI format
+
+    arangodb:database[?options]
+
+# Examples
+
+## Producer Examples
+
+### Save document on a collection
+
+    from("direct:insert")
+      .to("arangodb:testDb?documentCollection=collection&operation=SAVE_DOCUMENT");
+
+And you can set as body a BaseDocument class
+
+    BaseDocument myObject = new BaseDocument();
+    myObject.addAttribute("a", "Foo");
+    myObject.addAttribute("b", 42);
+
+### Query a collection
+
+    from("direct:query")
+      .to("arangodb:testDb?operation=AQL_QUERY
+
+And you can invoke an AQL Query in this way
+
+    String query = "FOR t IN " + COLLECTION_NAME + " FILTER t.value == @value";
+    Map<String, Object> bindVars = new MapBuilder().put("value", "hello")
+            .get();
+    
+    Exchange result = template.request("direct:query", exchange -> {
+        exchange.getMessage().setHeader(AQL_QUERY, query);
+        exchange.getMessage().setHeader(AQL_QUERY_BIND_PARAMETERS, bindVars);
+    });
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|documentCollection|Collection name, when using ArangoDb as a Document Database. Set the documentCollection name when using the CRUD operation on the document database collections (SAVE\_DOCUMENT , FIND\_DOCUMENT\_BY\_KEY, UPDATE\_DOCUMENT, DELETE\_DOCUMENT).||string|
+|edgeCollection|Collection name of vertices, when using ArangoDb as a Graph Database. Set the edgeCollection name to perform CRUD operation on edges using these operations : SAVE\_VERTEX, FIND\_VERTEX\_BY\_KEY, UPDATE\_VERTEX, DELETE\_VERTEX. The graph attribute is mandatory.||string|
+|graph|Graph name, when using ArangoDb as a Graph Database. Combine this attribute with one of the two attributes vertexCollection and edgeCollection.||string|
+|host|ArangoDB host. If host and port are default, this field is Optional.||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|Operations to perform on ArangoDb. For the operation AQL\_QUERY, no need to specify a collection or graph.||object|
+|port|ArangoDB exposed port. If host and port are default, this field is Optional.||integer|
+|vertexCollection|Collection name of vertices, when using ArangoDb as a Graph Database. Set the vertexCollection name to perform CRUD operation on vertices using these operations : SAVE\_EDGE, FIND\_EDGE\_BY\_KEY, UPDATE\_EDGE, DELETE\_EDGE. The graph attribute is mandatory.||string|
+|arangoDB|To use an existing ArangDB client.||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|vertx|To use an existing Vertx in the ArangoDB client.||object|
+|password|ArangoDB password. If user and password are default, this field is Optional.||string|
+|user|ArangoDB user. If user and password are default, this field is Optional.||string|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|database|database name||string|
+|documentCollection|Collection name, when using ArangoDb as a Document Database. Set the documentCollection name when using the CRUD operation on the document database collections (SAVE\_DOCUMENT , FIND\_DOCUMENT\_BY\_KEY, UPDATE\_DOCUMENT, DELETE\_DOCUMENT).||string|
+|edgeCollection|Collection name of vertices, when using ArangoDb as a Graph Database. Set the edgeCollection name to perform CRUD operation on edges using these operations : SAVE\_VERTEX, FIND\_VERTEX\_BY\_KEY, UPDATE\_VERTEX, DELETE\_VERTEX. The graph attribute is mandatory.||string|
+|graph|Graph name, when using ArangoDb as a Graph Database. Combine this attribute with one of the two attributes vertexCollection and edgeCollection.||string|
+|host|ArangoDB host. If host and port are default, this field is Optional.||string|
+|operation|Operations to perform on ArangoDb. For the operation AQL\_QUERY, no need to specify a collection or graph.||object|
+|port|ArangoDB exposed port. If host and port are default, this field is Optional.||integer|
+|vertexCollection|Collection name of vertices, when using ArangoDb as a Graph Database. Set the vertexCollection name to perform CRUD operation on vertices using these operations : SAVE\_EDGE, FIND\_EDGE\_BY\_KEY, UPDATE\_EDGE, DELETE\_EDGE. The graph attribute is mandatory.||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|arangoDB|To use an existing ArangDB client.||object|
+|vertx|To use an existing Vertx instance in the ArangoDB client.||object|
+|password|ArangoDB password. If user and password are default, this field is Optional.||string|
+|user|ArangoDB user. If user and password are default, this field is Optional.||string|

camel-as2.md

@@ -0,0 +1,89 @@
+# As2
+
+**Since Camel 2.22**
+
+**Both producer and consumer are supported**
+
+The AS2 component provides transport of EDI messages using the HTTP
+transfer protocol as specified in
+[RFC4130](https://tools.ietf.org/html/rfc4130).
+
+Maven users will need to add the following dependency to their pom.xml
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-as2</artifactId>
+        <version>x.x.x</version>
+        <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# URI format
+
+**Sample URL**
+
+    as2://apiName/methodName
+
+apiName can be one of:
+
+-   client
+
+-   server
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|configuration|Component configuration||object|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|apiName|What kind of operation to perform||object|
+|methodName|What sub operation to use for the selected operation||string|
+|as2From|The value of the AS2From header of AS2 message.||string|
+|as2MessageStructure|The structure of AS2 Message. One of: PLAIN - No encryption, no signature, SIGNED - No encryption, signature, ENCRYPTED - Encryption, no signature, ENCRYPTED\_SIGNED - Encryption, signature||object|
+|as2To|The value of the AS2To header of AS2 message.||string|
+|as2Version|The version of the AS2 protocol.|1.1|string|
+|asyncMdnPortNumber|The port number of asynchronous MDN server.||integer|
+|attachedFileName|The name of the attached file||string|
+|clientFqdn|The Client Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint.|camel.apache.org|string|
+|compressionAlgorithm|The algorithm used to compress EDI message.||object|
+|dispositionNotificationTo|The value of the Disposition-Notification-To header. Assigning a value to this parameter requests a message disposition notification (MDN) for the AS2 message.||string|
+|ediMessageTransferEncoding|The transfer encoding of EDI message.||string|
+|ediMessageType|The content type of EDI message. One of application/edifact, application/edi-x12, application/edi-consent, application/xml||object|
+|from|The value of the From header of AS2 message.||string|
+|hostnameVerifier|Set hostname verifier for SSL session.||object|
+|httpConnectionPoolSize|The maximum size of the connection pool for http connections (client only)|5|integer|
+|httpConnectionPoolTtl|The time to live for connections in the connection pool (client only)|15m|object|
+|httpConnectionTimeout|The timeout of the http connection (client only)|5s|object|
+|httpSocketTimeout|The timeout of the underlying http socket (client only)|5s|object|
+|inBody|Sets the name of a parameter to be passed in the exchange In Body||string|
+|mdnMessageTemplate|The template used to format MDN message||string|
+|receiptDeliveryOption|The return URL that the message receiver should send an asynchronous MDN to. If not present the receipt is synchronous. (Client only)||string|
+|requestUri|The request URI of EDI message.|/|string|
+|server|The value included in the Server message header identifying the AS2 Server.|Camel AS2 Server Endpoint|string|
+|serverFqdn|The Server Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint.|camel.apache.org|string|
+|serverPortNumber|The port number of server.||integer|
+|sslContext|Set SSL context for connection to remote server.||object|
+|subject|The value of Subject header of AS2 message.||string|
+|targetHostname|The host name (IP or DNS name) of target host.||string|
+|targetPortNumber|The port number of target host. -1 indicates the scheme default port.|80|integer|
+|userAgent|The value included in the User-Agent message header identifying the AS2 user agent.|Camel AS2 Client Endpoint|string|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|decryptingPrivateKey|The key used to encrypt the EDI message.||object|
+|encryptingAlgorithm|The algorithm used to encrypt EDI message.||object|
+|encryptingCertificateChain|The chain of certificates used to encrypt EDI message.||object|
+|signedReceiptMicAlgorithms|The list of algorithms, in order of preference, requested to generate a message integrity check (MIC) returned in message dispostion notification (MDN)||array|
+|signingAlgorithm|The algorithm used to sign EDI message.||object|
+|signingCertificateChain|The chain of certificates used to sign EDI message.||object|
+|signingPrivateKey|The key used to sign the EDI message.||object|
+|validateSigningCertificateChain|Certificates to validate the message's signature against. If not supplied, validation will not take place. Server: validates the received message. Client: not yet implemented, should validate the MDN||object|

camel-asterisk.md

@@ -0,0 +1,72 @@
+# Asterisk
+
+**Since Camel 2.18**
+
+**Both producer and consumer are supported**
+
+The Asterisk component allows you to work easily with an Asterisk PBX
+Server [http://www.asterisk.org/](http://www.asterisk.org/) using
+[asterisk-java](https://asterisk-java.org/)
+
+This component helps to interface with [Asterisk Manager
+Interface](http://www.voip-info.org/wiki-Asterisk+manager+API)
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-asterisk</artifactId>
+        <version>x.x.x</version>
+        <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# URI format
+
+    asterisk:name[?options]
+
+# Action
+
+Supported actions are:
+
+-   QUEUE\_STATUS: Queue status
+
+-   SIP\_PEERS: List SIP peers
+
+-   EXTENSION\_STATE: Check extension status
+
+# Examples
+
+## Producer Example
+
+    from("direct:in")
+      .to("asterisk://myVoIP?hostname=hostname&username=username&password=password&action=EXTENSION_STATE")
+
+## Consumer Example
+
+    from("asterisk:myVoIP?hostname=hostname&username=username&password=password")
+      .log("Received a message - ${body}");
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|name|Name of component||string|
+|hostname|The hostname of the asterisk server||string|
+|password|Login password||string|
+|username|Login username||string|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|action|What action to perform such as getting queue status, sip peers or extension state.||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|

camel-atmosphere-websocket.md

@@ -0,0 +1,119 @@
+# Atmosphere-websocket
+
+**Since Camel 2.14**
+
+**Both producer and consumer are supported**
+
+The Atmosphere-Websocket component provides Websocket based endpoints
+for a servlet communicating with external clients over Websocket (as a
+servlet accepting websocket connections from external clients). This
+component uses the
+[Atmosphere](https://github.com/Atmosphere/atmosphere) library to
+support the Websocket transport in various Servlet containers.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-atmosphere-websocket</artifactId>
+        <version>x.x.x</version>
+        <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# Reading and Writing Data over Websocket
+
+An atmopshere-websocket endpoint can either write data to the socket or
+read from the socket, depending on whether the endpoint is configured as
+the producer or the consumer, respectively.
+
+# Examples
+
+## Consumer Example
+
+In the route below, Camel will read from the specified websocket
+connection.
+
+    from("atmosphere-websocket:///servicepath")
+            .to("direct:next");
+
+And the equivalent Spring sample:
+
+    <camelContext xmlns="http://camel.apache.org/schema/spring">
+      <route>
+        <from uri="atmosphere-websocket:///servicepath"/>
+        <to uri="direct:next"/>
+      </route>
+    </camelContext>
+
+## Producer Example
+
+In the route below, Camel will write to the specified websocket
+connection.
+
+    from("direct:next")
+            .to("atmosphere-websocket:///servicepath");
+
+And the equivalent Spring sample:
+
+    <camelContext xmlns="http://camel.apache.org/schema/spring">
+      <route>
+        <from uri="direct:next"/>
+        <to uri="atmosphere-websocket:///servicepath"/>
+      </route>
+    </camelContext>
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|muteException|If enabled and an Exchange failed processing on the consumer side the response's body won't contain the exception's stack trace.|true|boolean|
+|servletName|Default name of servlet to use. The default name is CamelServlet.|CamelServlet|string|
+|attachmentMultipartBinding|Whether to automatic bind multipart/form-data as attachments on the Camel Exchange. The options attachmentMultipartBinding=true and disableStreamCache=false cannot work together. Remove disableStreamCache to use AttachmentMultipartBinding. This is turn off by default as this may require servlet specific configuration to enable this when using Servlet's.|false|boolean|
+|fileNameExtWhitelist|Whitelist of accepted filename extensions for accepting uploaded files. Multiple extensions can be separated by comma, such as txt,xml.||string|
+|httpRegistry|To use a custom org.apache.camel.component.servlet.HttpRegistry.||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|allowJavaSerializedObject|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|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|httpBinding|To use a custom HttpBinding to control the mapping between Camel message and HttpClient.||object|
+|httpConfiguration|To use the shared HttpConfiguration as base configuration.||object|
+|headerFilterStrategy|To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.||object|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|servicePath|Name of websocket endpoint||string|
+|chunked|If this option is false the Servlet will disable the HTTP streaming and set the content-length header on the response|true|boolean|
+|disableStreamCache|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 persistent store. DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support reading the stream multiple times. If you use Servlet to bridge/proxy an endpoint then consider enabling this option to improve performance, in case you do not need to read the message payload multiple times. The http producer will by default cache the response body stream. If setting this option to true, then the producers will not cache the response body stream but use the response stream as-is as the message body.|false|boolean|
+|sendToAll|Whether to send to all (broadcast) or send to a single receiver.|false|boolean|
+|transferException|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 incoming data from the request to Java and that can be a potential security risk.|false|boolean|
+|useStreaming|To enable streaming to send data as multiple text fragments.|false|boolean|
+|headerFilterStrategy|To use a custom HeaderFilterStrategy to filter header to and from Camel message.||object|
+|httpBinding|To use a custom HttpBinding to control the mapping between Camel message and HttpClient.||object|
+|async|Configure the consumer to work in async mode|false|boolean|
+|httpMethodRestrict|Used to only allow consuming if the HttpMethod matches, such as GET/POST/PUT etc. Multiple methods can be specified separated by comma.||string|
+|logException|If enabled and an Exchange failed processing on the consumer side the exception's stack trace will be logged when the exception stack trace is not sent in the response's body.|false|boolean|
+|matchOnUriPrefix|Whether or not the consumer should try to find a target consumer by matching the URI prefix if no exact match is found.|false|boolean|
+|muteException|If enabled and an Exchange failed processing on the consumer side the response's body won't contain the exception's stack trace.|false|boolean|
+|responseBufferSize|To use a custom buffer size on the jakarta.servlet.ServletResponse.||integer|
+|servletName|Name of the servlet to use|CamelServlet|string|
+|attachmentMultipartBinding|Whether to automatic bind multipart/form-data as attachments on the Camel Exchange. The options attachmentMultipartBinding=true and disableStreamCache=false cannot work together. Remove disableStreamCache to use AttachmentMultipartBinding. This is turn off by default as this may require servlet specific configuration to enable this when using Servlet's.|false|boolean|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|eagerCheckContentAvailable|Whether to eager check whether the HTTP requests has content if the content-length header is 0 or not present. This can be turned on in case HTTP clients do not send streamed data.|false|boolean|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|fileNameExtWhitelist|Whitelist of accepted filename extensions for accepting uploaded files. Multiple extensions can be separated by comma, such as txt,xml.||string|
+|mapHttpMessageBody|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|
+|mapHttpMessageFormUrlEncodedBody|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|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|
+|optionsEnabled|Specifies whether to enable HTTP OPTIONS for this Servlet consumer. By default OPTIONS is turned off.|false|boolean|
+|traceEnabled|Specifies whether to enable HTTP TRACE for this Servlet consumer. By default TRACE is turned off.|false|boolean|
+|bridgeEndpoint|If the option is true, HttpProducer will ignore the Exchange.HTTP\_URI header, and use the endpoint's URI for request. You may also set the option throwExceptionOnFailure to be false to let the HttpProducer send all the fault response back.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|oauth2ClientId|OAuth2 client id||string|
+|oauth2ClientSecret|OAuth2 client secret||string|
+|oauth2TokenEndpoint|OAuth2 Token endpoint||string|

camel-atom.md

@@ -0,0 +1,116 @@
+# Atom
+
+**Since Camel 1.2**
+
+**Only consumer is supported**
+
+The Atom component is used for polling Atom feeds.
+
+Camel will poll the feed every 60 seconds by default.  
+**Note:** The component currently only supports polling (consuming)
+feeds.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-atom</artifactId>
+        <version>x.x.x</version>
+        <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# URI format
+
+    atom://atomUri[?options]
+
+Where **atomUri** is the URI to the Atom feed to poll.
+
+# Exchange data format
+
+Camel will set the In body on the returned `Exchange` with the entries.
+Depending on the `splitEntries` flag Camel will either return one
+`Entry` or a `List<Entry>`.
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 10%" />
+<col style="width: 79%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Option</th>
+<th style="text-align: left;">Value</th>
+<th style="text-align: left;">Behavior</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>splitEntries</code></p></td>
+<td style="text-align: left;"><p><code>true</code></p></td>
+<td style="text-align: left;"><p>Only a single entry from the currently
+being processed feed is set:
+<code>exchange.in.body(Entry)</code></p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>splitEntries</code></p></td>
+<td style="text-align: left;"><p><code>false</code></p></td>
+<td style="text-align: left;"><p>The entire list of entries from the
+feed is set: <code>exchange.in.body(List&lt;Entry&gt;)</code></p></td>
+</tr>
+</tbody>
+</table>
+
+Camel can set the `Feed` object on the In header (see `feedHeader`
+option to disable this):
+
+# Examples
+
+## Consumer Example
+
+In this sample, we poll James Strachan’s blog.
+
+    from("atom://http://macstrac.blogspot.com/feeds/posts/default").to("seda:feeds");
+
+In this sample, we want to filter only good blogs we like to a SEDA
+queue. The sample also shows how to set up Camel standalone, not running
+in any Container or using Spring.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|feedUri|The URI to the feed to poll.||string|
+|sendEmptyMessageWhenIdle|If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.|false|boolean|
+|sortEntries|Sets whether to sort entries by published date. Only works when splitEntries = true.|false|boolean|
+|splitEntries|Sets whether or not entries should be sent individually or whether the entire feed should be sent as a single message|true|boolean|
+|throttleEntries|Sets whether all entries identified in a single feed poll should be delivered immediately. If true, only one entry is processed per delay. Only applicable when splitEntries = true.|true|boolean|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|pollStrategy|A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.||object|
+|feedHeader|Sets whether to add the feed object as a header.|true|boolean|
+|backoffErrorThreshold|The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.||integer|
+|backoffIdleThreshold|The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.||integer|
+|backoffMultiplier|To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.||integer|
+|delay|Milliseconds before the next poll.|500|integer|
+|greedy|If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.|false|boolean|
+|initialDelay|Milliseconds before the first poll starts.|1000|integer|
+|repeatCount|Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.|0|integer|
+|runLoggingLevel|The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.|TRACE|object|
+|scheduledExecutorService|Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.||object|
+|scheduler|To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler|none|object|
+|schedulerProperties|To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.||object|
+|startScheduler|Whether the scheduler should be auto started.|true|boolean|
+|timeUnit|Time unit for initialDelay and delay options.|MILLISECONDS|object|
+|useFixedDelay|Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.|true|boolean|

camel-avro.md

@@ -0,0 +1,212 @@
+# Avro
+
+**Since Camel 2.10**
+
+**Both producer and consumer are supported**
+
+This component provides support for Apache Avro’s rpc, by providing
+producers and consumers endpoint for using avro over netty or http.
+Before Camel 3.2 this functionality was a part of camel-avro component.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-avro-rpc</artifactId>
+        <version>x.x.x</version>
+        <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# Apache Avro Overview
+
+Avro allows you to define message types and a protocol using a json like
+format and then generate java code for the specified types and messages.
+An example of how a schema looks like is below.
+
+    {"namespace": "org.apache.camel.avro.generated",
+     "protocol": "KeyValueProtocol",
+    
+     "types": [
+         {"name": "Key", "type": "record",
+          "fields": [
+              {"name": "key",   "type": "string"}
+          ]
+         },
+         {"name": "Value", "type": "record",
+          "fields": [
+              {"name": "value",   "type": "string"}
+          ]
+         }
+     ],
+    
+     "messages": {
+         "put": {
+             "request": [{"name": "key", "type": "Key"}, {"name": "value", "type": "Value"} ],
+             "response": "null"
+         },
+         "get": {
+             "request": [{"name": "key", "type": "Key"}],
+             "response": "Value"
+         }
+     }
+    }
+
+You can easily generate classes from a schema, using maven, ant etc.
+More details can be found at the [Apache Avro
+documentation](http://avro.apache.org/docs/current/).
+
+However, it doesn’t enforce a schema-first approach, and you can create
+schema for your existing classes. You can use existing protocol
+interfaces to make RCP calls. You should use interface for the protocol
+itself and POJO beans or primitive/String classes for parameter and
+result types. Here is an example of the class that corresponds to the
+schema above:
+
+    package org.apache.camel.avro.reflection;
+    
+    public interface KeyValueProtocol {
+        void put(String key, Value value);
+        Value get(String key);
+    }
+    
+    class Value {
+        private String value;
+        public String getValue() { return value; }
+        public void setValue(String value) { this.value = value; }
+    }
+
+*Note: Existing classes can be used only for RPC (see below), not in
+data format.*
+
+# Using Avro RPC in Camel
+
+As mentioned above, Avro also provides RPC support over multiple
+transports such as http and netty. Camel provides consumers and
+producers for these two transports.
+
+    avro:[transport]:[host]:[port][?options]
+
+The supported transport values are currently http or netty.
+
+You can specify the message name right in the URI:
+
+    avro:[transport]:[host]:[port][/messageName][?options]
+
+For consumers, this allows you to have multiple routes attached to the
+same socket. Dispatching to the correct route will be done by the avro
+component automatically. Route with no messageName specified (if any)
+will be used as default.
+
+When using camel producers for avro ipc, the "in" message body needs to
+contain the parameters of the operation specified in the avro protocol.
+The response will be added in the body of the "out" message.
+
+In a similar manner when using camel avro consumers for avro ipc, the
+request parameters will be placed inside the "in" message body of the
+created exchange. Once the exchange is processed, the body of the "out"
+message will be sent as a response.
+
+**Note:** By default, consumer parameters are wrapped into an array. If
+you’ve got only one parameter, **since 2.12** you can use
+`singleParameter` URI option to receive it directly in the "in" message
+body without array wrapping.
+
+# Examples
+
+An example of using camel avro producers via http:
+
+            <route>
+                <from uri="direct:start"/>
+                <to uri="avro:http:localhost:{{avroport}}?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol"/>
+                <to uri="log:avro"/>
+            </route>
+
+In the example above you need to fill `CamelAvroMessageName` header.
+
+You can use the following syntax to call constant messages:
+
+            <route>
+                <from uri="direct:start"/>
+                <to uri="avro:http:localhost:{{avroport}}/put?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol"/>
+                <to uri="log:avro"/>
+            </route>
+
+An example of consuming messages using camel avro consumers via netty:
+
+            <route>
+                <from uri="avro:netty:localhost:{{avroport}}?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol"/>
+                <choice>
+                    <when>
+                        <el>${in.headers.CamelAvroMessageName == 'put'}</el>
+                        <process ref="putProcessor"/>
+                    </when>
+                    <when>
+                        <el>${in.headers.CamelAvroMessageName == 'get'}</el>
+                        <process ref="getProcessor"/>
+                    </when>
+                </choice>
+            </route>
+
+You can set up two distinct routes to perform the same task:
+
+            <route>
+                <from uri="avro:netty:localhost:{{avroport}}/put?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol">
+                <process ref="putProcessor"/>
+            </route>
+            <route>
+                <from uri="avro:netty:localhost:{{avroport}}/get?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol&singleParameter=true"/>
+                <process ref="getProcessor"/>
+            </route>
+
+In the example above, get takes only one parameter, so `singleParameter`
+is used and `getProcessor` will receive Value class directly in body,
+while `putProcessor` will receive an array of size 2 with `String` key
+and `Value` value filled as array contents.
+
+# Avro via HTTP SPI
+
+The Avro RPC component offers the
+`org.apache.camel.component.avro.spi.AvroRpcHttpServerFactory` service
+provider interface (SPI) so that various platforms can provide their own
+implementation based on their native HTTP server.
+
+The default implementation available in
+`org.apache.camel:camel-avro-jetty` is based on
+`org.apache.avro:avro-ipc-jetty`.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|protocol|Avro protocol to use||object|
+|protocolClassName|Avro protocol to use defined by the FQN class name||string|
+|protocolLocation|Avro protocol location||string|
+|reflectionProtocol|If the protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto-detected|false|boolean|
+|singleParameter|If true, consumer parameter won't be wrapped into an array. Will fail if protocol specifies more than one parameter for the message|false|boolean|
+|uriAuthority|Authority to use (username and password)||string|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|configuration|To use a shared AvroConfiguration to configure options once||object|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|transport|Transport to use, can be either http or netty||object|
+|port|Port number to use||integer|
+|host|Hostname to use||string|
+|messageName|The name of the message to send.||string|
+|protocol|Avro protocol to use||object|
+|protocolClassName|Avro protocol to use defined by the FQN class name||string|
+|protocolLocation|Avro protocol location||string|
+|reflectionProtocol|If the protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto-detected|false|boolean|
+|singleParameter|If true, consumer parameter won't be wrapped into an array. Will fail if protocol specifies more than one parameter for the message|false|boolean|
+|uriAuthority|Authority to use (username and password)||string|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|

camel-aws-bedrock-agent-runtime.md

@@ -0,0 +1,136 @@
+# Aws-bedrock-agent-runtime
+
+**Since Camel 4.5**
+
+**Only producer is supported**
+
+The AWS2 Bedrock component supports invoking a supported LLM model from
+[AWS Bedrock](https://aws.amazon.com/bedrock/) service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Bedrock. More information is available at
+[Amazon Bedrock](https://aws.amazon.com/bedrock/).
+
+# URI Format
+
+    aws-bedrock-agent-runtime://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required Bedrock component options
+
+You have to provide the bedrockRuntimeClient in the Registry or your
+accessKey and secretKey to access the [Amazon
+Bedrock](https://aws.amazon.com/bedrock/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws-bedrock</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|knowledgeBaseId|Define the Knowledge Base Id we are going to use||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|modelId|Define the model Id we are going to use||string|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name|false|string|
+|region|The region in which Bedrock Agent Runtime client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the Bedrock Agent Runtime client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Bedrock Agent Runtime client should expect to load credentials through a profile credentials provider.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|bedrockAgentRuntimeClient|To use an existing configured AWS Bedrock Agent Runtime client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Bedrock Agent Runtime client||string|
+|proxyPort|To define a proxy port when instantiating the Bedrock Agent Runtime client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Bedrock Agent Runtime client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useSessionCredentials|Set whether the Bedrock Agent Runtime client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Bedrock.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|knowledgeBaseId|Define the Knowledge Base Id we are going to use||string|
+|modelId|Define the model Id we are going to use||string|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name|false|string|
+|region|The region in which Bedrock Agent Runtime client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the Bedrock Agent Runtime client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Bedrock Agent Runtime client should expect to load credentials through a profile credentials provider.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|bedrockAgentRuntimeClient|To use an existing configured AWS Bedrock Agent Runtime client||object|
+|proxyHost|To define a proxy host when instantiating the Bedrock Agent Runtime client||string|
+|proxyPort|To define a proxy port when instantiating the Bedrock Agent Runtime client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Bedrock Agent Runtime client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useSessionCredentials|Set whether the Bedrock Agent Runtime client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Bedrock.|false|boolean|

camel-aws-bedrock-agent.md

@@ -0,0 +1,160 @@
+# Aws-bedrock-agent
+
+**Since Camel 4.5**
+
+**Both producer and consumer are supported**
+
+The AWS2 Bedrock component supports invoking a supported LLM model from
+[AWS Bedrock](https://aws.amazon.com/bedrock/) service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Bedrock. More information is available at
+[Amazon Bedrock](https://aws.amazon.com/bedrock/).
+
+# URI Format
+
+    aws-bedrock-agent-runtime://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required Bedrock component options
+
+You have to provide the bedrockRuntimeClient in the Registry or your
+accessKey and secretKey to access the [Amazon
+Bedrock](https://aws.amazon.com/bedrock/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws-bedrock</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|dataSourceId|Define the Data source Id we are going to use||string|
+|knowledgeBaseId|Define the Knowledge Base Id we are going to use||string|
+|modelId|Define the model Id we are going to use||string|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name|false|string|
+|region|The region in which Bedrock Agent client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the Bedrock Agent client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Bedrock Agent client should expect to load credentials through a profile credentials provider.|false|boolean|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|ingestionJobId|Define the Ingestion Job Id we want to track||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|bedrockAgentClient|To use an existing configured AWS Bedrock Agent client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Bedrock Agent client||string|
+|proxyPort|To define a proxy port when instantiating the Bedrock Agent client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Bedrock Agent client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useSessionCredentials|Set whether the Bedrock Agent client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Bedrock.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|dataSourceId|Define the Data source Id we are going to use||string|
+|knowledgeBaseId|Define the Knowledge Base Id we are going to use||string|
+|modelId|Define the model Id we are going to use||string|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name|false|string|
+|region|The region in which Bedrock Agent client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the Bedrock Agent client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Bedrock Agent client should expect to load credentials through a profile credentials provider.|false|boolean|
+|ingestionJobId|Define the Ingestion Job Id we want to track||string|
+|sendEmptyMessageWhenIdle|If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.|false|boolean|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|pollStrategy|A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|bedrockAgentClient|To use an existing configured AWS Bedrock Agent client||object|
+|proxyHost|To define a proxy host when instantiating the Bedrock Agent client||string|
+|proxyPort|To define a proxy port when instantiating the Bedrock Agent client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Bedrock Agent client|HTTPS|object|
+|backoffErrorThreshold|The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.||integer|
+|backoffIdleThreshold|The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.||integer|
+|backoffMultiplier|To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.||integer|
+|delay|Milliseconds before the next poll.|500|integer|
+|greedy|If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.|false|boolean|
+|initialDelay|Milliseconds before the first poll starts.|1000|integer|
+|repeatCount|Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.|0|integer|
+|runLoggingLevel|The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.|TRACE|object|
+|scheduledExecutorService|Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.||object|
+|scheduler|To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler|none|object|
+|schedulerProperties|To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.||object|
+|startScheduler|Whether the scheduler should be auto started.|true|boolean|
+|timeUnit|Time unit for initialDelay and delay options.|MILLISECONDS|object|
+|useFixedDelay|Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.|true|boolean|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useSessionCredentials|Set whether the Bedrock Agent client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Bedrock.|false|boolean|

camel-aws-bedrock.md

@@ -0,0 +1,830 @@
+# Aws-bedrock
+
+**Since Camel 4.5**
+
+**Only producer is supported**
+
+The AWS2 Bedrock component supports invoking a supported LLM model from
+[AWS Bedrock](https://aws.amazon.com/bedrock/) service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Bedrock. More information is available at
+[Amazon Bedrock](https://aws.amazon.com/bedrock/).
+
+# URI Format
+
+    aws-bedrock://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required Bedrock component options
+
+You have to provide the bedrockRuntimeClient in the Registry or your
+accessKey and secretKey to access the [Amazon
+Bedrock](https://aws.amazon.com/bedrock/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Supported AWS Bedrock Models
+
+-   Titan Text Express V1 with id `amazon.titan-text-express-v1` Express
+    is a large language model for text generation. It is useful for a
+    wide range of advanced, general language tasks such as open-ended
+    text generation and conversational chat, as well as support within
+    Retrieval Augmented Generation (RAG).
+
+Json schema for request
+
+    {
+      "$schema": "http://json-schema.org/draft-04/schema#",
+      "type": "object",
+      "properties": {
+        "inputText": {
+          "type": "string"
+        },
+        "textGenerationConfig": {
+          "type": "object",
+          "properties": {
+            "maxTokenCount": {
+              "type": "integer"
+            },
+            "stopSequences": {
+              "type": "array",
+              "items": [
+                {
+                  "type": "string"
+                }
+              ]
+            },
+            "temperature": {
+              "type": "integer"
+            },
+            "topP": {
+              "type": "integer"
+            }
+          },
+          "required": [
+            "maxTokenCount",
+            "stopSequences",
+            "temperature",
+            "topP"
+          ]
+        }
+      },
+      "required": [
+        "inputText",
+        "textGenerationConfig"
+      ]
+    }
+
+-   Titan Text Lite V1 with id `amazon.titan-text-lite-v1` Lite is a
+    light weight efficient model, ideal for fine-tuning of
+    English-language tasks.
+
+Json schema for request
+
+    {
+      "$schema": "http://json-schema.org/draft-04/schema#",
+      "type": "object",
+      "properties": {
+        "inputText": {
+          "type": "string"
+        },
+        "textGenerationConfig": {
+          "type": "object",
+          "properties": {
+            "maxTokenCount": {
+              "type": "integer"
+            },
+            "stopSequences": {
+              "type": "array",
+              "items": [
+                {
+                  "type": "string"
+                }
+              ]
+            },
+            "temperature": {
+              "type": "integer"
+            },
+            "topP": {
+              "type": "integer"
+            }
+          },
+          "required": [
+            "maxTokenCount",
+            "stopSequences",
+            "temperature",
+            "topP"
+          ]
+        }
+      },
+      "required": [
+        "inputText",
+        "textGenerationConfig"
+      ]
+    }
+
+-   Titan Image Generator G1 with id `amazon.titan-image-generator-v1`
+    It generates images from text, and allows users to upload and edit
+    an existing image. Users can edit an image with a text prompt
+    (without a mask) or parts of an image with an image mask. You can
+    extend the boundaries of an image with outpainting, and fill in an
+    image with inpainting.
+
+Json schema for request
+
+    {
+      "$schema": "http://json-schema.org/draft-04/schema#",
+      "type": "object",
+      "properties": {
+        "textToImageParams": {
+          "type": "object",
+          "properties": {
+            "text": {
+              "type": "string"
+            },
+            "negativeText": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "text",
+            "negativeText"
+          ]
+        },
+        "taskType": {
+          "type": "string"
+        },
+        "imageGenerationConfig": {
+          "type": "object",
+          "properties": {
+            "cfgScale": {
+              "type": "integer"
+            },
+            "seed": {
+              "type": "integer"
+            },
+            "quality": {
+              "type": "string"
+            },
+            "width": {
+              "type": "integer"
+            },
+            "height": {
+              "type": "integer"
+            },
+            "numberOfImages": {
+              "type": "integer"
+            }
+          },
+          "required": [
+            "cfgScale",
+            "seed",
+            "quality",
+            "width",
+            "height",
+            "numberOfImages"
+          ]
+        }
+      },
+      "required": [
+        "textToImageParams",
+        "taskType",
+        "imageGenerationConfig"
+      ]
+    }
+
+-   Titan Embeddings G1 with id `amazon.titan-embed-text-v1` The Amazon
+    Titan Embeddings G1 - Text – Text v1.2 can intake up to 8k tokens
+    and outputs a vector of 1,536 dimensions. The model also works in
+    25+ different language
+
+Json schema for request
+
+    {
+      "$schema": "http://json-schema.org/draft-04/schema#",
+      "type": "object",
+      "properties": {
+        "inputText": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "inputText"
+      ]
+    }
+
+-   Jurassic2-Ultra with id `ai21.j2-ultra-v1` Jurassic-2 Ultra is
+    AI21’s most powerful model for complex tasks that require advanced
+    text generation and comprehension.
+
+Json schema for request
+
+    {
+      "$schema": "http://json-schema.org/draft-04/schema#",
+      "type": "object",
+      "properties": {
+        "prompt": {
+          "type": "string"
+        },
+        "maxTokens": {
+          "type": "integer"
+        },
+        "temperature": {
+          "type": "integer"
+        },
+        "topP": {
+          "type": "integer"
+        },
+        "stopSequences": {
+          "type": "array",
+          "items": [
+            {
+              "type": "string"
+            }
+          ]
+        },
+        "presencePenalty": {
+          "type": "object",
+          "properties": {
+            "scale": {
+              "type": "integer"
+            }
+          },
+          "required": [
+            "scale"
+          ]
+        },
+        "frequencyPenalty": {
+          "type": "object",
+          "properties": {
+            "scale": {
+              "type": "integer"
+            }
+          },
+          "required": [
+            "scale"
+          ]
+        }
+      },
+      "required": [
+        "prompt",
+        "maxTokens",
+        "temperature",
+        "topP",
+        "stopSequences",
+        "presencePenalty",
+        "frequencyPenalty"
+      ]
+    }
+
+-   Jurassic2-Mid with id `ai21.j2-mid-v1` Jurassic-2 Mid is less
+    powerful than Ultra, yet carefully designed to strike the right
+    balance between exceptional quality and affordability.
+
+Json schema for request
+
+    {
+      "$schema": "http://json-schema.org/draft-04/schema#",
+      "type": "object",
+      "properties": {
+        "prompt": {
+          "type": "string"
+        },
+        "maxTokens": {
+          "type": "integer"
+        },
+        "temperature": {
+          "type": "integer"
+        },
+        "topP": {
+          "type": "integer"
+        },
+        "stopSequences": {
+          "type": "array",
+          "items": [
+            {
+              "type": "string"
+            }
+          ]
+        },
+        "presencePenalty": {
+          "type": "object",
+          "properties": {
+            "scale": {
+              "type": "integer"
+            }
+          },
+          "required": [
+            "scale"
+          ]
+        },
+        "frequencyPenalty": {
+          "type": "object",
+          "properties": {
+            "scale": {
+              "type": "integer"
+            }
+          },
+          "required": [
+            "scale"
+          ]
+        }
+      },
+      "required": [
+        "prompt",
+        "maxTokens",
+        "temperature",
+        "topP",
+        "stopSequences",
+        "presencePenalty",
+        "frequencyPenalty"
+      ]
+    }
+
+-   Claude Instant V1.2 with id `anthropic.claude-instant-v1` A fast,
+    affordable yet still very capable model, which can handle a range of
+    tasks including casual dialogue, text analysis, summarization, and
+    document question-answering.
+
+Json schema for request
+
+    {
+      "$schema": "http://json-schema.org/draft-04/schema#",
+      "type": "object",
+      "properties": {
+        "prompt": {
+          "type": "string"
+        },
+        "max_tokens_to_sample": {
+          "type": "integer"
+        },
+        "stop_sequences": {
+          "type": "array",
+          "items": [
+            {
+              "type": "string"
+            }
+          ]
+        },
+        "temperature": {
+          "type": "number"
+        },
+        "top_p": {
+          "type": "integer"
+        },
+        "top_k": {
+          "type": "integer"
+        },
+        "anthropic_version": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "prompt",
+        "max_tokens_to_sample",
+        "stop_sequences",
+        "temperature",
+        "top_p",
+        "top_k",
+        "anthropic_version"
+      ]
+    }
+
+-   Claude 2 with id `anthropic.claude-v2` Anthropic’s highly capable
+    model across a wide range of tasks from sophisticated dialogue and
+    creative content generation to detailed instruction following.
+
+Json schema for request
+
+    {
+      "$schema": "http://json-schema.org/draft-04/schema#",
+      "type": "object",
+      "properties": {
+        "prompt": {
+          "type": "string"
+        },
+        "max_tokens_to_sample": {
+          "type": "integer"
+        },
+        "stop_sequences": {
+          "type": "array",
+          "items": [
+            {
+              "type": "string"
+            }
+          ]
+        },
+        "temperature": {
+          "type": "number"
+        },
+        "top_p": {
+          "type": "integer"
+        },
+        "top_k": {
+          "type": "integer"
+        },
+        "anthropic_version": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "prompt",
+        "max_tokens_to_sample",
+        "stop_sequences",
+        "temperature",
+        "top_p",
+        "top_k",
+        "anthropic_version"
+      ]
+    }
+
+-   Claude 2.1 with id `anthropic.claude-v2:1` An update to Claude 2
+    that features double the context window, plus improvements across
+    reliability, hallucination rates, and evidence-based accuracy in
+    long document and RAG contexts.
+
+Json schema for request
+
+    {
+      "$schema": "http://json-schema.org/draft-04/schema#",
+      "type": "object",
+      "properties": {
+        "prompt": {
+          "type": "string"
+        },
+        "max_tokens_to_sample": {
+          "type": "integer"
+        },
+        "stop_sequences": {
+          "type": "array",
+          "items": [
+            {
+              "type": "string"
+            }
+          ]
+        },
+        "temperature": {
+          "type": "number"
+        },
+        "top_p": {
+          "type": "integer"
+        },
+        "top_k": {
+          "type": "integer"
+        },
+        "anthropic_version": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "prompt",
+        "max_tokens_to_sample",
+        "stop_sequences",
+        "temperature",
+        "top_p",
+        "top_k",
+        "anthropic_version"
+      ]
+    }
+
+-   Claude 3 Sonnet with id `anthropic.claude-3-sonnet-20240229-v1:0`
+    Claude 3 Sonnet by Anthropic strikes the ideal balance between
+    intelligence and speed—particularly for enterprise workloads.
+
+Json schema for request
+
+    {
+      "$schema": "http://json-schema.org/draft-04/schema#",
+      "type": "object",
+      "properties": {
+        "messages": {
+          "type": "array",
+          "items": [
+            {
+              "type": "object",
+              "properties": {
+                "role": {
+                  "type": "string"
+                },
+                "content": {
+                  "type": "array",
+                  "items": [
+                    {
+                      "type": "object",
+                      "properties": {
+                        "type": {
+                          "type": "string"
+                        },
+                        "text": {
+                          "type": "string"
+                        }
+                      },
+                      "required": [
+                        "type",
+                        "text"
+                      ]
+                    }
+                  ]
+                }
+              },
+              "required": [
+                "role",
+                "content"
+              ]
+            }
+          ]
+        },
+        "max_tokens": {
+          "type": "integer"
+        },
+        "anthropic_version": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "messages",
+        "max_tokens",
+        "anthropic_version"
+      ]
+    }
+
+-   Claude 3 Haiku with id `anthropic.claude-3-haiku-20240307-v1:0`
+    Claude 3 Haiku is Anthropic’s fastest, most compact model for
+    near-instant responsiveness. It answers simple queries and requests
+    with speed.
+
+Json schema for request
+
+    {
+      "$schema": "http://json-schema.org/draft-04/schema#",
+      "type": "object",
+      "properties": {
+        "messages": {
+          "type": "array",
+          "items": [
+            {
+              "type": "object",
+              "properties": {
+                "role": {
+                  "type": "string"
+                },
+                "content": {
+                  "type": "array",
+                  "items": [
+                    {
+                      "type": "object",
+                      "properties": {
+                        "type": {
+                          "type": "string"
+                        },
+                        "text": {
+                          "type": "string"
+                        }
+                      },
+                      "required": [
+                        "type",
+                        "text"
+                      ]
+                    }
+                  ]
+                }
+              },
+              "required": [
+                "role",
+                "content"
+              ]
+            }
+          ]
+        },
+        "max_tokens": {
+          "type": "integer"
+        },
+        "anthropic_version": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "messages",
+        "max_tokens",
+        "anthropic_version"
+      ]
+    }
+
+## Bedrock Producer operations
+
+Camel-AWS Bedrock component provides the following operation on the
+producer side:
+
+-   invokeTextModel
+
+-   invokeImageModel
+
+-   invokeEmbeddingsModel
+
+# Producer Examples
+
+-   invokeTextModel: this operation will invoke a model from Bedrock.
+    This is an example for both Titan Express and Titan Lite.
+
+<!-- -->
+
+    from("direct:invoke")
+        .to("aws-bedrock://test?bedrockRuntimeClient=#amazonBedrockRuntimeClient&operation=invokeTextModel&modelId="
+                                + BedrockModels.TITAN_TEXT_EXPRESS_V1.model))
+
+and you can then send to the direct endpoint something like
+
+            final Exchange result = template.send("direct:invoke", exchange -> {
+                ObjectMapper mapper = new ObjectMapper();
+                ObjectNode rootNode = mapper.createObjectNode();
+                rootNode.put("inputText",
+                        "User: Generate synthetic data for daily product sales in various categories - include row number, product name, category, date of sale and price. Produce output in JSON format. Count records and ensure there are no more than 5.");
+    
+                ArrayNode stopSequences = mapper.createArrayNode();
+                stopSequences.add("User:");
+                ObjectNode childNode = mapper.createObjectNode();
+                childNode.put("maxTokenCount", 1024);
+                childNode.put("stopSequences", stopSequences);
+                childNode.put("temperature", 0).put("topP", 1);
+    
+                rootNode.put("textGenerationConfig", childNode);
+                exchange.getMessage().setBody(mapper.writer().writeValueAsString(rootNode));
+                exchange.getMessage().setHeader(BedrockConstants.MODEL_CONTENT_TYPE, "application/json");
+                exchange.getMessage().setHeader(BedrockConstants.MODEL_ACCEPT_CONTENT_TYPE, "application/json");
+            });
+
+where template is a ProducerTemplate.
+
+-   invokeImageModel: this operation will invoke a model from Bedrock.
+    This is an example for both Titan Express and Titan Lite.
+
+<!-- -->
+
+    from("direct:invoke")
+        .to("aws-bedrock://test?bedrockRuntimeClient=#amazonBedrockRuntimeClient&operation=invokeImageModel&modelId="
+                                + BedrockModels.TITAN_IMAGE_GENERATOR_V1.model))
+                            .split(body())
+                            .unmarshal().base64()
+                            .setHeader("CamelFileName", simple("image-${random(128)}.png")).to("file:target/generated_images")
+
+and you can then send to the direct endpoint something like
+
+            final Exchange result = template.send("direct:send_titan_image", exchange -> {
+                ObjectMapper mapper = new ObjectMapper();
+                ObjectNode rootNode = mapper.createObjectNode();
+                ObjectNode textParameter = mapper.createObjectNode();
+                textParameter.putIfAbsent("text",
+                        new TextNode("A Sci-fi camel running in the desert"));
+                rootNode.putIfAbsent("textToImageParams", textParameter);
+                rootNode.putIfAbsent("taskType", new TextNode("TEXT_IMAGE"));
+                ObjectNode childNode = mapper.createObjectNode();
+                childNode.putIfAbsent("numberOfImages", new IntNode(3));
+                childNode.putIfAbsent("quality", new TextNode("standard"));
+                childNode.putIfAbsent("cfgScale", new IntNode(8));
+                childNode.putIfAbsent("height", new IntNode(512));
+                childNode.putIfAbsent("width", new IntNode(512));
+                childNode.putIfAbsent("seed", new IntNode(0));
+    
+                rootNode.putIfAbsent("imageGenerationConfig", childNode);
+    
+                exchange.getMessage().setBody(mapper.writer().writeValueAsString(rootNode));
+                exchange.getMessage().setHeader(BedrockConstants.MODEL_CONTENT_TYPE, "application/json");
+                exchange.getMessage().setHeader(BedrockConstants.MODEL_ACCEPT_CONTENT_TYPE, "application/json");
+            });
+
+where template is a ProducerTemplate.
+
+-   invokeEmbeddingsModel: this operation will invoke an Embeddings
+    model from Bedrock. This is an example for Titan Embeddings G1.
+
+<!-- -->
+
+    from("direct:send_titan_embeddings")
+        .to("aws-bedrock:label?useDefaultCredentialsProvider=true&region=us-east-1&operation=invokeEmbeddingsModel&modelId="
+        + BedrockModels.TITAN_EMBEDDINGS_G1.model)
+        .to(result);
+
+and you can then send to the direct endpoint something like
+
+            final Exchange result = template.send("direct:send_titan_embeddings", exchange -> {
+                ObjectMapper mapper = new ObjectMapper();
+                ObjectNode rootNode = mapper.createObjectNode();
+                rootNode.putIfAbsent("inputText",
+                        new TextNode("A Sci-fi camel running in the desert"));
+    
+                exchange.getMessage().setBody(mapper.writer().writeValueAsString(rootNode));
+                exchange.getMessage().setHeader(BedrockConstants.MODEL_CONTENT_TYPE, "application/json");
+                exchange.getMessage().setHeader(BedrockConstants.MODEL_ACCEPT_CONTENT_TYPE, "*/*");
+            });
+
+where template is a ProducerTemplate.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws-bedrock</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|modelId|Define the model Id we are going to use||string|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name|false|string|
+|region|The region in which Bedrock client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the Bedrock client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Bedrock client should expect to load credentials through a profile credentials provider.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|bedrockRuntimeClient|To use an existing configured AWS Bedrock Runtime client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Bedrock client||string|
+|proxyPort|To define a proxy port when instantiating the Bedrock client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Bedrock client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useSessionCredentials|Set whether the Bedrock client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Bedrock.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|modelId|Define the model Id we are going to use||string|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name|false|string|
+|region|The region in which Bedrock client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the Bedrock client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Bedrock client should expect to load credentials through a profile credentials provider.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|bedrockRuntimeClient|To use an existing configured AWS Bedrock Runtime client||object|
+|proxyHost|To define a proxy host when instantiating the Bedrock client||string|
+|proxyPort|To define a proxy port when instantiating the Bedrock client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Bedrock client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useSessionCredentials|Set whether the Bedrock client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Bedrock.|false|boolean|

camel-aws-cloudtrail.md

@@ -0,0 +1,143 @@
+# Aws-cloudtrail
+
+**Since Camel 3.19**
+
+**Only consumer is supported**
+
+The AWS Cloudtrail component supports receiving events from Amazon
+Cloudtrail service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Cloudtrail. More information is available at
+[AWS Cloudtrail](https://aws.amazon.com/cloudtrail/)
+
+# Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+# Cloudtrail Events consumed
+
+The Cloudtrail consumer will use an API method called LookupEvents.
+
+This method will only take into account management events like
+create/update/delete of resources and Cloudtrail insight events where
+enabled.
+
+This means you won’t consume the events registered in the Cloudtrail
+logs stored on S3, in case of creation of a new Trail.
+
+This is important to notice, and it must be taken into account when
+using this component.
+
+# URI Format
+
+    aws-cloudtrail://label[?options]
+
+The stream needs to be created prior to it being used.
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|configuration|Component configuration||object|
+|eventSource|Specify an event source to select events||string|
+|maxResults|Maximum number of records that will be fetched in each poll|1|integer|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with uriEndpointOverride option|false|boolean|
+|region|The region in which Cloudtrail client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|cloudTrailClient|Amazon Cloudtrail client to use for all requests for this endpoint||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Cloudtrail client||string|
+|proxyPort|To define a proxy port when instantiating the Cloudtrail client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Cloudtrail client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name.||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume a IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Cloudtrail client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Cloudtrail client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the CloudTrail client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in CloudTrail.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|A label for indexing cloudtrail endpoints||string|
+|eventSource|Specify an event source to select events||string|
+|maxResults|Maximum number of records that will be fetched in each poll|1|integer|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with uriEndpointOverride option|false|boolean|
+|region|The region in which Cloudtrail client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|sendEmptyMessageWhenIdle|If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.|false|boolean|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|pollStrategy|A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.||object|
+|cloudTrailClient|Amazon Cloudtrail client to use for all requests for this endpoint||object|
+|proxyHost|To define a proxy host when instantiating the Cloudtrail client||string|
+|proxyPort|To define a proxy port when instantiating the Cloudtrail client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Cloudtrail client|HTTPS|object|
+|backoffErrorThreshold|The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.||integer|
+|backoffIdleThreshold|The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.||integer|
+|backoffMultiplier|To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.||integer|
+|delay|Milliseconds before the next poll.|500|integer|
+|greedy|If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.|false|boolean|
+|initialDelay|Milliseconds before the first poll starts.|1000|integer|
+|repeatCount|Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.|0|integer|
+|runLoggingLevel|The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.|TRACE|object|
+|scheduledExecutorService|Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.||object|
+|scheduler|To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler|none|object|
+|schedulerProperties|To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.||object|
+|startScheduler|Whether the scheduler should be auto started.|true|boolean|
+|timeUnit|Time unit for initialDelay and delay options.|MILLISECONDS|object|
+|useFixedDelay|Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.|true|boolean|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name.||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume a IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Cloudtrail client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Cloudtrail client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the CloudTrail client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in CloudTrail.|false|boolean|

camel-aws-config.md

@@ -0,0 +1,117 @@
+# Aws-config
+
+**Since Camel 4.3**
+
+**Only producer is supported**
+
+The AWS Config component supports create and delete config rules [AWS
+ECS](https://aws.amazon.com/config/) clusters instances.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Config. More information is available at [Amazon
+Config](https://aws.amazon.com/config/).
+
+# URI Format
+
+    aws-config://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required Config component options
+
+You have to provide the ConfigClient in the Registry or your accessKey
+and secretKey to access the [Amazon
+Config](https://aws.amazon.com/config/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the Config client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|configClient|Amazon AWS Config Client instance||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Config client||string|
+|proxyPort|To define a proxy port when instantiating the Config client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Config client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Config client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Config client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Config client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Config.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the Config client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|configClient|Amazon AWS Config Client instance||object|
+|proxyHost|To define a proxy host when instantiating the Config client||string|
+|proxyPort|To define a proxy port when instantiating the Config client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Config client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Config client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Config client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Config client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Config.|false|boolean|

camel-aws-secrets-manager.md

@@ -0,0 +1,393 @@
+# Aws-secrets-manager
+
+**Since Camel 3.9**
+
+**Only producer is supported**
+
+The AWS Secrets Manager component supports list secret [AWS Secrets
+Manager](https://aws.amazon.com/secrets-manager/) service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Secrets Manager. More information is available
+at [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/).
+
+# URI Format
+
+    aws-secrets-manager://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Using AWS Secrets Manager Property Function
+
+To use this function, you’ll need to provide credentials to AWS Secrets
+Manager Service as environment variables:
+
+    export $CAMEL_VAULT_AWS_ACCESS_KEY=accessKey
+    export $CAMEL_VAULT_AWS_SECRET_KEY=secretKey
+    export $CAMEL_VAULT_AWS_REGION=region
+
+You can also configure the credentials in the `application.properties`
+file such as:
+
+    camel.vault.aws.accessKey = accessKey
+    camel.vault.aws.secretKey = secretKey
+    camel.vault.aws.region = region
+
+If you want instead to use the [AWS default credentials
+provider](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html),
+you’ll need to provide the following env variables:
+
+    export $CAMEL_VAULT_AWS_USE_DEFAULT_CREDENTIALS_PROVIDER=true
+    export $CAMEL_VAULT_AWS_REGION=region
+
+You can also configure the credentials in the `application.properties`
+file such as:
+
+    camel.vault.aws.defaultCredentialsProvider = true
+    camel.vault.aws.region = region
+
+It is also possible to specify a particular profile name for accessing
+AWS Secrets Manager
+
+    export $CAMEL_VAULT_AWS_USE_PROFILE_CREDENTIALS_PROVIDER=true
+    export $CAMEL_VAULT_AWS_PROFILE_NAME=test-account
+    export $CAMEL_VAULT_AWS_REGION=region
+
+You can also configure the credentials in the `application.properties`
+file such as:
+
+    camel.vault.aws.profileCredentialsProvider = true
+    camel.vault.aws.profileName = test-account
+    camel.vault.aws.region = region
+
+At this point, you’ll be able to reference a property in the following
+way:
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <to uri="{{aws:route}}"/>
+        </route>
+    </camelContext>
+
+Where route will be the name of the secret stored in the AWS Secrets
+Manager Service.
+
+You could specify a default value in case the secret is not present on
+AWS Secret Manager:
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <to uri="{{aws:route:default}}"/>
+        </route>
+    </camelContext>
+
+In this case, if the secret doesn’t exist, the property will fall back
+to "default" as value.
+
+Also, you are able to get a particular field of the secret, if you have,
+for example, a secret named database of this form:
+
+    {
+      "username": "admin",
+      "password": "password123",
+      "engine": "postgres",
+      "host": "127.0.0.1",
+      "port": "3128",
+      "dbname": "db"
+    }
+
+You’re able to do get single secret value in your route, like for
+example:
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <log message="Username is {{aws:database/username}}"/>
+        </route>
+    </camelContext>
+
+Or re-use the property as part of an endpoint.
+
+You could specify a default value in case the particular field of secret
+is not present on AWS Secret Manager:
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <log message="Username is {{aws:database/username:admin}}"/>
+        </route>
+    </camelContext>
+
+In this case, if the secret doesn’t exist or the secret exists, but the
+username field is not part of the secret, the property will fall back to
+"admin" as value.
+
+There is also the syntax to get a particular version of the secret for
+both the approach, with field/default value specified or only with
+secret:
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <to uri="{{aws:route@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}"/>
+        </route>
+    </camelContext>
+
+This approach will return the RAW route secret with the version
+*bf9b4f4b-8e63-43fd-a73c-3e2d3748b451*.
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <to uri="{{aws:route:default@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}"/>
+        </route>
+    </camelContext>
+
+This approach will return the route secret value with version
+*bf9b4f4b-8e63-43fd-a73c-3e2d3748b451* or default value in case the
+secret doesn’t exist or the version doesn’t exist.
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <log message="Username is {{aws:database/username:admin@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}"/>
+        </route>
+    </camelContext>
+
+This approach will return the username field of the database secret with
+version *bf9b4f4b-8e63-43fd-a73c-3e2d3748b451* or admin in case the
+secret doesn’t exist or the version doesn’t exist.
+
+For the moment we are not considering the rotation function if any are
+applied, but it is in the work to be done.
+
+The only requirement is adding the camel-aws-secrets-manager jar to your
+Camel application.
+
+## Automatic Camel context reloading on Secret Refresh
+
+Being able to reload Camel context on a Secret Refresh could be done by
+specifying the usual credentials (the same used for AWS Secret Manager
+Property Function).
+
+With Environment variables:
+
+    export $CAMEL_VAULT_AWS_USE_DEFAULT_CREDENTIALS_PROVIDER=accessKey
+    export $CAMEL_VAULT_AWS_REGION=region
+
+or as plain Camel main properties:
+
+    camel.vault.aws.useDefaultCredentialProvider = true
+    camel.vault.aws.region = region
+
+Or by specifying accessKey/SecretKey and region, instead of using the
+default credentials provider chain.
+
+To enable the automatic refresh, you’ll need additional properties to
+set:
+
+    camel.vault.aws.refreshEnabled=true
+    camel.vault.aws.refreshPeriod=60000
+    camel.vault.aws.secrets=Secret
+    camel.main.context-reload-enabled = true
+
+where `camel.vault.aws.refreshEnabled` will enable the automatic context
+reload, `camel.vault.aws.refreshPeriod` is the interval of time between
+two different checks for update events and `camel.vault.aws.secrets` is
+a regex representing the secrets we want to track for updates.
+
+Note that `camel.vault.aws.secrets` is not mandatory: if not specified
+the task responsible for checking updates events will take into accounts
+or the properties with an `aws:` prefix.
+
+## Automatic Camel context reloading on Secret Refresh with Eventbridge and AWS SQS Services
+
+Another option is to use AWS EventBridge in conjunction with the AWS SQS
+service.
+
+On the AWS side, the following resources need to be created:
+
+-   an AWS Couldtrail trail
+
+-   an AWS SQS Queue
+
+-   an Eventbridge rule of the following kind
+
+<!-- -->
+
+    {
+      "source": ["aws.secretsmanager"],
+      "detail-type": ["AWS API Call via CloudTrail"],
+      "detail": {
+        "eventSource": ["secretsmanager.amazonaws.com"]
+      }
+    }
+
+This rule will make the event related to AWS Secrets Manager filtered
+
+-   You need to set the a Rule target to the AWS SQS Queue for
+    Eventbridge rule
+
+-   You need to give permission to the Eventbrige rule, to write on the
+    above SQS Queue. For doing this you’ll need to define a json file
+    like this:
+
+<!-- -->
+
+    {
+        "Policy": "{\"Version\":\"2012-10-17\",\"Id\":\"<queue_arn>/SQSDefaultPolicy\",\"Statement\":[{\"Sid\": \"EventsToMyQueue\", \"Effect\": \"Allow\", \"Principal\": {\"Service\": \"events.amazonaws.com\"}, \"Action\": \"sqs:SendMessage\", \"Resource\": \"<queue_arn>\", \"Condition\": {\"ArnEquals\": {\"aws:SourceArn\": \"<eventbridge_rule_arn>\"}}}]}"
+    }
+
+Change the values for queue\_arn and eventbridge\_rule\_arn, save the
+file with policy.json name and run the following command with AWS CLI
+
+    aws sqs set-queue-attributes --queue-url <queue_url> --attributes file://policy.json
+
+where queue\_url is the AWS SQS Queue URL of the just created Queue.
+
+Now you should be able to set up the configuration on the Camel side. To
+enable the SQS notification add the following properties:
+
+    camel.vault.aws.refreshEnabled=true
+    camel.vault.aws.refreshPeriod=60000
+    camel.vault.aws.secrets=Secret
+    camel.main.context-reload-enabled = true
+    camel.vault.aws.useSqsNotification=true
+    camel.vault.aws.sqsQueueUrl=<queue_url>
+
+where queue\_url is the AWS SQS Queue URL of the just created Queue.
+
+Whenever an event of PutSecretValue for the Secret named *Secret* will
+happen, a message will be enqueued in the AWS SQS Queue and consumed on
+the Camel side and a context reload will be triggered.
+
+## Secrets Manager Producer operations
+
+Camel-AWS-Secrets-manager component provides the following operation on
+the producer side:
+
+-   listSecrets
+
+-   createSecret
+
+-   deleteSecret
+
+-   describeSecret
+
+-   rotateSecret
+
+-   getSecret
+
+-   updateSecret
+
+-   replicateSecretToRegions
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws-secrets-manager</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|binaryPayload|Set if the secret is binary or not|false|boolean|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|region|The region in which a Secrets Manager client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useProfileCredentialsProvider|Set whether the Secrets Manager client should expect to load credentials through a profile credentials provider.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|secretsManagerClient|To use an existing configured AWS Secrets Manager client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Secrets Manager client||string|
+|proxyPort|To define a proxy port when instantiating the Secrets Manager client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Secrets Manager client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Translate client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useSessionCredentials|Set whether the Secrets Manager client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Secrets Manager.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|binaryPayload|Set if the secret is binary or not|false|boolean|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|region|The region in which a Secrets Manager client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useProfileCredentialsProvider|Set whether the Secrets Manager client should expect to load credentials through a profile credentials provider.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|secretsManagerClient|To use an existing configured AWS Secrets Manager client||object|
+|proxyHost|To define a proxy host when instantiating the Secrets Manager client||string|
+|proxyPort|To define a proxy port when instantiating the Secrets Manager client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Secrets Manager client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Translate client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useSessionCredentials|Set whether the Secrets Manager client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Secrets Manager.|false|boolean|

camel-aws2-athena.md

@@ -0,0 +1,408 @@
+# Aws2-athena
+
+**Since Camel 3.4**
+
+**Only producer is supported**
+
+The AWS2 Athena component supports running queries with [AWS
+Athena](https://aws.amazon.com/athena/) and working with results.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Athena. More information is available at [AWS
+Athena](https://aws.amazon.com/athena/).
+
+# URI Format
+
+    aws2-athena://label[?options]
+
+You can append query options to the URI in the following format:
+`?options=value&option2=value&...`
+
+Required Athena component options
+
+You have to provide the amazonAthenaClient in the Registry or your
+accessKey and secretKey to access the [AWS
+Athena](https://aws.amazon.com/athena/) service.
+
+# Examples
+
+## Producer Examples
+
+For example, to run a simple query, wait up to 60 seconds for
+completion, and log the results:
+
+    from("direct:start")
+        .setBody(constant("SELECT 1"))
+        .to("aws2-athena://label?waitTimeout=60000&outputLocation=s3://bucket/path/")
+        .to("aws2-athena://label?operation=getQueryResults&outputType=StreamList")
+        .split(body()).streaming()
+        .to("log:out")
+        .to("mock:result");
+
+Similarly, running the query and returning a path to the results in S3:
+
+    from("direct:start")
+        .setBody(constant("SELECT 1"))
+        .to("aws2-athena://label?waitTimeout=60000&outputLocation=s3://bucket/path/")
+        .to("aws2-athena://label?operation=getQueryResults&outputType=S3Pointer")
+        .to("mock:result");
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Athena Producer operations
+
+The Camel-AWS Athena component provides the following operation on the
+producer side:
+
+-   getQueryExecution
+
+-   getQueryResults
+
+-   listQueryExecutions
+
+-   startQueryExecution
+
+## Advanced AmazonAthena configuration
+
+If your Camel Application is running behind a firewall or if you need to
+have more control over the `AthenaClient` instance configuration, you
+can create your own instance and refer to it in your Camel aws2-athena
+component configuration:
+
+    from("aws2-athena://MyQuery?amazonAthenaClient=#client&...")
+    .to("mock:result");
+
+## Overriding query parameters with message headers
+
+Message headers listed in "Message headers evaluated by the Athena
+producer" override the corresponding query parameters listed in "Query
+Parameters".
+
+For example:
+
+    from("direct:start")
+         .setHeader(Athena2Constants.OUTPUT_LOCATION, constant("s3://other/location/"))
+         .to("aws2-athena:label?outputLocation=s3://foo/bar/")
+         .to("mock:result");
+
+Will cause the output location to be `s3://other/location/`.
+
+## Athena Producer Operation examples
+
+-   getQueryExecution: this operation returns information about a query
+    given its query execution ID
+
+<!-- -->
+
+    from("direct:start")
+        .to("aws2-athena://label?operation=getQueryExecution&queryExecutionId=11111111-1111-1111-1111-111111111111")
+        .to("mock:result");
+
+The preceding example will yield an [Athena
+QueryExecution](https://docs.aws.amazon.com/athena/latest/APIReference/API_QueryExecution.html)
+in the body.
+
+The getQueryExecution operation also supports retrieving the query
+execution ID from a header (`CamelAwsAthenaQueryExecutionId`), and since
+startQueryExecution sets the same header, upon starting a query, these
+operations can be used together:
+
+    from("direct:start")
+        .setBody(constant("SELECT 1"))
+        .to("aws2-athena://label?operation=startQueryExecution&outputLocation=s3://bucket/path/")
+        .to("aws2-athena://label?operation=getQueryExecution")
+        .to("mock:result");
+
+The preceding example will yield an Athena QueryExecution in the body
+for the query that was just started.
+
+-   getQueryResults: this operation returns the results of a query that
+    has succeeded. The results are returned in the body in one of three
+    formats.
+
+`StreamList` - the default - returns a
+[GetQueryResultsIterable](https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/services/athena/paginators/GetQueryResultsIterable.html)
+in the body that can page through all results:
+
+    from("direct:start")
+        .setBody(constant("SELECT 1"))
+        .to("aws2-athena://label?operation=startQueryExecution&waitTimeout=60000&outputLocation=s3://bucket/path/")
+        .to("aws2-athena://label?operation=getQueryResults&outputType=StreamList")
+        .to("mock:result");
+
+The output of StreamList can be processed in various ways:
+
+    from("direct:start")
+        .setBody(constant(
+            "SELECT * FROM ("
+                + "    VALUES"
+                + "        (1, 'a'),"
+                + "        (2, 'b')"
+                + ") AS t (id, name)"))
+        .to("aws2-athena://label?operation=startQueryExecution&waitTimeout=60000&outputLocation=s3://bucket/path/")
+        .to("aws2-athena://label?operation=getQueryResults&outputType=StreamList")
+        .split(body()).streaming()
+        .process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) {
+            GetQueryResultsResponse page = exchange
+                                            .getMessage()
+                                            .getBody(GetQueryResultsResponse.class);
+            for (Row row : page.resultSet().rows()) {
+              String line = row.data()
+                              .stream()
+                              .map(Datum::varCharValue)
+                              .collect(Collectors.joining(","));
+              System.out.println(line);
+            }
+          }
+        })
+        .to("mock:result");
+
+The preceding example will print the results of the query as CSV to the
+console.
+
+`SelectList` - returns a
+[GetQueryResponse](https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/services/athena/model/GetQueryResultsResponse.html)
+in the body containing at most 1,000 rows, plus the NextToken value as a
+header (`CamelAwsAthenaNextToken`), which can be used for manual
+pagination of results:
+
+    from("direct:start")
+        .setBody(constant("SELECT 1"))
+        .to("aws2-athena://label?operation=startQueryExecution&waitTimeout=60000&outputLocation=s3://bucket/path/")
+        .to("aws2-athena://label?operation=getQueryResults&outputType=SelectList")
+        .to("mock:result");
+
+The preceding example will return a
+[GetQueryResponse](https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/services/athena/model/GetQueryResultsResponse.html)
+in the body plus the NextToken value as a header
+(`CamelAwsAthenaNextToken`), which can be used to manually page through
+the results 1,000 rows at a time.
+
+`S3Pointer` - return an S3 path (e.g. `s3://bucket/path/`) pointing to
+the results:
+
+    from("direct:start")
+        .setBody(constant("SELECT 1"))
+        .to("aws2-athena://label?operation=startQueryExecution&waitTimeout=60000&outputLocation=s3://bucket/path/")
+        .to("aws2-athena://label?operation=getQueryResults&outputType=S3Pointer")
+        .to("mock:result");
+
+The preceding example will return an S3 path (e.g. `s3://bucket/path/`)
+in the body pointing to the results. The path will also be set in a
+header (`CamelAwsAthenaOutputLocation`).
+
+-   listQueryExecutions: this operation returns a list of query
+    execution IDs
+
+<!-- -->
+
+    from("direct:start")
+        .to("aws2-athena://label?operation=listQueryExecutions")
+        .to("mock:result");
+
+The preceding example will return a list of query executions in the
+body, plus the NextToken value as a header (`CamelAwsAthenaNextToken`)
+than can be used for manual pagination of results.
+
+-   startQueryExecution: this operation starts the execution of a query.
+    It supports waiting for the query to complete before proceeding, and
+    retrying the query based on a set of configurable failure
+    conditions:
+
+<!-- -->
+
+    from("direct:start")
+        .setBody(constant("SELECT 1"))
+        .to("aws2-athena://label?operation=startQueryExecution&outputLocation=s3://bucket/path/")
+        .to("mock:result");
+
+The preceding example will start the query `SELECT 1` and configure the
+results to be saved to `s3://bucket/path/`, but will not wait for the
+query to complete.
+
+    from("direct:start")
+        .setBody(constant("SELECT 1"))
+        .to("aws2-athena://label?operation=startQueryExecution&waitTimeout=60000&outputLocation=s3://bucket/path/")
+        .to("mock:result");
+
+The preceding example will start a query and wait up to 60 seconds for
+it to reach a status that indicates it is complete (one of SUCCEEDED,
+FAILED, CANCELLED, or UNKNOWN\_TO\_SDK\_VERSION). Upon failure, the
+query would not be retried.
+
+    from("direct:start")
+        .setBody(constant("SELECT 1"))
+        .to("aws2-athena://label?operation=startQueryExecution&waitTimeout=60000&initialDelay=10000&delay=1000&maxAttempts=3&retry=retryable&outputLocation=s3://bucket/path/")
+        .to("mock:result");
+
+The preceding example will start a query and wait up to 60 seconds for
+it to reach a status that indicates it is complete (one of SUCCEEDED,
+FAILED, CANCELLED, or UNKNOWN\_TO\_SDK\_VERSION). Upon failure, the
+query would be automatically retried up to two more times if the failure
+state indicates the query may succeed upon retry (Athena queries that
+fail with states such as `GENERIC_INTERNAL_ERROR` or "resource limit
+exhaustion" will sometimes succeed if retried). While waiting for the
+query to complete, the query status would first be checked after an
+initial delay of 10 seconds, and subsequently every 1 second until the
+query completes.
+
+## Putting it all together
+
+    from("direct:start")
+        .setBody(constant("SELECT 1"))
+        .to("aws2-athena://label?waitTimeout=60000&&maxAttempts=3&retry=retryable&outputLocation=s3://bucket/path/")
+        .to("aws2-athena://label?operation=getQueryResults&outputType=StreamList")
+        .to("mock:result");
+
+The preceding example will start the query and wait up to 60 seconds for
+it to complete. Upon completion, getQueryResults put the results of the
+query into the body of the message for further processing.
+
+For the sake of completeness, a similar outcome could be achieved with
+the following:
+
+    from("direct:start")
+        .setBody(constant("SELECT 1"))
+        .to("aws2-athena://label?operation=startQueryExecution&outputLocation=s3://bucket/path/")
+        .loopDoWhile(simple("${header." + Athena2Constants.QUERY_EXECUTION_STATE + "} != 'SUCCEEDED'"))
+          .delay(1_000)
+          .to("aws2-athena://label?operation=getQueryExecution")
+        .end()
+        .to("aws2-athena://label?operation=getQueryResults&outputType=StreamList")
+        .to("mock:result");
+
+Caution: the preceding example would block indefinitely, however, if the
+query did not complete with a status of SUCCEEDED.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-athena</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|The component configuration.||object|
+|database|The Athena database to use.||string|
+|delay|Milliseconds before the next poll for query execution status. See the section Waiting for Query Completion and Retrying Failed Queries to learn more.|2000|integer|
+|initialDelay|Milliseconds before the first poll for query execution status. See the section Waiting for Query Completion and Retrying Failed Queries to learn more.|1000|integer|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|maxAttempts|Maximum number of times to attempt a query. Set to 1 to disable retries. See the section Waiting for Query Completion and Retrying Failed Queries to learn more.|1|integer|
+|maxResults|Max number of results to return for the given operation (if supported by the Athena API endpoint). If not set, will use the Athena API default for the given operation.||integer|
+|nextToken|Pagination token to use in the case where the response from the previous request was truncated.||string|
+|operation|The Athena API function to call.|startQueryExecution|object|
+|outputLocation|The location in Amazon S3 where query results are stored, such as s3://path/to/query/bucket/. Ensure this value ends with a forward slash.||string|
+|outputType|How query results should be returned. One of StreamList (default - return a GetQueryResultsIterable that can page through all results), SelectList (returns at most 1000 rows at a time, plus a NextToken value as a header than can be used for manual pagination of results), S3Pointer (return an S3 path pointing to the results).|StreamList|object|
+|queryExecutionId|The unique ID identifying the query execution.||string|
+|queryString|The SQL query to run. Except for simple queries, prefer setting this as the body of the Exchange or as a header using Athena2Constants.QUERY\_STRING to avoid having to deal with URL encoding issues.||string|
+|region|The region in which Athena client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1).||string|
+|resetWaitTimeoutOnRetry|Reset the waitTimeout countdown in the event of a query retry. If set to true, potential max time spent waiting for queries is equal to waitTimeout x maxAttempts. See the section Waiting for Query Completion and Retrying Failed Queries to learn more.|true|boolean|
+|retry|Optional comma separated list of error types to retry the query for. Use: 'retryable' to retry all retryable failure conditions (e.g. generic errors and resources exhausted), 'generic' to retry 'GENERIC\_INTERNAL\_ERROR' failures, 'exhausted' to retry queries that have exhausted resource limits, 'always' to always retry regardless of failure condition, or 'never' or null to never retry (default). See the section Waiting for Query Completion and Retrying Failed Queries to learn more.|never|string|
+|waitTimeout|Optional max wait time in millis to wait for a successful query completion. See the section Waiting for Query Completion and Retrying Failed Queries to learn more.|0|integer|
+|workGroup|The workgroup to use for running the query.||string|
+|amazonAthenaClient|The AmazonAthena instance to use as the client.||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|clientRequestToken|A unique string to ensure issues queries are idempotent. It is unlikely you will need to set this.||string|
+|includeTrace|Include useful trace information at the beginning of queries as an SQL comment (prefixed with --).|false|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Athena client.||string|
+|proxyPort|To define a proxy port when instantiating the Athena client.||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Athena client.|HTTPS|object|
+|accessKey|Amazon AWS Access Key.||string|
+|encryptionOption|The encryption type to use when storing query results in S3. One of SSE\_S3, SSE\_KMS, or CSE\_KMS.||object|
+|kmsKey|For SSE-KMS and CSE-KMS, this is the KMS key ARN or ID.||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key.||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|useDefaultCredentialsProvider|Set whether the Athena client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in|false|boolean|
+|useProfileCredentialsProvider|Set whether the Athena client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Athena client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume a IAM role for doing operations in Athena.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|database|The Athena database to use.||string|
+|delay|Milliseconds before the next poll for query execution status. See the section Waiting for Query Completion and Retrying Failed Queries to learn more.|2000|integer|
+|initialDelay|Milliseconds before the first poll for query execution status. See the section Waiting for Query Completion and Retrying Failed Queries to learn more.|1000|integer|
+|maxAttempts|Maximum number of times to attempt a query. Set to 1 to disable retries. See the section Waiting for Query Completion and Retrying Failed Queries to learn more.|1|integer|
+|maxResults|Max number of results to return for the given operation (if supported by the Athena API endpoint). If not set, will use the Athena API default for the given operation.||integer|
+|nextToken|Pagination token to use in the case where the response from the previous request was truncated.||string|
+|operation|The Athena API function to call.|startQueryExecution|object|
+|outputLocation|The location in Amazon S3 where query results are stored, such as s3://path/to/query/bucket/. Ensure this value ends with a forward slash.||string|
+|outputType|How query results should be returned. One of StreamList (default - return a GetQueryResultsIterable that can page through all results), SelectList (returns at most 1000 rows at a time, plus a NextToken value as a header than can be used for manual pagination of results), S3Pointer (return an S3 path pointing to the results).|StreamList|object|
+|queryExecutionId|The unique ID identifying the query execution.||string|
+|queryString|The SQL query to run. Except for simple queries, prefer setting this as the body of the Exchange or as a header using Athena2Constants.QUERY\_STRING to avoid having to deal with URL encoding issues.||string|
+|region|The region in which Athena client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1).||string|
+|resetWaitTimeoutOnRetry|Reset the waitTimeout countdown in the event of a query retry. If set to true, potential max time spent waiting for queries is equal to waitTimeout x maxAttempts. See the section Waiting for Query Completion and Retrying Failed Queries to learn more.|true|boolean|
+|retry|Optional comma separated list of error types to retry the query for. Use: 'retryable' to retry all retryable failure conditions (e.g. generic errors and resources exhausted), 'generic' to retry 'GENERIC\_INTERNAL\_ERROR' failures, 'exhausted' to retry queries that have exhausted resource limits, 'always' to always retry regardless of failure condition, or 'never' or null to never retry (default). See the section Waiting for Query Completion and Retrying Failed Queries to learn more.|never|string|
+|waitTimeout|Optional max wait time in millis to wait for a successful query completion. See the section Waiting for Query Completion and Retrying Failed Queries to learn more.|0|integer|
+|workGroup|The workgroup to use for running the query.||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|amazonAthenaClient|The AmazonAthena instance to use as the client.||object|
+|clientRequestToken|A unique string to ensure issues queries are idempotent. It is unlikely you will need to set this.||string|
+|includeTrace|Include useful trace information at the beginning of queries as an SQL comment (prefixed with --).|false|boolean|
+|proxyHost|To define a proxy host when instantiating the Athena client.||string|
+|proxyPort|To define a proxy port when instantiating the Athena client.||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Athena client.|HTTPS|object|
+|accessKey|Amazon AWS Access Key.||string|
+|encryptionOption|The encryption type to use when storing query results in S3. One of SSE\_S3, SSE\_KMS, or CSE\_KMS.||object|
+|kmsKey|For SSE-KMS and CSE-KMS, this is the KMS key ARN or ID.||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key.||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|useDefaultCredentialsProvider|Set whether the Athena client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in|false|boolean|
+|useProfileCredentialsProvider|Set whether the Athena client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Athena client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume a IAM role for doing operations in Athena.|false|boolean|

camel-aws2-cw.md

@@ -0,0 +1,163 @@
+# Aws2-cw
+
+**Since Camel 3.1**
+
+**Only producer is supported**
+
+The AWS2 Cloudwatch component allows messages to be sent to an [Amazon
+CloudWatch](https://aws.amazon.com/cloudwatch/) metrics. The
+implementation of the Amazon API is provided by the [AWS
+SDK](https://aws.amazon.com/sdkforjava/).
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon CloudWatch. More information is available at
+[Amazon CloudWatch](https://aws.amazon.com/cloudwatch/).
+
+# URI Format
+
+    aws2-cw://namespace[?options]
+
+The metrics will be created if they don’t already exist.
+
+You can append query options to the URI in the following format:
+`?options=value&option2=value&...`
+
+Required CW component options
+
+You have to provide the amazonCwClient in the Registry or your accessKey
+and secretKey to access the [Amazon’s
+CloudWatch](https://aws.amazon.com/cloudwatch/).
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Advanced CloudWatchClient configuration
+
+If you need more control over the `CloudWatchClient` instance
+configuration you can create your own instance and refer to it from the
+URI:
+
+    from("direct:start")
+    .to("aws2-cw://namespace?amazonCwClient=#client");
+
+The `#client` refers to a `CloudWatchClient` in the Registry.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-cw</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version`} must be replaced by the actual version of
+Camel.
+
+# Examples
+
+## Producer Example
+
+    from("direct:start")
+      .to("aws2-cw://http://camel.apache.org/aws-cw");
+
+and sends something like
+
+    exchange.getIn().setHeader(Cw2Constants.METRIC_NAME, "ExchangesCompleted");
+    exchange.getIn().setHeader(Cw2Constants.METRIC_VALUE, "2.0");
+    exchange.getIn().setHeader(Cw2Constants.METRIC_UNIT, "Count");
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|The component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|name|The metric name||string|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|region|The region in which CW client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|timestamp|The metric timestamp||object|
+|unit|The metric unit||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|value|The metric value||number|
+|amazonCwClient|To use the AmazonCloudWatch as the client||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the CW client||string|
+|proxyPort|To define a proxy port when instantiating the CW client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the CW client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the S3 client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Cloudwatch client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the CloudWatch client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in CloudWatch.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|namespace|The metric namespace||string|
+|name|The metric name||string|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|region|The region in which CW client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|timestamp|The metric timestamp||object|
+|unit|The metric unit||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|value|The metric value||number|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|amazonCwClient|To use the AmazonCloudWatch as the client||object|
+|proxyHost|To define a proxy host when instantiating the CW client||string|
+|proxyPort|To define a proxy port when instantiating the CW client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the CW client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the S3 client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Cloudwatch client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the CloudWatch client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in CloudWatch.|false|boolean|

camel-aws2-ddb.md

@@ -0,0 +1,263 @@
+# Aws2-ddb
+
+**Since Camel 3.1**
+
+**Only producer is supported**
+
+The AWS2 DynamoDB component supports storing and retrieving data from/to
+[Amazon’s DynamoDB](https://aws.amazon.com/dynamodb) service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon DynamoDB. More information is available at
+[Amazon DynamoDB](https://aws.amazon.com/dynamodb).
+
+# URI Format
+
+    aws2-ddb://domainName[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required DDB component options
+
+You have to provide the amazonDDBClient in the Registry or your
+accessKey and secretKey to access the [Amazon’s
+DynamoDB](https://aws.amazon.com/dynamodb).
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Advanced AmazonDynamoDB configuration
+
+If you need more control over the `AmazonDynamoDB` instance
+configuration you can create your own instance and refer to it from the
+URI:
+
+    public class MyRouteBuilder extends RouteBuilder {
+    
+        private String accessKey = "myaccessKey";
+        private String secretKey = "secretKey";
+    
+        @Override
+        public void configure() throws Exception {
+    
+            DynamoDbClient client = DynamoDbClient.builder()
+            .region(Region.AP_SOUTHEAST_2)
+            .credentialsProvider(StaticCredentialsProvider.create(AwsBasicCredentials.create(accessKey, secretKey)))
+            .build();
+    
+            getCamelContext().getRegistry().bind("client", client);
+    
+            from("direct:start")
+            .to("aws2-ddb://domainName?amazonDDBClient=#client");
+        }
+    }
+
+The `#client` refers to a `DynamoDbClient` in the Registry.
+
+# Supported producer operations
+
+-   BatchGetItems
+
+-   DeleteItem
+
+-   DeleteTable
+
+-   DescribeTable
+
+-   GetItem
+
+-   PutItem
+
+-   Query
+
+-   Scan
+
+-   UpdateItem
+
+-   UpdateTable
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-ddb</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+# Examples
+
+## Producer Examples
+
+-   PutItem: this operation will create an entry into DynamoDB
+
+<!-- -->
+
+    Map<String, AttributeValue> attributeMap = new HashMap<>();
+    attributeMap.put("partitionKey", AttributeValue.builder().s("3000").build());
+    attributeMap.put("id", AttributeValue.builder().s("1001").build());
+    attributeMap.put("barcode", AttributeValue.builder().s("9002811220001").build());
+    
+    from("direct:start")
+      .setHeader(Ddb2Constants.OPERATION,  constant(Ddb2Operations.PutItem))
+      .setHeader(Ddb2Constants.CONSISTENT_READ, constant("true"))
+      .setHeader(Ddb2Constants.RETURN_VALUES, constant("ALL_OLD"))
+      .setHeader(Ddb2Constants.ITEM, constant(attributeMap))
+      .setHeader(Ddb2Constants.ATTRIBUTE_NAMES, constant(attributeMap.keySet()))
+      .to("aws2-ddb://" + tableName + "?amazonDDBClient=#client");
+
+-   UpdateItem: this operation will update an entry into DynamoDB
+
+<!-- -->
+
+    Map<String, AttributeValueUpdate> attributeMap = new HashMap<>();
+    attributeMap.put("partitionKey", AttributeValueUpdate.builder().value(AttributeValue.builder().s("3000").build()).build());
+    attributeMap.put("sortKey",  AttributeValueUpdate.builder().value(AttributeValue.builder().s("1001").build()).build());
+    attributeMap.put("borcode",  AttributeValueUpdate.builder().value(AttributeValue.builder().s("900281122").build()).build());
+    
+    Map<String, AttributeValue> keyMap = new HashMap<>();
+    keyMap.put("partitionKey", AttributeValue.builder().s("3000").build());
+    keyMap.put("sortKey", AttributeValue.builder().s("1001").build());
+    
+    from("direct:start")
+      .setHeader(Ddb2Constants.OPERATION,  constant(Ddb2Operations.UpdateItem))
+      .setHeader(Ddb2Constants.UPDATE_VALUES,  constant(attributeMap))
+      .setHeader(Ddb2Constants.KEY,  constant(keyMap))
+      .to("aws2-ddb://" + tableName + "?amazonDDBClient=#client");
+
+-   GetItem: this operation will retrieve an entry from DynamoDB
+
+<!-- -->
+
+    from("direct:get")
+      .process(exchange -> {
+          final Map<String, AttributeValue> keyMap = new HashMap<>();
+          keyMap.put("table-key", AttributeValue.builder().s("1").build());
+    
+          exchange.getIn().setHeader(Ddb2Constants.OPERATION, Ddb2Operations.GetItem);
+          exchange.getIn().setHeader(Ddb2Constants.ATTRIBUTE_NAMES, constant(List.of("table-key", "message")));
+          exchange.getIn().setHeader(Ddb2Constants.KEY, keyMap);
+      })
+      .toF("aws2-ddb://%s?amazonDDBClient=#client&consistentRead=true", tableName);
+
+-   DeleteItem: this operation will delete an entry from DynamoDB
+
+<!-- -->
+
+    from("direct:delete")
+      .process(exchange -> {
+          final Map<String, AttributeValue> keyMap = new HashMap<>();
+          keyMap.put("table-key", AttributeValue.builder().s("1").build());
+    
+          exchange.getIn().setHeader(Ddb2Constants.OPERATION, Ddb2Operations.DeleteItem);
+          exchange.getIn().setHeader(Ddb2Constants.KEY, keyMap);
+      })
+      .toF("aws2-ddb://%s?amazonDDBClient=#client&consistentRead=true", tableName);
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|The component configuration||object|
+|consistentRead|Determines whether strong consistency should be enforced when data is read.|false|boolean|
+|enabledInitialDescribeTable|Set whether the initial Describe table operation in the DDB Endpoint must be done, or not.|true|boolean|
+|keyAttributeName|Attribute name when creating table||string|
+|keyAttributeType|Attribute type when creating table||string|
+|keyScalarType|The key scalar type, it can be S (String), N (Number) and B (Bytes)||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|What operation to perform|PutItem|object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with uriEndpointOverride option|false|boolean|
+|readCapacity|The provisioned throughput to reserve for reading resources from your table||integer|
+|region|The region in which DDB client needs to work||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|writeCapacity|The provisioned throughput to reserved for writing resources to your table||integer|
+|amazonDDBClient|To use the AmazonDynamoDB as the client||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the DDB client||string|
+|proxyPort|The region in which DynamoDB client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the DDB client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume a IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the S3 client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the DDB client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the DDB client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in DDB.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|tableName|The name of the table currently worked with.||string|
+|consistentRead|Determines whether strong consistency should be enforced when data is read.|false|boolean|
+|enabledInitialDescribeTable|Set whether the initial Describe table operation in the DDB Endpoint must be done, or not.|true|boolean|
+|keyAttributeName|Attribute name when creating table||string|
+|keyAttributeType|Attribute type when creating table||string|
+|keyScalarType|The key scalar type, it can be S (String), N (Number) and B (Bytes)||string|
+|operation|What operation to perform|PutItem|object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with uriEndpointOverride option|false|boolean|
+|readCapacity|The provisioned throughput to reserve for reading resources from your table||integer|
+|region|The region in which DDB client needs to work||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|writeCapacity|The provisioned throughput to reserved for writing resources to your table||integer|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|amazonDDBClient|To use the AmazonDynamoDB as the client||object|
+|proxyHost|To define a proxy host when instantiating the DDB client||string|
+|proxyPort|The region in which DynamoDB client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the DDB client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume a IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the S3 client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the DDB client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the DDB client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in DDB.|false|boolean|

camel-aws2-ddbstream.md

@@ -0,0 +1,181 @@
+# Aws2-ddbstream
+
+**Since Camel 3.1**
+
+**Only consumer is supported**
+
+The AWS2 DynamoDB Stream component supports receiving messages from
+Amazon DynamoDB Stream service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon DynamoDB Streams. More information are available
+at [AWS DynamoDB](https://aws.amazon.com/dynamodb/)
+
+# URI Format
+
+    aws2-ddbstream://table-name[?options]
+
+The stream needs to be created prior to it being used.  
+You can append query options to the URI in the following format,
+?options=value\&option2=value\&…
+
+Required DynamoDBStream component options
+
+You have to provide the DynamoDbStreamsClient in the Registry with
+proxies and relevant credentials configured.
+
+# Sequence Numbers
+
+You can provide a literal string as the sequence number or provide a
+bean in the registry. An example of using the bean would be to save your
+current position in the change feed and restore it on Camel startup.
+
+It is an error to provide a sequence number that is greater than the
+largest sequence number in the describe-streams result, as this will
+lead to the AWS call returning an HTTP 400.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials, by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - aws.accessKeyId and aws.secretKey
+
+-   Environment variables - AWS\_ACCESS\_KEY\_ID and
+    AWS\_SECRET\_ACCESS\_KEY.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable AWS\_CONTAINER\_CREDENTIALS\_RELATIVE\_URI is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+# Coping with Downtime
+
+## AWS DynamoDB Streams outage of less than 24 hours
+
+The consumer will resume from the last seen sequence number (as
+implemented for
+[CAMEL-9515](https://issues.apache.org/jira/browse/CAMEL-9515)), so you
+should receive a flood of events in quick succession, as long as the
+outage did not also include DynamoDB itself.
+
+## AWS DynamoDB Streams outage of more than 24 hours
+
+Given that AWS only retain 24 hours worth of changes, you will have
+missed change events no matter what mitigations are in place.
+
+## Message Body
+
+The Message body is instance of
+"software.amazon.awssdk.services.dynamodb.model.Record", for more
+information about it, have a look at the [related
+javadoc](https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/services/dynamodb/model/Record.html)
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-ddb</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|configuration|The component configuration||object|
+|maxResultsPerRequest|Maximum number of records that will be fetched in each poll||integer|
+|overrideEndpoint|Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option|false|boolean|
+|region|The region in which DDBStreams client needs to work||string|
+|streamIteratorType|Defines where in the DynamoDB stream to start getting records. Note that using FROM\_START can cause a significant delay before the stream has caught up to real-time.|FROM\_LATEST|object|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|amazonDynamoDbStreamsClient|Amazon DynamoDB client to use for all requests for this endpoint||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the DDBStreams client||string|
+|proxyPort|To define a proxy port when instantiating the DDBStreams client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the DDBStreams client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name.||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume a IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the DynamoDB Streams client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Cloudtrail client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the DDB Streams client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in DDB.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|tableName|Name of the dynamodb table||string|
+|maxResultsPerRequest|Maximum number of records that will be fetched in each poll||integer|
+|overrideEndpoint|Set the need for overidding the endpoint. This option needs to be used in combination with uriEndpointOverride option|false|boolean|
+|region|The region in which DDBStreams client needs to work||string|
+|sendEmptyMessageWhenIdle|If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.|false|boolean|
+|streamIteratorType|Defines where in the DynamoDB stream to start getting records. Note that using FROM\_START can cause a significant delay before the stream has caught up to real-time.|FROM\_LATEST|object|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|amazonDynamoDbStreamsClient|Amazon DynamoDB client to use for all requests for this endpoint||object|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|pollStrategy|A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.||object|
+|proxyHost|To define a proxy host when instantiating the DDBStreams client||string|
+|proxyPort|To define a proxy port when instantiating the DDBStreams client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the DDBStreams client|HTTPS|object|
+|backoffErrorThreshold|The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.||integer|
+|backoffIdleThreshold|The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.||integer|
+|backoffMultiplier|To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.||integer|
+|delay|Milliseconds before the next poll.|500|integer|
+|greedy|If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.|false|boolean|
+|initialDelay|Milliseconds before the first poll starts.|1000|integer|
+|repeatCount|Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.|0|integer|
+|runLoggingLevel|The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.|TRACE|object|
+|scheduledExecutorService|Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.||object|
+|scheduler|To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler|none|object|
+|schedulerProperties|To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.||object|
+|startScheduler|Whether the scheduler should be auto started.|true|boolean|
+|timeUnit|Time unit for initialDelay and delay options.|MILLISECONDS|object|
+|useFixedDelay|Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.|true|boolean|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name.||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume a IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the DynamoDB Streams client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Cloudtrail client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the DDB Streams client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in DDB.|false|boolean|

camel-aws2-ec2.md

@@ -0,0 +1,232 @@
+# Aws2-ec2
+
+**Since Camel 3.1**
+
+**Only producer is supported**
+
+The AWS2 EC2 component supports the ability to create, run, start, stop
+and terminate [AWS EC2](https://aws.amazon.com/ec2/) instances.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon EC2. More information is available at [Amazon
+EC2](https://aws.amazon.com/ec2/).
+
+# URI Format
+
+    aws2-ec2://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required EC2 component options
+
+You have to provide the amazonEc2Client in the Registry or your
+accessKey and secretKey to access the [Amazon
+EC2](https://aws.amazon.com/ec2/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+# Supported producer operations
+
+-   createAndRunInstances
+
+-   startInstances
+
+-   stopInstances
+
+-   terminateInstances
+
+-   describeInstances
+
+-   describeInstancesStatus
+
+-   rebootInstances
+
+-   monitorInstances
+
+-   unmonitorInstances
+
+-   createTags
+
+-   deleteTags
+
+# Examples
+
+## Producer Examples
+
+-   createAndRunInstances: this operation will create an EC2 instance
+    and run it
+
+<!-- -->
+
+    from("direct:createAndRun")
+         .setHeader(EC2Constants.IMAGE_ID, constant("ami-fd65ba94"))
+         .setHeader(EC2Constants.INSTANCE_TYPE, constant(InstanceType.T2Micro))
+         .setHeader(EC2Constants.INSTANCE_MIN_COUNT, constant("1"))
+         .setHeader(EC2Constants.INSTANCE_MAX_COUNT, constant("1"))
+         .to("aws2-ec2://TestDomain?accessKey=xxxx&secretKey=xxxx&operation=createAndRunInstances");
+
+-   startInstances: this operation will start a list of EC2 instances
+
+<!-- -->
+
+    from("direct:start")
+         .process(new Processor() {
+                @Override
+                public void process(Exchange exchange) throws Exception {
+                    Collection<String> l = new ArrayList<>();
+                    l.add("myinstance");
+                    exchange.getIn().setHeader(AWS2EC2Constants.INSTANCES_IDS, l);
+                }
+            })
+         .to("aws2-ec2://TestDomain?accessKey=xxxx&secretKey=xxxx&operation=startInstances");
+
+-   stopInstances: this operation will stop a list of EC2 instances
+
+<!-- -->
+
+    from("direct:stop")
+         .process(new Processor() {
+                @Override
+                public void process(Exchange exchange) throws Exception {
+                    Collection<String> l = new ArrayList<>();
+                    l.add("myinstance");
+                    exchange.getIn().setHeader(AWS2EC2Constants.INSTANCES_IDS, l);
+                }
+            })
+         .to("aws2-ec2://TestDomain?accessKey=xxxx&secretKey=xxxx&operation=stopInstances");
+
+-   terminateInstances: this operation will terminate a list of EC2
+    instances
+
+<!-- -->
+
+    from("direct:stop")
+         .process(new Processor() {
+                @Override
+                public void process(Exchange exchange) throws Exception {
+                    Collection<String> l = new ArrayList<>();
+                    l.add("myinstance");
+                    exchange.getIn().setHeader(AWS2EC2Constants.INSTANCES_IDS, l);
+                }
+            })
+         .to("aws2-ec2://TestDomain?accessKey=xxxx&secretKey=xxxx&operation=terminateInstances");
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as a body. In AWS
+EC2 there are multiple operations you can submit, as an example for
+Create and run an instance, you can do something like:
+
+    from("direct:start")
+      .setBody(RunInstancesRequest.builder().imageId("test-1").instanceType(InstanceType.T2_MICRO).build())
+      .to("aws2-ec2://TestDomain?accessKey=xxxx&secretKey=xxxx&operation=createAndRunInstances&pojoRequest=true");
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-ec2</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|amazonEc2Client|To use an existing configured AmazonEC2Client client||object|
+|configuration|The component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which EC2 client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the EC2 client||string|
+|proxyPort|To define a proxy port when instantiating the EC2 client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the EC2 client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the EC2 client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the EC2 client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the EC2 client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in EC2.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|amazonEc2Client|To use an existing configured AmazonEC2Client client||object|
+|operation|The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which EC2 client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|proxyHost|To define a proxy host when instantiating the EC2 client||string|
+|proxyPort|To define a proxy port when instantiating the EC2 client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the EC2 client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the EC2 client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the EC2 client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the EC2 client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in EC2.|false|boolean|

camel-aws2-ecs.md

@@ -0,0 +1,168 @@
+# Aws2-ecs
+
+**Since Camel 3.1**
+
+**Only producer is supported**
+
+The AWS2 ECS component supports create, delete, describe and list
+clusters [AWS ECS](https://aws.amazon.com/ecs/) clusters instances.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon ECS. More information is available at [Amazon
+ECS](https://aws.amazon.com/ecs/).
+
+# URI Format
+
+    aws2-ecs://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required ECS component options
+
+You have to provide the amazonECSClient in the Registry or your
+accessKey and secretKey to access the [Amazon
+ECS](https://aws.amazon.com/ecs/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## ECS Producer operations
+
+Camel-AWS ECS component provides the following operation on the producer
+side:
+
+-   listClusters
+
+-   createCluster
+
+-   describeCluster
+
+-   deleteCluster
+
+# Producer Examples
+
+-   listClusters: this operation will list the available clusters in ECS
+
+<!-- -->
+
+    from("direct:listClusters")
+        .to("aws2-ecs://test?ecsClient=#amazonEcsClient&operation=listClusters")
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as a body. In AWS
+ECS there are multiple operations you can submit, as an example for List
+cluster request, you can do something like:
+
+    from("direct:start")
+      .setBody(ListClustersRequest.builder().maxResults(10).build())
+      .to("aws2-ecs://test?ecsClient=#amazonEcsClient&operation=listClusters&pojoRequest=true")
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-ecs</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the ECS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|ecsClient|To use an existing configured AWS ECS client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the ECS client||string|
+|proxyPort|To define a proxy port when instantiating the ECS client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the ECS client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the ECS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the ECS client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the ECS client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in ECS.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the ECS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|ecsClient|To use an existing configured AWS ECS client||object|
+|proxyHost|To define a proxy host when instantiating the ECS client||string|
+|proxyPort|To define a proxy port when instantiating the ECS client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the ECS client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the ECS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the ECS client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the ECS client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in ECS.|false|boolean|

camel-aws2-eks.md

@@ -0,0 +1,168 @@
+# Aws2-eks
+
+**Since Camel 3.1**
+
+**Only producer is supported**
+
+The AWS2 EKS component supports create, delete, describe and list
+clusters [AWS EKS](https://aws.amazon.com/eks/) clusters instances.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon EKS. More information is available at [Amazon
+EKS](https://aws.amazon.com/eks/).
+
+# URI Format
+
+    aws2-eks://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required EKS component options
+
+You have to provide the amazonEKSClient in the Registry or your
+accessKey and secretKey to access the [Amazon
+EKS](https://aws.amazon.com/eks/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## EKS Producer operations
+
+Camel-AWS EKS component provides the following operation on the producer
+side:
+
+-   listClusters
+
+-   createCluster
+
+-   describeCluster
+
+-   deleteCluster
+
+# Producer Examples
+
+-   listClusters: this operation will list the available clusters in EKS
+
+<!-- -->
+
+    from("direct:listClusters")
+        .to("aws2-eks://test?eksClient=#amazonEksClient&operation=listClusters")
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as a body. In AWS
+EKS there are multiple operations you can submit, as an example for List
+cluster request, you can do something like:
+
+    from("direct:start")
+      .setBody(ListClustersRequest.builder().maxResults(12).build())
+      .to("aws2-eks://test?eksClient=#amazonEksClient&operation=listClusters&pojoRequest=true")
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-eks</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name|false|string|
+|region|The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the EKS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the EKS client should expect to load credentials through a profile credentials provider.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|eksClient|To use an existing configured AWS EKS client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the EKS client||string|
+|proxyPort|To define a proxy port when instantiating the EKS client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the EKS client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useSessionCredentials|Set whether the EKS client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in EKS.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name|false|string|
+|region|The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the EKS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the EKS client should expect to load credentials through a profile credentials provider.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|eksClient|To use an existing configured AWS EKS client||object|
+|proxyHost|To define a proxy host when instantiating the EKS client||string|
+|proxyPort|To define a proxy port when instantiating the EKS client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the EKS client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useSessionCredentials|Set whether the EKS client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in EKS.|false|boolean|

camel-aws2-eventbridge.md

@@ -0,0 +1,365 @@
+# Aws2-eventbridge
+
+**Since Camel 3.6**
+
+**Only producer is supported**
+
+The AWS2 Eventbridge component supports assumeRole operation. [AWS
+Eventbridge](https://aws.amazon.com/eventbridge/).
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Eventbridge. More information is available at
+[Amazon Eventbridge](https://aws.amazon.com/eventbridge/).
+
+To create a rule that triggers on an action by an AWS service that does
+not emit events, you can base the rule on API calls made by that
+service. The API calls are recorded by AWS CloudTrail, so you’ll need to
+have CloudTrail enabled. For more information, check [Services Supported
+by CloudTrail Event
+History](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/view-cloudtrail-events.html).
+
+# URI Format
+
+    aws2-eventbridge://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## AWS2-Eventbridge Producer operations
+
+Camel-AWS2-Eventbridge component provides the following operation on the
+producer side:
+
+-   putRule
+
+-   putTargets
+
+-   removeTargets
+
+-   deleteRule
+
+-   enableRule
+
+-   disableRule
+
+-   listRules
+
+-   describeRule
+
+-   listTargetsByRule
+
+-   listRuleNamesByTarget
+
+-   putEvent
+
+-   PutRule: this operation creates a rule related to an eventbus
+
+<!-- -->
+
+      from("direct:putRule").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
+          }
+      })
+      .to("aws2-eventbridge://test?operation=putRule&eventPatternFile=file:src/test/resources/eventpattern.json")
+      .to("mock:result");
+
+This operation will create a rule named *firstrule*, and it will use a
+json file for defining the EventPattern.
+
+-   PutTargets: this operation will add a target to the rule
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
+              Target target = Target.builder().id("sqs-queue").arn("arn:aws:sqs:eu-west-1:780410022472:camel-connector-test")
+                    .build();
+              List<Target> targets = new ArrayList<Target>();
+              targets.add(target);
+              exchange.getIn().setHeader(EventbridgeConstants.TARGETS, targets);
+          }
+      })
+      .to("aws2-eventbridge://test?operation=putTargets")
+      .to("mock:result");
+
+This operation will add the target sqs-queue with the arn reported to
+the targets of the *firstrule* rule.
+
+-   RemoveTargets: this operation will remove a collection of targets
+    from the rule
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
+              List<String> ids = new ArrayList<String>();
+              targets.add("sqs-queue");
+              exchange.getIn().setHeader(EventbridgeConstants.TARGETS_IDS, targets);
+          }
+      })
+      .to("aws2-eventbridge://test?operation=removeTargets")
+      .to("mock:result");
+
+This operation will remove the target sqs-queue from the *firstrule*
+rule.
+
+-   DeleteRule: this operation will delete a rule related to an eventbus
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
+          }
+      })
+      .to("aws2-eventbridge://test?operation=deleteRule")
+      .to("mock:result");
+
+This operation will remove the *firstrule* rule from the test eventbus.
+
+-   EnableRule: this operation will enable a rule related to an eventbus
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
+          }
+      })
+      .to("aws2-eventbridge://test?operation=enableRule")
+      .to("mock:result");
+
+This operation will enable the *firstrule* rule from the test eventbus.
+
+-   DisableRule: this operation will disable a rule related to an
+    eventbus
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
+          }
+      })
+      .to("aws2-eventbridge://test?operation=disableRule")
+      .to("mock:result");
+
+This operation will disable the *firstrule* rule from the test eventbus.
+
+-   ListRules: this operation will list all the rules related to an
+    eventbus with prefix first
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME_PREFIX, "first");
+          }
+      })
+      .to("aws2-eventbridge://test?operation=listRules")
+      .to("mock:result");
+
+This operation will list all the rules with prefix first from the test
+eventbus.
+
+-   DescribeRule: this operation will describe a specified rule related
+    to an eventbus
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
+          }
+      })
+      .to("aws2-eventbridge://test?operation=describeRule")
+      .to("mock:result");
+
+This operation will describe the *firstrule* rule from the test
+eventbus.
+
+-   ListTargetsByRule: this operation will return a list of targets
+    associated with a rule
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(EventbridgeConstants.RULE_NAME, "firstrule");
+          }
+      })
+      .to("aws2-eventbridge://test?operation=listTargetsByRule")
+      .to("mock:result");
+
+this operation will return a list of targets associated with the
+*firstrule* rule.
+
+-   ListRuleNamesByTarget: this operation will return a list of rules
+    associated with a target
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(EventbridgeConstants.TARGET_ARN, "firstrule");
+          }
+      })
+      .to("aws2-eventbridge://test?operation=listRuleNamesByTarget")
+      .to("mock:result");
+
+this operation will return a list of rules associated with a target.
+
+-   PutEvent: this operation will send an event to the Servicebus
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+                    exchange.getIn().setHeader(EventbridgeConstants.EVENT_RESOURCES_ARN, "arn:aws:sqs:eu-west-1:780410022472:camel-connector-test");
+                    exchange.getIn().setHeader(EventbridgeConstants.EVENT_SOURCE, "com.pippo");
+                    exchange.getIn().setHeader(EventbridgeConstants.EVENT_DETAIL_TYPE, "peppe");
+                    exchange.getIn().setBody("Test Event");
+          }
+      })
+      .to("aws2-eventbridge://test?operation=putEvent")
+      .to("mock:result");
+
+this operation will return a list of entries with related ID sent to
+servicebus.
+
+# Updating the rule
+
+To update a rule, you’ll need to perform the putRule operation again.
+There is no explicit update rule operation in the Java SDK.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-eventbridge</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|eventPatternFile|EventPattern File||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform|putRule|object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the Eventbridge client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|eventbridgeClient|To use an existing configured AWS Eventbridge client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Eventbridge client||string|
+|proxyPort|To define a proxy port when instantiating the Eventbridge client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Eventbridge client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Eventbridge client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Eventbridge client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Eventbridge client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Eventbridge.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|eventbusNameOrArn|Event bus name or ARN||string|
+|eventPatternFile|EventPattern File||string|
+|operation|The operation to perform|putRule|object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the Eventbridge client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|eventbridgeClient|To use an existing configured AWS Eventbridge client||object|
+|proxyHost|To define a proxy host when instantiating the Eventbridge client||string|
+|proxyPort|To define a proxy port when instantiating the Eventbridge client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Eventbridge client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Eventbridge client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Eventbridge client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Eventbridge client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Eventbridge.|false|boolean|

camel-aws2-iam.md

@@ -0,0 +1,228 @@
+# Aws2-iam
+
+**Since Camel 3.1**
+
+**Only producer is supported**
+
+The AWS2 IAM component supports create, run, start, stop and terminate
+[AWS IAM](https://aws.amazon.com/iam/) instances.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon IAM. More information is available at [Amazon
+IAM](https://aws.amazon.com/iam/).
+
+# URI Format
+
+    aws2-iam://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+The AWS2 IAM component works on the aws-global region, and it has
+aws-global as the default region
+
+Required IAM component options
+
+You have to provide the amazonKmsClient in the Registry or your
+accessKey and secretKey to access the [Amazon
+IAM](https://aws.amazon.com/iam/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## IAM Producer operations
+
+Camel-AWS2 IAM component provides the following operation on the
+producer side:
+
+-   listAccessKeys
+
+-   createUser
+
+-   deleteUser
+
+-   listUsers
+
+-   getUser
+
+-   createAccessKey
+
+-   deleteAccessKey
+
+-   updateAccessKey
+
+-   createGroup
+
+-   deleteGroup
+
+-   listGroups
+
+-   addUserToGroup
+
+-   removeUserFromGroup
+
+# Producer Examples
+
+-   createUser: this operation will create a user in IAM
+
+<!-- -->
+
+    from("direct:createUser")
+        .setHeader(IAM2Constants.USERNAME, constant("camel"))
+        .to("aws2-iam://test?iamClient=#amazonIAMClient&operation=createUser")
+
+-   deleteUser: this operation will delete a user in IAM
+
+<!-- -->
+
+    from("direct:deleteUser")
+        .setHeader(IAM2Constants.USERNAME, constant("camel"))
+        .to("aws2-iam://test?iamClient=#amazonIAMClient&operation=deleteUser")
+
+-   listUsers: this operation will list the users in IAM
+
+<!-- -->
+
+    from("direct:listUsers")
+        .to("aws2-iam://test?iamClient=#amazonIAMClient&operation=listUsers")
+
+-   createGroup: this operation will add a group in IAM
+
+<!-- -->
+
+    from("direct:deleteUser")
+        .setHeader(IAM2Constants.GROUP_NAME, constant("camel"))
+        .to("aws2-iam://test?iamClient=#amazonIAMClient&operation=createGroup")
+
+-   deleteGroup: this operation will delete a group in IAM
+
+<!-- -->
+
+    from("direct:deleteUser")
+        .setHeader(IAM2Constants.GROUP_NAME, constant("camel"))
+        .to("aws2-iam://test?iamClient=#amazonIAMClient&operation=deleteGroup")
+
+-   listGroups: this operation will list the groups in IAM
+
+<!-- -->
+
+    from("direct:listUsers")
+        .to("aws2-iam://test?iamClient=#amazonIAMClient&operation=listGroups")
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as a body. In AWS
+IAM, there are multiple operations you can submit, as an example for
+Create User request, you can do something like:
+
+    from("direct:createUser")
+         .setBody(CreateUserRequest.builder().userName("camel").build())
+        .to("aws2-iam://test?iamClient=#amazonIAMClient&operation=createUser&pojoRequest=true")
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-iam</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|iamClient|To use an existing configured AWS IAM client||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform. You can configure a default operation on the component level, or the operation as part of the endpoint, or via a message header with the key CamelAwsIAMOperation.||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which IAM client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()|aws-global|string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the IAM client||string|
+|proxyPort|To define a proxy port when instantiating the IAM client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the IAM client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the IAM client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the IAM client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the IAM client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume a IAM role for doing operations in IAM.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|iamClient|To use an existing configured AWS IAM client||object|
+|operation|The operation to perform. You can configure a default operation on the component level, or the operation as part of the endpoint, or via a message header with the key CamelAwsIAMOperation.||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which IAM client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()|aws-global|string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|proxyHost|To define a proxy host when instantiating the IAM client||string|
+|proxyPort|To define a proxy port when instantiating the IAM client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the IAM client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the IAM client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the IAM client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the IAM client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume a IAM role for doing operations in IAM.|false|boolean|

camel-aws2-kinesis-firehose.md

@@ -0,0 +1,192 @@
+# Aws2-kinesis-firehose
+
+**Since Camel 3.2**
+
+**Only producer is supported**
+
+The AWS2 Kinesis Firehose component supports sending messages to Amazon
+Kinesis Firehose service (Batch not supported).
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Kinesis Firehose. More information is available
+at [AWS Kinesis Firehose](https://aws.amazon.com/kinesis/firehose/)
+
+The AWS2 Kinesis Firehose component is not supported in OSGI
+
+# URI Format
+
+    aws2-kinesis-firehose://delivery-stream-name[?options]
+
+The stream needs to be created prior to it being used.
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+# URI Options
+
+Required Kinesis Firehose component options
+
+You have to provide the FirehoseClient in the Registry with proxies and
+relevant credentials configured.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Amazon Kinesis Firehose configuration
+
+You then have to reference the FirehoseClient in the
+`amazonKinesisFirehoseClient` URI option.
+
+    from("aws2-kinesis-firehose://mykinesisdeliverystream?amazonKinesisFirehoseClient=#kinesisClient")
+      .to("log:out?showAll=true");
+
+## Providing AWS Credentials
+
+It is recommended that the credentials are obtained by using the
+[DefaultAWSCredentialsProviderChain](http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/DefaultAWSCredentialsProviderChain.html)
+that is the default when creating a new ClientConfiguration instance,
+however, a different
+[AWSCredentialsProvider](http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/AWSCredentialsProvider.html)
+can be specified when calling createClient(…).
+
+## Kinesis Firehose Producer operations
+
+Camel-AWS s3 component provides the following operation on the producer
+side:
+
+-   SendBatchRecord
+
+-   CreateDeliveryStream
+
+-   DeleteDeliveryStream
+
+-   DescribeDeliveryStream
+
+-   UpdateDestination
+
+## Send Batch Records Example
+
+You can send an iterable of Kinesis Record (as the following example
+shows), or you can send directly a PutRecordBatchRequest POJO instance
+in the body.
+
+        @Test
+        public void testFirehoseBatchRouting() throws Exception {
+            Exchange exchange = template.send("direct:start", ExchangePattern.InOnly, new Processor() {
+                public void process(Exchange exchange) throws Exception {
+                    List<Record> recs = new ArrayList<Record>();
+                    Record rec = Record.builder().data(SdkBytes.fromString("Test1", Charset.defaultCharset())).build();
+                    Record rec1 = Record.builder().data(SdkBytes.fromString("Test2", Charset.defaultCharset())).build();
+                    recs.add(rec);
+                    recs.add(rec1);
+                    exchange.getIn().setBody(recs);
+                }
+            });
+            assertNotNull(exchange.getIn().getBody());
+        }
+    
+    from("direct:start").to("aws2-kinesis-firehose://cc?amazonKinesisFirehoseClient=#FirehoseClient&operation=sendBatchRecord");
+
+In the deliveryStream you’ll find "Test1Test2".
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-kinesis</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|cborEnabled|This option will set the CBOR\_ENABLED property during the execution|true|boolean|
+|configuration|Component configuration||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with uriEndpointOverride option|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to do in case the user don't want to send only a record||object|
+|region|The region in which Kinesis Firehose client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the Kinesis Firehose client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|amazonKinesisFirehoseClient|Amazon Kinesis Firehose client to use for all requests for this endpoint||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Kinesis Firehose client||string|
+|proxyPort|To define a proxy port when instantiating the Kinesis Firehose client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Kinesis Firehose client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name.||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume a IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useProfileCredentialsProvider|Set whether the Kinesis Firehose client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Kinesis Firehose client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in Kinesis Firehose.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|streamName|Name of the stream||string|
+|cborEnabled|This option will set the CBOR\_ENABLED property during the execution|true|boolean|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with uriEndpointOverride option|false|boolean|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|operation|The operation to do in case the user don't want to send only a record||object|
+|region|The region in which Kinesis Firehose client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|useDefaultCredentialsProvider|Set whether the Kinesis Firehose client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|amazonKinesisFirehoseClient|Amazon Kinesis Firehose client to use for all requests for this endpoint||object|
+|proxyHost|To define a proxy host when instantiating the Kinesis Firehose client||string|
+|proxyPort|To define a proxy port when instantiating the Kinesis Firehose client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Kinesis Firehose client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name.||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume a IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useProfileCredentialsProvider|Set whether the Kinesis Firehose client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Kinesis Firehose client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in Kinesis Firehose.|false|boolean|

camel-aws2-kinesis.md

@@ -0,0 +1,242 @@
+# Aws2-kinesis
+
+**Since Camel 3.2**
+
+**Both producer and consumer are supported**
+
+The AWS2 Kinesis component supports consuming messages from and
+producing messages to Amazon Kinesis service.
+
+The AWS2 Kinesis component also supports Synchronous and Asynchronous
+Client, which means you choose what fits best your requirements, so if
+you need the connection (client) to be async, there’s a property of
+*asyncClient* (in DSL also can be found) needs to be turned true.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Kinesis. More information is available at [AWS
+Kinesis](https://aws.amazon.com/kinesis/)
+
+# URI Format
+
+    aws2-kinesis://stream-name[?options]
+
+The stream needs to be created prior to it being used.
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required Kinesis component options
+
+You have to provide the KinesisClient in the Registry with proxies and
+relevant credentials configured.
+
+# Batch Consumer
+
+This component implements the Batch Consumer.
+
+This allows you, for instance, to know how many messages exist in this
+batch and for instance, let the Aggregator aggregate this number of
+messages.
+
+The consumer is able to consume either from a single specific shard or
+all available shards (multiple shards consumption) of Amazon Kinesis,
+therefore, if you leave the *shardId* property in the DSL configuration
+empty, then it’ll consume all available shards otherwise only the
+specified shard corresponding to the shardId will be consumed.
+
+# Batch Producer
+
+This component implements the Batch Producer.
+
+This allows you to send multiple messages in a single request to Amazon
+Kinesis. Messages with batch size more than 500 is allowed. Producer
+will split them into multiple requests.
+
+The batch type needs to implement the `Iterable` interface. For example,
+it can be a `List`, `Set` or any other collection type. The message type
+can be one or more of types `byte[]`, `ByteBuffer`, UTF-8 `String`, or
+`InputStream`. Other types are not supported.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## AmazonKinesis configuration
+
+You then have to reference the KinesisClient in the
+`amazonKinesisClient` URI option.
+
+    from("aws2-kinesis://mykinesisstream?amazonKinesisClient=#kinesisClient")
+      .to("log:out?showAll=true");
+
+## Providing AWS Credentials
+
+It is recommended that the credentials are obtained by using the
+[DefaultAWSCredentialsProviderChain](http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/DefaultAWSCredentialsProviderChain.html)
+that is the default when creating a new ClientConfiguration instance,
+however, a different
+[AWSCredentialsProvider](http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/AWSCredentialsProvider.html)
+can be specified when calling createClient(…).
+
+## AWS Kinesis KCL Consumer
+
+The component supports also the KCL (Kinesis Client Library) for
+consuming from a Kinesis Data Stream.
+
+To enable this feature you’ll need to set two different parameter in
+your endpoint:
+
+    from("aws2-kinesis://mykinesisstream?asyncClient=true&useDefaultCredentialsProvider=true&useKclConsumers=true")
+      .to("log:out?showAll=true");
+
+This feature will make possible to automatically checkpointing the Shard
+Iterations by combining the usage of KCL, DynamoDB Table and CloudWatch
+alarms.
+
+Everything will work out of the box, by simply using your AWS
+Credentials.
+
+In the beginning the consumer will require 60/70 seconds for preparing
+everything, listing the shards, creating/querying the Lease table on
+Dynamo DB. Keep it in mind while working with the KCL consumer.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-kinesis</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|cborEnabled|This option will set the CBOR\_ENABLED property during the execution|true|boolean|
+|configuration|Component configuration||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with uriEndpointOverride option|false|boolean|
+|region|The region in which Kinesis Firehose client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|iteratorType|Defines where in the Kinesis stream to start getting records|TRIM\_HORIZON|object|
+|maxResultsPerRequest|Maximum number of records that will be fetched in each poll|1|integer|
+|sequenceNumber|The sequence number to start polling from. Required if iteratorType is set to AFTER\_SEQUENCE\_NUMBER or AT\_SEQUENCE\_NUMBER||string|
+|shardClosed|Define what will be the behavior in case of shard closed. Possible value are ignore, silent and fail. In case of ignore a message will be logged and the consumer will restart from the beginning,in case of silent there will be no logging and the consumer will start from the beginning,in case of fail a ReachedClosedStateException will be raised|ignore|object|
+|shardId|Defines which shardId in the Kinesis stream to get records from||string|
+|shardMonitorInterval|The interval in milliseconds to wait between shard polling|10000|integer|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|amazonKinesisClient|Amazon Kinesis client to use for all requests for this endpoint||object|
+|asyncClient|If we want to a KinesisAsyncClient instance set it to true|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|cloudWatchAsyncClient|If we want to a KCL Consumer, we can pass an instance of CloudWatchAsyncClient||object|
+|dynamoDbAsyncClient|If we want to a KCL Consumer, we can pass an instance of DynamoDbAsyncClient||object|
+|useKclConsumers|If we want to a KCL Consumer set it to true|false|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Kinesis client||string|
+|proxyPort|To define a proxy port when instantiating the Kinesis client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Kinesis client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name.||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume a IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Kinesis client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Kinesis client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Kinesis client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in Kinesis.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|streamName|Name of the stream||string|
+|cborEnabled|This option will set the CBOR\_ENABLED property during the execution|true|boolean|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with uriEndpointOverride option|false|boolean|
+|region|The region in which Kinesis Firehose client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|iteratorType|Defines where in the Kinesis stream to start getting records|TRIM\_HORIZON|object|
+|maxResultsPerRequest|Maximum number of records that will be fetched in each poll|1|integer|
+|sendEmptyMessageWhenIdle|If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.|false|boolean|
+|sequenceNumber|The sequence number to start polling from. Required if iteratorType is set to AFTER\_SEQUENCE\_NUMBER or AT\_SEQUENCE\_NUMBER||string|
+|shardClosed|Define what will be the behavior in case of shard closed. Possible value are ignore, silent and fail. In case of ignore a message will be logged and the consumer will restart from the beginning,in case of silent there will be no logging and the consumer will start from the beginning,in case of fail a ReachedClosedStateException will be raised|ignore|object|
+|shardId|Defines which shardId in the Kinesis stream to get records from||string|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|pollStrategy|A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.||object|
+|shardMonitorInterval|The interval in milliseconds to wait between shard polling|10000|integer|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|amazonKinesisClient|Amazon Kinesis client to use for all requests for this endpoint||object|
+|asyncClient|If we want to a KinesisAsyncClient instance set it to true|false|boolean|
+|cloudWatchAsyncClient|If we want to a KCL Consumer, we can pass an instance of CloudWatchAsyncClient||object|
+|dynamoDbAsyncClient|If we want to a KCL Consumer, we can pass an instance of DynamoDbAsyncClient||object|
+|useKclConsumers|If we want to a KCL Consumer set it to true|false|boolean|
+|proxyHost|To define a proxy host when instantiating the Kinesis client||string|
+|proxyPort|To define a proxy port when instantiating the Kinesis client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Kinesis client|HTTPS|object|
+|backoffErrorThreshold|The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.||integer|
+|backoffIdleThreshold|The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.||integer|
+|backoffMultiplier|To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.||integer|
+|delay|Milliseconds before the next poll.|500|integer|
+|greedy|If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.|false|boolean|
+|initialDelay|Milliseconds before the first poll starts.|1000|integer|
+|repeatCount|Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.|0|integer|
+|runLoggingLevel|The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.|TRACE|object|
+|scheduledExecutorService|Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.||object|
+|scheduler|To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler|none|object|
+|schedulerProperties|To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.||object|
+|startScheduler|Whether the scheduler should be auto started.|true|boolean|
+|timeUnit|Time unit for initialDelay and delay options.|MILLISECONDS|object|
+|useFixedDelay|Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.|true|boolean|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider this parameter will set the profile name.||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume a IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Kinesis client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Kinesis client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Kinesis client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in Kinesis.|false|boolean|

camel-aws2-kms.md

@@ -0,0 +1,193 @@
+# Aws2-kms
+
+**Since Camel 3.1**
+
+**Only producer is supported**
+
+The AWS2 KMS component supports the ability to work with keys stored in
+[AWS KMS](https://aws.amazon.com/kms/) instances.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon KMS. More information is available at [Amazon
+KMS](https://aws.amazon.com/kms/).
+
+# URI Format
+
+    aws2-kms://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required KMS component options
+
+You have to provide the amazonKmsClient in the Registry or your
+accessKey and secretKey to access the [Amazon
+KMS](https://aws.amazon.com/kms/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## KMS Producer operations
+
+Camel-AWS KMS component provides the following operation on the producer
+side:
+
+-   listKeys
+
+-   createKey
+
+-   disableKey
+
+-   scheduleKeyDeletion
+
+-   describeKey
+
+-   enableKey
+
+# Producer Examples
+
+-   listKeys: this operation will list the available keys in KMS
+
+<!-- -->
+
+    from("direct:listKeys")
+          .to("aws2-kms://test?kmsClient=#amazonKmsClient&operation=listKeys")
+
+-   createKey: this operation will create a key in KMS
+
+<!-- -->
+
+    from("direct:createKey")
+          .to("aws2-kms://test?kmsClient=#amazonKmsClient&operation=createKey")
+
+-   disableKey: this operation will disable a key in KMS
+
+<!-- -->
+
+    from("direct:disableKey")
+          .setHeader(KMS2Constants.KEY_ID, constant("123")
+          .to("aws2-kms://test?kmsClient=#amazonKmsClient&operation=disableKey")
+
+-   enableKey: this operation will enable a key in KMS
+
+<!-- -->
+
+    from("direct:enableKey")
+          .setHeader(KMS2Constants.KEY_ID, constant("123")
+          .to("aws2-kms://test?kmsClient=#amazonKmsClient&operation=enableKey")
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as the body. In AWS
+KMS there are multiple operations you can submit, as an example for List
+keys request, you can do something like:
+
+    from("direct:createUser")
+         .setBody(ListKeysRequest.builder().limit(10).build())
+         .to("aws2-kms://test?kmsClient=#amazonKmsClient&operation=listKeys&pojoRequest=true")
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-kms</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|kmsClient|To use an existing configured AWS KMS client||object|
+|proxyHost|To define a proxy host when instantiating the KMS client||string|
+|proxyPort|To define a proxy port when instantiating the KMS client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the KMS client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the KMS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the KMS client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the KMS client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume a IAM role for doing operations in KMS.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|kmsClient|To use an existing configured AWS KMS client||object|
+|proxyHost|To define a proxy host when instantiating the KMS client||string|
+|proxyPort|To define a proxy port when instantiating the KMS client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the KMS client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the KMS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the KMS client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the KMS client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume a IAM role for doing operations in KMS.|false|boolean|

camel-aws2-lambda.md

@@ -0,0 +1,225 @@
+# Aws2-lambda
+
+**Since Camel 3.2**
+
+**Only producer is supported**
+
+The AWS2 Lambda component supports create, get, list, delete, and invoke
+[AWS Lambda](https://aws.amazon.com/lambda/) functions.
+
+**Prerequisites**
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Lambda. More information is available at [AWS
+Lambda](https://aws.amazon.com/lambda/).
+
+When creating a Lambda function, you need to specify an IAM role which
+has at least the AWSLambdaBasicExecuteRole policy attached.
+
+# URI Format
+
+    aws2-lambda://functionName[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required Lambda component options
+
+You have to provide the awsLambdaClient in the Registry or your
+accessKey and secretKey to access the [Amazon
+Lambda](https://aws.amazon.com/lambda/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+# List of Available Operations
+
+-   listFunctions
+
+-   getFunction
+
+-   createFunction
+
+-   deleteFunction
+
+-   invokeFunction
+
+-   updateFunction
+
+-   createEventSourceMapping
+
+-   deleteEventSourceMapping
+
+-   listEventSourceMapping
+
+-   listTags
+
+-   tagResource
+
+-   untagResource
+
+-   publishVersion
+
+-   listVersions
+
+-   createAlias
+
+-   deleteAlias
+
+-   getAlias
+
+-   listAliases
+
+# Examples
+
+## Producer Example
+
+To have a full understanding of how the component works, you may have a
+look at these [integration
+tests](https://github.com/apache/camel/tree/main/components/camel-aws/camel-aws2-lambda/src/test/java/org/apache/camel/component/aws2/lambda/integration)
+
+## Producer Examples
+
+-   CreateFunction: this operation will create a function for you in AWS
+    Lambda
+
+<!-- -->
+
+      from("direct:createFunction").to("aws2-lambda://GetHelloWithName?operation=createFunction").to("mock:result");
+
+and by sending
+
+            template.send("direct:createFunction", ExchangePattern.InOut, new Processor() {
+                @Override
+                public void process(Exchange exchange) throws Exception {
+                    exchange.getIn().setHeader(Lambda2Constants.RUNTIME, "nodejs6.10");
+                    exchange.getIn().setHeader(Lambda2Constants.HANDLER, "GetHelloWithName.handler");
+                    exchange.getIn().setHeader(Lambda2Constants.DESCRIPTION, "Hello with node.js on Lambda");
+                    exchange.getIn().setHeader(Lambda2Constants.ROLE,
+                            "arn:aws:iam::643534317684:role/lambda-execution-role");
+    
+                    ClassLoader classLoader = getClass().getClassLoader();
+                    File file = new File(
+                            classLoader
+                                    .getResource("org/apache/camel/component/aws2/lambda/function/node/GetHelloWithName.zip")
+                                    .getFile());
+                    FileInputStream inputStream = new FileInputStream(file);
+                    exchange.getIn().setBody(inputStream);
+                }
+            });
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as the body. In AWS
+Lambda there are multiple operations you can submit, as an example for
+Get Function request, you can do something like:
+
+    from("direct:getFunction")
+         .setBody(GetFunctionRequest.builder().functionName("test").build())
+         .to("aws2-lambda://GetHelloWithName?awsLambdaClient=#awsLambdaClient&operation=getFunction&pojoRequest=true")
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-lambda</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction|invokeFunction|object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the Lambda client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|awsLambdaClient|To use an existing configured AwsLambdaClient client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Lambda client||string|
+|proxyPort|To define a proxy port when instantiating the Lambda client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Lambda client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Lambda client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Lambda client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Lambda client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Lambda.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|function|Name of the Lambda function.||string|
+|operation|The operation to perform. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction|invokeFunction|object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the Lambda client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|awsLambdaClient|To use an existing configured AwsLambdaClient client||object|
+|proxyHost|To define a proxy host when instantiating the Lambda client||string|
+|proxyPort|To define a proxy port when instantiating the Lambda client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Lambda client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Lambda client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Lambda client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Lambda client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Lambda.|false|boolean|

camel-aws2-mq.md

@@ -0,0 +1,216 @@
+# Aws2-mq
+
+**Since Camel 3.1**
+
+**Only producer is supported**
+
+The AWS2 MQ component supports create, run, start, stop and terminate
+[AWS MQ](https://aws.amazon.com/amazon-mq/) instances.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon MQ. More information is available at [Amazon
+MQ](https://aws.amazon.com/amazon-mq/).
+
+# URI Format
+
+    aws2-mq://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required MQ component options
+
+You have to provide the amazonMqClient in the Registry or your accessKey
+and secretKey to access the [Amazon
+MQ](https://aws.amazon.com/amazon-mq/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## MQ Producer operations
+
+Camel-AWS MQ component provides the following operation on the producer
+side:
+
+-   listBrokers
+
+-   createBroker
+
+-   deleteBroker
+
+-   rebootBroker
+
+-   updateBroker
+
+-   describeBroker
+
+# Examples
+
+## Producer Examples
+
+-   listBrokers: this operation will list the available MQ Brokers in
+    AWS
+
+<!-- -->
+
+    from("direct:listBrokers")
+        .to("aws2-mq://test?amazonMqClient=#amazonMqClient&operation=listBrokers")
+
+-   createBroker: this operation will create an MQ Broker in AWS
+
+<!-- -->
+
+    from("direct:createBroker")
+        .process(new Processor() {
+           @Override
+           public void process(Exchange exchange) throws Exception {
+                    exchange.getIn().setHeader(MQ2Constants.BROKER_NAME, "test");
+                    exchange.getIn().setHeader(MQ2Constants.BROKER_DEPLOYMENT_MODE, DeploymentMode.SINGLE_INSTANCE);
+                    exchange.getIn().setHeader(MQ2Constants.BROKER_INSTANCE_TYPE, "mq.t2.micro");
+                    exchange.getIn().setHeader(MQ2Constants.BROKER_ENGINE, EngineType.ACTIVEMQ.name());
+                    exchange.getIn().setHeader(MQ2Constants.BROKER_ENGINE_VERSION, "5.15.6");
+                    exchange.getIn().setHeader(MQ2Constants.BROKER_PUBLICLY_ACCESSIBLE, false);
+                    List<User> users = new ArrayList<>();
+                    User.Builder user = User.builder();
+                    user.username("camel");
+                    user.password("camelpwd");
+                    users.add(user.build());
+                    exchange.getIn().setHeader(MQ2Constants.BROKER_USERS, users);
+    
+           }
+        })
+        .to("aws2-mq://test?amazonMqClient=#amazonMqClient&operation=createBroker")
+
+-   deleteBroker: this operation will delete an MQ Broker in AWS
+
+<!-- -->
+
+    from("direct:listBrokers")
+        .setHeader(MQ2Constants.BROKER_ID, constant("123")
+        .to("aws2-mq://test?amazonMqClient=#amazonMqClient&operation=deleteBroker")
+
+-   rebootBroker: this operation will delete an MQ Broker in AWS
+
+<!-- -->
+
+    from("direct:listBrokers")
+        .setHeader(MQ2Constants.BROKER_ID, constant("123")
+        .to("aws2-mq://test?amazonMqClient=#amazonMqClient&operation=rebootBroker")
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as the body. In AWS
+MQ, there are multiple operations you can submit, as an example for List
+brokers request, you can do something like:
+
+    from("direct:aws2-mq")
+         .setBody(ListBrokersRequest.builder().maxResults(10).build())
+         .to("aws2-mq://test?amazonMqClient=#amazonMqClient&operation=listBrokers&pojoRequest=true")
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-mq</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform. It can be listBrokers, createBroker, deleteBroker||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which MQ client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|amazonMqClient|To use a existing configured AmazonMQClient client||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the MQ client||string|
+|proxyPort|To define a proxy port when instantiating the MQ client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the MQ client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the MQ client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the MQ client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the MQ client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in MQ.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|operation|The operation to perform. It can be listBrokers, createBroker, deleteBroker||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which MQ client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|amazonMqClient|To use a existing configured AmazonMQClient client||object|
+|proxyHost|To define a proxy host when instantiating the MQ client||string|
+|proxyPort|To define a proxy port when instantiating the MQ client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the MQ client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the MQ client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the MQ client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the MQ client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in MQ.|false|boolean|

camel-aws2-msk.md

@@ -0,0 +1,199 @@
+# Aws2-msk
+
+**Since Camel 3.1**
+
+**Only producer is supported**
+
+The AWS2 MSK component supports create, run, start, stop and terminate
+[AWS MSK](https://aws.amazon.com/msk/) instances.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon MSK. More information is available at [Amazon
+MSK](https://aws.amazon.com/msk/).
+
+# URI Format
+
+    aws2-msk://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required MSK component options
+
+You have to provide the amazonMskClient in the Registry or your
+accessKey and secretKey to access the [Amazon
+MSK](https://aws.amazon.com/msk/) service.
+
+# Usage
+
+## Static credentials vs Default Credential Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## MSK Producer operations
+
+Camel-AWS MSK component provides the following operation on the producer
+side:
+
+-   listClusters
+
+-   createCluster
+
+-   deleteCluster
+
+-   describeCluster
+
+# Examples
+
+## Producer Examples
+
+-   listClusters: this operation will list the available MSK Brokers in
+    AWS
+
+<!-- -->
+
+    from("direct:listClusters")
+        .to("aws2-msk://test?mskClient=#amazonMskClient&operation=listClusters")
+
+-   createCluster: this operation will create an MSK Cluster in AWS
+
+<!-- -->
+
+    from("direct:createCluster")
+        .process(new Processor() {
+           @Override
+           public void process(Exchange exchange) throws Exception {
+                    exchange.getIn().setHeader(MSK2Constants.CLUSTER_NAME, "test-kafka");
+                    exchange.getIn().setHeader(MSK2Constants.CLUSTER_KAFKA_VERSION, "2.1.1");
+                    exchange.getIn().setHeader(MSK2Constants.BROKER_NODES_NUMBER, 2);
+                    BrokerNodeGroupInfo groupInfo = BrokerNodeGroupInfo.builder().build();
+                    exchange.getIn().setHeader(MSK2Constants.BROKER_NODES_GROUP_INFO, groupInfo);
+           }
+        })
+        .to("aws2-msk://test?mskClient=#amazonMskClient&operation=createCluster")
+
+-   deleteCluster: this operation will delete an MSK Cluster in AWS
+
+<!-- -->
+
+    from("direct:deleteCluster")
+        .setHeader(MSK2Constants.CLUSTER_ARN, constant("test-kafka"));
+        .to("aws2-msk://test?mskClient=#amazonMskClient&operation=deleteCluster")
+    
+    from("direct:createCluster")
+        .process(new Processor() {
+           @Override
+           public void process(Exchange exchange) throws Exception {
+                    exchange.getIn().setHeader(MSK2Constants.CLUSTER_NAME, "test-kafka");
+                    exchange.getIn().setHeader(MSK2Constants.CLUSTER_KAFKA_VERSION, "2.1.1");
+                    exchange.getIn().setHeader(MSK2Constants.BROKER_NODES_NUMBER, 2);
+                    BrokerNodeGroupInfo groupInfo = BrokerNodeGroupInfo.builder().build();
+                    exchange.getIn().setHeader(MSK2Constants.BROKER_NODES_GROUP_INFO, groupInfo);
+           }
+        })
+        .to("aws2-msk://test?mskClient=#amazonMskClient&operation=deleteCluster")
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as the body. In AWS
+MSK, there are multiple operations you can submit, as an example for
+List clusters request, you can do something like:
+
+    from("direct:aws2-msk")
+         .setBody(ListClustersRequest.builder().maxResults(10).build())
+         .to("aws2-msk://test?mskClient=#amazonMskClient&operation=listClusters&pojoRequest=true")
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-msk</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the MSK client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|mskClient|To use an existing configured AWS MSK client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the MSK client||string|
+|proxyPort|To define a proxy port when instantiating the MSK client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the MSK client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Kafka client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the MSK client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the MSK client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in MSK.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|operation|The operation to perform||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the MSK client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|mskClient|To use an existing configured AWS MSK client||object|
+|proxyHost|To define a proxy host when instantiating the MSK client||string|
+|proxyPort|To define a proxy port when instantiating the MSK client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the MSK client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Kafka client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the MSK client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the MSK client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in MSK.|false|boolean|

camel-aws2-redshift-data.md

@@ -0,0 +1,184 @@
+# Aws2-redshift-data
+
+**Since Camel 4.1**
+
+**Only producer is supported**
+
+The AWS2 Redshift Data component supports the following operations on
+[AWS Redshift](https://aws.amazon.com/redshift/):
+
+-   listDatabases, listSchemas, listStatements, listTables,
+    describeTable, executeStatement, batchExecuteStatement,
+    cancelStatement, describeStatement, getStatementResult
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Redshift. More information is available at [AWS
+Redshift](https://aws.amazon.com/redshift/).
+
+# URI Format
+
+    aws2-redshift-data://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required Redshift Data component options
+
+You have to provide the awsRedshiftDataClient in the Registry or your
+accessKey and secretKey to access the [AWS
+Redshift](https://aws.amazon.com/redshift/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Redshift Producer operations
+
+Camel-AWS Redshift Data component provides the following operation on
+the producer side:
+
+-   listDatabases
+
+-   listSchemas
+
+-   listStatements
+
+-   listTables
+
+-   describeTable
+
+-   executeStatement
+
+-   batchExecuteStatement
+
+-   cancelStatement
+
+-   describeStatement
+
+-   getStatementResult
+
+# Producer Examples
+
+-   listDatabases: this operation will list redshift databases
+
+<!-- -->
+
+    from("direct:listDatabases")
+        .to("aws2-redshift-data://test?awsRedshiftDataClient=#awsRedshiftDataClient&operation=listDatabases")
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as body. In AWS
+Redshift Data there are multiple operations you can submit, as an
+example for List Databases request, you can do something like:
+
+    from("direct:start")
+      .setBody(ListDatabases.builder().database("database1").build())
+      .to("aws2-redshift-data://test?awsRedshiftDataClient=#awsRedshiftDataClient&operation=listDatabases&pojoRequest=true")
+
+In this way you’ll pass the request directly without the need of passing
+headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-redshift-data</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform. It can be batchExecuteStatement, cancelStatement, describeStatement, describeTable, executeStatement, getStatementResult, listDatabases, listSchemas, listStatements or listTables||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|region|The region in which RedshiftData client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the RedshiftData client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the RedshiftData client should expect to load credentials through a profile credentials provider.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|awsRedshiftDataClient|To use an existing configured AwsRedshiftDataClient client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the RedshiftData client||string|
+|proxyPort|To define a proxy port when instantiating the RedshiftData client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the RedshiftData client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|useSessionCredentials|Set whether the Redshift client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Redshift.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|operation|The operation to perform. It can be batchExecuteStatement, cancelStatement, describeStatement, describeTable, executeStatement, getStatementResult, listDatabases, listSchemas, listStatements or listTables||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|region|The region in which RedshiftData client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the RedshiftData client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the RedshiftData client should expect to load credentials through a profile credentials provider.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|awsRedshiftDataClient|To use an existing configured AwsRedshiftDataClient client||object|
+|proxyHost|To define a proxy host when instantiating the RedshiftData client||string|
+|proxyPort|To define a proxy port when instantiating the RedshiftData client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the RedshiftData client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|useSessionCredentials|Set whether the Redshift client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Redshift.|false|boolean|

camel-aws2-s3.md

@@ -0,0 +1,644 @@
+# Aws2-s3
+
+**Since Camel 3.2**
+
+**Both producer and consumer are supported**
+
+The AWS2 S3 component supports storing and retrieving objects from/to
+[Amazon’s S3](https://aws.amazon.com/s3) service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon S3. More information is available at [Amazon
+S3](https://aws.amazon.com/s3).
+
+# URI Format
+
+    aws2-s3://bucketNameOrArn[?options]
+
+The bucket will be created if it doesn’t already exist.
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required S3 component options
+
+You have to provide the amazonS3Client in the Registry or your accessKey
+and secretKey to access the [Amazon’s S3](https://aws.amazon.com/s3).
+
+# Batch Consumer
+
+This component implements the Batch Consumer.
+
+This allows you, for instance, to know how many messages exist in this
+batch and for instance, let the Aggregator aggregate this number of
+messages.
+
+# Usage
+
+For example, to read file `hello.txt` from bucket `helloBucket`, use the
+following snippet:
+
+    from("aws2-s3://helloBucket?accessKey=yourAccessKey&secretKey=yourSecretKey&prefix=hello.txt")
+      .to("file:/var/downloaded");
+
+## S3 Producer operations
+
+Camel-AWS2-S3 component provides the following operation on the producer
+side:
+
+-   copyObject
+
+-   deleteObject
+
+-   listBuckets
+
+-   deleteBucket
+
+-   listObjects
+
+-   getObject (this will return an S3Object instance)
+
+-   getObjectRange (this will return an S3Object instance)
+
+-   createDownloadLink
+
+If you don’t specify an operation, explicitly the producer will do:
+
+-   a single file upload
+
+-   a multipart upload if multiPartUpload option is enabled
+
+## Advanced AmazonS3 configuration
+
+If your Camel Application is running behind a firewall or if you need to
+have more control over the `S3Client` instance configuration, you can
+create your own instance and refer to it in your Camel aws2-s3 component
+configuration:
+
+    from("aws2-s3://MyBucket?amazonS3Client=#client&delay=5000&maxMessagesPerPoll=5")
+    .to("mock:result");
+
+## Use KMS with the S3 component
+
+To use AWS KMS to encrypt/decrypt data by using AWS infrastructure, you
+can use the options introduced in 2.21.x like in the following example
+
+    from("file:tmp/test?fileName=test.txt")
+         .setHeader(AWS2S3Constants.KEY, constant("testFile"))
+         .to("aws2-s3://mybucket?amazonS3Client=#client&useAwsKMS=true&awsKMSKeyId=3f0637ad-296a-3dfe-a796-e60654fb128c");
+
+In this way, you’ll ask S3 to use the KMS key
+3f0637ad-296a-3dfe-a796-e60654fb128c, to encrypt the file test.txt. When
+you ask to download this file, the decryption will be done directly
+before the download.
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## S3 Producer Operation examples
+
+-   Single Upload: This operation will upload a file to S3 based on the
+    body content
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(AWS2S3Constants.KEY, "camel.txt");
+              exchange.getIn().setBody("Camel rocks!");
+          }
+      })
+      .to("aws2-s3://mycamelbucket?amazonS3Client=#amazonS3Client")
+      .to("mock:result");
+
+This operation will upload the file camel.txt with the content "Camel
+rocks!" in the *mycamelbucket* bucket
+
+-   Multipart Upload: This operation will perform a multipart upload of
+    a file to S3 based on the body content
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(AWS2S3Constants.KEY, "empty.txt");
+              exchange.getIn().setBody(new File("src/empty.txt"));
+          }
+      })
+      .to("aws2-s3://mycamelbucket?amazonS3Client=#amazonS3Client&multiPartUpload=true&autoCreateBucket=true&partSize=1048576")
+      .to("mock:result");
+
+This operation will perform a multipart upload of the file empty.txt
+with based on the content the file src/empty.txt in the *mycamelbucket*
+bucket
+
+-   CopyObject: this operation copies an object from one bucket to a
+    different one
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(AWS2S3Constants.BUCKET_DESTINATION_NAME, "camelDestinationBucket");
+              exchange.getIn().setHeader(AWS2S3Constants.KEY, "camelKey");
+              exchange.getIn().setHeader(AWS2S3Constants.DESTINATION_KEY, "camelDestinationKey");
+          }
+      })
+      .to("aws2-s3://mycamelbucket?amazonS3Client=#amazonS3Client&operation=copyObject")
+      .to("mock:result");
+
+This operation will copy the object with the name expressed in the
+header camelDestinationKey to the camelDestinationBucket bucket, from
+the bucket *mycamelbucket*.
+
+-   DeleteObject: this operation deletes an object from a bucket
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(AWS2S3Constants.KEY, "camelKey");
+          }
+      })
+      .to("aws2-s3://mycamelbucket?amazonS3Client=#amazonS3Client&operation=deleteObject")
+      .to("mock:result");
+
+This operation will delete the object camelKey from the bucket
+*mycamelbucket*.
+
+-   ListBuckets: this operation lists the buckets for this account in
+    this region
+
+<!-- -->
+
+      from("direct:start")
+      .to("aws2-s3://mycamelbucket?amazonS3Client=#amazonS3Client&operation=listBuckets")
+      .to("mock:result");
+
+This operation will list the buckets for this account
+
+-   DeleteBucket: this operation deletes the bucket specified as URI
+    parameter or header
+
+<!-- -->
+
+      from("direct:start")
+      .to("aws2-s3://mycamelbucket?amazonS3Client=#amazonS3Client&operation=deleteBucket")
+      .to("mock:result");
+
+This operation will delete the bucket *mycamelbucket*
+
+-   ListObjects: this operation list object in a specific bucket
+
+<!-- -->
+
+      from("direct:start")
+      .to("aws2-s3://mycamelbucket?amazonS3Client=#amazonS3Client&operation=listObjects")
+      .to("mock:result");
+
+This operation will list the objects in the *mycamelbucket* bucket
+
+-   GetObject: this operation gets a single object in a specific bucket
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(AWS2S3Constants.KEY, "camelKey");
+          }
+      })
+      .to("aws2-s3://mycamelbucket?amazonS3Client=#amazonS3Client&operation=getObject")
+      .to("mock:result");
+
+This operation will return an S3Object instance related to the camelKey
+object in *mycamelbucket* bucket.
+
+-   GetObjectRange: this operation gets a single object range in a
+    specific bucket
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(AWS2S3Constants.KEY, "camelKey");
+              exchange.getIn().setHeader(AWS2S3Constants.RANGE_START, "0");
+              exchange.getIn().setHeader(AWS2S3Constants.RANGE_END, "9");
+          }
+      })
+      .to("aws2-s3://mycamelbucket?amazonS3Client=#amazonS3Client&operation=getObjectRange")
+      .to("mock:result");
+
+This operation will return an S3Object instance related to the camelKey
+object in *mycamelbucket* bucket, containing the bytes from 0 to 9.
+
+-   CreateDownloadLink: this operation will return a download link
+    through S3 Presigner
+
+<!-- -->
+
+      from("direct:start").process(new Processor() {
+    
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              exchange.getIn().setHeader(AWS2S3Constants.KEY, "camelKey");
+          }
+      })
+      .to("aws2-s3://mycamelbucket?accessKey=xxx&secretKey=yyy&region=region&operation=createDownloadLink")
+      .to("mock:result");
+
+This operation will return a download link url for the file camel-key in
+the bucket *mycamelbucket* and region *region*. Parameters (`accessKey`,
+`secretKey` and `region`) are mandatory for this operation, if S3 client
+is autowired from the registry.
+
+If checksum validations are enabled, the url will no longer be browser
+compatible because it adds a signed header that must be included in the
+HTTP request.
+
+# Streaming Upload mode
+
+With the stream mode enabled, users will be able to upload data to S3
+without knowing ahead of time the dimension of the data, by leveraging
+multipart upload. The upload will be completed when the batchSize has
+been completed or the batchMessageNumber has been reached. There are two
+possible naming strategies: progressive and random. With the progressive
+strategy, each file will have the name composed by keyName option and a
+progressive counter, and eventually the file extension (if any), while
+with the random strategy a UUID will be added after keyName and
+eventually the file extension will be appended.
+
+As an example:
+
+    from(kafka("topic1").brokers("localhost:9092"))
+            .log("Kafka Message is: ${body}")
+            .to(aws2S3("camel-bucket").streamingUploadMode(true).batchMessageNumber(25).namingStrategy(AWS2S3EndpointBuilderFactory.AWSS3NamingStrategyEnum.progressive).keyName("{{kafkaTopic1}}/{{kafkaTopic1}}.txt"));
+    
+    from(kafka("topic2").brokers("localhost:9092"))
+             .log("Kafka Message is: ${body}")
+             .to(aws2S3("camel-bucket").streamingUploadMode(true).batchMessageNumber(25).namingStrategy(AWS2S3EndpointBuilderFactory.AWSS3NamingStrategyEnum.random).keyName("{{kafkaTopic2}}/{{kafkaTopic2}}.txt"));
+
+The default size for a batch is 1 Mb, but you can adjust it according to
+your requirements.
+
+When you stop your producer route, the producer will take care of
+flushing the remaining buffered message and complete the upload.
+
+In Streaming upload, you’ll be able to restart the producer from the
+point where it left. It’s important to note that this feature is
+critical only when using the progressive naming strategy.
+
+By setting the restartingPolicy to lastPart, you will restart uploading
+files and contents from the last part number the producer left.
+
+As example: - Start the route with progressive naming strategy and
+keyname equals to camel.txt, with batchMessageNumber equals to 20, and
+restartingPolicy equals to lastPart - Send 70 messages. - Stop the
+route - On your S3 bucket you should now see four files: camel.txt,
+camel-1.txt, camel-2.txt and camel-3.txt, the first three will have 20
+messages, while the last one is only 10. - Restart the route - Send 25
+messages - Stop the route - You’ll now have two other files in your
+bucket: camel-5.txt and camel-6.txt, the first with 20 messages and the
+second with 5 messages. - Go ahead
+
+This won’t be needed when using the random naming strategy.
+
+On the opposite, you can specify the override restartingPolicy. In that
+case, you’ll be able to override whatever you written before (for that
+particular keyName) in your bucket.
+
+In Streaming upload mode, the only keyName option that will be taken
+into account is the endpoint option. Using the header will throw an NPE
+and this is done by design. Setting the header means potentially change
+the file name on each exchange, and this is against the aim of the
+streaming upload producer. The keyName needs to be fixed and static. The
+selected naming strategy will do the rest of the work.
+
+Another possibility is specifying a streamingUploadTimeout with
+batchMessageNumber and batchSize options. With this option, the user
+will be able to complete the upload of a file after a certain time
+passed. In this way, the upload completion will be passed on three
+tiers: the timeout, the number of messages and the batch size.
+
+As an example:
+
+    from(kafka("topic1").brokers("localhost:9092"))
+            .log("Kafka Message is: ${body}")
+            .to(aws2S3("camel-bucket").streamingUploadMode(true).batchMessageNumber(25).streamingUploadTimeout(10000).namingStrategy(AWS2S3EndpointBuilderFactory.AWSS3NamingStrategyEnum.progressive).keyName("{{kafkaTopic1}}/{{kafkaTopic1}}.txt"));
+
+In this case, the upload will be completed after 10 seconds.
+
+# Bucket Auto-creation
+
+With the option `autoCreateBucket` users are able to avoid the
+auto-creation of an S3 Bucket in case it doesn’t exist. The default for
+this option is `false`. If set to false, any operation on a not-existent
+bucket in AWS won’t be successful and an error will be returned.
+
+# Moving stuff between a bucket and another bucket
+
+Some users like to consume stuff from a bucket and move the content in a
+different one without using the copyObject feature of this component. If
+this is case for you, remember to remove the bucketName header from the
+incoming exchange of the consumer, otherwise the file will always be
+overwritten on the same original bucket.
+
+# MoveAfterRead consumer option
+
+In addition to deleteAfterRead, it has been added another option,
+moveAfterRead. With this option enabled, the consumed object will be
+moved to a target destinationBucket instead of being only deleted. This
+will require specifying the destinationBucket option. As example:
+
+      from("aws2-s3://mycamelbucket?amazonS3Client=#amazonS3Client&moveAfterRead=true&destinationBucket=myothercamelbucket")
+      .to("mock:result");
+
+In this case, the objects consumed will be moved to *myothercamelbucket*
+bucket and deleted from the original one (because of deleteAfterRead set
+to true as default).
+
+You have also the possibility of using a key prefix/suffix while moving
+the file to a different bucket. The options are destinationBucketPrefix
+and destinationBucketSuffix.
+
+Taking the above example, you could do something like:
+
+      from("aws2-s3://mycamelbucket?amazonS3Client=#amazonS3Client&moveAfterRead=true&destinationBucket=myothercamelbucket&destinationBucketPrefix=RAW(pre-)&destinationBucketSuffix=RAW(-suff)")
+      .to("mock:result");
+
+In this case, the objects consumed will be moved to *myothercamelbucket*
+bucket and deleted from the original one (because of deleteAfterRead set
+to true as default).
+
+So if the file name is test, in the *myothercamelbucket* you should see
+a file called pre-test-suff.
+
+# Using customer key as encryption
+
+We introduced also the customer key support (an alternative of using
+KMS). The following code shows an example.
+
+    String key = UUID.randomUUID().toString();
+    byte[] secretKey = generateSecretKey();
+    String b64Key = Base64.getEncoder().encodeToString(secretKey);
+    String b64KeyMd5 = Md5Utils.md5AsBase64(secretKey);
+    
+    String awsEndpoint = "aws2-s3://mycamel?autoCreateBucket=false&useCustomerKey=true&customerKeyId=RAW(" + b64Key + ")&customerKeyMD5=RAW(" + b64KeyMd5 + ")&customerAlgorithm=" + AES256.name();
+    
+    from("direct:putObject")
+        .setHeader(AWS2S3Constants.KEY, constant("test.txt"))
+        .setBody(constant("Test"))
+        .to(awsEndpoint);
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as the body. In AWS
+S3 there are multiple operations you can submit, as an example for List
+brokers request, you can do something like:
+
+    from("direct:aws2-s3")
+         .setBody(ListObjectsRequest.builder().bucket(bucketName).build())
+         .to("aws2-s3://test?amazonS3Client=#amazonS3Client&operation=listObjects&pojoRequest=true")
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Create S3 client and add component to registry
+
+Sometimes you would want to perform some advanced configuration using
+AWS2S3Configuration, which also allows to set the S3 client. You can
+create and set the S3 client in the component configuration as shown in
+the following example
+
+    String awsBucketAccessKey = "your_access_key";
+    String awsBucketSecretKey = "your_secret_key";
+    
+    S3Client s3Client = S3Client.builder().credentialsProvider(StaticCredentialsProvider.create(AwsBasicCredentials.create(awsBucketAccessKey, awsBucketSecretKey)))
+                    .region(Region.US_EAST_1).build();
+    
+    AWS2S3Configuration configuration = new AWS2S3Configuration();
+    configuration.setAmazonS3Client(s3Client);
+    configuration.setAutoDiscoverClient(true);
+    configuration.setBucketName("s3bucket2020");
+    configuration.setRegion("us-east-1");
+
+Now you can configure the S3 component (using the configuration object
+created above) and add it to the registry in the configure method before
+initialization of routes.
+
+    AWS2S3Component s3Component = new AWS2S3Component(getContext());
+    s3Component.setConfiguration(configuration);
+    s3Component.setLazyStartProducer(true);
+    camelContext.addComponent("aws2-s3", s3Component);
+
+Now your component will be used for all the operations implemented in
+camel routes.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-s3</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|autoCreateBucket|Setting the autocreation of the S3 bucket bucketName. This will apply also in case of moveAfterRead option enabled, and it will create the destinationBucket if it doesn't exist already.|false|boolean|
+|configuration|The component configuration||object|
+|delimiter|The delimiter which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in.||string|
+|forcePathStyle|Set whether the S3 client should use path-style URL instead of virtual-hosted-style|false|boolean|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|policy|The policy for this queue to set in the com.amazonaws.services.s3.AmazonS3#setBucketPolicy() method.||string|
+|prefix|The prefix which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in.||string|
+|region|The region in which the S3 client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|customerAlgorithm|Define the customer algorithm to use in case CustomerKey is enabled||string|
+|customerKeyId|Define the id of the Customer key to use in case CustomerKey is enabled||string|
+|customerKeyMD5|Define the MD5 of Customer key to use in case CustomerKey is enabled||string|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|deleteAfterRead|Delete objects from S3 after they have been retrieved. The deleting is only performed if the Exchange is committed. If a rollback occurs, the object is not deleted. If this option is false, then the same objects will be retrieved over and over again in the polls. Therefore, you need to use the Idempotent Consumer EIP in the route to filter out duplicates. You can filter using the AWS2S3Constants#BUCKET\_NAME and AWS2S3Constants#KEY headers, or only the AWS2S3Constants#KEY header.|true|boolean|
+|destinationBucket|Define the destination bucket where an object must be moved when moveAfterRead is set to true.||string|
+|destinationBucketPrefix|Define the destination bucket prefix to use when an object must be moved, and moveAfterRead is set to true.||string|
+|destinationBucketSuffix|Define the destination bucket suffix to use when an object must be moved, and moveAfterRead is set to true.||string|
+|doneFileName|If provided, Camel will only consume files if a done file exists.||string|
+|fileName|To get the object from the bucket with the given file name||string|
+|ignoreBody|If it is true, the S3 Object Body will be ignored completely if it is set to false, the S3 Object will be put in the body. Setting this to true will override any behavior defined by includeBody option.|false|boolean|
+|includeBody|If it is true, the S3Object exchange will be consumed and put into the body and closed. If false, the S3Object stream will be put raw into the body and the headers will be set with the S3 object metadata. This option is strongly related to the autocloseBody option. In case of setting includeBody to true because the S3Object stream will be consumed then it will also be closed, while in case of includeBody false then it will be up to the caller to close the S3Object stream. However, setting autocloseBody to true when includeBody is false it will schedule to close the S3Object stream automatically on exchange completion.|true|boolean|
+|includeFolders|If it is true, the folders/directories will be consumed. If it is false, they will be ignored, and Exchanges will not be created for those|true|boolean|
+|moveAfterRead|Move objects from S3 bucket to a different bucket after they have been retrieved. To accomplish the operation, the destinationBucket option must be set. The copy bucket operation is only performed if the Exchange is committed. If a rollback occurs, the object is not moved.|false|boolean|
+|autocloseBody|If this option is true and includeBody is false, then the S3Object.close() method will be called on exchange completion. This option is strongly related to includeBody option. In case of setting includeBody to false and autocloseBody to false, it will be up to the caller to close the S3Object stream. Setting autocloseBody to true, will close the S3Object stream automatically.|true|boolean|
+|batchMessageNumber|The number of messages composing a batch in streaming upload mode|10|integer|
+|batchSize|The batch size (in bytes) in streaming upload mode|1000000|integer|
+|bufferSize|The buffer size (in bytes) in streaming upload mode|1000000|integer|
+|deleteAfterWrite|Delete file object after the S3 file has been uploaded|false|boolean|
+|keyName|Setting the key name for an element in the bucket through endpoint parameter||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|multiPartUpload|If it is true, camel will upload the file with multipart format. The part size is decided by the partSize option. Camel will only do multipart uploads for files that are larger than the part-size thresholds. Files that are smaller will be uploaded in a single operation.|false|boolean|
+|namingStrategy|The naming strategy to use in streaming upload mode|progressive|object|
+|operation|The operation to do in case the user don't want to do only an upload||object|
+|partSize|Set up the partSize which is used in multipart upload, the default size is 25M. Camel will only do multipart uploads for files that are larger than the part-size thresholds. Files that are smaller will be uploaded in a single operation.|26214400|integer|
+|restartingPolicy|The restarting policy to use in streaming upload mode|override|object|
+|storageClass|The storage class to set in the com.amazonaws.services.s3.model.PutObjectRequest request.||string|
+|streamingUploadMode|When stream mode is true, the upload to bucket will be done in streaming|false|boolean|
+|streamingUploadTimeout|While streaming upload mode is true, this option set the timeout to complete upload||integer|
+|awsKMSKeyId|Define the id of KMS key to use in case KMS is enabled||string|
+|useAwsKMS|Define if KMS must be used or not|false|boolean|
+|useCustomerKey|Define if Customer Key must be used or not|false|boolean|
+|useSSES3|Define if SSE S3 must be used or not|false|boolean|
+|amazonS3Client|Reference to a com.amazonaws.services.s3.AmazonS3 in the registry.||object|
+|amazonS3Presigner|An S3 Presigner for Request, used mainly in createDownloadLink operation||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the SQS client||string|
+|proxyPort|Specify a proxy port to be used inside the client definition.||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the S3 client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the S3 client should expect to load credentials through a default credentials provider.|false|boolean|
+|useProfileCredentialsProvider|Set whether the S3 client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the S3 client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in S3.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|bucketNameOrArn|Bucket name or ARN||string|
+|autoCreateBucket|Setting the autocreation of the S3 bucket bucketName. This will apply also in case of moveAfterRead option enabled, and it will create the destinationBucket if it doesn't exist already.|false|boolean|
+|delimiter|The delimiter which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in.||string|
+|forcePathStyle|Set whether the S3 client should use path-style URL instead of virtual-hosted-style|false|boolean|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|policy|The policy for this queue to set in the com.amazonaws.services.s3.AmazonS3#setBucketPolicy() method.||string|
+|prefix|The prefix which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in.||string|
+|region|The region in which the S3 client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|customerAlgorithm|Define the customer algorithm to use in case CustomerKey is enabled||string|
+|customerKeyId|Define the id of the Customer key to use in case CustomerKey is enabled||string|
+|customerKeyMD5|Define the MD5 of Customer key to use in case CustomerKey is enabled||string|
+|deleteAfterRead|Delete objects from S3 after they have been retrieved. The deleting is only performed if the Exchange is committed. If a rollback occurs, the object is not deleted. If this option is false, then the same objects will be retrieved over and over again in the polls. Therefore, you need to use the Idempotent Consumer EIP in the route to filter out duplicates. You can filter using the AWS2S3Constants#BUCKET\_NAME and AWS2S3Constants#KEY headers, or only the AWS2S3Constants#KEY header.|true|boolean|
+|destinationBucket|Define the destination bucket where an object must be moved when moveAfterRead is set to true.||string|
+|destinationBucketPrefix|Define the destination bucket prefix to use when an object must be moved, and moveAfterRead is set to true.||string|
+|destinationBucketSuffix|Define the destination bucket suffix to use when an object must be moved, and moveAfterRead is set to true.||string|
+|doneFileName|If provided, Camel will only consume files if a done file exists.||string|
+|fileName|To get the object from the bucket with the given file name||string|
+|ignoreBody|If it is true, the S3 Object Body will be ignored completely if it is set to false, the S3 Object will be put in the body. Setting this to true will override any behavior defined by includeBody option.|false|boolean|
+|includeBody|If it is true, the S3Object exchange will be consumed and put into the body and closed. If false, the S3Object stream will be put raw into the body and the headers will be set with the S3 object metadata. This option is strongly related to the autocloseBody option. In case of setting includeBody to true because the S3Object stream will be consumed then it will also be closed, while in case of includeBody false then it will be up to the caller to close the S3Object stream. However, setting autocloseBody to true when includeBody is false it will schedule to close the S3Object stream automatically on exchange completion.|true|boolean|
+|includeFolders|If it is true, the folders/directories will be consumed. If it is false, they will be ignored, and Exchanges will not be created for those|true|boolean|
+|maxConnections|Set the maxConnections parameter in the S3 client configuration|60|integer|
+|maxMessagesPerPoll|Gets the maximum number of messages as a limit to poll at each polling. Gets the maximum number of messages as a limit to poll at each polling. The default value is 10. Use 0 or a negative number to set it as unlimited.|10|integer|
+|moveAfterRead|Move objects from S3 bucket to a different bucket after they have been retrieved. To accomplish the operation, the destinationBucket option must be set. The copy bucket operation is only performed if the Exchange is committed. If a rollback occurs, the object is not moved.|false|boolean|
+|sendEmptyMessageWhenIdle|If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.|false|boolean|
+|autocloseBody|If this option is true and includeBody is false, then the S3Object.close() method will be called on exchange completion. This option is strongly related to includeBody option. In case of setting includeBody to false and autocloseBody to false, it will be up to the caller to close the S3Object stream. Setting autocloseBody to true, will close the S3Object stream automatically.|true|boolean|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|inProgressRepository|A pluggable in-progress repository org.apache.camel.spi.IdempotentRepository. The in-progress repository is used to account the current in progress files being consumed. By default a memory based repository is used.||object|
+|pollStrategy|A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.||object|
+|batchMessageNumber|The number of messages composing a batch in streaming upload mode|10|integer|
+|batchSize|The batch size (in bytes) in streaming upload mode|1000000|integer|
+|bufferSize|The buffer size (in bytes) in streaming upload mode|1000000|integer|
+|deleteAfterWrite|Delete file object after the S3 file has been uploaded|false|boolean|
+|keyName|Setting the key name for an element in the bucket through endpoint parameter||string|
+|multiPartUpload|If it is true, camel will upload the file with multipart format. The part size is decided by the partSize option. Camel will only do multipart uploads for files that are larger than the part-size thresholds. Files that are smaller will be uploaded in a single operation.|false|boolean|
+|namingStrategy|The naming strategy to use in streaming upload mode|progressive|object|
+|operation|The operation to do in case the user don't want to do only an upload||object|
+|partSize|Set up the partSize which is used in multipart upload, the default size is 25M. Camel will only do multipart uploads for files that are larger than the part-size thresholds. Files that are smaller will be uploaded in a single operation.|26214400|integer|
+|restartingPolicy|The restarting policy to use in streaming upload mode|override|object|
+|storageClass|The storage class to set in the com.amazonaws.services.s3.model.PutObjectRequest request.||string|
+|streamingUploadMode|When stream mode is true, the upload to bucket will be done in streaming|false|boolean|
+|streamingUploadTimeout|While streaming upload mode is true, this option set the timeout to complete upload||integer|
+|awsKMSKeyId|Define the id of KMS key to use in case KMS is enabled||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|useAwsKMS|Define if KMS must be used or not|false|boolean|
+|useCustomerKey|Define if Customer Key must be used or not|false|boolean|
+|useSSES3|Define if SSE S3 must be used or not|false|boolean|
+|amazonS3Client|Reference to a com.amazonaws.services.s3.AmazonS3 in the registry.||object|
+|amazonS3Presigner|An S3 Presigner for Request, used mainly in createDownloadLink operation||object|
+|proxyHost|To define a proxy host when instantiating the SQS client||string|
+|proxyPort|Specify a proxy port to be used inside the client definition.||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the S3 client|HTTPS|object|
+|backoffErrorThreshold|The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.||integer|
+|backoffIdleThreshold|The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.||integer|
+|backoffMultiplier|To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.||integer|
+|delay|Milliseconds before the next poll.|500|integer|
+|greedy|If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.|false|boolean|
+|initialDelay|Milliseconds before the first poll starts.|1000|integer|
+|repeatCount|Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.|0|integer|
+|runLoggingLevel|The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.|TRACE|object|
+|scheduledExecutorService|Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.||object|
+|scheduler|To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler|none|object|
+|schedulerProperties|To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.||object|
+|startScheduler|Whether the scheduler should be auto started.|true|boolean|
+|timeUnit|Time unit for initialDelay and delay options.|MILLISECONDS|object|
+|useFixedDelay|Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.|true|boolean|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the S3 client should expect to load credentials through a default credentials provider.|false|boolean|
+|useProfileCredentialsProvider|Set whether the S3 client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the S3 client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in S3.|false|boolean|

camel-aws2-ses.md

@@ -0,0 +1,162 @@
+# Aws2-ses
+
+**Since Camel 3.1**
+
+**Only producer is supported**
+
+The AWS2 SES component supports sending emails with [Amazon’s
+SES](https://aws.amazon.com/ses) service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon SES. More information is available at [Amazon
+SES](https://aws.amazon.com/ses).
+
+# URI Format
+
+    aws2-ses://from[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required SES component options
+
+You have to provide the amazonSESClient in the Registry or your
+accessKey and secretKey to access the [Amazon’s
+SES](https://aws.amazon.com/ses).
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Advanced SesClient configuration
+
+If you need more control over the `SesClient` instance configuration you
+can create your own instance and refer to it from the URI:
+
+    from("direct:start")
+    .to("aws2-ses://example@example.com?amazonSESClient=#client");
+
+The `#client` refers to a `SesClient` in the Registry.
+
+# Examples
+
+## Producer Examples
+
+    from("direct:start")
+        .setHeader(SesConstants.SUBJECT, constant("This is my subject"))
+        .setHeader(SesConstants.TO, constant(Collections.singletonList("to@example.com"))
+        .setBody(constant("This is my message text."))
+        .to("aws2-ses://from@example.com?accessKey=xxx&secretKey=yyy");
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-ses</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|bcc|List of comma-separated destination blind carbon copy (bcc) email address. Can be overridden with 'CamelAwsSesBcc' header.||string|
+|cc|List of comma-separated destination carbon copy (cc) email address. Can be overridden with 'CamelAwsSesCc' header.||string|
+|configuration|component configuration||object|
+|configurationSet|Set the configuration set to send with every request. Override it with 'CamelAwsSesConfigurationSet' header.||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|region|The region in which SES client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|replyToAddresses|List of comma separated reply-to email address(es) for the message, override it using 'CamelAwsSesReplyToAddresses' header.||string|
+|returnPath|The email address to which bounce notifications are to be forwarded, override it using 'CamelAwsSesReturnPath' header.||string|
+|subject|The subject which is used if the message header 'CamelAwsSesSubject' is not present.||string|
+|to|List of comma separated destination email address. Can be overridden with 'CamelAwsSesTo' header.||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|amazonSESClient|To use the AmazonSimpleEmailService as the client||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the SES client||string|
+|proxyPort|To define a proxy port when instantiating the SES client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the SES client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Ses client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the SES client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the SES client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in SES.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|from|The sender's email address.||string|
+|bcc|List of comma-separated destination blind carbon copy (bcc) email address. Can be overridden with 'CamelAwsSesBcc' header.||string|
+|cc|List of comma-separated destination carbon copy (cc) email address. Can be overridden with 'CamelAwsSesCc' header.||string|
+|configurationSet|Set the configuration set to send with every request. Override it with 'CamelAwsSesConfigurationSet' header.||string|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|region|The region in which SES client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|replyToAddresses|List of comma separated reply-to email address(es) for the message, override it using 'CamelAwsSesReplyToAddresses' header.||string|
+|returnPath|The email address to which bounce notifications are to be forwarded, override it using 'CamelAwsSesReturnPath' header.||string|
+|subject|The subject which is used if the message header 'CamelAwsSesSubject' is not present.||string|
+|to|List of comma separated destination email address. Can be overridden with 'CamelAwsSesTo' header.||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|amazonSESClient|To use the AmazonSimpleEmailService as the client||object|
+|proxyHost|To define a proxy host when instantiating the SES client||string|
+|proxyPort|To define a proxy port when instantiating the SES client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the SES client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Ses client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the SES client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the SES client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in SES.|false|boolean|

camel-aws2-sns.md

@@ -0,0 +1,253 @@
+# Aws2-sns
+
+**Since Camel 3.1**
+
+**Only producer is supported**
+
+The AWS2 SNS component allows messages to be sent to an [Amazon Simple
+Notification](https://aws.amazon.com/sns) Topic. The implementation of
+the Amazon API is provided by the [AWS
+SDK](https://aws.amazon.com/sdkforjava/).
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon SNS. More information is available at [Amazon
+SNS](https://aws.amazon.com/sns).
+
+# URI Format
+
+    aws2-sns://topicNameOrArn[?options]
+
+The topic will be created if they don’t already exist.
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+# URI Options
+
+Required SNS component options
+
+You have to provide the amazonSNSClient in the Registry or your
+accessKey and secretKey to access the [Amazon’s
+SNS](https://aws.amazon.com/sns).
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Advanced AmazonSNS configuration
+
+If you need more control over the `SnsClient` instance configuration you
+can create your own instance and refer to it from the URI:
+
+    from("direct:start")
+    .to("aws2-sns://MyTopic?amazonSNSClient=#client");
+
+The `#client` refers to a `AmazonSNS` in the Registry.
+
+## Create a subscription between an AWS SNS Topic and an AWS SQS Queue
+
+You can create a subscription of an SQS Queue to an SNS Topic in this
+way:
+
+    from("direct:start")
+    .to("aws2-sns://test-camel-sns1?amazonSNSClient=#amazonSNSClient&subscribeSNStoSQS=true&queueArn=arn:aws:sqs:eu-central-1:123456789012:test_camel");
+
+The `#amazonSNSClient` refers to a `SnsClient` in the Registry. By
+specifying `subscribeSNStoSQS` to true and a `queueArn` of an existing
+SQS Queue, you’ll be able to subscribe your SQS Queue to your SNS Topic.
+
+At this point, you can consume messages coming from SNS Topic through
+your SQS Queue
+
+    from("aws2-sqs://test-camel?amazonSQSClient=#amazonSQSClient&delay=50&maxMessagesPerPoll=5")
+        .to(...);
+
+# Topic Autocreation
+
+With the option `autoCreateTopic` users are able to avoid the
+autocreation of an SNS Topic in case it doesn’t exist. The default for
+this option is `false`. If set to false, any operation on a non-existent
+topic in AWS won’t be successful and an error will be returned.
+
+# SNS FIFO
+
+SNS FIFO are supported. While creating the SQS queue, you will subscribe
+to the SNS topic there is an important point to remember, you’ll need to
+make possible for the SNS Topic to send the message to the SQS Queue.
+
+This is clear with an example.
+
+Suppose you created an SNS FIFO Topic called Order.fifo and an SQS Queue
+called QueueSub.fifo.
+
+In the access Policy of the QueueSub.fifo you should submit something
+like this
+
+    {
+      "Version": "2008-10-17",
+      "Id": "__default_policy_ID",
+      "Statement": [
+        {
+          "Sid": "__owner_statement",
+          "Effect": "Allow",
+          "Principal": {
+            "AWS": "arn:aws:iam::780560123482:root"
+          },
+          "Action": "SQS:*",
+          "Resource": "arn:aws:sqs:eu-west-1:780560123482:QueueSub.fifo"
+        },
+        {
+          "Effect": "Allow",
+          "Principal": {
+            "Service": "sns.amazonaws.com"
+          },
+          "Action": "SQS:SendMessage",
+          "Resource": "arn:aws:sqs:eu-west-1:780560123482:QueueSub.fifo",
+          "Condition": {
+            "ArnLike": {
+              "aws:SourceArn": "arn:aws:sns:eu-west-1:780410022472:Order.fifo"
+            }
+          }
+        }
+      ]
+    }
+
+This is a critical step to make the subscription work correctly.
+
+## SNS Fifo Topic Message group ID Strategy and message Deduplication ID Strategy
+
+When sending something to the FIFO topic, you’ll need to always set up a
+message group ID strategy.
+
+If the content-based message deduplication has been enabled on the SNS
+Fifo topic, where won’t be the need of setting a message deduplication
+id strategy, otherwise you’ll have to set it.
+
+# Examples
+
+## Producer Examples
+
+Sending to a topic
+
+    from("direct:start")
+      .to("aws2-sns://camel-topic?subject=The+subject+message&autoCreateTopic=true");
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-sns</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|autoCreateTopic|Setting the auto-creation of the topic|false|boolean|
+|configuration|Component configuration||object|
+|kmsMasterKeyId|The ID of an AWS-managed customer master key (CMK) for Amazon SNS or a custom CMK.||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|messageDeduplicationIdStrategy|Only for FIFO Topic. Strategy for setting the messageDeduplicationId on the message. It can be one of the following options: useExchangeId, useContentBasedDeduplication. For the useContentBasedDeduplication option, no messageDeduplicationId will be set on the message.|useExchangeId|string|
+|messageGroupIdStrategy|Only for FIFO Topic. Strategy for setting the messageGroupId on the message. It can be one of the following options: useConstant, useExchangeId, usePropertyValue. For the usePropertyValue option, the value of property CamelAwsSnsMessageGroupId will be used.||string|
+|messageStructure|The message structure to use such as json||string|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|policy|The policy for this topic. Is loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems.||string|
+|queueArn|The ARN endpoint to subscribe to||string|
+|region|The region in which the SNS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|serverSideEncryptionEnabled|Define if Server Side Encryption is enabled or not on the topic|false|boolean|
+|subject|The subject which is used if the message header 'CamelAwsSnsSubject' is not present.||string|
+|subscribeSNStoSQS|Define if the subscription between SNS Topic and SQS must be done or not|false|boolean|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|amazonSNSClient|To use the AmazonSNS as the client||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the SNS client||string|
+|proxyPort|To define a proxy port when instantiating the SNS client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the SNS client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the SNS client should expect to load credentials on an AWS infra instance or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the SNS client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the SNS client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in SNS.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|topicNameOrArn|Topic name or ARN||string|
+|autoCreateTopic|Setting the auto-creation of the topic|false|boolean|
+|headerFilterStrategy|To use a custom HeaderFilterStrategy to map headers to/from Camel.||object|
+|kmsMasterKeyId|The ID of an AWS-managed customer master key (CMK) for Amazon SNS or a custom CMK.||string|
+|messageDeduplicationIdStrategy|Only for FIFO Topic. Strategy for setting the messageDeduplicationId on the message. It can be one of the following options: useExchangeId, useContentBasedDeduplication. For the useContentBasedDeduplication option, no messageDeduplicationId will be set on the message.|useExchangeId|string|
+|messageGroupIdStrategy|Only for FIFO Topic. Strategy for setting the messageGroupId on the message. It can be one of the following options: useConstant, useExchangeId, usePropertyValue. For the usePropertyValue option, the value of property CamelAwsSnsMessageGroupId will be used.||string|
+|messageStructure|The message structure to use such as json||string|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|policy|The policy for this topic. Is loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems.||string|
+|queueArn|The ARN endpoint to subscribe to||string|
+|region|The region in which the SNS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|serverSideEncryptionEnabled|Define if Server Side Encryption is enabled or not on the topic|false|boolean|
+|subject|The subject which is used if the message header 'CamelAwsSnsSubject' is not present.||string|
+|subscribeSNStoSQS|Define if the subscription between SNS Topic and SQS must be done or not|false|boolean|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|amazonSNSClient|To use the AmazonSNS as the client||object|
+|proxyHost|To define a proxy host when instantiating the SNS client||string|
+|proxyPort|To define a proxy port when instantiating the SNS client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the SNS client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the SNS client should expect to load credentials on an AWS infra instance or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the SNS client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the SNS client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in SNS.|false|boolean|

camel-aws2-sqs.md

@@ -0,0 +1,389 @@
+# Aws2-sqs
+
+**Since Camel 3.1**
+
+**Both producer and consumer are supported**
+
+The AWS2 SQS component supports sending and receiving messages to
+[Amazon’s SQS](https://aws.amazon.com/sqs) service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon SQS. More information is available at [Amazon
+SQS](https://aws.amazon.com/sqs).
+
+# URI Format
+
+    aws2-sqs://queueNameOrArn[?options]
+
+The queue will be created if they don’t already exist.
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required SQS component options
+
+You have to provide the amazonSQSClient in the Registry or your
+accessKey and secretKey to access the [Amazon’s
+SQS](https://aws.amazon.com/sqs).
+
+# Batch Consumer
+
+This component implements the Batch Consumer.
+
+This allows you, for instance, to know how many messages exist in this
+batch and for instance, let the Aggregator aggregate this number of
+messages.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Advanced AmazonSQS configuration
+
+If your Camel Application is running behind a firewall or if you need to
+have more control over the SqsClient instance configuration, you can
+create your own instance, and configure Camel to use your instance by
+the bean id.
+
+In the example below, we use *myClient* as the bean id:
+
+    // crate my own instance of SqsClient
+    SqsClient sqs = ...
+    
+    // register the client into Camel registry
+    camelContext.getRegistry().bind("myClient", sqs);
+    
+    // refer to the custom client via myClient as the bean id
+    from("aws2-sqs://MyQueue?amazonSQSClient=#m4yClient&delay=5000&maxMessagesPerPoll=5")
+    .to("mock:result");
+
+## DelayQueue VS Delay for Single message
+
+When the option delayQueue is set to true, the SQS Queue will be a
+DelayQueue with the DelaySeconds option as delay. For more information
+about DelayQueue you can read the [AWS SQS
+documentation](https://docs.aws.amazon.com/en_us/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-delay-queues.html).
+One important information to take into account is the following:
+
+-   For standard queues, the per-queue delay setting is not
+    retroactively—changing the setting doesn’t affect the delay of
+    messages already in the queue.
+
+-   For FIFO queues, the per-queue delay setting is
+    retroactively—changing the setting affects the delay of messages
+    already in the queue.
+
+as stated in the official documentation. If you want to specify a delay
+on single messages, you can ignore the delayQueue option, while you can
+set this option to true if you need to add a fixed delay to all messages
+enqueued.
+
+## Server Side Encryption
+
+There is a set of Server Side Encryption attributes for a queue. The
+related option are: `serverSideEncryptionEnabled`, `keyMasterKeyId` and
+`kmsDataKeyReusePeriod`. The SSE is disabled by default. You need to
+explicitly set the option to true and set the related parameters as
+queue attributes.
+
+# JMS-style Selectors
+
+SQS does not allow selectors, but you can effectively achieve this by
+using the Camel Filter EIP and setting an appropriate
+`visibilityTimeout`. When SQS dispatches a message, it will wait up to
+the visibility timeout before it tries to dispatch the message to a
+different consumer unless a DeleteMessage is received. By default, Camel
+will always send the DeleteMessage at the end of the route, unless the
+route ended in failure. To achieve appropriate filtering and not send
+the DeleteMessage even on successful completion of the route, use a
+Filter:
+
+    from("aws2-sqs://MyQueue?amazonSQSClient=#client&defaultVisibilityTimeout=5000&deleteIfFiltered=false&deleteAfterRead=false")
+    .filter("${header.login} == true")
+      .setProperty(Sqs2Constants.SQS_DELETE_FILTERED, constant(true))
+      .to("mock:filter");
+
+In the above code, if an exchange doesn’t have an appropriate header, it
+will not make it through the filter AND also not be deleted from the SQS
+queue. After 5000 milliseconds, the message will become visible to other
+consumers.
+
+Note we must set the property `Sqs2Constants.SQS_DELETE_FILTERED` to
+`true` to instruct Camel to send the DeleteMessage, if being filtered.
+
+# Available Producer Operations
+
+-   single message (default)
+
+-   sendBatchMessage
+
+-   deleteMessage
+
+-   listQueues
+
+# Send Message
+
+    from("direct:start")
+      .setBody(constant("Camel rocks!"))
+      .to("aws2-sqs://camel-1?accessKey=RAW(xxx)&secretKey=RAW(xxx)&region=eu-west-1");
+
+# Send Batch Message
+
+You can set a `SendMessageBatchRequest` or an `Iterable`
+
+    from("direct:start")
+      .setHeader(SqsConstants.SQS_OPERATION, constant("sendBatchMessage"))
+      .process(new Processor() {
+          @Override
+          public void process(Exchange exchange) throws Exception {
+              List c = new ArrayList();
+              c.add("team1");
+              c.add("team2");
+              c.add("team3");
+              c.add("team4");
+              exchange.getIn().setBody(c);
+          }
+      })
+      .to("aws2-sqs://camel-1?accessKey=RAW(xxx)&secretKey=RAW(xxx)&region=eu-west-1");
+
+As result, you’ll get an exchange containing a
+`SendMessageBatchResponse` instance, that you can examine to check what
+messages were successful and what not. The id set on each message of the
+batch will be a Random UUID.
+
+# Delete single Message
+
+Use deleteMessage operation to delete a single message. You’ll need to
+set a receipt handle header for the message you want to delete.
+
+    from("direct:start")
+      .setHeader(SqsConstants.SQS_OPERATION, constant("deleteMessage"))
+      .setHeader(SqsConstants.RECEIPT_HANDLE, constant("123456"))
+      .to("aws2-sqs://camel-1?accessKey=RAW(xxx)&secretKey=RAW(xxx)&region=eu-west-1");
+
+As result, you’ll get an exchange containing a `DeleteMessageResponse`
+instance, that you can use to check if the message was deleted or not.
+
+# List Queues
+
+Use listQueues operation to list queues.
+
+    from("direct:start")
+      .setHeader(SqsConstants.SQS_OPERATION, constant("listQueues"))
+      .to("aws2-sqs://camel-1?accessKey=RAW(xxx)&secretKey=RAW(xxx)&region=eu-west-1");
+
+As result, you’ll get an exchange containing a `ListQueuesResponse`
+instance, that you can examine to check the actual queues.
+
+# Purge Queue
+
+Use purgeQueue operation to purge queue.
+
+    from("direct:start")
+      .setHeader(SqsConstants.SQS_OPERATION, constant("purgeQueue"))
+      .to("aws2-sqs://camel-1?accessKey=RAW(xxx)&secretKey=RAW(xxx)&region=eu-west-1");
+
+As result you’ll get an exchange containing a `PurgeQueueResponse`
+instance.
+
+# Queue Auto-creation
+
+With the option `autoCreateQueue` users are able to avoid the
+autocreation of an SQS Queue in case it doesn’t exist. The default for
+this option is `false`. If set to *false*, any operation on a
+non-existent queue in AWS won’t be successful and an error will be
+returned.
+
+# Send Batch Message and Message Deduplication Strategy
+
+In case you’re using a SendBatchMessage Operation, you can set two
+different kinds of Message Deduplication Strategy: - useExchangeId -
+useContentBasedDeduplication
+
+The first one will use a ExchangeIdMessageDeduplicationIdStrategy, that
+will use the Exchange ID as parameter The other one will use a
+NullMessageDeduplicationIdStrategy, that will use the body as a
+deduplication element.
+
+In case of send batch message operation, you’ll need to use the
+`useContentBasedDeduplication` and on the Queue you’re pointing you’ll
+need to enable the `content based deduplication` option.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-sqs</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|amazonAWSHost|The hostname of the Amazon AWS cloud.|amazonaws.com|string|
+|autoCreateQueue|Setting the auto-creation of the queue|false|boolean|
+|configuration|The AWS SQS default configuration||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|protocol|The underlying protocol used to communicate with SQS|https|string|
+|queueOwnerAWSAccountId|Specify the queue owner aws account id when you need to connect the queue with a different account owner.||string|
+|region|The region in which SQS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|attributeNames|A list of attribute names to receive when consuming. Multiple names can be separated by comma.||string|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|concurrentConsumers|Allows you to use multiple threads to poll the sqs queue to increase throughput|1|integer|
+|defaultVisibilityTimeout|The default visibility timeout (in seconds)||integer|
+|deleteAfterRead|Delete message from SQS after it has been read|true|boolean|
+|deleteIfFiltered|Whether to send the DeleteMessage to the SQS queue if the exchange has property with key Sqs2Constants#SQS\_DELETE\_FILTERED (CamelAwsSqsDeleteFiltered) set to true.|true|boolean|
+|extendMessageVisibility|If enabled, then a scheduled background task will keep extending the message visibility on SQS. This is needed if it takes a long time to process the message. If set to true defaultVisibilityTimeout must be set. See details at Amazon docs.|false|boolean|
+|kmsDataKeyReusePeriodSeconds|The length of time, in seconds, for which Amazon SQS can reuse a data key to encrypt or decrypt messages before calling AWS KMS again. An integer representing seconds, between 60 seconds (1 minute) and 86,400 seconds (24 hours). Default: 300 (5 minutes).||integer|
+|kmsMasterKeyId|The ID of an AWS-managed customer master key (CMK) for Amazon SQS or a custom CMK.||string|
+|messageAttributeNames|A list of message attribute names to receive when consuming. Multiple names can be separated by comma.||string|
+|serverSideEncryptionEnabled|Define if Server Side Encryption is enabled or not on the queue|false|boolean|
+|visibilityTimeout|The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest. This only makes sense if it's different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently.||integer|
+|waitTimeSeconds|Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response.||integer|
+|batchSeparator|Set the separator when passing a String to send batch message operation|,|string|
+|delaySeconds|Delay sending messages for a number of seconds.||integer|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|messageDeduplicationIdStrategy|Only for FIFO queues. Strategy for setting the messageDeduplicationId on the message. It can be one of the following options: useExchangeId, useContentBasedDeduplication. For the useContentBasedDeduplication option, no messageDeduplicationId will be set on the message.|useExchangeId|string|
+|messageGroupIdStrategy|Only for FIFO queues. Strategy for setting the messageGroupId on the message. It can be one of the following options: useConstant, useExchangeId, usePropertyValue. For the usePropertyValue option, the value of property CamelAwsMessageGroupId will be used.||string|
+|messageHeaderExceededLimit|What to do if sending to AWS SQS has more messages than AWS allows (currently only maximum 10 message headers are allowed). WARN will log a WARN about the limit is for each additional header, so the message can be sent to AWS. WARN\_ONCE will only log one time a WARN about the limit is hit, and drop additional headers, so the message can be sent to AWS. IGNORE will ignore (no logging) and drop additional headers, so the message can be sent to AWS. FAIL will cause an exception to be thrown and the message is not sent to AWS.|WARN|string|
+|operation|The operation to do in case the user don't want to send only a message||object|
+|amazonSQSClient|To use the AmazonSQS client||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|delayQueue|Define if you want to apply delaySeconds option to the queue or on single messages|false|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the SQS client||string|
+|proxyPort|To define a proxy port when instantiating the SQS client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the SQS client|HTTPS|object|
+|maximumMessageSize|The maximumMessageSize (in bytes) an SQS message can contain for this queue.||integer|
+|messageRetentionPeriod|The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue.||integer|
+|policy|The policy for this queue. It can be loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems.||string|
+|queueUrl|To define the queueUrl explicitly. All other parameters, which would influence the queueUrl, are ignored. This parameter is intended to be used to connect to a mock implementation of SQS, for testing purposes.||string|
+|receiveMessageWaitTimeSeconds|If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait.||integer|
+|redrivePolicy|Specify the policy that send message to DeadLetter queue. See detail at Amazon docs.||string|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the SQS client should expect to load credentials on an AWS infra instance or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the SQS client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the SQS client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in SQS.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|queueNameOrArn|Queue name or ARN||string|
+|amazonAWSHost|The hostname of the Amazon AWS cloud.|amazonaws.com|string|
+|autoCreateQueue|Setting the auto-creation of the queue|false|boolean|
+|headerFilterStrategy|To use a custom HeaderFilterStrategy to map headers to/from Camel.||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|protocol|The underlying protocol used to communicate with SQS|https|string|
+|queueOwnerAWSAccountId|Specify the queue owner aws account id when you need to connect the queue with a different account owner.||string|
+|region|The region in which SQS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|attributeNames|A list of attribute names to receive when consuming. Multiple names can be separated by comma.||string|
+|concurrentConsumers|Allows you to use multiple threads to poll the sqs queue to increase throughput|1|integer|
+|defaultVisibilityTimeout|The default visibility timeout (in seconds)||integer|
+|deleteAfterRead|Delete message from SQS after it has been read|true|boolean|
+|deleteIfFiltered|Whether to send the DeleteMessage to the SQS queue if the exchange has property with key Sqs2Constants#SQS\_DELETE\_FILTERED (CamelAwsSqsDeleteFiltered) set to true.|true|boolean|
+|extendMessageVisibility|If enabled, then a scheduled background task will keep extending the message visibility on SQS. This is needed if it takes a long time to process the message. If set to true defaultVisibilityTimeout must be set. See details at Amazon docs.|false|boolean|
+|kmsDataKeyReusePeriodSeconds|The length of time, in seconds, for which Amazon SQS can reuse a data key to encrypt or decrypt messages before calling AWS KMS again. An integer representing seconds, between 60 seconds (1 minute) and 86,400 seconds (24 hours). Default: 300 (5 minutes).||integer|
+|kmsMasterKeyId|The ID of an AWS-managed customer master key (CMK) for Amazon SQS or a custom CMK.||string|
+|maxMessagesPerPoll|Gets the maximum number of messages as a limit to poll at each polling. Is default unlimited, but use 0 or negative number to disable it as unlimited.||integer|
+|messageAttributeNames|A list of message attribute names to receive when consuming. Multiple names can be separated by comma.||string|
+|sendEmptyMessageWhenIdle|If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.|false|boolean|
+|serverSideEncryptionEnabled|Define if Server Side Encryption is enabled or not on the queue|false|boolean|
+|visibilityTimeout|The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest. This only makes sense if it's different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently.||integer|
+|waitTimeSeconds|Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response.||integer|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|pollStrategy|A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.||object|
+|batchSeparator|Set the separator when passing a String to send batch message operation|,|string|
+|delaySeconds|Delay sending messages for a number of seconds.||integer|
+|messageDeduplicationIdStrategy|Only for FIFO queues. Strategy for setting the messageDeduplicationId on the message. It can be one of the following options: useExchangeId, useContentBasedDeduplication. For the useContentBasedDeduplication option, no messageDeduplicationId will be set on the message.|useExchangeId|string|
+|messageGroupIdStrategy|Only for FIFO queues. Strategy for setting the messageGroupId on the message. It can be one of the following options: useConstant, useExchangeId, usePropertyValue. For the usePropertyValue option, the value of property CamelAwsMessageGroupId will be used.||string|
+|messageHeaderExceededLimit|What to do if sending to AWS SQS has more messages than AWS allows (currently only maximum 10 message headers are allowed). WARN will log a WARN about the limit is for each additional header, so the message can be sent to AWS. WARN\_ONCE will only log one time a WARN about the limit is hit, and drop additional headers, so the message can be sent to AWS. IGNORE will ignore (no logging) and drop additional headers, so the message can be sent to AWS. FAIL will cause an exception to be thrown and the message is not sent to AWS.|WARN|string|
+|operation|The operation to do in case the user don't want to send only a message||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|amazonSQSClient|To use the AmazonSQS client||object|
+|delayQueue|Define if you want to apply delaySeconds option to the queue or on single messages|false|boolean|
+|proxyHost|To define a proxy host when instantiating the SQS client||string|
+|proxyPort|To define a proxy port when instantiating the SQS client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the SQS client|HTTPS|object|
+|maximumMessageSize|The maximumMessageSize (in bytes) an SQS message can contain for this queue.||integer|
+|messageRetentionPeriod|The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue.||integer|
+|policy|The policy for this queue. It can be loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems.||string|
+|queueUrl|To define the queueUrl explicitly. All other parameters, which would influence the queueUrl, are ignored. This parameter is intended to be used to connect to a mock implementation of SQS, for testing purposes.||string|
+|receiveMessageWaitTimeSeconds|If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait.||integer|
+|redrivePolicy|Specify the policy that send message to DeadLetter queue. See detail at Amazon docs.||string|
+|backoffErrorThreshold|The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.||integer|
+|backoffIdleThreshold|The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.||integer|
+|backoffMultiplier|To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.||integer|
+|delay|Milliseconds before the next poll.|500|integer|
+|greedy|If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.|false|boolean|
+|initialDelay|Milliseconds before the first poll starts.|1000|integer|
+|repeatCount|Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.|0|integer|
+|runLoggingLevel|The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.|TRACE|object|
+|scheduledExecutorService|Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.||object|
+|scheduler|To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler|none|object|
+|schedulerProperties|To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.||object|
+|startScheduler|Whether the scheduler should be auto started.|true|boolean|
+|timeUnit|Time unit for initialDelay and delay options.|MILLISECONDS|object|
+|useFixedDelay|Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.|true|boolean|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the SQS client should expect to load credentials on an AWS infra instance or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the SQS client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the SQS client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in SQS.|false|boolean|

camel-aws2-step-functions.md

@@ -0,0 +1,202 @@
+# Aws2-step-functions
+
+**Since Camel 4.0**
+
+**Only producer is supported**
+
+The AWS2 Step Functions component supports the following operations on
+[AWS Step Functions](https://aws.amazon.com/step-functions/):
+
+-   Create, delete, update, describe, list state machines.
+
+-   Create, delete, describe, list activities.
+
+-   Start, start sync, stop, list, describe executions.
+
+-   Get activities task.
+
+-   Get execution history
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Step Functions. More information is available at
+[AWS Step Functions](https://aws.amazon.com/step-functions/).
+
+# URI Format
+
+    aws2-step-functions://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required Step Functions component options
+
+You have to provide the awsSfnClient in the Registry or your accessKey
+and secretKey to access the [AWS Step
+Functions](https://aws.amazon.com/step-functions/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Step Functions Producer operations
+
+Camel-AWS Step Functions component provides the following operation on
+the producer side:
+
+-   createStateMachine
+
+-   deleteStateMachine
+
+-   updateStateMachine
+
+-   describeStateMachine
+
+-   listStateMachines
+
+-   createActivity
+
+-   deleteActivity
+
+-   describeActivity
+
+-   getActivityTask
+
+-   listActivities
+
+-   startExecution
+
+-   startSyncExecution
+
+-   stopExecution
+
+-   describeExecution
+
+-   listExecutions
+
+-   getExecutionHistory
+
+# Producer Examples
+
+-   createStateMachine: this operation will create a state machine
+
+<!-- -->
+
+    from("direct:createStateMachine")
+        .to("aws2-step-functions://test?awsSfnClient=#awsSfnClient&operation=createMachine")
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as the body. In AWS
+Step Functions, there are multiple operations you can submit, as an
+example for Create state machine request, you can do something like:
+
+    from("direct:start")
+      .setBody(CreateStateMachineRequest.builder().name("state-machine").build())
+      .to("aws2-step-functions://test?awsSfnClient=#awsSfnClient&operation=createStateMachine&pojoRequest=true")
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-step-functions</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|region|The region in which StepFunctions client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the StepFunctions client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the StepFunctions client should expect to load credentials through a profile credentials provider.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|awsSfnClient|To use an existing configured AwsStepFunctionsClient client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the StepFunctions client||string|
+|proxyPort|To define a proxy port when instantiating the StepFunctions client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the StepFunctions client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|useSessionCredentials|Set whether the Step Functions client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Step Functions.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|operation|The operation to perform. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|region|The region in which StepFunctions client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the StepFunctions client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the StepFunctions client should expect to load credentials through a profile credentials provider.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|awsSfnClient|To use an existing configured AwsStepFunctionsClient client||object|
+|proxyHost|To define a proxy host when instantiating the StepFunctions client||string|
+|proxyPort|To define a proxy port when instantiating the StepFunctions client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the StepFunctions client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|useSessionCredentials|Set whether the Step Functions client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Step Functions.|false|boolean|

camel-aws2-sts.md

@@ -0,0 +1,182 @@
+# Aws2-sts
+
+**Since Camel 3.5**
+
+**Only producer is supported**
+
+The AWS2 STS component supports assumeRole operation. [AWS
+STS](https://aws.amazon.com/sts/).
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon STS. More information is available at [Amazon
+STS](https://aws.amazon.com/sts/).
+
+The AWS2 STS component works on the aws-global region, and it has
+aws-global as the default region.
+
+# URI Format
+
+    aws2-sts://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required STS component options
+
+You have to provide the amazonSTSClient in the Registry or your
+accessKey and secretKey to access the [Amazon
+STS](https://aws.amazon.com/sts/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## STS Producer operations
+
+Camel-AWS STS component provides the following operation on the producer
+side:
+
+-   assumeRole
+
+-   getSessionToken
+
+-   getFederationToken
+
+# Producer Examples
+
+-   assumeRole: this operation will make an AWS user assume a different
+    role temporary
+
+<!-- -->
+
+    from("direct:assumeRole")
+        .setHeader(STS2Constants.ROLE_ARN, constant("arn:123"))
+        .setHeader(STS2Constants.ROLE_SESSION_NAME, constant("groot"))
+        .to("aws2-sts://test?stsClient=#amazonSTSClient&operation=assumeRole")
+
+-   getSessionToken: this operation will return a temporary session
+    token
+
+<!-- -->
+
+    from("direct:getSessionToken")
+        .to("aws2-sts://test?stsClient=#amazonSTSClient&operation=getSessionToken")
+
+-   getFederationToken: this operation will return a temporary
+    federation token
+
+<!-- -->
+
+    from("direct:getFederationToken")
+        .setHeader(STS2Constants.FEDERATED_NAME, constant("federation-account"))
+        .to("aws2-sts://test?stsClient=#amazonSTSClient&operation=getSessionToken")
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as the body. In AWS
+STS, as an example for Assume Role request, you can do something like:
+
+    from("direct:createUser")
+         .setBody(AssumeRoleRequest.builder().roleArn("arn:123").roleSessionName("groot").build())
+        .to("aws2-sts://test?stsClient=#amazonSTSClient&operation=assumeRole&pojoRequest=true")
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-sts</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform|assumeRole|object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the STS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()|aws-global|string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|stsClient|To use an existing configured AWS STS client||object|
+|proxyHost|To define a proxy host when instantiating the STS client||string|
+|proxyPort|To define a proxy port when instantiating the STS client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the STS client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the STS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the STS client should expect to load credentials through a profile credentials provider.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|operation|The operation to perform|assumeRole|object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the STS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()|aws-global|string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|stsClient|To use an existing configured AWS STS client||object|
+|proxyHost|To define a proxy host when instantiating the STS client||string|
+|proxyPort|To define a proxy port when instantiating the STS client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the STS client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the STS client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the STS client should expect to load credentials through a profile credentials provider.|false|boolean|

camel-aws2-timestream.md

@@ -0,0 +1,270 @@
+# Aws2-timestream
+
+**Since Camel 4.1**
+
+**Only producer is supported**
+
+The AWS2 Timestream component supports the following operations on [AWS
+Timestream](https://aws.amazon.com/timestream/):
+
+-   Write Operations
+    
+    -   Describe Write Endpoints
+    
+    -   Create, Describe, Resume, List Batch Load Tasks
+    
+    -   Create, Delete, Update, Describe, List Databases
+    
+    -   Create, Delete, Update, Describe, List Tables
+    
+    -   Write Records
+
+-   Query Operations
+    
+    -   Describe Query Endpoints
+    
+    -   Prepare Query, Query, Cancel Query
+    
+    -   Create, Delete, Execute, Update, Describe, List Scheduled
+        Queries
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Timestream. More information is available at
+[AWS Timestream](https://aws.amazon.com/timestream/).
+
+# URI Format
+
+    aws2-timestream://clientType:label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required Timestream component options
+
+Based on the type of operation to be performed, the type of client
+(write/query) needs to be provided as clientType URI path parameter
+
+You have to provide either the awsTimestreamWriteClient(for write
+operations) or awsTimestreamQueryClient(for query operations) in the
+Registry or your accessKey and secretKey to access the [AWS
+Timestream](https://aws.amazon.com/timestream/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Timestream Producer operations
+
+Camel-AWS Timestream component provides the following operation on the
+producer side:
+
+-   Write Operations
+    
+    -   describeEndpoints
+    
+    -   createBatchLoadTask
+    
+    -   describeBatchLoadTask
+    
+    -   resumeBatchLoadTask
+    
+    -   listBatchLoadTasks
+    
+    -   createDatabase
+    
+    -   deleteDatabase
+    
+    -   describeDatabase
+    
+    -   updateDatabase
+    
+    -   listDatabases
+    
+    -   createTable
+    
+    -   deleteTable
+    
+    -   describeTable
+    
+    -   updateTable
+    
+    -   listTables
+    
+    -   writeRecords
+
+-   Query Operations
+    
+    -   describeEndpoints
+    
+    -   createScheduledQuery
+    
+    -   deleteScheduledQuery
+    
+    -   executeScheduledQuery
+    
+    -   updateScheduledQuery
+    
+    -   describeScheduledQuery
+    
+    -   listScheduledQueries
+    
+    -   prepareQuery
+    
+    -   query
+    
+    -   cancelQuery
+
+# Producer Examples
+
+-   Write Operation
+    
+    -   createDatabase: this operation will create a timestream database
+
+<!-- -->
+
+    from("direct:createDatabase")
+        .setHeader(Timestream2Constants.DATABASE_NAME, constant("testDb"))
+        .setHeader(Timestream2Constants.KMS_KEY_ID, constant("testKmsKey"))
+        .to("aws2-timestream://write:test?awsTimestreamWriteClient=#awsTimestreamWriteClient&operation=createDatabase")
+
+-   Query Operation
+    
+    -   query: this operation will execute a timestream query
+
+<!-- -->
+
+    from("direct:query")
+        .setHeader(Timestream2Constants.QUERY_STRING, constant("SELECT * FROM testDb.testTable ORDER BY time DESC LIMIT 10"))
+        .to("aws2-timestream://query:test?awsTimestreamQueryClient=#awsTimestreamQueryClient&operation=query")
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as the body. In AWS
+Timestream there are multiple operations you can submit, as an example
+for Create state machine request, you can do something like:
+
+-   Write Operation
+    
+    -   createDatabase: this operation will create a timestream database
+
+<!-- -->
+
+    from("direct:start")
+      .setBody(CreateDatabaseRequest.builder().database(Database.builder().databaseName("testDb").kmsKeyId("testKmsKey").build()).build())
+      .to("aws2-timestream://write:test?awsTimestreamWriteClient=#awsTimestreamWriteClient&operation=createDatabase&pojoRequest=true")
+
+-   Query Operation
+    
+    -   query: this operation will execute a timestream query
+
+<!-- -->
+
+    from("direct:query")
+        .setBody(QueryRequest.builder().queryString("SELECT * FROM testDb.testTable ORDER BY time DESC LIMIT 10").build())
+        .to("aws2-timestream://query:test?awsTimestreamQueryClient=#awsTimestreamQueryClient&operation=query&pojoRequest=true")
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-timestream</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform. It can be describeEndpoints,createBatchLoadTask,describeBatchLoadTask, resumeBatchLoadTask,listBatchLoadTasks,createDatabase,deleteDatabase,describeDatabase,updateDatabase, listDatabases,createTable,deleteTable,describeTable,updateTable,listTables,writeRecords, createScheduledQuery,deleteScheduledQuery,executeScheduledQuery,updateScheduledQuery, describeScheduledQuery,listScheduledQueries,prepareQuery,query,cancelQuery||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|region|The region in which the Timestream client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the Timestream client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Timestream client should expect to load credentials through a profile credentials provider.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|awsTimestreamQueryClient|To use an existing configured AwsTimestreamQueryClient client||object|
+|awsTimestreamWriteClient|To use an existing configured AwsTimestreamWriteClient client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Timestream client||string|
+|proxyPort|To define a proxy port when instantiating the Timestream client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Timestream client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|clientType|Type of client - write/query||object|
+|label|Logical name||string|
+|operation|The operation to perform. It can be describeEndpoints,createBatchLoadTask,describeBatchLoadTask, resumeBatchLoadTask,listBatchLoadTasks,createDatabase,deleteDatabase,describeDatabase,updateDatabase, listDatabases,createTable,deleteTable,describeTable,updateTable,listTables,writeRecords, createScheduledQuery,deleteScheduledQuery,executeScheduledQuery,updateScheduledQuery, describeScheduledQuery,listScheduledQueries,prepareQuery,query,cancelQuery||object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|region|The region in which the Timestream client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|useDefaultCredentialsProvider|Set whether the Timestream client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Timestream client should expect to load credentials through a profile credentials provider.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|awsTimestreamQueryClient|To use an existing configured AwsTimestreamQueryClient client||object|
+|awsTimestreamWriteClient|To use an existing configured AwsTimestreamWriteClient client||object|
+|proxyHost|To define a proxy host when instantiating the Timestream client||string|
+|proxyPort|To define a proxy port when instantiating the Timestream client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Timestream client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|secretKey|Amazon AWS Secret Key||string|

camel-aws2-translate.md

@@ -0,0 +1,171 @@
+# Aws2-translate
+
+**Since Camel 3.1**
+
+**Only producer is supported**
+
+The AWS2 Translate component supports translate a text in multiple
+languages. [AWS Translate](https://aws.amazon.com/translate/) clusters
+instances.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Translate. More information is available at
+[Amazon Translate](https://aws.amazon.com/translate/).
+
+# URI Format
+
+    aws2-translate://label[?options]
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+Required Translate component options
+
+You have to provide the amazonTranslateClient in the Registry or your
+accessKey and secretKey to access the [Amazon
+Translate](https://aws.amazon.com/translate/) service.
+
+# Usage
+
+## Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static
+credentials by specifying the useDefaultCredentialsProvider option and
+set it to true.
+
+The order of evaluation for Default Credentials Provider is the
+following:
+
+-   Java system properties - `aws.accessKeyId` and `aws.secretKey`
+
+-   Environment variables - `AWS_ACCESS_KEY_ID` and
+    `AWS_SECRET_ACCESS_KEY`.
+
+-   Web Identity Token from AWS STS.
+
+-   The shared credentials and config files.
+
+-   Amazon ECS container credentials - loaded from the Amazon ECS if the
+    environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is
+    set.
+
+-   Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by
+specifying the useProfileCredentialsProvider option to true and
+profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the
+same time.
+
+For more information about this you can look at [AWS credentials
+documentation](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html)
+
+## Translate Producer operations
+
+Camel-AWS Translate component provides the following operation on the
+producer side:
+
+-   translateText
+
+# Translate Text example
+
+    from("direct:start")
+      .setHeader(TranslateConstants.SOURCE_LANGUAGE, TranslateLanguageEnum.ITALIAN)
+      .setHeader(TranslateConstants.TARGET_LANGUAGE, TranslateLanguageEnum.GERMAN)
+      .setBody("Ciao")
+      .to("aws2-translate://test?translateClient=#amazonTranslateClient&operation=translateText");
+
+As a result, you’ll get an exchange containing the translated text.
+
+# Using a POJO as body
+
+Sometimes building an AWS Request can be complex because of multiple
+options. We introduce the possibility to use a POJO as the body. In AWS
+Translate, the only operation available is TranslateText, so you can do
+something like:
+
+    from("direct:start")
+      .setBody(TranslateTextRequest.builder().sourceLanguageCode(Translate2LanguageEnum.ITALIAN.toString())
+                        .targetLanguageCode(Translate2LanguageEnum.GERMAN.toString()).text("Ciao").build())
+      .to("aws2-translate://test?translateClient=#amazonTranslateClient&operation=translateText&pojoRequest=true");
+
+In this way, you’ll pass the request directly without the need of
+passing headers and options specifically related to this operation.
+
+# Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+**pom.xml**
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-aws2-translate</artifactId>
+        <version>${camel-version}</version>
+    </dependency>
+
+where `${camel-version}` must be replaced by the actual version of
+Camel.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|autodetectSourceLanguage|Being able to autodetect the source language|false|boolean|
+|configuration|Component configuration||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The operation to perform|translateText|object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the Translate client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|sourceLanguage|Source language to use||string|
+|targetLanguage|Target language to use||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|translateClient|To use an existing configured AWS Translate client||object|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|proxyHost|To define a proxy host when instantiating the Translate client||string|
+|proxyPort|To define a proxy port when instantiating the Translate client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Translate client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Translate client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Translate client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Translate client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Translate.|false|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Logical name||string|
+|autodetectSourceLanguage|Being able to autodetect the source language|false|boolean|
+|operation|The operation to perform|translateText|object|
+|overrideEndpoint|Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option|false|boolean|
+|pojoRequest|If we want to use a POJO request as body or not|false|boolean|
+|region|The region in which the Translate client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You'll need to use the name Region.EU\_WEST\_1.id()||string|
+|sourceLanguage|Source language to use||string|
+|targetLanguage|Target language to use||string|
+|uriEndpointOverride|Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|translateClient|To use an existing configured AWS Translate client||object|
+|proxyHost|To define a proxy host when instantiating the Translate client||string|
+|proxyPort|To define a proxy port when instantiating the Translate client||integer|
+|proxyProtocol|To define a proxy protocol when instantiating the Translate client|HTTPS|object|
+|accessKey|Amazon AWS Access Key||string|
+|profileCredentialsName|If using a profile credentials provider, this parameter will set the profile name||string|
+|secretKey|Amazon AWS Secret Key||string|
+|sessionToken|Amazon AWS Session Token used when the user needs to assume an IAM role||string|
+|trustAllCertificates|If we want to trust all certificates in case of overriding the endpoint|false|boolean|
+|useDefaultCredentialsProvider|Set whether the Translate client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in.|false|boolean|
+|useProfileCredentialsProvider|Set whether the Translate client should expect to load credentials through a profile credentials provider.|false|boolean|
+|useSessionCredentials|Set whether the Translate client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Translate.|false|boolean|

camel-azure-cosmosdb.md

@@ -0,0 +1,791 @@
+# Azure-cosmosdb
+
+**Since Camel 3.10**
+
+**Both producer and consumer are supported**
+
+[Azure Cosmos DB](https://azure.microsoft.com/en-us/services/cosmos-db/)
+is Microsoft’s globally distributed, multimodel database service for
+operational and analytics workloads. It offers multi-mastering feature
+by automatically scaling throughput, compute, and storage. This
+component interacts with Azure CosmosDB through Azure SQL API.
+
+Prerequisites
+
+You must have a valid Windows Azure Storage account. More information is
+available at [Azure Documentation
+Portal](https://docs.microsoft.com/azure/).
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-azure-cosmosdb</artifactId>
+        <version>x.x.x</version>
+        <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# URI Format
+
+    azure-cosmosdb://[databaseName][/containerName][?options]
+
+In case of the consumer, `databaseName`, `containerName` are required,
+In case of the producer, it depends on the operation that being
+requested, for example if operation is on a database level, e.b:
+deleteDatabase, only `databaseName` is required, but in case of
+operation being requested in container level, e.g: readItem, then
+`databaseName` and `containerName` are required.
+
+You can append query options to the URI in the following format,
+`?options=value&option2=value&`…
+
+# Authentication Information
+
+To use this component, you have two options to provide the required
+Azure authentication information:
+
+-   Provide `accountKey` and `databaseEndpoint` for your Azure CosmosDB
+    account. The account key can be generated through your CosmosDB
+    Azure portal.
+
+-   Provide a
+    [CosmosAsyncClient](https://docs.microsoft.com/en-us/java/api/com.azure.cosmos.cosmosasyncclient?view=azure-java-stable)
+    instance which can be provided into `cosmosAsyncClient`.
+
+# Async Consumer and Producer
+
+This component implements the async Consumer and producer.
+
+This allows camel route to consume and produce events asynchronously
+without blocking any threads.
+
+# Usage
+
+For example, to consume records from a specific container in a specific
+database to a file, use the following snippet:
+
+    from("azure-cosmosdb://camelDb/myContainer?accountKey=MyaccountKey&databaseEndpoint=https//myazure.com:443&leaseDatabaseName=myLeaseDB&createLeaseDatabaseIfNotExists=true&createLeaseContainerIfNotExists=true").
+    to("file://directory");
+
+## Message headers evaluated by the component producer
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 10%" />
+<col style="width: 10%" />
+<col style="width: 69%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Header</th>
+<th style="text-align: left;">Variable Name</th>
+<th style="text-align: left;">Type</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbDatabaseName</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.DATABASE_NAME</code></p></td>
+<td style="text-align: left;"><p><code>String</code></p></td>
+<td style="text-align: left;"><p>Overrides the database name which is
+the name of the Cosmos database that component should connect to. In
+case you are producing data and have createDatabaseIfNotExists=true, the
+component will automatically auto create a Cosmos database.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbContainerName</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.CONTAINER_NAME</code></p></td>
+<td style="text-align: left;"><p><code>String</code></p></td>
+<td style="text-align: left;"><p>Overrides the container name which is
+the name of the Cosmos container that component should connect to. In
+case you are producing data and have createContainerIfNotExists=true,
+the component will automatically auto create a Cosmos
+container.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbOperation</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.OPERATION</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbOperationsDefinition</code></p></td>
+<td style="text-align: left;"><p>Set the producer operation which can be
+used to execute a specific operation on the producer.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbQuery</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.QUERY</code></p></td>
+<td style="text-align: left;"><p><code>String</code></p></td>
+<td style="text-align: left;"><p>Set the SQL query to execute on a given
+producer query operations.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbQueryRequestOptions</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.QUERY_REQUEST_OPTIONS</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosQueryRequestOptions</code></p></td>
+<td style="text-align: left;"><p>Set additional QueryRequestOptions that
+can be used with queryItems, queryContainers, queryDatabases,
+listDatabases, listItems, listContainers operations.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbCreateDatabaseIfNotExist</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.CREATE_DATABASE_IF_NOT_EXIST</code></p></td>
+<td style="text-align: left;"><p><code>boolean</code></p></td>
+<td style="text-align: left;"><p>Sets if the component should create the
+Cosmos database automatically in case it doesn’t exist in the Cosmos
+account.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbCreateContainerIfNotExist</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.CREATE_CONTAINER_IF_NOT_EXIST</code></p></td>
+<td style="text-align: left;"><p><code>boolean</code></p></td>
+<td style="text-align: left;"><p>Sets if the component should create
+Cosmos container automatically in case it doesn’t exist in the Cosmos
+account.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbThroughputProperties</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.THROUGHPUT_PROPERTIES</code></p></td>
+<td
+style="text-align: left;"><p><code>ThroughputProperties</code></p></td>
+<td style="text-align: left;"><p>Sets throughput of the resources in the
+Azure Cosmos DB service.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbDatabaseRequestOptions</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.DATABASE_REQUEST_OPTIONS</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDatabaseRequestOptions</code></p></td>
+<td style="text-align: left;"><p>Sets additional options to execute on
+database operations.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbContainerPartitionKeyPath</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.CONTAINER_PARTITION_KEY_PATH</code></p></td>
+<td style="text-align: left;"><p><code>String</code></p></td>
+<td style="text-align: left;"><p>Set the container partition key
+path.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbContainerRequestOptions</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.CONTAINER_REQUEST_OPTIONS</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosContainerRequestOptions</code></p></td>
+<td style="text-align: left;"><p>Set additional options to execute on
+container operations.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbItemPartitionKey</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.ITEM_PARTITION_KEY</code></p></td>
+<td style="text-align: left;"><p><code>String</code></p></td>
+<td style="text-align: left;"><p>Set the partition key. Represents a
+partition key value in the Azure Cosmos DB database service. A partition
+key identifies the partition where the item is stored in.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbItemRequestOptions</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.ITEM_REQUEST_OPTIONS</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosItemRequestOptions</code></p></td>
+<td style="text-align: left;"><p>Set additional options to execute on
+item operations.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbItemId</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.ITEM_ID</code></p></td>
+<td style="text-align: left;"><p><code>String</code></p></td>
+<td style="text-align: left;"><p>Set the itemId in case needed for
+operation on item like <em>delete</em>, <em>replace</em>.</p></td>
+</tr>
+</tbody>
+</table>
+
+## Message headers set by the component producer
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 10%" />
+<col style="width: 10%" />
+<col style="width: 69%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Header</th>
+<th style="text-align: left;">Variable Name</th>
+<th style="text-align: left;">Type</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbRecourseId</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.RESOURCE_ID</code></p></td>
+<td style="text-align: left;"><p><code>String</code></p></td>
+<td style="text-align: left;"><p>The resource ID of the requested
+resource.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbEtag</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.E_TAG</code></p></td>
+<td style="text-align: left;"><p><code>String</code></p></td>
+<td style="text-align: left;"><p>The Etag ID of the requested
+resource.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbTimestamp</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.TIMESTAMP</code></p></td>
+<td style="text-align: left;"><p><code>String</code></p></td>
+<td style="text-align: left;"><p>The timestamp of the requested
+resource.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbResponseHeaders</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.RESPONSE_HEADERS</code></p></td>
+<td style="text-align: left;"><p><code>Map</code></p></td>
+<td style="text-align: left;"><p>The response headers of the requested
+resource.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbStatusCode</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.STATUS_CODE</code></p></td>
+<td style="text-align: left;"><p><code>Integer</code></p></td>
+<td style="text-align: left;"><p>The status code of the requested
+resource.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbDefaultTimeToLiveInSeconds</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.DEFAULT_TIME_TO_LIVE_SECONDS</code></p></td>
+<td style="text-align: left;"><p><code>Integer</code></p></td>
+<td style="text-align: left;"><p>The TTL of the requested
+resource.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbManualThroughput</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.MANUAL_THROUGHPUT</code></p></td>
+<td style="text-align: left;"><p><code>Integer</code></p></td>
+<td style="text-align: left;"><p>The manual throughput of the requested
+resource.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelAzureCosmosDbAutoscaleMaxThroughput</code></p></td>
+<td
+style="text-align: left;"><p><code>CosmosDbConstants.AUTOSCALE_MAX_THROUGHPUT</code></p></td>
+<td style="text-align: left;"><p><code>Integer</code></p></td>
+<td style="text-align: left;"><p>The AutoscaleMaxThroughput of the
+requested resource.</p></td>
+</tr>
+</tbody>
+</table>
+
+## Azure CosmosDB Producer operations
+
+Camel Azure CosmosDB component provides a wide range of operations on
+the producer side:
+
+**Operations on the service level**
+
+For these operations, `databaseName` is **required** except for
+`queryDatabases` and `listDatabases` operations.
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>listDatabases</code></p></td>
+<td style="text-align: left;"><p>Gets a list of all databases as
+<code>List&lt;CosmosDatabaseProperties&gt;</code> set in the exchange
+message body.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>createDatabase</code></p></td>
+<td style="text-align: left;"><p>Create a database in the specified
+Azure CosmosDB account.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>queryDatabases</code></p></td>
+<td style="text-align: left;"><p><strong><code>query</code> is
+required</strong> Execute an SQL query against the service level in
+order for example return only a small subset of the databases list. It
+will set <code>List&lt;CosmosDatabaseProperties&gt;</code> set in the
+exchange message body.</p></td>
+</tr>
+</tbody>
+</table>
+
+**Operations on the database level**
+
+For these operations, `databaseName` is **required** for all operations
+here and `containerName` only for `createContainer` and
+`queryContainers`.
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>deleteDatabase</code></p></td>
+<td style="text-align: left;"><p>Delete a database from the Azure
+CosmosDB account.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>createContainer</code></p></td>
+<td style="text-align: left;"><p>Create a container in the specified
+Azure CosmosDB database.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>replaceDatabaseThroughput</code></p></td>
+<td style="text-align: left;"><p>Replace the throughput for the
+specified Azure CosmosDB database.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>listContainers</code></p></td>
+<td style="text-align: left;"><p>Gets a list of all containers in the
+specified database as <code>List&lt;CosmosContainerProperties&gt;</code>
+set in the exchange message body.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>queryContainers</code></p></td>
+<td style="text-align: left;"><p><strong><code>query</code> is
+required</strong> Executes an SQL query against the database level in
+order for example return only a small subset of the container list for
+the specified database. It will set
+<code>List&lt;CosmosContainerProperties&gt;</code> set in the exchange
+message body.</p></td>
+</tr>
+</tbody>
+</table>
+
+**Operations on the container level**
+
+For these operations, `databaseName` and `containerName` is **required**
+for all operations here.
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>deleteContainer</code></p></td>
+<td style="text-align: left;"><p>Delete a container from the specified
+Azure CosmosDB database.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>replaceContainerThroughput</code></p></td>
+<td style="text-align: left;"><p>Replace the throughput for the
+specified Azure CosmosDB container.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>createItem</code></p></td>
+<td style="text-align: left;"><p><strong><code>itemPartitionKey</code>
+is required</strong> Creates an item in the specified container, it
+accepts POJO or key value as <code>Map&lt;String, ?&gt;</code>.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>upsertItem</code></p></td>
+<td style="text-align: left;"><p><strong><code>itemPartitionKey</code>
+is required</strong> Creates an item in the specified container if it
+doesn’t exist otherwise overwrite it if it exists, it accepts POJO or
+key value as <code>Map&lt;String, ?&gt;</code>.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>replaceItem</code></p></td>
+<td style="text-align: left;"><p><strong><code>itemPartitionKey</code>
+and <code>itemId</code> are required</strong> Overwrites an item in the
+specified container, it accepts POJO or key value as
+<code>Map&lt;String, ?&gt;</code>.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>deleteItem</code></p></td>
+<td style="text-align: left;"><p><strong><code>itemPartitionKey</code>
+and <code>itemId</code> are required</strong> Deletes an item in the
+specified container.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>readItem</code></p></td>
+<td style="text-align: left;"><p><strong><code>itemPartitionKey</code>
+and <code>itemId</code> are required</strong> Gets an item in the
+specified container as <code>Map&lt;String,?&gt;</code> set in the
+exchange body message.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>readItem</code></p></td>
+<td
+style="text-align: left;"><p><strong><code>itemPartitionKey</code></strong>
+Gets a list of items in the specified container per the
+<code>itemPartitionKey</code> as
+<code>List&lt;Map&lt;String,?&gt;&gt;</code> set in the exchange body
+message.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>queryItems</code></p></td>
+<td style="text-align: left;"><p><strong><code>query</code> is
+required</strong> Execute an SQL query against the container level in
+order, for example, return only matching items per the SQL query. It
+will set <code>List&lt;Map&lt;String,&gt;?&gt;</code> in the exchange
+message body.</p></td>
+</tr>
+</tbody>
+</table>
+
+Refer to the example section in this page to learn how to use these
+operations into your camel application.
+
+### Examples
+
+-   `listDatabases`:
+
+<!-- -->
+
+    from("direct:start")
+      .to("azure-cosmosdb://?operation=listDatabases")
+      .to("mock:result");
+
+-   `createDatabase`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(CosmosDbConstants.DATABASE_NAME, "myDb");
+          })
+      .to("azure-cosmosdb://?operation=createDatabase")
+      .to("mock:result");
+
+-   `deleteDatabase`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(CosmosDbConstants.DATABASE_NAME, "myDb");
+          })
+      .to("azure-cosmosdb://?operation=deleteDatabase")
+      .to("mock:result");
+
+-   `createContainer`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(CosmosDbConstants.DATABASE_NAME, "databaseName");
+            exchange.getIn().setHeader(CosmosDbConstants.CONTAINER_NAME, "containerName");
+            exchange.getIn().setHeader(CosmosDbConstants.CONTAINER_PARTITION_KEY_PATH, "path");
+            exchange.getIn().setHeader(CosmosDbConstants.CREATE_DATABASE_IF_NOT_EXIST, true);
+          })
+      .to("azure-cosmosdb://?operation=createContainer")
+      .to("mock:result");
+
+-   `deleteContainer`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(CosmosDbConstants.DATABASE_NAME, "databaseName");
+            exchange.getIn().setHeader(CosmosDbConstants.CONTAINER_NAME, "containerName");
+          })
+      .to("azure-cosmosdb://?operation=deleteContainer")
+      .to("mock:result");
+
+-   `replaceDatabaseThroughput`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(CosmosDbConstants.DATABASE_NAME, "databaseName");
+             exchange.getIn().setHeader(CosmosDbConstants.THROUGHPUT_PROPERTIES,
+                        ThroughputProperties.createManualThroughput(700));
+          })
+      .to("azure-cosmosdb://?operation=replaceDatabaseThroughput")
+      .to("mock:result");
+
+-   `queryContainers`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(CosmosDbConstants.DATABASE_NAME, "databaseName");
+                exchange.getIn().setHeader(CosmosDbConstants.QUERY, "SELECT * from c where c.id = 'myAwersomeContainer'");
+          })
+      .to("azure-cosmosdb://?operation=queryContainers")
+      .to("mock:result");
+
+-   `createItem`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+                // create item to send
+                final Map<String, Object> item = new HashMap<>();
+                item1.put("id", "test-id-1");
+                item1.put("partition", "test-1");
+                item1.put("field1", "awesome!");
+    
+                exchange.getIn().setHeader(CosmosDbConstants.DATABASE_NAME, "databaseName");
+                exchange.getIn().setHeader(CosmosDbConstants.CONTAINER_NAME, "containerName");
+                exchange.getIn().setHeader(CosmosDbConstants.CONTAINER_PARTITION_KEY_PATH, "partition");
+                exchange.getIn().setHeader(CosmosDbConstants.ITEM_PARTITION_KEY, "test-1");
+                exchange.getIn().setBody(item);
+          })
+      .to("azure-cosmosdb://?operation=createItem")
+      .to("mock:result");
+
+-   `replaceItem`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+                // create item to send
+                final Map<String, Object> item = new HashMap<>();
+                item1.put("id", "test-id-1");
+                item1.put("partition", "test-1");
+                item1.put("field1", "awesome!");
+    
+                exchange.getIn().setHeader(CosmosDbConstants.DATABASE_NAME, "databaseName");
+                exchange.getIn().setHeader(CosmosDbConstants.CONTAINER_NAME, "containerName");
+                exchange.getIn().setHeader(CosmosDbConstants.ITEM_PARTITION_KEY, "test-1");
+                exchange.getIn().setHeader(CosmosDbConstants.ITEM_ID, "test-id-1");
+                exchange.getIn().setBody(item);
+          })
+      .to("azure-cosmosdb://?operation=replaceItem")
+      .to("mock:result");
+
+-   `deleteItem`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+                exchange.getIn().setHeader(CosmosDbConstants.DATABASE_NAME, "databaseName");
+                exchange.getIn().setHeader(CosmosDbConstants.CONTAINER_NAME, "containerName");
+                exchange.getIn().setHeader(CosmosDbConstants.ITEM_PARTITION_KEY, "test-1");
+                exchange.getIn().setHeader(CosmosDbConstants.ITEM_ID, "test-id-1");
+                exchange.getIn().setBody(item);
+          })
+      .to("azure-cosmosdb://?operation=deleteItem")
+      .to("mock:result");
+
+-   `queryItems`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+                exchange.getIn().setHeader(CosmosDbConstants.DATABASE_NAME, "databaseName");
+                exchange.getIn().setHeader(CosmosDbConstants.CONTAINER_NAME, "containerName");
+                exchange.getIn().setHeader(CosmosDbConstants.QUERY, "SELECT c.id,c.field2,c.field1 from c where c.id = 'test-id-1'");
+          })
+      .to("azure-cosmosdb://?operation=queryItems")
+      .to("mock:result");
+
+## Azure CosmosDB Consumer
+
+Camel Azure CosmosDB uses [ChangeFeed
+pattern](https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed-design-patterns)
+to capture a feed of events and feed them into the Camel in an Async
+manner, something similar to the Change Data Capture (CDC) design
+pattern. However, it doesn’t capture deletions as these are removed from
+the feed as well.
+
+To use the Camel Azure CosmosDB, `containerName` and `databaseName` are
+required. However, there are more options that need to be set to use
+this feature:
+
+-   `leaseDatabaseName`: Sets the lease database where the
+    `leaseContainerName` will be stored. If it is not specified, this
+    component will store the lease container in the same database that
+    is specified in databaseName. It will be auto-created if
+    `createLeaseDatabaseIfNotExists` is set to true.
+
+-   `leaseContainerName`: Sets the lease container which acts as a state
+    storage and coordinates processing the change feed across multiple
+    workers. The lease container can be stored in the same account as
+    the monitored container or in a separate account. It will be
+    auto-created if `createLeaseContainerIfNotExists` is set to true. If
+    not specified, this component will create container called
+    `camel-lease`.
+
+-   `hostName`: Sets the hostname. The host: a host is an application
+    instance that uses the change feed processor to listen for changes.
+    Multiple instances with the same lease configuration can run in
+    parallel, but each instance should have a different instance name.
+    If not specified, this will be a generated random hostname.
+
+-   `changeFeedProcessorOptions`: Sets additional options for the change
+    feed processor.
+
+The consumer will set `List<Map<String,>>` in exchange message body
+which reflect the list of items in a single feed.
+
+### Example:
+
+For example, to listen to the events in `myContainer` container in
+`myDb`:
+
+    from("azure-cosmosdb://myDb/myContainer?leaseDatabaseName=myLeaseDb&createLeaseDatabaseIfNotExists=true&createLeaseContainerIfNotExists=true")
+      .to("mock:result");
+
+## Development Notes (Important)
+
+When developing on this component, you will need to obtain your Azure
+accessKey in order to run the integration tests. In addition to the
+mocked unit tests, you **will need to run the integration tests with
+every change you make or even client upgrade as the Azure client can
+break things even on minor versions upgrade.** To run the integration
+tests, on this component directory, run the following maven command:
+
+    mvn clean install -Dendpoint={{dbaddress}} -DaccessKey={{accessKey}}
+
+Whereby `endpoint` is your Azure CosmosDB endpoint name and `accessKey`
+is the access key being generated from Azure CosmosDB portal.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|clientTelemetryEnabled|Sets the flag to enable client telemetry which will periodically collect database operations aggregation statistics, system information like cpu/memory and send it to cosmos monitoring service, which will be helpful during debugging. DEFAULT value is false indicating this is opt in feature, by default no telemetry collection.|false|boolean|
+|configuration|The component configurations||object|
+|connectionSharingAcrossClientsEnabled|Enables connections sharing across multiple Cosmos Clients. The default is false. When you have multiple instances of Cosmos Client in the same JVM interacting to multiple Cosmos accounts, enabling this allows connection sharing in Direct mode if possible between instances of Cosmos Client. Please note, when setting this option, the connection configuration (e.g., socket timeout config, idle timeout config) of the first instantiated client will be used for all other client instances.|false|boolean|
+|consistencyLevel|Sets the consistency levels supported for Azure Cosmos DB client operations in the Azure Cosmos DB service. The requested ConsistencyLevel must match or be weaker than that provisioned for the database account. Consistency levels by order of strength are STRONG, BOUNDED\_STALENESS, SESSION and EVENTUAL. Refer to consistency level documentation for additional details: https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels|SESSION|object|
+|containerPartitionKeyPath|Sets the container partition key path.||string|
+|contentResponseOnWriteEnabled|Sets the boolean to only return the headers and status code in Cosmos DB response in case of Create, Update and Delete operations on CosmosItem. In Consumer, it is enabled by default because of the ChangeFeed in the consumer that needs this flag to be enabled and thus is shouldn't be overridden. In Producer, it advised to disable it since it reduces the network overhead|true|boolean|
+|cosmosAsyncClient|Inject an external CosmosAsyncClient into the component which provides a client-side logical representation of the Azure Cosmos DB service. This asynchronous client is used to configure and execute requests against the service.||object|
+|createContainerIfNotExists|Sets if the component should create Cosmos container automatically in case it doesn't exist in Cosmos database|false|boolean|
+|createDatabaseIfNotExists|Sets if the component should create Cosmos database automatically in case it doesn't exist in Cosmos account|false|boolean|
+|databaseEndpoint|Sets the Azure Cosmos database endpoint the component will connect to.||string|
+|multipleWriteRegionsEnabled|Sets the flag to enable writes on any regions for geo-replicated database accounts in the Azure Cosmos DB service. When the value of this property is true, the SDK will direct write operations to available writable regions of geo-replicated database account. Writable regions are ordered by PreferredRegions property. Setting the property value to true has no effect until EnableMultipleWriteRegions in DatabaseAccount is also set to true. DEFAULT value is true indicating that writes are directed to available writable regions of geo-replicated database account.|true|boolean|
+|preferredRegions|Sets the comma separated preferred regions for geo-replicated database accounts. For example, East US as the preferred region. When EnableEndpointDiscovery is true and PreferredRegions is non-empty, the SDK will prefer to use the regions in the container in the order they are specified to perform operations.||string|
+|readRequestsFallbackEnabled|Sets whether to allow for reads to go to multiple regions configured on an account of Azure Cosmos DB service. DEFAULT value is true. If this property is not set, the default is true for all Consistency Levels other than Bounded Staleness, The default is false for Bounded Staleness. 1. endpointDiscoveryEnabled is true 2. the Azure Cosmos DB account has more than one region|true|boolean|
+|throughputProperties|Sets throughput of the resources in the Azure Cosmos DB service.||object|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|changeFeedProcessorOptions|Sets the ChangeFeedProcessorOptions to be used. Unless specifically set the default values that will be used are: maximum items per page or FeedResponse: 100 lease renew interval: 17 seconds lease acquire interval: 13 seconds lease expiration interval: 60 seconds feed poll delay: 5 seconds maximum scale count: unlimited||object|
+|createLeaseContainerIfNotExists|Sets if the component should create Cosmos lease container for the consumer automatically in case it doesn't exist in Cosmos database|false|boolean|
+|createLeaseDatabaseIfNotExists|Sets if the component should create Cosmos lease database for the consumer automatically in case it doesn't exist in Cosmos account|false|boolean|
+|hostName|Sets the hostname. The host: a host is an application instance that uses the change feed processor to listen for changes. Multiple instances with the same lease configuration can run in parallel, but each instance should have a different instance name. If not specified, this will be a generated random hostname.||string|
+|leaseContainerName|Sets the lease container which acts as a state storage and coordinates processing the change feed across multiple workers. The lease container can be stored in the same account as the monitored container or in a separate account. It will be auto created if createLeaseContainerIfNotExists is set to true.|camel-lease|string|
+|leaseDatabaseName|Sets the lease database where the leaseContainerName will be stored. If it is not specified, this component will store the lease container in the same database that is specified in databaseName. It will be auto created if createLeaseDatabaseIfNotExists is set to true.||string|
+|itemId|Sets the itemId in case needed for operation on item like delete, replace||string|
+|itemPartitionKey|Sets partition key. Represents a partition key value in the Azure Cosmos DB database service. A partition key identifies the partition where the item is stored in.||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The CosmosDB operation that can be used with this component on the producer.|listDatabases|object|
+|query|An SQL query to execute on a given resources. To learn more about Cosmos SQL API, check this link {link https://docs.microsoft.com/en-us/azure/cosmos-db/sql-query-getting-started}||string|
+|queryRequestOptions|Set additional QueryRequestOptions that can be used with queryItems, queryContainers, queryDatabases, listDatabases, listItems, listContainers operations||object|
+|indexingPolicy|The CosmosDB Indexing Policy that will be set in case of container creation, this option is related to createLeaseContainerIfNotExists and it will be taken into account when the latter is true.||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|accountKey|Sets either a master or readonly key used to perform authentication for accessing resource.||string|
+|credentialType|Determines the credential strategy to adopt|SHARED\_ACCOUNT\_KEY|object|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|databaseName|The name of the Cosmos database that component should connect to. In case you are producing data and have createDatabaseIfNotExists=true, the component will automatically auto create a Cosmos database.||string|
+|containerName|The name of the Cosmos container that component should connect to. In case you are producing data and have createContainerIfNotExists=true, the component will automatically auto create a Cosmos container.||string|
+|clientTelemetryEnabled|Sets the flag to enable client telemetry which will periodically collect database operations aggregation statistics, system information like cpu/memory and send it to cosmos monitoring service, which will be helpful during debugging. DEFAULT value is false indicating this is opt in feature, by default no telemetry collection.|false|boolean|
+|connectionSharingAcrossClientsEnabled|Enables connections sharing across multiple Cosmos Clients. The default is false. When you have multiple instances of Cosmos Client in the same JVM interacting to multiple Cosmos accounts, enabling this allows connection sharing in Direct mode if possible between instances of Cosmos Client. Please note, when setting this option, the connection configuration (e.g., socket timeout config, idle timeout config) of the first instantiated client will be used for all other client instances.|false|boolean|
+|consistencyLevel|Sets the consistency levels supported for Azure Cosmos DB client operations in the Azure Cosmos DB service. The requested ConsistencyLevel must match or be weaker than that provisioned for the database account. Consistency levels by order of strength are STRONG, BOUNDED\_STALENESS, SESSION and EVENTUAL. Refer to consistency level documentation for additional details: https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels|SESSION|object|
+|containerPartitionKeyPath|Sets the container partition key path.||string|
+|contentResponseOnWriteEnabled|Sets the boolean to only return the headers and status code in Cosmos DB response in case of Create, Update and Delete operations on CosmosItem. In Consumer, it is enabled by default because of the ChangeFeed in the consumer that needs this flag to be enabled and thus is shouldn't be overridden. In Producer, it advised to disable it since it reduces the network overhead|true|boolean|
+|cosmosAsyncClient|Inject an external CosmosAsyncClient into the component which provides a client-side logical representation of the Azure Cosmos DB service. This asynchronous client is used to configure and execute requests against the service.||object|
+|createContainerIfNotExists|Sets if the component should create Cosmos container automatically in case it doesn't exist in Cosmos database|false|boolean|
+|createDatabaseIfNotExists|Sets if the component should create Cosmos database automatically in case it doesn't exist in Cosmos account|false|boolean|
+|databaseEndpoint|Sets the Azure Cosmos database endpoint the component will connect to.||string|
+|multipleWriteRegionsEnabled|Sets the flag to enable writes on any regions for geo-replicated database accounts in the Azure Cosmos DB service. When the value of this property is true, the SDK will direct write operations to available writable regions of geo-replicated database account. Writable regions are ordered by PreferredRegions property. Setting the property value to true has no effect until EnableMultipleWriteRegions in DatabaseAccount is also set to true. DEFAULT value is true indicating that writes are directed to available writable regions of geo-replicated database account.|true|boolean|
+|preferredRegions|Sets the comma separated preferred regions for geo-replicated database accounts. For example, East US as the preferred region. When EnableEndpointDiscovery is true and PreferredRegions is non-empty, the SDK will prefer to use the regions in the container in the order they are specified to perform operations.||string|
+|readRequestsFallbackEnabled|Sets whether to allow for reads to go to multiple regions configured on an account of Azure Cosmos DB service. DEFAULT value is true. If this property is not set, the default is true for all Consistency Levels other than Bounded Staleness, The default is false for Bounded Staleness. 1. endpointDiscoveryEnabled is true 2. the Azure Cosmos DB account has more than one region|true|boolean|
+|throughputProperties|Sets throughput of the resources in the Azure Cosmos DB service.||object|
+|changeFeedProcessorOptions|Sets the ChangeFeedProcessorOptions to be used. Unless specifically set the default values that will be used are: maximum items per page or FeedResponse: 100 lease renew interval: 17 seconds lease acquire interval: 13 seconds lease expiration interval: 60 seconds feed poll delay: 5 seconds maximum scale count: unlimited||object|
+|createLeaseContainerIfNotExists|Sets if the component should create Cosmos lease container for the consumer automatically in case it doesn't exist in Cosmos database|false|boolean|
+|createLeaseDatabaseIfNotExists|Sets if the component should create Cosmos lease database for the consumer automatically in case it doesn't exist in Cosmos account|false|boolean|
+|hostName|Sets the hostname. The host: a host is an application instance that uses the change feed processor to listen for changes. Multiple instances with the same lease configuration can run in parallel, but each instance should have a different instance name. If not specified, this will be a generated random hostname.||string|
+|leaseContainerName|Sets the lease container which acts as a state storage and coordinates processing the change feed across multiple workers. The lease container can be stored in the same account as the monitored container or in a separate account. It will be auto created if createLeaseContainerIfNotExists is set to true.|camel-lease|string|
+|leaseDatabaseName|Sets the lease database where the leaseContainerName will be stored. If it is not specified, this component will store the lease container in the same database that is specified in databaseName. It will be auto created if createLeaseDatabaseIfNotExists is set to true.||string|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|itemId|Sets the itemId in case needed for operation on item like delete, replace||string|
+|itemPartitionKey|Sets partition key. Represents a partition key value in the Azure Cosmos DB database service. A partition key identifies the partition where the item is stored in.||string|
+|operation|The CosmosDB operation that can be used with this component on the producer.|listDatabases|object|
+|query|An SQL query to execute on a given resources. To learn more about Cosmos SQL API, check this link {link https://docs.microsoft.com/en-us/azure/cosmos-db/sql-query-getting-started}||string|
+|queryRequestOptions|Set additional QueryRequestOptions that can be used with queryItems, queryContainers, queryDatabases, listDatabases, listItems, listContainers operations||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|indexingPolicy|The CosmosDB Indexing Policy that will be set in case of container creation, this option is related to createLeaseContainerIfNotExists and it will be taken into account when the latter is true.||object|
+|accountKey|Sets either a master or readonly key used to perform authentication for accessing resource.||string|
+|credentialType|Determines the credential strategy to adopt|SHARED\_ACCOUNT\_KEY|object|

camel-azure-eventhubs.md

@@ -0,0 +1,271 @@
+# Azure-eventhubs
+
+**Since Camel 3.5**
+
+**Both producer and consumer are supported**
+
+The Azure Event Hubs used to integrate [Azure Event
+Hubs](https://azure.microsoft.com/en-us/services/event-hubs/) using
+[AMQP
+protocol](https://en.wikipedia.org/wiki/Advanced_Message_Queuing_Protocol).
+Azure EventHubs is a highly scalable publish-subscribe service that can
+ingest millions of events per second and stream them to multiple
+consumers.
+
+Besides AMQP protocol support, Event Hubs as well supports Kafka and
+HTTPS protocols. Therefore, you can also use the [Camel
+Kafka](#components::kafka-component.adoc) component to produce and
+consume to Azure Event Hubs. You can lean more
+[here](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-quickstart-kafka-enabled-event-hubs).
+
+Prerequisites
+
+You must have a valid Windows Azure Event Hubs account. More information
+is available at [Azure Documentation
+Portal](https://docs.microsoft.com/azure/).
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-azure-eventhubs</artifactId>
+        <version>x.x.x</version>
+      <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# URI Format
+
+    azure-eventhubs://[namespace/eventHubName][?options]
+
+In case you supply the `connectionString`, `namespace` and
+`eventHubName` are not required as these options already included in the
+`connectionString`
+
+# Authentication Information
+
+You have three different Credential Types: AZURE\_IDENTITY,
+TOKEN\_CREDENTIAL and CONNECTION\_STRING. You can also provide a client
+instance yourself. To use this component, you have three options to
+provide the required Azure authentication information:
+
+**CONNECTION\_STRING**:
+
+-   Provide `sharedAccessName` and `sharedAccessKey` for your Azure
+    Event Hubs account. The sharedAccessKey can be generated through
+    your Event Hubs Azure portal.
+
+-   Provide `connectionString` string, if you provide the connection
+    string, you don’t supply `namespace`, `eventHubName`,
+    `sharedAccessKey` and `sharedAccessName` as these data already
+    included in the `connectionString`, therefore is the simplest option
+    to get started. Learn more
+    [here](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string)
+    on how to generate the connection string.
+
+**TOKEN\_CREDENTIAL**:
+
+-   Provide an implementation of
+    `com.azure.core.credential.TokenCredential` into the Camel’s
+    Registry, e.g., using the
+    `com.azure.identity.DefaultAzureCredentialBuilder().build();` API.
+    See the documentation [here about Azure-AD
+    authentication](https://docs.microsoft.com/en-us/azure/active-directory/authentication/overview-authentication).
+
+AZURE\_IDENTITY: - This will use
+`com.azure.identity.DefaultAzureCredentialBuilder().build();` instance.
+This will follow the Default Azure Credential Chain. See the
+documentation [here about Azure-AD
+authentication](https://docs.microsoft.com/en-us/azure/active-directory/authentication/overview-authentication).
+
+**Client instance**:
+
+-   Provide a
+    [EventHubProducerAsyncClient](https://docs.microsoft.com/en-us/java/api/com.azure.messaging.eventhubs.eventhubproducerasyncclient?view=azure-java-stable)
+    instance which can be provided into `producerAsyncClient`. However,
+    this is **only possible for camel producer**, for the camel
+    consumer, is not possible to inject the client due to some design
+    constraint by the `EventProcessorClient`.
+
+# Checkpoint Store Information
+
+A checkpoint store stores and retrieves partition ownership information
+and checkpoint details for each partition in a given consumer group of
+an event hub instance. Users are not meant to implement a
+CheckpointStore. Users are expected to choose existing implementations
+of this interface, instantiate it, and pass it to the component through
+`checkpointStore` option. Users are not expected to use any of the
+methods on a checkpoint store, these are used internally by the client.
+
+Having said that, if the user does not pass any `CheckpointStore`
+implementation, the component will fall back to use
+[`BlobCheckpointStore`](https://docs.microsoft.com/en-us/javascript/api/@azure/eventhubs-checkpointstore-blob/blobcheckpointstore?view=azure-node-latest)
+to store the checkpoint info in the Azure Blob Storage account. If you
+chose to use the default `BlobCheckpointStore`, you will need to supply
+the following options:
+
+-   `blobAccountName`: It sets Azure account name to be used for
+    authentication with azure blob services.
+
+-   `blobAccessKey`: It sets the access key for the associated azure
+    account name to be used for authentication with azure blob services.
+
+-   `blobContainerName`: It sets the blob container that shall be used
+    by the BlobCheckpointStore to store the checkpoint offsets.
+
+# Async Consumer and Producer
+
+This component implements the async Consumer and producer.
+
+This allows camel route to consume and produce events asynchronously
+without blocking any threads.
+
+# Usage
+
+For example, to consume event from EventHub, use the following snippet:
+
+    from("azure-eventhubs:/camel/camelHub?sharedAccessName=SASaccountName&sharedAccessKey=SASaccessKey&blobAccountName=accountName&blobAccessKey=accessKey&blobContainerName=containerName")
+      .to("file://queuedirectory");
+
+## Message body type
+
+The component’s producer expects the data in the message body to be in
+`byte[]`. This allows the user to utilize Camel TypeConverter to
+marshal/unmarshal data with ease. The same goes as well for the
+component’s consumer, it will set the encoded data as `byte[]` in the
+message body.
+
+## Automatic detection of EventHubProducerAsyncClient client in registry
+
+The component is capable of detecting the presence of an
+EventHubProducerAsyncClient bean into the registry. If it’s the only
+instance of that type, it will be used as the client, and you won’t have
+to define it as uri parameter, like the example above. This may be
+really useful for smarter configuration of the endpoint.
+
+## Consumer Example
+
+The example below will unmarshal the events that were originally
+produced in JSON:
+
+    from("azure-eventhubs:?connectionString=RAW({{connectionString}})"&blobContainerName=containerTest&eventPosition=#eventPosition"
+        +"&blobAccountName={{blobAccountName}}&blobAccessKey=RAW({{blobAccessKey}})")
+    .unmarshal().json(JsonLibrary.Jackson)
+    .to(result);
+
+## Producer Example
+
+The example below will send events as String to EventHubs:
+
+    from("direct:start")
+    .process(exchange -> {
+            exchange.getIn().setHeader(EventHubsConstants.PARTITION_ID, firstPartition);
+            exchange.getIn().setBody("test event");
+    })
+    .to("azure-eventhubs:?connectionString=RAW({{connectionString}})"
+
+Also, the component supports as well **aggregation** of messages by
+sending events as **iterable** of either Exchanges/Messages or normal
+data (e.g.: list of Strings). For example:
+
+    from("direct:start")
+    .process(exchange -> {
+            final List<String> messages = new LinkedList<>();
+            messages.add("Test String Message 1");
+            messages.add("Test String Message 2");
+    
+            exchange.getIn().setHeader(EventHubsConstants.PARTITION_ID, firstPartition);
+            exchange.getIn().setBody(messages);
+    })
+    .to("azure-eventhubs:?connectionString=RAW({{connectionString}})"
+
+## Azure-AD Authentication example
+
+The example below makes use of the Azure-AD authentication. See
+[here](https://docs.microsoft.com/en-us/java/api/overview/azure/identity-readme?view=azure-java-stable#environment-variables)
+about what environment variables you need to set for this to work:
+
+    @BindToRegistry("myTokenCredential")
+    public com.azure.core.credential.TokenCredential myTokenCredential() {
+        return com.azure.identity.DefaultAzureCredentialBuilder().build();
+    }
+    
+    from("direct:start")
+    .to("azure-eventhubs:namespace/eventHubName?tokenCredential=#myTokenCredential&credentialType=TOKEN_CREDENTIAL)"
+
+## Development Notes (Important)
+
+When developing on this component, you will need to obtain your Azure
+accessKey to run the integration tests. In addition to the mocked unit
+tests, you **will need to run the integration tests with every change
+you make or even client upgrade as the Azure client can break things
+even on minor versions upgrade.** To run the integration tests, on this
+component directory, run the following maven command:
+
+    mvn verify -DconnectionString=string -DblobAccountName=blob -DblobAccessKey=key
+
+Whereby `blobAccountName` is your Azure account name and `blobAccessKey`
+is the access key being generated from Azure portal and
+`connectionString` is the eventHub connection string.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|amqpRetryOptions|Sets the retry policy for EventHubAsyncClient. If not specified, the default retry options are used.||object|
+|amqpTransportType|Sets the transport type by which all the communication with Azure Event Hubs occurs. Default value is AmqpTransportType#AMQP.|AMQP|object|
+|configuration|The component configurations||object|
+|blobAccessKey|In case you chose the default BlobCheckpointStore, this sets access key for the associated azure account name to be used for authentication with azure blob services.||string|
+|blobAccountName|In case you chose the default BlobCheckpointStore, this sets Azure account name to be used for authentication with azure blob services.||string|
+|blobContainerName|In case you chose the default BlobCheckpointStore, this sets the blob container that shall be used by the BlobCheckpointStore to store the checkpoint offsets.||string|
+|blobStorageSharedKeyCredential|In case you chose the default BlobCheckpointStore, StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information.||object|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|checkpointBatchSize|Sets the batch size between each checkpoint updates. Works jointly with checkpointBatchTimeout.|500|integer|
+|checkpointBatchTimeout|Sets the batch timeout between each checkpoint updates. Works jointly with checkpointBatchSize.|5000|integer|
+|checkpointStore|Sets the CheckpointStore the EventProcessorClient will use for storing partition ownership and checkpoint information. Users can, optionally, provide their own implementation of CheckpointStore which will store ownership and checkpoint information. By default it set to use com.azure.messaging.eventhubs.checkpointstore.blob.BlobCheckpointStore which stores all checkpoint offsets into Azure Blob Storage.|BlobCheckpointStore|object|
+|consumerGroupName|Sets the name of the consumer group this consumer is associated with. Events are read in the context of this group. The name of the consumer group that is created by default is {code $Default}.|$Default|string|
+|eventPosition|Sets the map containing the event position to use for each partition if a checkpoint for the partition does not exist in CheckpointStore. This map is keyed off of the partition id. If there is no checkpoint in CheckpointStore and there is no entry in this map, the processing of the partition will start from {link EventPosition#latest() latest} position.||object|
+|prefetchCount|Sets the count used by the receiver to control the number of events the Event Hub consumer will actively receive and queue locally without regard to whether a receive operation is currently active.|500|integer|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|partitionId|Sets the identifier of the Event Hub partition that the events will be sent to. If the identifier is not specified, the Event Hubs service will be responsible for routing events that are sent to an available partition.||string|
+|partitionKey|Sets a hashing key to be provided for the batch of events, which instructs the Event Hubs service to map this key to a specific partition. The selection of a partition is stable for a given partition hashing key. Should any other batches of events be sent using the same exact partition hashing key, the Event Hubs service will route them all to the same partition. This should be specified only when there is a need to group events by partition, but there is flexibility into which partition they are routed. If ensuring that a batch of events is sent only to a specific partition, it is recommended that the {link #setPartitionId(String) identifier of the position be specified directly} when sending the batch.||string|
+|producerAsyncClient|Sets the EventHubProducerAsyncClient.An asynchronous producer responsible for transmitting EventData to a specific Event Hub, grouped together in batches. Depending on the options specified when creating an {linkEventDataBatch}, the events may be automatically routed to an available partition or specific to a partition. Use by this component to produce the data in camel producer.||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|connectionString|Instead of supplying namespace, sharedAccessKey, sharedAccessName ... etc, you can just supply the connection string for your eventHub. The connection string for EventHubs already include all the necessary information to connection to your EventHub. To learn on how to generate the connection string, take a look at this documentation: https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string||string|
+|credentialType|Determines the credential strategy to adopt|CONNECTION\_STRING|object|
+|sharedAccessKey|The generated value for the SharedAccessName.||string|
+|sharedAccessName|The name you chose for your EventHubs SAS keys.||string|
+|tokenCredential|Still another way of authentication (beside supplying namespace, sharedAccessKey, sharedAccessName or connection string) is through Azure-AD authentication using an implementation instance of TokenCredential.||object|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|namespace|EventHubs namespace created in Azure Portal.||string|
+|eventHubName|EventHubs name under a specific namespace.||string|
+|amqpRetryOptions|Sets the retry policy for EventHubAsyncClient. If not specified, the default retry options are used.||object|
+|amqpTransportType|Sets the transport type by which all the communication with Azure Event Hubs occurs. Default value is AmqpTransportType#AMQP.|AMQP|object|
+|blobAccessKey|In case you chose the default BlobCheckpointStore, this sets access key for the associated azure account name to be used for authentication with azure blob services.||string|
+|blobAccountName|In case you chose the default BlobCheckpointStore, this sets Azure account name to be used for authentication with azure blob services.||string|
+|blobContainerName|In case you chose the default BlobCheckpointStore, this sets the blob container that shall be used by the BlobCheckpointStore to store the checkpoint offsets.||string|
+|blobStorageSharedKeyCredential|In case you chose the default BlobCheckpointStore, StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information.||object|
+|checkpointBatchSize|Sets the batch size between each checkpoint updates. Works jointly with checkpointBatchTimeout.|500|integer|
+|checkpointBatchTimeout|Sets the batch timeout between each checkpoint updates. Works jointly with checkpointBatchSize.|5000|integer|
+|checkpointStore|Sets the CheckpointStore the EventProcessorClient will use for storing partition ownership and checkpoint information. Users can, optionally, provide their own implementation of CheckpointStore which will store ownership and checkpoint information. By default it set to use com.azure.messaging.eventhubs.checkpointstore.blob.BlobCheckpointStore which stores all checkpoint offsets into Azure Blob Storage.|BlobCheckpointStore|object|
+|consumerGroupName|Sets the name of the consumer group this consumer is associated with. Events are read in the context of this group. The name of the consumer group that is created by default is {code $Default}.|$Default|string|
+|eventPosition|Sets the map containing the event position to use for each partition if a checkpoint for the partition does not exist in CheckpointStore. This map is keyed off of the partition id. If there is no checkpoint in CheckpointStore and there is no entry in this map, the processing of the partition will start from {link EventPosition#latest() latest} position.||object|
+|prefetchCount|Sets the count used by the receiver to control the number of events the Event Hub consumer will actively receive and queue locally without regard to whether a receive operation is currently active.|500|integer|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|partitionId|Sets the identifier of the Event Hub partition that the events will be sent to. If the identifier is not specified, the Event Hubs service will be responsible for routing events that are sent to an available partition.||string|
+|partitionKey|Sets a hashing key to be provided for the batch of events, which instructs the Event Hubs service to map this key to a specific partition. The selection of a partition is stable for a given partition hashing key. Should any other batches of events be sent using the same exact partition hashing key, the Event Hubs service will route them all to the same partition. This should be specified only when there is a need to group events by partition, but there is flexibility into which partition they are routed. If ensuring that a batch of events is sent only to a specific partition, it is recommended that the {link #setPartitionId(String) identifier of the position be specified directly} when sending the batch.||string|
+|producerAsyncClient|Sets the EventHubProducerAsyncClient.An asynchronous producer responsible for transmitting EventData to a specific Event Hub, grouped together in batches. Depending on the options specified when creating an {linkEventDataBatch}, the events may be automatically routed to an available partition or specific to a partition. Use by this component to produce the data in camel producer.||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|connectionString|Instead of supplying namespace, sharedAccessKey, sharedAccessName ... etc, you can just supply the connection string for your eventHub. The connection string for EventHubs already include all the necessary information to connection to your EventHub. To learn on how to generate the connection string, take a look at this documentation: https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string||string|
+|credentialType|Determines the credential strategy to adopt|CONNECTION\_STRING|object|
+|sharedAccessKey|The generated value for the SharedAccessName.||string|
+|sharedAccessName|The name you chose for your EventHubs SAS keys.||string|
+|tokenCredential|Still another way of authentication (beside supplying namespace, sharedAccessKey, sharedAccessName or connection string) is through Azure-AD authentication using an implementation instance of TokenCredential.||object|

camel-azure-files.md

@@ -0,0 +1,430 @@
+# Azure-files
+
+**Since Camel 3.22**
+
+**Both producer and consumer are supported**
+
+This component provides access to Azure Files.
+
+This is preview component, therefore, anything can change in future
+releases (features and behavior can be changed, modified or even dropped
+without notice). At the same time it is consolidated enough, sparingly
+documented, a few users reported it was working in their environment,
+and it is ready for wider feedback.
+
+When consuming from remote files server, make sure you read the section
+titled *Consuming Files* further below for details related to consuming
+files.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-azure-files</artifactId>
+        <version>x.y.z</version>
+        <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# Endpoint URI Format
+
+    azure-files://account[.file.core.windows.net][:port]/share[/directory]
+
+Where **directory** represents the underlying directory. The directory
+is a relative path and does not include the share name. The relative
+path can contain nested folders, such as `inbox/spam`. It defaults to
+the share root directory.
+
+The `autoCreate` option is supported for the directory; when consumer or
+producer starts, there’s an additional operation performed to create the
+directory configured for the endpoint. The default value for
+`autoCreate` is `true`. On the contrary, the share must exist; it is not
+automatically created.
+
+If no **port** number is provided, Camel will provide default values
+according to the protocol (https 443).
+
+You can append query options to the URI in the following format
+`?option=value&option2=value&...`.
+
+To use this component, you have multiple options to provide the required
+Azure authentication information:
+
+-   Via Azure Identity, when specifying `credentialType=AZURE_IDENTITY`
+    and providing required [environment
+    variables](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/identity/azure-identity#environment-variables).
+    This enables service principal (e.g. app registration)
+    authentication with secret/certificate as well as username password.
+
+-   Via shared storage account key, when specifying
+    `credentialType=SHARED_ACCOUNT_KEY` and providing `sharedKey` for
+    your Azure account, this is the simplest way to get started. The
+    sharedKey can be generated through your Azure portal.
+
+-   Via Azure SAS, when specifying `credentialType=AZURE_SAS` and
+    providing a SAS Token parameter through the `token` parameter.
+
+## Endpoint URI Examples
+
+    azure-files://camelazurefiles.file.core.windows.net/samples?sv=2022-11-02&ss=f&srt=sco&sp=rwdlc&se=2023-06-18T22:29:13Z&st=2023-06-05T14:29:13Z&spr=https&sig=MPsMh8zci0v3To7IT9SKdaFGZV8ezno63m9C8s9bdVQ%3D
+    
+    azure-files://camelazurefiles/samples/inbox/spam?sharedKey=FAKE502UyuBD...3Z%2BASt9dCmJg%3D%3D&delete=true
+
+# Paths
+
+The path separator is `/`. The absolute paths start with the path
+separator. The absolute paths do not include the share name, and they
+are relative to the share root rather than to the endpoint starting
+directory.
+
+**NOTE:** At some places, namely logs of used libraries, OS-specific
+path separator appears, and the relative paths are relative to the share
+root (rather than to the current working directory or to the endpoint
+starting directory) so interpret them with a grain of salt.
+
+# Concurrency
+
+This component does not support concurrency on its endpoints.
+
+# More Information
+
+This component mimics the FTP component. So, there are more samples and
+details on the FTP component page.
+
+This component uses the Azure Java SDK libraries for the actual work.
+
+# Consuming Files
+
+The remote consumer will by default leave the consumed files untouched
+on the remote cloud files server. You have to configure it explicitly if
+you want it to delete the files or move them to another location. For
+example, you can use `delete=true` to delete the files, or use
+`move=.done` to move the files into `.done` sub directory.
+
+In Camel, the `.`-prefixed folders are excluded from recursive polling.
+
+The regular File consumer is different as it will by default move files
+to a `.camel` sub directory. The reason Camel does **not** do this by
+default for the remote consumer is that it may lack permissions by
+default to be able to move or delete files.
+
+## Body Type Options
+
+For each matching file, the consumer sends to the Camel exchange a
+message with a selected body type:
+
+-   `byte[]` by default
+
+-   `java.io.InputStream` if `streamDownload=true` is configured
+
+-   `java.io.File` if `localWorkDirectory` is configured
+
+The body type configuration should be tuned to fit available resources,
+performance targets, route processors, caching, resuming, etc.
+
+## Limitations
+
+The option **readLock** can be used to force Camel **not** to consume
+files that are currently in the progress of being written. However, this
+option is turned off by default, as it requires that the user has write
+access. See the endpoint options table for more details about read
+locks.  
+There are other solutions to avoid consuming files that are currently
+being written; for instance, you can write to a temporary destination
+and move the file after it has been written.
+
+For the `readLock=changed`, it relies only on the last modified;
+furthermore a precision finer than 5 seconds might be problematic.
+
+When moving files using `move` or `preMove` option, the files are
+restricted to the share. That prevents consumer from moving files
+outside the endpoint share.
+
+## Exchange Properties
+
+The consumer sets the following exchange properties
+
+<table>
+<colgroup>
+<col style="width: 50%" />
+<col style="width: 50%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Header</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>CamelBatchIndex</code></p></td>
+<td style="text-align: left;"><p>The current index out of total number
+of files being consumed in this batch.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>CamelBatchSize</code></p></td>
+<td style="text-align: left;"><p>The total number of files being
+consumed in this batch.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>CamelBatchComplete</code></p></td>
+<td style="text-align: left;"><p>True if there are no more files in this
+batch.</p></td>
+</tr>
+</tbody>
+</table>
+
+# Producing Files
+
+The Files producer is optimized for two body types:
+
+-   `java.io.InputStream` if `CamelFileLength` header is set
+
+-   `byte[]`
+
+In either case, the remote file size is allocated and then rewritten
+with body content. Any inconsistency between declared file length and
+stream length results in a corrupted remote file.
+
+## Limitations
+
+The underlying Azure Files service does not allow growing files. The
+file length must be known at its creation time, consequently:
+
+-   `CamelFileLength` header has an important meaning even for
+    producers.
+
+-   No appending mode is supported.
+
+# About Timeouts
+
+You can use the `connectTimeout` option to set a timeout in millis to
+connect or disconnect.
+
+The `timeout` option only applies as the data timeout in millis.
+
+The meta-data operations timeout is minimum of: `readLockCheckInterval`,
+`timeout` and 20\_000 millis.
+
+For now, the file upload has no timeout. During the upload, the
+underlying library could log timeout warnings. They are recoverable and
+upload could continue.
+
+# Using Local Work Directory
+
+Camel supports consuming from remote files servers and downloading the
+files directly into a local work directory. This avoids reading the
+entire remote file content into memory as it is streamed directly into
+the local file using `FileOutputStream`.
+
+Camel will store to a local file with the same name as the remote file,
+though with `.inprogress` as an extension while the file is being
+downloaded. Afterward, the file is renamed to remove the `.inprogress`
+suffix. And finally, when the Exchange is complete, the local file is
+deleted.
+
+So if you want to download files from a remote files server and store it
+as local files, then you need to route to a file endpoint such as:
+
+    from("azure-files://...&localWorkDirectory=/tmp").to("file://inbox");
+
+The route above is ultra efficient as it avoids reading the entire file
+content into memory. It will download the remote file directly to a
+local file stream. The `java.io.File` handle is then used as the
+Exchange body. The file producer leverages this fact and can work
+directly on the work file `java.io.File` handle and perform a
+`java.io.File.rename` to the target filename. As Camel knows it’s a
+local work file, it can optimize and use a rename instead of a file
+copy, as the work file is meant to be deleted anyway.
+
+# Custom Filtering
+
+Camel supports pluggable filtering strategies. This strategy it to use
+the build in `org.apache.camel.component.file.GenericFileFilter` in
+Java. You can then configure the endpoint with such a filter to skip
+certain filters before being processed.
+
+In the sample, we have built our own filter that only accepts files
+starting with the report in the filename.
+
+And then we can configure our route using the **filter** attribute to
+reference our filter (using `#` notation) that we have defined in the
+spring XML file:
+
+The accept(file) file argument has properties:
+
+-   endpoint path: the share name such as `/samples`
+
+-   relative path: a path to the file such as `subdir/a file`
+
+-   directory: `true` if a directory
+
+-   file length: if not a directory, then a length of the file in bytes
+
+# Filtering using ANT path matcher
+
+The ANT path matcher is a filter shipped out-of-the-box in the
+**camel-spring** jar. So you need to depend on **camel-spring** if you
+are using Maven.  
+The reason is that we leverage Spring’s
+[AntPathMatcher](http://static.springsource.org/spring/docs/3.0.x/api/org/springframework/util/AntPathMatcher.html)
+to do the actual matching.
+
+The file paths are matched with the following rules:
+
+-   `?` matches one character
+
+-   `*` matches zero or more characters
+
+-   `**` matches zero or more directories in a path
+
+The sample below demonstrates how to use it:
+
+    from("azure-files://...&antInclude=**/*.txt").to("...");
+
+# Using a Proxy
+
+Consult the [underlying
+library](https://learn.microsoft.com/en-us/azure/developer/java/sdk/proxying)
+documentation.
+
+# Consuming a single file using a fixed name
+
+Unlike FTP component that features a special combination of options:
+
+-   `useList=false`
+
+-   `fileName=myFileName.txt`
+
+-   `ignoreFileNotFoundOrPermissionError=true`
+
+to optimize *the single file using a fixed name* use case, it is
+necessary to fall back to regular filters (i.e. the list permission is
+needed).
+
+# Debug logging
+
+This component has log level **TRACE** that can be helpful if you have
+problems.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|account|The account to use||string|
+|share|The share to use||string|
+|port|Port of the FTP server||integer|
+|directoryName|The starting directory||string|
+|credentialType|Determines the credential strategy to adopt|SHARED\_ACCOUNT\_KEY|object|
+|disconnect|Whether or not to disconnect from remote FTP server right after use. Disconnect will only disconnect the current connection to the FTP server. If you have a consumer which you want to stop, then you need to stop the consumer/route instead.|false|boolean|
+|doneFileName|Producer: If provided, then Camel will write a 2nd done file when the original file has been written. The done file will be empty. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders. The done file will always be written in the same folder as the original file. Consumer: If provided, Camel will only consume files if a done file exists. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders.The done file is always expected in the same folder as the original file. Only ${file.name} and ${file.name.next} is supported as dynamic placeholders.||string|
+|fileName|Use Expression such as File Language to dynamically set the filename. For consumers, it's used as a filename filter. For producers, it's used to evaluate the filename to write. If an expression is set, it take precedence over the CamelFileName header. (Note: The header itself can also be an Expression). The expression options support both String and Expression types. If the expression is a String type, it is always evaluated using the File Language. If the expression is an Expression type, the specified Expression type is used - this allows you, for instance, to use OGNL expressions. For the consumer, you can use it to filter filenames, so you can for instance consume today's file using the File Language syntax: mydata-${date:now:yyyyMMdd}.txt. The producers support the CamelOverruleFileName header which takes precedence over any existing CamelFileName header; the CamelOverruleFileName is a header that is used only once, and makes it easier as this avoids to temporary store CamelFileName and have to restore it afterwards.||string|
+|sharedKey|Shared key (storage account key)||string|
+|delete|If true, the file will be deleted after it is processed successfully.|false|boolean|
+|moveFailed|Sets the move failure expression based on Simple language. For example, to move files into a .error subdirectory use: .error. Note: When moving the files to the fail location Camel will handle the error and will not pick up the file again.||string|
+|noop|If true, the file is not moved or deleted in any way. This option is good for readonly data, or for ETL type requirements. If noop=true, Camel will set idempotent=true as well, to avoid consuming the same files over and over again.|false|boolean|
+|preMove|Expression (such as File Language) used to dynamically set the filename when moving it before processing. For example to move in-progress files into the order directory set this value to order.||string|
+|preSort|When pre-sort is enabled then the consumer will sort the file and directory names during polling, that was retrieved from the file system. You may want to do this in case you need to operate on the files in a sorted order. The pre-sort is executed before the consumer starts to filter, and accept files to process by Camel. This option is default=false meaning disabled.|false|boolean|
+|recursive|If a directory, will look for files in all the sub-directories as well.|false|boolean|
+|resumeDownload|Configures whether resume download is enabled. In addition the options localWorkDirectory must be configured so downloaded files are stored in a local directory, which is required to support resuming of downloads.|false|boolean|
+|sendEmptyMessageWhenIdle|If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.|false|boolean|
+|streamDownload|Sets the download method to use when not using a local working directory. If set to true, the remote files are streamed to the route as they are read. When set to false, the remote files are loaded into memory before being sent into the route. If enabling this option then you must set stepwise=false as both cannot be enabled at the same time.|false|boolean|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|download|Whether the FTP consumer should download the file. If this option is set to false, then the message body will be null, but the consumer will still trigger a Camel Exchange that has details about the file such as file name, file size, etc. It's just that the file will not be downloaded.|false|boolean|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|inProgressRepository|A pluggable in-progress repository org.apache.camel.spi.IdempotentRepository. The in-progress repository is used to account the current in progress files being consumed. By default a memory based repository is used.||object|
+|localWorkDirectory|When consuming, a local work directory can be used to store the remote file content directly in local files, to avoid loading the content into memory. This is beneficial, if you consume a very big remote file and thus can conserve memory.||string|
+|onCompletionExceptionHandler|To use a custom org.apache.camel.spi.ExceptionHandler to handle any thrown exceptions that happens during the file on completion process where the consumer does either a commit or rollback. The default implementation will log any exception at WARN level and ignore.||object|
+|pollStrategy|A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.||object|
+|processStrategy|A pluggable org.apache.camel.component.file.GenericFileProcessStrategy allowing you to implement your own readLock option or similar. Can also be used when special conditions must be met before a file can be consumed, such as a special ready file exists. If this option is set then the readLock option does not apply.||object|
+|checksumFileAlgorithm|If provided, then Camel will write a checksum file when the original file has been written. The checksum file will contain the checksum created with the provided algorithm for the original file. The checksum file will always be written in the same folder as the original file.||string|
+|fileExist|What to do if a file already exists with the same name. Override, which is the default, replaces the existing file. - Append - adds content to the existing file. - Fail - throws a GenericFileOperationException, indicating that there is already an existing file. - Ignore - silently ignores the problem and does not override the existing file, but assumes everything is okay. - Move - option requires to use the moveExisting option to be configured as well. The option eagerDeleteTargetFile can be used to control what to do if an moving the file, and there exists already an existing file, otherwise causing the move operation to fail. The Move option will move any existing files, before writing the target file. - TryRename is only applicable if tempFileName option is in use. This allows to try renaming the file from the temporary name to the actual name, without doing any exists check. This check may be faster on some file systems and especially FTP servers.|Override|object|
+|flatten|Flatten is used to flatten the file name path to strip any leading paths, so it's just the file name. This allows you to consume recursively into sub-directories, but when you eg write the files to another directory they will be written in a single directory. Setting this to true on the producer enforces that any file name in CamelFileName header will be stripped for any leading paths.|false|boolean|
+|jailStartingDirectory|Used for jailing (restricting) writing files to the starting directory (and sub) only. This is enabled by default to not allow Camel to write files to outside directories (to be more secured out of the box). You can turn this off to allow writing files to directories outside the starting directory, such as parent or root folders.|true|boolean|
+|tempFileName|The same as tempPrefix option but offering a more fine grained control on the naming of the temporary filename as it uses the File Language. The location for tempFilename is relative to the final file location in the option 'fileName', not the target directory in the base uri. For example if option fileName includes a directory prefix: dir/finalFilename then tempFileName is relative to that subdirectory dir.||string|
+|tempPrefix|This option is used to write the file using a temporary name and then, after the write is complete, rename it to the real name. Can be used to identify files being written and also avoid consumers (not using exclusive read locks) reading in progress files. Is often used by FTP when uploading big files.||string|
+|allowNullBody|Used to specify if a null body is allowed during file writing. If set to true then an empty file will be created, when set to false, and attempting to send a null body to the file component, a GenericFileWriteException of 'Cannot write null body to file.' will be thrown. If the fileExist option is set to 'Override', then the file will be truncated, and if set to append the file will remain unchanged.|false|boolean|
+|disconnectOnBatchComplete|Whether or not to disconnect from remote FTP server right after a Batch upload is complete. disconnectOnBatchComplete will only disconnect the current connection to the FTP server.|false|boolean|
+|eagerDeleteTargetFile|Whether or not to eagerly delete any existing target file. This option only applies when you use fileExists=Override and the tempFileName option as well. You can use this to disable (set it to false) deleting the target file before the temp file is written. For example you may write big files and want the target file to exists during the temp file is being written. This ensure the target file is only deleted until the very last moment, just before the temp file is being renamed to the target filename. This option is also used to control whether to delete any existing files when fileExist=Move is enabled, and an existing file exists. If this option copyAndDeleteOnRenameFails false, then an exception will be thrown if an existing file existed, if its true, then the existing file is deleted before the move operation.|true|boolean|
+|keepLastModified|Will keep the last modified timestamp from the source file (if any). Will use the FileConstants.FILE\_LAST\_MODIFIED header to located the timestamp. This header can contain either a java.util.Date or long with the timestamp. If the timestamp exists and the option is enabled it will set this timestamp on the written file. Note: This option only applies to the file producer. You cannot use this option with any of the ftp producers.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|moveExistingFileStrategy|Strategy (Custom Strategy) used to move file with special naming token to use when fileExist=Move is configured. By default, there is an implementation used if no custom strategy is provided||object|
+|autoCreate|Automatically create missing directories in the file's pathname. For the file consumer, that means creating the starting directory. For the file producer, it means the directory the files should be written to.|true|boolean|
+|connectTimeout|Sets the connect timeout for waiting for a connection to be established Used by both FTPClient and JSCH|10000|duration|
+|maximumReconnectAttempts|Specifies the maximum reconnect attempts Camel performs when it tries to connect to the remote FTP server. Use 0 to disable this behavior.||integer|
+|reconnectDelay|Delay in millis Camel will wait before performing a reconnect attempt.|1000|duration|
+|throwExceptionOnConnectFailed|Should an exception be thrown if connection failed (exhausted)By default exception is not thrown and a WARN is logged. You can use this to enable exception being thrown and handle the thrown exception from the org.apache.camel.spi.PollingConsumerPollStrategy rollback method.|false|boolean|
+|timeout|Sets the data timeout for waiting for reply Used only by FTPClient|30000|duration|
+|antExclude|Ant style filter exclusion. If both antInclude and antExclude are used, antExclude takes precedence over antInclude. Multiple exclusions may be specified in comma-delimited format.||string|
+|antFilterCaseSensitive|Sets case sensitive flag on ant filter.|true|boolean|
+|antInclude|Ant style filter inclusion. Multiple inclusions may be specified in comma-delimited format.||string|
+|eagerMaxMessagesPerPoll|Allows for controlling whether the limit from maxMessagesPerPoll is eager or not. If eager then the limit is during the scanning of files. Where as false would scan all files, and then perform sorting. Setting this option to false allows for sorting all files first, and then limit the poll. Mind that this requires a higher memory usage as all file details are in memory to perform the sorting.|true|boolean|
+|exclude|Is used to exclude files, if filename matches the regex pattern (matching is case in-sensitive). Notice if you use symbols such as plus sign and others you would need to configure this using the RAW() syntax if configuring this as an endpoint uri. See more details at configuring endpoint uris||string|
+|excludeExt|Is used to exclude files matching file extension name (case insensitive). For example to exclude bak files, then use excludeExt=bak. Multiple extensions can be separated by comma, for example to exclude bak and dat files, use excludeExt=bak,dat. Note that the file extension includes all parts, for example having a file named mydata.tar.gz will have extension as tar.gz. For more flexibility then use the include/exclude options.||string|
+|filter|Pluggable filter as a org.apache.camel.component.file.GenericFileFilter class. Will skip files if filter returns false in its accept() method.||object|
+|filterDirectory|Filters the directory based on Simple language. For example to filter on current date, you can use a simple date pattern such as ${date:now:yyyMMdd}||string|
+|filterFile|Filters the file based on Simple language. For example to filter on file size, you can use ${file:size} 5000||string|
+|idempotent|Option to use the Idempotent Consumer EIP pattern to let Camel skip already processed files. Will by default use a memory based LRUCache that holds 1000 entries. If noop=true then idempotent will be enabled as well to avoid consuming the same files over and over again.|false|boolean|
+|idempotentEager|Option to use the Idempotent Consumer EIP pattern to let Camel skip already processed files. Will by default use a memory based LRUCache that holds 1000 entries. If noop=true then idempotent will be enabled as well to avoid consuming the same files over and over again.|false|boolean|
+|idempotentKey|To use a custom idempotent key. By default the absolute path of the file is used. You can use the File Language, for example to use the file name and file size, you can do: idempotentKey=${file:name}-${file:size}||string|
+|idempotentRepository|A pluggable repository org.apache.camel.spi.IdempotentRepository which by default use MemoryIdempotentRepository if none is specified and idempotent is true.||object|
+|include|Is used to include files, if filename matches the regex pattern (matching is case in-sensitive). Notice if you use symbols such as plus sign and others you would need to configure this using the RAW() syntax if configuring this as an endpoint uri. See more details at configuring endpoint uris||string|
+|includeExt|Is used to include files matching file extension name (case insensitive). For example to include txt files, then use includeExt=txt. Multiple extensions can be separated by comma, for example to include txt and xml files, use includeExt=txt,xml. Note that the file extension includes all parts, for example having a file named mydata.tar.gz will have extension as tar.gz. For more flexibility then use the include/exclude options.||string|
+|maxDepth|The maximum depth to traverse when recursively processing a directory.|2147483647|integer|
+|maxMessagesPerPoll|To define a maximum messages to gather per poll. By default no maximum is set. Can be used to set a limit of e.g. 1000 to avoid when starting up the server that there are thousands of files. Set a value of 0 or negative to disabled it. Notice: If this option is in use then the File and FTP components will limit before any sorting. For example if you have 100000 files and use maxMessagesPerPoll=500, then only the first 500 files will be picked up, and then sorted. You can use the eagerMaxMessagesPerPoll option and set this to false to allow to scan all files first and then sort afterwards.||integer|
+|minDepth|The minimum depth to start processing when recursively processing a directory. Using minDepth=1 means the base directory. Using minDepth=2 means the first sub directory.||integer|
+|move|Expression (such as Simple Language) used to dynamically set the filename when moving it after processing. To move files into a .done subdirectory just enter .done.||string|
+|exclusiveReadLockStrategy|Pluggable read-lock as a org.apache.camel.component.file.GenericFileExclusiveReadLockStrategy implementation.||object|
+|readLock|Used by consumer, to only poll the files if it has exclusive read-lock on the file (i.e. the file is not in-progress or being written). Camel will wait until the file lock is granted. This option provides the build in strategies: - none - No read lock is in use - markerFile - Camel creates a marker file (fileName.camelLock) and then holds a lock on it. This option is not available for the FTP component - changed - Changed is using file length/modification timestamp to detect whether the file is currently being copied or not. Will at least use 1 sec to determine this, so this option cannot consume files as fast as the others, but can be more reliable as the JDK IO API cannot always determine whether a file is currently being used by another process. The option readLockCheckInterval can be used to set the check frequency. - fileLock - is for using java.nio.channels.FileLock. This option is not avail for Windows OS and the FTP component. This approach should be avoided when accessing a remote file system via a mount/share unless that file system supports distributed file locks. - rename - rename is for using a try to rename the file as a test if we can get exclusive read-lock. - idempotent - (only for file component) idempotent is for using a idempotentRepository as the read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that. - idempotent-changed - (only for file component) idempotent-changed is for using a idempotentRepository and changed as the combined read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that. - idempotent-rename - (only for file component) idempotent-rename is for using a idempotentRepository and rename as the combined read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that.Notice: The various read locks is not all suited to work in clustered mode, where concurrent consumers on different nodes is competing for the same files on a shared file system. The markerFile using a close to atomic operation to create the empty marker file, but its not guaranteed to work in a cluster. The fileLock may work better but then the file system need to support distributed file locks, and so on. Using the idempotent read lock can support clustering if the idempotent repository supports clustering, such as Hazelcast Component or Infinispan.|none|string|
+|readLockCheckInterval|Interval in millis for the read-lock, if supported by the read lock. This interval is used for sleeping between attempts to acquire the read lock. For example when using the changed read lock, you can set a higher interval period to cater for slow writes. The default of 1 sec. may be too fast if the producer is very slow writing the file. Notice: For FTP the default readLockCheckInterval is 5000. The readLockTimeout value must be higher than readLockCheckInterval, but a rule of thumb is to have a timeout that is at least 2 or more times higher than the readLockCheckInterval. This is needed to ensure that ample time is allowed for the read lock process to try to grab the lock before the timeout was hit.|1000|integer|
+|readLockDeleteOrphanLockFiles|Whether or not read lock with marker files should upon startup delete any orphan read lock files, which may have been left on the file system, if Camel was not properly shutdown (such as a JVM crash). If turning this option to false then any orphaned lock file will cause Camel to not attempt to pickup that file, this could also be due another node is concurrently reading files from the same shared directory.|true|boolean|
+|readLockLoggingLevel|Logging level used when a read lock could not be acquired. By default a DEBUG is logged. You can change this level, for example to OFF to not have any logging. This option is only applicable for readLock of types: changed, fileLock, idempotent, idempotent-changed, idempotent-rename, rename.|DEBUG|object|
+|readLockMarkerFile|Whether to use marker file with the changed, rename, or exclusive read lock types. By default a marker file is used as well to guard against other processes picking up the same files. This behavior can be turned off by setting this option to false. For example if you do not want to write marker files to the file systems by the Camel application.|true|boolean|
+|readLockMinAge|This option is applied only for readLock=changed. It allows to specify a minimum age the file must be before attempting to acquire the read lock. For example use readLockMinAge=300s to require the file is at last 5 minutes old. This can speedup the changed read lock as it will only attempt to acquire files which are at least that given age.|0|integer|
+|readLockMinLength|This option is applied only for readLock=changed. It allows you to configure a minimum file length. By default Camel expects the file to contain data, and thus the default value is 1. You can set this option to zero, to allow consuming zero-length files.|1|integer|
+|readLockRemoveOnCommit|This option is applied only for readLock=idempotent. It allows to specify whether to remove the file name entry from the idempotent repository when processing the file is succeeded and a commit happens. By default the file is not removed which ensures that any race-condition do not occur so another active node may attempt to grab the file. Instead the idempotent repository may support eviction strategies that you can configure to evict the file name entry after X minutes - this ensures no problems with race conditions. See more details at the readLockIdempotentReleaseDelay option.|false|boolean|
+|readLockRemoveOnRollback|This option is applied only for readLock=idempotent. It allows to specify whether to remove the file name entry from the idempotent repository when processing the file failed and a rollback happens. If this option is false, then the file name entry is confirmed (as if the file did a commit).|true|boolean|
+|readLockTimeout|Optional timeout in millis for the read-lock, if supported by the read-lock. If the read-lock could not be granted and the timeout triggered, then Camel will skip the file. At next poll Camel, will try the file again, and this time maybe the read-lock could be granted. Use a value of 0 or lower to indicate forever. Currently fileLock, changed and rename support the timeout. Notice: For FTP the default readLockTimeout value is 20000 instead of 10000. The readLockTimeout value must be higher than readLockCheckInterval, but a rule of thumb is to have a timeout that is at least 2 or more times higher than the readLockCheckInterval. This is needed to ensure that ample time is allowed for the read lock process to try to grab the lock before the timeout was hit.|10000|integer|
+|backoffErrorThreshold|The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.||integer|
+|backoffIdleThreshold|The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.||integer|
+|backoffMultiplier|To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.||integer|
+|delay|Milliseconds before the next poll.|500|integer|
+|greedy|If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.|false|boolean|
+|initialDelay|Milliseconds before the first poll starts.|1000|integer|
+|repeatCount|Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.|0|integer|
+|runLoggingLevel|The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.|TRACE|object|
+|scheduledExecutorService|Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.||object|
+|scheduler|To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler|none|object|
+|schedulerProperties|To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.||object|
+|startScheduler|Whether the scheduler should be auto started.|true|boolean|
+|timeUnit|Time unit for initialDelay and delay options.|MILLISECONDS|object|
+|useFixedDelay|Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.|true|boolean|
+|sdd|part of service SAS token||string|
+|se|part of SAS token||string|
+|si|part of service SAS token||string|
+|sig|part of SAS token||string|
+|sip|part of SAS token||string|
+|sp|part of SAS token||string|
+|spr|part of SAS token||string|
+|sr|part of service SAS token||string|
+|srt|part of SAS token||string|
+|ss|part of account SAS token||string|
+|st|part of SAS token||string|
+|sv|part of SAS token||string|
+|shuffle|To shuffle the list of files (sort in random order)|false|boolean|
+|sortBy|Built-in sort by using the File Language. Supports nested sorts, so you can have a sort by file name and as a 2nd group sort by modified date.||string|
+|sorter|Pluggable sorter as a java.util.Comparator class.||object|

camel-azure-key-vault.md

@@ -0,0 +1,298 @@
+# Azure-key-vault
+
+**Since Camel 3.17**
+
+**Only producer is supported**
+
+The azure-key-vault component that integrates [Azure Key
+Vault](https://azure.microsoft.com/en-us/services/key-vault/).
+
+Prerequisites
+
+You must have a valid Windows Azure Key Vault account. More information
+is available at [Azure Documentation
+Portal](https://docs.microsoft.com/azure/).
+
+# URI Format
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-azure-key-vault</artifactId>
+        <version>x.x.x</version>
+        <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# Usage
+
+## Using Azure Key Vault Property Function
+
+To use this function, you’ll need to provide credentials to Azure Key
+Vault Service as environment variables:
+
+    export $CAMEL_VAULT_AZURE_TENANT_ID=tenantId
+    export $CAMEL_VAULT_AZURE_CLIENT_ID=clientId
+    export $CAMEL_VAULT_AZURE_CLIENT_SECRET=clientSecret
+    export $CAMEL_VAULT_AZURE_VAULT_NAME=vaultName
+
+You can also configure the credentials in the `application.properties`
+file such as:
+
+    camel.vault.azure.tenantId = accessKey
+    camel.vault.azure.clientId = clientId
+    camel.vault.azure.clientSecret = clientSecret
+    camel.vault.azure.vaultName = vaultName
+
+Or you can enable the usage of Azure Identity in the following way:
+
+    export $CAMEL_VAULT_AZURE_IDENTITY_ENABLED=true
+    export $CAMEL_VAULT_AZURE_VAULT_NAME=vaultName
+
+You can also enable the usage of Azure Identity in the
+`application.properties` file such as:
+
+    camel.vault.azure.azureIdentityEnabled = true
+    camel.vault.azure.vaultName = vaultName
+
+At this point, you’ll be able to reference a property in the following
+way:
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <to uri="{{azure:route}}"/>
+        </route>
+    </camelContext>
+
+Where route will be the name of the secret stored in the Azure Key Vault
+Service.
+
+You could specify a default value in case the secret is not present on
+Azure Key Vault Service:
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <to uri="{{azure:route:default}}"/>
+        </route>
+    </camelContext>
+
+In this case, if the secret doesn’t exist, the property will fall back
+to "default" as value.
+
+Also, you are able to get a particular field of the secret, if you have,
+for example, a secret named database of this form:
+
+    {
+      "username": "admin",
+      "password": "password123",
+      "engine": "postgres",
+      "host": "127.0.0.1",
+      "port": "3128",
+      "dbname": "db"
+    }
+
+You’re able to do get single secret value in your route, like for
+example:
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <log message="Username is {{azure:database/username}}"/>
+        </route>
+    </camelContext>
+
+Or re-use the property as part of an endpoint.
+
+You could specify a default value in case the particular field of secret
+is not present on Azure Key Vault:
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <log message="Username is {{azure:database/username:admin}}"/>
+        </route>
+    </camelContext>
+
+In this case, if the secret doesn’t exist or the secret exists, but the
+username field is not part of the secret, the property will fall back to
+"admin" as value.
+
+There is also the syntax to get a particular version of the secret for
+both the approach, with field/default value specified or only with
+secret:
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <to uri="{{azure:route@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}"/>
+        </route>
+    </camelContext>
+
+This approach will return the RAW route secret with the version
+*bf9b4f4b-8e63-43fd-a73c-3e2d3748b451*.
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <to uri="{{azure:route:default@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}"/>
+        </route>
+    </camelContext>
+
+This approach will return the route secret value with version
+*bf9b4f4b-8e63-43fd-a73c-3e2d3748b451* or default value in case the
+secret doesn’t exist or the version doesn’t exist.
+
+    <camelContext>
+        <route>
+            <from uri="direct:start"/>
+            <log message="Username is {{azure:database/username:admin@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}"/>
+        </route>
+    </camelContext>
+
+This approach will return the username field of the database secret with
+version *bf9b4f4b-8e63-43fd-a73c-3e2d3748b451* or admin in case the
+secret doesn’t exist or the version doesn’t exist.
+
+For the moment we are not considering the rotation function if any are
+applied, but it is in the work to be done.
+
+The only requirement is adding the camel-azure-key-vault jar to your
+Camel application.
+
+## Automatic Camel context reloading on Secret Refresh
+
+Being able to reload Camel context on a Secret Refresh could be done by
+specifying the usual credentials (the same used for Azure Key Vault
+Property Function).
+
+With Environment variables:
+
+    export $CAMEL_VAULT_AZURE_TENANT_ID=tenantId
+    export $CAMEL_VAULT_AZURE_CLIENT_ID=clientId
+    export $CAMEL_VAULT_AZURE_CLIENT_SECRET=clientSecret
+    export $CAMEL_VAULT_AZURE_VAULT_NAME=vaultName
+
+or as plain Camel main properties:
+
+    camel.vault.azure.tenantId = accessKey
+    camel.vault.azure.clientId = clientId
+    camel.vault.azure.clientSecret = clientSecret
+    camel.vault.azure.vaultName = vaultName
+
+If you want to use Azure Identity with environment variables, you can do
+in the following way:
+
+    export $CAMEL_VAULT_AZURE_IDENTITY_ENABLED=true
+    export $CAMEL_VAULT_AZURE_VAULT_NAME=vaultName
+
+You can also enable the usage of Azure Identity in the
+`application.properties` file such as:
+
+    camel.vault.azure.azureIdentityEnabled = true
+    camel.vault.azure.vaultName = vaultName
+
+To enable the automatic refresh, you’ll need additional properties to
+set:
+
+    camel.vault.azure.refreshEnabled=true
+    camel.vault.azure.refreshPeriod=60000
+    camel.vault.azure.secrets=Secret
+    camel.vault.azure.eventhubConnectionString=eventhub_conn_string
+    camel.vault.azure.blobAccountName=blob_account_name
+    camel.vault.azure.blobContainerName=blob_container_name
+    camel.vault.azure.blobAccessKey=blob_access_key
+    camel.main.context-reload-enabled = true
+
+where `camel.vault.azure.refreshEnabled` will enable the automatic
+context reload, `camel.vault.azure.refreshPeriod` is the interval of
+time between two different checks for update events and
+`camel.vault.azure.secrets` is a regex representing the secrets we want
+to track for updates.
+
+where `camel.vault.azure.eventhubConnectionString` is the eventhub
+connection string to get notification from,
+`camel.vault.azure.blobAccountName`,
+`camel.vault.azure.blobContainerName` and
+`camel.vault.azure.blobAccessKey` are the Azure Storage Blob parameters
+for the checkpoint store needed by Azure Eventhub.
+
+Note that `camel.vault.azure.secrets` is not mandatory: if not specified
+the task responsible for checking updates events will take into accounts
+or the properties with an `azure:` prefix.
+
+The only requirement is adding the camel-azure-key-vault jar to your
+Camel application.
+
+## Azure Key Vault Producer operations
+
+Azure Key Vault component provides the following operation on the
+producer side:
+
+-   createSecret
+
+-   getSecret
+
+-   deleteSecret
+
+-   purgeDeletedSecret
+
+# Examples
+
+## Producer Examples
+
+-   createSecret: this operation will create a secret in Azure Key Vault
+
+<!-- -->
+
+    from("direct:createSecret")
+        .setHeader(KeyVaultConstants.SECRET_NAME, "Test")
+        .setBody(constant("Test"))
+        .to("azure-key-vault://test123?clientId=RAW({{clientId}})&clientSecret=RAW({{clientSecret}})&tenantId=RAW({{tenantId}})")
+
+-   getSecret: this operation will get a secret from Azure Key Vault
+
+<!-- -->
+
+    from("direct:getSecret")
+        .setHeader(KeyVaultConstants.SECRET_NAME, "Test")
+        .to("azure-key-vault://test123?clientId=RAW({{clientId}})&clientSecret=RAW({{clientSecret}})&tenantId=RAW({{tenantId}})&operation=getSecret")
+
+-   deleteSecret: this operation will delete a Secret from Azure Key
+    Vault
+
+<!-- -->
+
+    from("direct:deleteSecret")
+        .setHeader(KeyVaultConstants.SECRET_NAME, "Test")
+        .to("azure-key-vault://test123?clientId=RAW({{clientId}})&clientSecret=RAW({{clientSecret}})&tenantId=RAW({{tenantId}})&operation=deleteSecret")
+
+-   purgeDeletedSecret: this operation will purge a deleted Secret from
+    Azure Key Vault
+
+<!-- -->
+
+    from("direct:purgeDeletedSecret")
+        .setHeader(KeyVaultConstants.SECRET_NAME, "Test")
+        .to("azure-key-vault://test123?clientId=RAW({{clientId}})&clientSecret=RAW({{clientSecret}})&tenantId=RAW({{tenantId}})&operation=purgeDeletedSecret")
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|vaultName|Vault Name to be used||string|
+|credentialType|Determines the credential strategy to adopt|CLIENT\_SECRET|object|
+|operation|Operation to be performed||object|
+|secretClient|Instance of Secret client||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|clientId|Client Id to be used||string|
+|clientSecret|Client Secret to be used||string|
+|tenantId|Tenant Id to be used||string|

camel-azure-servicebus.md

@@ -0,0 +1,246 @@
+# Azure-servicebus
+
+**Since Camel 3.12**
+
+**Both producer and consumer are supported**
+
+The azure-servicebus component that integrates [Azure
+ServiceBus](https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview).
+Azure ServiceBus is a fully managed enterprise integration message
+broker. Service Bus can decouple applications and services. Service Bus
+offers a reliable and secure platform for asynchronous transfer of data
+and state. Data is transferred between different applications and
+services using messages.
+
+Prerequisites
+
+You must have a valid Windows Azure Storage account. More information is
+available at [Azure Documentation
+Portal](https://docs.microsoft.com/azure/).
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-azure-servicebus</artifactId>
+        <version>x.x.x</version>
+        <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# Consumer and Producer
+
+This component implements the Consumer and Producer.
+
+# Usage
+
+## Authentication Information
+
+You have three different Credential Types: AZURE\_IDENTITY,
+TOKEN\_CREDENTIAL and CONNECTION\_STRING. You can also provide a client
+instance yourself. To use this component, you have three options to
+provide the required Azure authentication information:
+
+**CONNECTION\_STRING**:
+
+-   Provide `connectionString` string it is the simplest option to get
+    started.
+
+**TOKEN\_CREDENTIAL**:
+
+-   Provide an implementation of
+    `com.azure.core.credential.TokenCredential` into the Camel’s
+    Registry, e.g., using the
+    `com.azure.identity.DefaultAzureCredentialBuilder().build();` API.
+    See the documentation [here about Azure-AD
+    authentication](https://docs.microsoft.com/en-us/azure/active-directory/authentication/overview-authentication).
+
+**AZURE\_IDENTITY**:
+
+-   This will use
+    `com.azure.identity.DefaultAzureCredentialBuilder().build();`
+    instance. This will follow the Default Azure Credential Chain. See
+    the documentation [here about Azure-AD
+    authentication](https://docs.microsoft.com/en-us/azure/active-directory/authentication/overview-authentication).
+
+**Client instance**:
+
+-   You can provide a
+    `com.azure.messaging.servicebus.ServiceBusSenderClient` for sending
+    message and/or
+    `com.azure.messaging.servicebus.ServiceBusReceiverClient` to receive
+    messages. If you provide the instances, they will be autowired.
+
+## Message Body
+
+In the producer, this component accepts message body of `String`,
+`byte[]` and `BinaryData` types or `List<String>`, `List<byte[]>` and
+`List<BinaryData>` to send batch messages.
+
+In the consumer, the returned message body will be of type \`String.
+
+## Azure ServiceBus Producer operations
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>sendMessages</code></p></td>
+<td style="text-align: left;"><p>Sends a set of messages to a Service
+Bus queue or topic using a batched approach.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>scheduleMessages</code></p></td>
+<td style="text-align: left;"><p>Sends a scheduled message to the Azure
+Service Bus entity this sender is connected to. A scheduled message is
+enqueued and made available to receivers only at the scheduled enqueue
+time.</p></td>
+</tr>
+</tbody>
+</table>
+
+## Azure ServiceBus Consumer operations
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>receiveMessages</code></p></td>
+<td style="text-align: left;"><p>Receives an &lt;b&gt;infinite&lt;/b&gt;
+stream of messages from the Service Bus entity.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>peekMessages</code></p></td>
+<td style="text-align: left;"><p>Reads the next batch of active messages
+without changing the state of the receiver or the message
+source.</p></td>
+</tr>
+</tbody>
+</table>
+
+### Examples
+
+-   `sendMessages`
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+             final List<Object> inputBatch = new LinkedList<>();
+                inputBatch.add("test batch 1");
+                inputBatch.add("test batch 2");
+                inputBatch.add("test batch 3");
+                inputBatch.add(123456);
+    
+                exchange.getIn().setBody(inputBatch);
+           })
+      .to("azure-servicebus:test//?connectionString=test")
+      .to("mock:result");
+
+-   `scheduleMessages`
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+             final List<Object> inputBatch = new LinkedList<>();
+                inputBatch.add("test batch 1");
+                inputBatch.add("test batch 2");
+                inputBatch.add("test batch 3");
+                inputBatch.add(123456);
+    
+                exchange.getIn().setHeader(ServiceBusConstants.SCHEDULED_ENQUEUE_TIME, OffsetDateTime.now());
+                exchange.getIn().setBody(inputBatch);
+           })
+      .to("azure-servicebus:test//?connectionString=test&producerOperation=scheduleMessages")
+      .to("mock:result");
+
+-   `receiveMessages`
+
+<!-- -->
+
+    from("azure-servicebus:test//?connectionString=test")
+      .log("${body}")
+      .to("mock:result");
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|amqpRetryOptions|Sets the retry options for Service Bus clients. If not specified, the default retry options are used.||object|
+|amqpTransportType|Sets the transport type by which all the communication with Azure Service Bus occurs. Default value is AMQP.|AMQP|object|
+|clientOptions|Sets the ClientOptions to be sent from the client built from this builder, enabling customization of certain properties, as well as support the addition of custom header information.||object|
+|configuration|The component configurations||object|
+|headerFilterStrategy|To use a custom HeaderFilterStrategy to filter Service Bus application properties to and from Camel message headers.||object|
+|proxyOptions|Sets the proxy configuration to use for ServiceBusSenderClient. When a proxy is configured, AMQP\_WEB\_SOCKETS must be used for the transport type.||object|
+|serviceBusType|The service bus type of connection to execute. Queue is for typical queue option and topic for subscription based model.|queue|object|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|enableDeadLettering|Enable application level deadlettering to the subscription deadletter subqueue if deadletter related headers are set.|false|boolean|
+|maxAutoLockRenewDuration|Sets the amount of time to continue auto-renewing the lock. Setting ZERO disables auto-renewal. For ServiceBus receive mode (RECEIVE\_AND\_DELETE RECEIVE\_AND\_DELETE), auto-renewal is disabled.|5m|object|
+|maxConcurrentCalls|Sets maximum number of concurrent calls|1|integer|
+|prefetchCount|Sets the prefetch count of the receiver. For both PEEK\_LOCK PEEK\_LOCK and RECEIVE\_AND\_DELETE RECEIVE\_AND\_DELETE receive modes the default value is 1. Prefetch speeds up the message flow by aiming to have a message readily available for local retrieval when and before the application asks for one using receive message. Setting a non-zero value will prefetch that number of messages. Setting the value to zero turns prefetch off.||integer|
+|processorClient|Sets the processorClient in order to consume messages by the consumer||object|
+|serviceBusReceiveMode|Sets the receive mode for the receiver.|PEEK\_LOCK|object|
+|subQueue|Sets the type of the SubQueue to connect to.||object|
+|subscriptionName|Sets the name of the subscription in the topic to listen to. topicOrQueueName and serviceBusType=topic must also be set. This property is required if serviceBusType=topic and the consumer is in use.||string|
+|binary|Set binary mode. If true, message body will be sent as byte. By default, it is false.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|producerOperation|Sets the desired operation to be used in the producer|sendMessages|object|
+|scheduledEnqueueTime|Sets OffsetDateTime at which the message should appear in the Service Bus queue or topic.||object|
+|senderClient|Sets senderClient to be used in the producer.||object|
+|serviceBusTransactionContext|Represents transaction in service. This object just contains transaction id.||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|connectionString|Sets the connection string for a Service Bus namespace or a specific Service Bus resource.||string|
+|credentialType|Determines the credential strategy to adopt|CONNECTION\_STRING|object|
+|fullyQualifiedNamespace|Fully Qualified Namespace of the service bus||string|
+|tokenCredential|A TokenCredential for Azure AD authentication.||object|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|topicOrQueueName|Selected topic name or the queue name, that is depending on serviceBusType config. For example if serviceBusType=queue, then this will be the queue name and if serviceBusType=topic, this will be the topic name.||string|
+|amqpRetryOptions|Sets the retry options for Service Bus clients. If not specified, the default retry options are used.||object|
+|amqpTransportType|Sets the transport type by which all the communication with Azure Service Bus occurs. Default value is AMQP.|AMQP|object|
+|clientOptions|Sets the ClientOptions to be sent from the client built from this builder, enabling customization of certain properties, as well as support the addition of custom header information.||object|
+|headerFilterStrategy|To use a custom HeaderFilterStrategy to filter Service Bus application properties to and from Camel message headers.||object|
+|proxyOptions|Sets the proxy configuration to use for ServiceBusSenderClient. When a proxy is configured, AMQP\_WEB\_SOCKETS must be used for the transport type.||object|
+|serviceBusType|The service bus type of connection to execute. Queue is for typical queue option and topic for subscription based model.|queue|object|
+|enableDeadLettering|Enable application level deadlettering to the subscription deadletter subqueue if deadletter related headers are set.|false|boolean|
+|maxAutoLockRenewDuration|Sets the amount of time to continue auto-renewing the lock. Setting ZERO disables auto-renewal. For ServiceBus receive mode (RECEIVE\_AND\_DELETE RECEIVE\_AND\_DELETE), auto-renewal is disabled.|5m|object|
+|maxConcurrentCalls|Sets maximum number of concurrent calls|1|integer|
+|prefetchCount|Sets the prefetch count of the receiver. For both PEEK\_LOCK PEEK\_LOCK and RECEIVE\_AND\_DELETE RECEIVE\_AND\_DELETE receive modes the default value is 1. Prefetch speeds up the message flow by aiming to have a message readily available for local retrieval when and before the application asks for one using receive message. Setting a non-zero value will prefetch that number of messages. Setting the value to zero turns prefetch off.||integer|
+|processorClient|Sets the processorClient in order to consume messages by the consumer||object|
+|serviceBusReceiveMode|Sets the receive mode for the receiver.|PEEK\_LOCK|object|
+|subQueue|Sets the type of the SubQueue to connect to.||object|
+|subscriptionName|Sets the name of the subscription in the topic to listen to. topicOrQueueName and serviceBusType=topic must also be set. This property is required if serviceBusType=topic and the consumer is in use.||string|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|binary|Set binary mode. If true, message body will be sent as byte. By default, it is false.|false|boolean|
+|producerOperation|Sets the desired operation to be used in the producer|sendMessages|object|
+|scheduledEnqueueTime|Sets OffsetDateTime at which the message should appear in the Service Bus queue or topic.||object|
+|senderClient|Sets senderClient to be used in the producer.||object|
+|serviceBusTransactionContext|Represents transaction in service. This object just contains transaction id.||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|connectionString|Sets the connection string for a Service Bus namespace or a specific Service Bus resource.||string|
+|credentialType|Determines the credential strategy to adopt|CONNECTION\_STRING|object|
+|fullyQualifiedNamespace|Fully Qualified Namespace of the service bus||string|
+|tokenCredential|A TokenCredential for Azure AD authentication.||object|

camel-azure-storage-blob.md

@@ -0,0 +1,806 @@
+# Azure-storage-blob
+
+**Since Camel 3.3**
+
+**Both producer and consumer are supported**
+
+The Azure Storage Blob component is used for storing and retrieving
+blobs from [Azure Storage
+Blob](https://azure.microsoft.com/services/storage/blobs/) Service using
+**Azure APIs v12**. However, in the case of versions above v12, we will
+see if this component can adopt these changes depending on how much
+breaking changes can result.
+
+Prerequisites
+
+You must have a valid Windows Azure Storage account. More information is
+available at [Azure Documentation
+Portal](https://docs.microsoft.com/azure/).
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-azure-storage-blob</artifactId>
+        <version>x.x.x</version>
+      <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# URI Format
+
+    azure-storage-blob://accountName[/containerName][?options]
+
+In the case of a consumer, `accountName`, `containerName` are required.
+
+In the case of a producer, it depends on the operation that is being
+requested, for example, if operation is on a container level, e.b:
+createContainer, accountName and containerName are only required, but in
+case of operation being requested in blob level, e.g: getBlob,
+accountName, containerName and blobName are required.
+
+The blob will be created if it does not already exist. You can append
+query options to the URI in the following format,
+`?options=value&option2=value&...`
+
+**Required information options:**
+
+To use this component, you have multiple options to provide the required
+Azure authentication information:
+
+-   By providing your own
+    [BlobServiceClient](https://azuresdkdocs.blob.core.windows.net/$web/java/azure-storage-blob/12.0.0/com/azure/storage/blob/BlobServiceClient.html)
+    instance which can be injected into `blobServiceClient`. Note: You
+    don’t need to create a specific client, e.g.: BlockBlobClient, the
+    BlobServiceClient represents the upper level which can be used to
+    retrieve lower level clients.
+
+-   Via Azure Identity, when specifying `credentialType=AZURE_IDENTITY`
+    and providing required [environment
+    variables](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/identity/azure-identity#environment-variables).
+    This enables service principal (e.g. app registration)
+    authentication with secret/certificate as well as username password.
+    Note that this is the default authentication strategy.
+
+-   Via shared storage account key, when specifying
+    `credentialType=SHARED_ACCOUNT_KEY` and providing `accountName` and
+    `accessKey` for your Azure account, this is the simplest way to get
+    started. The accessKey can be generated through your Azure portal.
+
+-   Via shared storage account key, when specifying
+    `credentialType=SHARED_KEY_CREDENTIAL` and providing a
+    [StorageSharedKeyCredential](https://azuresdkartifacts.blob.core.windows.net/azure-sdk-for-java/staging/apidocs/com/azure/storage/common/StorageSharedKeyCredential.html)
+    instance which can be injected into `credentials` option.
+
+-   Via Azure SAS, when specifying `credentialType=AZURE_SAS` and
+    providing a SAS Token parameter through the `sasToken` parameter.
+
+# Usage
+
+For example, to download a blob content from the block blob `hello.txt`
+located on the `container1` in the `camelazure` storage account, use the
+following snippet:
+
+    from("azure-storage-blob://camelazure/container1?blobName=hello.txt&credentialType=SHARED_ACCOUNT_KEY&accessKey=RAW(yourAccessKey)").
+    to("file://blobdirectory");
+
+## Advanced Azure Storage Blob configuration
+
+If your Camel Application is running behind a firewall or if you need to
+have more control over the `BlobServiceClient` instance configuration,
+you can create your own instance:
+
+    StorageSharedKeyCredential credential = new StorageSharedKeyCredential("yourAccountName", "yourAccessKey");
+    String uri = String.format("https://%s.blob.core.windows.net", "yourAccountName");
+    
+    BlobServiceClient client = new BlobServiceClientBuilder()
+                              .endpoint(uri)
+                              .credential(credential)
+                              .buildClient();
+    // This is camel context
+    context.getRegistry().bind("client", client);
+
+Then refer to this instance in your Camel `azure-storage-blob` component
+configuration:
+
+    from("azure-storage-blob://cameldev/container1?blobName=myblob&serviceClient=#client")
+    .to("mock:result");
+
+## Automatic detection of BlobServiceClient client in registry
+
+The component is capable of detecting the presence of an
+BlobServiceClient bean into the registry. If it’s the only instance of
+that type, it will be used as the client, and you won’t have to define
+it as uri parameter, like the example above. This may be really useful
+for smarter configuration of the endpoint.
+
+## Azure Storage Blob Producer operations
+
+Camel Azure Storage Blob component provides a wide range of operations
+on the producer side:
+
+**Operations on the service level**
+
+For these operations, `accountName` is **required**.
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td
+style="text-align: left;"><p><code>listBlobContainers</code></p></td>
+<td style="text-align: left;"><p>Get the content of the blob. You can
+restrict the output of this operation to a blob range.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>getChangeFeed</code></p></td>
+<td style="text-align: left;"><p>Returns transaction logs of all the
+changes that occur to the blobs and the blob metadata in your storage
+account. The change feed provides ordered, guaranteed, durable,
+immutable, read-only log of these changes.</p></td>
+</tr>
+</tbody>
+</table>
+
+**Operations on the container level**
+
+For these operations, `accountName` and `containerName` are
+**required**.
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td
+style="text-align: left;"><p><code>createBlobContainer</code></p></td>
+<td style="text-align: left;"><p>Create a new container within a storage
+account. If a container with the same name already exists, the producer
+will ignore it.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>deleteBlobContainer</code></p></td>
+<td style="text-align: left;"><p>Delete the specified container in the
+storage account. If the container doesn’t exist, the operation
+fails.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>listBlobs</code></p></td>
+<td style="text-align: left;"><p>Returns a list of blobs in this
+container, with folder structures flattened.</p></td>
+</tr>
+</tbody>
+</table>
+
+**Operations on the blob level**
+
+For these operations, `accountName`, `containerName` and `blobName` are
+**required**.
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 10%" />
+<col style="width: 79%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Blob Type</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>getBlob</code></p></td>
+<td style="text-align: left;"><p>Common</p></td>
+<td style="text-align: left;"><p>Get the content of the blob. You can
+restrict the output of this operation to a blob range.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>deleteBlob</code></p></td>
+<td style="text-align: left;"><p>Common</p></td>
+<td style="text-align: left;"><p>Delete a blob.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>downloadBlobToFile</code></p></td>
+<td style="text-align: left;"><p>Common</p></td>
+<td style="text-align: left;"><p>Download the entire blob into a file
+specified by the path. The file will be created and must not exist, if
+the file already exists a <code>FileAlreadyExistsException</code> will
+be thrown.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>downloadLink</code></p></td>
+<td style="text-align: left;"><p>Common</p></td>
+<td style="text-align: left;"><p>Generate the download link for the
+specified blob using shared access signatures (SAS). This by default
+only limits to 1hour of allowed access. However, you can override the
+default expiration duration through the headers.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>uploadBlockBlob</code></p></td>
+<td style="text-align: left;"><p>BlockBlob</p></td>
+<td style="text-align: left;"><p>Creates a new block blob, or updates
+the content of an existing block blob. Updating an existing block blob
+overwrites any existing metadata on the blob. Partial updates are not
+supported with PutBlob; the content of the existing blob is overwritten
+with the new content.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>stageBlockBlobList</code></p></td>
+<td style="text-align: left;"><p><code>BlockBlob</code></p></td>
+<td style="text-align: left;"><p>Uploads the specified block to the
+block blob’s "staging area" to be later committed by a call to
+commitBlobBlockList. However, in case header
+<code>CamelAzureStorageBlobCommitBlobBlockListLater</code> or config
+<code>commitBlockListLater</code> is set to false, this will commit the
+blocks immediately after staging the blocks.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>commitBlobBlockList</code></p></td>
+<td style="text-align: left;"><p><code>BlockBlob</code></p></td>
+<td style="text-align: left;"><p>Write a blob by specifying the list of
+block IDs that are to make up the blob. To be written as part of a blob,
+a block must have been successfully written to the server in a prior
+<code>stageBlockBlobList</code> operation. You can call
+<code>commitBlobBlockList</code> to update a blob by uploading only
+those blocks that have changed, then committing the new and existing
+blocks together. Any blocks not specified in the block list and
+permanently deleted.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>getBlobBlockList</code></p></td>
+<td style="text-align: left;"><p><code>BlockBlob</code></p></td>
+<td style="text-align: left;"><p>Returns the list of blocks that have
+been uploaded as part of a block blob using the specified blocklist
+filter.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>createAppendBlob</code></p></td>
+<td style="text-align: left;"><p><code>AppendBlob</code></p></td>
+<td style="text-align: left;"><p>Creates a 0-length append blob. Call
+commitAppendBlo`b operation to append data to an append blob.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>commitAppendBlob</code></p></td>
+<td style="text-align: left;"><p><code>AppendBlob</code></p></td>
+<td style="text-align: left;"><p>Commits a new block of data to the end
+of the existing append blob. In case of header
+<code>CamelAzureStorageBlobCreateAppendBlob</code> or config
+<code>createAppendBlob</code> is set to true, it will attempt to create
+the appendBlob through internal call to <code>createAppendBlob</code>
+operation first before committing.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>createPageBlob</code></p></td>
+<td style="text-align: left;"><p><code>PageBlob</code></p></td>
+<td style="text-align: left;"><p>Creates a page blob of the specified
+length. Call <code>uploadPageBlob</code> operation to upload data to a
+page blob.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>uploadPageBlob</code></p></td>
+<td style="text-align: left;"><p><code>PageBlob</code></p></td>
+<td style="text-align: left;"><p>Write one or more pages to the page
+blob. The size must be a multiple of 512. In case of header
+<code>CamelAzureStorageBlobCreatePageBlob</code> or config
+<code>createPageBlob</code> is set to true, it will attempt to create
+the appendBlob through internal call to <code>createPageBlob</code>
+operation first before uploading.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>resizePageBlob</code></p></td>
+<td style="text-align: left;"><p><code>PageBlob</code></p></td>
+<td style="text-align: left;"><p>Resizes the page blob to the specified
+size, which must be a multiple of 512.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>clearPageBlob</code></p></td>
+<td style="text-align: left;"><p><code>PageBlob</code></p></td>
+<td style="text-align: left;"><p>Free the specified pages from the page
+blob. The size of the range must be a multiple of 512.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>getPageBlobRanges</code></p></td>
+<td style="text-align: left;"><p><code>PageBlob</code></p></td>
+<td style="text-align: left;"><p>Returns the list of valid page ranges
+for a page blob or snapshot of a page blob.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>copyBlob</code></p></td>
+<td style="text-align: left;"><p><code>Common</code></p></td>
+<td style="text-align: left;"><p>Copy a blob from one container to
+another one, even from different accounts.</p></td>
+</tr>
+</tbody>
+</table>
+
+Refer to the example section in this page to learn how to use these
+operations into your camel application.
+
+## Consumer Examples
+
+To consume a blob into a file using the file component, this can be done
+like this:
+
+    from("azure-storage-blob://camelazure/container1?blobName=hello.txt&accountName=yourAccountName&accessKey=yourAccessKey").
+    to("file://blobdirectory");
+
+However, you can also write to file directly without using the file
+component, you will need to specify `fileDir` folder path to save your
+blob in your machine.
+
+    from("azure-storage-blob://camelazure/container1?blobName=hello.txt&accountName=yourAccountName&accessKey=yourAccessKey&fileDir=/var/to/awesome/dir").
+    to("mock:results");
+
+Also, the component supports batch consumer, hence you can consume
+multiple blobs with only specifying the container name, the consumer
+will return multiple exchanges depending on the number of the blobs in
+the container. Example:
+
+    from("azure-storage-blob://camelazure/container1?accountName=yourAccountName&accessKey=yourAccessKey&fileDir=/var/to/awesome/dir").
+    to("mock:results");
+
+## Producer Operations Examples
+
+-   `listBlobContainers`:
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+        // set the header you want the producer to evaluate, refer to the previous
+        // section to learn about the headers that can be set
+        // e.g.:
+        exchange.getIn().setHeader(BlobConstants.LIST_BLOB_CONTAINERS_OPTIONS, new ListBlobContainersOptions().setMaxResultsPerPage(10));
+      })
+      .to("azure-storage-blob://camelazure?operation=listBlobContainers&client&serviceClient=#client")
+      .to("mock:result");
+
+-   `createBlobContainer`:
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+        // set the header you want the producer to evaluate, refer to the previous
+        // section to learn about the headers that can be set
+        // e.g.:
+        exchange.getIn().setHeader(BlobConstants.BLOB_CONTAINER_NAME, "newContainerName");
+      })
+      .to("azure-storage-blob://camelazure/container1?operation=createBlobContainer&serviceClient=#client")
+      .to("mock:result");
+
+-   `deleteBlobContainer`:
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+        // set the header you want the producer to evaluate, refer to the previous
+        // section to learn about the headers that can be set
+        // e.g.:
+        exchange.getIn().setHeader(BlobConstants.BLOB_CONTAINER_NAME, "overridenName");
+      })
+      .to("azure-storage-blob://camelazure/container1?operation=deleteBlobContainer&serviceClient=#client")
+      .to("mock:result");
+
+-   `listBlobs`:
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+        // set the header you want the producer to evaluate, refer to the previous
+        // section to learn about the headers that can be set
+        // e.g.:
+        exchange.getIn().setHeader(BlobConstants.BLOB_CONTAINER_NAME, "overridenName");
+      })
+      .to("azure-storage-blob://camelazure/container1?operation=listBlobs&serviceClient=#client")
+      .to("mock:result");
+
+-   `getBlob`:
+
+We can either set an `outputStream` in the exchange body and write the
+data to it. E.g.:
+
+    from("direct:start")
+      .process(exchange -> {
+        // set the header you want the producer to evaluate, refer to the previous
+        // section to learn about the headers that can be set
+        // e.g.:
+        exchange.getIn().setHeader(BlobConstants.BLOB_CONTAINER_NAME, "overridenName");
+    
+        // set our body
+        exchange.getIn().setBody(outputStream);
+      })
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=getBlob&serviceClient=#client")
+      .to("mock:result");
+
+If we don’t set a body, then this operation will give us an
+`InputStream` instance which can proceeded further downstream:
+
+    from("direct:start")
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=getBlob&serviceClient=#client")
+      .process(exchange -> {
+          InputStream inputStream = exchange.getMessage().getBody(InputStream.class);
+          // We use Apache common IO for simplicity, but you are free to do whatever dealing
+          // with inputStream
+          System.out.println(IOUtils.toString(inputStream, StandardCharsets.UTF_8.name()));
+      })
+      .to("mock:result");
+
+-   `deleteBlob`:
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+        // set the header you want the producer to evaluate, refer to the previous
+        // section to learn about the headers that can be set
+        // e.g.:
+        exchange.getIn().setHeader(BlobConstants.BLOB_NAME, "overridenName");
+      })
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=deleteBlob&serviceClient=#client")
+      .to("mock:result");
+
+-   `downloadBlobToFile`:
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+        // set the header you want the producer to evaluate, refer to the previous
+        // section to learn about the headers that can be set
+        // e.g.:
+        exchange.getIn().setHeader(BlobConstants.BLOB_NAME, "overridenName");
+      })
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=downloadBlobToFile&fileDir=/var/mydir&serviceClient=#client")
+      .to("mock:result");
+
+-   `downloadLink`
+
+<!-- -->
+
+    from("direct:start")
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=downloadLink&serviceClient=#client")
+      .process(exchange -> {
+          String link = exchange.getMessage().getHeader(BlobConstants.DOWNLOAD_LINK, String.class);
+          System.out.println("My link " + link);
+      })
+      .to("mock:result");
+
+-   `uploadBlockBlob`
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+        // set the header you want the producer to evaluate, refer to the previous
+        // section to learn about the headers that can be set
+        // e.g.:
+        exchange.getIn().setHeader(BlobConstants.BLOB_NAME, "overridenName");
+        exchange.getIn().setBody("Block Blob");
+      })
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=uploadBlockBlob&serviceClient=#client")
+      .to("mock:result");
+
+-   `stageBlockBlobList`
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+          final List<BlobBlock> blocks = new LinkedList<>();
+          blocks.add(BlobBlock.createBlobBlock(new ByteArrayInputStream("Hello".getBytes())));
+          blocks.add(BlobBlock.createBlobBlock(new ByteArrayInputStream("From".getBytes())));
+          blocks.add(BlobBlock.createBlobBlock(new ByteArrayInputStream("Camel".getBytes())));
+    
+          exchange.getIn().setBody(blocks);
+      })
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=stageBlockBlobList&serviceClient=#client")
+      .to("mock:result");
+
+-   `commitBlockBlobList`
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+          // We assume here you have the knowledge of these blocks you want to commit
+          final List<Block> blockIds = new LinkedList<>();
+          blockIds.add(new Block().setName("id-1"));
+          blockIds.add(new Block().setName("id-2"));
+          blockIds.add(new Block().setName("id-3"));
+    
+          exchange.getIn().setBody(blockIds);
+      })
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=commitBlockBlobList&serviceClient=#client")
+      .to("mock:result");
+
+-   `getBlobBlockList`
+
+<!-- -->
+
+    from("direct:start")
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=getBlobBlockList&serviceClient=#client")
+      .log("${body}")
+      .to("mock:result");
+
+-   `createAppendBlob`
+
+<!-- -->
+
+    from("direct:start")
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=createAppendBlob&serviceClient=#client")
+      .to("mock:result");
+
+-   `commitAppendBlob`
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+        final String data = "Hello world from my awesome tests!";
+        final InputStream dataStream = new ByteArrayInputStream(data.getBytes(StandardCharsets.UTF_8));
+    
+        exchange.getIn().setBody(dataStream);
+    
+        // of course, you can set whatever headers you like, refer to the headers section to learn more
+      })
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=commitAppendBlob&serviceClient=#client")
+      .to("mock:result");
+
+-   `createPageBlob`
+
+<!-- -->
+
+    from("direct:start")
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=createPageBlob&serviceClient=#client")
+      .to("mock:result");
+
+-   `uploadPageBlob`
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+        byte[] dataBytes = new byte[512]; // we set range for the page from 0-511
+        new Random().nextBytes(dataBytes);
+        final InputStream dataStream = new ByteArrayInputStream(dataBytes);
+        final PageRange pageRange = new PageRange().setStart(0).setEnd(511);
+    
+        exchange.getIn().setHeader(BlobConstants.PAGE_BLOB_RANGE, pageRange);
+        exchange.getIn().setBody(dataStream);
+      })
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=uploadPageBlob&serviceClient=#client")
+      .to("mock:result");
+
+-   `resizePageBlob`
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+        final PageRange pageRange = new PageRange().setStart(0).setEnd(511);
+    
+        exchange.getIn().setHeader(BlobConstants.PAGE_BLOB_RANGE, pageRange);
+      })
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=resizePageBlob&serviceClient=#client")
+      .to("mock:result");
+
+-   `clearPageBlob`
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+        final PageRange pageRange = new PageRange().setStart(0).setEnd(511);
+    
+        exchange.getIn().setHeader(BlobConstants.PAGE_BLOB_RANGE, pageRange);
+      })
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=clearPageBlob&serviceClient=#client")
+      .to("mock:result");
+
+-   `getPageBlobRanges`
+
+<!-- -->
+
+    from("direct:start")
+      .process(exchange -> {
+        final PageRange pageRange = new PageRange().setStart(0).setEnd(511);
+    
+        exchange.getIn().setHeader(BlobConstants.PAGE_BLOB_RANGE, pageRange);
+      })
+      .to("azure-storage-blob://camelazure/container1?blobName=blob&operation=getPageBlobRanges&serviceClient=#client")
+      .log("${body}")
+      .to("mock:result");
+
+-   `copyBlob`
+
+<!-- -->
+
+    from("direct:copyBlob")
+      .process(exchange -> {
+        exchange.getIn().setHeader(BlobConstants.BLOB_NAME, "file.txt");
+        exchange.getMessage().setHeader(BlobConstants.SOURCE_BLOB_CONTAINER_NAME, "containerblob1");
+        exchange.getMessage().setHeader(BlobConstants.SOURCE_BLOB_ACCOUNT_NAME, "account");
+      })
+      .to("azure-storage-blob://account/containerblob2?operation=copyBlob&sourceBlobAccessKey=RAW(accessKey)")
+      .to("mock:result");
+
+In this way the `file.txt` in the container `containerblob1` of the
+account `account`, will be copied to the container `containerblob2` of
+the same account.
+
+## SAS Token generation example
+
+SAS Blob Container tokens can be generated programmatically or via Azure
+UI. To generate the token with java code, the following can be done:
+
+    BlobContainerClient blobClient = new BlobContainerClientBuilder()
+                .endpoint(String.format("https://%s.blob.core.windows.net/%s", accountName, accessKey))
+                .containerName(containerName)
+                .credential(new StorageSharedKeyCredential(accountName, accessKey))
+                .buildClient();
+    
+            // Create a SAS token that's valid for 1 day, as an example
+            OffsetDateTime expiryTime = OffsetDateTime.now().plusDays(1);
+    
+            // Assign permissions to the SAS token
+            BlobContainerSasPermission blobContainerSasPermission = new BlobContainerSasPermission()
+                .setWritePermission(true)
+                .setListPermission(true)
+                .setCreatePermission(true)
+                .setDeletePermission(true)
+                .setAddPermission(true)
+                .setReadPermission(true);
+    
+            BlobServiceSasSignatureValues sasSignatureValues = new BlobServiceSasSignatureValues(expiryTime, blobContainerSasPermission);
+    
+            return blobClient.generateSas(sasSignatureValues);
+
+The generated SAS token can be then stored to an application.properties
+file so that it can be loaded by the camel route, for example:
+
+    camel.component.azure-storage-blob.sas-token=MY_TOKEN_HERE
+    
+    from("direct:copyBlob")
+      .to("azure-storage-blob://account/containerblob2?operation=uploadBlockBlob&credentialType=AZURE_SAS")
+
+## Development Notes (Important)
+
+All integration tests use
+[Testcontainers](https://www.testcontainers.org/) and run by default.
+Obtaining of Azure accessKey and accountName is needed to be able to run
+all integration tests using Azure services. In addition to the mocked
+unit tests, you **will need to run the integration tests with every
+change you make or even client upgrade as the Azure client can break
+things even on minor versions upgrade.** To run the integration tests,
+on this component directory, run the following maven command:
+
+    mvn verify -DaccountName=myacc -DaccessKey=mykey -DcredentialType=SHARED_ACCOUNT_KEY
+
+Whereby `accountName` is your Azure account name and `accessKey` is the
+access key being generated from Azure portal.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|blobName|The blob name, to consume specific blob from a container. However, on producer it is only required for the operations on the blob level||string|
+|blobOffset|Set the blob offset for the upload or download operations, default is 0|0|integer|
+|blobType|The blob type in order to initiate the appropriate settings for each blob type|blockblob|object|
+|closeStreamAfterRead|Close the stream after read or keep it open, default is true|true|boolean|
+|configuration|The component configurations||object|
+|credentials|StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information||object|
+|credentialType|Determines the credential strategy to adopt|AZURE\_IDENTITY|object|
+|dataCount|How many bytes to include in the range. Must be greater than or equal to 0 if specified.||integer|
+|fileDir|The file directory where the downloaded blobs will be saved to, this can be used in both, producer and consumer||string|
+|maxResultsPerPage|Specifies the maximum number of blobs to return, including all BlobPrefix elements. If the request does not specify maxResultsPerPage or specifies a value greater than 5,000, the server will return up to 5,000 items.||integer|
+|maxRetryRequests|Specifies the maximum number of additional HTTP Get requests that will be made while reading the data from a response body.|0|integer|
+|prefix|Filters the results to return only blobs whose names begin with the specified prefix. May be null to return all blobs.||string|
+|regex|Filters the results to return only blobs whose names match the specified regular expression. May be null to return all if both prefix and regex are set, regex takes the priority and prefix is ignored.||string|
+|sasToken|In case of usage of Shared Access Signature we'll need to set a SAS Token||string|
+|serviceClient|Client to a storage account. This client does not hold any state about a particular storage account but is instead a convenient way of sending off appropriate requests to the resource on the service. It may also be used to construct URLs to blobs and containers. This client contains operations on a service account. Operations on a container are available on BlobContainerClient through BlobServiceClient#getBlobContainerClient(String), and operations on a blob are available on BlobClient through BlobContainerClient#getBlobClient(String).||object|
+|timeout|An optional timeout value beyond which a RuntimeException will be raised.||object|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|blobSequenceNumber|A user-controlled value that you can use to track requests. The value of the sequence number must be between 0 and 263 - 1.The default value is 0.|0|integer|
+|blockListType|Specifies which type of blocks to return.|COMMITTED|object|
+|changeFeedContext|When using getChangeFeed producer operation, this gives additional context that is passed through the Http pipeline during the service call.||object|
+|changeFeedEndTime|When using getChangeFeed producer operation, this filters the results to return events approximately before the end time. Note: A few events belonging to the next hour can also be returned. A few events belonging to this hour can be missing; to ensure all events from the hour are returned, round the end time up by an hour.||object|
+|changeFeedStartTime|When using getChangeFeed producer operation, this filters the results to return events approximately after the start time. Note: A few events belonging to the previous hour can also be returned. A few events belonging to this hour can be missing; to ensure all events from the hour are returned, round the start time down by an hour.||object|
+|closeStreamAfterWrite|Close the stream after write or keep it open, default is true|true|boolean|
+|commitBlockListLater|When is set to true, the staged blocks will not be committed directly.|true|boolean|
+|createAppendBlob|When is set to true, the append blocks will be created when committing append blocks.|true|boolean|
+|createPageBlob|When is set to true, the page blob will be created when uploading page blob.|true|boolean|
+|downloadLinkExpiration|Override the default expiration (millis) of URL download link.||integer|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|The blob operation that can be used with this component on the producer|listBlobContainers|object|
+|pageBlobSize|Specifies the maximum size for the page blob, up to 8 TB. The page blob size must be aligned to a 512-byte boundary.|512|integer|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|accessKey|Access key for the associated azure account name to be used for authentication with azure blob services||string|
+|sourceBlobAccessKey|Source Blob Access Key: for copyblob operation, sadly, we need to have an accessKey for the source blob we want to copy Passing an accessKey as header, it's unsafe so we could set as key.||string|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|accountName|Azure account name to be used for authentication with azure blob services||string|
+|containerName|The blob container name||string|
+|blobName|The blob name, to consume specific blob from a container. However, on producer it is only required for the operations on the blob level||string|
+|blobOffset|Set the blob offset for the upload or download operations, default is 0|0|integer|
+|blobServiceClient|Client to a storage account. This client does not hold any state about a particular storage account but is instead a convenient way of sending off appropriate requests to the resource on the service. It may also be used to construct URLs to blobs and containers. This client contains operations on a service account. Operations on a container are available on BlobContainerClient through getBlobContainerClient(String), and operations on a blob are available on BlobClient through getBlobContainerClient(String).getBlobClient(String).||object|
+|blobType|The blob type in order to initiate the appropriate settings for each blob type|blockblob|object|
+|closeStreamAfterRead|Close the stream after read or keep it open, default is true|true|boolean|
+|credentials|StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information||object|
+|credentialType|Determines the credential strategy to adopt|AZURE\_IDENTITY|object|
+|dataCount|How many bytes to include in the range. Must be greater than or equal to 0 if specified.||integer|
+|fileDir|The file directory where the downloaded blobs will be saved to, this can be used in both, producer and consumer||string|
+|maxResultsPerPage|Specifies the maximum number of blobs to return, including all BlobPrefix elements. If the request does not specify maxResultsPerPage or specifies a value greater than 5,000, the server will return up to 5,000 items.||integer|
+|maxRetryRequests|Specifies the maximum number of additional HTTP Get requests that will be made while reading the data from a response body.|0|integer|
+|prefix|Filters the results to return only blobs whose names begin with the specified prefix. May be null to return all blobs.||string|
+|regex|Filters the results to return only blobs whose names match the specified regular expression. May be null to return all if both prefix and regex are set, regex takes the priority and prefix is ignored.||string|
+|sasToken|In case of usage of Shared Access Signature we'll need to set a SAS Token||string|
+|serviceClient|Client to a storage account. This client does not hold any state about a particular storage account but is instead a convenient way of sending off appropriate requests to the resource on the service. It may also be used to construct URLs to blobs and containers. This client contains operations on a service account. Operations on a container are available on BlobContainerClient through BlobServiceClient#getBlobContainerClient(String), and operations on a blob are available on BlobClient through BlobContainerClient#getBlobClient(String).||object|
+|timeout|An optional timeout value beyond which a RuntimeException will be raised.||object|
+|sendEmptyMessageWhenIdle|If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.|false|boolean|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|pollStrategy|A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.||object|
+|blobSequenceNumber|A user-controlled value that you can use to track requests. The value of the sequence number must be between 0 and 263 - 1.The default value is 0.|0|integer|
+|blockListType|Specifies which type of blocks to return.|COMMITTED|object|
+|changeFeedContext|When using getChangeFeed producer operation, this gives additional context that is passed through the Http pipeline during the service call.||object|
+|changeFeedEndTime|When using getChangeFeed producer operation, this filters the results to return events approximately before the end time. Note: A few events belonging to the next hour can also be returned. A few events belonging to this hour can be missing; to ensure all events from the hour are returned, round the end time up by an hour.||object|
+|changeFeedStartTime|When using getChangeFeed producer operation, this filters the results to return events approximately after the start time. Note: A few events belonging to the previous hour can also be returned. A few events belonging to this hour can be missing; to ensure all events from the hour are returned, round the start time down by an hour.||object|
+|closeStreamAfterWrite|Close the stream after write or keep it open, default is true|true|boolean|
+|commitBlockListLater|When is set to true, the staged blocks will not be committed directly.|true|boolean|
+|createAppendBlob|When is set to true, the append blocks will be created when committing append blocks.|true|boolean|
+|createPageBlob|When is set to true, the page blob will be created when uploading page blob.|true|boolean|
+|downloadLinkExpiration|Override the default expiration (millis) of URL download link.||integer|
+|operation|The blob operation that can be used with this component on the producer|listBlobContainers|object|
+|pageBlobSize|Specifies the maximum size for the page blob, up to 8 TB. The page blob size must be aligned to a 512-byte boundary.|512|integer|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|backoffErrorThreshold|The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.||integer|
+|backoffIdleThreshold|The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.||integer|
+|backoffMultiplier|To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.||integer|
+|delay|Milliseconds before the next poll.|500|integer|
+|greedy|If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.|false|boolean|
+|initialDelay|Milliseconds before the first poll starts.|1000|integer|
+|repeatCount|Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.|0|integer|
+|runLoggingLevel|The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.|TRACE|object|
+|scheduledExecutorService|Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.||object|
+|scheduler|To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler|none|object|
+|schedulerProperties|To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.||object|
+|startScheduler|Whether the scheduler should be auto started.|true|boolean|
+|timeUnit|Time unit for initialDelay and delay options.|MILLISECONDS|object|
+|useFixedDelay|Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.|true|boolean|
+|accessKey|Access key for the associated azure account name to be used for authentication with azure blob services||string|
+|sourceBlobAccessKey|Source Blob Access Key: for copyblob operation, sadly, we need to have an accessKey for the source blob we want to copy Passing an accessKey as header, it's unsafe so we could set as key.||string|

camel-azure-storage-datalake.md

@@ -0,0 +1,557 @@
+# Azure-storage-datalake
+
+**Since Camel 3.8**
+
+**Both producer and consumer are supported**
+
+The Azure storage datalake component is used for storing and retrieving
+file from Azure Storage Data Lake Service using the **Azure APIs v12**.
+
+Prerequisites
+
+You need to have a valid Azure account with Azure storage set up. More
+information can be found at [Azure Documentation
+Portal](https://docs.microsoft.com/azure/).
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component.
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-azure-storage-datalake</artifactId>
+        <version>x.x.x</version>
+        <!-- use the same version as your camel core version -->
+    </dependency>
+
+# Uri Format
+
+    azure-storage-datalake:accountName[/fileSystemName][?options]
+
+In the case of the consumer, both `accountName` and `fileSystemName` are
+required. In the case of the producer, it depends on the operation being
+requested.
+
+You can append query options to the URI in the following format:
+`?option1=value&option2=value&...`
+
+## Methods of authentication
+
+To use this component, you will have to provide at least one of the
+specific credentialType parameters:
+
+-   `SHARED_KEY_CREDENTIAL`: Provide `accountName` and `accessKey` for
+    your azure account or provide StorageSharedKeyCredential instance
+    which can be provided into `sharedKeyCredential` option.
+
+-   `CLIENT_SECRET`: Provide ClientSecretCredential instance which can
+    be provided into `clientSecretCredential` option or provide
+    `accountName`, `clientId`, `clientSecret` and `tenantId` for
+    authentication with Azure Active Directory.
+
+-   `SERVICE_CLIENT_INSTANCE`: Provide a DataLakeServiceClient instance
+    which can be provided into `serviceClient` option.
+
+-   `AZURE_IDENTITY`: Use the Default Azure Credential Provider Chain
+
+-   `AZURE_SAS`: Provide `sasSignature` or `sasCredential` parameters to
+    use SAS mechanism
+
+The default is `CLIENT_SECRET`.
+
+# Usage
+
+For example, to download content from file `test.txt` located on the
+`filesystem` in `camelTesting` storage account, use the following
+snippet:
+
+    from("azure-storage-datalake:camelTesting/filesystem?fileName=test.txt&accountKey=key").
+    to("file://fileDirectory");
+
+## Automatic detection of a service client
+
+The component is capable of automatically detecting the presence of a
+DataLakeServiceClient bean in the registry. Hence, if your registry has
+only one instance of type DataLakeServiceClient, it will be
+automatically used as the default client. You won’t have to explicitly
+define it as an uri parameter.
+
+## Azure Storage DataLake Producer Operations
+
+The various operations supported by Azure Storage DataLake are as given
+below:
+
+**Operations on Service level**
+
+For these operations, `accountName` option is required
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>listFileSystem</code></p></td>
+<td style="text-align: left;"><p>List all the file systems that are
+present in the given azure account.</p></td>
+</tr>
+</tbody>
+</table>
+
+**Operations on File system level**
+
+For these operations, `accountName` and `fileSystemName` options are
+required
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>createFileSystem</code></p></td>
+<td style="text-align: left;"><p>Create a new file System with the
+storage account</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>deleteFileSystem</code></p></td>
+<td style="text-align: left;"><p>Delete the specified file system within
+the storage account</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>listPaths</code></p></td>
+<td style="text-align: left;"><p>Returns list of all the files within
+the given path in the given file system, with folder structure
+flattened</p></td>
+</tr>
+</tbody>
+</table>
+
+**Operations on Directory level**
+
+For these operations, `accountName`, `fileSystemName` and
+`directoryName` options are required
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>createFile</code></p></td>
+<td style="text-align: left;"><p>Create a new file in the specified
+directory within the fileSystem</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>deleteDirectory</code></p></td>
+<td style="text-align: left;"><p>Delete the specified directory within
+the file system</p></td>
+</tr>
+</tbody>
+</table>
+
+**Operations on file level**
+
+For these operations, `accountName`, `fileSystemName` and `fileName`
+options are required
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>getFile</code></p></td>
+<td style="text-align: left;"><p>Get the contents of a file</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>downloadToFile</code></p></td>
+<td style="text-align: left;"><p>Download the entire file from the file
+system into a path specified by fileDir.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>downloadLink</code></p></td>
+<td style="text-align: left;"><p>Generate a download link for the
+specified file using Shared Access Signature (SAS). The expiration time
+to be set for the link can be specified otherwise 1 hour is taken as
+default.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>deleteFile</code></p></td>
+<td style="text-align: left;"><p>Delete the specified file.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>appendToFile</code></p></td>
+<td style="text-align: left;"><p>Appends the data passed to the
+specified file in the file System. Flush command is required after
+append.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>flushToFile</code></p></td>
+<td style="text-align: left;"><p>Flushes the data already appended to
+the specified file.</p></td>
+</tr>
+<tr>
+<td
+style="text-align: left;"><p><code>openQueryInputStream</code></p></td>
+<td style="text-align: left;"><p>Opens an <code>InputStream</code> based
+on the query passed to the endpoint. For this operation, you must first
+register the query acceleration feature with your subscription.</p></td>
+</tr>
+</tbody>
+</table>
+
+Refer to the examples section below for more details on how to use these
+operations
+
+## Consumer Examples
+
+To consume a file from the storage datalake into a file using the file
+component, this can be done like this:
+
+    from("azure-storage-datalake":cameltesting/filesystem?fileName=test.txt&accountKey=yourAccountKey").
+    to("file:/filelocation");
+
+You can also directly write to a file without using the file component.
+For this, you will need to specify the path in `fileDir` option, to save
+it to your machine.
+
+    from("azure-storage-datalake":cameltesting/filesystem?fileName=test.txt&accountKey=yourAccountKey&fileDir=/test/directory").
+    to("mock:results");
+
+This component also supports batch consumer. So, you can consume
+multiple files from a file system by specifying the path from where you
+want to consume the files.
+
+    from("azure-storage-datalake":cameltesting/filesystem?accountKey=yourAccountKey&fileDir=/test/directory&path=abc/test").
+    to("mock:results");
+
+## Producer Examples
+
+-   `listFileSystem`
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            //required headers can be added here
+            exchange.getIn().setHeader(DataLakeConstants.LIST_FILESYSTEMS_OPTIONS, new ListFileSystemsOptions().setMaxResultsPerPage(10));
+        })
+        .to("azure-storage-datalake:cameltesting?operation=listFileSystem&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+-   `createFileSystem`
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(DataLakeConstants.FILESYSTEM_NAME, "test1");
+        })
+        .to("azure-storage-datalake:cameltesting?operation=createFileSystem&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+-   `deleteFileSystem`
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(DataLakeConstants.FILESYSTEM_NAME, "test1");
+        })
+        .to("azure-storage-datalake:cameltesting?operation=deleteFileSystem&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+-   `listPaths`
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(DataLakeConstants.LIST_PATH_OPTIONS, new ListPathsOptions().setPath("/main"));
+        })
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=listPaths&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+-   `getFile`
+
+This can be done in two ways, We can either set an `OutputStream` in the
+exchange body
+
+    from("direct:start")
+        .process(exchange -> {
+            // set an OutputStream where the file data can should be written
+            exchange.getIn().setBody(outputStream);
+        })
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=getFile&fileName=test.txt&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+Or if the body is not set, the operation will give an `InputStream`,
+given that you have already registered for query acceleration in azure
+portal.
+
+    from("direct:start")
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=getFile&fileName=test.txt&dataLakeServiceClient=#serviceClient")
+        .process(exchange -> {
+            InputStream inputStream = exchange.getMessage().getBody(InputStream.class);
+            System.out.Println(IOUtils.toString(inputStream, StandardCharcets.UTF_8.name()));
+        })
+        .to("mock:results");
+
+-   `deleteFile`
+
+<!-- -->
+
+    from("direct:start")
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=deleteFile&fileName=test.txt&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+-   `downloadToFile`
+
+<!-- -->
+
+    from("direct:start")
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=downloadToFile&fileName=test.txt&fileDir=/test/mydir&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+-   `downloadLink`
+
+<!-- -->
+
+    from("direct:start")
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=downloadLink&fileName=test.txt&dataLakeServiceClient=#serviceClient")
+        .process(exchange -> {
+            String link = exchange.getMessage().getBody(String.class);
+            System.out.println(link);
+        })
+        .to("mock:results");
+
+-   `appendToFile`
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            final String data = "test data";
+            final InputStream inputStream = new ByteArrayInputStream(data.getBytes(StandardCharsets.UTF_8));
+            exchange.getIn().setBody(inputStream);
+        })
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=appendToFile&fileName=test.txt&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+-   `flushToFile`
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(DataLakeConstants.POSITION, 0);
+        })
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=flushToFile&fileName=test.txt&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+-   `openQueryInputStream`
+
+For this operation, you should have already registered for query
+acceleration on the azure portal
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(DataLakeConstants.QUERY_OPTIONS, new FileQueryOptions("SELECT * from BlobStorage"));
+        })
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=openQueryInputStream&fileName=test.txt&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+-   `upload`
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            final String data = "test data";
+            final InputStream inputStream = new ByteArrayInputStream(data.getBytes(StandardCharsets.UTF_8));
+            exchange.getIn().setBody(inputStream);
+        })
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=upload&fileName=test.txt&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+-   `uploadFromFile`
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(DataLakeConstants.PATH, "test/file.txt");
+        })
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=uploadFromFile&fileName=test.txt&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+-   `createFile`
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(DataLakeConstants.DIRECTORY_NAME, "test/file/");
+        })
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=createFile&fileName=test.txt&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+-   `deleteDirectory`
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+            exchange.getIn().setHeader(DataLakeConstants.DIRECTORY_NAME, "test/file/");
+        })
+        .to("azure-storage-datalake:cameltesting/filesystem?operation=deleteDirectory&dataLakeServiceClient=#serviceClient")
+        .to("mock:results");
+
+## Testing
+
+Please run all the unit tests and integration tests while making changes
+to the component as changes or version upgrades can break things. For
+running all the tests in the component, you will need to obtain azure
+`accountName` and `accessKey`. After obtaining the same, you can run the
+full test on this component directory by running the following maven
+command
+
+    mvn verify -Dazure.storage.account.name=<accountName> -Dazure.storage.account.key=<accessKey>
+
+You can also skip the integration test and run only basic unit test by
+using the command
+
+    mvn test
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|clientId|client id for azure account||string|
+|close|Whether or not a file changed event raised indicates completion (true) or modification (false)||boolean|
+|closeStreamAfterRead|check for closing stream after read||boolean|
+|configuration|configuration object for data lake||object|
+|credentialType|Determines the credential strategy to adopt|CLIENT\_SECRET|object|
+|dataCount|count number of bytes to download||integer|
+|directoryName|directory of the file to be handled in component||string|
+|downloadLinkExpiration|download link expiration time||integer|
+|expression|expression for queryInputStream||string|
+|fileDir|directory of file to do operations in the local system||string|
+|fileName|name of file to be handled in component||string|
+|fileOffset|offset position in file for different operations||integer|
+|maxResults|maximum number of results to show at a time||integer|
+|maxRetryRequests|no of retries to a given request||integer|
+|openOptions|set open options for creating file||object|
+|path|path in azure data lake for operations||string|
+|permission|permission string for the file||string|
+|position|This parameter allows the caller to upload data in parallel and control the order in which it is appended to the file.||integer|
+|recursive|recursively include all paths||boolean|
+|regex|regular expression for matching file names||string|
+|retainUncommitedData|Whether or not uncommitted data is to be retained after the operation||boolean|
+|serviceClient|data lake service client for azure storage data lake||object|
+|sharedKeyCredential|shared key credential for azure data lake gen2||object|
+|tenantId|tenant id for azure account||string|
+|timeout|Timeout for operation||object|
+|umask|umask permission for file||string|
+|userPrincipalNameReturned|whether or not to use upn||boolean|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|operation to be performed|listFileSystem|object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|accountKey|account key for authentication||string|
+|clientSecret|client secret for azure account||string|
+|clientSecretCredential|client secret credential for authentication||object|
+|sasCredential|SAS token credential||object|
+|sasSignature|SAS token signature||string|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|accountName|name of the azure account||string|
+|fileSystemName|name of filesystem to be used||string|
+|clientId|client id for azure account||string|
+|close|Whether or not a file changed event raised indicates completion (true) or modification (false)||boolean|
+|closeStreamAfterRead|check for closing stream after read||boolean|
+|credentialType|Determines the credential strategy to adopt|CLIENT\_SECRET|object|
+|dataCount|count number of bytes to download||integer|
+|dataLakeServiceClient|service client of data lake||object|
+|directoryName|directory of the file to be handled in component||string|
+|downloadLinkExpiration|download link expiration time||integer|
+|expression|expression for queryInputStream||string|
+|fileDir|directory of file to do operations in the local system||string|
+|fileName|name of file to be handled in component||string|
+|fileOffset|offset position in file for different operations||integer|
+|maxResults|maximum number of results to show at a time||integer|
+|maxRetryRequests|no of retries to a given request||integer|
+|openOptions|set open options for creating file||object|
+|path|path in azure data lake for operations||string|
+|permission|permission string for the file||string|
+|position|This parameter allows the caller to upload data in parallel and control the order in which it is appended to the file.||integer|
+|recursive|recursively include all paths||boolean|
+|regex|regular expression for matching file names||string|
+|retainUncommitedData|Whether or not uncommitted data is to be retained after the operation||boolean|
+|serviceClient|data lake service client for azure storage data lake||object|
+|sharedKeyCredential|shared key credential for azure data lake gen2||object|
+|tenantId|tenant id for azure account||string|
+|timeout|Timeout for operation||object|
+|umask|umask permission for file||string|
+|userPrincipalNameReturned|whether or not to use upn||boolean|
+|sendEmptyMessageWhenIdle|If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.|false|boolean|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|pollStrategy|A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.||object|
+|operation|operation to be performed|listFileSystem|object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|backoffErrorThreshold|The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.||integer|
+|backoffIdleThreshold|The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.||integer|
+|backoffMultiplier|To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.||integer|
+|delay|Milliseconds before the next poll.|500|integer|
+|greedy|If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.|false|boolean|
+|initialDelay|Milliseconds before the first poll starts.|1000|integer|
+|repeatCount|Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.|0|integer|
+|runLoggingLevel|The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.|TRACE|object|
+|scheduledExecutorService|Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.||object|
+|scheduler|To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler|none|object|
+|schedulerProperties|To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.||object|
+|startScheduler|Whether the scheduler should be auto started.|true|boolean|
+|timeUnit|Time unit for initialDelay and delay options.|MILLISECONDS|object|
+|useFixedDelay|Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.|true|boolean|
+|accountKey|account key for authentication||string|
+|clientSecret|client secret for azure account||string|
+|clientSecretCredential|client secret credential for authentication||object|
+|sasCredential|SAS token credential||object|
+|sasSignature|SAS token signature||string|

camel-azure-storage-queue.md

@@ -0,0 +1,424 @@
+# Azure-storage-queue
+
+**Since Camel 3.3**
+
+**Both producer and consumer are supported**
+
+The Azure Storage Queue component supports storing and retrieving the
+messages to/from [Azure Storage
+Queue](https://azure.microsoft.com/services/storage/queues/) service
+using **Azure APIs v12**. However, in the case of versions above v12, we
+will see if this component can adopt these changes depending on how much
+breaking changes can result.
+
+Prerequisites
+
+You must have a valid Windows Azure Storage account. More information is
+available at [Azure Documentation
+Portal](https://docs.microsoft.com/azure/).
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-azure-storage-queue</artifactId>
+        <version>x.x.x</version>
+      <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# URI Format
+
+    azure-storage-queue://accountName[/queueName][?options]
+
+In the case of consumer, `accountName` and `queueName` are required.
+
+In the case of producer, it depends on the operation that being
+requested, for example, if operation is on a service level, e.b:
+`listQueues`, only `accountName` is required, but in the case of
+operation being requested on the queue level, e.g.:
+``createQueue, `sendMessage``, etc., both `accountName` and
+`queueName` are required.
+
+The queue will be created if it does not already exist. You can append
+query options to the URI in the following format:
+`?options=value&option2=value&...`
+
+**Required information options:**
+
+**Required information options:**
+
+To use this component, you have multiple options to provide the required
+Azure authentication information:
+
+-   By providing your own QueueServiceClient instance which can be
+    injected into `serviceClient`.
+
+-   Via Azure Identity, when specifying `credentialType=AZURE_IDENTITY`
+    and providing required [environment
+    variables](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/identity/azure-identity#environment-variables).
+    This enables service principal (e.g. app registration)
+    authentication with secret/certificate as well as username password.
+
+-   Via shared storage account key, when specifying
+    `credentialType=SHARED_ACCOUNT_KEY` and providing `accountName` and
+    `accessKey` for your Azure account, this is the simplest way to get
+    started. The accessKey can be generated through your Azure portal.
+    Note that this is the default authentication strategy.
+
+-   Via shared storage account key, when specifying
+    `credentialType=SHARED_KEY_CREDENTIAL` and providing a
+    [StorageSharedKeyCredential](https://azuresdkartifacts.blob.core.windows.net/azure-sdk-for-java/staging/apidocs/com/azure/storage/common/StorageSharedKeyCredential.html)
+    instance which can be injected into `credentials` option.
+
+# Usage
+
+For example, to get a message content from the queue `messageQueue` in
+the `storageAccount` storage account and, use the following snippet:
+
+    from("azure-storage-queue://storageAccount/messageQueue?accessKey=yourAccessKey").
+    to("file://queuedirectory");
+
+## Advanced Azure Storage Queue configuration
+
+If your Camel Application is running behind a firewall or if you need to
+have more control over the `QueueServiceClient` instance configuration,
+you can create your own instance:
+
+    StorageSharedKeyCredential credential = new StorageSharedKeyCredential("yourAccountName", "yourAccessKey");
+    String uri = String.format("https://%s.queue.core.windows.net", "yourAccountName");
+    
+    QueueServiceClient client = new QueueServiceClientBuilder()
+                              .endpoint(uri)
+                              .credential(credential)
+                              .buildClient();
+    // This is camel context
+    context.getRegistry().bind("client", client);
+
+Then refer to this instance in your Camel `azure-storage-queue`
+component configuration:
+
+    from("azure-storage-queue://cameldev/queue1?serviceClient=#client")
+    .to("file://outputFolder?fileName=output.txt&fileExist=Append");
+
+## Automatic detection of QueueServiceClient client in registry
+
+The component is capable of detecting the presence of an
+QueueServiceClient bean into the registry. If it’s the only instance of
+that type, it will be used as the client, and you won’t have to define
+it as uri parameter, like the example above. This may be really useful
+for smarter configuration of the endpoint.
+
+## Azure Storage Queue Producer operations
+
+Camel Azure Storage Queue component provides a wide range of operations
+on the producer side:
+
+**Operations on the service level**
+
+For these operations, `accountName` is **required**.
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>listQueues</code></p></td>
+<td style="text-align: left;"><p>Lists the queues in the storage account
+that pass the filter starting at the specified marker.</p></td>
+</tr>
+</tbody>
+</table>
+
+**Operations on the queue level**
+
+For these operations, `accountName` and `queueName` are **required**.
+
+<table>
+<colgroup>
+<col style="width: 10%" />
+<col style="width: 89%" />
+</colgroup>
+<thead>
+<tr>
+<th style="text-align: left;">Operation</th>
+<th style="text-align: left;">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;"><p><code>createQueue</code></p></td>
+<td style="text-align: left;"><p>Creates a new queue.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>deleteQueue</code></p></td>
+<td style="text-align: left;"><p>Permanently deletes the queue.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>clearQueue</code></p></td>
+<td style="text-align: left;"><p>Deletes all messages in the
+queue..</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>sendMessage</code></p></td>
+<td style="text-align: left;"><p><strong>Default Producer
+Operation</strong> Sends a message with a given time-to-live and timeout
+period where the message is invisible in the queue. The message text is
+evaluated from the exchange message body. By default, if the queue
+doesn’t exist, it will create an empty queue first. If you want to
+disable this, set the config <code>createQueue</code> or header
+<code>CamelAzureStorageQueueCreateQueue</code> to
+<code>false</code>.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>deleteMessage</code></p></td>
+<td style="text-align: left;"><p>Deletes the specified message in the
+queue.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>receiveMessages</code></p></td>
+<td style="text-align: left;"><p>Retrieves up to the maximum number of
+messages from the queue and hides them from other operations for the
+timeout period. However, it will not dequeue the message from the queue
+due to reliability reasons.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>peekMessages</code></p></td>
+<td style="text-align: left;"><p>Peek messages from the front of the
+queue up to the maximum number of messages.</p></td>
+</tr>
+<tr>
+<td style="text-align: left;"><p><code>updateMessage</code></p></td>
+<td style="text-align: left;"><p>Updates the specific message in the
+queue with a new message and resets the visibility timeout. The message
+text is evaluated from the exchange message body.</p></td>
+</tr>
+</tbody>
+</table>
+
+Refer to the example section in this page to learn how to use these
+operations into your camel application.
+
+## Consumer Examples
+
+To consume a queue into a file component with maximum five messages in
+one batch, this can be done like this:
+
+    from("azure-storage-queue://cameldev/queue1?serviceClient=#client&maxMessages=5")
+    .to("file://outputFolder?fileName=output.txt&fileExist=Append");
+
+## Producer Operations Examples
+
+-   `listQueues`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+          // set the header you want the producer to evaluate, refer to the previous
+          // section to learn about the headers that can be set
+          // e.g., to only returns a list of queues with 'awesome' prefix:
+          exchange.getIn().setHeader(QueueConstants.QUEUES_SEGMENT_OPTIONS, new QueuesSegmentOptions().setPrefix("awesome"));
+         })
+        .to("azure-storage-queue://cameldev?serviceClient=#client&operation=listQueues")
+        .log("${body}")
+        .to("mock:result");
+
+-   `createQueue`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+          // set the header you want the producer to evaluate, refer to the previous
+          // section to learn about the headers that can be set
+          // e.g.:
+          exchange.getIn().setHeader(QueueConstants.QUEUE_NAME, "overrideName");
+         })
+        .to("azure-storage-queue://cameldev/test?serviceClient=#client&operation=createQueue");
+
+-   `deleteQueue`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+          // set the header you want the producer to evaluate, refer to the previous
+          // section to learn about the headers that can be set
+          // e.g.:
+          exchange.getIn().setHeader(QueueConstants.QUEUE_NAME, "overrideName");
+         })
+        .to("azure-storage-queue://cameldev/test?serviceClient=#client&operation=deleteQueue");
+
+-   `clearQueue`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+          // set the header you want the producer to evaluate, refer to the previous
+          // section to learn about the headers that can be set
+          // e.g.:
+          exchange.getIn().setHeader(QueueConstants.QUEUE_NAME, "overrideName");
+         })
+        .to("azure-storage-queue://cameldev/test?serviceClient=#client&operation=clearQueue");
+
+-   `sendMessage`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+          // set the header you want the producer to evaluate, refer to the previous
+          // section to learn about the headers that can be set
+          // e.g.:
+          exchange.getIn().setBody("message to send");
+          // we set a visibility of 1min
+          exchange.getIn().setHeader(QueueConstants.VISIBILITY_TIMEOUT, Duration.ofMinutes(1));
+         })
+        .to("azure-storage-queue://cameldev/test?serviceClient=#client");
+
+-   `deleteMessage`:
+
+<!-- -->
+
+    from("direct:start")
+        .process(exchange -> {
+          // set the header you want the producer to evaluate, refer to the previous
+          // section to learn about the headers that can be set
+          // e.g.:
+          // Mandatory header:
+          exchange.getIn().setHeader(QueueConstants.MESSAGE_ID, "1");
+          // Mandatory header:
+          exchange.getIn().setHeader(QueueConstants.POP_RECEIPT, "PAAAAHEEERXXX-1");
+         })
+        .to("azure-storage-queue://cameldev/test?serviceClient=#client&operation=deleteMessage");
+
+-   `receiveMessages`:
+
+<!-- -->
+
+    from("direct:start")
+        .to("azure-storage-queue://cameldev/test?serviceClient=#client&operation=receiveMessages")
+        .process(exchange -> {
+            final List<QueueMessageItem> messageItems = exchange.getMessage().getBody(List.class);
+            messageItems.forEach(messageItem -> System.out.println(messageItem.getMessageText()));
+        })
+       .to("mock:result");
+
+-   `peekMessages`:
+
+<!-- -->
+
+    from("direct:start")
+        .to("azure-storage-queue://cameldev/test?serviceClient=#client&operation=peekMessages")
+        .process(exchange -> {
+            final List<PeekedMessageItem> messageItems = exchange.getMessage().getBody(List.class);
+            messageItems.forEach(messageItem -> System.out.println(messageItem.getMessageText()));
+        })
+       .to("mock:result");
+
+-   `updateMessage`:
+
+<!-- -->
+
+    from("direct:start")
+       .process(exchange -> {
+           // set the header you want the producer to evaluate, refer to the previous
+           // section to learn about the headers that can be set
+           // e.g.:
+           exchange.getIn().setBody("new message text");
+           // Mandatory header:
+           exchange.getIn().setHeader(QueueConstants.MESSAGE_ID, "1");
+           // Mandatory header:
+           exchange.getIn().setHeader(QueueConstants.POP_RECEIPT, "PAAAAHEEERXXX-1");
+           // Mandatory header:
+           exchange.getIn().setHeader(QueueConstants.VISIBILITY_TIMEOUT, Duration.ofMinutes(1));
+        })
+        .to("azure-storage-queue://cameldev/test?serviceClient=#client&operation=updateMessage");
+
+## Development Notes (Important)
+
+When developing on this component, you will need to obtain your Azure
+`accessKey` to run the integration tests. In addition to the mocked unit
+tests, you **will need to run the integration tests with every change
+you make or even client upgrade as the Azure client can break things
+even on minor versions upgrade.** To run the integration tests, on this
+component directory, run the following maven command:
+
+    mvn verify -DaccountName=myacc -DaccessKey=mykey
+
+Whereby `accountName` is your Azure account name and `accessKey` is the
+access key being generated from Azure portal.
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|configuration|The component configurations||object|
+|credentialType|Determines the credential strategy to adopt|SHARED\_ACCOUNT\_KEY|object|
+|serviceClient|Service client to a storage account to interact with the queue service. This client does not hold any state about a particular storage account but is instead a convenient way of sending off appropriate requests to the resource on the service. This client contains all the operations for interacting with a queue account in Azure Storage. Operations allowed by the client are creating, listing, and deleting queues, retrieving and updating properties of the account, and retrieving statistics of the account.||object|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|createQueue|When is set to true, the queue will be automatically created when sending messages to the queue.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|operation|Queue service operation hint to the producer||object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|healthCheckConsumerEnabled|Used for enabling or disabling all consumer based health checks from this component|true|boolean|
+|healthCheckProducerEnabled|Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.|true|boolean|
+|maxMessages|Maximum number of messages to get, if there are less messages exist in the queue than requested all the messages will be returned. If left empty only 1 message will be retrieved, the allowed range is 1 to 32 messages.|1|integer|
+|messageId|The ID of the message to be deleted or updated.||string|
+|popReceipt|Unique identifier that must match for the message to be deleted or updated.||string|
+|timeout|An optional timeout applied to the operation. If a response is not returned before the timeout concludes a RuntimeException will be thrown.||object|
+|timeToLive|How long the message will stay alive in the queue. If unset the value will default to 7 days, if -1 is passed the message will not expire. The time to live must be -1 or any positive number. The format should be in this form: PnDTnHnMn.nS., e.g: PT20.345S -- parses as 20.345 seconds, P2D -- parses as 2 days However, in case you are using EndpointDsl/ComponentDsl, you can do something like Duration.ofSeconds() since these Java APIs are typesafe.||object|
+|visibilityTimeout|The timeout period for how long the message is invisible in the queue. The timeout must be between 1 seconds and 7 days. The format should be in this form: PnDTnHnMn.nS., e.g: PT20.345S -- parses as 20.345 seconds, P2D -- parses as 2 days However, in case you are using EndpointDsl/ComponentDsl, you can do something like Duration.ofSeconds() since these Java APIs are typesafe.||object|
+|accessKey|Access key for the associated azure account name to be used for authentication with azure queue services||string|
+|credentials|StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information||object|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|accountName|Azure account name to be used for authentication with azure queue services||string|
+|queueName|The queue resource name||string|
+|credentialType|Determines the credential strategy to adopt|SHARED\_ACCOUNT\_KEY|object|
+|serviceClient|Service client to a storage account to interact with the queue service. This client does not hold any state about a particular storage account but is instead a convenient way of sending off appropriate requests to the resource on the service. This client contains all the operations for interacting with a queue account in Azure Storage. Operations allowed by the client are creating, listing, and deleting queues, retrieving and updating properties of the account, and retrieving statistics of the account.||object|
+|sendEmptyMessageWhenIdle|If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.|false|boolean|
+|bridgeErrorHandler|Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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|
+|exceptionHandler|To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.||object|
+|exchangePattern|Sets the exchange pattern when the consumer creates an exchange.||object|
+|pollStrategy|A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.||object|
+|createQueue|When is set to true, the queue will be automatically created when sending messages to the queue.|false|boolean|
+|operation|Queue service operation hint to the producer||object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|maxMessages|Maximum number of messages to get, if there are less messages exist in the queue than requested all the messages will be returned. If left empty only 1 message will be retrieved, the allowed range is 1 to 32 messages.|1|integer|
+|messageId|The ID of the message to be deleted or updated.||string|
+|popReceipt|Unique identifier that must match for the message to be deleted or updated.||string|
+|timeout|An optional timeout applied to the operation. If a response is not returned before the timeout concludes a RuntimeException will be thrown.||object|
+|timeToLive|How long the message will stay alive in the queue. If unset the value will default to 7 days, if -1 is passed the message will not expire. The time to live must be -1 or any positive number. The format should be in this form: PnDTnHnMn.nS., e.g: PT20.345S -- parses as 20.345 seconds, P2D -- parses as 2 days However, in case you are using EndpointDsl/ComponentDsl, you can do something like Duration.ofSeconds() since these Java APIs are typesafe.||object|
+|visibilityTimeout|The timeout period for how long the message is invisible in the queue. The timeout must be between 1 seconds and 7 days. The format should be in this form: PnDTnHnMn.nS., e.g: PT20.345S -- parses as 20.345 seconds, P2D -- parses as 2 days However, in case you are using EndpointDsl/ComponentDsl, you can do something like Duration.ofSeconds() since these Java APIs are typesafe.||object|
+|backoffErrorThreshold|The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.||integer|
+|backoffIdleThreshold|The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.||integer|
+|backoffMultiplier|To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.||integer|
+|delay|Milliseconds before the next poll.|500|integer|
+|greedy|If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.|false|boolean|
+|initialDelay|Milliseconds before the first poll starts.|1000|integer|
+|repeatCount|Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.|0|integer|
+|runLoggingLevel|The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.|TRACE|object|
+|scheduledExecutorService|Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.||object|
+|scheduler|To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler|none|object|
+|schedulerProperties|To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.||object|
+|startScheduler|Whether the scheduler should be auto started.|true|boolean|
+|timeUnit|Time unit for initialDelay and delay options.|MILLISECONDS|object|
+|useFixedDelay|Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.|true|boolean|
+|accessKey|Access key for the associated azure account name to be used for authentication with azure queue services||string|
+|credentials|StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information||object|

camel-bean-validator.md

@@ -0,0 +1,218 @@
+# Bean-validator
+
+**Since Camel 2.3**
+
+**Only producer is supported**
+
+The Validator component performs bean validation of the message body
+using the Java Bean Validation API ([JSR
+303](http://jcp.org/en/jsr/detail?id=303)). Camel uses the reference
+implementation, which is [Hibernate
+Validator](https://docs.jboss.org/hibernate/validator/6.2/reference/en-US/html_single/).
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+    <dependency>
+        <groupId>org.apache.camel</groupId>
+        <artifactId>camel-bean-validator</artifactId>
+        <version>x.y.z</version>
+        <!-- use the same version as your Camel core version -->
+    </dependency>
+
+# URI format
+
+    bean-validator:label[?options]
+
+Where **label** is an arbitrary text value describing the endpoint. You
+can append query options to the URI in the following format:
+`?option=value&option=value&...`
+
+# OSGi deployment
+
+To use Hibernate Validator in the OSGi environment use dedicated
+`ValidationProviderResolver` implementation, just as
+`org.apache.camel.component.bean.validator.HibernateValidationProviderResolver`.
+The snippet below demonstrates this approach. You can also use
+`HibernateValidationProviderResolver`.
+
+## Using HibernateValidationProviderResolver
+
+Java  
+from("direct:test").
+to("bean-validator://ValidationProviderResolverTest?validationProviderResolver=#myValidationProviderResolver");
+
+XML  
+<bean id="myValidationProviderResolver" class="org.apache.camel.component.bean.validator.HibernateValidationProviderResolver"/>
+
+If no custom `ValidationProviderResolver` is defined and the validator
+component has been deployed into the OSGi environment, the
+`HibernateValidationProviderResolver` will be automatically used.
+
+# Example
+
+Assumed we have a java bean with the following annotations
+
+**Car.java**
+
+    public class Car {
+    
+        @NotNull
+        private String manufacturer;
+    
+        @NotNull
+        @Size(min = 5, max = 14, groups = OptionalChecks.class)
+        private String licensePlate;
+    
+        // getter and setter
+    }
+
+and an interface definition for our custom validation group
+
+**OptionalChecks.java**
+
+    public interface OptionalChecks {
+    }
+
+with the following Camel route, only the **@NotNull** constraints on the
+attributes `manufacturer` and `licensePlate` will be validated (Camel
+uses the default group `jakarta.validation.groups.Default`).
+
+    from("direct:start")
+    .to("bean-validator://x")
+    .to("mock:end")
+
+If you want to check the constraints from the group `OptionalChecks`,
+you have to define the route like this
+
+    from("direct:start")
+    .to("bean-validator://x?group=OptionalChecks")
+    .to("mock:end")
+
+If you want to check the constraints from both groups, you have to
+define a new interface first:
+
+**AllChecks.java**
+
+    @GroupSequence({Default.class, OptionalChecks.class})
+    public interface AllChecks {
+    }
+
+And then your route definition should look like this:
+
+    from("direct:start")
+    .to("bean-validator://x?group=AllChecks")
+    .to("mock:end")
+
+And if you have to provide your own message interpolator, traversable
+resolver and constraint validator factory, you have to write a route
+like this:
+
+Java  
+<bean id="myMessageInterpolator" class="my.ConstraintValidatorFactory" />  
+<bean id="myTraversableResolver" class="my.TraversableResolver" />  
+<bean id="myConstraintValidatorFactory" class="my.ConstraintValidatorFactory" />
+
+XML  
+from("direct:start")
+.to("bean-validator://x?group=AllChecks\&messageInterpolator=#myMessageInterpolator
+\&traversableResolver=#myTraversableResolver\&constraintValidatorFactory=#myConstraintValidatorFactory")
+.to("mock:end")
+
+It’s also possible to describe your constraints as XML and not as Java
+annotations. In this case, you have to provide the files
+`META-INF/validation.xml` and `constraints-car.xml` which could look
+like this:
+
+validation.xml  
+<validation-config
+xmlns="https://jakarta.ee/xml/ns/validation/configuration"
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+xsi:schemaLocation="https://jakarta.ee/xml/ns/validation/configuration https://jakarta.ee/xml/ns/validation/validation-configuration-3.0.xsd"
+version="3.0">
+
+        <default-provider>org.hibernate.validator.HibernateValidator</default-provider>
+        <message-interpolator>org.hibernate.validator.engine.ResourceBundleMessageInterpolator</message-interpolator>
+        <traversable-resolver>org.hibernate.validator.engine.resolver.DefaultTraversableResolver</traversable-resolver>
+        <constraint-validator-factory>org.hibernate.validator.engine.ConstraintValidatorFactoryImpl</constraint-validator-factory>
+        <constraint-mapping>/constraints-car.xml</constraint-mapping>
+    
+    </validation-config>
+
+constraints-car.xml  
+<constraint-mappings
+xmlns="https://jakarta.ee/xml/ns/validation/mapping"
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+xsi:schemaLocation="https://jakarta.ee/xml/ns/validation/mapping
+https://jakarta.ee/xml/ns/validation/validation-mapping-3.0.xsd"
+version="3.0">
+
+        <default-package>org.apache.camel.component.bean.validator</default-package>
+    
+        <bean class="CarWithoutAnnotations" ignore-annotations="true">
+            <field name="manufacturer">
+                <constraint annotation="jakarta.validation.constraints.NotNull" />
+            </field>
+    
+            <field name="licensePlate">
+                <constraint annotation="jakarta.validation.constraints.NotNull" />
+    
+                <constraint annotation="jakarta.validation.constraints.Size">
+                    <groups>
+                        <value>org.apache.camel.component.bean.validator.OptionalChecks</value>
+                    </groups>
+                    <element name="min">5</element>
+                    <element name="max">14</element>
+                </constraint>
+            </field>
+        </bean>
+    </constraint-mappings>
+
+Here is the XML syntax for the example route definition where
+**OrderedChecks** can be
+[https://github.com/apache/camel/blob/main/components/camel-bean-validator/src/test/java/org/apache/camel/component/bean/validator/OrderedChecks.java](https://github.com/apache/camel/blob/main/components/camel-bean-validator/src/test/java/org/apache/camel/component/bean/validator/OrderedChecks.java)
+
+Note that the body should include an instance of a class to validate.
+
+    <beans xmlns="http://www.springframework.org/schema/beans"
+           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+           xsi:schemaLocation="
+        http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
+        http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd">
+    
+        <camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
+            <route>
+                <from uri="direct:start"/>
+                <to uri="bean-validator://x?group=org.apache.camel.component.bean.validator.OrderedChecks"/>
+            </route>
+        </camelContext>
+    </beans>
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|ignoreXmlConfiguration|Whether to ignore data from the META-INF/validation.xml file.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|constraintValidatorFactory|To use a custom ConstraintValidatorFactory||object|
+|messageInterpolator|To use a custom MessageInterpolator||object|
+|traversableResolver|To use a custom TraversableResolver||object|
+|validationProviderResolver|To use a a custom ValidationProviderResolver||object|
+|validatorFactory|To use a custom ValidatorFactory||object|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|label|Where label is an arbitrary text value describing the endpoint||string|
+|group|To use a custom validation group|jakarta.validation.groups.Default|string|
+|ignoreXmlConfiguration|Whether to ignore data from the META-INF/validation.xml file.|false|boolean|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|constraintValidatorFactory|To use a custom ConstraintValidatorFactory||object|
+|messageInterpolator|To use a custom MessageInterpolator||object|
+|traversableResolver|To use a custom TraversableResolver||object|
+|validationProviderResolver|To use a a custom ValidationProviderResolver||object|
+|validatorFactory|To use a custom ValidatorFactory||object|

camel-bean.md

@@ -0,0 +1,124 @@
+# Bean
+
+**Since Camel 1.0**
+
+**Only producer is supported**
+
+The Bean component binds beans to Camel message exchanges.
+
+# URI format
+
+    bean:beanName[?options]
+
+Where `beanName` can be any string used to look up the bean in the
+Registry
+
+# Examples
+
+A **bean:** endpoint cannot be defined as the input to the route; i.e.,
+you cannot consume from it, you can only route from some inbound message
+Endpoint to the bean endpoint as output, such as the **direct** endpoint
+as input.
+
+Suppose you have the following POJO class to be used by Camel
+
+    package com.foo;
+    
+    public class MyBean {
+    
+        public String saySomething(String input) {
+            return "Hello " + input;
+        }
+    }
+
+Then the bean can be called in a Camel route by the fully qualified
+class name:
+
+Java  
+from("direct:hello")
+.to("bean:com.foo.MyBean");
+
+XML  
+<route>  
+<from uri="direct:hello"/>  
+<to uri="bean:com.foo.MyBean"/>  
+</route>
+
+What happens is that when the exchange is routed to the MyBean, then
+Camel will use the Bean Binding to invoke the bean, in this case the
+*saySomething* method, by converting the `Exchange` in body to the
+`String` type and storing the output of the method back to the Exchange
+again.
+
+The bean component can also call a bean by *bean id* by looking up the
+bean in the [Registry](#manual::registry.adoc) instead of using the
+class name.
+
+# Java DSL specific bean syntax
+
+Java DSL comes with syntactic sugar for the [Bean](#bean-component.adoc)
+component. Instead of specifying the bean explicitly as the endpoint
+(i.e., `to("bean:beanName")`) you can use the following syntax:
+
+    // Send a message to the bean endpoint
+    // and invoke method using Bean Binding.
+    from("direct:start").bean("beanName");
+    
+    // Send a message to the bean endpoint
+    // and invoke given method.
+    from("direct:start").bean("beanName", "methodName");
+
+Instead of passing the name of the reference to the bean (so that Camel
+will look up for it in the [Registry](#manual::registry.adoc)), you can
+specify the bean itself:
+
+    // Send a message to the given bean instance.
+    from("direct:start").bean(new ExampleBean());
+    
+    // Explicit selection of bean method to be invoked.
+    from("direct:start").bean(new ExampleBean(), "methodName");
+    
+    // Camel will create the instance of bean and cache it for you.
+    from("direct:start").bean(ExampleBean.class);
+
+This bean could be a lambda if you cast the lambda to a
+`@FunctionalInterface`
+
+    @FunctionalInterface
+    public interface ExampleInterface() {
+        @Handler String methodName();
+    }
+    
+    from("direct:start")
+        .bean((ExampleInterface) () -> ""))
+
+# Bean Binding
+
+The [Bean Binding](#manual::bean-binding.adoc) mechanism defines how
+methods to be invoked are chosen (if they are not specified explicitly
+through the **method** parameter) and how parameter values are
+constructed from the Message. These are used throughout all the various
+[Bean Integration](#manual::bean-integration.adoc) mechanisms in Camel.
+
+See also related [Bean Language](#languages:bean-language.adoc).
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|scope|Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple times while processing the request. The bean does not have to be thread-safe as the instance is only called from the same request. When using delegate scope, then the bean will be looked up or created per call. However in case of lookup then this is delegated to the bean registry such as Spring or CDI (if in use), which depends on their configuration can act as either singleton or prototype scope. so when using prototype then this depends on the delegated registry.|Singleton|object|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+|beanInfoCacheSize|Maximum cache size of internal cache for bean introspection. Setting a value of 0 or negative will disable the cache.|1000|integer|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|beanName|Sets the name of the bean to invoke||string|
+|method|Sets the name of the method to invoke on the bean||string|
+|scope|Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple times while processing the request. The bean does not have to be thread-safe as the instance is only called from the same request. When using prototype scope, then the bean will be looked up or created per call. However in case of lookup then this is delegated to the bean registry such as Spring or CDI (if in use), which depends on their configuration can act as either singleton or prototype scope. so when using prototype then this depends on the delegated registry.|Singleton|object|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|parameters|Used for configuring additional properties on the bean||object|

camel-bonita.md

@@ -0,0 +1,60 @@
+# Bonita
+
+**Since Camel 2.19**
+
+**Only producer is supported**
+
+Used for communicating with a remote Bonita BPM process engine.
+
+# URI format
+
+    bonita://[operation]?[options]
+
+Where **operation** is the specific action to perform on Bonita.
+
+# Body content
+
+For the startCase operation, the input variables are retrieved from the
+body message. This one has to contain a `Map<String,Serializable>`.
+
+# Examples
+
+The following example starts a new case in Bonita:
+
+    from("direct:start").to("bonita:startCase?hostname=localhost&amp;port=8080&amp;processName=TestProcess&amp;username=install&amp;password=install");
+
+# Dependencies
+
+To use Bonita in your Camel routes, you need to add a dependency on
+**camel-bonita**, which implements the component.
+
+If you use Maven, you can add the following to your pom.xml,
+substituting the version number for the latest and greatest release (see
+the download page for the latest versions).
+
+    <dependency>
+      <groupId>org.apache.camel</groupId>
+      <artifactId>camel-bonita</artifactId>
+      <version>x.x.x</version>
+    </dependency>
+
+## Component Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|autowiredEnabled|Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.|true|boolean|
+
+## Endpoint Configurations
+
+  
+|Name|Description|Default|Type|
+|---|---|---|---|
+|operation|Operation to use||object|
+|hostname|Hostname where Bonita engine runs|localhost|string|
+|port|Port of the server hosting Bonita engine|8080|string|
+|processName|Name of the process involved in the operation||string|
+|lazyStartProducer|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 starting the producer may take a little time and prolong the total processing time of the processing.|false|boolean|
+|password|Password to authenticate to Bonita engine.||string|
+|username|Username to authenticate to Bonita engine.||string|