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 ae2c79dcd64424acc82a29c9a46620809ea6414c Author: Andrea Cosentino <[email protected]> AuthorDate: Tue Jan 26 14:06:33 2021 +0100 Full build --- docs/components/modules/ROOT/pages/aws2-kinesis-component.adoc | 6 ------ .../modules/ROOT/pages/aws2-kinesis-firehose-component.adoc | 6 ------ docs/components/modules/ROOT/pages/aws2-kms-component.adoc | 6 ------ docs/components/modules/ROOT/pages/aws2-lambda-component.adoc | 6 ------ docs/components/modules/ROOT/pages/aws2-mq-component.adoc | 6 ------ docs/components/modules/ROOT/pages/aws2-msk-component.adoc | 6 ------ docs/components/modules/ROOT/pages/aws2-s3-component.adoc | 6 ------ docs/components/modules/ROOT/pages/aws2-ses-component.adoc | 6 ------ docs/components/modules/ROOT/pages/aws2-sns-component.adoc | 6 ------ docs/components/modules/ROOT/pages/aws2-sqs-component.adoc | 6 ------ docs/components/modules/ROOT/pages/aws2-sts-component.adoc | 6 ------ docs/components/modules/ROOT/pages/aws2-translate-component.adoc | 6 ------ 12 files changed, 72 deletions(-) diff --git a/docs/components/modules/ROOT/pages/aws2-kinesis-component.adoc b/docs/components/modules/ROOT/pages/aws2-kinesis-component.adoc index 759ce68..aec3782 100644 --- a/docs/components/modules/ROOT/pages/aws2-kinesis-component.adoc +++ b/docs/components/modules/ROOT/pages/aws2-kinesis-component.adoc @@ -226,12 +226,6 @@ http://docs.aws.amazon.com/kinesis/latest/APIReference/API_PutRecord.html#API_Pu |======================================================================= -== Automatic detection of KinesisClient client in registry - -The component is capable of detecting the presence of an KinesisClient bean into the registry. -If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter. -This may be really useful for smarter configuration of the endpoint. - == Dependencies Maven users will need to add the following dependency to their pom.xml. diff --git a/docs/components/modules/ROOT/pages/aws2-kinesis-firehose-component.adoc b/docs/components/modules/ROOT/pages/aws2-kinesis-firehose-component.adoc index fdcaf4d4..da1a1b0 100644 --- a/docs/components/modules/ROOT/pages/aws2-kinesis-firehose-component.adoc +++ b/docs/components/modules/ROOT/pages/aws2-kinesis-firehose-component.adoc @@ -199,12 +199,6 @@ http://docs.aws.amazon.com/firehose/latest/APIReference/API_PutRecord.html#API_P |======================================================================= -== Automatic detection of AmazonKinesisFirehose client in registry - -The component is capable of detecting the presence of an FirehoseClient bean into the registry. -If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter. -This may be really useful for smarter configuration of the endpoint. - == Dependencies Maven users will need to add the following dependency to their pom.xml. diff --git a/docs/components/modules/ROOT/pages/aws2-kms-component.adoc b/docs/components/modules/ROOT/pages/aws2-kms-component.adoc index b42227a..34bcc73 100644 --- a/docs/components/modules/ROOT/pages/aws2-kms-component.adoc +++ b/docs/components/modules/ROOT/pages/aws2-kms-component.adoc @@ -182,12 +182,6 @@ from("direct:enableKey") .to("aws2-kms://test?kmsClient=#amazonKmsClient&operation=enableKey") -------------------------------------------------------------------------------- -== Automatic detection of KmsClient client in registry - -The component is capable of detecting the presence of an KmsClient bean into the registry. -If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter. -This may be really useful for smarter configuration of the endpoint. - == Using a POJO as body Sometimes build an AWS Request can be complex, because of multiple options. We introduce the possibility to use a POJO as body. diff --git a/docs/components/modules/ROOT/pages/aws2-lambda-component.adoc b/docs/components/modules/ROOT/pages/aws2-lambda-component.adoc index b127cfb..58424e6 100644 --- a/docs/components/modules/ROOT/pages/aws2-lambda-component.adoc +++ b/docs/components/modules/ROOT/pages/aws2-lambda-component.adoc @@ -218,12 +218,6 @@ The default is 3 seconds.|No To have a full understanding of how the component works, you may have a look at this https://github.com/apache/camel/blob/master/components/camel-aws/src/test/java/org/apache/camel/component/aws/lambda/integration/LambdaComponentIntegrationTest.java[integration test] -== Automatic detection of LambdaClient client in registry - -The component is capable of detecting the presence of an LambdaClient bean into the registry. -If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter. -This may be really useful for smarter configuration of the endpoint. - == Using a POJO as body Sometimes build an AWS Request can be complex, because of multiple options. We introduce the possibility to use a POJO as body. diff --git a/docs/components/modules/ROOT/pages/aws2-mq-component.adoc b/docs/components/modules/ROOT/pages/aws2-mq-component.adoc index a6a9eef..4c199e4 100644 --- a/docs/components/modules/ROOT/pages/aws2-mq-component.adoc +++ b/docs/components/modules/ROOT/pages/aws2-mq-component.adoc @@ -213,12 +213,6 @@ from("direct:listBrokers") .to("aws2-mq://test?amazonMqClient=#amazonMqClient&operation=rebootBroker") -------------------------------------------------------------------------------- -== Automatic detection of MqClient client in registry - -The component is capable of detecting the presence of an MqClient bean into the registry. -If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter. -This may be really useful for smarter configuration of the endpoint. - == Using a POJO as body Sometimes build an AWS Request can be complex, because of multiple options. We introduce the possibility to use a POJO as body. diff --git a/docs/components/modules/ROOT/pages/aws2-msk-component.adoc b/docs/components/modules/ROOT/pages/aws2-msk-component.adoc index 70576df..e90005f 100644 --- a/docs/components/modules/ROOT/pages/aws2-msk-component.adoc +++ b/docs/components/modules/ROOT/pages/aws2-msk-component.adoc @@ -201,12 +201,6 @@ from("direct:createCluster") .to("aws2-msk://test?mskClient=#amazonMskClient&operation=deleteCluster") -------------------------------------------------------------------------------- -== Automatic detection of KafkaClient client in registry - -The component is capable of detecting the presence of an KafkaClient bean into the registry. -If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter. -This may be really useful for smarter configuration of the endpoint. - == Using a POJO as body Sometimes build an AWS Request can be complex, because of multiple options. We introduce the possibility to use a POJO as body. diff --git a/docs/components/modules/ROOT/pages/aws2-s3-component.adoc b/docs/components/modules/ROOT/pages/aws2-s3-component.adoc index f90969c..47f8a4b 100644 --- a/docs/components/modules/ROOT/pages/aws2-s3-component.adoc +++ b/docs/components/modules/ROOT/pages/aws2-s3-component.adoc @@ -549,12 +549,6 @@ This operation will return a download link url for the file camel-key in the buc With the option `autoCreateBucket` users are able to avoid the autocreation of an S3 Bucket in case it doesn't exist. The default for this option is `true`. If set to false any operation on a not-existent bucket in AWS won't be successful and an error will be returned. -== Automatic detection of AmazonS3 client in registry - -The component is capable of detecting the presence of an AmazonS3 bean into the registry. -If it's the only instance of that type it will be used as 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. - == 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. diff --git a/docs/components/modules/ROOT/pages/aws2-ses-component.adoc b/docs/components/modules/ROOT/pages/aws2-ses-component.adoc index 83f6fcc..09f0546 100644 --- a/docs/components/modules/ROOT/pages/aws2-ses-component.adoc +++ b/docs/components/modules/ROOT/pages/aws2-ses-component.adoc @@ -162,12 +162,6 @@ from("direct:start") The `#client` refers to a `SesClient` in the Registry. -== Automatic detection of SesClient client in registry - -The component is capable of detecting the presence of an SesClient bean into the registry. -If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter. -This may be really useful for smarter configuration of the endpoint. - == Producer Examples [source,java] diff --git a/docs/components/modules/ROOT/pages/aws2-sns-component.adoc b/docs/components/modules/ROOT/pages/aws2-sns-component.adoc index 1374527..88c31e9 100644 --- a/docs/components/modules/ROOT/pages/aws2-sns-component.adoc +++ b/docs/components/modules/ROOT/pages/aws2-sns-component.adoc @@ -202,12 +202,6 @@ from("aws2-sqs://test-camel?amazonSQSClient=#amazonSQSClient&delay=50&maxMessage 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 `true`. If set to false any operation on a not-existent topic in AWS won't be successful and an error will be returned. -== Automatic detection of SnsClient client in registry - -The component is capable of detecting the presence of an SnsClient bean into the registry. -If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter. -This may be really useful for smarter configuration of the endpoint. - == 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 message to the SQS Queue. diff --git a/docs/components/modules/ROOT/pages/aws2-sqs-component.adoc b/docs/components/modules/ROOT/pages/aws2-sqs-component.adoc index e29befd..917f487 100644 --- a/docs/components/modules/ROOT/pages/aws2-sqs-component.adoc +++ b/docs/components/modules/ROOT/pages/aws2-sqs-component.adoc @@ -407,12 +407,6 @@ As result you'll get an exchange containing a `PurgeQueueResponse` instance. 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 `true`. If set to false any operation on a not-existent queue in AWS won't be successful and an error will be returned. -== Automatic detection of SqsClient client in registry - -The component is capable of detecting the presence of an SqsClient bean into the registry. -If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter. -This may be really useful for smarter configuration of the endpoint. - == Send Batch Message and Message Deduplication Strategy In case you're using a SendBatchMessage Operation, you can set two different kind of Message Deduplication Strategy: diff --git a/docs/components/modules/ROOT/pages/aws2-sts-component.adoc b/docs/components/modules/ROOT/pages/aws2-sts-component.adoc index 0f5cf4b..f7b3110 100644 --- a/docs/components/modules/ROOT/pages/aws2-sts-component.adoc +++ b/docs/components/modules/ROOT/pages/aws2-sts-component.adoc @@ -161,12 +161,6 @@ from("direct:getFederationToken") .to("aws2-sts://test?stsClient=#amazonSTSClient&operation=getSessionToken") -------------------------------------------------------------------------------- -== Automatic detection of StsClient client in registry - -The component is capable of detecting the presence of an StsClient bean into the registry. -If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter. -This may be really useful for smarter configuration of the endpoint. - == Using a POJO as body Sometimes build an AWS Request can be complex, because of multiple options. We introduce the possibility to use a POJO as body. diff --git a/docs/components/modules/ROOT/pages/aws2-translate-component.adoc b/docs/components/modules/ROOT/pages/aws2-translate-component.adoc index 2f951f7..2d3da4d 100644 --- a/docs/components/modules/ROOT/pages/aws2-translate-component.adoc +++ b/docs/components/modules/ROOT/pages/aws2-translate-component.adoc @@ -147,12 +147,6 @@ Camel-AWS Translate component provides the following operation on the producer s - translateText -== Automatic detection of TranslateClient client in registry - -The component is capable of detecting the presence of an TranslateClient bean into the registry. -If it's the only instance of that type it will be used as client and you won't have to define it as uri parameter. -This may be really useful for smarter configuration of the endpoint. - == Translate Text example ------------------------------------------------------------------------------------------------------
