This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch CAMEL-13678
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 9f6b9de2ee62028ffc7e3e28c2aee0fa0116426d
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Mon Jul 8 11:50:41 2019 +0200
Regen
---
components/camel-mail/src/main/docs/mail-component.adoc | 2 +-
components/readme.adoc | 4 ++--
docs/components/modules/ROOT/pages/mail-component.adoc | 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/components/camel-mail/src/main/docs/mail-component.adoc
b/components/camel-mail/src/main/docs/mail-component.adoc
index 664a379..68dccfc 100644
--- a/components/camel-mail/src/main/docs/mail-component.adoc
+++ b/components/camel-mail/src/main/docs/mail-component.adoc
@@ -246,7 +246,7 @@ The component supports 49 options, which are listed below.
| *camel.component.mail.configuration.ignore-uri-scheme* | Option to let Camel
ignore unsupported charset in the local JVM when sending mails. If the charset
is unsupported then charset=XXX (where XXX represents the unsupported charset)
is removed from the content-type and it relies on the platform default instead.
| false | Boolean
| *camel.component.mail.configuration.java-mail-properties* | Sets the java
mail options. Will clear any default properties and only use the properties
provided for this method. | | Properties
| *camel.component.mail.configuration.java-mail-sender* | To use a custom
{@link org.apache.camel.component.mail.JavaMailSender} for sending emails. | |
JavaMailSender
-| *camel.component.mail.configuration.map-mail-message* | Specifies whether
Camel should map the received mail message to Camel body/headers. If set to
true, the body of the mail message is mapped to the body of the Camel IN
message and the mail headers are mapped to IN headers. If this option is set to
false then the IN message contains a raw javax.mail.Message. You can retrieve
this raw message by calling exchange.getIn().getBody(javax.mail.Message.class).
| true | Boolean
+| *camel.component.mail.configuration.map-mail-message* | Specifies whether
Camel should map the received mail message to Camel body/headers/attachments.
If set to true, the body of the mail message is mapped to the body of the Camel
IN message, the mail headers are mapped to IN headers, and the attachments to
Camel IN attachment message. If this option is set to false then the IN message
contains a raw javax.mail.Message. You can retrieve this raw message by calling
exchange.getIn().get [...]
| *camel.component.mail.configuration.mime-decode-headers* | This option
enables transparent MIME decoding and unfolding for mail headers. | false |
Boolean
| *camel.component.mail.configuration.password* | The password for login | |
String
| *camel.component.mail.configuration.peek* | Will mark the javax.mail.Message
as peeked before processing the mail message. This applies to IMAPMessage
messages types only. By using peek the mail will not be eager marked as SEEN on
the mail server, which allows us to rollback the mail message if there is an
error processing in Camel. | true | Boolean
diff --git a/components/readme.adoc b/components/readme.adoc
index b21c547..323f7a3 100644
--- a/components/readme.adoc
+++ b/components/readme.adoc
@@ -202,10 +202,10 @@ Number of Components: 297 in 234 JAR artifacts (0
deprecated)
| link:camel-crypto-cms/src/main/docs/crypto-cms-component.adoc[Crypto CMS]
(camel-crypto-cms) +
`crypto-cms:cryptoOperation:name` | 2.20 | The crypto cms component is used
for encrypting data in CMS Enveloped Data format, decrypting CMS Enveloped
Data, signing data in CMS Signed Data format, and verifying CMS Signed Data.
-| link:@@@ARTIFACTID@@@/src/main/docs/cxf-component.adoc[CXF]
(@@@ARTIFACTID@@@) +
+| link:camel-cxf/src/main/docs/cxf-component.adoc[CXF] (camel-cxf) +
`cxf:beanId:address` | 1.0 | The cxf component is used for SOAP WebServices
using Apache CXF.
-| link:@@@ARTIFACTID@@@/src/main/docs/cxfrs-component.adoc[CXF-RS]
(@@@ARTIFACTID@@@) +
+| link:camel-cxf/src/main/docs/cxfrs-component.adoc[CXF-RS] (camel-cxf) +
`cxfrs:beanId:address` | 2.0 | The cxfrs component is used for JAX-RS REST
services using Apache CXF.
| link:camel-dataformat/src/main/docs/dataformat-component.adoc[Data Format]
(camel-dataformat) +
diff --git a/docs/components/modules/ROOT/pages/mail-component.adoc
b/docs/components/modules/ROOT/pages/mail-component.adoc
index 792df33..68dccfc 100644
--- a/docs/components/modules/ROOT/pages/mail-component.adoc
+++ b/docs/components/modules/ROOT/pages/mail-component.adoc
@@ -153,7 +153,7 @@ with the following path and query parameters:
| *fetchSize* (consumer) | Sets the maximum number of messages to consume
during a poll. This can be used to avoid overloading a mail server, if a
mailbox folder contains a lot of messages. Default value of -1 means no fetch
size and all messages will be consumed. Setting the value to 0 is a special
corner case, where Camel will not consume any messages at all. | -1 | int
| *folderName* (consumer) | The folder to poll. | INBOX | String
| *mailUidGenerator* (consumer) | A pluggable MailUidGenerator that allows to
use custom logic to generate UUID of the mail message. | | MailUidGenerator
-| *mapMailMessage* (consumer) | Specifies whether Camel should map the
received mail message to Camel body/headers. If set to true, the body of the
mail message is mapped to the body of the Camel IN message and the mail headers
are mapped to IN headers. If this option is set to false then the IN message
contains a raw javax.mail.Message. You can retrieve this raw message by calling
exchange.getIn().getBody(javax.mail.Message.class). | true | boolean
+| *mapMailMessage* (consumer) | Specifies whether Camel should map the
received mail message to Camel body/headers/attachments. If set to true, the
body of the mail message is mapped to the body of the Camel IN message, the
mail headers are mapped to IN headers, and the attachments to Camel IN
attachment message. If this option is set to false then the IN message contains
a raw javax.mail.Message. You can retrieve this raw message by calling
exchange.getIn().getBody(javax.mail.Message.cl [...]
| *pollStrategy* (consumer) | 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.
| | PollingConsumerPoll Strategy
| *postProcessAction* (consumer) | Refers to an MailBoxPostProcessAction for
doing post processing tasks on the mailbox once the normal processing ended. |
| MailBoxPostProcess Action
| *bcc* (producer) | Sets the BCC email address. Separate multiple email
addresses with comma. | | String
@@ -246,7 +246,7 @@ The component supports 49 options, which are listed below.
| *camel.component.mail.configuration.ignore-uri-scheme* | Option to let Camel
ignore unsupported charset in the local JVM when sending mails. If the charset
is unsupported then charset=XXX (where XXX represents the unsupported charset)
is removed from the content-type and it relies on the platform default instead.
| false | Boolean
| *camel.component.mail.configuration.java-mail-properties* | Sets the java
mail options. Will clear any default properties and only use the properties
provided for this method. | | Properties
| *camel.component.mail.configuration.java-mail-sender* | To use a custom
{@link org.apache.camel.component.mail.JavaMailSender} for sending emails. | |
JavaMailSender
-| *camel.component.mail.configuration.map-mail-message* | Specifies whether
Camel should map the received mail message to Camel body/headers. If set to
true, the body of the mail message is mapped to the body of the Camel IN
message and the mail headers are mapped to IN headers. If this option is set to
false then the IN message contains a raw javax.mail.Message. You can retrieve
this raw message by calling exchange.getIn().getBody(javax.mail.Message.class).
| true | Boolean
+| *camel.component.mail.configuration.map-mail-message* | Specifies whether
Camel should map the received mail message to Camel body/headers/attachments.
If set to true, the body of the mail message is mapped to the body of the Camel
IN message, the mail headers are mapped to IN headers, and the attachments to
Camel IN attachment message. If this option is set to false then the IN message
contains a raw javax.mail.Message. You can retrieve this raw message by calling
exchange.getIn().get [...]
| *camel.component.mail.configuration.mime-decode-headers* | This option
enables transparent MIME decoding and unfolding for mail headers. | false |
Boolean
| *camel.component.mail.configuration.password* | The password for login | |
String
| *camel.component.mail.configuration.peek* | Will mark the javax.mail.Message
as peeked before processing the mail message. This applies to IMAPMessage
messages types only. By using peek the mail will not be eager marked as SEEN on
the mail server, which allows us to rollback the mail message if there is an
error processing in Camel. | true | Boolean
