[jboss-cvs] JBoss Messaging SVN: r7612 - trunk/docs/user-manual/en.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jul 27 10:43:26 EDT 2009
Author: ataylor
Date: 2009-07-27 10:43:26 -0400 (Mon, 27 Jul 2009)
New Revision: 7612
Modified:
trunk/docs/user-manual/en/appserver-integration.xml
Log:
DOC FIX
Modified: trunk/docs/user-manual/en/appserver-integration.xml
===================================================================
--- trunk/docs/user-manual/en/appserver-integration.xml 2009-07-27 14:42:27 UTC (rev 7611)
+++ trunk/docs/user-manual/en/appserver-integration.xml 2009-07-27 14:43:26 UTC (rev 7612)
@@ -14,8 +14,8 @@
<title>Configuring Message Driven Beans</title>
<para>The delivery of messages to an MDB using JBoss Messaging is configured on the JCA
Adapter via a configuration file <literal>ra.xml</literal> which can be found under in
- the <literal>jms-ra.rar</literal> archive of directory. By default this is configured
- to consume messages using an InVM connector from the instance of JBoss Messaging running
+ the <literal>jms-ra.rar</literal> archive of directory. By default this is configured to
+ consume messages using an InVM connector from the instance of JBoss Messaging running
within the application server. A full list of what is configurable is found later in
this chapter. </para>
<para>All MDB's however need to have the destination type and the destination configured.
@@ -34,9 +34,9 @@
mapped into JNDI with the binding <literal>queue/testQueue</literal>. This queue must be
preconfigured in the usual way using the JBoss Messaging configuration files.</para>
<section>
- <title>Using Container Managed Persistence</title>
- <para>When an MDB is using Container Managed Persistence, the delivery of the message is
- done within the scope of an XA transaction. The commit or rollback of this
+ <title>Using Container Managed Transactions</title>
+ <para>When an MDB is using Container Managed Transactions, the delivery of the message
+ is done within the scope of an XA transaction. The commit or rollback of this
transaction is controlled by the container itself. If the transaction is rolled back
then the JBoss Message delivery semantics will kick in (by default this is to try
and redeliver the message up to 10 times before sending to a DLQ). Using annotations
@@ -97,8 +97,8 @@
}</programlisting>
</section>
<section>
- <title>Using Bean Managed Persistence</title>
- <para>Message driven beans can also be configured to use Bean Managed Persistence. In
+ <title>Using Bean Managed Transactions</title>
+ <para>Message driven beans can also be configured to use Bean Managed Transactions. In
this case a User Transaction is created. This would be configured as follows:</para>
<programlisting>@MessageDriven(name = "MDB_BMPExample",
activationConfig =
@@ -1000,10 +1000,10 @@
(depending on the transaction outcome) when the server is restarted.</para>
<section>
<title>XA Recovery Configuration</title>
- <para>To enable JBoss Messagings XA Recovery, the Recovery Manager must be configured to connect
- to JBoss Messaging to recover its resources. The following property must be added to
- the <literal>jta</literal> section of <literal>conf/jbossts-properties.xml</literal>
- of JBoss AS profiles:</para>
+ <para>To enable JBoss Messagings XA Recovery, the Recovery Manager must be configured to
+ connect to JBoss Messaging to recover its resources. The following property must be
+ added to the <literal>jta</literal> section of <literal
+ >conf/jbossts-properties.xml</literal> of JBoss AS profiles:</para>
<programlisting>
<properties depends="arjuna" name="jta">
...
@@ -1012,29 +1012,36 @@
value="org.jboss.messaging.jms.server.recovery.MessagingXAResourceRecovery;[connection configuration]"/>
</properties>
</programlisting>
- <para>The <literal>[connection configuration]</literal> contains all the information required to connect to
- JBoss Messaging node under the form <literal>[connector factory class name],[user name], [password], [connector parameters]</literal>.
- </para>
+ <para>The <literal>[connection configuration]</literal> contains all the information
+ required to connect to JBoss Messaging node under the form <literal>[connector
+ factory class name],[user name], [password], [connector parameters]</literal>. </para>
<itemizedlist>
<listitem>
- <para><literal>[connector factory class name]</literal> corresponds to the name of the <literal>ConnectorFactory</literal> used
- to connect to JBoss Messaging. Values can be <literal>org.jboss.messaging.core.remoting.impl.invm.InVMConnectorFactory</literal>
- or <literal>org.jboss.messaging.integration.transports.netty.NettyConnectorFactory</literal></para>
+ <para><literal>[connector factory class name]</literal> corresponds to the name
+ of the <literal>ConnectorFactory</literal> used to connect to JBoss
+ Messaging. Values can be <literal
+ >org.jboss.messaging.core.remoting.impl.invm.InVMConnectorFactory</literal>
+ or <literal
+ >org.jboss.messaging.integration.transports.netty.NettyConnectorFactory</literal></para>
</listitem>
<listitem>
- <para><literal>[user name]</literal> is the user name to create a client session. It is optional</para>
+ <para><literal>[user name]</literal> is the user name to create a client
+ session. It is optional</para>
</listitem>
<listitem>
- <para><literal>[password]</literal> is the password to create a client session. It is mandatory only if the user name is specified</para>
+ <para><literal>[password]</literal> is the password to create a client session.
+ It is mandatory only if the user name is specified</para>
</listitem>
<listitem>
- <para><literal>[connector parameters]</literal> is a list of comma-separated key=value pair which are passed to the connector factory (see <xref
- linkend="configuring-transports"/> for a list of the transport parameters).</para>
+ <para><literal>[connector parameters]</literal> is a list of comma-separated
+ key=value pair which are passed to the connector factory (see <xref
+ linkend="configuring-transports"/> for a list of the transport
+ parameters).</para>
</listitem>
</itemizedlist>
<note>
- <para>JBoss Messaging must have a valid acceptor which corresponds to the connector
- specified in <literal>conf/jbossts-properties.xml</literal>.</para>
+ <para>JBoss Messaging must have a valid acceptor which corresponds to the connector
+ specified in <literal>conf/jbossts-properties.xml</literal>.</para>
</note>
<section>
<title>Configuration Settings</title>
@@ -1044,7 +1051,8 @@
<factory-class>org.jboss.messaging.core.remoting.impl.invm.InVMAcceptorFactory</factory-class>
</acceptor>
</programlisting>
- <para>the corresponding configuration in <literal>conf/jbossts-properties.xml</literal> is:</para>
+ <para>the corresponding configuration in <literal
+ >conf/jbossts-properties.xml</literal> is:</para>
<programlisting>
<property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1"
value="org.jboss.messaging.jms.server.recovery.MessagingXAResourceRecovery;org.jboss.messaging.core.remoting.impl.invm.InVMConnectorFactory"/>
@@ -1056,21 +1064,25 @@
<param key="jbm.remoting.netty.port" value="8888" type="Integer"/>
</acceptor>
</programlisting>
- <para>the corresponding configuration in <literal>conf/jbossts-properties.xml</literal> is:</para>
+ <para>the corresponding configuration in <literal
+ >conf/jbossts-properties.xml</literal> is:</para>
<programlisting>
<property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1"
value="org.jboss.messaging.jms.server.recovery.MessagingXAResourceRecovery;org.jboss.messaging.integration.transports.netty.NettyConnectorFactory, , , jbm.remoting.netty.port=8888"/>
</programlisting>
<note>
- <para>Note the additional commas to skip the user and password before connector parameters</para>
+ <para>Note the additional commas to skip the user and password before connector
+ parameters</para>
</note>
- <para>If the recovery must use <literal>admin, adminpass</literal>, the configuration would have been:</para>
+ <para>If the recovery must use <literal>admin, adminpass</literal>, the
+ configuration would have been:</para>
<programlisting>
<property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1"
value="org.jboss.messaging.jms.server.recovery.MessagingXAResourceRecovery;org.jboss.messaging.integration.transports.netty.NettyConnectorFactory, admin, adminpass, jbm.remoting.netty.port=8888"/>
- </programlisting>
- <para>Configuring JBoss Messaging with an invm acceptor and configuring the Recovery Manager with an invm connector is the recommended
- way to enable XA Recovery.</para>
+ </programlisting>
+ <para>Configuring JBoss Messaging with an invm acceptor and configuring the Recovery
+ Manager with an invm connector is the recommended way to enable XA
+ Recovery.</para>
</section>
</section>
<section>
More information about the jboss-cvs-commits
mailing list