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

[do-not-reply at jboss.org]

Author: nzamosenchuk
Date: 2011-08-17 10:16:40 -0400 (Wed, 17 Aug 2011)
New Revision: 4769

Modified:
   jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/api-extensions.xml
Log:
EOXJCR-267 : System property notice added to documentation

Modified: jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/api-extensions.xml
===================================================================
--- jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/api-extensions.xml	2011-08-17 13:50:37 UTC (rev 4768)
+++ jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/api-extensions.xml	2011-08-17 14:16:40 UTC (rev 4769)
@@ -49,6 +49,15 @@
       functionally-full analogue of specified getNodes() operation. So when
       having a deal with huge list of child nodes, getNodes() can be simply
       and safely substituted with getNodesLazily().</para>
+
+      <para>JCR gives an experimental opportunity to replace all getNodes()
+      invocations with getNodesLazily() calls. It handles a boolean system
+      property named "org.exoplatform.jcr.forceUserGetNodesLazily" that
+      internally replaces one call with another, without any code changes. But
+      be sure using it only for development purposes. This feature can be used
+      with top level products using eXo JCR to perform a quick compatibility
+      and performance tests without changing any code. This is not recommended
+      to be used as a production solution.</para>
     </section>
 
     <section>