svn commit: r838246 [1/2] - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache camel-2110-release.html camel-jmx.html mail.html

[bu...@apache.org]

Author: buildbot
Date: Tue Nov 13 18:22:26 2012
New Revision: 838246

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/book-component-appendix.html
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-2110-release.html
    websites/production/camel/content/camel-jmx.html
    websites/production/camel/content/mail.html

Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Tue Nov 13 18:22:26 2012
@@ -10551,7 +10551,7 @@ smtp:<span class="code-comment">//mycomp
 
 <h3><a shape="rect" name="BookComponentAppendix-Options"></a>Options</h3>
 <div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Property </th><th colspan="1" rowspan="1" class="confluenceTh"> Default </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The host name or IP address to connect to. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>port</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> See <a shape="rect" href="#BookComponentAppendix-DefaultPorts">DefaultPorts</a> </td><td colspan="1" rowspan="1" class="confluenceTd"> The TCP port number to connect on. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>username</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The user name on the e
 mail server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>password</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The password on the email server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ignoreUriScheme</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If <tt>false</tt>, Camel uses the scheme to determine the transport protocol (POP, IMAP, SMTP etc.) </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>defaultEncoding</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The default encoding to use for Mime Messages. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>contentType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>text/plain</tt> </
 td><td colspan="1" rowspan="1" class="confluenceTd"> The mail message content type. Use <tt>text/html</tt> for HTML mails. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>folderName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>INBOX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The folder to poll. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>destination</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>username@host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>@deprecated</b> Use the <tt>to</tt> option instead. The <tt>TO</tt> recipients (receivers of the email). </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>to</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>username@host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The TO recipients (the receivers of the mail). Separate multiple email addresses with a comma. </td></
 tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>replyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>alias@host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> As of <b>Camel 2.8.4, 2.9.1+</b>, the Reply-To recipients (the receivers of the response mail). Separate multiple email addresses with a comma. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CC</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">The CC recipients (the receivers of the mail). Separate multiple email addresses with a comma. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>BCC</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The BCC recipients (the receivers of the mail). Separate multiple email addresses with a comma. </td></tr><tr><td colspan="1" rowspan="1" class="c
 onfluenceTd"> <tt>from</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>camel@localhost</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The FROM email address. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>subject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> As of <b>Camel 2.3</b>, the Subject of the message being sent. Note: Setting the subject in the header takes precedence over this option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>delete</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Deletes the messages after they have been processed. This is done by setting the <tt>DELETED</tt> flag on the mail message. If <tt>false</tt>, the <tt>SEEN</tt> flag is set instead. As of <b>Camel 2.10</b> you can override this configuration option by setting a h
 eader with the key <tt>delete</tt> to determine if the mail should be deleted or not. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>unseen</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> It is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. The default option of <tt>true</tt> will filter to only unseen messages.  POP3 does not support the <tt>SEEN</tt> flag, so this option is not supported in POP3; use IMAP instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>copyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.10:</b> Consumer only. After processing a mail message, it can be copied to a mail folder with the given name. You can override
  this configuration value, with a header with the key <tt>copyTo</tt>, allowing you to copy messages to folder names configured at runtime. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>fetchSize</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 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 <tt>-1</tt> 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. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>alternativeBodyHeader</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelMailAlternativeBody</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies the key to an IN message header that contains an 
 alternative email body. For example, if you send emails in <tt>text/html</tt> format and want to provide an alternative mail body for non-HTML email clients, set the alternative mail body with this key as a header. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>debugMode</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Enable debug mode on the underlying mail framework. The SUN Mail framework logs the debug messages to <tt>System.out</tt> by default. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>connectionTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>30000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The connection timeout in milliseconds. Default is 30 seconds. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>consumer.initialDelay</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt
 >1000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Milliseconds before the polling starts. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>consumer.delay</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>60000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Camel will poll the mailbox only once a minute by default to avoid overloading the mail server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>consumer.useFixedDelay</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Set to <tt>true</tt> to use a fixed delay between polls, otherwise fixed rate is used. See <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ScheduledExecutorService.html" rel="nofollow">ScheduledExecutorService</a> in JDK for details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"
 > <tt>disconnect</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8.3/2.9:</b> Whether the consumer should disconnect after polling. If enabled this forces Camel to connect on each poll. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>mail.XXX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Set any <a shape="rect" class="external-link" href="http://java.sun.com/products/javamail/javadocs/index.html" rel="nofollow">additional java mail properties</a>. For instance if you want to set a special property when using POP3 you can now provide the option directly in the URI such as: <tt>mail.pop3.forgettopheaders=true</tt>. You can set multiple such options, for example: <tt>mail.pop3.forgettopheaders=true&amp;mail.mime.encodefilename=true</tt>. </td></tr><tr><td colspan="1" rowspan="1" class=
 "confluenceTd"> <tt>mapMailMessage</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8:</b> 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 <tt>javax.mail.Message</tt>. You can retrieve this raw message by calling <tt>exchange.getIn().getBody(javax.mail.Message.class)</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>maxMessagesPerPoll</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid downloading thousands of files
  when the server starts up. Set a value of 0 or negative to disable this option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>javaMailSender</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies a pluggable <tt>org.springframework.mail.javamail.JavaMailSender</tt> instance in order to use a custom email implementation. If none provided, Camel uses the default <tt>org.springframework.mail.javamail.JavaMailSenderImpl</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ignoreUnsupportedCharset</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Option to let Camel ignore unsupported charset in the local JVM when sending mails. If the charset is unsupported then <tt>charset=XXX</tt> (where <tt>XXX</tt> represents the unsupported charset) is removed from the <tt>content-type<
 /tt> and it relies on the platform default instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>sslContextParameters</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.10:</b> Reference to a <tt>org.apache.camel.util.jsse.SSLContextParameters</tt> in the <a shape="rect" class="external-link" href="http://camel.apache.org/registry.html">Registry</a>.&#160; This reference overrides any configured SSLContextParameters at the component level.&#160; See <a shape="rect" class="external-link" href="http://camel.apache.org/http4.html#HTTP4-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Property </th><th colspan="1" rowspan="1" class="confluenceTh"> Default </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The host name or IP address to connect to. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>port</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> See <a shape="rect" href="#BookComponentAppendix-DefaultPorts">DefaultPorts</a> </td><td colspan="1" rowspan="1" class="confluenceTd"> The TCP port number to connect on. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>username</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The user name on the e
 mail server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>password</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The password on the email server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ignoreUriScheme</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If <tt>false</tt>, Camel uses the scheme to determine the transport protocol (POP, IMAP, SMTP etc.) </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>defaultEncoding</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The default encoding to use for Mime Messages. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>contentType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>text/plain</tt> </
 td><td colspan="1" rowspan="1" class="confluenceTd"> The mail message content type. Use <tt>text/html</tt> for HTML mails. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>folderName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>INBOX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The folder to poll. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>destination</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>username@host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>@deprecated</b> Use the <tt>to</tt> option instead. The <tt>TO</tt> recipients (receivers of the email). </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>to</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>username@host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The TO recipients (the receivers of the mail). Separate multiple email addresses with a comma. </td></
 tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>replyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>alias@host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> As of <b>Camel 2.8.4, 2.9.1+</b>, the Reply-To recipients (the receivers of the response mail). Separate multiple email addresses with a comma. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CC</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">The CC recipients (the receivers of the mail). Separate multiple email addresses with a comma. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>BCC</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The BCC recipients (the receivers of the mail). Separate multiple email addresses with a comma. </td></tr><tr><td colspan="1" rowspan="1" class="c
 onfluenceTd"> <tt>from</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>camel@localhost</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The FROM email address. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>subject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> As of <b>Camel 2.3</b>, the Subject of the message being sent. Note: Setting the subject in the header takes precedence over this option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>delete</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Deletes the messages after they have been processed. This is done by setting the <tt>DELETED</tt> flag on the mail message. If <tt>false</tt>, the <tt>SEEN</tt> flag is set instead. As of <b>Camel 2.10</b> you can override this configuration option by setting a h
 eader with the key <tt>delete</tt> to determine if the mail should be deleted or not. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>unseen</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> It is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. The default option of <tt>true</tt> will filter to only unseen messages.  POP3 does not support the <tt>SEEN</tt> flag, so this option is not supported in POP3; use IMAP instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>copyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.10:</b> Consumer only. After processing a mail message, it can be copied to a mail folder with the given name. You can override
  this configuration value, with a header with the key <tt>copyTo</tt>, allowing you to copy messages to folder names configured at runtime. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>fetchSize</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 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 <tt>-1</tt> 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. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>alternativeBodyHeader</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelMailAlternativeBody</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies the key to an IN message header that contains an 
 alternative email body. For example, if you send emails in <tt>text/html</tt> format and want to provide an alternative mail body for non-HTML email clients, set the alternative mail body with this key as a header. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>debugMode</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Enable debug mode on the underlying mail framework. The SUN Mail framework logs the debug messages to <tt>System.out</tt> by default. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>connectionTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>30000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The connection timeout in milliseconds. Default is 30 seconds. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>consumer.initialDelay</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt
 >1000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Milliseconds before the polling starts. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>consumer.delay</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>60000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Camel will poll the mailbox only once a minute by default to avoid overloading the mail server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>consumer.useFixedDelay</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Set to <tt>true</tt> to use a fixed delay between polls, otherwise fixed rate is used. See <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ScheduledExecutorService.html" rel="nofollow">ScheduledExecutorService</a> in JDK for details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"
 > <tt>disconnect</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8.3/2.9:</b> Whether the consumer should disconnect after polling. If enabled this forces Camel to connect on each poll. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>mail.XXX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Set any <a shape="rect" class="external-link" href="http://java.sun.com/products/javamail/javadocs/index.html" rel="nofollow">additional java mail properties</a>. For instance if you want to set a special property when using POP3 you can now provide the option directly in the URI such as: <tt>mail.pop3.forgettopheaders=true</tt>. You can set multiple such options, for example: <tt>mail.pop3.forgettopheaders=true&amp;mail.mime.encodefilename=true</tt>. </td></tr><tr><td colspan="1" rowspan="1" class=
 "confluenceTd"> <tt>mapMailMessage</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8:</b> 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 <tt>javax.mail.Message</tt>. You can retrieve this raw message by calling <tt>exchange.getIn().getBody(javax.mail.Message.class)</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>maxMessagesPerPoll</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid downloading thousands of files
  when the server starts up. Set a value of 0 or negative to disable this option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>javaMailSender</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies a pluggable <tt>org.springframework.mail.javamail.JavaMailSender</tt> instance in order to use a custom email implementation. If none provided, Camel uses the default <tt>org.springframework.mail.javamail.JavaMailSenderImpl</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ignoreUnsupportedCharset</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Option to let Camel ignore unsupported charset in the local JVM when sending mails. If the charset is unsupported then <tt>charset=XXX</tt> (where <tt>XXX</tt> represents the unsupported charset) is removed from the <tt>content-type<
 /tt> and it relies on the platform default instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>sslContextParameters</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.10:</b> Reference to a <tt>org.apache.camel.util.jsse.SSLContextParameters</tt> in the <a shape="rect" class="external-link" href="http://camel.apache.org/registry.html">Registry</a>.&#160; This reference overrides any configured SSLContextParameters at the component level.&#160; See <a shape="rect" class="external-link" href="http://camel.apache.org/http4.html#HTTP4-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>searchTerm</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> Refers to a <tt>javax.mail.search.S
 earchTerm</tt> which allows to filter mails based on search criteria such as subject, body, from, sent after a certain date etc. See further below for examples. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>searchTerm.xxx</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> To configure search terms directly from the endpoint uri, which supports a limited number of terms defined by the <tt>org.apache.camel.component.mail.SimpleSearchTerm</tt> class. See further below for examples. </td></tr></tbody></table>
 </div>
 </div>
 
