Author: buildbot
Date: Tue Nov  5 18:20:03 2013
New Revision: 885534

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-2130-release.html
    websites/production/camel/content/camel-jmx.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/camel-2130-release.html
==============================================================================
--- websites/production/camel/content/camel-2130-release.html (original)
+++ websites/production/camel/content/camel-2130-release.html Tue Nov  5 
18:20:03 2013
@@ -94,7 +94,7 @@
 
 <p>Welcome to the 2.13.0 release which approx XXX issues resolved (new 
features, improvements and bug fixes such as...)</p>
 
-<ul><li>When using multiple OSGi Blueprint &lt;cm:property-placeholder&gt;'s 
then Camel now favors using non-default placeholders, or the last 
property-placeholder defined in the Blueprint XML file. This allows for example 
to define default properties in one placeholder, and override these values in 
other placeholders.</li><li><a shape="rect" href="ftp2.html" 
title="FTP2">FTP</a> consumer allow to download a single named file without 
using the FTP LIST command. This allows to download a known file from a FTP 
server even when the user account does not have permission to do FTP LIST 
command.</li><li><a shape="rect" href="ftp2.html" title="FTP2">FTP</a> consumer 
allow to ignore file not found or insufficient file permission 
errors.</li><li><a shape="rect" href="data-format.html" title="Data 
Format">Data Format</a> using marshal now leverages <a shape="rect" 
href="stream-caching.html" title="Stream caching">Stream caching</a> out of the 
box if enabled, which allows to marshal big stream
 s and spool to disk, instead of being pure in-memory based.</li><li>Improved 
using <a shape="rect" href="bean.html" title="Bean">Bean</a> when the bean is 
looked up in the <a shape="rect" href="registry.html" 
title="Registry">Registry</a>, when using concurrent processing in the 
route.</li><li>Added <tt>cache</tt> option to <tt>beanRef</tt> and 
<tt>&lt;bean&gt;</tt> in the DSL. This avoids looking up the <a shape="rect" 
href="bean.html" title="Bean">Bean</a> from the <a shape="rect" 
href="registry.html" title="Registry">Registry</a> on each usage; this can 
safely be done for singleton beans.</li><li>Configuring <a shape="rect" 
href="data-format.html" title="Data Format">Data Format</a>s in XML attributes 
now supports reference lookup using the # syntax, eg <tt>&lt;jaxb 
xmlStreamWriterWrapper="#myWriterWrapper" ..&gt;</tt></li><li><a shape="rect" 
href="jdbc.html" title="JDBC">JDBC</a> component now also support 
<tt>outputType</tt> to specify the expected output as either a List or si
 ngle Object. As well allow to map to a bean using a <tt>BeanRowMapper</tt> to 
control the mapping of ROW names to bean properties.</li><li>Both <a 
shape="rect" href="quartz.html" title="Quartz">Quartz</a> as well as <a 
shape="rect" href="quartz2.html" title="Quartz2">Quartz2</a> based <a 
shape="rect" href="scheduledroutepolicy.html" 
title="ScheduledRoutePolicy">ScheduledRoutePolicy</a> has been improved to 
better support cluster setups (e.g. to not schedule jobs being already 
scheduled through another node inside a given cluster).</li><li>Reduced the 
work the <a shape="rect" href="aggregator2.html" 
title="Aggregator2">Aggregate</a> EIP does while holding a lock during 
aggregation, which can lead to improved performance in some 
use-cases.</li><li><tt>JndiRegistry</tt> now implements all the find 
methods.</li><li><a shape="rect" href="vm.html" title="VM">VM</a> component now 
supports <tt>multipleConsumers=true</tt> across deployment units.</li><li>Added 
<tt>@PreConsumed</tt> to <a sha
 pe="rect" href="jpa.html" title="JPA">JPA</a> consumer.</li><li>Added 
