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 2012/11/02 15:18:13 UTC

svn commit: r837026 - in /websites/production/camel/content: cache/main.pageCache controlbus.html

Author: buildbot
Date: Fri Nov  2 14:18:12 2012
New Revision: 837026

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/controlbus.html

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

Modified: websites/production/camel/content/controlbus.html
==============================================================================
--- websites/production/camel/content/controlbus.html (original)
+++ websites/production/camel/content/controlbus.html Fri Nov  2 14:18:12 2012
@@ -76,13 +76,13 @@
         <tr>
         <td valign="top" width="100%">
 <div class="wiki-content maincontent"><h3><a shape="rect" name="ControlBus-ControlBus"></a>ControlBus</h3>
-<p>The <a shape="rect" class="external-link" href="http://www.eaipatterns.com/ControlBus.html" rel="nofollow">Control Bus</a> from the <a shape="rect" href="enterprise-integration-patterns.html" title="Enterprise Integration Patterns">EIP patterns</a> is that the integration system can be monitored and managed from within the framework. </p>
+<p>The <a shape="rect" class="external-link" href="http://www.eaipatterns.com/ControlBus.html" rel="nofollow">Control Bus</a> from the <a shape="rect" href="enterprise-integration-patterns.html" title="Enterprise Integration Patterns">EIP patterns</a> allows for the integration system to be monitored and managed from within the framework. </p>
 
 <p><span class="image-wrap" style=""><img src="http://www.eaipatterns.com/img/ControlBus.gif" style="border: 0px solid black"></span></p>
 
 <p>Use a Control Bus to manage an enterprise integration system. The Control Bus uses the same messaging mechanism used by the application data, but uses separate channels to transmit data that is relevant to the management of components involved in the message flow.</p>
 
-<p>In Camel you can manage and monitor using <a shape="rect" href="camel-jmx.html" title="Camel JMX">JMX</a>, or access the Java API from <tt>CamelContext</tt>, or from the <tt>org.apache.camel.api.management</tt> package,<br clear="none">
+<p>In Camel you can manage and monitor using <a shape="rect" href="camel-jmx.html" title="Camel JMX">JMX</a>, or by using a Java API from the <tt>CamelContext</tt>, or from the <tt>org.apache.camel.api.management</tt> package,<br clear="none">
 or use the event notifier which has an example <a shape="rect" href="eventnotifier-to-log-details-about-all-sent-exchanges.html" title="EventNotifier to log details about all sent Exchanges">here</a>.</p>
 
 <p>From Camel 2.11 onwards we have introduced a new <a shape="rect" href="controlbus-component.html" title="ControlBus Component">ControlBus Component</a> that allows you to send messages to a control bus <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> that reacts accordingly.</p>