You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2016/01/31 03:24:33 UTC
svn commit: r979059 [3/3] - in /websites/production/camel/content: ./
2016/01/30/ cache/
Modified: websites/production/camel/content/message-history.html
==============================================================================
--- websites/production/camel/content/message-history.html (original)
+++ websites/production/camel/content/message-history.html Sun Jan 31 02:24:33 2016
@@ -85,59 +85,20 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3 id="MessageHistory-MessageHistory">Message History</h3>
-
-<p>The <a shape="rect" class="external-link" href="http://www.eaipatterns.com/MessageHistory.html" rel="nofollow">Message History</a> from the <a shape="rect" href="enterprise-integration-patterns.html">EIP patterns</a> allows for analyzing and debugging the flow of messages in a loosely coupled system.</p>
-
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://www.eaipatterns.com/img/MessageHistory.gif" data-image-src="http://www.eaipatterns.com/img/MessageHistory.gif"></span></p>
-
-<p>Attaching a Message History to the message will provide a list of all applications that the message passed through since its origination.</p>
-
-<p>In Camel you can trace message flow using the <a shape="rect" href="tracer.html">Tracer</a>, or access information using the Java API from <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/UnitOfWork.html">UnitOfWork</a> using the <code>getTracedRouteNodes</code> method. </p>
-
-<p>When Camel sends a message to an endpoint that endpoint information is stored on the <a shape="rect" href="exchange.html">Exchange</a> as a property with the key <code>Exchange.TO_ENDPOINT</code>.<br clear="none">
-This property contains the last known endpoint the <a shape="rect" href="exchange.html">Exchange</a> was sent to (it will be overridden when sending to new endpoint). Alternatively you can trace messages being sent using <a shape="rect" href="intercept.html">interceptors</a> or the <a shape="rect" href="eventnotifier-to-log-details-about-all-sent-exchanges.html">Event Notifier</a>.</p>
-
-<h3 id="MessageHistory-EasierMessageHistory">Easier Message History</h3>
-<p><strong>Available as of Camel 2.12</strong></p>
-
-<p><a shape="rect" href="message-history.html">Message History</a> is enabled by default from Camel 2.12. During routing Camel captures how the <a shape="rect" href="exchange.html">Exchange</a> is routed, as a <code>org.apache.camel.MessageHistory</code> entity that is stored on the <a shape="rect" href="exchange.html">Exchange</a>. On the <code>org.apache.camel.MessageHistory</code> there is information abut the route id, processor id, timestamp, and elapsed time it took to process the <a shape="rect" href="exchange.html">Exchange</a> by the processor. </p>
-
-<p>The information can be reached from Java code with:</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[
-List<MessageHistory> list = exchange.getProperty(Exchange.MESSAGE_HISTORY, List.class);
+<div class="wiki-content maincontent"><h3 id="MessageHistory-MessageHistory">Message History</h3><p>The <a shape="rect" class="external-link" href="http://www.eaipatterns.com/MessageHistory.html" rel="nofollow">Message History</a> from the <a shape="rect" href="enterprise-integration-patterns.html">EIP patterns</a> allows for analyzing and debugging the flow of messages in a loosely coupled system.</p><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://www.eaipatterns.com/img/MessageHistory.gif" data-image-src="http://www.eaipatterns.com/img/MessageHistory.gif"></span></p><p>Attaching a Message History to the message will provide a list of all applications that the message passed through since its origination.</p><p>In Camel you can trace message flow using the <a shape="rect" href="tracer.html">Tracer</a>, or access information using the Java API from <a shape="rect" class="external-link" href="http://cam
el.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/UnitOfWork.html">UnitOfWork</a> using the <code>getTracedRouteNodes</code> method.</p><p>When Camel sends a message to an endpoint that endpoint information is stored on the <a shape="rect" href="exchange.html">Exchange</a> as a property with the key <code>Exchange.TO_ENDPOINT</code>.<br clear="none"> This property contains the last known endpoint the <a shape="rect" href="exchange.html">Exchange</a> was sent to (it will be overridden when sending to new endpoint). Alternatively you can trace messages being sent using <a shape="rect" href="intercept.html">interceptors</a> or the <a shape="rect" href="eventnotifier-to-log-details-about-all-sent-exchanges.html">Event Notifier</a>.</p><h3 id="MessageHistory-EasierMessageHistory">Easier Message History</h3><p><strong>Available as of Camel 2.12</strong></p><p><a shape="rect" href="message-history.html">Message History</a> is enabled by default from Camel 2.12. During rou
ting Camel captures how the <a shape="rect" href="exchange.html">Exchange</a> is routed, as a <code>org.apache.camel.MessageHistory</code> entity that is stored on the <a shape="rect" href="exchange.html">Exchange</a>. On the <code>org.apache.camel.MessageHistory</code> there is information abut the route id, processor id, timestamp, and elapsed time it took to process the <a shape="rect" href="exchange.html">Exchange</a> by the processor.</p><p>The information can be reached from Java code with:</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[List<MessageHistory> list = exchange.getProperty(Exchange.MESSAGE_HISTORY, List.class);
...
]]></script>
-</div></div>
-
-<h4 id="MessageHistory-Enablingordisablingmessagehistory">Enabling or disabling message history</h4>
-
-<p>The <a shape="rect" href="message-history.html">Message History</a> can be enabled or disabled per <code>CamelContext</code> or per route. For example you can turn it off with</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.setMessageHistory(false);
+</div></div><h4 id="MessageHistory-Enablingordisablingmessagehistory">Enabling or disabling message history</h4><p>The <a shape="rect" href="message-history.html">Message History</a> can be enabled or disabled per <code>CamelContext</code> or per route. For example you can turn it off with</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.setMessageHistory(false);
]]></script>
-</div></div>
-
-<p>Or from XML DSL with</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[
-<camelContext messageHistory="false" ...>
+</div></div><p>Or from XML DSL with</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[<camelContext messageHistory="false" ...>
...
</camelContext>
]]></script>
-</div></div>
-
-<p>You can also do this per route. Then a route level configuration overrides the <code>CamelContext</code> level configuration. </p>
-
-<h4 id="MessageHistory-Routestack-traceinexceptionsloggedbyerrorhandler">Route stack-trace in exceptions logged by error handler</h4>
-
-<p>If <a shape="rect" href="message-history.html">Message History</a> is enabled, then Camel will leverage this information, when the <a shape="rect" href="error-handler.html">Error Handler</a> logs exhausted exceptions. Then in addition to the caused exception with its stacktrace, you can see the message history; you may think this as a "route stacktrace". And example is provided below:</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[
-2013-05-31 14:41:28,084 [ - seda://start] ERROR DefaultErrorHandler - Failed delivery for (MessageId: ID-davsclaus-air-lan-55446-1370004087263-0-1 on ExchangeId: ID-davsclaus-air-lan-55446-1370004087263-0-3). Exhausted after delivery attempt: 1 caught: java.lang.IllegalArgumentException: Forced to dump message history
+</div></div><p>You can also do this per route. Then a route level configuration overrides the <code>CamelContext</code> level configuration.</p><h4 id="MessageHistory-Routestack-traceinexceptionsloggedbyerrorhandler">Route stack-trace in exceptions logged by error handler</h4><p>If <a shape="rect" href="message-history.html">Message History</a> is enabled, then Camel will leverage this information, when the <a shape="rect" href="error-handler.html">Error Handler</a> logs exhausted exceptions. Then in addition to the caused exception with its stacktrace, you can see the message history; you may think this as a "route stacktrace". And example is provided below:</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[2013-05-31 14:41:28,084 [ - seda://start] ERROR DefaultErrorHandler - Failed delivery for (MessageId: ID-davsclaus-air-lan-55446-1370004087263-0-1 on ExchangeId: ID-davsclaus-air-lan-55446-1370004087263-0-3). Exhausted after delivery attempt: 1 caught: java.lang.IllegalArgumentException: Forced to dump message history
Message History
---------------------------------------------------------------------------------------------------------------------------------------
@@ -173,16 +134,12 @@ java.lang.IllegalArgumentException: Forc
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
]]></script>
-</div></div>
-
-<p>You can turn off logging message history from the <a shape="rect" href="error-handler.html">Error Handler</a> using</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[
-errorHandler(defaultErrorHandler().logExhaustedMessageHistory(false));
+</div></div><p>You can turn off logging message history from the <a shape="rect" href="error-handler.html">Error Handler</a> using</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[errorHandler(defaultErrorHandler().logExhaustedMessageHistory(false));
]]></script>
-</div></div>
-
-<h4 id="MessageHistory-UsingThisPattern">Using This Pattern</h4>
+</div></div><p>From Camel 2.17 onwards the <a shape="rect" href="error-handler.html">Error Handler</a> do not log the message body/header details anymore (to avoid logging sensitive message body details). You can turn on the old behavior.</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[errorHandler(defaultErrorHandler().logExhaustedMessageBody(true));]]></script>
+</div></div><p> </p><p></p><h4 id="MessageHistory-UsingThisPattern">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></div>
</td>
Modified: websites/production/camel/content/news.html
==============================================================================
--- websites/production/camel/content/news.html (original)
+++ websites/production/camel/content/news.html Sun Jan 31 02:24:33 2016
@@ -84,6 +84,26 @@
<div class="blog-post-listing">
<div class="logo-heading-block">
<span class="logoBlock">
+ <a shape="rect" class="userLogoLink" href=" /confluence/display/~davsclaus ">
+ <img class="userLogo logo" src="news.userimage/user-avatar" alt="User icon: davsclaus" title="davsclaus">
+ </a> </span>
+ <span class="blogHeading">
+ <a shape="rect" class="blogHeading" href="2016/01/30/cve-2015-5344-apache-camel-medium-disclosure-vulnerability.html">CVE-2015-5344 - Apache Camel medium disclosure vulnerability</a>
+ </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href=" /confluence/display/~davsclaus ">Claus Ibsen</a> posted on Jan 30, 2016</div>
+
+ </div>
+
+ <div class="wiki-content">
+ <p>Apache Camel's XStream usage is vulnerable to Remote Code Execution attacks</p><p>Apache Camel's camel-xstream component is vulnerable to Java object de-serialisation vulnerability.<br clear="none">Such as de-serializing untrusted data can lead to security flaws as demonstrated in various similar reports about Java de-serialization issues.</p><p>Please study this security vulnerability carefully!<br clear="none">CVE-2015-5344 - [1]</p><p>You can download the fixed Apache Camel 2.15.x and 2.16.x version from the Apache mirrors [2] or from the Central Maven repository.</p><p>[1] <a shape="rect" class="external-link" href="http://camel.apache.org/security-advisories.data/CVE-2015-5344.txt.asc?version=1&modificationDate=1454056803464&api=v2">http://camel.apache.org/security-advisories.data/CVE-2015-5344.txt.asc?version=1&modificationDate=1454056803464&api=v2</a><br clear="none">[2] <a shape="rect" class="external-link" href="http://camel.apache.org/download">h
ttp://camel.apache.org/download</a></p><p> </p><p>On behalf of the Camel PMC,<br clear="none">Claus Ibsen</p>
+ </div>
+
+
+ </div>
+
+
+<div class="blog-post-listing">
+ <div class="logo-heading-block">
+ <span class="logoBlock">
<a shape="rect" class="userLogoLink" href=" /confluence/display/~gzurowski ">
<img class="userLogo logo" src="news.userimage/gzurowski-89607-pp-wojtek-avatar.png" alt="User icon: gzurowski" title="gzurowski">
</a> </span>
@@ -458,26 +478,6 @@
</div>
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href=" /confluence/display/~njiang ">
- <img class="userLogo logo" src="news.userimage/njiang-38992-pp-pic.jpeg" alt="User icon: njiang" title="njiang">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2015/03/11/apache-camel-2134-released.html">Apache Camel 2.13.4 released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href=" /confluence/display/~njiang ">willem jiang</a> posted on Mar 11, 2015</div>
-
- </div>
-
- <div class="wiki-content">
- <p>The Camel community announces the immediate availability of the new patch release Camel 2.13.4. This release contains a total of 81 fixes applied in the past 3 months by the community on the Camel 2.13.x maintenance branch.</p><p>The artifacts are published and ready for you to <a shape="rect" class="external-link" href="http://camel.apache.org/download.html">download</a> either from the Apache mirrors or from the Central Maven repository. For more details please take a look at the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12328899&styleName=&projectId=12311211">release notes</a><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324786&projectId=12311211">.</a></p><p>Many thanks to all who made this release possible.</p><p>On behalf of the Camel PMC,</p><p>Willem</p>
- </div>
-
-
</div>
</div>
</td>
Modified: websites/production/camel/content/tools.html
==============================================================================
--- websites/production/camel/content/tools.html (original)
+++ websites/production/camel/content/tools.html Sun Jan 31 02:24:33 2016
@@ -75,7 +75,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Tools-Tools">Tools</h2><p>This page gives a list of the various tools available for Camel</p><h3 id="Tools-CamelMavenTools">Camel Maven Tools</h3><ul><li><a shape="rect" href="camel-maven-plugin.html">Camel Maven Plugin</a> for booting up Camel applications directly in maven to test it</li><li><a shape="rect" class="external-link" href="http://camel.apache.org/camel-maven-archetypes.html" style="line-height: 1.4285715;">Camel Maven Archetypes</a> for using a maven archetype to create new Camel projects</li><li><a shape="rect" href="creating-a-new-camel-component.html">Creating a new Camel Component</a><span style="line-height: 1.4285715;"> using a maven archetype. See also </span><a shape="rect" href="add-new-component-guide.html">this guide</a><span style="line-height: 1.4285715;"> about adding new components to the Apache Camel </span>distribution<span style="line-height: 1.4285715;">.</span></li></ul><h3 id="Tools-CamelComma
ndsforCLI">Camel Commands for CLI</h3><ul><li>Core Commands is a set of Camel commands that SPI can reuse to integrate Camel commands in various tooling. The core commands is in the <code>camel-commands-core</code> JAR.</li><li><a shape="rect" href="karaf.html">Karaf Commands</a> is the Camel core commands for using with Apache Karaf based containers.</li><li>commands-spring-boot is the Camel commands for <a shape="rect" href="spring-boot.html">Spring Boot</a></li><li>commands-jolokia is the Camel commands integrated with Jolokia to allow remote management</li></ul><h3 id="Tools-CamelCatalog">Camel Catalog</h3><ul><li>Is a standalone JAR <code>camel-catalog</code> that contains catalog information about the Apache Camel release. Such as information about each of the Camel components, with documentation in json schema format. This is intended for SPI to leverage for tooling, such as being able to implement Apache Camel component editors that can provide the set of opti
ons the component offers, with documentation included. </li></ul><h3 id="Tools-ExternalOpenSourceTools">External Open Source Tools</h3><ul><li><a shape="rect" class="external-link" href="http://hawt.io/" rel="nofollow">hawtio</a> is an open source HTML5 web application for visualizing, starting/stopping and tracing Apache Camel routes, browsing endpoints, sending messages to endpoints as well as browsing and sending to ActiveMQ destinations, viewing logs and metric charting etc.</li><li><a shape="rect" class="external-link" href="http://tools.jboss.org/features/apachecamel.html" rel="nofollow">JBoss </a><a shape="rect" class="external-link" href="http://tools.jboss.org/features/apachecamel.html" rel="nofollow">Tools for Apache Camel</a><a shape="rect" class="external-link" href="http://tools.jboss.org/features/apachecamel.html" rel="nofollow"> is an open source set of eclipse plugins for creating Apache Camel projects, editing Camel routes using a graphical editor.</a></li
><li><a shape="rect" class="external-link" href="http://fabric8.io/" rel="nofollow">fabric8</a> <a shape="rect" class="external-link" href="http://fabric8.io/guide/forge.html" rel="nofollow">Camel forge addon</a> is a set of both the Camel commands for remote management, and a set of Camel editing tools to edit Camel endpoints, components in both Java and XML routes.</li></ul></div>
+<div class="wiki-content maincontent"><h2 id="Tools-Tools">Tools</h2><p>This page gives a list of the various tools available for Camel</p><h3 id="Tools-CamelMavenTools">Camel Maven Tools</h3><ul><li><a shape="rect" href="camel-maven-plugin.html">Camel Maven Plugin</a> for booting up Camel applications directly in maven to test it</li><li><a shape="rect" class="external-link" href="http://camel.apache.org/camel-maven-archetypes.html" style="line-height: 1.4285715;">Camel Maven Archetypes</a> for using a maven archetype to create new Camel projects</li><li><a shape="rect" href="creating-a-new-camel-component.html">Creating a new Camel Component</a><span style="line-height: 1.4285715;"> using a maven archetype. See also </span><a shape="rect" href="add-new-component-guide.html">this guide</a><span style="line-height: 1.4285715;"> about adding new components to the Apache Camel </span>distribution<span style="line-height: 1.4285715;">.</span></li></ul><h3 id="Tools-CamelComma
ndsforCLI">Camel Commands for CLI</h3><ul><li>Core Commands is a set of Camel commands that SPI can reuse to integrate Camel commands in various tooling. The core commands is in the <code>camel-commands-core</code> JAR.</li><li><a shape="rect" href="karaf.html">Karaf Commands</a> is the Camel core commands for using with Apache Karaf based containers.</li><li>commands-spring-boot is the Camel commands for <a shape="rect" href="spring-boot.html">Spring Boot</a></li><li>commands-jolokia is the Camel commands integrated with Jolokia to allow remote management</li></ul><h3 id="Tools-CamelCatalog">Camel Catalog</h3><ul><li>Is a standalone JAR <code>camel-catalog</code> that contains catalog information about the Apache Camel release. Such as information about each of the Camel components, with documentation in json schema format. This is intended for SPI to leverage for tooling, such as being able to implement Apache Camel component editors that can provide the set of opti
ons the component offers, with documentation included. </li></ul><h3 id="Tools-ExternalOpenSourceTools">External Open Source Tools</h3><ul><li><a shape="rect" class="external-link" href="http://hawt.io/" rel="nofollow">hawtio</a> is an open source HTML5 web application for visualizing, starting/stopping and tracing Apache Camel routes, browsing endpoints, sending messages to endpoints as well as browsing and sending to ActiveMQ destinations, viewing logs and metric charting etc.</li><li><a shape="rect" class="external-link" href="http://tools.jboss.org/features/apachecamel.html" rel="nofollow">JBoss </a><a shape="rect" class="external-link" href="http://tools.jboss.org/features/apachecamel.html" rel="nofollow">Tools for Apache Camel</a><a shape="rect" class="external-link" href="http://tools.jboss.org/features/apachecamel.html" rel="nofollow"> is an open source set of eclipse plugins for creating Apache Camel projects, editing Camel routes using a graphical editor.</a></li
><li><a shape="rect" class="external-link" href="http://fabric8.io/" rel="nofollow">fabric8</a> <a shape="rect" class="external-link" href="http://fabric8.io/guide/forge.html" rel="nofollow">Camel forge addon</a> is a set of both the Camel commands for remote management, and a set of Camel editing tools to edit Camel endpoints, components in both Java and XML routes.</li><li><a shape="rect" class="external-link" href="http://fabric8.io/" rel="nofollow">fabric8</a> <a shape="rect" class="external-link" href="http://fabric8.io/guide/camelMavenPlugin.html" rel="nofollow">Camel Maven Plugin</a> is a maven plugin that is able to validate all your Camel endpoints from the source code, so you quickly can catch typo and other mistakes in your endpoints, and not have to wait for runtime to fail.</li></ul></div>
</td>
<td valign="top">
<div class="navigation">