Author: buildbot
Date: Wed Jul 10 10:19:02 2013
New Revision: 869019
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/book-pattern-appendix.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/logeip.html
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 Jul 10 10:19:02
2013
@@ -21406,6 +21406,7 @@ from("direct:start").log("Processing ${i
<div class="panelMacro"><table class="infoMacro"><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/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Difference between log in the DSL and <a shape="rect"
href="log.html" title="Log">Log</a> component</b><br clear="none">The
<tt>log</tt> DSL is much lighter and meant for logging human logs such as
<tt>Starting to do ...</tt> etc. It can only log a message based on the <a
shape="rect" href="simple.html" title="Simple">Simple</a> language. On the
other hand <a shape="rect" href="log.html" title="Log">Log</a> component is a
full fledged component which involves using endpoints and etc. The <a
shape="rect" href="log.html" title="Log">Log</a> component is meant for logging
the Message itself and you have many URI options to control what you would like
to be logged.</td></tr></table></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>Logging message body with streamed messages</b><br
clear="none">If the message body is stream based, then logging the message
body, may cause the message body to be <em>empty</em> afterwards. See this <a
shape="rect" href="why-is-my-message-body-empty.html" title="Why is my message
body empty?">FAQ</a>. For streamed messages you can use <a shape="rect"
href="stream-caching.html" title="Stream caching">Stream caching</a> to allow
logging the message body and be able to read the message body afterwards
again.</td></tr></table></div>
<p>The log DSL have overloaded methods to set the logging level and/or name as
well.</p>
Modified: websites/production/camel/content/book-pattern-appendix.html
==============================================================================
--- websites/production/camel/content/book-pattern-appendix.html (original)
+++ websites/production/camel/content/book-pattern-appendix.html Wed Jul 10
10:19:02 2013
@@ -6177,6 +6177,7 @@ from("direct:start").log("Processing ${i
<div class="panelMacro"><table class="infoMacro"><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/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Difference between log in the DSL and <a shape="rect"
href="log.html" title="Log">Log</a> component</b><br clear="none">The
<tt>log</tt> DSL is much lighter and meant for logging human logs such as
<tt>Starting to do ...</tt> etc. It can only log a message based on the <a
shape="rect" href="simple.html" title="Simple">Simple</a> language. On the
other hand <a shape="rect" href="log.html" title="Log">Log</a> component is a
full fledged component which involves using endpoints and etc. The <a
shape="rect" href="log.html" title="Log">Log</a> component is meant for logging
the Message itself and you have many URI options to control what you would like
to be logged.</td></tr></table></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>Logging message body with streamed messages</b><br
clear="none">If the message body is stream based, then logging the message
body, may cause the message body to be <em>empty</em> afterwards. See this <a
shape="rect" href="why-is-my-message-body-empty.html" title="Why is my message
body empty?">FAQ</a>. For streamed messages you can use <a shape="rect"
href="stream-caching.html" title="Stream caching">Stream caching</a> to allow
logging the message body and be able to read the message body afterwards
again.</td></tr></table></div>
<p>The log DSL have overloaded methods to set the logging level and/or name as
well.</p>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/logeip.html
==============================================================================
--- websites/production/camel/content/logeip.html (original)
+++ websites/production/camel/content/logeip.html Wed Jul 10 10:19:02 2013
@@ -108,6 +108,7 @@ from("direct:start").log("Processing ${i
<div class="panelMacro"><table class="infoMacro"><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/information.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1"
rowspan="1"><b>Difference between log in the DSL and <a shape="rect"
href="log.html" title="Log">Log</a> component</b><br clear="none">The
<tt>log</tt> DSL is much lighter and meant for logging human logs such as
<tt>Starting to do ...</tt> etc. It can only log a message based on the <a
shape="rect" href="simple.html" title="Simple">Simple</a> language. On the
other hand <a shape="rect" href="log.html" title="Log">Log</a> component is a
full fledged component which involves using endpoints and etc. The <a
shape="rect" href="log.html" title="Log">Log</a> component is meant for logging
the Message itself and you have many URI options to control what you would like
to be logged.</td></tr></table></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>Logging message body with streamed messages</b><br
clear="none">If the message body is stream based, then logging the message
body, may cause the message body to be <em>empty</em> afterwards. See this <a
shape="rect" href="why-is-my-message-body-empty.html" title="Why is my message
body empty?">FAQ</a>. For streamed messages you can use <a shape="rect"
href="stream-caching.html" title="Stream caching">Stream caching</a> to allow
logging the message body and be able to read the message body afterwards
again.</td></tr></table></div>
<p>The log DSL have overloaded methods to set the logging level and/or name as
well.</p>
![https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"){kind=link}
![https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"){kind=link}