CamelFileName header support to the <a shape="rect" href="hdfs.html" 
title="HDFS">HDFS</a> producer</li><li>Like as <tt>JpaConsumer</tt> now also 
<tt>JpaProducer</tt> of the <a shape="rect" href="jpa.html" title="JPA">JPA</a> 
component supports the <tt>CamelEntityManager</tt> header.</li><li><a 
shape="rect" href="restlet.html" title="Restlet">Restlet</a> consumer now 
supports returning custom headers as HTTP headers from the Camel <a 
shape="rect" href="message.html" title="Message">Message</a>.</li><li><a 
shape="rect" href="spring-java-config.html" title="Spring Java Config">Spring 
Java Config</a> <tt>CamelConfiguration</tt> now automagically detects all 
<tt>RouteBuilder</tt> instances registered in the Spring context if 
<tt>CamelConfiguration#routes</tt> method is not overridden.</li><li>Added 
support for transferring custom headers with <a shape="rect" 
href="rabbitmq.html" title="RabbitMQ">RabbitMQ</a> component
 .</li><li><a shape="rect" href="crypto.html" title="Crypto">PGPDataFormat</a> 
enables stream cache during 
unmarshaling.</li><li><tt>FileIdempotentRepository</tt> now creates necessary 
parent directories together with the new repository file.</li></ul>
+<ul><li>The MBean names registered by <a shape="rect" href="camel-jmx.html" 
title="Camel JMX">Camel JMX</a> no longer include the hostname in the 
<tt>context</tt> part, eg before <tt>context=myHost/myCamelId</tt> and now 
after <tt>context=myCamelId</tt>. Having the hostname in the MBean name does 
not bring much value, and in fact makes things more complicated as the mbean 
name changes depending on the host running Camel.</li><li>When using multiple 
OSGi Blueprint &lt;cm:property-placeholder&gt;'s then Camel now favors using 
non-default placeholders, or the last property-placeholder defined in the 
Blueprint XML file. This allows for example to define default properties in one 
placeholder, and override these values in other placeholders.</li><li><a 
shape="rect" href="ftp2.html" title="FTP2">FTP</a> consumer allow to download a 
single named file without using the FTP LIST command. This allows to download a 
known file from a FTP server even when the user account does not have permission
  to do FTP LIST command.</li><li><a shape="rect" href="ftp2.html" 
title="FTP2">FTP</a> consumer allow to ignore file not found or insufficient 
file permission errors.</li><li><a shape="rect" href="data-format.html" 
title="Data Format">Data Format</a> using marshal now leverages <a shape="rect" 
href="stream-caching.html" title="Stream caching">Stream caching</a> out of the 
box if enabled, which allows to marshal big streams and spool to disk, instead 
of being pure in-memory based.</li><li>Improved using <a shape="rect" 
href="bean.html" title="Bean">Bean</a> when the bean is looked up in the <a 
shape="rect" href="registry.html" title="Registry">Registry</a>, when using 
concurrent processing in the route.</li><li>Added <tt>cache</tt> option to 
<tt>beanRef</tt> and <tt>&lt;bean&gt;</tt> in the DSL. This avoids looking up 
the <a shape="rect" href="bean.html" title="Bean">Bean</a> from the <a 
shape="rect" href="registry.html" title="Registry">Registry</a> on each usage; 
this can safely be
  done for singleton beans.</li><li>Configuring <a shape="rect" 
href="data-format.html" title="Data Format">Data Format</a>s in XML attributes 
now supports reference lookup using the # syntax, eg <tt>&lt;jaxb 
xmlStreamWriterWrapper="#myWriterWrapper" ..&gt;</tt></li><li><a shape="rect" 
href="jdbc.html" title="JDBC">JDBC</a> component now also support 
<tt>outputType</tt> to specify the expected output as either a List or single 
Object. As well allow to map to a bean using a <tt>BeanRowMapper</tt> to 
control the mapping of ROW names to bean properties.</li><li>Both <a 
shape="rect" href="quartz.html" title="Quartz">Quartz</a> as well as <a 
shape="rect" href="quartz2.html" title="Quartz2">Quartz2</a> based <a 
shape="rect" href="scheduledroutepolicy.html" 
title="ScheduledRoutePolicy">ScheduledRoutePolicy</a> has been improved to 
better support cluster setups (e.g. to not schedule jobs being already 
scheduled through another node inside a given cluster).</li><li>Reduced the 
work the <a sha
 pe="rect" href="aggregator2.html" title="Aggregator2">Aggregate</a> EIP does 
