[36/51] [partial] camel git commit: CAMEL-9541: Use -component as suffix for component docs.

[da...@apache.org]

http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-aws/src/main/docs/aws-sqs-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-sqs-component.adoc b/components/camel-aws/src/main/docs/aws-sqs-component.adoc
new file mode 100644
index 0000000..9ed1de2
--- /dev/null
+++ b/components/camel-aws/src/main/docs/aws-sqs-component.adoc
@@ -0,0 +1,245 @@
+[[AWS-SQS-SQSComponent]]
+SQS Component
+~~~~~~~~~~~~~
+
+*Available as of Camel 2.6*
+
+The sqs component supports sending and receiving messages to
+http://aws.amazon.com/sqs[Amazon's SQS] service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon SQS. More information are available at
+http://aws.amazon.com/sqs[Amazon SQS].
+
+[[AWS-SQS-URIFormat]]
+URI Format
+^^^^^^^^^^
+
+[source,java]
+------------------------------
+aws-sqs://queueNameOrArn[?options]
+------------------------------
+
+The queue will be created if they don't already exists. +
+ You can append query options to the URI in the following format,
+?options=value&option2=value&...
+
+[[AWS-SQS-URIOptions]]
+URI Options
+^^^^^^^^^^^
+
+
+// component options: START
+The AWS Simple Queue Service component has no options.
+// component options: END
+
+
+
+
+
+
+
+
+// endpoint options: START
+The AWS Simple Queue Service component supports 45 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| queueNameOrArn | common |  | String | *Required* Queue name or ARN
+| accessKey | common |  | String | Amazon AWS Access Key
+| amazonSQSClient | common |  | AmazonSQS | To use the AmazonSQS as client
+| amazonSQSEndpoint | common |  | String | The region with which the AWS-SQS client wants to work with. Only works if Camel creates the AWS-SQS client i.e. if you explicitly set amazonSQSClient then this setting will have no effect. You would have to set it on the client you create directly
+| headerFilterStrategy | common |  | HeaderFilterStrategy | To use a custom HeaderFilterStrategy to map headers to/from Camel.
+| queueOwnerAWSAccountId | common |  | String | Specify the queue owner aws account id when you need to connect the queue with different account owner.
+| region | common |  | String | Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL.
+| secretKey | common |  | String | Amazon AWS Secret Key
+| attributeNames | consumer |  | String | A list of attribute names to receive when consuming. Multiple names can be separated by comma.
+| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| concurrentConsumers | consumer | 1 | int | Allows you to use multiple threads to poll the sqs queue to increase throughput
+| defaultVisibilityTimeout | consumer |  | Integer | The default visibility timeout (in seconds)
+| deleteAfterRead | consumer | true | boolean | Delete message from SQS after it has been read
+| deleteIfFiltered | consumer | true | boolean | Whether or not to send the DeleteMessage to the SQS queue if an exchange fails to get through a filter. If 'false' and exchange does not make it through a Camel filter upstream in the route then don't send DeleteMessage.
+| extendMessageVisibility | consumer | false | boolean | 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.
+| maxMessagesPerPoll | consumer |  | int | 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.
+| messageAttributeNames | consumer |  | String | A list of message attribute names to receive when consuming. Multiple names can be separated by comma.
+| sendEmptyMessageWhenIdle | consumer | false | boolean | If the polling consumer did not poll any files you can enable this option to send an empty message (no body) instead.
+| visibilityTimeout | consumer |  | Integer | 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 make sense if its different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently.
+| waitTimeSeconds | consumer |  | Integer | 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.
+| exceptionHandler | consumer (advanced) |  | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| pollStrategy | consumer (advanced) |  | PollingConsumerPollStrategy | 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.
+| delaySeconds | producer |  | Integer | Delay sending messages for a number of seconds.
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
+| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
+| backoffErrorThreshold | scheduler |  | int | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.
+| backoffIdleThreshold | scheduler |  | int | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.
+| backoffMultiplier | scheduler |  | int | 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.
+| delay | scheduler | 500 | long | Milliseconds before the next poll. You can also specify time values using units such as 60s (60 seconds) 5m30s (5 minutes and 30 seconds) and 1h (1 hour).
+| greedy | scheduler | false | boolean | If greedy is enabled then the ScheduledPollConsumer will run immediately again if the previous run polled 1 or more messages.
+| initialDelay | scheduler | 1000 | long | Milliseconds before the first poll starts. You can also specify time values using units such as 60s (60 seconds) 5m30s (5 minutes and 30 seconds) and 1h (1 hour).
+| runLoggingLevel | scheduler | TRACE | LoggingLevel | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.
+| scheduledExecutorService | scheduler |  | 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.
+| scheduler | scheduler | none | ScheduledPollConsumerScheduler | To use a cron scheduler from either camel-spring or camel-quartz2 component
+| schedulerProperties | scheduler |  | Map | To configure additional properties when using a custom scheduler or any of the Quartz2 Spring based scheduler.
+| startScheduler | scheduler | true | boolean | Whether the scheduler should be auto started.
+| timeUnit | scheduler | MILLISECONDS | TimeUnit | Time unit for initialDelay and delay options.
+| useFixedDelay | scheduler | true | boolean | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.
+| proxyHost | proxy |  | String | To define a proxy host when instantiating the SQS client
+| proxyPort | proxy |  | Integer | To define a proxy port when instantiating the SQS client
+| maximumMessageSize | queue |  | Integer | The maximumMessageSize (in bytes) an SQS message can contain for this queue.
+| messageRetentionPeriod | queue |  | Integer | The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue.
+| policy | queue |  | String | The policy for this queue
+| receiveMessageWaitTimeSeconds | queue |  | Integer | If you do not specify WaitTimeSeconds in the request the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait.
+| redrivePolicy | queue |  | String | Specify the policy that send message to DeadLetter queue. See detail at Amazon docs.
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+
+
+
+
+
+Required SQS component options
+
+You have to provide the amazonSQSClient in the
+link:registry.html[Registry] or your accessKey and secretKey to access
+the http://aws.amazon.com/sqs[Amazon's SQS].
+
+[[AWS-SQS-BatchConsumer]]
+Batch Consumer
+^^^^^^^^^^^^^^
+
+This component implements the link:batch-consumer.html[Batch Consumer].
+
+This allows you for instance to know how many messages exists in this
+batch and for instance let the link:aggregator.html[Aggregator]
+aggregate this number of messages.
+
+[[AWS-SQS-Usage]]
+Usage
+^^^^^
+
+[[AWS-SQS-MessageheaderssetbytheSQSproducer]]
+Message headers set by the SQS producer
++++++++++++++++++++++++++++++++++++++++
+
+[width="100%",cols="10%,10%,80%",options="header",]
+|=======================================================================
+|Header |Type |Description
+
+|`CamelAwsSqsMD5OfBody` |`String` |The MD5 checksum of the Amazon SQS message.
+
+|`CamelAwsSqsMessageId` |`String` |The Amazon SQS message ID.
+
+|`CamelAwsSqsDelaySeconds` |`Integer` |Since *Camel 2.11*, the delay seconds that the Amazon SQS message can be
+see by others.
+|=======================================================================
+
+[[AWS-SQS-MessageheaderssetbytheSQSconsumer]]
+Message headers set by the SQS consumer
++++++++++++++++++++++++++++++++++++++++
+
+[width="100%",cols="10%,10%,80%",options="header",]
+|=======================================================================
+|Header |Type |Description
+
+|`CamelAwsSqsMD5OfBody` |`String` |The MD5 checksum of the Amazon SQS message.
+
+|`CamelAwsSqsMessageId` |`String` |The Amazon SQS message ID. 
+
+|`CamelAwsSqsReceiptHandle` |`String` |The Amazon SQS message receipt handle.
+
+|`CamelAwsSqsAttributes` |`Map<String, String>` |The Amazon SQS message attributes.
+|=======================================================================
+
+[[AWS-SQS-AdvancedAmazonSQSconfiguration]]
+Advanced AmazonSQS configuration
+++++++++++++++++++++++++++++++++
+
+If your Camel Application is running behind a firewall or if you need to
+have more control over the AmazonSQS instance configuration, you can
+create your own instance:
+
+[source,java]
+--------------------------------------------------------------------------------------
+AWSCredentials awsCredentials = new BasicAWSCredentials("myAccessKey", "mySecretKey");
+
+ClientConfiguration clientConfiguration = new ClientConfiguration();
+clientConfiguration.setProxyHost("http://myProxyHost");
+clientConfiguration.setProxyPort(8080);
+
+AmazonSQS client = new AmazonSQSClient(awsCredentials, clientConfiguration);
+
+registry.bind("client", client);
+--------------------------------------------------------------------------------------
+
+and refer to it in your Camel aws-sqs component configuration:
+
+[source,java]
+---------------------------------------------------------------------------------
+from("aws-sqs://MyQueue?amazonSQSClient=#client&delay=5000&maxMessagesPerPoll=5")
+.to("mock:result");
+---------------------------------------------------------------------------------
+
+[[AWS-SQS-Dependencies]]
+Dependencies
+^^^^^^^^^^^^
+
+Maven users will need to add the following dependency to their pom.xml.
+
+*pom.xml*
+
+[source,xml]
+---------------------------------------
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-aws</artifactId>
+    <version>${camel-version}</version>
+</dependency>
+---------------------------------------
+
+where `${camel-version`} must be replaced by the actual version of Camel
+(2.6 or higher).
+
+[[AWS-SQS-JMS-styleSelectors]]
+JMS-style Selectors
+^^^^^^^^^^^^^^^^^^^
+
+SQS does not allow selectors, but you can effectively achieve this by
+using the link:message-filter.html[Camel Filter EIP] and setting an
+appropriate `visibilityTimeout`. When SQS dispatches a message, it will
+wait up to the visibility timeout before it will try 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:
+
+[source,java]
+------------------------------------------------------------------------------------------------------
+from("aws-sqs://MyQueue?amazonSQSClient=#client&defaultVisibilityTimeout=5000&deleteIfFiltered=false")
+.filter("${header.login} == true")
+.to("mock:result");
+------------------------------------------------------------------------------------------------------
+
+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 miliseconds, the message will become visible to other
+consumers.
+
+[[AWS-SQS-SeeAlso]]
+See Also
+^^^^^^^^
+
+* link:configuring-camel.html[Configuring Camel]
+* link:component.html[Component]
+* link:endpoint.html[Endpoint]
+* link:getting-started.html[Getting Started]
+
+* link:aws.html[AWS Component]
+

