[camel] 02/02: Regen and sync properties

[acosentino]

This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git

commit ebf15c593b9532725b15137ca7301f572423cdd9
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Tue Aug 4 18:21:39 2020 +0200

    Regen and sync properties
---
 camel-dependencies/pom.xml                           |  2 +-
 .../camel/catalog/docs/aws2-sqs-component.adoc       | 20 ++++++++++++++++----
 2 files changed, 17 insertions(+), 5 deletions(-)

diff --git a/camel-dependencies/pom.xml b/camel-dependencies/pom.xml
index 777c2ee..31b007c 100644
--- a/camel-dependencies/pom.xml
+++ b/camel-dependencies/pom.xml
@@ -352,7 +352,7 @@
     <jolokia-version>1.6.2</jolokia-version>
     <jolt-version>0.1.1</jolt-version>
     <jool-version>0.9.12</jool-version>
-    <jooq-version>3.13.3</jooq-version>
+    <jooq-version>3.13.4</jooq-version>
     <jose4j-version>0.6.4</jose4j-version>
     <jota-version>1.0.0-beta7</jota-version>
     <jsch-version>0.1.55</jsch-version>
diff --git 
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws2-sqs-component.adoc
 
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws2-sqs-component.adoc
index 19b69b7..839b8e2 100644
--- 
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws2-sqs-component.adoc
+++ 
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws2-sqs-component.adoc
@@ -330,6 +330,16 @@ consumers.
 - deleteMessage
 - listQueues
 
+== Send Message
+
+You can set a `SendMessageBatchRequest` or an `Iterable`
+
+------------------------------------------------------------------------------------------------------
+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`
@@ -348,7 +358,7 @@ from("direct:start")
           exchange.getIn().setBody(c);                                 
       }
   })
-  
.to("aws2-sqs://camel-1?accessKey=RAW(xxx)&secretKey=RAW(xxx)&region=EU_WEST_1");
+  
.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 examinate to check what messages were successfull and 
what not.
@@ -362,7 +372,7 @@ Use deleteMessage operation to delete a single message. 
You'll need to set a rec
 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");
+  
.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.
@@ -373,7 +383,8 @@ 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");
+  .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 examinate to check the actual queues.
@@ -384,7 +395,8 @@ 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");
+  .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.