Spring/spring-integration
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

INT-1239, updated the docs to reflect INT-1240 change for 'operation-name' and 'object-name' attributes

Browse Source
This commit is contained in:
Oleg Zhurakousky
2010-07-19 12:28:38 +00:00
parent c2f526586a
commit d348f353b1
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/docbkx/jmx.xml
View File

@@ -106,8 +106,8 @@
any managed operation exposed by an MBean. Each invocation requires the
operation name to be invoked and the ObjectName of the target MBean. Both of these must be explicitly provided via adapter configuration:
<programlisting language="xml"><![CDATA[ <jmx:operation-invoking-channel-adapter id="adapter"
default-object-name="example.domain:name=TestBean"
default-operation-name="ping"/>
object-name="example.domain:name=TestBean"
operation-name="ping"/>
]]></programlisting>
Then the adapter only needs to be able to discover the "mbeanServer" bean. If
a different bean name is required, then provide the "mbean-server" attribute
@@ -135,8 +135,8 @@
Such return value will be sent as message payload to the 'reply-channel' specified by this Gateway.
<programlisting language="xml"><![CDATA[ <jmx:operation-invoking-outbound-gateway request-channel="requestChannel"
reply-channel="replyChannel"
default-object-name="org.springframework.integration.jmx.config:type=TestBean,name=testBeanGateway"
default-operation-name="testWithReturn"/>
object-name="org.springframework.integration.jmx.config:type=TestBean,name=testBeanGateway"
operation-name="testWithReturn"/>
]]></programlisting>
Another way of provideing the 'reply-channel' is by setting <interfacename>MessageHeaders.REPLY_CHANNEL</interfacename> Message Header
</para>