http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-aws/src/main/docs/aws-sqs.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-sqs.adoc b/components/camel-aws/src/main/docs/aws-sqs.adoc
deleted file mode 100644
index 9ed1de2..0000000
--- a/components/camel-aws/src/main/docs/aws-sqs.adoc
+++ /dev/null
@@ -1,245 +0,0 @@
-[[AWS-SQS-SQSComponent]]
-SQS Component
-~~~~~~~~~~~~~
-
-*Available as of Camel 2.6*
-
-The sqs component supports sending and receiving messages to
-http://aws.amazon.com/sqs[Amazon's SQS] service.
-
-Prerequisites
-
-You must have a valid Amazon Web Services developer account, and be
-signed up to use Amazon SQS. More information are available at
-http://aws.amazon.com/sqs[Amazon SQS].
-
-[[AWS-SQS-URIFormat]]
-URI Format
-^^^^^^^^^^
-
-[source,java]
-------------------------------
-aws-sqs://queueNameOrArn[?options]
-------------------------------
-
-The queue will be created if they don't already exists. +
- You can append query options to the URI in the following format,
-?options=value&option2=value&...
-
-[[AWS-SQS-URIOptions]]
-URI Options
-^^^^^^^^^^^
-
-
-// component options: START
-The AWS Simple Queue Service component has no options.
-// component options: END
-
-
-
-
-
-
-
-
-// endpoint options: START
-The AWS Simple Queue Service component supports 45 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| queueNameOrArn | common |  | String | *Required* Queue name or ARN
-| accessKey | common |  | String | Amazon AWS Access Key
-| amazonSQSClient | common |  | AmazonSQS | To use the AmazonSQS as client
-| amazonSQSEndpoint | common |  | String | The region with which the AWS-SQS client wants to work with. Only works if Camel creates the AWS-SQS client i.e. if you explicitly set amazonSQSClient then this setting will have no effect. You would have to set it on the client you create directly
-| headerFilterStrategy | common |  | HeaderFilterStrategy | To use a custom HeaderFilterStrategy to map headers to/from Camel.
-| queueOwnerAWSAccountId | common |  | String | Specify the queue owner aws account id when you need to connect the queue with different account owner.
-| region | common |  | String | Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL.
-| secretKey | common |  | String | Amazon AWS Secret Key
-| attributeNames | consumer |  | String | A list of attribute names to receive when consuming. Multiple names can be separated by comma.
-| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| concurrentConsumers | consumer | 1 | int | Allows you to use multiple threads to poll the sqs queue to increase throughput
-| defaultVisibilityTimeout | consumer |  | Integer | The default visibility timeout (in seconds)
-| deleteAfterRead | consumer | true | boolean | Delete message from SQS after it has been read
-| deleteIfFiltered | consumer | true | boolean | Whether or not to send the DeleteMessage to the SQS queue if an exchange fails to get through a filter. If 'false' and exchange does not make it through a Camel filter upstream in the route then don't send DeleteMessage.
-| extendMessageVisibility | consumer | false | boolean | 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.
-| maxMessagesPerPoll | consumer |  | int | 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.
-| messageAttributeNames | consumer |  | String | A list of message attribute names to receive when consuming. Multiple names can be separated by comma.
-| sendEmptyMessageWhenIdle | consumer | false | boolean | If the polling consumer did not poll any files you can enable this option to send an empty message (no body) instead.
-| visibilityTimeout | consumer |  | Integer | 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 make sense if its different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently.
-| waitTimeSeconds | consumer |  | Integer | 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.
-| exceptionHandler | consumer (advanced) |  | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| pollStrategy | consumer (advanced) |  | PollingConsumerPollStrategy | 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.
-| delaySeconds | producer |  | Integer | Delay sending messages for a number of seconds.
-| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
-| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
-| backoffErrorThreshold | scheduler |  | int | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.
-| backoffIdleThreshold | scheduler |  | int | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.
-| backoffMultiplier | scheduler |  | int | 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.
-| delay | scheduler | 500 | long | Milliseconds before the next poll. You can also specify time values using units such as 60s (60 seconds) 5m30s (5 minutes and 30 seconds) and 1h (1 hour).
-| greedy | scheduler | false | boolean | If greedy is enabled then the ScheduledPollConsumer will run immediately again if the previous run polled 1 or more messages.
-| initialDelay | scheduler | 1000 | long | Milliseconds before the first poll starts. You can also specify time values using units such as 60s (60 seconds) 5m30s (5 minutes and 30 seconds) and 1h (1 hour).
-| runLoggingLevel | scheduler | TRACE | LoggingLevel | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.
-| scheduledExecutorService | scheduler |  | 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.
-| scheduler | scheduler | none | ScheduledPollConsumerScheduler | To use a cron scheduler from either camel-spring or camel-quartz2 component
-| schedulerProperties | scheduler |  | Map | To configure additional properties when using a custom scheduler or any of the Quartz2 Spring based scheduler.
-| startScheduler | scheduler | true | boolean | Whether the scheduler should be auto started.
-| timeUnit | scheduler | MILLISECONDS | TimeUnit | Time unit for initialDelay and delay options.
-| useFixedDelay | scheduler | true | boolean | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.
-| proxyHost | proxy |  | String | To define a proxy host when instantiating the SQS client
-| proxyPort | proxy |  | Integer | To define a proxy port when instantiating the SQS client
-| maximumMessageSize | queue |  | Integer | The maximumMessageSize (in bytes) an SQS message can contain for this queue.
-| messageRetentionPeriod | queue |  | Integer | The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue.
-| policy | queue |  | String | The policy for this queue
-| receiveMessageWaitTimeSeconds | queue |  | Integer | If you do not specify WaitTimeSeconds in the request the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait.
-| redrivePolicy | queue |  | String | Specify the policy that send message to DeadLetter queue. See detail at Amazon docs.
-|=======================================================================
-{% endraw %}
-// endpoint options: END
-
-
-
-
-
-
-
-Required SQS component options
-
-You have to provide the amazonSQSClient in the
-link:registry.html[Registry] or your accessKey and secretKey to access
-the http://aws.amazon.com/sqs[Amazon's SQS].
-
-[[AWS-SQS-BatchConsumer]]
-Batch Consumer
-^^^^^^^^^^^^^^
-
-This component implements the link:batch-consumer.html[Batch Consumer].
-
-This allows you for instance to know how many messages exists in this
-batch and for instance let the link:aggregator.html[Aggregator]
-aggregate this number of messages.
-
-[[AWS-SQS-Usage]]
-Usage
-^^^^^
-
-[[AWS-SQS-MessageheaderssetbytheSQSproducer]]
-Message headers set by the SQS producer
-+++++++++++++++++++++++++++++++++++++++
-
-[width="100%",cols="10%,10%,80%",options="header",]
-|=======================================================================
-|Header |Type |Description
-
-|`CamelAwsSqsMD5OfBody` |`String` |The MD5 checksum of the Amazon SQS message.
-
-|`CamelAwsSqsMessageId` |`String` |The Amazon SQS message ID.
-
-|`CamelAwsSqsDelaySeconds` |`Integer` |Since *Camel 2.11*, the delay seconds that the Amazon SQS message can be
-see by others.
-|=======================================================================
-
-[[AWS-SQS-MessageheaderssetbytheSQSconsumer]]
-Message headers set by the SQS consumer
-+++++++++++++++++++++++++++++++++++++++
-
-[width="100%",cols="10%,10%,80%",options="header",]
-|=======================================================================
-|Header |Type |Description
-
-|`CamelAwsSqsMD5OfBody` |`String` |The MD5 checksum of the Amazon SQS message.
-
-|`CamelAwsSqsMessageId` |`String` |The Amazon SQS message ID. 
-
-|`CamelAwsSqsReceiptHandle` |`String` |The Amazon SQS message receipt handle.
-
-|`CamelAwsSqsAttributes` |`Map<String, String>` |The Amazon SQS message attributes.
-|=======================================================================
-
-[[AWS-SQS-AdvancedAmazonSQSconfiguration]]
-Advanced AmazonSQS configuration
-++++++++++++++++++++++++++++++++
-
-If your Camel Application is running behind a firewall or if you need to
-have more control over the AmazonSQS instance configuration, you can
-create your own instance:
-
-[source,java]
---------------------------------------------------------------------------------------
-AWSCredentials awsCredentials = new BasicAWSCredentials("myAccessKey", "mySecretKey");
-
-ClientConfiguration clientConfiguration = new ClientConfiguration();
-clientConfiguration.setProxyHost("http://myProxyHost");
-clientConfiguration.setProxyPort(8080);
-
-AmazonSQS client = new AmazonSQSClient(awsCredentials, clientConfiguration);
-
-registry.bind("client", client);
---------------------------------------------------------------------------------------
-
-and refer to it in your Camel aws-sqs component configuration:
-
-[source,java]
----------------------------------------------------------------------------------
-from("aws-sqs://MyQueue?amazonSQSClient=#client&delay=5000&maxMessagesPerPoll=5")
-.to("mock:result");
----------------------------------------------------------------------------------
-
-[[AWS-SQS-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
-
-Maven users will need to add the following dependency to their pom.xml.
-
-*pom.xml*
-
-[source,xml]
----------------------------------------
-<dependency>
-    <groupId>org.apache.camel</groupId>
-    <artifactId>camel-aws</artifactId>
-    <version>${camel-version}</version>
-</dependency>
----------------------------------------
-
-where `${camel-version`} must be replaced by the actual version of Camel
-(2.6 or higher).
-
-[[AWS-SQS-JMS-styleSelectors]]
-JMS-style Selectors
-^^^^^^^^^^^^^^^^^^^
-
-SQS does not allow selectors, but you can effectively achieve this by
-using the link:message-filter.html[Camel Filter EIP] and setting an
-appropriate `visibilityTimeout`. When SQS dispatches a message, it will
-wait up to the visibility timeout before it will try 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:
-
-[source,java]
-------------------------------------------------------------------------------------------------------
-from("aws-sqs://MyQueue?amazonSQSClient=#client&defaultVisibilityTimeout=5000&deleteIfFiltered=false")
-.filter("${header.login} == true")
-.to("mock:result");
-------------------------------------------------------------------------------------------------------
-
-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 miliseconds, the message will become visible to other
-consumers.
-
-[[AWS-SQS-SeeAlso]]
-See Also
-^^^^^^^^
-
-* link:configuring-camel.html[Configuring Camel]
-* link:component.html[Component]
-* link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
-* link:aws.html[AWS Component]
-

http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-aws/src/main/docs/aws-swf-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-swf-component.adoc b/components/camel-aws/src/main/docs/aws-swf-component.adoc
new file mode 100644
index 0000000..25ee304
--- /dev/null
+++ b/components/camel-aws/src/main/docs/aws-swf-component.adoc
@@ -0,0 +1,245 @@
+[[AWS-SWF-SWFComponent]]
+SWF Component
+~~~~~~~~~~~~~
+
+*Available as of Camel 2.13*
+
+The Simple Workflow component supports managing workflows from
+http://aws.amazon.com/swf/[Amazon's Simple Workflow] service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Simple Workflow. More information are available
+at http://aws.amazon.com/swf/[Amazon Simple Workflow].
+
+[[AWS-SWF-URIFormat]]
+URI Format
+^^^^^^^^^^
+
+[source,java]
+---------------------------------------
+aws-swf://<workflow|activity>[?options]
+---------------------------------------
+
+You can append query options to the URI in the following format,
+?options=value&option2=value&...
+
+[[AWS-SWF-URIOptions]]
+URI Options
+^^^^^^^^^^^
+
+
+// component options: START
+The AWS Simple Workflow component has no options.
+// component options: END
+
+
+
+
+// endpoint options: START
+The AWS Simple Workflow component supports 30 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| type | common |  | String | *Required* Activity or workflow
+| accessKey | common |  | String | Amazon AWS Access Key.
+| amazonSWClient | common |  | AmazonSimpleWorkflowClient | To use the given AmazonSimpleWorkflowClient as client
+| dataConverter | common |  | DataConverter | An instance of com.amazonaws.services.simpleworkflow.flow.DataConverter to use for serializing/deserializing the data.
+| domainName | common |  | String | The workflow domain to use.
+| eventName | common |  | String | The workflow or activity event name to use.
+| secretKey | common |  | String | Amazon AWS Secret Key.
+| version | common |  | String | The workflow or activity event version to use.
+| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| exceptionHandler | consumer (advanced) |  | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| clientConfigurationParameters | advanced |  | Map | To configure the ClientConfiguration using the key/values from the Map.
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
+| startWorkflowOptionsParameters | advanced |  | Map | To configure the StartWorkflowOptions using the key/values from the Map.
+| sWClientParameters | advanced |  | Map | To configure the AmazonSimpleWorkflowClient using the key/values from the Map.
+| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
+| activityList | activity |  | String | The list name to consume activities from.
+| activitySchedulingOptions | activity |  | ActivitySchedulingOptions | Activity scheduling options
+| activityThreadPoolSize | activity | 100 | int | Maximum number of threads in work pool for activity.
+| activityTypeExecutionOptions | activity |  | ActivityTypeExecutionOptions | Activity execution options
+| activityTypeRegistrationOptions | activity |  | ActivityTypeRegistrationOptions | Activity registration options
+| childPolicy | workflow |  | String | The policy to use on child workflows when terminating a workflow.
+| executionStartToCloseTimeout | workflow | 3600 | String | Set the execution start to close timeout.
+| operation | workflow | START | String | Workflow operation
+| signalName | workflow |  | String | The name of the signal to send to the workflow.
+| stateResultType | workflow |  | String | The type of the result when a workflow state is queried.
+| taskStartToCloseTimeout | workflow | 600 | String | Set the task start to close timeout.
+| terminationDetails | workflow |  | String | Details for terminating a workflow.
+| terminationReason | workflow |  | String | The reason for terminating a workflow.
+| workflowList | workflow |  | String | The list name to consume workflows from.
+| workflowTypeRegistrationOptions | workflow |  | WorkflowTypeRegistrationOptions | Workflow registration options
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+
+Required SWF component options
+
+You have to provide the�amazonSWClient in the
+link:registry.html[Registry] or your accessKey and secretKey to access
+the http://aws.amazon.com/swf[Amazon's Simple Workflow Service].
+
+[[AWS-SWF-Usage]]
+Usage
+^^^^^
+
+[[AWS-SWF-MessageheadersevaluatedbytheSWFWorkflowProducer]]
+Message headers evaluated by the SWF Workflow Producer
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+A workflow producer allows interacting with a workflow. It can start a
+new workflow execution, query its state, send signals to a running
+workflow, or terminate and cancel it.
+
+[width="100%",cols="10%,10%,80%",options="header",]
+|=======================================================================
+|Header |Type |Description
+
+|`CamelSWFOperation` |`String` |The operation to perform on the workflow. Supported operations are:  +
+ SIGNAL, CANCEL, TERMINATE, GET_STATE, START, DESCRIBE, GET_HISTORY.
+
+|`CamelSWFWorkflowId` |`String` |A workflow ID to use.
+
+|`CamelAwsDdbKeyCamelSWFRunId` |`String` |A worfklow run ID to use.
+
+|`CamelSWFStateResultType` |`String` |The type of the result when a workflow state is queried.
+
+|`CamelSWFEventName` |`String` |The workflow or activity event name to use.
+
+|`CamelSWFVersion` |`String` |The workflow or activity event version to use.
+
+|`CamelSWFReason` |`String` |The reason for terminating a workflow.
+
+|`CamelSWFDetails` |`String` |Details for terminating a workflow.
+
+|`CamelSWFChildPolicy` |`String` |The policy to use on child workflows when terminating a workflow.
+|=======================================================================
+
+[[AWS-SWF-MessageheaderssetbytheSWFWorkflowProducer]]
+Message headers set by the SWF Workflow Producer
+++++++++++++++++++++++++++++++++++++++++++++++++
+
+[width="100%",cols="10%,10%,80%",options="header",]
+|=======================================================================
+|Header |Type |Description
+
+|`CamelSWFWorkflowId` |`String` |The worfklow ID used or newly generated.
+
+|`CamelAwsDdbKeyCamelSWFRunId` |`String` |The worfklow run ID used or generated.
+|=======================================================================
+
+[[AWS-SWF-MessageheaderssetbytheSWFWorkflowConsumer]]
+Message headers set by the SWF Workflow Consumer
+++++++++++++++++++++++++++++++++++++++++++++++++
+
+A workflow consumer represents the workflow logic. When it is started,
+it will start polling workflow decision tasks and process them. In
+addition to processing decision tasks, a workflow consumer route, will
+also receive signals (send from a workflow producer) or state queries.
+The primary purpose of a workflow consumer is to schedule activity tasks
+for execution using activity producers. Actually activity tasks can be
+scheduled only from a thread started by a workflow consumer.
+
+[width="100%",cols="10%,10%,80%",options="header",]
+|=======================================================================
+|Header |Type |Description
+
+|`CamelSWFAction` |`String` |Indicates what type is the current event: CamelSWFActionExecute,
+CamelSWFSignalReceivedAction or CamelSWFGetStateAction.
+
+|`CamelSWFWorkflowReplaying` |`boolean` |Indicates whether the current decision task is a replay or not.
+
+|`CamelSWFWorkflowStartTime` |`long` |The time of the start event for this decision task.
+|=======================================================================
+
+[[AWS-SWF-MessageheaderssetbytheSWFActivityProducer]]
+Message headers set by the SWF Activity Producer
+++++++++++++++++++++++++++++++++++++++++++++++++
+
+An activity producer allows scheduling activity tasks. An activity
+producer can be used only from a thread started by a workflow consumer
+ie, it can process synchronous exchanges started by a workflow consumer.
+
+[width="100%",cols="10%,10%,80%",options="header",]
+|=======================================================================
+|Header |Type |Description
+
+|`CamelSWFEventName` |`String` |The activity name to schedule.
+
+|`CamelSWFVersion` |`String` |The activity version to schedule.
+|=======================================================================
+
+[[AWS-SWF-MessageheaderssetbytheSWFActivityConsumer]]
+Message headers set by the SWF Activity Consumer
+++++++++++++++++++++++++++++++++++++++++++++++++
+
+[width="100%",cols="10%,10%,80%",options="header",]
+|=======================================================================
+|Header |Type |Description
+
+|`CamelSWFTaskToken` |`String` |The task token that is required to report task completion for manually
+completed tasks.
+|=======================================================================
+
+[[AWS-SWF-AdvancedamazonSWClientconfiguration]]
+Advanced amazonSWClient configuration
++++++++++++++++++++++++++++++++++++++
+
+If you need more control over the�AmazonSimpleWorkflowClient instance
+configuration you can create your own instance and refer to it from the
+URI:
+
+The `#client` refers to a�AmazonSimpleWorkflowClient in the
+link:registry.html[Registry].
+
+For example if your Camel Application is running behind a firewall:
+
+[source,java]
+--------------------------------------------------------------------------------------------------------
+AWSCredentials awsCredentials = new BasicAWSCredentials("myAccessKey", "mySecretKey");
+ClientConfiguration clientConfiguration = new ClientConfiguration();
+clientConfiguration.setProxyHost("http://myProxyHost");
+clientConfiguration.setProxyPort(8080);
+
+AmazonSimpleWorkflowClient client = new AmazonSimpleWorkflowClient(awsCredentials, clientConfiguration);
+
+registry.bind("client", client);
+--------------------------------------------------------------------------------------------------------
+
+[[AWS-SWF-Dependencies]]
+Dependencies
+^^^^^^^^^^^^
+
+Maven users will need to add the following dependency to their pom.xml.
+
+*pom.xml*
+
+[source,xml]
+---------------------------------------
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-aws</artifactId>
+    <version>${camel-version}</version>
+</dependency>
+---------------------------------------
+
+where `${camel-version`} must be replaced by the actual version of Camel
+(2.13 or higher).
+
+[[AWS-SWF-SeeAlso]]
+See Also
+^^^^^^^^
+
+* link:configuring-camel.html[Configuring Camel]
+* link:component.html[Component]
+* link:endpoint.html[Endpoint]
+* link:getting-started.html[Getting Started]
+
+link:aws.html[AWS Component]

