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

do-not-reply at jboss.org do-not-reply at jboss.org
Thu Feb 18 06:45:31 EST 2010


Author: sergiykarpenko
Date: 2010-02-18 06:45:30 -0500 (Thu, 18 Feb 2010)
New Revision: 1889

Modified:
   jcr/trunk/docs/reference/en/src/main/docbook/en-US/master.xml
   jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/configuration.xml
   jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/external-value-storages.xml
Log:
EXOJCR-490: links updated

Modified: jcr/trunk/docs/reference/en/src/main/docbook/en-US/master.xml
===================================================================
--- jcr/trunk/docs/reference/en/src/main/docbook/en-US/master.xml	2010-02-18 11:08:34 UTC (rev 1888)
+++ jcr/trunk/docs/reference/en/src/main/docbook/en-US/master.xml	2010-02-18 11:45:30 UTC (rev 1889)
@@ -75,5 +75,8 @@
   <xi:include href="modules/query-handler-config.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude" />
 
+  <xi:include href="modules/external-value-storages.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
 
+
 </book>

Modified: jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/configuration.xml
===================================================================
--- jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/configuration.xml	2010-02-18 11:08:34 UTC (rev 1888)
+++ jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/configuration.xml	2010-02-18 11:45:30 UTC (rev 1889)
@@ -117,14 +117,14 @@
     <section>
       <title>JCR Configuration</title>
 
-      <para> The Configuration is defined in an XML file (see DTD below).
-      </para>
+      <para>The Configuration is defined in an XML file (see DTD
+      below).</para>
 
       <para>JCR Service can use multiple Repositories and each repository can
-      have multiple Workspaces. </para>
+      have multiple Workspaces.</para>
 
       <para>Repositories configuration parameters support human-readable
-      formats of values. They are all case-insensitive: </para>
+      formats of values. They are all case-insensitive:</para>
 
       <itemizedlist>
         <listitem>
@@ -137,8 +137,8 @@
 
         <listitem>
           <para>Time format endings: ms - milliseconds, s - seconds, m -
-          minutes, h - hours, d - days, w - weeks, if no ending - seconds.
-          </para>
+          minutes, h - hours, d - days, w - weeks, if no ending -
+          seconds.</para>
 
           <para>Examples: 500ms - 500 milliseconds, 20 or 20s - 20 seconds,
           30m - 30 minutes, 12h - 12 hours, 5d - 5 days, 4w - 4 weeks.</para>
@@ -148,12 +148,12 @@
       <para></para>
     </section>
 
-    <section>
-      <title>Repository service configuration </title>
+    <section id="sect_repository_service_configuration">
+      <title>Repository service configuration</title>
 
       <para>Default configuration of the Repository Service located in
       jar:/conf/portal/exo-jcr-config.xml, it will be available for portal and
-      standalone modes. </para>
+      standalone modes.</para>
 
       <para>In portal mode it is overriden and located in the portal web
       application portal/WEB-INF/conf/jcr/repository-configuration.xml.</para>
@@ -272,7 +272,7 @@
 
       <para>default-workspace - the name of a workspace obtained using
       Session's login() or login(Credentials) methods (ones without an
-      explicit workspace name) </para>
+      explicit workspace name)</para>
 
       <para>system-workspace - name of workspace where /jcr:system node is
       placed</para>
@@ -308,7 +308,7 @@
 
       <para>cache - workspace storage cache configuration</para>
 
-      <para>query-handler - query handler configuration </para>
+      <para>query-handler - query handler configuration</para>
 
       <para>Workspace data container configuration:</para>
 
@@ -338,15 +338,14 @@
 
       <para>Initializer configuration (optional):</para>
 
-      <para>class - initializer implementation class. </para>
+      <para>class - initializer implementation class.</para>
 
       <para>properties - the list of properties (name-value pairs). Properties
       are supported:</para>
 
-      <para> root-nodetype - The node type for root node initialization
-      </para>
+      <para>root-nodetype - The node type for root node initialization</para>
 
-      <para> root-permissions - Default permissions of the root node. It is
+      <para>root-permissions - Default permissions of the root node. It is
       defined as a set of semicolon-delimited permissions containing a group
       of space-delimited identities (user, group etc, see Organization service
       documentation for details) and the type of permission. For example any
@@ -363,21 +362,20 @@
 
       <para>class - cache implementation class, optional from 1.9. Default
       value is
-      org.exoplatform.services.jcr.impl.dataflow.persistent.LinkedWorkspaceStorageCacheImpl.
-      </para>
+      org.exoplatform.services.jcr.impl.dataflow.persistent.LinkedWorkspaceStorageCacheImpl.</para>
 
       <para>Cache can be configured to use concrete implementation of
       WorkspaceStorageCache interface. JCR core has two implementation to use:
       * LinkedWorkspaceStorageCacheImpl - default, with configurable read
       behavior and statistic. * WorkspaceStorageCacheImpl - pre 1.9, still can
-      be used. </para>
+      be used.</para>
 
       <para>properties - the list of properties (name-value pairs) for
-      Workspace cache: </para>
+      Workspace cache:</para>
 
-      <para> max-size - cache maximum size. </para>
+      <para>max-size - cache maximum size.</para>
 
-      <para> live-time - cached item live time.</para>
+      <para>live-time - cached item live time.</para>
 
       <para>LinkedWorkspaceStorageCacheImpl supports additional optional
       parameters TODO</para>
@@ -393,10 +391,10 @@
       <para>Lock Manager configuration:</para>
 
       <para>time-out - time after which the unused global lock will be
-      removed. </para>
+      removed.</para>
 
       <para>persister - a class for storing lock information for future use.
-      For example, remove lock after jcr restart. </para>
+      For example, remove lock after jcr restart.</para>
 
       <para>path - a lock folder, each workspace has its own.</para>
 

Modified: jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/external-value-storages.xml
===================================================================
--- jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/external-value-storages.xml	2010-02-18 11:08:34 UTC (rev 1888)
+++ jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/external-value-storages.xml	2010-02-18 11:45:30 UTC (rev 1889)
@@ -16,7 +16,8 @@
     (BLOBs) for example (see [TODOBinary values processing link]).</para>
 
     <para>Value storage configuration is a part of Repository configuration,
-    find more details there [TODO link to repository configuration].</para>
+    find more details <link
+    linkend="sect_repository_service_configuration">there</link>.</para>
 
     <para>Tree-based storage is recommended for most of cases. If you run an
     application on Amazon EC2 - the S3 option may be interesting for



More information about the exo-jcr-commits mailing list