@@ -10822,6 +10822,66 @@ from(<span class="code-quote">"imaps:<sp
 </div></div>
 
 
+<h3><a shape="rect" name="BookComponentAppendix-UsingcustomSearchTerm"></a>Using custom SearchTerm</h3>
+<p><b>Available as of Camel 2.11</b></p>
+
+<p>You can configure a <tt>searchTerm</tt> on the <tt>MailEndpoint</tt> which allows you to filter out unwanted mails. </p>
+
+<p>For example to filter mails to contain Camel in either Subject or Text you can do as follows:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;route&gt;</span>
+  <span class="code-tag">&lt;from uri=<span class="code-quote">"imaps://mymailseerver?username=foo&amp;password=secret&amp;searchTerm.subjectOrBody=Camel"</span>/&gt;</span>
+  <span class="code-tag">&lt;to uri=<span class="code-quote">"bean:myBean"</span>/&gt;</span>
+<span class="code-tag">&lt;/route&gt;</span>
+</pre>
+</div></div>
+
+<p>Notice we use the <tt>"searchTerm.subjectOrBody"</tt> as parameter key to indicate that we want to search on mail subject or body, to contain the word "Camel".<br clear="none">
+The class <tt>org.apache.camel.component.mail.SimpleSearchTerm</tt> has a number of options you can configure:</p>
+
+<div class="confluenceTableSmall"><div class="table-wrap">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Option </th><th colspan="1" rowspan="1" class="confluenceTh"> Default </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> unseen </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Whether to limit by unseen mails only. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> subjectOrBody </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To limit by subject or body to contain the word. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> subject </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The subject must contain the word. </td></tr><tr><td colspan="1" rowspan="1" cl
 ass="confluenceTd"> body </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The body must contain the word. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> from </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The mail must be from a given email pattern. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> to </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The mail must be to a given email pattern. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> fromSentDate </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The mail must be sent after or equals (GE) a given date. The date pattern is <tt>yyyy-MM-dd HH:mm:SS</tt>, eg use <tt>"2012-01-01 00:00
 :00"</tt> to be from the year 2012 onwards. You can use <tt>"now"</tt> for current timestamp. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> toSentDate </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The mail must be sent before or equals (BE) a given date. The date pattern is <tt>yyyy-MM-dd HH:mm:SS</tt>, eg use <tt>"2012-01-01 00:00:00"</tt> to be before the year 2012. You can use <tt>"now"</tt> for current timestamp. </td></tr></tbody></table>
+</div>
+</div>
+
+<p>The <tt>SimpleSearchTerm</tt> is designed to be easily configurable from a POJO, so you can also configure it using a &lt;bean&gt; style in XML</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-java">
+&lt;bean id=<span class="code-quote">"mySearchTerm"</span> class=<span class="code-quote">"org.apache.camel.component.mail.SimpleSearchTerm"</span>&gt;
+  &lt;property name=<span class="code-quote">"subject"</span> value=<span class="code-quote">"Order"</span>/&gt;
+  &lt;property name=<span class="code-quote">"to"</span> value=<span class="code-quote">"acme-order@acme.com"</span>/&gt;
+  &lt;property name=<span class="code-quote">"fromSentDate"</span> value=<span class="code-quote">"now"</span>/&gt;
+ &lt;/bean&gt;
+</pre>
+</div></div>
+
+<p>You can then refer to this bean, using #beanId in your Camel route as shown:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;route&gt;</span>
+  <span class="code-tag">&lt;from uri=<span class="code-quote">"imaps://mymailseerver?username=foo&amp;password=secret&amp;searchTerm=#mySearchTerm"</span>/&gt;</span>
+  <span class="code-tag">&lt;to uri=<span class="code-quote">"bean:myBean"</span>/&gt;</span>
+<span class="code-tag">&lt;/route&gt;</span>
+</pre>
+</div></div>
+
+<p>In Java there is a builder class to build compound <tt>SearchTerm}}s using the {{org.apache.camel.component.mail.SearchTermBuilder</tt> class.<br clear="none">
+This allows you to build complex terms such as:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-java">
+<span class="code-comment">// we just want the unseen mails which is not spam
+</span>SearchTermBuilder builder = <span class="code-keyword">new</span> SearchTermBuilder();
+
+builder.unseen().body(Op.not, <span class="code-quote">"Spam"</span>).subject(Op.not, <span class="code-quote">"Spam"</span>)
+  <span class="code-comment">// which was sent from either foo or bar
+</span>  .from(<span class="code-quote">"foo@somewhere.com"</span>).from(Op.or, <span class="code-quote">"bar@somewhere.com"</span>);
+  <span class="code-comment">// .. and we could <span class="code-keyword">continue</span> building the terms
+</span>
+SearchTerm term = builder.build();
+</pre>
+</div></div>
+
 <h3><a shape="rect" name="BookComponentAppendix-SeeAlso"></a>See Also</h3>
 <ul><li><a shape="rect" href="configuring-camel.html" title="Configuring Camel">Configuring Camel</a></li><li><a shape="rect" href="component.html" title="Component">Component</a></li><li><a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a></li><li><a shape="rect" href="getting-started.html" title="Getting Started">Getting Started</a></li></ul>
 

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Tue Nov 13 18:22:26 2012
@@ -30787,7 +30787,7 @@ smtp:<span class="code-comment">//mycomp
 
 <h3><a shape="rect" name="BookInOnePage-Options"></a>Options</h3>
 <div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Property </th><th colspan="1" rowspan="1" class="confluenceTh"> Default </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The host name or IP address to connect to. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>port</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> See <a shape="rect" href="#BookInOnePage-DefaultPorts">DefaultPorts</a> </td><td colspan="1" rowspan="1" class="confluenceTd"> The TCP port number to connect on. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>username</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The user name on the email ser
 ver. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>password</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The password on the email server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ignoreUriScheme</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If <tt>false</tt>, Camel uses the scheme to determine the transport protocol (POP, IMAP, SMTP etc.) </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>defaultEncoding</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The default encoding to use for Mime Messages. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>contentType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>text/plain</tt> </td><td c
 olspan="1" rowspan="1" class="confluenceTd"> The mail message content type. Use <tt>text/html</tt> for HTML mails. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>folderName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>INBOX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The folder to poll. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>destination</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>username@host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>@deprecated</b> Use the <tt>to</tt> option instead. The <tt>TO</tt> recipients (receivers of the email). </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>to</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>username@host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The TO recipients (the receivers of the mail). Separate multiple email addresses with a comma. </td></tr><tr><
 td colspan="1" rowspan="1" class="confluenceTd"> <tt>replyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>alias@host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> As of <b>Camel 2.8.4, 2.9.1+</b>, the Reply-To recipients (the receivers of the response mail). Separate multiple email addresses with a comma. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CC</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">The CC recipients (the receivers of the mail). Separate multiple email addresses with a comma. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>BCC</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The BCC recipients (the receivers of the mail). Separate multiple email addresses with a comma. </td></tr><tr><td colspan="1" rowspan="1" class="confluenc
 eTd"> <tt>from</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>camel@localhost</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The FROM email address. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>subject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> As of <b>Camel 2.3</b>, the Subject of the message being sent. Note: Setting the subject in the header takes precedence over this option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>delete</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Deletes the messages after they have been processed. This is done by setting the <tt>DELETED</tt> flag on the mail message. If <tt>false</tt>, the <tt>SEEN</tt> flag is set instead. As of <b>Camel 2.10</b> you can override this configuration option by setting a header wi
 th the key <tt>delete</tt> to determine if the mail should be deleted or not. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>unseen</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> It is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. The default option of <tt>true</tt> will filter to only unseen messages.  POP3 does not support the <tt>SEEN</tt> flag, so this option is not supported in POP3; use IMAP instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>copyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.10:</b> Consumer only. After processing a mail message, it can be copied to a mail folder with the given name. You can override this co
 nfiguration value, with a header with the key <tt>copyTo</tt>, allowing you to copy messages to folder names configured at runtime. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>fetchSize</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 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 <tt>-1</tt> 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. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>alternativeBodyHeader</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelMailAlternativeBody</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies the key to an IN message header that contains an alternat
 ive email body. For example, if you send emails in <tt>text/html</tt> format and want to provide an alternative mail body for non-HTML email clients, set the alternative mail body with this key as a header. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>debugMode</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Enable debug mode on the underlying mail framework. The SUN Mail framework logs the debug messages to <tt>System.out</tt> by default. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>connectionTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>30000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The connection timeout in milliseconds. Default is 30 seconds. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>consumer.initialDelay</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1000</t
 t> </td><td colspan="1" rowspan="1" class="confluenceTd"> Milliseconds before the polling starts. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>consumer.delay</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>60000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Camel will poll the mailbox only once a minute by default to avoid overloading the mail server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>consumer.useFixedDelay</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Set to <tt>true</tt> to use a fixed delay between polls, otherwise fixed rate is used. See <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ScheduledExecutorService.html" rel="nofollow">ScheduledExecutorService</a> in JDK for details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>di
 sconnect</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8.3/2.9:</b> Whether the consumer should disconnect after polling. If enabled this forces Camel to connect on each poll. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>mail.XXX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Set any <a shape="rect" class="external-link" href="http://java.sun.com/products/javamail/javadocs/index.html" rel="nofollow">additional java mail properties</a>. For instance if you want to set a special property when using POP3 you can now provide the option directly in the URI such as: <tt>mail.pop3.forgettopheaders=true</tt>. You can set multiple such options, for example: <tt>mail.pop3.forgettopheaders=true&amp;mail.mime.encodefilename=true</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="conflue
 nceTd"> <tt>mapMailMessage</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8:</b> 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 <tt>javax.mail.Message</tt>. You can retrieve this raw message by calling <tt>exchange.getIn().getBody(javax.mail.Message.class)</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>maxMessagesPerPoll</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid downloading thousands of files when th
 e server starts up. Set a value of 0 or negative to disable this option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>javaMailSender</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies a pluggable <tt>org.springframework.mail.javamail.JavaMailSender</tt> instance in order to use a custom email implementation. If none provided, Camel uses the default <tt>org.springframework.mail.javamail.JavaMailSenderImpl</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ignoreUnsupportedCharset</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Option to let Camel ignore unsupported charset in the local JVM when sending mails. If the charset is unsupported then <tt>charset=XXX</tt> (where <tt>XXX</tt> represents the unsupported charset) is removed from the <tt>content-type</tt> and
  it relies on the platform default instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>sslContextParameters</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.10:</b> Reference to a <tt>org.apache.camel.util.jsse.SSLContextParameters</tt> in the <a shape="rect" class="external-link" href="http://camel.apache.org/registry.html">Registry</a>.&#160; This reference overrides any configured SSLContextParameters at the component level.&#160; See <a shape="rect" class="external-link" href="http://camel.apache.org/http4.html#HTTP4-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Property </th><th colspan="1" rowspan="1" class="confluenceTh"> Default </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The host name or IP address to connect to. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>port</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> See <a shape="rect" href="#BookInOnePage-DefaultPorts">DefaultPorts</a> </td><td colspan="1" rowspan="1" class="confluenceTd"> The TCP port number to connect on. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>username</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> The user name on the email ser
 ver. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>password</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The password on the email server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ignoreUriScheme</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If <tt>false</tt>, Camel uses the scheme to determine the transport protocol (POP, IMAP, SMTP etc.) </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>defaultEncoding</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The default encoding to use for Mime Messages. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>contentType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>text/plain</tt> </td><td c
 olspan="1" rowspan="1" class="confluenceTd"> The mail message content type. Use <tt>text/html</tt> for HTML mails. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>folderName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>INBOX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The folder to poll. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>destination</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>username@host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>@deprecated</b> Use the <tt>to</tt> option instead. The <tt>TO</tt> recipients (receivers of the email). </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>to</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>username@host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The TO recipients (the receivers of the mail). Separate multiple email addresses with a comma. </td></tr><tr><
 td colspan="1" rowspan="1" class="confluenceTd"> <tt>replyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>alias@host</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> As of <b>Camel 2.8.4, 2.9.1+</b>, the Reply-To recipients (the receivers of the response mail). Separate multiple email addresses with a comma. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CC</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">The CC recipients (the receivers of the mail). Separate multiple email addresses with a comma. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>BCC</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The BCC recipients (the receivers of the mail). Separate multiple email addresses with a comma. </td></tr><tr><td colspan="1" rowspan="1" class="confluenc
 eTd"> <tt>from</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>camel@localhost</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The FROM email address. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>subject</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> As of <b>Camel 2.3</b>, the Subject of the message being sent. Note: Setting the subject in the header takes precedence over this option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>delete</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Deletes the messages after they have been processed. This is done by setting the <tt>DELETED</tt> flag on the mail message. If <tt>false</tt>, the <tt>SEEN</tt> flag is set instead. As of <b>Camel 2.10</b> you can override this configuration option by setting a header wi
 th the key <tt>delete</tt> to determine if the mail should be deleted or not. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>unseen</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> It is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. The default option of <tt>true</tt> will filter to only unseen messages.  POP3 does not support the <tt>SEEN</tt> flag, so this option is not supported in POP3; use IMAP instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>copyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.10:</b> Consumer only. After processing a mail message, it can be copied to a mail folder with the given name. You can override this co
 nfiguration value, with a header with the key <tt>copyTo</tt>, allowing you to copy messages to folder names configured at runtime. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>fetchSize</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 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 <tt>-1</tt> 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. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>alternativeBodyHeader</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>CamelMailAlternativeBody</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies the key to an IN message header that contains an alternat
 ive email body. For example, if you send emails in <tt>text/html</tt> format and want to provide an alternative mail body for non-HTML email clients, set the alternative mail body with this key as a header. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>debugMode</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Enable debug mode on the underlying mail framework. The SUN Mail framework logs the debug messages to <tt>System.out</tt> by default. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>connectionTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>30000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The connection timeout in milliseconds. Default is 30 seconds. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>consumer.initialDelay</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1000</t
 t> </td><td colspan="1" rowspan="1" class="confluenceTd"> Milliseconds before the polling starts. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>consumer.delay</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>60000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Camel will poll the mailbox only once a minute by default to avoid overloading the mail server. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>consumer.useFixedDelay</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Set to <tt>true</tt> to use a fixed delay between polls, otherwise fixed rate is used. See <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ScheduledExecutorService.html" rel="nofollow">ScheduledExecutorService</a> in JDK for details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>di
 sconnect</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8.3/2.9:</b> Whether the consumer should disconnect after polling. If enabled this forces Camel to connect on each poll. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>mail.XXX</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Set any <a shape="rect" class="external-link" href="http://java.sun.com/products/javamail/javadocs/index.html" rel="nofollow">additional java mail properties</a>. For instance if you want to set a special property when using POP3 you can now provide the option directly in the URI such as: <tt>mail.pop3.forgettopheaders=true</tt>. You can set multiple such options, for example: <tt>mail.pop3.forgettopheaders=true&amp;mail.mime.encodefilename=true</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="conflue
 nceTd"> <tt>mapMailMessage</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.8:</b> 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 <tt>javax.mail.Message</tt>. You can retrieve this raw message by calling <tt>exchange.getIn().getBody(javax.mail.Message.class)</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>maxMessagesPerPoll</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid downloading thousands of files when th
 e server starts up. Set a value of 0 or negative to disable this option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>javaMailSender</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies a pluggable <tt>org.springframework.mail.javamail.JavaMailSender</tt> instance in order to use a custom email implementation. If none provided, Camel uses the default <tt>org.springframework.mail.javamail.JavaMailSenderImpl</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>ignoreUnsupportedCharset</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Option to let Camel ignore unsupported charset in the local JVM when sending mails. If the charset is unsupported then <tt>charset=XXX</tt> (where <tt>XXX</tt> represents the unsupported charset) is removed from the <tt>content-type</tt> and
  it relies on the platform default instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>sslContextParameters</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.10:</b> Reference to a <tt>org.apache.camel.util.jsse.SSLContextParameters</tt> in the <a shape="rect" class="external-link" href="http://camel.apache.org/registry.html">Registry</a>.&#160; This reference overrides any configured SSLContextParameters at the component level.&#160; See <a shape="rect" class="external-link" href="http://camel.apache.org/http4.html#HTTP4-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>searchTerm</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> Refers to a <tt>javax.mail.search.SearchTer
 m</tt> which allows to filter mails based on search criteria such as subject, body, from, sent after a certain date etc. See further below for examples. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>searchTerm.xxx</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> To configure search terms directly from the endpoint uri, which supports a limited number of terms defined by the <tt>org.apache.camel.component.mail.SimpleSearchTerm</tt> class. See further below for examples. </td></tr></tbody></table>
 </div>
 </div>
 
@@ -31058,6 +31058,66 @@ from(<span class="code-quote">"imaps:<sp
 </div></div>
 
 
+<h3><a shape="rect" name="BookInOnePage-UsingcustomSearchTerm"></a>Using custom SearchTerm</h3>
+<p><b>Available as of Camel 2.11</b></p>
+
+<p>You can configure a <tt>searchTerm</tt> on the <tt>MailEndpoint</tt> which allows you to filter out unwanted mails. </p>
+
+<p>For example to filter mails to contain Camel in either Subject or Text you can do as follows:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;route&gt;</span>
+  <span class="code-tag">&lt;from uri=<span class="code-quote">"imaps://mymailseerver?username=foo&amp;password=secret&amp;searchTerm.subjectOrBody=Camel"</span>/&gt;</span>
+  <span class="code-tag">&lt;to uri=<span class="code-quote">"bean:myBean"</span>/&gt;</span>
+<span class="code-tag">&lt;/route&gt;</span>
+</pre>
+</div></div>
+
+<p>Notice we use the <tt>"searchTerm.subjectOrBody"</tt> as parameter key to indicate that we want to search on mail subject or body, to contain the word "Camel".<br clear="none">
+The class <tt>org.apache.camel.component.mail.SimpleSearchTerm</tt> has a number of options you can configure:</p>
+
+<div class="confluenceTableSmall"><div class="table-wrap">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Option </th><th colspan="1" rowspan="1" class="confluenceTh"> Default </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> unseen </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Whether to limit by unseen mails only. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> subjectOrBody </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> To limit by subject or body to contain the word. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> subject </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The subject must contain the word. </td></tr><tr><td colspan="1" rowspan="1" cl
 ass="confluenceTd"> body </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The body must contain the word. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> from </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The mail must be from a given email pattern. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> to </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The mail must be to a given email pattern. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> fromSentDate </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The mail must be sent after or equals (GE) a given date. The date pattern is <tt>yyyy-MM-dd HH:mm:SS</tt>, eg use <tt>"2012-01-01 00:00
 :00"</tt> to be from the year 2012 onwards. You can use <tt>"now"</tt> for current timestamp. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> toSentDate </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> The mail must be sent before or equals (BE) a given date. The date pattern is <tt>yyyy-MM-dd HH:mm:SS</tt>, eg use <tt>"2012-01-01 00:00:00"</tt> to be before the year 2012. You can use <tt>"now"</tt> for current timestamp. </td></tr></tbody></table>
+</div>
+</div>
+
+<p>The <tt>SimpleSearchTerm</tt> is designed to be easily configurable from a POJO, so you can also configure it using a &lt;bean&gt; style in XML</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-java">
+&lt;bean id=<span class="code-quote">"mySearchTerm"</span> class=<span class="code-quote">"org.apache.camel.component.mail.SimpleSearchTerm"</span>&gt;
+  &lt;property name=<span class="code-quote">"subject"</span> value=<span class="code-quote">"Order"</span>/&gt;
+  &lt;property name=<span class="code-quote">"to"</span> value=<span class="code-quote">"acme-order@acme.com"</span>/&gt;
+  &lt;property name=<span class="code-quote">"fromSentDate"</span> value=<span class="code-quote">"now"</span>/&gt;
+ &lt;/bean&gt;
+</pre>
+</div></div>
+
+<p>You can then refer to this bean, using #beanId in your Camel route as shown:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;route&gt;</span>
+  <span class="code-tag">&lt;from uri=<span class="code-quote">"imaps://mymailseerver?username=foo&amp;password=secret&amp;searchTerm=#mySearchTerm"</span>/&gt;</span>
+  <span class="code-tag">&lt;to uri=<span class="code-quote">"bean:myBean"</span>/&gt;</span>
+<span class="code-tag">&lt;/route&gt;</span>
+</pre>
+</div></div>
+
+<p>In Java there is a builder class to build compound <tt>SearchTerm}}s using the {{org.apache.camel.component.mail.SearchTermBuilder</tt> class.<br clear="none">
+This allows you to build complex terms such as:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-java">
+<span class="code-comment">// we just want the unseen mails which is not spam
+</span>SearchTermBuilder builder = <span class="code-keyword">new</span> SearchTermBuilder();
+
+builder.unseen().body(Op.not, <span class="code-quote">"Spam"</span>).subject(Op.not, <span class="code-quote">"Spam"</span>)
+  <span class="code-comment">// which was sent from either foo or bar
+</span>  .from(<span class="code-quote">"foo@somewhere.com"</span>).from(Op.or, <span class="code-quote">"bar@somewhere.com"</span>);
+  <span class="code-comment">// .. and we could <span class="code-keyword">continue</span> building the terms
+</span>
+SearchTerm term = builder.build();
+</pre>
+</div></div>
+
 <h3><a shape="rect" name="BookInOnePage-SeeAlso"></a>See Also</h3>
 <ul><li><a shape="rect" href="configuring-camel.html" title="Configuring Camel">Configuring Camel</a></li><li><a shape="rect" href="component.html" title="Component">Component</a></li><li><a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a></li><li><a shape="rect" href="getting-started.html" title="Getting Started">Getting Started</a></li></ul>
 

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/camel-2110-release.html
==============================================================================
--- websites/production/camel/content/camel-2110-release.html (original)
+++ websites/production/camel/content/camel-2110-release.html Tue Nov 13 18:22:26 2012
@@ -84,7 +84,7 @@
 
 <p>Welcome to the 2.11.0 release with approximately XXX issues resolved - including new features, improvements, and bug fixes, such as: </p>
 
-<ul><li>Added <a shape="rect" href="binding.html" title="Binding">Binding</a> support, so it is easy to combine things like a <a shape="rect" href="data-format.html" title="Data Format">Data Format</a> to an <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> for easier composition of routes.</li><li>Added support for SOAP 1.2 in <a shape="rect" href="soap.html" title="SOAP">SOAP</a> data format.</li><li><a shape="rect" href="cache.html" title="Cache">Cache</a> operation for add/update now supports expiry headers to control time to live/idle/eternal.</li><li>Added <tt>allowNullBody</tt> option to <a shape="rect" href="jms.html" title="JMS">JMS</a> to configure whether sending messages with no body is allowed.</li><li>Added <tt>connectOnStartup</tt> option to <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> to allow to connect on demand, to avoid having Hadoop block for long time connecting to the HDFS cluster, as it has a hardcoded 15 minute retry mechan
 ism.</li><li>Added support for daily and weekly trends to <a shape="rect" href="twitter.html" title="Twitter">Twitter</a> component.</li><li>The <a shape="rect" href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> now generates projects without any license headers.</li><li>Added 'rejectOld' option to the <a shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> to prevent out of order messages from being delivered after capacity/timeout events occur</li><li>Further optimized <a shape="rect" href="xpath.html" title="XPath">XPath</a> under concurrent load, and as well ensured resources are cleaned up eagerly</li><li>Added options <tt>allowNullBody</tt> and <tt>readLockMinLength</tt> to the <a shape="rect" href="file2.html" title="File2">File</a> and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components.</li><li>Made <tt>changed</tt> read lock strategy on <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> g
 o faster (eg when the FTP server has a lot of files in the directory) if you enable the <tt>fastExistsCheck=true</tt> option as well. Notice that some FTP server may not support this.</li><li><a shape="rect" href="hl7.html" title="HL7">HL7</a> moves to HAPI 2.0 and supports using a dedicated Parser instance in the <a shape="rect" href="hl7.html" title="HL7">HL7</a> MLLP codec and DataFormat. Added "Terser" language and expression to be able to extract fields from a parsed message. <a shape="rect" href="hl7.html" title="HL7">HL7</a> now uses Apache Mina 2.x.</li><li>Add an option <tt>HttpMethodRestrict</tt> to restrict HTTP method in <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> and <a shape="rect" href="servlet.html" title="SERVLET">SERVLET</a></li><li>Add support for selection of <a shape="rect" href="direct-vm.html" title="Direct-VM">Direct-VM</a> consumers by using ant-like path expression.</li><li>The <a shape="rect" href="pojo-producing.html" title="POJO Pro
 ducing">POJO Producing</a>, and <a shape="rect" href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a> with @Consume, @Produce, @EndpointInject now supports a new {{property} attribute to get the endpoint configuration from a bean property (eg using a getter method); this allows you to configure this on the bean using conventional bean configuration.</li><li>Testing with <tt>camel-test-blueprint</tt> on Windows no longer tries to cleanup after testing taking up 5 seconds and logging WARNs.</li><li>The <a shape="rect" href="file2.html" title="File2">File</a>, and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components now support <tt>fileExist=Move</tt> option to move any existing files before writing a file.</li><li>Added option <tt>loadStatisticsEnabled</tt> on <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel JMX</a> to allow to disable load statistics if not needed (avoids a background thread being in use, to calculate the load stats).</
 li><li>Enabled "lazy connections" for <a shape="rect" href="xmpp.html" title="XMPP">XMPP</a> providers via the <tt>testConnectionOnStartup</tt> option</li><li>Added a connection monitor to detect and fix dropped <a shape="rect" href="xmpp.html" title="XMPP">XMPP</a> consumer connections at configurable <tt>connectionPollDelay</tt> intervals</li><li>Added an <tt>org.apache.camel.builder.ExchangeBuilder</tt> to build the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> using a builder pattern.</li><li>The <a shape="rect" href="camel-run-maven-goal.html" title="Camel Run Maven Goal">Camel Run Maven Goal</a> can now run <a shape="rect" href="cdi.html" title="CDI">CDI</a> applications.</li><li>The Camel <a shape="rect" href="cdi.html" title="CDI">CDI</a> component has improved a lot.</li><li>Added option <tt>allowRedeliveryWhileStopping</tt> to <a shape="rect" href="dead-letter-channel.html" title="Dead Letter Channel">error handlers</a> to control if redelivery
  is allowed during stopping/shutting down Camel or the route(s). Turning this option <tt>false</tt> allows to stop quicker by rejecting redelivery attempts.</li><li>Added support for specifying user info in Camel <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> urls, which contains the @ sign; now the @ sign can be given as is; without being encoded to %40.</li><li>Added robust connection support for <a shape="rect" href="jmx.html" title="JMX">JMX</a>. Optional <tt>testConnectionOnStartup</tt> allows a JMX consumer to attach to a JMX server that becomes available <em>after</em> the JMX endpoint starts; <tt>reconnectOnConnectionFailure</tt> enables re-connection of failed JMX connections.</li><li><a shape="rect" href="jaxb.html" title="JAXB">JAXB</a> and <a shape="rect" href="soap.html" title="SOAP">SOAP</a> data format now supports controlling namespace prefix mappings when marshalling (eg to avoid prefixes such as ns2, ns3, ns4 etc.)</li><li>Added support 
 for using raw uris when <a shape="rect" href="component.html" title="Component">Component</a>s create <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a>s. This gives component writers full power in case their component has special syntax/notation for endpoint uri configurations.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s configured with custom <tt>AggregationStrategy</tt> will now strict check the custom strategy exists in the <a shape="rect" href="registry.html" title="Registry">Registry</a> and no longer fallback and use a default strategy if not.</li><li>Camel now logs on shutdown if any thread pools hasn't been properly shutdown, and will shutdown them as fail safe (can only be done for the thread pools Camel manages).</li><li>The buffer size of <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a> is now configurable.</li><li>Improved startup performance.</li><li>Added <a shape="rect" href="jms.html" title
 ="JMS">JMS</a> URI option <tt>messageListenerContainerFactoryRef</tt> which allows you to specify a <tt>MessageListenerContainerFactory</tt> to determine what <tt>org.springframework.jms.listener.AbstractMessageListenerContainer</tt> to use to consume messages.</li><li><a shape="rect" href="mqtt.html" title="MQTT">MQTT</a> producer now leverages the <a shape="rect" href="asynchronous-routing-engine.html" title="Asynchronous Routing Engine">Asynchronous Routing Engine</a></li><li>The <a shape="rect" href="netty.html" title="Netty">Netty</a> producer scales up and down much better by leveraging a channel pool.</li><li>Added new <a shape="rect" href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> for creating Camel and Groovy applications.</li><li>Camel now injects <tt>CamelContext</tt> on <tt>Language</tt> and <tt>DataFormat</tt> that implements <tt>CamelContextAware</tt></li><li>Thread pools in Camel with <tt>maximumQueueSize</tt> of 0 
 or negative will now not use a worker queue but do direct hand-over to thread instead.</li><li><a shape="rect" href="simple.html" title="Simple">Simple</a> unary operators for inc and dec must now have function on left hand side, to be parsed as unary function. Otherwise its now regarded as literal.</li><li>Custom assigned id's on Camel <a shape="rect" href="routes.html" title="Routes">Routes</a> is now validated on starting the routes, that they must be unique within the same CamelContext.</li><li>Added <tt>AbstractListAggregationStrategy</tt> abstract class to make it easier to <a shape="rect" href="aggregator2.html" title="Aggregator2">aggregate</a> into a List&lt;V&gt; using a custom <tt>AggregationStrategy</tt>.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s which support using <tt>AggregationStrategy</tt> now control the lifecycle of the strategy; allowing end users to do custom logic in the start/stop methods of their strategy implementation.</li><li>Add
 ed option <tt>includeSentJMSMessageID</tt> to <a shape="rect" href="jms.html" title="JMS">JMS</a> to allow to enrich Camel Message with the actual JMSMessageID for the sent message. Can be used by end users for logging purpose etc.</li><li>Added option <tt>allowShortLines</tt> and <tt>ignoreExtraColumns</tt> to <a shape="rect" href="flatpack-dataformat.html" title="Flatpack DataFormat">Flatpack data format</a>.</li></ul>
+<ul><li>Added <a shape="rect" href="binding.html" title="Binding">Binding</a> support, so it is easy to combine things like a <a shape="rect" href="data-format.html" title="Data Format">Data Format</a> to an <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> for easier composition of routes.</li><li>Added support for SOAP 1.2 in <a shape="rect" href="soap.html" title="SOAP">SOAP</a> data format.</li><li><a shape="rect" href="cache.html" title="Cache">Cache</a> operation for add/update now supports expiry headers to control time to live/idle/eternal.</li><li>Added <tt>allowNullBody</tt> option to <a shape="rect" href="jms.html" title="JMS">JMS</a> to configure whether sending messages with no body is allowed.</li><li>Added <tt>connectOnStartup</tt> option to <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> to allow to connect on demand, to avoid having Hadoop block for long time connecting to the HDFS cluster, as it has a hardcoded 15 minute retry mechan
 ism.</li><li>Added support for daily and weekly trends to <a shape="rect" href="twitter.html" title="Twitter">Twitter</a> component.</li><li>The <a shape="rect" href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> now generates projects without any license headers.</li><li>Added 'rejectOld' option to the <a shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> to prevent out of order messages from being delivered after capacity/timeout events occur</li><li>Further optimized <a shape="rect" href="xpath.html" title="XPath">XPath</a> under concurrent load, and as well ensured resources are cleaned up eagerly</li><li>Added options <tt>allowNullBody</tt> and <tt>readLockMinLength</tt> to the <a shape="rect" href="file2.html" title="File2">File</a> and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components.</li><li>Made <tt>changed</tt> read lock strategy on <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> g
 o faster (eg when the FTP server has a lot of files in the directory) if you enable the <tt>fastExistsCheck=true</tt> option as well. Notice that some FTP server may not support this.</li><li><a shape="rect" href="hl7.html" title="HL7">HL7</a> moves to HAPI 2.0 and supports using a dedicated Parser instance in the <a shape="rect" href="hl7.html" title="HL7">HL7</a> MLLP codec and DataFormat. Added "Terser" language and expression to be able to extract fields from a parsed message. <a shape="rect" href="hl7.html" title="HL7">HL7</a> now uses Apache Mina 2.x.</li><li>Add an option <tt>HttpMethodRestrict</tt> to restrict HTTP method in <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> and <a shape="rect" href="servlet.html" title="SERVLET">SERVLET</a></li><li>Add support for selection of <a shape="rect" href="direct-vm.html" title="Direct-VM">Direct-VM</a> consumers by using ant-like path expression.</li><li>The <a shape="rect" href="pojo-producing.html" title="POJO Pro
 ducing">POJO Producing</a>, and <a shape="rect" href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a> with @Consume, @Produce, @EndpointInject now supports a new {{property} attribute to get the endpoint configuration from a bean property (eg using a getter method); this allows you to configure this on the bean using conventional bean configuration.</li><li>Testing with <tt>camel-test-blueprint</tt> on Windows no longer tries to cleanup after testing taking up 5 seconds and logging WARNs.</li><li>The <a shape="rect" href="file2.html" title="File2">File</a>, and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components now support <tt>fileExist=Move</tt> option to move any existing files before writing a file.</li><li>Added option <tt>loadStatisticsEnabled</tt> on <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel JMX</a> to allow to disable load statistics if not needed (avoids a background thread being in use, to calculate the load stats).</
 li><li>Enabled "lazy connections" for <a shape="rect" href="xmpp.html" title="XMPP">XMPP</a> providers via the <tt>testConnectionOnStartup</tt> option</li><li>Added a connection monitor to detect and fix dropped <a shape="rect" href="xmpp.html" title="XMPP">XMPP</a> consumer connections at configurable <tt>connectionPollDelay</tt> intervals</li><li>Added an <tt>org.apache.camel.builder.ExchangeBuilder</tt> to build the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> using a builder pattern.</li><li>The <a shape="rect" href="camel-run-maven-goal.html" title="Camel Run Maven Goal">Camel Run Maven Goal</a> can now run <a shape="rect" href="cdi.html" title="CDI">CDI</a> applications.</li><li>The Camel <a shape="rect" href="cdi.html" title="CDI">CDI</a> component has improved a lot.</li><li>Added option <tt>allowRedeliveryWhileStopping</tt> to <a shape="rect" href="dead-letter-channel.html" title="Dead Letter Channel">error handlers</a> to control if redelivery
  is allowed during stopping/shutting down Camel or the route(s). Turning this option <tt>false</tt> allows to stop quicker by rejecting redelivery attempts.</li><li>Added support for specifying user info in Camel <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> urls, which contains the @ sign; now the @ sign can be given as is; without being encoded to %40.</li><li>Added robust connection support for <a shape="rect" href="jmx.html" title="JMX">JMX</a>. Optional <tt>testConnectionOnStartup</tt> allows a JMX consumer to attach to a JMX server that becomes available <em>after</em> the JMX endpoint starts; <tt>reconnectOnConnectionFailure</tt> enables re-connection of failed JMX connections.</li><li><a shape="rect" href="jaxb.html" title="JAXB">JAXB</a> and <a shape="rect" href="soap.html" title="SOAP">SOAP</a> data format now supports controlling namespace prefix mappings when marshalling (eg to avoid prefixes such as ns2, ns3, ns4 etc.)</li><li>Added support 
 for using raw uris when <a shape="rect" href="component.html" title="Component">Component</a>s create <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a>s. This gives component writers full power in case their component has special syntax/notation for endpoint uri configurations.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s configured with custom <tt>AggregationStrategy</tt> will now strict check the custom strategy exists in the <a shape="rect" href="registry.html" title="Registry">Registry</a> and no longer fallback and use a default strategy if not.</li><li>Camel now logs on shutdown if any thread pools hasn't been properly shutdown, and will shutdown them as fail safe (can only be done for the thread pools Camel manages).</li><li>The buffer size of <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a> is now configurable.</li><li>Improved startup performance.</li><li>Added <a shape="rect" href="jms.html" title
 ="JMS">JMS</a> URI option <tt>messageListenerContainerFactoryRef</tt> which allows you to specify a <tt>MessageListenerContainerFactory</tt> to determine what <tt>org.springframework.jms.listener.AbstractMessageListenerContainer</tt> to use to consume messages.</li><li><a shape="rect" href="mqtt.html" title="MQTT">MQTT</a> producer now leverages the <a shape="rect" href="asynchronous-routing-engine.html" title="Asynchronous Routing Engine">Asynchronous Routing Engine</a></li><li>The <a shape="rect" href="netty.html" title="Netty">Netty</a> producer scales up and down much better by leveraging a channel pool.</li><li>Added new <a shape="rect" href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> for creating Camel and Groovy applications.</li><li>Camel now injects <tt>CamelContext</tt> on <tt>Language</tt> and <tt>DataFormat</tt> that implements <tt>CamelContextAware</tt></li><li>Thread pools in Camel with <tt>maximumQueueSize</tt> of 0 
 or negative will now not use a worker queue but do direct hand-over to thread instead.</li><li><a shape="rect" href="simple.html" title="Simple">Simple</a> unary operators for inc and dec must now have function on left hand side, to be parsed as unary function. Otherwise its now regarded as literal.</li><li>Custom assigned id's on Camel <a shape="rect" href="routes.html" title="Routes">Routes</a> is now validated on starting the routes, that they must be unique within the same CamelContext.</li><li>Added <tt>AbstractListAggregationStrategy</tt> abstract class to make it easier to <a shape="rect" href="aggregator2.html" title="Aggregator2">aggregate</a> into a List&lt;V&gt; using a custom <tt>AggregationStrategy</tt>.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s which support using <tt>AggregationStrategy</tt> now control the lifecycle of the strategy; allowing end users to do custom logic in the start/stop methods of their strategy implementation.</li><li>Add
 ed option <tt>includeSentJMSMessageID</tt> to <a shape="rect" href="jms.html" title="JMS">JMS</a> to allow to enrich Camel Message with the actual JMSMessageID for the sent message. Can be used by end users for logging purpose etc.</li><li>Added option <tt>allowShortLines</tt> and <tt>ignoreExtraColumns</tt> to <a shape="rect" href="flatpack-dataformat.html" title="Flatpack DataFormat">Flatpack data format</a>.</li><li><a shape="rect" href="mail.html" title="Mail">Mail</a> consumer now supports using search terms to filter mails by terms such as subject, from, body, sent date etc.</li></ul>
 
 
 <h3><a shape="rect" name="Camel2.11.0Release-Fixedissues"></a>Fixed issues</h3>