http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-aws/src/main/docs/aws-swf.adoc
----------------------------------------------------------------------
diff --git a/components/camel-aws/src/main/docs/aws-swf.adoc b/components/camel-aws/src/main/docs/aws-swf.adoc
deleted file mode 100644
index 25ee304..0000000
--- a/components/camel-aws/src/main/docs/aws-swf.adoc
+++ /dev/null
@@ -1,245 +0,0 @@
-[[AWS-SWF-SWFComponent]]
-SWF Component
-~~~~~~~~~~~~~
-
-*Available as of Camel 2.13*
-
-The Simple Workflow component supports managing workflows from
-http://aws.amazon.com/swf/[Amazon's Simple Workflow] service.
-
-Prerequisites
-
-You must have a valid Amazon Web Services developer account, and be
-signed up to use Amazon Simple Workflow. More information are available
-at http://aws.amazon.com/swf/[Amazon Simple Workflow].
-
-[[AWS-SWF-URIFormat]]
-URI Format
-^^^^^^^^^^
-
-[source,java]
----------------------------------------
-aws-swf://<workflow|activity>[?options]
----------------------------------------
-
-You can append query options to the URI in the following format,
-?options=value&option2=value&...
-
-[[AWS-SWF-URIOptions]]
-URI Options
-^^^^^^^^^^^
-
-
-// component options: START
-The AWS Simple Workflow component has no options.
-// component options: END
-
-
-
-
-// endpoint options: START
-The AWS Simple Workflow component supports 30 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| type | common |  | String | *Required* Activity or workflow
-| accessKey | common |  | String | Amazon AWS Access Key.
-| amazonSWClient | common |  | AmazonSimpleWorkflowClient | To use the given AmazonSimpleWorkflowClient as client
-| dataConverter | common |  | DataConverter | An instance of com.amazonaws.services.simpleworkflow.flow.DataConverter to use for serializing/deserializing the data.
-| domainName | common |  | String | The workflow domain to use.
-| eventName | common |  | String | The workflow or activity event name to use.
-| secretKey | common |  | String | Amazon AWS Secret Key.
-| version | common |  | String | The workflow or activity event version to use.
-| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| exceptionHandler | consumer (advanced) |  | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| clientConfigurationParameters | advanced |  | Map | To configure the ClientConfiguration using the key/values from the Map.
-| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
-| startWorkflowOptionsParameters | advanced |  | Map | To configure the StartWorkflowOptions using the key/values from the Map.
-| sWClientParameters | advanced |  | Map | To configure the AmazonSimpleWorkflowClient using the key/values from the Map.
-| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
-| activityList | activity |  | String | The list name to consume activities from.
-| activitySchedulingOptions | activity |  | ActivitySchedulingOptions | Activity scheduling options
-| activityThreadPoolSize | activity | 100 | int | Maximum number of threads in work pool for activity.
-| activityTypeExecutionOptions | activity |  | ActivityTypeExecutionOptions | Activity execution options
-| activityTypeRegistrationOptions | activity |  | ActivityTypeRegistrationOptions | Activity registration options
-| childPolicy | workflow |  | String | The policy to use on child workflows when terminating a workflow.
-| executionStartToCloseTimeout | workflow | 3600 | String | Set the execution start to close timeout.
-| operation | workflow | START | String | Workflow operation
-| signalName | workflow |  | String | The name of the signal to send to the workflow.
-| stateResultType | workflow |  | String | The type of the result when a workflow state is queried.
-| taskStartToCloseTimeout | workflow | 600 | String | Set the task start to close timeout.
-| terminationDetails | workflow |  | String | Details for terminating a workflow.
-| terminationReason | workflow |  | String | The reason for terminating a workflow.
-| workflowList | workflow |  | String | The list name to consume workflows from.
-| workflowTypeRegistrationOptions | workflow |  | WorkflowTypeRegistrationOptions | Workflow registration options
-|=======================================================================
-{% endraw %}
-// endpoint options: END
-
-
-
-Required SWF component options
-
-You have to provide the�amazonSWClient in the
-link:registry.html[Registry] or your accessKey and secretKey to access
-the http://aws.amazon.com/swf[Amazon's Simple Workflow Service].
-
-[[AWS-SWF-Usage]]
-Usage
-^^^^^
-
-[[AWS-SWF-MessageheadersevaluatedbytheSWFWorkflowProducer]]
-Message headers evaluated by the SWF Workflow Producer
-++++++++++++++++++++++++++++++++++++++++++++++++++++++
-
-A workflow producer allows interacting with a workflow. It can start a
-new workflow execution, query its state, send signals to a running
-workflow, or terminate and cancel it.
-
-[width="100%",cols="10%,10%,80%",options="header",]
-|=======================================================================
-|Header |Type |Description
-
-|`CamelSWFOperation` |`String` |The operation to perform on the workflow. Supported operations are:  +
- SIGNAL, CANCEL, TERMINATE, GET_STATE, START, DESCRIBE, GET_HISTORY.
-
-|`CamelSWFWorkflowId` |`String` |A workflow ID to use.
-
-|`CamelAwsDdbKeyCamelSWFRunId` |`String` |A worfklow run ID to use.
-
-|`CamelSWFStateResultType` |`String` |The type of the result when a workflow state is queried.
-
-|`CamelSWFEventName` |`String` |The workflow or activity event name to use.
-
-|`CamelSWFVersion` |`String` |The workflow or activity event version to use.
-
-|`CamelSWFReason` |`String` |The reason for terminating a workflow.
-
-|`CamelSWFDetails` |`String` |Details for terminating a workflow.
-
-|`CamelSWFChildPolicy` |`String` |The policy to use on child workflows when terminating a workflow.
-|=======================================================================
-
-[[AWS-SWF-MessageheaderssetbytheSWFWorkflowProducer]]
-Message headers set by the SWF Workflow Producer
-++++++++++++++++++++++++++++++++++++++++++++++++
-
-[width="100%",cols="10%,10%,80%",options="header",]
-|=======================================================================
-|Header |Type |Description
-
-|`CamelSWFWorkflowId` |`String` |The worfklow ID used or newly generated.
-
-|`CamelAwsDdbKeyCamelSWFRunId` |`String` |The worfklow run ID used or generated.
-|=======================================================================
-
-[[AWS-SWF-MessageheaderssetbytheSWFWorkflowConsumer]]
-Message headers set by the SWF Workflow Consumer
-++++++++++++++++++++++++++++++++++++++++++++++++
-
-A workflow consumer represents the workflow logic. When it is started,
-it will start polling workflow decision tasks and process them. In
-addition to processing decision tasks, a workflow consumer route, will
-also receive signals (send from a workflow producer) or state queries.
-The primary purpose of a workflow consumer is to schedule activity tasks
-for execution using activity producers. Actually activity tasks can be
-scheduled only from a thread started by a workflow consumer.
-
-[width="100%",cols="10%,10%,80%",options="header",]
-|=======================================================================
-|Header |Type |Description
-
-|`CamelSWFAction` |`String` |Indicates what type is the current event: CamelSWFActionExecute,
-CamelSWFSignalReceivedAction or CamelSWFGetStateAction.
-
-|`CamelSWFWorkflowReplaying` |`boolean` |Indicates whether the current decision task is a replay or not.
-
-|`CamelSWFWorkflowStartTime` |`long` |The time of the start event for this decision task.
-|=======================================================================
-
-[[AWS-SWF-MessageheaderssetbytheSWFActivityProducer]]
-Message headers set by the SWF Activity Producer
-++++++++++++++++++++++++++++++++++++++++++++++++
-
-An activity producer allows scheduling activity tasks. An activity
-producer can be used only from a thread started by a workflow consumer
-ie, it can process synchronous exchanges started by a workflow consumer.
-
-[width="100%",cols="10%,10%,80%",options="header",]
-|=======================================================================
-|Header |Type |Description
-
-|`CamelSWFEventName` |`String` |The activity name to schedule.
-
-|`CamelSWFVersion` |`String` |The activity version to schedule.
-|=======================================================================
-
-[[AWS-SWF-MessageheaderssetbytheSWFActivityConsumer]]
-Message headers set by the SWF Activity Consumer
-++++++++++++++++++++++++++++++++++++++++++++++++
-
-[width="100%",cols="10%,10%,80%",options="header",]
-|=======================================================================
-|Header |Type |Description
-
-|`CamelSWFTaskToken` |`String` |The task token that is required to report task completion for manually
-completed tasks.
-|=======================================================================
-
-[[AWS-SWF-AdvancedamazonSWClientconfiguration]]
-Advanced amazonSWClient configuration
-+++++++++++++++++++++++++++++++++++++
-
-If you need more control over the�AmazonSimpleWorkflowClient instance
-configuration you can create your own instance and refer to it from the
-URI:
-
-The `#client` refers to a�AmazonSimpleWorkflowClient in the
-link:registry.html[Registry].
-
-For example if your Camel Application is running behind a firewall:
-
-[source,java]
---------------------------------------------------------------------------------------------------------
-AWSCredentials awsCredentials = new BasicAWSCredentials("myAccessKey", "mySecretKey");
-ClientConfiguration clientConfiguration = new ClientConfiguration();
-clientConfiguration.setProxyHost("http://myProxyHost");
-clientConfiguration.setProxyPort(8080);
-
-AmazonSimpleWorkflowClient client = new AmazonSimpleWorkflowClient(awsCredentials, clientConfiguration);
-
-registry.bind("client", client);
---------------------------------------------------------------------------------------------------------
-
-[[AWS-SWF-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
-
-Maven users will need to add the following dependency to their pom.xml.
-
-*pom.xml*
-
-[source,xml]
----------------------------------------
-<dependency>
-    <groupId>org.apache.camel</groupId>
-    <artifactId>camel-aws</artifactId>
-    <version>${camel-version}</version>
-</dependency>
----------------------------------------
-
-where `${camel-version`} must be replaced by the actual version of Camel
-(2.13 or higher).
-
-[[AWS-SWF-SeeAlso]]
-See Also
-^^^^^^^^
-
-* link:configuring-camel.html[Configuring Camel]
-* link:component.html[Component]
-* link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
-link:aws.html[AWS Component]

http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc b/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc
new file mode 100644
index 0000000..9ed8142
--- /dev/null
+++ b/components/camel-bean-validator/src/main/docs/bean-validator-component.adoc
@@ -0,0 +1,258 @@
+[[BeanValidator-BeanValidatorComponent]]
+Bean Validator Component
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+*Available as of Camel 2.3*
+
+The Validator component performs bean validation of the message body
+using the Java Bean Validation API
+(http://jcp.org/en/jsr/detail?id=303[JSR 303]). Camel uses the reference
+implementation, which is
+http://docs.jboss.org/hibernate/validator/4.3/reference/en-US/html_single/[Hibernate
+Validator].
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+[source,xml]
+------------------------------------------------------------
+<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>
+------------------------------------------------------------
+
+[[BeanValidator-URIformat]]
+URI format
+^^^^^^^^^^
+
+[source,java]
+------------------------------
+bean-validator:label[?options]
+------------------------------
+
+or
+
+[source,java]
+--------------------------------
+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&...
+
+[[BeanValidator-URIOptions]]
+URI Options
+^^^^^^^^^^^
+
+
+// component options: START
+The Bean Validator component has no options.
+// component options: END
+
+
+
+// endpoint options: START
+The Bean Validator component supports 8 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| label | producer |  | String | *Required* Where label is an arbitrary text value describing the endpoint
+| constraintValidatorFactory | producer |  | ConstraintValidatorFactory | To use a custom ConstraintValidatorFactory
+| group | producer | javax.validation.groups.Default | String | To use a custom validation group
+| messageInterpolator | producer |  | MessageInterpolator | To use a custom MessageInterpolator
+| traversableResolver | producer |  | TraversableResolver | To use a custom TraversableResolver
+| validationProviderResolver | producer |  | ValidationProviderResolver | To use a a custom ValidationProviderResolver
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
+| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+[[BeanValidator-OSGideployment]]
+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. Keep in mind that you can
+use `HibernateValidationProviderResolver` starting from the Camel
+2.13.0.
+
+*Using HibernateValidationProviderResolver*
+
+[source,java]
+--------------------------------------------------------------------------------------------------------------------------------
+from("direct:test").
+  to("bean-validator://ValidationProviderResolverTest?validationProviderResolver=#myValidationProviderResolver");
+
+...
+
+<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.
+
+[[BeanValidator-Example]]
+Example
+^^^^^^^
+
+Assumed we have a java bean with the following annotations
+
+*Car.java*
+
+[source,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*
+
+[source,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 `javax.validation.groups.Default`).
+
+[source,java]
+-------------------------
+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
+
+[source,java]
+----------------------------------------------
+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*
+
+[source,java]
+-----------------------------------------------------
+@GroupSequence({Default.class, OptionalChecks.class})
+public interface AllChecks {
+}
+-----------------------------------------------------
+
+and then your route definition should looks like this
+
+[source,java]
+-----------------------------------------
+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
+
+[source,java]
+------------------------------------------------------------------------------------------------------
+<bean id="myMessageInterpolator" class="my.ConstraintValidatorFactory" />
+<bean id="myTraversableResolver" class="my.TraversableResolver" />
+<bean id="myConstraintValidatorFactory" class="my.ConstraintValidatorFactory" />
+
+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 file
+`META-INF/validation.xml` which could looks like this
+
+*validation.xml*
+
+[source,java]
+------------------------------------------------------------------------------------------------------------------------------
+<?xml version="1.0" encoding="UTF-8"?>
+<validation-config
+    xmlns="http://jboss.org/xml/ns/javax/validation/configuration"
+    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration">
+    <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>
+------------------------------------------------------------------------------------------------------------------------------
+
+and the `constraints-car.xml` file
+
+*constraints-car.xml*
+
+[source,java]
+----------------------------------------------------------------------------------------------------
+<?xml version="1.0" encoding="UTF-8"?>
+<constraint-mappings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/mapping validation-mapping-1.0.xsd"
+    xmlns="http://jboss.org/xml/ns/javax/validation/mapping">
+    <default-package>org.apache.camel.component.bean.validator</default-package>
+    
+    <bean class="CarWithoutAnnotations" ignore-annotations="true">
+        <field name="manufacturer">
+            <constraint annotation="javax.validation.constraints.NotNull" />
+        </field>
+        
+        <field name="licensePlate">
+            <constraint annotation="javax.validation.constraints.NotNull" />
+            
+            <constraint annotation="javax.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>
+----------------------------------------------------------------------------------------------------
+
+[[BeanValidator-SeeAlso]]
+See Also
+^^^^^^^^
+
+* link:configuring-camel.html[Configuring Camel]
+* link:component.html[Component]
+* link:endpoint.html[Endpoint]
+* link:getting-started.html[Getting Started]
+

http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-bean-validator/src/main/docs/bean-validator.adoc
----------------------------------------------------------------------
diff --git a/components/camel-bean-validator/src/main/docs/bean-validator.adoc b/components/camel-bean-validator/src/main/docs/bean-validator.adoc
deleted file mode 100644
index 9ed8142..0000000
--- a/components/camel-bean-validator/src/main/docs/bean-validator.adoc
+++ /dev/null
@@ -1,258 +0,0 @@
-[[BeanValidator-BeanValidatorComponent]]
-Bean Validator Component
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-*Available as of Camel 2.3*
-
-The Validator component performs bean validation of the message body
-using the Java Bean Validation API
-(http://jcp.org/en/jsr/detail?id=303[JSR 303]). Camel uses the reference
-implementation, which is
-http://docs.jboss.org/hibernate/validator/4.3/reference/en-US/html_single/[Hibernate
-Validator].
-
-Maven users will need to add the following dependency to their `pom.xml`
-for this component:
-
-[source,xml]
-------------------------------------------------------------
-<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>
-------------------------------------------------------------
-
-[[BeanValidator-URIformat]]
-URI format
-^^^^^^^^^^
-
-[source,java]
-------------------------------
-bean-validator:label[?options]
-------------------------------
-
-or
-
-[source,java]
---------------------------------
-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&...
-
-[[BeanValidator-URIOptions]]
-URI Options
-^^^^^^^^^^^
-
-
-// component options: START
-The Bean Validator component has no options.
-// component options: END
-
-
-
-// endpoint options: START
-The Bean Validator component supports 8 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| label | producer |  | String | *Required* Where label is an arbitrary text value describing the endpoint
-| constraintValidatorFactory | producer |  | ConstraintValidatorFactory | To use a custom ConstraintValidatorFactory
-| group | producer | javax.validation.groups.Default | String | To use a custom validation group
-| messageInterpolator | producer |  | MessageInterpolator | To use a custom MessageInterpolator
-| traversableResolver | producer |  | TraversableResolver | To use a custom TraversableResolver
-| validationProviderResolver | producer |  | ValidationProviderResolver | To use a a custom ValidationProviderResolver
-| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
-| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
-|=======================================================================
-{% endraw %}
-// endpoint options: END
-
-
-[[BeanValidator-OSGideployment]]
-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. Keep in mind that you can
-use `HibernateValidationProviderResolver` starting from the Camel
-2.13.0.
-
-*Using HibernateValidationProviderResolver*
-
-[source,java]
---------------------------------------------------------------------------------------------------------------------------------
-from("direct:test").
-  to("bean-validator://ValidationProviderResolverTest?validationProviderResolver=#myValidationProviderResolver");
-
-...
-
-<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.
-
-[[BeanValidator-Example]]
-Example
-^^^^^^^
-
-Assumed we have a java bean with the following annotations
-
-*Car.java*
-
-[source,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*
-
-[source,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 `javax.validation.groups.Default`).
-
-[source,java]
--------------------------
-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
-
-[source,java]
-----------------------------------------------
-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*
-
-[source,java]
------------------------------------------------------
-@GroupSequence({Default.class, OptionalChecks.class})
-public interface AllChecks {
-}
------------------------------------------------------
-
-and then your route definition should looks like this
-
-[source,java]
------------------------------------------
-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
-
-[source,java]
-------------------------------------------------------------------------------------------------------
-<bean id="myMessageInterpolator" class="my.ConstraintValidatorFactory" />
-<bean id="myTraversableResolver" class="my.TraversableResolver" />
-<bean id="myConstraintValidatorFactory" class="my.ConstraintValidatorFactory" />
-
-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 file
-`META-INF/validation.xml` which could looks like this
-
-*validation.xml*
-
-[source,java]
-------------------------------------------------------------------------------------------------------------------------------
-<?xml version="1.0" encoding="UTF-8"?>
-<validation-config
-    xmlns="http://jboss.org/xml/ns/javax/validation/configuration"
-    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration">
-    <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>
-------------------------------------------------------------------------------------------------------------------------------
-
-and the `constraints-car.xml` file
-
-*constraints-car.xml*
-
-[source,java]
-----------------------------------------------------------------------------------------------------
-<?xml version="1.0" encoding="UTF-8"?>
-<constraint-mappings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/mapping validation-mapping-1.0.xsd"
-    xmlns="http://jboss.org/xml/ns/javax/validation/mapping">
-    <default-package>org.apache.camel.component.bean.validator</default-package>
-    
-    <bean class="CarWithoutAnnotations" ignore-annotations="true">
-        <field name="manufacturer">
-            <constraint annotation="javax.validation.constraints.NotNull" />
-        </field>
-        
-        <field name="licensePlate">
-            <constraint annotation="javax.validation.constraints.NotNull" />
-            
-            <constraint annotation="javax.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>
-----------------------------------------------------------------------------------------------------
-
-[[BeanValidator-SeeAlso]]
-See Also
-^^^^^^^^
-
-* link:configuring-camel.html[Configuring Camel]
-* link:component.html[Component]
-* link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-

http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
new file mode 100644
index 0000000..01b097d
--- /dev/null
+++ b/components/camel-beanstalk/src/main/docs/beanstalk-component.adoc
@@ -0,0 +1,231 @@
+[[Beanstalk-Beanstalkcomponent]]
+Beanstalk component
+~~~~~~~~~~~~~~~~~~~
+
+*Available in Camel 2.15*
+
+camel-beanstalk project provides a Camel component for job retrieval and
+post-processing of Beanstalk jobs.
+
+You can find the detailed explanation of Beanstalk job lifecycle
+at�http://github.com/kr/beanstalkd/blob/v1.3/doc/protocol.txt[Beanstalk
+protocol].
+
+[[Beanstalk-Dependencies]]
+Dependencies
+^^^^^^^^^^^^
+
+Maven users need to add the following dependency to their `pom.xml`
+
+[source,xml]
+------------------------------------------
+<dependency>
+  <groupId>org.apache.camel</groupId>
+  <artifactId>camel-beanstalk</artifactId>
+  <version>${camel-version}</version>
+</dependency>
+------------------------------------------
+
+where `${camel-version`} must be replaced by the actual version of Camel
+(2.15.0 or higher).
+
+[[Beanstalk-URIformat]]
+URI format
+^^^^^^^^^^
+
+[source,xml]
+------------------------------------------
+beanstalk://[host[:port]][/tube][?options]
+------------------------------------------
+
+You may omit either�`port`�or both�`host`�and�`port`: for the Beanstalk
+defaults to be used (\u201clocalhost\u201d and 11300). If you omit�`tube`,
+Beanstalk component will use the tube with name \u201cdefault\u201d.
+
+When listening, you may probably want to watch for jobs from several
+tubes. Just separate them with plus sign, e.g.
+
+[source,java]
+---------------------------------------
+beanstalk://localhost:11300/tube1+tube2
+---------------------------------------
+
+Tube name will be URL decoded, so if your tube names include special
+characters like + or ?, you need to URL-encode them appropriately, or
+use the RAW syntax, see link:how-do-i-configure-endpoints.html[more
+details here].
+
+By the way, you cannot specify several tubes when you are writing jobs
+into Beanstalk.
+
+[[Beanstalk-options]]
+Beanstalk options
+^^^^^^^^^^^^^^^^^
+
+
+// component options: START
+The Beanstalk component supports 1 options which are listed below.
+
+
+
+{% raw %}
+[width="100%",cols="2s,1m,8",options="header"]
+|=======================================================================
+| Name | Java Type | Description
+| connectionSettingsFactory | ConnectionSettingsFactory | Custom ConnectionSettingsFactory. Specify which ConnectionSettingsFactory to use to make connections to Beanstalkd. Especially useful for unit testing without beanstalkd daemon (you can mock ConnectionSettings)
+|=======================================================================
+{% endraw %}
+// component options: END
+
+
+
+// endpoint options: START
+The Beanstalk component supports 27 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| connectionSettings | common |  | String | Connection settings host:port/tube
+| command | common |  | BeanstalkCommand | put means to put the job into Beanstalk. Job body is specified in the Camel message body. Job ID will be returned in beanstalk.jobId message header. delete release touch or bury expect Job ID in the message header beanstalk.jobId. Result of the operation is returned in beanstalk.result message header kick expects the number of jobs to kick in the message body and returns the number of jobs actually kicked out in the message header beanstalk.result.
+| jobDelay | common | 0 | int | Job delay in seconds.
+| jobPriority | common | 1000 | long | Job priority. (0 is the highest see Beanstalk protocol)
+| jobTimeToRun | common | 60 | int | Job time to run in seconds. (when 0 the beanstalkd daemon raises it to 1 automatically see Beanstalk protocol)
+| awaitJob | consumer | true | boolean | Whether to wait for job to complete before ack the job from beanstalk
+| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| onFailure | consumer |  | BeanstalkCommand | Command to use when processing failed.
+| sendEmptyMessageWhenIdle | consumer | false | boolean | If the polling consumer did not poll any files you can enable this option to send an empty message (no body) instead.
+| useBlockIO | consumer | true | boolean | Whether to use blockIO.
+| exceptionHandler | consumer (advanced) |  | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| pollStrategy | consumer (advanced) |  | PollingConsumerPollStrategy | 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.
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
+| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
+| backoffErrorThreshold | scheduler |  | int | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.
+| backoffIdleThreshold | scheduler |  | int | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.
+| backoffMultiplier | scheduler |  | int | 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.
+| delay | scheduler | 500 | long | Milliseconds before the next poll. You can also specify time values using units such as 60s (60 seconds) 5m30s (5 minutes and 30 seconds) and 1h (1 hour).
+| greedy | scheduler | false | boolean | If greedy is enabled then the ScheduledPollConsumer will run immediately again if the previous run polled 1 or more messages.
+| initialDelay | scheduler | 1000 | long | Milliseconds before the first poll starts. You can also specify time values using units such as 60s (60 seconds) 5m30s (5 minutes and 30 seconds) and 1h (1 hour).
+| runLoggingLevel | scheduler | TRACE | LoggingLevel | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.
+| scheduledExecutorService | scheduler |  | 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.
+| scheduler | scheduler | none | ScheduledPollConsumerScheduler | To use a cron scheduler from either camel-spring or camel-quartz2 component
+| schedulerProperties | scheduler |  | Map | To configure additional properties when using a custom scheduler or any of the Quartz2 Spring based scheduler.
+| startScheduler | scheduler | true | boolean | Whether the scheduler should be auto started.
+| timeUnit | scheduler | MILLISECONDS | TimeUnit | Time unit for initialDelay and delay options.
+| useFixedDelay | scheduler | true | boolean | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+Producer�behavior�is affected by the�`command`�parameter which tells
+what to do with the job, it can be
+
+The consumer may delete the job immediately after reserving it or wait
+until Camel routes process it. While the first scenario is more like a
+\u201cmessage queue\u201d, the second is similar to \u201cjob queue\u201d. This behavior is
+controlled by�`consumer.awaitJob`�parameter, which equals�`true`�by
+default (following Beanstalkd nature).
+
+When synchronous, the consumer calls�`delete`�on successful job
+completion and calls�`bury`�on failure. You can choose which command to
+execute in the case of failure by
+specifying�`consumer.onFailure`�parameter in the URI. It can take values
+of�`bury`,�`delete`�or�`release`.
+
+There is a boolean parameter�`consumer.useBlockIO`�which corresponds to
+the same parameter in JavaBeanstalkClient library. By default it
+is�`true`.
+
+Be careful when specifying�`release`, as the failed job will immediately
+become available in the same tube and your consumer will try to acquire
+it again. You can�`release`�and specify�_jobDelay_�though.
+
+The beanstalk consumer is a�Scheduled�link:polling-consumer.html[Polling
+Consumer] which means there is more options you can configure, such as
+how frequent the consumer should poll. For more details
+see�link:polling-consumer.html[Polling Consumer].
+
+[[Beanstalk-ConsumerHeaders]]
+Consumer Headers
+^^^^^^^^^^^^^^^^
+
+The consumer stores a number of job headers in the Exchange message:
+
+[width="100%",cols="10%,10%,80%",options="header",]
+|=======================================================================
+|Property |Type |Description
+
+|_beanstalk.jobId_ |long | Job ID
+
+|_beanstalk.tube_ |string |the name of the tube that contains this job
+
+|_beanstalk.state_ |string |\u201cready\u201d or \u201cdelayed\u201d or \u201creserved\u201d or \u201cburied\u201d (must be \u201creserved\u201d)
+
+|_beanstalk.priority_ |long |the priority value set
+
+|_beanstalk.age_ |int |the time in seconds since the put command that created this job
+
+|_beanstalk.time-left_ |int |the number of seconds left until the server puts this job into the ready
+queue
+
+|_beanstalk.timeouts_ |int |the number of times this job has timed out during a reservation
+
+|_beanstalk.releases_ |int |the number of times a client has released this job from a reservation
+
+|_beanstalk.buries_ |int |the number of times this job has been buried
+
+|_beanstalk.kicks_ |int |the number of times this job has been kicked
+|=======================================================================
+
+[[Beanstalk-Examples]]
+Examples
+^^^^^^^^
+
+This Camel component lets you both request the jobs for processing and
+supply them to Beanstalkd daemon. Our simple demo routes may look like
+
+[source,java]
+----------------------------------------------------------------------------------------------
+from("beanstalk:testTube").
+   log("Processing job #${property.beanstalk.jobId} with body ${in.body}").
+   process(new Processor() {
+     @Override
+     public void process(Exchange exchange) {
+       // try to make integer value out of body
+       exchange.getIn().setBody( Integer.valueOf(exchange.getIn().getBody(classOf[String])) );
+     }
+   }).
+   log("Parsed job #${property.beanstalk.jobId} to body ${in.body}");
+----------------------------------------------------------------------------------------------
+
+[source,java]
+---------------------------------------------------------------------
+from("timer:dig?period=30seconds").
+   setBody(constant(10)).log("Kick ${in.body} buried/delayed tasks").
+   to("beanstalk:testTube?command=kick");
+---------------------------------------------------------------------
+
+In the first route we are listening for new jobs in tube \u201ctestTube\u201d.
+When they are arriving, we are trying to parse integer value from the
+message body. If done successful, we log it and this successful exchange
+completion makes Camel component to�_delete_�this job from Beanstalk
+automatically. Contrary, when we cannot parse the job data, the exchange
+failed and the Camel component�_buries_�it by default, so that it can be
+processed later or probably we are going to inspect failed jobs
+manually.
+
+So the second route periodically requests Beanstalk to�_kick_�10 jobs
+out of buried and/or delayed state to the normal queue.
+
+�
+
+[[Beanstalk-SeeAlso]]
+See Also
+^^^^^^^^
+
+* link:configuring-camel.html[Configuring Camel]
+* link:component.html[Component]
+* link:endpoint.html[Endpoint]
+* link:getting-started.html[Getting Started]
+