Author: buildbot
Date: Wed Apr 27 08:19:52 2016
New Revision: 986800
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 Apr 27 08:19:52
2016
@@ -3612,11 +3612,11 @@ The tutorial has been designed in two pa
While not actual tutorials you might find working through the source of the
various <a shape="rect" href="examples.html">Examples</a> useful.</li></ul>
<h2 id="BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring
Remoting with JMS</h2><p> </p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Thanks</p><span
class="aui-icon aui-icon-small aui-iconfont-info
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>This tutorial was kindly donated
to Apache Camel by Martin Gilday.</p></div></div><h2
id="BookInOnePage-Preface">Preface</h2><p>This tutorial aims to guide the
reader through the stages of creating a project which uses Camel to facilitate
the routing of messages from a JMS queue to a <a shape="rect"
class="external-link" href="http://www.springramework.org";
rel="nofollow">Spring</a> service. The route works in a synchronous fashion
returning a response to the client.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1461698341526 {padding: 0px;}
-div.rbtoc1461698341526 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1461698341526 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1461745109691 {padding: 0px;}
+div.rbtoc1461745109691 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1461745109691 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1461698341526">
+/*]]>*/</style></p><div class="toc-macro rbtoc1461745109691">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring
Remoting with JMS</a></li><li><a shape="rect"
href="#BookInOnePage-Preface">Preface</a></li><li><a shape="rect"
href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect"
href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect"
href="#BookInOnePage-About">About</a></li><li><a shape="rect"
href="#BookInOnePage-CreatetheCamelProject">Create the Camel Project</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-UpdatethePOMwithDependencies">Update the POM with
Dependencies</a></li></ul>
</li><li><a shape="rect" href="#BookInOnePage-WritingtheServer">Writing the
Server</a>
@@ -5731,11 +5731,11 @@ So we completed the last piece in the pi
<p>This example has been removed from <strong>Camel 2.9</strong> onwards.
Apache Axis 1.4 is a very old and unsupported framework. We encourage users to
use <a shape="rect" href="cxf.html">CXF</a> instead of Axis.</p></div></div>
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1461698342375 {padding: 0px;}
-div.rbtoc1461698342375 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1461698342375 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1461745109963 {padding: 0px;}
+div.rbtoc1461745109963 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1461745109963 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1461698342375">
+/*]]>*/</style><div class="toc-macro rbtoc1461745109963">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis
1.4 with Apache Camel</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect"
href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect"
href="#BookInOnePage-Introduction">Introduction</a></li><li><a shape="rect"
href="#BookInOnePage-SettinguptheprojecttorunAxis">Setting up the project to
run Axis</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-Maven2">Maven 2</a></li><li><a shape="rect"
href="#BookInOnePage-wsdl">wsdl</a></li><li><a shape="rect"
href="#BookInOnePage-ConfiguringAxis">Configuring Axis</a></li><li><a
shape="rect" href="#BookInOnePage-RunningtheExample">Running the
Example</a></li></ul>
@@ -16146,10 +16146,10 @@ from("direct:tap")
</div></div><h3
id="BookInOnePage-UsingonPreparetoexecutecustomlogicwhenpreparingmessages.3">Using
onPrepare to execute custom logic when preparing
messages</h3><p><strong>Available as of Camel 2.8</strong></p><p>See details at
<a shape="rect" href="multicast.html">Multicast</a></p><p></p><h4
id="BookInOnePage-UsingThisPattern.47">Using This Pattern</h4>
<p>If you would like to use this EIP Pattern then please read the <a
shape="rect" href="getting-started.html">Getting Started</a>, you may also find
the <a shape="rect" href="architecture.html">Architecture</a> useful
particularly the description of <a shape="rect"
href="endpoint.html">Endpoint</a> and <a shape="rect"
href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect"
href="examples.html">Examples</a> first before trying this pattern out.</p>
-<h2 id="BookInOnePage-Log">Log</h2><p>How can I log processing a <a
shape="rect" href="message.html">Message</a>?</p><p>Camel provides many ways to
log processing a message. Here is just some examples:</p><ul
class="alternate"><li>You can use the <a shape="rect" href="log.html">Log</a>
component which logs the Message content.</li><li>You can use the <a
shape="rect" href="tracer.html">Tracer</a> which trace logs message
flow.</li><li>You can also use a <a shape="rect"
href="processor.html">Processor</a> or <a shape="rect"
href="bean.html">Bean</a> and log from Java code.</li><li>You can use the
<code>log</code> DSL.</li></ul><h3 id="BookInOnePage-UsinglogDSL">Using log
DSL</h3><p>And in <strong>Camel 2.2</strong> you can use the <code>log</code>
DSL which allows you to use <a shape="rect" href="simple.html">Simple</a>
language to construct a dynamic message which gets logged.<br clear="none"> For
example you can do</p><div class="code panel pdl" style="border-width:
1px;"><div class
="codeContent panelContent pdl">
+<h2 id="BookInOnePage-Log">Log</h2><p>How can I log the processing of a <a
shape="rect" href="message.html">Message</a>?</p><p>Camel provides many ways to
log the fact that you are processing a message. Here are just a few
examples:</p><ul class="alternate"><li>You can use the <a shape="rect"
href="log.html">Log</a> component which logs the Message content.</li><li>You
can use the <a shape="rect" href="tracer.html">Tracer</a> which trace logs
message flow.</li><li>You can also use a <a shape="rect"
href="processor.html">Processor</a> or <a shape="rect"
href="bean.html">Bean</a> and log from Java code.</li><li>You can use the
<code>log</code> DSL.</li></ul><h3 id="BookInOnePage-UsinglogDSL">Using log
DSL</h3><p>In <strong>Camel 2.2</strong> you can use the <code>log</code> DSL
which allows you to use <a shape="rect" href="simple.html">Simple</a> language
to construct a dynamic message which gets logged.<br clear="none"> For example
you can do</p><div class="code panel pdl" style="bor
der-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("direct:start").log("Processing
${id}").to("bean:foo");
]]></script>
-</div></div><p>Which will construct a String message at runtime using the <a
shape="rect" href="simple.html">Simple</a> language. The log message will by
logged at <code>INFO</code> level using the route id as the log name. By
default a route is named <code>route-1</code>, <code>route-2</code> etc. But
you can use the <code>routeId("myCoolRoute")</code> to set a route name of
choice.</p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Difference between
log in the DSL and [Log] component</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>The <code>log</code> DSL is much
lighter and meant for logging human logs such as <code>Starting to do
...</code> etc. It can only log a message based on the <a shape="rect"
href="simple.html">Simple</a> language. On the other hand <a shape="rect"
href="log.html">Log</a> component is a full fledged com
ponent which involves using endpoints and etc. The <a shape="rect"
href="log.html">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.</p></div></div><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Using Logger
instance from the the Registry</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>As of <strong>Camel
2.12.4/2.13.1</strong>, if no logger name or logger instance is passed to log
DSL, there's a Registry lookup performed to find single instance
of <code>org.slf4j.Logger</code>. If such instance is found, it is used
instead of creating a new logger instance. If more instances are found, the
behavior defaults to creating a new instance of logger.</p></div></div><div
class="confluence-information-macro confluence-information-macro-tip"><p class="
title">Logging message body with streamed messages</p><span class="aui-icon
aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>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">FAQ</a>. For streamed messages you can
use <a shape="rect" href="stream-caching.html">Stream caching</a> to allow
logging the message body and be able to read the message body afterwards
again.</p></div></div><p>The log DSL have overloaded methods to set the logging
level and/or name as well.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Which will construct a String message at runtime using the <a
shape="rect" href="simple.html">Simple</a> language. The log message will by
logged at <code>INFO</code> level using the route id as the log name. By
default a route is named <code>route-1</code>, <code>route-2</code> etc. But
you can use the <code>routeId("myCoolRoute")</code> to set a route name of
choice.</p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Difference between
log in the DSL and [Log] component</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>The <code>log</code> DSL is much
lighter and meant for logging human logs such as <code>Starting to do
...</code> etc. It can only log a message based on the <a shape="rect"
href="simple.html">Simple</a> language. On the other hand <a shape="rect"
href="log.html">Log</a> component is a full fledged com
ponent which involves using endpoints and etc. The <a shape="rect"
href="log.html">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.</p></div></div><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Using Logger
instance from the the Registry</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>As of <strong>Camel
2.12.4/2.13.1</strong>, if no logger name or logger instance is passed to log
DSL, there is a Registry lookup performed to find single instance
of <code>org.slf4j.Logger</code>. If such an instance is found, it is used
instead of creating a new logger instance. If more instances are found, the
behavior defaults to creating a new instance of logger.</p></div></div><div
class="confluence-information-macro confluence-information-macro-tip"><p cla
ss="title">Logging message body with streamed messages</p><span
class="aui-icon aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>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">FAQ</a>. For streamed messages you can
use <a shape="rect" href="stream-caching.html">Stream caching</a> to allow
logging the message body and be able to read the message body afterwards
again.</p></div></div><p>The log DSL have overloaded methods to set the logging
level and/or name as well.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("direct:start").log(LoggingLevel.DEBUG,
"Processing ${id}").to("bean:foo");
]]></script>
</div></div><p>and to set a logger name</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -16160,7 +16160,7 @@ from("direct:tap")
</div></div><p>For example you can use this to log the file name being
processed if you consume files.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("file://target/files").log(LoggingLevel.DEBUG,
"Processing file ${file:name}").to("bean:foo");
]]></script>
-</div></div><h4 id="BookInOnePage-UsinglogDSLfromSpring">Using log DSL from
Spring</h4><p>In Spring DSL its also easy to use log DSL as shown
below:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><h4 id="BookInOnePage-UsinglogDSLfromSpring">Using log DSL from
Spring</h4><p>In Spring DSL it is also easy to use log DSL as shown
below:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <route id="foo">
<from uri="direct:foo"/>
<log message="Got ${body}"/>
@@ -16185,7 +16185,7 @@ from("direct:tap")
<to uri="mock:baz"/>
</route>
]]></script>
-</div></div><h4 id="BookInOnePage-Configuringlognameglobally">Configuring log
name globally</h4><p><strong>Available as of Camel 2.17</strong></p><p>By
default the log name is the route id. If you want to use a different log name,
you would need to configure the logName option. However if you have many log's
and you want all of them to use the same log name, then you would need to set
that logName option on all of them.</p><p>With Camel 2.17 onwards you can
configure a global log name that is used instead of the route id, eg</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><h4 id="BookInOnePage-Configuringlognameglobally">Configuring log
name globally</h4><p><strong>Available as of Camel 2.17</strong></p><p>By
default the log name is the route id. If you want to use a different log name,
you would need to configure the logName option. However if you have many logs
and you want all of them to use the same log name, then you would need to set
that logName option on all of them.</p><p>With Camel 2.17 onwards you can
configure a global log name that is used instead of the route id, eg</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[CamelContext context = ...
context.getProperties().put(Exchange.LOG_EIP_NAME,
"com.foo.myapp");]]></script>
</div></div><p>And in XML</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
@@ -17132,11 +17132,11 @@ template.send("direct:alias-verify&
]]></script>
</div></div><p></p><h3 id="BookInOnePage-SeeAlso.28">See Also</h3>
<ul><li><a shape="rect" href="configuring-camel.html">Configuring
Camel</a></li><li><a shape="rect"
href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect"
href="getting-started.html">Getting Started</a></li></ul><ul><li><a
shape="rect" href="crypto.html">Crypto</a> Crypto is also available as a <a
shape="rect" href="data-format.html">Data Format</a></li></ul> <h2
id="BookInOnePage-CXFComponent">CXF Component</h2><div
class="confluence-information-macro confluence-information-macro-note"><span
class="aui-icon aui-icon-small aui-iconfont-warning
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When using CXF as a consumer, the
<a shape="rect" href="cxf-bean-component.html">CXF Bean Component</a> allows
you to factor out how message payloads are received from their processing as a
RESTful or SOAP web service. This has the potential of using a multitude of
transports to consume web
services. The bean component's configuration is also simpler and provides the
fastest method to implement web services using Camel and
CXF.</p></div></div><div class="confluence-information-macro
confluence-information-macro-tip"><span class="aui-icon aui-icon-small
aui-iconfont-approve confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When using CXF in streaming modes
(see DataFormat option), then also read about <a shape="rect"
href="stream-caching.html">Stream caching</a>.</p></div></div><p>The
<strong>cxf:</strong> component provides integration with <a shape="rect"
href="http://cxf.apache.org";>Apache CXF</a> for connecting to JAX-WS services
hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1461698401320 {padding: 0px;}
-div.rbtoc1461698401320 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1461698401320 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1461745111745 {padding: 0px;}
+div.rbtoc1461745111745 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1461745111745 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1461698401320">
+/*]]>*/</style></p><div class="toc-macro rbtoc1461745111745">
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-CXFComponent">CXF Component</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-URIformat">URI format</a></li><li><a shape="rect"
href="#BookInOnePage-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#BookInOnePage-Thedescriptionsofthedataformats">The descriptions of the
dataformats</a>
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 Apr 27
08:19:52 2016
@@ -4606,10 +4606,10 @@ from("direct:tap")
</div></div><h3
id="BookPatternAppendix-UsingonPreparetoexecutecustomlogicwhenpreparingmessages.3">Using
onPrepare to execute custom logic when preparing
messages</h3><p><strong>Available as of Camel 2.8</strong></p><p>See details at
<a shape="rect" href="multicast.html">Multicast</a></p><p></p><h4
id="BookPatternAppendix-UsingThisPattern.47">Using This Pattern</h4>
<p>If you would like to use this EIP Pattern then please read the <a
shape="rect" href="getting-started.html">Getting Started</a>, you may also find
the <a shape="rect" href="architecture.html">Architecture</a> useful
particularly the description of <a shape="rect"
href="endpoint.html">Endpoint</a> and <a shape="rect"
href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect"
href="examples.html">Examples</a> first before trying this pattern out.</p>
-<h2 id="BookPatternAppendix-Log">Log</h2><p>How can I log processing a <a
shape="rect" href="message.html">Message</a>?</p><p>Camel provides many ways to
log processing a message. Here is just some examples:</p><ul
class="alternate"><li>You can use the <a shape="rect" href="log.html">Log</a>
component which logs the Message content.</li><li>You can use the <a
shape="rect" href="tracer.html">Tracer</a> which trace logs message
flow.</li><li>You can also use a <a shape="rect"
href="processor.html">Processor</a> or <a shape="rect"
href="bean.html">Bean</a> and log from Java code.</li><li>You can use the
<code>log</code> DSL.</li></ul><h3 id="BookPatternAppendix-UsinglogDSL">Using
log DSL</h3><p>And in <strong>Camel 2.2</strong> you can use the
<code>log</code> DSL which allows you to use <a shape="rect"
href="simple.html">Simple</a> language to construct a dynamic message which
gets logged.<br clear="none"> For example you can do</p><div class="code panel
pdl" style="border-width: 1px;
"><div class="codeContent panelContent pdl">
+<h2 id="BookPatternAppendix-Log">Log</h2><p>How can I log the processing of a
<a shape="rect" href="message.html">Message</a>?</p><p>Camel provides many ways
to log the fact that you are processing a message. Here are just a few
examples:</p><ul class="alternate"><li>You can use the <a shape="rect"
href="log.html">Log</a> component which logs the Message content.</li><li>You
can use the <a shape="rect" href="tracer.html">Tracer</a> which trace logs
message flow.</li><li>You can also use a <a shape="rect"
href="processor.html">Processor</a> or <a shape="rect"
href="bean.html">Bean</a> and log from Java code.</li><li>You can use the
<code>log</code> DSL.</li></ul><h3 id="BookPatternAppendix-UsinglogDSL">Using
log DSL</h3><p>In <strong>Camel 2.2</strong> you can use the <code>log</code>
DSL which allows you to use <a shape="rect" href="simple.html">Simple</a>
language to construct a dynamic message which gets logged.<br clear="none"> For
example you can do</p><div class="code panel pdl
" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("direct:start").log("Processing
${id}").to("bean:foo");
]]></script>
-</div></div><p>Which will construct a String message at runtime using the <a
shape="rect" href="simple.html">Simple</a> language. The log message will by
logged at <code>INFO</code> level using the route id as the log name. By
default a route is named <code>route-1</code>, <code>route-2</code> etc. But
you can use the <code>routeId("myCoolRoute")</code> to set a route name of
choice.</p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Difference between
log in the DSL and [Log] component</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>The <code>log</code> DSL is much
lighter and meant for logging human logs such as <code>Starting to do
...</code> etc. It can only log a message based on the <a shape="rect"
href="simple.html">Simple</a> language. On the other hand <a shape="rect"
href="log.html">Log</a> component is a full fledged com
ponent which involves using endpoints and etc. The <a shape="rect"
href="log.html">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.</p></div></div><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Using Logger
instance from the the Registry</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>As of <strong>Camel
2.12.4/2.13.1</strong>, if no logger name or logger instance is passed to log
DSL, there's a Registry lookup performed to find single instance
of <code>org.slf4j.Logger</code>. If such instance is found, it is used
instead of creating a new logger instance. If more instances are found, the
behavior defaults to creating a new instance of logger.</p></div></div><div
class="confluence-information-macro confluence-information-macro-tip"><p class="
title">Logging message body with streamed messages</p><span class="aui-icon
aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>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">FAQ</a>. For streamed messages you can
use <a shape="rect" href="stream-caching.html">Stream caching</a> to allow
logging the message body and be able to read the message body afterwards
again.</p></div></div><p>The log DSL have overloaded methods to set the logging
level and/or name as well.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Which will construct a String message at runtime using the <a
shape="rect" href="simple.html">Simple</a> language. The log message will by
logged at <code>INFO</code> level using the route id as the log name. By
default a route is named <code>route-1</code>, <code>route-2</code> etc. But
you can use the <code>routeId("myCoolRoute")</code> to set a route name of
choice.</p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Difference between
log in the DSL and [Log] component</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>The <code>log</code> DSL is much
lighter and meant for logging human logs such as <code>Starting to do
...</code> etc. It can only log a message based on the <a shape="rect"
href="simple.html">Simple</a> language. On the other hand <a shape="rect"
href="log.html">Log</a> component is a full fledged com
ponent which involves using endpoints and etc. The <a shape="rect"
href="log.html">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.</p></div></div><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Using Logger
instance from the the Registry</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>As of <strong>Camel
2.12.4/2.13.1</strong>, if no logger name or logger instance is passed to log
DSL, there is a Registry lookup performed to find single instance
of <code>org.slf4j.Logger</code>. If such an instance is found, it is used
instead of creating a new logger instance. If more instances are found, the
behavior defaults to creating a new instance of logger.</p></div></div><div
class="confluence-information-macro confluence-information-macro-tip"><p cla
ss="title">Logging message body with streamed messages</p><span
class="aui-icon aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>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">FAQ</a>. For streamed messages you can
use <a shape="rect" href="stream-caching.html">Stream caching</a> to allow
logging the message body and be able to read the message body afterwards
again.</p></div></div><p>The log DSL have overloaded methods to set the logging
level and/or name as well.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("direct:start").log(LoggingLevel.DEBUG,
"Processing ${id}").to("bean:foo");
]]></script>
</div></div><p>and to set a logger name</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -4620,7 +4620,7 @@ from("direct:tap")
</div></div><p>For example you can use this to log the file name being
processed if you consume files.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("file://target/files").log(LoggingLevel.DEBUG,
"Processing file ${file:name}").to("bean:foo");
]]></script>
-</div></div><h4 id="BookPatternAppendix-UsinglogDSLfromSpring">Using log DSL
from Spring</h4><p>In Spring DSL its also easy to use log DSL as shown
below:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><h4 id="BookPatternAppendix-UsinglogDSLfromSpring">Using log DSL
from Spring</h4><p>In Spring DSL it is also easy to use log DSL as shown
below:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <route id="foo">
<from uri="direct:foo"/>
<log message="Got ${body}"/>
@@ -4645,7 +4645,7 @@ from("direct:tap")
<to uri="mock:baz"/>
</route>
]]></script>
-</div></div><h4
id="BookPatternAppendix-Configuringlognameglobally">Configuring log name
globally</h4><p><strong>Available as of Camel 2.17</strong></p><p>By default
the log name is the route id. If you want to use a different log name, you
would need to configure the logName option. However if you have many log's and
you want all of them to use the same log name, then you would need to set that
logName option on all of them.</p><p>With Camel 2.17 onwards you can configure
a global log name that is used instead of the route id, eg</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4
id="BookPatternAppendix-Configuringlognameglobally">Configuring log name
globally</h4><p><strong>Available as of Camel 2.17</strong></p><p>By default
the log name is the route id. If you want to use a different log name, you
would need to configure the logName option. However if you have many logs and
you want all of them to use the same log name, then you would need to set that
logName option on all of them.</p><p>With Camel 2.17 onwards you can configure
a global log name that is used instead of the route id, eg</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[CamelContext context = ...
context.getProperties().put(Exchange.LOG_EIP_NAME,
"com.foo.myapp");]]></script>
</div></div><p>And in XML</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
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 Apr 27 08:19:52 2016
@@ -85,10 +85,10 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="LogEIP-Log">Log</h2><p>How can I
log processing a <a shape="rect" href="message.html">Message</a>?</p><p>Camel
provides many ways to log processing a message. Here is just some
examples:</p><ul class="alternate"><li>You can use the <a shape="rect"
href="log.html">Log</a> component which logs the Message content.</li><li>You
can use the <a shape="rect" href="tracer.html">Tracer</a> which trace logs
message flow.</li><li>You can also use a <a shape="rect"
href="processor.html">Processor</a> or <a shape="rect"
href="bean.html">Bean</a> and log from Java code.</li><li>You can use the
<code>log</code> DSL.</li></ul><h3 id="LogEIP-UsinglogDSL">Using log
DSL</h3><p>And in <strong>Camel 2.2</strong> you can use the <code>log</code>
DSL which allows you to use <a shape="rect" href="simple.html">Simple</a>
language to construct a dynamic message which gets logged.<br clear="none"> For
example you can do</p><div class="code panel pdl" style="border
-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="LogEIP-Log">Log</h2><p>How can I
log the processing of a <a shape="rect"
href="message.html">Message</a>?</p><p>Camel provides many ways to log the fact
that you are processing a message. Here are just a few examples:</p><ul
class="alternate"><li>You can use the <a shape="rect" href="log.html">Log</a>
component which logs the Message content.</li><li>You can use the <a
shape="rect" href="tracer.html">Tracer</a> which trace logs message
flow.</li><li>You can also use a <a shape="rect"
href="processor.html">Processor</a> or <a shape="rect"
href="bean.html">Bean</a> and log from Java code.</li><li>You can use the
<code>log</code> DSL.</li></ul><h3 id="LogEIP-UsinglogDSL">Using log
DSL</h3><p>In <strong>Camel 2.2</strong> you can use the <code>log</code> DSL
which allows you to use <a shape="rect" href="simple.html">Simple</a> language
to construct a dynamic message which gets logged.<br clear="none"> For example
you can do</p><div class="co
de panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("direct:start").log("Processing
${id}").to("bean:foo");
]]></script>
-</div></div><p>Which will construct a String message at runtime using the <a
shape="rect" href="simple.html">Simple</a> language. The log message will by
logged at <code>INFO</code> level using the route id as the log name. By
default a route is named <code>route-1</code>, <code>route-2</code> etc. But
you can use the <code>routeId("myCoolRoute")</code> to set a route name of
choice.</p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Difference between
log in the DSL and [Log] component</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>The <code>log</code> DSL is much
lighter and meant for logging human logs such as <code>Starting to do
...</code> etc. It can only log a message based on the <a shape="rect"
href="simple.html">Simple</a> language. On the other hand <a shape="rect"
href="log.html">Log</a> component is a full fledged com
ponent which involves using endpoints and etc. The <a shape="rect"
href="log.html">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.</p></div></div><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Using Logger
instance from the the Registry</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>As of <strong>Camel
2.12.4/2.13.1</strong>, if no logger name or logger instance is passed to log
DSL, there's a Registry lookup performed to find single instance
of <code>org.slf4j.Logger</code>. If such instance is found, it is used
instead of creating a new logger instance. If more instances are found, the
behavior defaults to creating a new instance of logger.</p></div></div><div
class="confluence-information-macro confluence-information-macro-tip"><p class="
title">Logging message body with streamed messages</p><span class="aui-icon
aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>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">FAQ</a>. For streamed messages you can
use <a shape="rect" href="stream-caching.html">Stream caching</a> to allow
logging the message body and be able to read the message body afterwards
again.</p></div></div><p>The log DSL have overloaded methods to set the logging
level and/or name as well.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Which will construct a String message at runtime using the <a
shape="rect" href="simple.html">Simple</a> language. The log message will by
logged at <code>INFO</code> level using the route id as the log name. By
default a route is named <code>route-1</code>, <code>route-2</code> etc. But
you can use the <code>routeId("myCoolRoute")</code> to set a route name of
choice.</p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Difference between
log in the DSL and [Log] component</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>The <code>log</code> DSL is much
lighter and meant for logging human logs such as <code>Starting to do
...</code> etc. It can only log a message based on the <a shape="rect"
href="simple.html">Simple</a> language. On the other hand <a shape="rect"
href="log.html">Log</a> component is a full fledged com
ponent which involves using endpoints and etc. The <a shape="rect"
href="log.html">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.</p></div></div><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Using Logger
instance from the the Registry</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>As of <strong>Camel
2.12.4/2.13.1</strong>, if no logger name or logger instance is passed to log
DSL, there is a Registry lookup performed to find single instance
of <code>org.slf4j.Logger</code>. If such an instance is found, it is used
instead of creating a new logger instance. If more instances are found, the
behavior defaults to creating a new instance of logger.</p></div></div><div
class="confluence-information-macro confluence-information-macro-tip"><p cla
ss="title">Logging message body with streamed messages</p><span
class="aui-icon aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>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">FAQ</a>. For streamed messages you can
use <a shape="rect" href="stream-caching.html">Stream caching</a> to allow
logging the message body and be able to read the message body afterwards
again.</p></div></div><p>The log DSL have overloaded methods to set the logging
level and/or name as well.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("direct:start").log(LoggingLevel.DEBUG,
"Processing ${id}").to("bean:foo");
]]></script>
</div></div><p>and to set a logger name</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -99,7 +99,7 @@
</div></div><p>For example you can use this to log the file name being
processed if you consume files.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("file://target/files").log(LoggingLevel.DEBUG,
"Processing file ${file:name}").to("bean:foo");
]]></script>
-</div></div><h4 id="LogEIP-UsinglogDSLfromSpring">Using log DSL from
Spring</h4><p>In Spring DSL its also easy to use log DSL as shown
below:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><h4 id="LogEIP-UsinglogDSLfromSpring">Using log DSL from
Spring</h4><p>In Spring DSL it is also easy to use log DSL as shown
below:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
<script class="brush: xml; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[ <route id="foo">
<from uri="direct:foo"/>
<log message="Got ${body}"/>
@@ -124,7 +124,7 @@
<to uri="mock:baz"/>
</route>
]]></script>
-</div></div><h4 id="LogEIP-Configuringlognameglobally">Configuring log name
globally</h4><p><strong>Available as of Camel 2.17</strong></p><p>By default
the log name is the route id. If you want to use a different log name, you
would need to configure the logName option. However if you have many log's and
you want all of them to use the same log name, then you would need to set that
logName option on all of them.</p><p>With Camel 2.17 onwards you can configure
a global log name that is used instead of the route id, eg</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="LogEIP-Configuringlognameglobally">Configuring log name
globally</h4><p><strong>Available as of Camel 2.17</strong></p><p>By default
the log name is the route id. If you want to use a different log name, you
would need to configure the logName option. However if you have many logs and
you want all of them to use the same log name, then you would need to set that
logName option on all of them.</p><p>With Camel 2.17 onwards you can configure
a global log name that is used instead of the route id, eg</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[CamelContext context = ...
context.getProperties().put(Exchange.LOG_EIP_NAME,
"com.foo.myapp");]]></script>
</div></div><p>And in XML</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
