[jboss-cvs] JBoss Messaging SVN: r6986 - trunk/docs/user-manual/en.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri May 22 03:49:13 EDT 2009
Author: ataylor
Date: 2009-05-22 03:49:13 -0400 (Fri, 22 May 2009)
New Revision: 6986
Modified:
trunk/docs/user-manual/en/appserver-integration.xml
Log:
more proof reading updates
Modified: trunk/docs/user-manual/en/appserver-integration.xml
===================================================================
--- trunk/docs/user-manual/en/appserver-integration.xml 2009-05-22 07:41:42 UTC (rev 6985)
+++ trunk/docs/user-manual/en/appserver-integration.xml 2009-05-22 07:49:13 UTC (rev 6986)
@@ -2,17 +2,18 @@
<chapter id="appserver-integration">
<title>Application Server Integration and JavaEE</title>
<para>JBM is fully integrated with the JBoss Application Server version 5.1. For details on
- installing JBM in the AS refer to Quick Start guide.</para>
+ installing JBM in the Application Server refer to Quick Start guide.</para>
<para>This section explains the basics behind configuring the different JEE components in the
AS.</para>
<section>
<title>Using and Configuring the JCA Adapter</title>
<para>The Java Connector Architecture (JCA) Adapter is what allows JBM to be integrated with
JEE components such as MDB's and EJB's. It configures how components such as MDB's
- consume messages from the JBM server and also how components can send messages.</para>
+ consume messages from the JBM server and also how components such as EJB's or Servlet's
+ can send messages.</para>
<para>The JBM JCA adapter is deployed via the <literal>jms-ra.rar</literal> archive. The
- configuration of the Adapter is found in this archive under <literal
- >META-INF/ra.xml</literal>.</para>
+ configuration of the Adapter is found in this archive under
+ <literal>META-INF/ra.xml</literal>.</para>
<para>The configuration will look something like the following:</para>
<programlisting><resourceadapter>
<resourceadapter-class>org.jboss.messaging.ra.JBMResourceAdapter</resourceadapter
@@ -315,11 +316,11 @@
<para>The outbound configuration should remain unchanged as they define Connection
Factories that are used by EE components. These Connection Factories can be defined
inside a configuration file that matches the name <literal>*-ds.xml</literal>.
- You'll find a default <literal>jms-ds.xml</literal> configuration under the <literal
- >messaging.sar</literal> directory in the Jboss AS deployment. the connection
- factories defined in the config file inherit their properties from the main <literal
- >ra.xml</literal> config but can also be overridden, the following example show
- how to define one.</para>
+ You'll find a default <literal>jms-ds.xml</literal> configuration under the
+ <literal>messaging.sar</literal> directory in the Jboss AS deployment. the
+ connection factories defined in the config file inherit their properties from the
+ main <literal>ra.xml</literal> config but can also be overridden, the following
+ example show how to define one.</para>
<programlisting><tx-connection-factory>
<jndi-name>RemoteJmsXA</jndi-name>
<xa-transaction/>
@@ -394,12 +395,12 @@
}
}
}</programlisting>
- <para>In this example we have configured the MDB to consume from the queue named <literal
- >queue/testQueue</literal>. It is also possible to override properties for the
- inbound resource adapter here is well. Here the MDB is configured to connect to a
+ <para>In this example we have configured the MDB to consume from the queue named
+ <literal>queue/testQueue</literal>. It is also possible to override properties for
+ the inbound resource adapter here is well. Here the MDB is configured to connect to a
different server.</para>
- <para>It is alsp possible to define these properties in the <literal>web.xml</literal>
- confid file. Refer to the JBoss AS documentation on how to do this.</para>
+ <para>It is also possible to define these properties in the <literal>web.xml</literal>
+ deployment descriptor. Refer to the JBoss AS documentation on how to do this.</para>
</section>
<section>
<title>High Availability JNDI (HAJNDI)</title>
@@ -415,7 +416,7 @@
initialContext = new InitialContext(jndiParameters);</programlisting>
<para>For more information visit <ulink
url="http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Clustering_Guide/5/html/clustering-jndi.html"
- /></para>
+ >here</ulink></para>
</section>
<section>
<title>The JMS Bridge</title>
@@ -555,24 +556,24 @@
of its constructor parameters in order follows:</para>
<itemizedlist>
<listitem>
- <para>Source Connection Factory Factory - This injects the <literal
- >SourceCFF</literal> bean that is the connection factory defined later in
- the beans file.</para>
+ <para>Source Connection Factory Factory - This injects the
+ <literal>SourceCFF</literal> bean that is the connection factory defined
+ later in the beans file.</para>
</listitem>
<listitem>
- <para>Target Connection Factory Factory - This injects the <literal
- >TargetCFF</literal> bean that is the connection factory defined later in
- the beans file.</para>
+ <para>Target Connection Factory Factory - This injects the
+ <literal>TargetCFF</literal> bean that is the connection factory defined
+ later in the beans file.</para>
</listitem>
<listitem>
- <para>Source Destination Factory Factory - This injects the <literal
- >SourceDestinationFactory</literal> bean that is used to create or lookup
- the sourcedestination.</para>
+ <para>Source Destination Factory Factory - This injects the
+ <literal>SourceDestinationFactory</literal> bean that is used to create or
+ lookup the sourcedestination.</para>
</listitem>
<listitem>
- <para>Target Destination Factory Factory - This injects the <literal
- >TargetDestinationFactory</literal> bean that is used to create or lookup
- the target destination.</para>
+ <para>Target Destination Factory Factory - This injects the
+ <literal>TargetDestinationFactory</literal> bean that is used to create or
+ lookup the target destination.</para>
</listitem>
<listitem>
<para>Source User Name - the user name to use for the source connection.</para>
@@ -615,9 +616,9 @@
</listitem>
<listitem>
<para>Concatenate Message ID - If this is set the message ID from the received
- message will be concatenated as message header <literal
- >JBM_BRIDGE_MSG_ID_LIST</literal>. This is because it will change once the
- bridge forwards it. When passing through multiple bridges each ID is
+ message will be concatenated as message header
+ <literal>JBM_BRIDGE_MSG_ID_LIST</literal>. This is because it will change
+ once the bridge forwards it. When passing through multiple bridges each ID is
concatenated to the list.</para>
<note>
<para>when you receive the message you can send back a response using the
@@ -634,14 +635,15 @@
<para>In this example we have used the default provided by JBM that look up the
connection factory using JNDI. For other Application Servers or JMS providers a new
implementation may have to be provided. This can easily be done by implementing the
- interface <literal
- >org.jboss.messaging.jms.bridge.ConnectionFactoryFactory</literal>.</para>
+ interface
+ <literal>org.jboss.messaging.jms.bridge.ConnectionFactoryFactory</literal>.</para>
</section>
<section>
<title>Source and Target Destination Factories</title>
<para>Again, similarly, these are used to create or lookup up the destinations. To
- provid a new implementation simple implement <literal
- >org.jboss.messaging.jms.bridge.DestinationFactory</literal> interface.</para>
+ provide a new implementation simple implement
+ <literal>org.jboss.messaging.jms.bridge.DestinationFactory</literal>
+ interface.</para>
</section>
<section>
<title>Quality Of Service</title>
@@ -728,10 +730,10 @@
</properties>
</programlisting>
<para>This informs the recovery manager that it can recovers JBoss Messaging XA
- Resources using the <literal>XAConnectionFactory</literal> bound to <literal
- >java:/XAConnectionFactory</literal> in JNDI. A ConnectionFactory must have been
- configured with this JNDI name in <literal>jbm-jms.xml</literal> (see <xref
- linkend="using-jms.server.configuration"/>).</para>
+ Resources using the <literal>XAConnectionFactory</literal> bound to
+ <literal>java:/XAConnectionFactory</literal> in JNDI. A ConnectionFactory must
+ have been configured with this JNDI name in <literal>jbm-jms.xml</literal> (see
+ <xref linkend="using-jms.server.configuration"/>).</para>
</section>
<section>
<title>Example</title>
More information about the jboss-cvs-commits
mailing list