From 7dc8fbaa932be6ce2c57759f3ac897d9a065d355 Mon Sep 17 00:00:00 2001 From: Dave Syer Date: Fri, 12 Nov 2010 15:55:20 +0000 Subject: [PATCH] INT-1420: fix CDATA --- docs/src/reference/docbook/control-bus.xml | 15 +++++---- docs/src/reference/docbook/groovy.xml | 3 +- docs/src/reference/docbook/jmx.xml | 39 +++++----------------- 3 files changed, 20 insertions(+), 37 deletions(-) diff --git a/docs/src/reference/docbook/control-bus.xml b/docs/src/reference/docbook/control-bus.xml index 0038cf3830..b56ac4931b 100644 --- a/docs/src/reference/docbook/control-bus.xml +++ b/docs/src/reference/docbook/control-bus.xml @@ -1,6 +1,10 @@ -
+
Control Bus As described in (EIP), the idea behind the Control Bus is that @@ -8,11 +12,10 @@ the components within the framework as is used for "application-level" messaging. In Spring Integration we build upon the adapters described above so that it's possible to send Messages - as a means of invoking exposed operations. - - ]]> + as a means of invoking exposed operations. - + ]]> The Control Bus has an input channel that can be accessed for invoking operations on the beans in the application context. It diff --git a/docs/src/reference/docbook/groovy.xml b/docs/src/reference/docbook/groovy.xml index bfe5e062c6..93b78d872b 100644 --- a/docs/src/reference/docbook/groovy.xml +++ b/docs/src/reference/docbook/groovy.xml @@ -71,7 +71,8 @@ monitoring and managing the components within the framework as is used for "application-level" messaging. In Spring Integration we build upon the adapters described above so that it's possible to send Messages as a means - of invoking exposed operations. <groovy:control-bus input-channel="operationChannel"/> + of invoking exposed operations. + <groovy:control-bus input-channel="operationChannel"/> The Control Bus has an input channel that can be accessed for invoking operations on the beans in the application context. diff --git a/docs/src/reference/docbook/jmx.xml b/docs/src/reference/docbook/jmx.xml index f1e0176158..2b5cc0d566 100644 --- a/docs/src/reference/docbook/jmx.xml +++ b/docs/src/reference/docbook/jmx.xml @@ -144,7 +144,7 @@ create an instance of the IntegrationMBeanExporter, define a bean and provide a reference to an MBeanServer and a domain name (if desired). The domain can be left out in which case the default domain - is "org.springframework.integration". <jmx:mbean-exporter domain="my.company.domain" mbean-server="mbeanServer"/> + is "org.springframework.integration". <jmx:mbean-exporter default-domain="my.company.domain" server="mbeanServer"/> <bean id="mbeanServer" class="org.springframework.jmx.support.MBeanServerFactoryBean"> <property name="locateExistingServerIfPossible" value="true"/> @@ -155,36 +155,15 @@ can expose the exporter itself, and certain other components in Spring Integration, using the standard <context:mbean-export/> tag. + +
+ MBean Features + + All the MessageChannel, MessageHandler and MessageSource + instances in the application are wrapped by the MBean exporter to + provide management and monitoring features.
-
- Control Bus - - As described in (EIP), the idea - behind the Control Bus is that the same messaging system can be used for - monitoring and managing the components within the framework as is used for - "application-level" messaging. In Spring Integration we build upon the - adapters described above so that it's possible to send Messages as a means - of invoking exposed operations. Internally, the Control Bus uses a Spring - MBeanExporter instance to expose the various endpoints and channels. To - create an instance of the Control Bus, define a bean and provide a - reference to an MBeanServer and a domain name. <jmx:control-bus mbean-exporter="mbeanExporter" operation-channel="operationChannel"/> - - <jmx:mbean-exporter id="mbeanExporter" mbean-server="mbeanServer"/> - - - The Control Bus has an "operationChannel" that can be accessed for - invoking operations on the MBeans that it has exported. This will also be - covered by namespace support soon to make it easier to configure - references to that channel for other producers. We will likely add some - other channels for notifications and attribute polling as well. - - The Control Bus functionality is a work in progress. At this time, - one can perform some basic monitoring of Message Channels and/or invoke - Lifecycle operations (start/stop) on Message Endpoints. Now that the - foundation is available, however, we will be able to extend the attributes - and operations that are being exposed.
+