[jboss-cvs] JBoss Messaging SVN: r7960 - 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
Tue Feb 23 21:23:20 EST 2010


Author: benlc
Date: 2010-02-23 21:23:20 -0500 (Tue, 23 Feb 2010)
New Revision: 7960

Modified:
   projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/configuration.xml
Log:
'changed wording for JBPAPP-3788' 


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	2010-02-24 01:36:01 UTC (rev 7959)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_7/en-US/configuration.xml	2010-02-24 02:23:20 UTC (rev 7960)
@@ -33,7 +33,9 @@
   
   <warning><title>Clustering won't work with the default database.</title>
     <para>
-      JBoss uses HSQLDB as the default database. This database is not production-ready. For a clustered installation, it is necessary that all nodes have access to a shared database. It is necessary to replace the default HSQLDB database with a production-ready shared database for clustering to work.
+      JBoss uses HSQLDB as the default database which is <emphasis>not</emphasis> a production-ready database. For a JBoss Messaging cluster to work, all nodes must have access to a production-ready 
+shared database. It is therefore necessary to replace the default HSQLDB database with a
+production-ready shared database.  
     </para>  
   </warning>
 




More information about the jboss-cvs-commits mailing list