Author: buildbot
Date: Sat Aug 31 12:20:37 2013
New Revision: 876820
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/log.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 Sat Aug 31
12:20:37 2013
@@ -10743,6 +10743,23 @@ Headers:{breadcrumbId=ID-machine-local-5
<p>NOTE: the <tt>ExchangeFormatter</tt> gets applied to <b>all Log endpoints
within that Camel Context</b>. If you need different ExchangeFormatters for
different endpoints, just instantiate the LogComponent as many times as needed,
and use the relevant bean name as the endpoint prefix.</p>
+<p>From <b>Camel 2.11.2/2.12.1</b> onwards when using a custom log formatter,
you can specify parameters in the log uri, which gets configured on the custom
log formatter. Though when you do that you should define the "logForamtter" as
prototype scoped so its not shared if you have different parameters, eg:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+<bean name="logFormatter" class="com.xyz.MyCustomExchangeFormatter"
scope="prototype"/>
+]]></script>
+</div></div>
+
+<p>And then we can have Camel routes using the log uri with different
options:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+<to uri="log:foo?param1=foo&amp;param2=100"/>
+...
+<to uri="log:bar?param1=bar&amp;param2=200"/>
+]]></script>
+</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 Sat Aug 31 12:20:37
2013
@@ -32462,6 +32462,23 @@ Headers:{breadcrumbId=ID-machine-local-5
<p>NOTE: the <tt>ExchangeFormatter</tt> gets applied to <b>all Log endpoints
within that Camel Context</b>. If you need different ExchangeFormatters for
different endpoints, just instantiate the LogComponent as many times as needed,
and use the relevant bean name as the endpoint prefix.</p>
+<p>From <b>Camel 2.11.2/2.12.1</b> onwards when using a custom log formatter,
you can specify parameters in the log uri, which gets configured on the custom
log formatter. Though when you do that you should define the "logForamtter" as
prototype scoped so its not shared if you have different parameters, eg:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+<bean name="logFormatter" class="com.xyz.MyCustomExchangeFormatter"
scope="prototype"/>
+]]></script>
+</div></div>
+
+<p>And then we can have Camel routes using the log uri with different
options:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+<to uri="log:foo?param1=foo&amp;param2=100"/>
+...
+<to uri="log:bar?param1=bar&amp;param2=200"/>
+]]></script>
+</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/log.html
==============================================================================
--- websites/production/camel/content/log.html (original)
+++ websites/production/camel/content/log.html Sat Aug 31 12:20:37 2013
@@ -241,6 +241,23 @@ Headers:{breadcrumbId=ID-machine-local-5
<p>NOTE: the <tt>ExchangeFormatter</tt> gets applied to <b>all Log endpoints
within that Camel Context</b>. If you need different ExchangeFormatters for
different endpoints, just instantiate the LogComponent as many times as needed,
and use the relevant bean name as the endpoint prefix.</p>
+<p>From <b>Camel 2.11.2/2.12.1</b> onwards when using a custom log formatter,
you can specify parameters in the log uri, which gets configured on the custom
log formatter. Though when you do that you should define the "logForamtter" as
prototype scoped so its not shared if you have different parameters, eg:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+<bean name="logFormatter" class="com.xyz.MyCustomExchangeFormatter"
scope="prototype"/>
+]]></script>
+</div></div>
+
+<p>And then we can have Camel routes using the log uri with different
options:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+<to uri="log:foo?param1=foo&amp;param2=100"/>
+...
+<to uri="log:bar?param1=bar&amp;param2=200"/>
+]]></script>
+</div></div>
+
<h3><a shape="rect" name="Log-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>
