[jboss-cvs] JBoss Messaging SVN: r7915 - projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Dec 2 02:33:19 EST 2009
Author: laubai
Date: 2009-12-02 02:33:19 -0500 (Wed, 02 Dec 2009)
New Revision: 7915
Modified:
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/Book_Info.xml
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/Revision_History.xml
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/configuration.xml
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/recovery_config.xml
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/runningexamples.xml
Log:
Added changes for JBPAPP-3200.
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/Book_Info.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/Book_Info.xml 2009-12-02 07:24:14 UTC (rev 7914)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/Book_Info.xml 2009-12-02 07:33:19 UTC (rev 7915)
@@ -6,7 +6,7 @@
<title>JBoss Messaging User Guide CP07</title>
<subtitle>for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 7</subtitle>
<edition>1.0</edition>
- <pubsnumber>5</pubsnumber>
+ <pubsnumber>6</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
<productnumber>4.3</productnumber>
<abstract><para>This book is about JBoss Messaging 1.4</para></abstract>
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/Revision_History.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/Revision_History.xml 2009-12-02 07:24:14 UTC (rev 7914)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/Revision_History.xml 2009-12-02 07:33:19 UTC (rev 7915)
@@ -7,8 +7,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>1.0</revnumber>
- <date>Thu Nov 19 2009</date>
+ <revnumber>1.1</revnumber>
+ <date>Wed Dec 02 2009</date>
<author>
<firstname>Laura</firstname>
<surname>Bailey</surname>
@@ -16,7 +16,7 @@
</author>
<revdescription>
<simplelist>
- <member>Initial draft.</member>
+ <member>Corrections for JBPAPP-3200.</member>
</simplelist>
</revdescription>
</revision>
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/configuration.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/configuration.xml 2009-12-02 07:24:14 UTC (rev 7914)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/configuration.xml 2009-12-02 07:33:19 UTC (rev 7915)
@@ -67,16 +67,20 @@
<!-- The default Dead Letter Queue (DLQ) to use for destinations.
This can be overridden on a per destinatin basis -->
- <attribute name="DefaultDLQ">jboss.messaging.destination:service=Queue,name=DLQ</attribute>
+ <attribute name="DefaultDLQ">
+ jboss.messaging.destination:service=Queue,name=DLQ
+ </attribute>
<!-- The default maximum number of times to attempt delivery of a message before sending to the DLQ (if configured).
- This can be overridden on a per destinatin basis -->
+ This can be overridden on a per destination basis -->
<attribute name="DefaultMaxDeliveryAttempts">10</attribute>
<!-- The default Expiry Queue to use for destinations. This can be overridden on a per destinatin basis -->
- <attribute name="DefaultExpiryQueue">jboss.messaging.destination:service=Queue,name=ExpiryQueue</attribute>
+ <attribute name="DefaultExpiryQueue">
+ jboss.messaging.destination:service=Queue,name=ExpiryQueue
+ </attribute>
<!-- The default redelivery delay to impose. This can be overridden on a per destination basis -->
@@ -102,7 +106,9 @@
<!-- The name of the connection factory to use for creating connections between nodes to pull messages -->
- <attribute name="ClusterPullConnectionFactoryName">jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory</attribute>
+ <attribute name="ClusterPullConnectionFactoryName">
+ jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory
+ </attribute>
<!-- When redistributing messages in the cluster. Do we need to preserve the order of messages received
by a particular consumer from a particular producer? -->
@@ -555,7 +561,7 @@
<para>If the database you want to switch to is one of MySQL, Oracle,
PostgreSQL, MS SQL Sever or Sybase, persistence configuration files are
- already available in the <filename>examples/config</filename> directory of
+ already available in the <filename>jboss-as/docs/examples/jms</filename> directory of
the release bundle.</para>
<para>In order to enable support for one of these databases, just replace
@@ -960,7 +966,7 @@
<filename>postgres-persistence-service.xml</filename>,
<filename>sybase-persistence-service.xml</filename>,
<filename>mssql-persistence-service.xml</filename> and <filename>db2-persistence-service.xml</filename> configuration files are
- available in the <filename>examples/config</filename> directory of the
+ available in the <filename>jboss-as/docs/examples/jms</filename> directory of the
release bundle.</para>
<para>Users are encouraged to contribute their own configuration files
@@ -2029,7 +2035,7 @@
<para>It is also possible to create an entirely new service deployment
descriptor <filename>xxx-service.xml</filename> altogether and deploy it
- in <filename>$JBOSS_HOME/server/messaging/deploy</filename>.</para>
+ in <filename>$JBOSS_HOME/server/<your profile>/deploy</filename>.</para>
<para>Connection factories can support automatic failover and/or
load-balancing by setting the corresponding attributes</para>
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/recovery_config.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/recovery_config.xml 2009-12-02 07:24:14 UTC (rev 7914)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/recovery_config.xml 2009-12-02 07:33:19 UTC (rev 7915)
@@ -2,8 +2,7 @@
<chapter id="recovery">
<title>JBoss Messaging XA Recovery Configuration</title>
- <para>This section describes how to configure JBoss Transactions in JBoss AS
- 4.2.0 to handle XA recovery for JBoss Messaging resources.</para>
+ <para>This section describes how to configure JBoss Transactions to handle XA recovery for JBoss Messaging resources.</para>
<para>JBoss Transactions recovery manager can easily be configured to
continually poll for and recover JBoss Messaging XA resources, this provides
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/runningexamples.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/runningexamples.xml 2009-12-02 07:24:14 UTC (rev 7914)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/runningexamples.xml 2009-12-02 07:33:19 UTC (rev 7915)
@@ -2,77 +2,83 @@
<chapter id="examples">
<title>Running the Examples</title>
- <para>In the directory <literal>docs/examples</literal>, you will find a set
+ <para>In the directory <literal>docs/examples/jboss-messaging-examples</literal>, you will find a set
of examples demonstrating JBoss Messaging working in various examples.
</para>
-<para>Before running these examples, you must deploy the example-destinations located under <filename>/docs/examples/destinations</filename></para>
+<para>Before running these examples, you must deploy the example-destinations located under <filename>/docs/examples/jboss-messaging-examples/destinations</filename></para>
<para>Examples list:
<itemizedlist>
<listitem>
- <para>docs/example/queue</para>
+ <para>docs/examples/jboss-messaging-examples/queue</para>
<para>This example shows a simple send and receive to a remote queue
using a JMS client</para>
</listitem>
+
+ <listitem>
+ <para>docs/examples/jboss-messaging-examples/queue-failover</para>
+
+ <para>This example demonstrates the transparent failover of a JMS consumer.</para>
+ </listitem>
<listitem>
- <para>docs/example/topic</para>
+ <para>docs/examples/jboss-messaging-examples/topic</para>
<para>This example shows a simple send and receive to a remote topic
using a JMS client</para>
</listitem>
<listitem>
- <para>docs/example/mdb</para>
+ <para>docs/examples/jboss-messaging-examples/mdb</para>
<para>This example demonstrates usage of an EJB2.1 MDB with JBoss
Messaging</para>
</listitem>
<listitem>
- <para>docs/example/ejb3mdb</para>
+ <para>docs/examples/jboss-messaging-examples/ejb3mdb</para>
<para>This example demonstrates usage of an EJB3 MDB with JBoss
Messaging</para>
</listitem>
<listitem>
- <para>docs/example/stateless</para>
+ <para>docs/examples/jboss-messaging-examples/stateless</para>
<para>This example demonstrates an EJB2.1 stateless session bean
interacting with JBoss Messaging</para>
</listitem>
<listitem>
- <para>docs/example/mdb-failure</para>
+ <para>docs/examples/jboss-messaging-examples/mdb-failure</para>
<para>This example demonstrates rollback and redelivery occuring with
an EJB2.1 MDB</para>
</listitem>
<listitem>
- <para>docs/example/secure-socket</para>
+ <para>docs/examples/jboss-messaging-examples/secure-socket</para>
<para>This example demonstrates a JMS client interacting with a JBoss
Messaging server using SSL encrypted transport</para>
</listitem>
<listitem>
- <para>docs/example/http</para>
+ <para>docs/examples/jboss-messaging-examples/http</para>
<para>This example demonstrates a JMS client interacting with a JBoss
Messaging server tunneling traffic over the HTTP protocol</para>
</listitem>
<listitem>
- <para>docs/example/web-service</para>
+ <para>docs/examples/jboss-messaging-examples/web-service</para>
<para>This example demonstrates JBoss web-service interacting with
JBoss Messaging</para>
</listitem>
<listitem>
- <para>docs/example/distributed-queue</para>
+ <para>docs/examples/jboss-messaging-examples/distributed-queue</para>
<para>This example demonstrates a JMS client interacting with a JBoss
Messaging distributed queue - it requires two JBoss AS instances to be
@@ -80,7 +86,7 @@
</listitem>
<listitem>
- <para>docs/example/distributed-topic</para>
+ <para>docs/examples/jboss-messaging-examples/distributed-topic</para>
<para>This example demonstrates a JMS client interacting with a JBoss
Messaging distributed topic - it requires two JBoss AS instances to be
@@ -88,7 +94,7 @@
</listitem>
<listitem>
- <para>docs/example/stateless-clustered</para>
+ <para>docs/examples/jboss-messaging-examples/stateless-clustered</para>
<para>This example demonstrates a JMS client interacting with
clustered EJB2.1 stateless session bean, which in turn interacts with
@@ -97,7 +103,7 @@
</listitem>
<listitem>
- <para>docs/example/bridge</para>
+ <para>docs/examples/jboss-messaging-examples/bridge</para>
<para>This example demonstrates using a message bridge. It deploys a
message bridge in JBoss AS which then proceeds to move messages from a
@@ -105,7 +111,7 @@
</listitem>
<listitem>
- <para>docs/example/servlet</para>
+ <para>docs/examples/jboss-messaging-examples/servlet</para>
<para>This example demonstrates how to use servlet transport with JBoss Messaging.
It deploys a servlet and a ConnectionFactory that uses the servlet transport.
@@ -113,7 +119,7 @@
</listitem>
<listitem>
- <para>docs/example/ordering-group</para>
+ <para>docs/examples/jboss-messaging-examples/ordering-group</para>
<para>This example demonstrates using strict message ordering with JBoss Messaging.
It uses JBoss Messaging ordering group API to deliver strictly ordered messages, regardless of
More information about the jboss-cvs-commits
mailing list