[jboss-cvs] JBossAS SVN: r100844 - projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Feb 10 20:07:39 EST 2010
Author: laubai
Date: 2010-02-10 20:07:38 -0500 (Wed, 10 Feb 2010)
New Revision: 100844
Modified:
projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Remoting.xml
Log:
Updated Admin and Config Guide.
Modified: projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Remoting.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Remoting.xml 2010-02-11 00:51:58 UTC (rev 100843)
+++ projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Remoting.xml 2010-02-11 01:07:38 UTC (rev 100844)
@@ -66,7 +66,7 @@
<section>
<title>MBeans</title>
- <para>In the HornetQ JMS subsystem, a Remoting server is
+ <para>In the JBoss Messaging JMS subsystem, a Remoting server is
configured in the file remoting-bisocket-service.xml, which, in abbreviated
form, looks like </para>
@@ -101,7 +101,7 @@
<para>it runs on port 4457 of host ${jboss.bind.address}; and</para>
</listitem>
<listitem>
- <para>HornetQ uses its own marshalling algorithm.</para>
+ <para>JBoss Messaging uses its own marshalling algorithm.</para>
</listitem>
</itemizedlist>
@@ -127,16 +127,16 @@
POJO:</para>
<programlisting>
- <bean name="HornetQConnector" class="org.jboss.remoting.transport.Connector">
+ <bean name="JBMConnector" class="org.jboss.remoting.transport.Connector">
<annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX
(name="jboss.messaging:service=Connector,transport=bisocket",
exposedInterface=org.jboss.remoting.transport.ConnectorMBean.class,
registerDirectly=true)</annotation>
- <property name="serverConfiguration"><inject bean="HornetQConfiguration"/></property>
+ <property name="serverConfiguration"><inject bean="JBMConfiguration"/></property>
</bean>
<!-- Remoting server configuration -->
- <bean name="HornetQConfiguration" class="org.jboss.remoting.ServerConfiguration">
+ <bean name="JBMConfiguration" class="org.jboss.remoting.ServerConfiguration">
<constructor>
<parameter>bisocket</parameter>
</constructor>
@@ -148,7 +148,7 @@
<key>serverBindAddress</key>
<value>
<value-factory bean="ServiceBindingManager" method="getStringBinding">
- <parameter>HornetQConnector</parameter>
+ <parameter>JBMConnector</parameter>
<parameter>${host}</parameter>
</value-factory>
</value>
@@ -157,7 +157,7 @@
<key>serverBindPort</key>
<value>
<value-factory bean="ServiceBindingManager" method="getStringBinding">
- <parameter>HornetQConnector</parameter>
+ <parameter>JBMConnector</parameter>
<parameter>${port}</parameter>
</value-factory>
</value>
@@ -180,13 +180,13 @@
</programlisting>
<para>In this version, the configuration information is expressed in the
- HornetQConfiguration <classname>ServerConfiguration</classname> POJO, which
- is then injected into the HornetQConnector
+ JBMConfiguration <classname>ServerConfiguration</classname> POJO, which
+ is then injected into the JBMConnector
<classname>org.jboss.remoting.transport.Connector</classname> POJO.
The syntax is that of the Microcontainer, which is beyond the scope of this chapter. See <xref linkend="microcontainer"/> for details. One variation from the MBean version is the use of the
ServiceBindingManager, which is also beyond the scope of this chapter. Note
that the @org.jboss.aop.microcontainer.aspects.jmx.JMX annotation causes the
- HornetQConnector to be visible as an MBean named
+ JBMConnector to be visible as an MBean named
"jboss.messaging:service=Connector,transport=bisocket".</para>
</section>
@@ -203,7 +203,7 @@
<constructor>
<parameter class="java.lang.String">
<value-factory bean="ServiceBindingManager" method="getStringBinding">
- <parameter>HornetQConnector:bindingHome1</parameter>
+ <parameter>JBMConnector:bindingHome1</parameter>
<parameter>${host}:${port}</parameter>
</value-factory>
</parameter>
@@ -215,7 +215,7 @@
<factory bean="homes1"/>
<parameter>
<value-factory bean="ServiceBindingManager" method="getStringBinding">
- <parameter>HornetQConnector:bindingHome2</parameter>
+ <parameter>JBMConnector:bindingHome2</parameter>
<parameter>!${host}:${port}</parameter>
</value-factory>
</parameter>
@@ -224,7 +224,7 @@
</programlisting>
<para>which results in a StringBuffer with a value something like (according
- to the ServiceBindingManager configuration values for HornetQConnector:bindingHome1 and HornetQConnector:bindingHome2)
+ to the ServiceBindingManager configuration values for JBMConnector:bindingHome1 and JBMConnector:bindingHome2)
"external.acme.com:5555!internal.acme.com:4444", and (2) replacing the
"serverBindAddress" and "serverBindPort" parameters with</para>
@@ -237,7 +237,7 @@
<para>which transforms the StringBuffer into the String
"external.acme.com:5555!internal.acme.com:4444" and injects it into the
- HornetQConnector. The resulting InvokerLocator will look like</para>
+ JBMConnector. The resulting InvokerLocator will look like</para>
<programlisting>
bisocket://multihome/?homes=external.acme.com:5555!internal.acme.com:
@@ -269,7 +269,7 @@
<para>EJB2: ${JBOSS_HOME}/server/${CONFIG}/deploy/remoting-jboss-beans.xml</para>
<para>EJB3: ${JBOSS_HOME}/server/${CONFIG}/deploy/ejb3-connectors-jboss-beans.xml</para>
- <para>HornetQ: ${JBOSS_HOME}/server/${CONFIG}/deploy/messaging/remoting-bisocket-service.xml</para>
+ <para>JBM: ${JBOSS_HOME}/server/${CONFIG}/deploy/messaging/remoting-bisocket-service.xml</para>
</section>
<section>
More information about the jboss-cvs-commits
mailing list