[exo-jcr-commits] exo-jcr SVN: r5870 - in jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules: jcr and 1 other directory.

[do-not-reply at jboss.org]

Author: nfilotto
Date: 2012-03-16 07:58:28 -0400 (Fri, 16 Mar 2012)
New Revision: 5870

Modified:
   jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/faq/jcr-faq.xml
   jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/jbosscache-configuration-templates.xml
Log:
EXOJCR-1763: Doc updates

Modified: jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/faq/jcr-faq.xml
===================================================================
--- jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/faq/jcr-faq.xml	2012-03-15 12:32:14 UTC (rev 5869)
+++ jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/faq/jcr-faq.xml	2012-03-16 11:58:28 UTC (rev 5870)
@@ -322,14 +322,18 @@
 
               <listitem>
                 <para>"jgroups-configuration" is path to JGroups configuration
-                that is multiplexer stack is used (default). This file is also
+                that should not be anymore jgroups' stack definitions but a
+                normal jgroups configuration format with the shared transport
+                configured by simply setting the jgroups property
+                singleton_name to a unique name (it must remain unique from
+                one portal container to another). This file is also
                 pre-bundled with templates and is recommended for use;</para>
               </listitem>
 
               <listitem>
-                <para>"jgroups-multiplexer-stack" set to "false" with the
-                jgroups configuration with the shared transport enabled in
-                order to use the shared transport.</para>
+                <para>"jgroups-multiplexer-stack" set to "false" in order to
+                disable the multiplexer stack as now it is recommended to use
+                the JGroups' shared transport instead.</para>
               </listitem>
 
               <listitem>

Modified: jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/jbosscache-configuration-templates.xml
===================================================================
--- jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/jbosscache-configuration-templates.xml	2012-03-15 12:32:14 UTC (rev 5869)
+++ jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/jbosscache-configuration-templates.xml	2012-03-16 11:58:28 UTC (rev 5870)
@@ -6,8 +6,9 @@
 
   <title>JBoss Cache configuration</title>
 
-  <para>This chapter will show you how to use and configure Jboss Cache in the clustered environment.
-  Also, you will know how to use a template-based configuration offered by eXo JCR for JBoss Cache instances.</para>
+  <para>This chapter will show you how to use and configure Jboss Cache in the
+  clustered environment. Also, you will know how to use a template-based
+  configuration offered by eXo JCR for JBoss Cache instances.</para>
 
   <section id="JCR.JBossCacheConfigurationTemplates.JBoss_Cache_Config_for_Indexer">
     <title>JBoss cache configuration for indexer, lock manager and data
@@ -65,7 +66,7 @@
     channel for set of clusters. This feature reduces network overheads and
     increase performance and stability of application. To enable multiplexer
     stack, you should define appropriate configuration file (upd-mux.xml is
-    pre-shipped one with eXo JCR) and set "jgroups-multiplexer-stack" into
+    pre-shipped one with eXo JCR) and set "jgroups-multiplexer-stack" to
     "true".</para>
 
     <programlisting language="xml">&lt;property name="jgroups-configuration" value="jar:/conf/portal/udp-mux.xml" /&gt;
@@ -73,9 +74,14 @@
 
     <para>I<emphasis>t is now highly recommended to use the shared transport
     instead of the multiplexer</emphasis>, to do so simply disable the
-    multiplexer stack in the configuration of each component then set the
-    property <emphasis>singleton_name</emphasis> of your JGroups configuration
-    to a unique name.</para>
+    multiplexer stack in the configuration of each component by setting the
+    property <emphasis>jgroups-multiplexer-stack</emphasis> to
+    <emphasis>false</emphasis> then you will need to ensure that the format of
+    your jgroups configuration is not anymore a jgroups stack definitions but
+    a normal configuration and finally you will need to set the property
+    <emphasis>singleton_name</emphasis> of your JGroups configuration to a
+    unique name (this name must not be the same from one portal container to
+    another).</para>
 
     <programlisting language="xml">&lt;property name="jgroups-configuration" value="jar:/conf/portal/udp-mux.xml" /&gt;
 &lt;property name="jgroups-multiplexer-stack" value="false" /&gt;</programlisting>