[jboss-cvs] JBoss Messaging SVN: r7992 - projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: laubai
Date: 2010-03-30 20:20:58 -0400 (Tue, 30 Mar 2010)
New Revision: 7992

Modified:
   projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US/JBoss_Messaging_User_Guide_CP07.xml
   projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US/configuration.xml
Log:
JBPAPP-2059 Added system properties section to JBoss Messaging User Guide.

Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US/JBoss_Messaging_User_Guide_CP07.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US/JBoss_Messaging_User_Guide_CP07.xml	2010-03-30 11:13:47 UTC (rev 7991)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US/JBoss_Messaging_User_Guide_CP07.xml	2010-03-31 00:20:58 UTC (rev 7992)
@@ -6,7 +6,7 @@
 	<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
 <!--	<xi:include href="About_This_Book.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
 	<xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-	<xi:include href="gettingstarted.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<!--	<xi:include href="gettingstarted.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />-->
 <!--	<xi:include href="Important_Features.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
 <!--	<xi:include href="installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
 	<xi:include href="runningexamples.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />

Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US/configuration.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US/configuration.xml	2010-03-30 11:13:47 UTC (rev 7991)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_4_3_8/en-US/configuration.xml	2010-03-31 00:20:58 UTC (rev 7992)
@@ -20,7 +20,7 @@
   <filename>messaging-service.xml</filename>,
   <filename>remoting-bisocket-service.xml</filename>,
   <filename>xxx-persistence-service.xml</filename> (where xx is the name of
-  your database) , <filename>connection-factories-service.xml</filename> and
+  your database), <filename>connection-factories-service.xml</filename> and
   <filename>destinations-service.xml</filename>.</para>
 
   <para>The AOP client-side and server-side interceptor stacks are configured
@@ -31,7 +31,7 @@
   considered the security implications before removing the security
   interceptor.</para>
   
-  <warning><title>Clustering won't work with the default database.</title>
+  <warning><title>Clustering will not work with the default database.</title>
     <para>
       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
@@ -39,6 +39,30 @@
     </para>  
   </warning>
 
+  <section id="properties">
+    <title>System Properties used by JBoss Messaging</title>
+
+      <section id="properties.supportBytesId">
+        <title>support.bytesId</title>
+
+        <para>This system property controls the default behavior when constructing a JBossMessage object from a foreign message object. If set to true, the JBossMessage constructor
+        will try to extract the native byte[] correlation ID from the foreign message headers. If set to false, it will use the normal string type JMSCorrelationID. If this system property is absent or
+        is given some value other than 'true' and 'false', it will defaults to 'true'.</para>
+      </section>
+
+      <section id="properties.retainOldxabehaviour">
+      <title>retain.oldxabehaviour</title>
+
+        <para>This system property controls what kind of exception a JMS XAResource throws when the prepare is called after the connection is broken. If this property is not defined, an XAException with XA_RBCOMMFAIL error code will be thrown. If this propertie is defined, an XAException with XA_RETRY error code will be thrown instead. JBM by default doesn't define this property.</para>
+      </section>
+
+      <section id="properties.mapmessagesupportnullobject">
+      <title>mapmessage.support.null.object</title>
+
+        <para>This system property, once defined, allows null values in MapMessage.setObject(String key, Object value). JBM by default doesn't define this property, which means passing null values to the setObject() method will cause a MessageFormatException to be thrown.</para>
+      </section>
+  </section> 
+
   <section id="conf.serverpeer">
     <title>Configuring the ServerPeer</title>