while holding a lock during aggregation, which can lead to improved performance 
in some use-cases.</li><li><tt>JndiRegistry</tt> now implements all the find 
methods.</li><li><a shape="rect" href="vm.html" title="VM">VM</a> component now 
supports <tt>multipleConsumers=true</tt> across deployment units.</li><li>Added 
<tt>@PreConsumed</tt> to <a shape="rect" href="jpa.html" title="JPA">JPA</a> 
consumer.</li><li>Added CamelFileName header support to the <a shape="rect" 
href="hdfs.html" title="HDFS">HDFS</a> producer</li><li>Like as 
<tt>JpaConsumer</tt> now also <tt>JpaProducer</tt> of the <a shape="rect" 
href="jpa.html" title="JPA">JPA</a> component supports the 
<tt>CamelEntityManager</tt> header.</li><li><a shape="rect" href="restlet.html" 
title="Restlet">Restlet</a> consumer now supports returning custom headers as 
HTTP headers from the Camel <a shape="rect" href="message.html" 
title="Message">Message</a>.</l
 i><li><a shape="rect" href="spring-java-config.html" title="Spring Java 
Config">Spring Java Config</a> <tt>CamelConfiguration</tt> now automagically 
detects all <tt>RouteBuilder</tt> instances registered in the Spring context if 
<tt>CamelConfiguration#routes</tt> method is not overridden.</li><li>Added 
support for transferring custom headers with <a shape="rect" 
href="rabbitmq.html" title="RabbitMQ">RabbitMQ</a> component.</li><li><a 
shape="rect" href="crypto.html" title="Crypto">PGPDataFormat</a> enables stream 
cache during unmarshaling.</li><li><tt>FileIdempotentRepository</tt> now 
creates necessary parent directories together with the new repository 
file.</li></ul>
 
 
 <h3><a shape="rect" name="Camel2.13.0Release-FixedIssues"></a>Fixed Issues</h3>
@@ -147,7 +147,8 @@
 
 
 <h2><a shape="rect" 
name="Camel2.13.0Release-Changesthatmayaffectendusers"></a>Changes that may 
affect end users</h2>
-<ul><li>Components depending on Servlet API has been upgrade from Servlet API 
2.5 to 3.0</li><li>Jetty upgraded from 7.6.x to 8.1.x</li><li><a shape="rect" 
href="hazelcast-component.html" title="Hazelcast Component">Hazelcast 
Component</a> uses <tt>Object</tt> instead of <tt>String</tt> as the 
key.</li><li><a shape="rect" href="hazelcast-component.html" title="Hazelcast 
Component">Hazelcast Component</a> atomic number producer was using incorrect 
name (<a shape="rect" class="external-link" 
href="https://issues.apache.org/jira/browse/CAMEL-6833";>CAMEL-6833</a>).  Name 
will be different with this release.</li><li><a shape="rect" 
href="hazelcast-component.html" title="Hazelcast Component">Hazelcast 
Component</a> instance consumer was incorrectly writing headers to the "out" 
message as opposed to the "in" message.  Headers are now written to the "in" 
message.</li><li><a shape="rect" href="hazelcast-component.html" 
title="Hazelcast Component">Hazelcast Component</a> map/multimap consumer
  were sending header value "envict" when an item was evicted.  This has been 
corrected and the value "evicted" is used now.</li><li>The enum value 
<tt>NON_BLOCKING</tt> has been removed in <tt>camel-apns</tt> as its no longer 
support in APNS itself.</li><li><tt>DefaultTimeoutMap</tt> must call 
<tt>start</tt> to initialize the map before 
use.</li><li><tt>@ExcludeRoutes</tt> test annotation now accepts only classes 
implementing <tt>RoutesBuilder</tt> interface.</li></ul>
+<ul><li>Components depending on Servlet API has been upgrade from Servlet API 
2.5 to 3.0</li><li>Jetty upgraded from 7.6.x to 8.1.x</li><li><a shape="rect" 
href="hazelcast-component.html" title="Hazelcast Component">Hazelcast 
Component</a> uses <tt>Object</tt> instead of <tt>String</tt> as the 
key.</li><li><a shape="rect" href="hazelcast-component.html" title="Hazelcast 
Component">Hazelcast Component</a> atomic number producer was using incorrect 
name (<a shape="rect" class="external-link" 
href="https://issues.apache.org/jira/browse/CAMEL-6833";>CAMEL-6833</a>).  Name 
will be different with this release.</li><li><a shape="rect" 
href="hazelcast-component.html" title="Hazelcast Component">Hazelcast 
Component</a> instance consumer was incorrectly writing headers to the "out" 
message as opposed to the "in" message.  Headers are now written to the "in" 
message.</li><li><a shape="rect" href="hazelcast-component.html" 
title="Hazelcast Component">Hazelcast Component</a> map/multimap consumer
  were sending header value "envict" when an item was evicted.  This has been 
