Author: buildbot
Date: Mon Jun 3 18:19:56 2013
New Revision: 864232
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-2120-release.html
websites/production/camel/content/controlbus-component.html
websites/production/camel/content/controlbus.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-2120-release.html
==============================================================================
--- websites/production/camel/content/camel-2120-release.html (original)
+++ websites/production/camel/content/camel-2120-release.html Mon Jun 3
18:19:56 2013
@@ -84,7 +84,7 @@
<p>Welcome to the 2.12.0 release which approx XXX issues resolved (new
features, improvements and bug fixes such as...)</p>
-<ul><li><a shape="rect" href="endpoint-annotations.html" title="Endpoint
Annotations">Endpoint Annotations</a> along with automatically created HTML
documentation for the endpoint parameters; this makes it easier for component
developers to add a few refactoring-safe annotations to their Endpoint or
Consumer implementations and, (along with javadoc comments on the field or
setter method), get nice user documentation on how to use the endpoint for
free.</li><li><a shape="rect" href="componentconfiguration.html"
title="ComponentConfiguration">ComponentConfiguration</a> API provides a handy
API for tools developers to introspect on a Component to find all the possible
parameters, their types and any extra annotations (like Bean Validation
Annotations) to be able to create/edit endpoints or URI strings so that tools
can generate nicer UIs for configuring endpoints than just letting folks edit
Strings.</li><li><a shape="rect" href="endpointcompleter.html"
title="EndpointCompleter
">EndpointCompleter</a> API provides a hook so that command line tools (like
<a shape="rect" class="external-link"
href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/using-console.html";>Karaf's
shell</a>), IDEs and web tools can get (bash tab like) auto-completion on
endpoint paths (such as file or directory names, message queue names, database
table names) when creating or using new endpoints</li><li>Reduced stack-frames
in use during routing, that also makes Camel's stack traces being logged much
less verbose. This also allows people to easier debug the internals of Camel as
less <tt>AsyncCallback</tt> callbacks are in use during routing.</li><li>Easy
to use <a shape="rect" href="message-history.html" title="Message
History">Message History</a> out of the box. And included message history as
"route stack-trace" when exceptions logged by <a shape="rect"
href="error-handler.html" title="Error Handler">Error Handler</a> to make it
easier for end users to spot where
the exception occurred.</li><li><a shape="rect"
href="spring-web-services.html" title="Spring Web Services">Spring Web
Services</a> now supports setting/receiving SOAP headers more easily using a
header on the Camel <a shape="rect" href="message.html"
title="Message">Message</a>.</li><li>Evaluating <a shape="rect"
href="groovy.html" title="Groovy">Groovy</a> expressions is faster as we cache
the compiled scripts.</li><li>Added <tt>base64</tt> option to <a shape="rect"
href="shiro-security.html" title="Shiro Security">Shiro Security</a> to allow
transferring security token over <a shape="rect" href="jms.html"
title="JMS">JMS</a> and other transports as base64 encoded
representation.</li><li>Made it easier to use <a shape="rect"
href="shiro-security.html" title="Shiro Security">Shiro Security</a> as the
credentials can be provided in headers, when sending a message to a secured
route.</li><li><a shape="rect" href="bindy.html" title="Bindy">Bindy</a> now
supports enums.</li><l
i>Added new <a shape="rect" href="backlogdebugger.html"
title="BacklogDebugger">BacklogDebugger</a> to perform live debugging of
messages during routing. The <a shape="rect" href="backlogdebugger.html"
title="BacklogDebugger">BacklogDebugger</a> has JMX API allows tooling to
control the debugger.</li><li>While using the <a shape="rect"
class="external-link" href="http://xircles.codehaus.org/projects/jackson";
rel="nofollow">Jackson library</a> through the <a shape="rect" href="json.html"
title="JSON">JSON</a> Dataformat there's now a <tt>jsonView</tt> attribute you
could make use of directly inside the <a shape="rect" href="dsl.html"
title="DSL">DSL</a> itself.</li><li><a shape="rect" href="smpp.html"
title="SMPP">SMPP</a> now supports optional parameters in all commands where
they are possible.</li><li><a shape="rect" href="jdbc.html"
title="JDBC">JDBC</a> now supports named parameters.</li><li>Added timeout
support for <a shape="rect" href="direct.html" title="Direct">Direc
t</a> producers to wait for consumer to become active.</li></ul>
+<ul><li><a shape="rect" href="endpoint-annotations.html" title="Endpoint
Annotations">Endpoint Annotations</a> along with automatically created HTML
documentation for the endpoint parameters; this makes it easier for component
developers to add a few refactoring-safe annotations to their Endpoint or
Consumer implementations and, (along with javadoc comments on the field or
setter method), get nice user documentation on how to use the endpoint for
free.</li><li><a shape="rect" href="componentconfiguration.html"
title="ComponentConfiguration">ComponentConfiguration</a> API provides a handy
API for tools developers to introspect on a Component to find all the possible
parameters, their types and any extra annotations (like Bean Validation
Annotations) to be able to create/edit endpoints or URI strings so that tools
can generate nicer UIs for configuring endpoints than just letting folks edit
Strings.</li><li><a shape="rect" href="endpointcompleter.html"
title="EndpointCompleter
">EndpointCompleter</a> API provides a hook so that command line tools (like
<a shape="rect" class="external-link"
href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/using-console.html";>Karaf's
shell</a>), IDEs and web tools can get (bash tab like) auto-completion on
endpoint paths (such as file or directory names, message queue names, database
table names) when creating or using new endpoints</li><li>Reduced stack-frames
in use during routing, that also makes Camel's stack traces being logged much
less verbose. This also allows people to easier debug the internals of Camel as
less <tt>AsyncCallback</tt> callbacks are in use during routing.</li><li>Easy
to use <a shape="rect" href="message-history.html" title="Message
History">Message History</a> out of the box. And included message history as
"route stack-trace" when exceptions logged by <a shape="rect"
href="error-handler.html" title="Error Handler">Error Handler</a> to make it
easier for end users to spot where
the exception occurred.</li><li><a shape="rect"
href="spring-web-services.html" title="Spring Web Services">Spring Web
Services</a> now supports setting/receiving SOAP headers more easily using a
header on the Camel <a shape="rect" href="message.html"
title="Message">Message</a>.</li><li>Evaluating <a shape="rect"
href="groovy.html" title="Groovy">Groovy</a> expressions is faster as we cache
the compiled scripts.</li><li>Added <tt>base64</tt> option to <a shape="rect"
href="shiro-security.html" title="Shiro Security">Shiro Security</a> to allow
transferring security token over <a shape="rect" href="jms.html"
title="JMS">JMS</a> and other transports as base64 encoded
representation.</li><li>Made it easier to use <a shape="rect"
href="shiro-security.html" title="Shiro Security">Shiro Security</a> as the
credentials can be provided in headers, when sending a message to a secured
route.</li><li><a shape="rect" href="bindy.html" title="Bindy">Bindy</a> now
supports enums.</li><l
i>Added new <a shape="rect" href="backlogdebugger.html"
title="BacklogDebugger">BacklogDebugger</a> to perform live debugging of
messages during routing. The <a shape="rect" href="backlogdebugger.html"
title="BacklogDebugger">BacklogDebugger</a> has JMX API allows tooling to
control the debugger.</li><li>While using the <a shape="rect"
class="external-link" href="http://xircles.codehaus.org/projects/jackson";
rel="nofollow">Jackson library</a> through the <a shape="rect" href="json.html"
title="JSON">JSON</a> Dataformat there's now a <tt>jsonView</tt> attribute you
could make use of directly inside the <a shape="rect" href="dsl.html"
title="DSL">DSL</a> itself.</li><li><a shape="rect" href="smpp.html"
title="SMPP">SMPP</a> now supports optional parameters in all commands where
they are possible.</li><li><a shape="rect" href="jdbc.html"
title="JDBC">JDBC</a> now supports named parameters.</li><li>Added timeout
support for <a shape="rect" href="direct.html" title="Direct">Direc
t</a> producers to wait for consumer to become active.</li><li>Added
<tt>stats</tt> action to <a shape="rect" href="controlbus.html"
title="ControlBus">ControlBus</a> to easily get performance statics in a single
XML message.</li></ul>
<h3><a shape="rect" name="Camel2.12.0Release-FixedIssues"></a>Fixed Issues</h3>
Modified: websites/production/camel/content/controlbus-component.html
==============================================================================
--- websites/production/camel/content/controlbus-component.html (original)
+++ websites/production/camel/content/controlbus-component.html Mon Jun 3
18:19:56 2013
@@ -97,7 +97,7 @@ controlbus:command[?options]
<h3><a shape="rect" name="ControlBusComponent-Options"></a>Options</h3>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>routeId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> To specify a route by its <tt>id</tt>. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>action</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> To denote an action that can be
either: <tt>start</tt>, <tt>stop</tt>, or <tt>status</tt>. To either start or
stop a route, or to get the status of the route as output in the message body.
You can use <tt>suspend</tt> and <tt>resume</tt> from <b>Camel 2.11.1</b>
onwards to either suspend or resume a route.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>async</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Whether to execute the control
bus task asynchronously. <b>Important:</b> If this option is enabled, then any
result from the task is <b>not</b> set on the <a shape="rect"
href="exchange.html" title="Exchange">Exchange</a>. This is only possible if
executing tasks synchronously. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>loggingLevel</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>INFO</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Logging level used for logging when task is done, or if
any exceptions occurred during processing the task. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>routeId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> To specify a route by its <tt>id</tt>. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>action</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> To denote an action that can be
either: <tt>start</tt>, <tt>stop</tt>, or <tt>status</tt>. To either start or
stop a route, or to get the status of the route as output in the message body.
You can use <tt>suspend</tt> and <tt>resume</tt> from <b>Camel 2.11.1</b>
onwards to either suspend or resume a route.
And from <b>Camel 2.11.1</b> onwards you can use <tt>stats</tt> to get
performance statics returned in XML format; the <tt>routeId</tt> option can be
used to define which route to get the performance stats for, if
<tt>routeId</tt> is not defined, then you get statistics for the entire <a
shape="rect" href="camelcontext.html" title="CamelContext">CamelContext</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>async</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Whether to execute the control
bus task asynchronously. <b>Important:</b> If this option is enabled, then any
result from the task is <b>not</b> set on the <a shape="rect"
href="exchange.html" title="Exchange">Exchange</a>. This is only possible if
executing tasks synchronously. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>loggingLevel</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"
> <tt>INFO</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Logging
> level used for logging when task is done, or if any exceptions occurred
> during processing the task. </td></tr></tbody></table>
</div>
</div>
@@ -122,6 +122,26 @@ template.sendBody(<span class="code-quot
</div></div>
+<h5><a shape="rect"
name="ControlBusComponent-Gettingperformancestatistics"></a>Getting performance
statistics</h5>
+<p><b>Available as of Camel 2.11.1</b></p>
+
+<p>This requires JMX to be enabled (is by default) then you can get the
performance statics per route, or for the <a shape="rect"
href="camelcontext.html" title="CamelContext">CamelContext</a>. For example to
get the statics for a route named foo, we can do:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<pre class="code-java">
+<span class="code-object">String</span> xml = template.requestBody(<span
class="code-quote">"controlbus:route?routeId=foo&action=stats"</span>,
<span class="code-keyword">null</span>, <span
class="code-object">String</span>.class);
+</pre>
+</div></div>
+
+<p>The returned statics is in XML format. Its the same data you can get from
JMX with the <tt>dumpRouteStatsAsXml</tt> operation on the
<tt>ManagedRouteMBean</tt>.</p>
+
+<p>To get statics for the entire <a shape="rect" href="camelcontext.html"
title="CamelContext">CamelContext</a> you just omit the routeId parameter as
shown below:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<pre class="code-java">
+<span class="code-object">String</span> xml = template.requestBody(<span
class="code-quote">"controlbus:route?action=stats"</span>, <span
class="code-keyword">null</span>, <span
class="code-object">String</span>.class);
+</pre>
+</div></div>
+
+
<h4><a shape="rect" name="ControlBusComponent-UsingSimplelanguage"></a>Using
<a shape="rect" href="simple.html" title="Simple">Simple</a> language</h4>
<p>You can use the <a shape="rect" href="simple.html"
title="Simple">Simple</a> language with the control bus, for example to stop a
specific route, you can send a message to the
<tt>"controlbus:language:simple"</tt> endpoint containing the following
message:</p>
Modified: websites/production/camel/content/controlbus.html
==============================================================================
--- websites/production/camel/content/controlbus.html (original)
+++ websites/production/camel/content/controlbus.html Mon Jun 3 18:19:56 2013
@@ -109,7 +109,7 @@ controlbus:command[?options]
<h3><a shape="rect" name="ControlBus-Options"></a>Options</h3>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>routeId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> To specify a route by its <tt>id</tt>. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>action</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> To denote an action that can be
either: <tt>start</tt>, <tt>stop</tt>, or <tt>status</tt>. To either start or
stop a route, or to get the status of the route as output in the message body.
You can use <tt>suspend</tt> and <tt>resume</tt> from <b>Camel 2.11.1</b>
onwards to either suspend or resume a route.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>async</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Whether to execute the control
bus task asynchronously. <b>Important:</b> If this option is enabled, then any
result from the task is <b>not</b> set on the <a shape="rect"
href="exchange.html" title="Exchange">Exchange</a>. This is only possible if
executing tasks synchronously. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>loggingLevel</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>INFO</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Logging level used for logging when task is done, or if
any exceptions occurred during processing the task. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>routeId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> To specify a route by its <tt>id</tt>. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>action</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> To denote an action that can be
either: <tt>start</tt>, <tt>stop</tt>, or <tt>status</tt>. To either start or
stop a route, or to get the status of the route as output in the message body.
You can use <tt>suspend</tt> and <tt>resume</tt> from <b>Camel 2.11.1</b>
onwards to either suspend or resume a route.
And from <b>Camel 2.11.1</b> onwards you can use <tt>stats</tt> to get
performance statics returned in XML format; the <tt>routeId</tt> option can be
used to define which route to get the performance stats for, if
<tt>routeId</tt> is not defined, then you get statistics for the entire <a
shape="rect" href="camelcontext.html" title="CamelContext">CamelContext</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>async</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Whether to execute the control
bus task asynchronously. <b>Important:</b> If this option is enabled, then any
result from the task is <b>not</b> set on the <a shape="rect"
href="exchange.html" title="Exchange">Exchange</a>. This is only possible if
executing tasks synchronously. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>loggingLevel</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"
> <tt>INFO</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Logging
> level used for logging when task is done, or if any exceptions occurred
> during processing the task. </td></tr></tbody></table>
</div>
</div>
@@ -134,6 +134,26 @@ template.sendBody(<span class="code-quot
</div></div>
+<h5><a shape="rect" name="ControlBus-Gettingperformancestatistics"></a>Getting
performance statistics</h5>
+<p><b>Available as of Camel 2.11.1</b></p>
+
+<p>This requires JMX to be enabled (is by default) then you can get the
performance statics per route, or for the <a shape="rect"
href="camelcontext.html" title="CamelContext">CamelContext</a>. For example to
get the statics for a route named foo, we can do:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<pre class="code-java">
+<span class="code-object">String</span> xml = template.requestBody(<span
class="code-quote">"controlbus:route?routeId=foo&action=stats"</span>,
<span class="code-keyword">null</span>, <span
class="code-object">String</span>.class);
+</pre>
+</div></div>
+
+<p>The returned statics is in XML format. Its the same data you can get from
JMX with the <tt>dumpRouteStatsAsXml</tt> operation on the
<tt>ManagedRouteMBean</tt>.</p>
+
+<p>To get statics for the entire <a shape="rect" href="camelcontext.html"
title="CamelContext">CamelContext</a> you just omit the routeId parameter as
shown below:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<pre class="code-java">
+<span class="code-object">String</span> xml = template.requestBody(<span
class="code-quote">"controlbus:route?action=stats"</span>, <span
class="code-keyword">null</span>, <span
class="code-object">String</span>.class);
+</pre>
+</div></div>
+
+
<h4><a shape="rect" name="ControlBus-UsingSimplelanguage"></a>Using <a
shape="rect" href="simple.html" title="Simple">Simple</a> language</h4>
<p>You can use the <a shape="rect" href="simple.html"
title="Simple">Simple</a> language with the control bus, for example to stop a
specific route, you can send a message to the
<tt>"controlbus:language:simple"</tt> endpoint containing the following
message:</p>
