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
The following commit(s) were added to refs/heads/master by this push:
new 6250d6f Regen docs
6250d6f is described below
commit 6250d6fb3f2ae4588dd33c4984918f6148be7057
Author: Andrea Cosentino <[email protected]>
AuthorDate: Thu Jan 23 15:55:53 2020 +0100
Regen docs
---
docs/components/modules/ROOT/pages/aws-s3-component.adoc | 6 ++++++
docs/user-manual/modules/ROOT/pages/aggregate-eip.adoc | 6 +++---
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/docs/components/modules/ROOT/pages/aws-s3-component.adoc
b/docs/components/modules/ROOT/pages/aws-s3-component.adoc
index 90596b2..5045930 100644
--- a/docs/components/modules/ROOT/pages/aws-s3-component.adoc
+++ b/docs/components/modules/ROOT/pages/aws-s3-component.adoc
@@ -551,6 +551,12 @@ The component is capable of detecting the presence of an
AmazonS3 bean into the
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.
+If this is case for you, don't forget to remove the bucketName header from the
incoming exchange of the consumer, otherwise the file will be always
overwritten on the same
+original bucket.
+
== Dependencies
Maven users will need to add the following dependency to their pom.xml.
diff --git a/docs/user-manual/modules/ROOT/pages/aggregate-eip.adoc
b/docs/user-manual/modules/ROOT/pages/aggregate-eip.adoc
index da3d2c0..e129a26 100644
--- a/docs/user-manual/modules/ROOT/pages/aggregate-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/aggregate-eip.adoc
@@ -222,7 +222,7 @@ completion predicates / sizes / timeouts etc, and complete
the group.
For example the following logic (from an unit test) will complete the
group if the message body size is larger than 5. This is done by setting
-the property `Exchange.AGGREGATION_COMPLETE_CURRENT_GROUP` to `true`.
+the exchange property `Exchange.AGGREGATION_COMPLETE_CURRENT_GROUP` to `true`.
[source,java]
----
@@ -279,12 +279,12 @@ setting the property
`Exchange.AGGREGATION_COMPLETE_ALL_GROUPS` to `true`.
== Manually Force the Completion of All Aggregated Exchanges Immediately
You can manually trigger completion of all current aggregated exchanges
-by sending a message containing the header
+by sending an exchange containing the exchange property
`Exchange.AGGREGATION_COMPLETE_ALL_GROUPS` set to `true`. The message is
considered a signal message only, the message headers/contents will not
be processed otherwise.
-You can alternatively set the header
+You can alternatively set the exchange property
`Exchange.AGGREGATION_COMPLETE_ALL_GROUPS_INCLUSIVE` to `true` to trigger
completion of all groups after processing the current message.