corrected and the value "evicted" is used now.</li><li>The enum value 
<tt>NON_BLOCKING</tt> has been removed in <tt>camel-apns</tt> as its no longer 
support in APNS itself.</li><li><tt>DefaultTimeoutMap</tt> must call 
<tt>start</tt> to initialize the map before 
use.</li><li><tt>@ExcludeRoutes</tt> test annotation now accepts only classes 
implementing <tt>RoutesBuilder</tt> interface.</li><li>The MBean names 
registered by <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel 
JMX</a> no longer include the hostname in the <tt>context</tt> part, eg before 
<tt>context=myHost/myCamelId</tt> and now after <tt>context=myCamelId</tt>. 
Having the hostname in the MBean name does not bring much value, and in fact 
makes things more complicated as the mbean name changes depending on the host 
running Camel. There is an option <tt>includeHostName</tt> that can be 
configure as <tt>true</tt> to preserve the old behav
 ior.</li></ul>
+
 
 
 <h2><a shape="rect" 
name="Camel2.13.0Release-Importantchangestoconsiderwhenupgrading"></a>Important 
changes to consider when upgrading</h2>

Modified: websites/production/camel/content/camel-jmx.html
==============================================================================
--- websites/production/camel/content/camel-jmx.html (original)
+++ websites/production/camel/content/camel-jmx.html Tue Nov  5 18:20:03 2013
@@ -379,7 +379,7 @@ SUNJMX=-Dcom.sun.management.jmxremote=tr
 <h4><a shape="rect" name="CamelJMX-jmxAgentPropertiesReference"></a>jmxAgent 
Properties Reference</h4>
 
 <div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" 
class="confluenceTh"> Spring property </th><th colspan="1" rowspan="1" 
class="confluenceTh"> System property </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>id</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" 
class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" 
class="confluenceTd"> The JMX agent name, and it is not optional 
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>usePlatformMBeanServer</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>org.apache.camel.jmx.usePlatformMBeanServer</tt> 
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt>, 
<tt>true</tt> - Release 1.5 or later </td><td colspan="1" rowspan="1" 
class="confluenceTd"> If <tt>true</tt>, it 
 will use the <tt>MBeanServer</tt> from the JVM </td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"> <tt>mbeanServerDefaultDomain</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> 
<tt>org.apache.camel.jmx.mbeanServerDefaultDomain</tt> </td><td colspan="1" 
rowspan="1" class="confluenceTd"> <tt>org.apache.camel</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> The default JMX domain of the 
<tt>MBeanServer</tt> </td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>mbeanObjectDomainName</tt> </td><td colspan="1" 
rowspan="1" class="confluenceTd"> 
<tt>org.apache.camel.jmx.mbeanObjectDomainName</tt> </td><td colspan="1" 
rowspan="1" class="confluenceTd"> <tt>org.apache.camel</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> The JMX domain that all object 
names will use </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>createConnector</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>org.apache.camel.jmx.cr
 eateRmiConnect</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If we 
should create a JMX connector (to allow remote management) for the 
<tt>MBeanServer</tt> </td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>registryPort</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>org.apache.camel.jmx.rmiConnector.registryPort</tt> 
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1099</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> The port that the JMX RMI 
registry will use </td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>connectorPort</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>org.apache.camel.jmx.rmiConnector.connectorPort</tt> 
</td><td colspan="1" rowspan="1" class="confluenceTd"> -1 (dynamic) </td><td 
colspan="1" rowspan="1" class="confluenceTd"> The port that the JMX RMI server 
will use </td></tr><tr><td colspan="1"
  rowspan="1" class="confluenceTd"> <tt>serviceUrlPath</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> 
