[exo-jcr-commits] exo-jcr SVN: r5548 - jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration.

[do-not-reply at jboss.org]

Author: nfilotto
Date: 2012-02-01 03:13:41 -0500 (Wed, 01 Feb 2012)
New Revision: 5548

Modified:
   jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration/exo-jcr-configuration.xml
Log:
EXOJCR-1737: The doc has been completed

Modified: jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration/exo-jcr-configuration.xml
===================================================================
--- jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration/exo-jcr-configuration.xml	2012-01-31 17:57:20 UTC (rev 5547)
+++ jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration/exo-jcr-configuration.xml	2012-02-01 08:13:41 UTC (rev 5548)
@@ -522,9 +522,12 @@
     <para>The effective configuration of all the repositories and their
     workspaces can be known thanks to the method
     <emphasis>getConfigurationXML</emphasis>() that is exposed through JMX at
-    the <emphasis>RepositoryServiceConfiguration</emphasis> level. This method
-    will give you the effective configuration in XML format that has been
-    really interpreted by the the JCR core. This could be helpful to
+    the <emphasis>RepositoryServiceConfiguration</emphasis> level in case of a
+    <emphasis>PortalContainer</emphasis> the name of the related MBean will be
+    of type
+    <emphasis>exo:portal=${portal-container-name},service=RepositoryServiceConfiguration</emphasis>.
+    This method will give you the effective configuration in XML format that
+    has been really interpreted by the the JCR core. This could be helpful to
     understand how your repositories/workspaces are configured especially if
     you would like to overwrite the configuration for some reasons.</para>
   </section>