camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r838321 - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache mail.html why-is-my-processor-not-showing-up-in-jconsole.html
Date Wed, 14 Nov 2012 10:22:50 GMT
Author: buildbot
Date: Wed Nov 14 10:22:50 2012
New Revision: 838321

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/mail.html
    websites/production/camel/content/why-is-my-processor-not-showing-up-in-jconsole.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 Wed Nov 14 10:22:50 2012
@@ -10840,8 +10840,29 @@ from(<span class="code-quote">"imaps:<sp
 <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>
 
+<p>Or to get the new unseen emails going 24 hours back in time you can do. Notice the
"now-24h" syntax. See the table below for more details.</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.fromSentDate=now-24h"</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>You can have multiple searchTerm in the endpoint uri configuration. They would then
be combined together using AND operator, eg so both conditions must match. For example to
get the last unseen emails going back 24 hours which has Camel in the mail subject you can
do: </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.subject=Camel&amp;searchTerm.fromSentDate=now-24h"</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>
+
+
 <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>
+<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. The "now" syntax supports an optional offset, that can be specified
as either + or - with a numeric value. For example for last 24 hours, you can use <tt>"now
- 24h"</tt> or without spaces <tt>"now-24h"</tt>. Notice that Camel supports
shorthands for hours, minutes, and seconds. </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.
The "now" syntax supports an optional offset, that can be specified as either + or - with
a numeric value. For example for last 24 hours, you can use <tt>"now - 24h"</tt>
or without spaces <tt
 >"now-24h"</tt>. Notice that Camel supports shorthands for hours, minutes, and seconds.
</td></tr></tbody></table>
 </div>
 </div>
 

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 Wed Nov 14 10:22:50 2012
@@ -31076,8 +31076,29 @@ from(<span class="code-quote">"imaps:<sp
 <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>
 
+<p>Or to get the new unseen emails going 24 hours back in time you can do. Notice the
"now-24h" syntax. See the table below for more details.</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.fromSentDate=now-24h"</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>You can have multiple searchTerm in the endpoint uri configuration. They would then
be combined together using AND operator, eg so both conditions must match. For example to
get the last unseen emails going back 24 hours which has Camel in the mail subject you can
do: </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.subject=Camel&amp;searchTerm.fromSentDate=now-24h"</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>
+
+
 <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>
+<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. The "now" syntax supports an optional offset, that can be specified
as either + or - with a numeric value. For example for last 24 hours, you can use <tt>"now
- 24h"</tt> or without spaces <tt>"now-24h"</tt>. Notice that Camel supports
shorthands for hours, minutes, and seconds. </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.
The "now" syntax supports an optional offset, that can be specified as either + or - with
a numeric value. For example for last 24 hours, you can use <tt>"now - 24h"</tt>
or without spaces <tt
 >"now-24h"</tt>. Notice that Camel supports shorthands for hours, minutes, and seconds.
</td></tr></tbody></table>
 </div>
 </div>
 

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

Modified: websites/production/camel/content/mail.html
==============================================================================
--- websites/production/camel/content/mail.html (original)
+++ websites/production/camel/content/mail.html Wed Nov 14 10:22:50 2012
@@ -447,8 +447,29 @@ from(<span class="code-quote">"imaps:<sp
 <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>
 
+<p>Or to get the new unseen emails going 24 hours back in time you can do. Notice the
"now-24h" syntax. See the table below for more details.</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.fromSentDate=now-24h"</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>You can have multiple searchTerm in the endpoint uri configuration. They would then
be combined together using AND operator, eg so both conditions must match. For example to
get the last unseen emails going back 24 hours which has Camel in the mail subject you can
do: </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.subject=Camel&amp;searchTerm.fromSentDate=now-24h"</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>
+
+
 <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>
+<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. The "now" syntax supports an optional offset, that can be specified
as either + or - with a numeric value. For example for last 24 hours, you can use <tt>"now
- 24h"</tt> or without spaces <tt>"now-24h"</tt>. Notice that Camel supports
shorthands for hours, minutes, and seconds. </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.
The "now" syntax supports an optional offset, that can be specified as either + or - with
a numeric value. For example for last 24 hours, you can use <tt>"now - 24h"</tt>
or without spaces <tt
 >"now-24h"</tt>. Notice that Camel supports shorthands for hours, minutes, and seconds.
</td></tr></tbody></table>
 </div>
 </div>
 

Modified: websites/production/camel/content/why-is-my-processor-not-showing-up-in-jconsole.html
==============================================================================
--- websites/production/camel/content/why-is-my-processor-not-showing-up-in-jconsole.html
(original)
+++ websites/production/camel/content/why-is-my-processor-not-showing-up-in-jconsole.html
Wed Nov 14 10:22:50 2012
@@ -82,7 +82,7 @@
 <p>A processor must implement the <tt>org.apache.camel.Service</tt> to
be managed. Most EIP processors does this.<br clear="none">
 For example the minor ones such as <tt>setHeader</tt> does not and thus is not
visible in JConsole.</p>
 
-<p>From <b>Camel 2.6</b> onwards your custom <tt>Processor</tt>
should use the Spring JMX annotations. Just add <tt>@ManagedResource</tt> to the
class, and the other annotations for the attributes and operations. Then Camel will automatic
use those when the processor is being registered in JMX.</p>
+<p>From <b>Camel 2.6</b> onwards your custom <tt>Processor</tt>
should use the Spring JMX annotations (for <b>Camel 2.9</b> onwards see the tip
box below). Just add <tt>@ManagedResource</tt> to the class, and the other annotations
for the attributes and operations. Then Camel will automatic use those when the processor
is being registered in JMX.</p>
 
 <div class="code panel" style="border-width: 1px;"><div class="codeHeader panelHeader"
style="border-bottom-width: 1px;"><b>Custom processor</b></div><div
class="codeContent panelContent">
 <pre class="code-java">@ManagedResource(description = <span class="code-quote">"My
Managed Component"</span>)
@@ -131,6 +131,7 @@ For example the minor ones such as <tt>s
 </pre>
 </div></div>
 
+<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Camel
2.9 onwards provides Camel's own JMX annotations</b><br clear="none">Notice that
from Camel 2.9 onwards its encouraged to use the <tt>@ManagedResource</tt>, <tt>@ManagedAttribute</tt>
and <tt>@ManagedOperation</tt> from the <tt>org.apache.camel.api.management</tt>
package. This allows your custom code to not depend on Spring JARs anymore.</td></tr></table></div>
 
 <h3><a shape="rect" name="WhyismyprocessornotshowingupinJConsole-Seealso"></a>See
also</h3>
 <ul class="alternate" type="square"><li><a shape="rect" href="camel-jmx.html"
title="Camel JMX">Camel JMX</a></li></ul>



Mime
View raw message