<tt>org.apache.camel.jmx.serviceUrlPath</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>/jmxrmi/camel</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> The path that JMX connector will be registered under 
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>onlyRegisterProcessorWithCustomId</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> 
<tt>org.apache.camel.jmx.onlyRegisterProcessorWithCustomId</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.0:</b> If this option 
is enabled then only processors with a custom id set will be registered. This 
allows you to filer out unwanted processors in the JMX console. 
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>statisticsLevel</tt> </td><td colspan="1" rowspan="1" clas
 s="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>All</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 
2.1:</b> Configures the level for whether performance statistics is enabled for 
the MBean. See section <em>Configuring level of granularity for performance 
statistics</em> for more details. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" 
class="confluenceTh"> Spring property </th><th colspan="1" rowspan="1" 
class="confluenceTh"> System property </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>id</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" 
class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" 
class="confluenceTd"> The JMX agent name, and it is not optional 
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>usePlatformMBeanServer</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>org.apache.camel.jmx.usePlatformMBeanServer</tt> 
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt>, 
<tt>true</tt> - Release 1.5 or later </td><td colspan="1" rowspan="1" 
class="confluenceTd"> If <tt>true</tt>, it 
 will use the <tt>MBeanServer</tt> from the JVM </td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"> <tt>mbeanServerDefaultDomain</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> 
<tt>org.apache.camel.jmx.mbeanServerDefaultDomain</tt> </td><td colspan="1" 
rowspan="1" class="confluenceTd"> <tt>org.apache.camel</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> The default JMX domain of the 
<tt>MBeanServer</tt> </td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>mbeanObjectDomainName</tt> </td><td colspan="1" 
rowspan="1" class="confluenceTd"> 
<tt>org.apache.camel.jmx.mbeanObjectDomainName</tt> </td><td colspan="1" 
rowspan="1" class="confluenceTd"> <tt>org.apache.camel</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> The JMX domain that all object 
names will use </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>createConnector</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>org.apache.camel.jmx.cr
 eateRmiConnect</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If we 
should create a JMX connector (to allow remote management) for the 
<tt>MBeanServer</tt> </td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>registryPort</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>org.apache.camel.jmx.rmiConnector.registryPort</tt> 
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1099</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> The port that the JMX RMI 
registry will use </td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>connectorPort</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>org.apache.camel.jmx.rmiConnector.connectorPort</tt> 
</td><td colspan="1" rowspan="1" class="confluenceTd"> -1 (dynamic) </td><td 
colspan="1" rowspan="1" class="confluenceTd"> The port that the JMX RMI server 
will use </td></tr><tr><td colspan="1"
  rowspan="1" class="confluenceTd"> <tt>serviceUrlPath</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> 
<tt>org.apache.camel.jmx.serviceUrlPath</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>/jmxrmi/camel</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> The path that JMX connector will be registered under 
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>onlyRegisterProcessorWithCustomId</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> 
<tt>org.apache.camel.jmx.onlyRegisterProcessorWithCustomId</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.0:</b> If this option 
is enabled then only processors with a custom id set will be registered. This 
allows you to filer out unwanted processors in the JMX console. 
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>statisticsLevel</tt> </td><td colspan="1" rowspan="1" clas
 s="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"> 
<tt>All</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 
2.1:</b> Configures the level for whether performance statistics is enabled for 
the MBean. See section <em>Configuring level of granularity for performance 
statistics</em> for more details. </td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>includeHostName</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>org.apache.camel.jmx.includeHostName</tt> </td><td 
colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" 
rowspan="1" class="confluenceTd"> <b>Camel 2.13:</b> Whether to include the 
hostname in the MBean naming. From Camel 2.13 onwards this is default 
<tt>false</tt>, where as in older releases its default <tt>true</tt>. You can 
use this option to restore old behavior if really needed. 
</td></tr></tbody></table>
 </div>
 
 


Reply via email to