[gatein-commits] gatein SVN: r8091 - in epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules: Advanced and 2 other directories.

Author: smumford Date: 2011-11-17 21:57:59 -0500 (Thu, 17 Nov 2011) New Revision: 8091 Added: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR.xml Removed: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR.xml Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr-with-gtn/managed-datasources-under-jboss-as.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/api-extensions.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/cluster-config.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/data-container-howto.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/data-container.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/db-cleaner-service.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/intro.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jbosscache-configuration-templates.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jbossts-transaction-service.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jca.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jta.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/lock-manager-config.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/performance-tuning-guide.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/query-handler-config.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/repository-check-controller.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/repository-creation-service.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/statistics.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/transaction-manager-lookup.xml Log: Restructure to make JCR chapter a new Part Deleted: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -1,98 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> -%BOOK_ENTITIES; -]> -<part id="part-Reference_Guide_eXo_JCR_1.14-eXo_JCR"> - <title><remark>Java Content Repository</remark></title> - <!--<xi:include href="eXoJCR/eXoJCR/jcr.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />--> - <xi:include href="eXoJCR/jcr/intro.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- concepts --> - <!-- <xi:include href="eXoJCR/jcr/concepts/why-jcr.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> - <xi:include href="eXoJCR/jcr/concepts/jcr-exo-implementation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/concepts/jcr-advantages.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/concepts/jcr-compatibility-levels.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/concepts/jcr-usage.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- <xi:include href="eXoJCR/jcr/concepts/jcr-extensions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> - <xi:include href="eXoJCR/jcr/concepts/jcr-applications.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/concepts/nodetypes-and-namespaces.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/concepts/nodetype-registration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/concepts/jcr-registry-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/concepts/jcr-namespace-altering.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- common configs --> - <xi:include href="eXoJCR/jcr/configuration/exo-jcr-configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/configuration/multilanguage-support.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/configuration/search-configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/configuration/configuration-persister.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/configuration/jdbc-data-container-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/configuration/external-value-storages.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/configuration/workspace-persistence-storage.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/configuration/rest-services-on-groovy.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- cluster configs --> - <xi:include href="eXoJCR/jcr/cluster-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/jbosscache-configuration-templates.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/lock-manager-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/query-handler-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/jbossts-transaction-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/transaction-manager-lookup.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/repository-creation-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- search --> - <xi:include href="eXoJCR/jcr/searching/jcr-query-usecases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/searching/searching-repository-content.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/searching/fulltext-search-and-settings.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - - <!-- api extensions --> - <xi:include href="eXoJCR/jcr/api-extensions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- protocols --> - <xi:include href="eXoJCR/jcr/protocols/webdav.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/protocols/ftp.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- backup --> - <xi:include href="eXoJCR/jcr/backup/exojcr-backup-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/backup/backup-client.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/backup/use-external-backup-tool.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- other --> - <xi:include href="eXoJCR/jcr/statistics.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/repository-check-controller.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/jta.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/jca.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/other/acl.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/other/acl-ext.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/other/link-producer.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/other/binary-values-processing.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="eXoJCR/jcr/other/jcr-resources.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- data container configs --> - <xi:include href="eXoJCR/jcr/data-container.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- <xi:include href="eXoJCR/jcr/data-container-howto.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> - - <xi:include href="eXoJCR/jcr/db-cleaner-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- tuning guide - DOC NOTE: Could possibly be moved to a specific Tuning Guide later --> - <xi:include href="eXoJCR/jcr/performance-tuning-guide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!--JCR Core - DOC NOTE: This section seems to include items covered elsewhere in this guide, or things that are not relevant to EPP - <xi:include href="eXoJCR/core.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> - - <!-- Web services - DOC NOTE: Red Hat JBoss has two possible Web Services packages. No need to document the eXo offering: - <xi:include href="eXoJCR/ws.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />--> - - <!--GateIn and JCR --> - <xi:include href="eXoJCR/jcr-with-gatein.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!--DOC NOTE: Commented FAQ section out as per advice from Philippe Aristote; "Unfit for publication" --> - <!--<xi:include href="eXoJCR/faq.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />--> -</part> - Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/api-extensions.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/api-extensions.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/api-extensions.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> -<section> +<chapter> <title>JCR API Extensions</title> @@ -97,4 +97,4 @@ implementation specific issue typical for "lazy-pattern".</para> </section> </section> -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/cluster-config.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/cluster-config.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/cluster-config.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Cluster_Config"> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Cluster_Config"> <!-- This document was created with Syntext Serna Free. --> <title>Cluster Configuration</title> <section id="sect-Reference_Guide_eXo_JCR_1.14-Cluster_Config-Launching_Cluster"> @@ -302,6 +302,6 @@ </section> -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/data-container-howto.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/data-container-howto.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/data-container-howto.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,80 +3,80 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_implement_Workspace_Data_Container"> - <title>How-to implement Workspace Data Container</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_implement_Workspace_Data_Container-Short_intro_about_Workspace_data_container_implementation_practices"> - <title>Short intro about Workspace data container implementation practices:</title> - <orderedlist> - <listitem> - <para> - Read a bit about the <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-JCR_Workspace_Data_Container" />. - </para> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-How_to_implement_Workspace_Data_Container"> + <title>How-to implement Workspace Data Container</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_implement_Workspace_Data_Container-Short_intro_about_Workspace_data_container_implementation_practices"> + <title>Short intro about Workspace data container implementation practices:</title> + <orderedlist> + <listitem> + <para> + Read a bit about the <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-JCR_Workspace_Data_Container" />. + </para> - </listitem> - <listitem> - <para> - Start new implementation project pom.xml with org.exoplatform.jcr parent. (optional, but will makes the development easy) - </para> + </listitem> + <listitem> + <para> + Start new implementation project pom.xml with org.exoplatform.jcr parent. (optional, but will makes the development easy) + </para> - </listitem> - <listitem> - <para> - Update sources of JCR Core and read JavaDoc on <emphasis role="bold">org.exoplatform.services.jcr.storage.WorkspaceDataContainer</emphasis> and <emphasis role="bold">org.exoplatform.services.jcr.storage.WorkspaceStorageConnection</emphasis> interfaces. They are the main part for the implementation. - </para> + </listitem> + <listitem> + <para> + Update sources of JCR Core and read JavaDoc on <emphasis role="bold">org.exoplatform.services.jcr.storage.WorkspaceDataContainer</emphasis> and <emphasis role="bold">org.exoplatform.services.jcr.storage.WorkspaceStorageConnection</emphasis> interfaces. They are the main part for the implementation. + </para> - </listitem> - <listitem> - <para> - Look at <emphasis role="bold">org.exoplatform.services.jcr.impl.dataflow.persistent.WorkspacePersistentDataManager</emphasis> sourcecode, check how data manager uses container and its connections (see in save() method) - </para> + </listitem> + <listitem> + <para> + Look at <emphasis role="bold">org.exoplatform.services.jcr.impl.dataflow.persistent.WorkspacePersistentDataManager</emphasis> sourcecode, check how data manager uses container and its connections (see in save() method) + </para> - </listitem> - <listitem> - <para> - Create <emphasis role="bold">WorkspaceStorageConnection</emphasis> dummy implementation class. It's freeform class, but to be close to the eXo JCR, check how to implement JDBC or SimpleDB containers ( <emphasis role="bold">org.exoplatform.services.jcr.impl.storage.jdbc.JDBCStorageConnection</emphasis> and <emphasis role="bold">org.exoplatform.services.jcr.aws.storage.sdb.SDBWorkspaceStorageConnection</emphasis>). Take in account usage of <emphasis role="bold">ValueStoragePluginProvider</emphasis> in both implementations.Value storage is an useful option for production versions. But leave it to the end of implementation work. - </para> + </listitem> + <listitem> + <para> + Create <emphasis role="bold">WorkspaceStorageConnection</emphasis> dummy implementation class. It's freeform class, but to be close to the eXo JCR, check how to implement JDBC or SimpleDB containers ( <emphasis role="bold">org.exoplatform.services.jcr.impl.storage.jdbc.JDBCStorageConnection</emphasis> and <emphasis role="bold">org.exoplatform.services.jcr.aws.storage.sdb.SDBWorkspaceStorageConnection</emphasis>). Take in account usage of <emphasis role="bold">ValueStoragePluginProvider</emphasis> in both implementations.Value storage is an useful option for production versions. But leave it to the end of implementation work. + </para> - </listitem> - <listitem> - <para> - Create the connection implementation unit tests to play TTD. (optional, but takes many benefits for the process) - </para> + </listitem> + <listitem> + <para> + Create the connection implementation unit tests to play TTD. (optional, but takes many benefits for the process) + </para> - </listitem> - <listitem> - <para> - Implement CRUD starting from the read to write etc. Test the methods by using the external implementation ways of data read/write in your backend. - </para> + </listitem> + <listitem> + <para> + Implement CRUD starting from the read to write etc. Test the methods by using the external implementation ways of data read/write in your backend. + </para> - </listitem> - <listitem> - <para> - When all methods of the connection done start <emphasis role="bold">WorkspaceDataContainer</emphasis>. Container class is very simple, it's like a factory for the connections only. - </para> + </listitem> + <listitem> + <para> + When all methods of the connection done start <emphasis role="bold">WorkspaceDataContainer</emphasis>. Container class is very simple, it's like a factory for the connections only. + </para> - </listitem> - <listitem> - <para> - Care about container reuseConnection(WorkspaceStorageConnection) method logic. For some backends, it cab be same as openConnection(), but for some others, it's important to reuse physical backend connection, e.g. to be in the same transaction - see JDBC container. - </para> + </listitem> + <listitem> + <para> + Care about container reuseConnection(WorkspaceStorageConnection) method logic. For some backends, it cab be same as openConnection(), but for some others, it's important to reuse physical backend connection, e.g. to be in the same transaction - see JDBC container. + </para> - </listitem> - <listitem> - <para> - It's almost ready to use in data manager. Start another test and go on. - </para> + </listitem> + <listitem> + <para> + It's almost ready to use in data manager. Start another test and go on. + </para> - </listitem> + </listitem> - </orderedlist> - <para> - When the container will be ready to run as JCR persistence storage (e.g. for this level testing), it should be configured in Repository configuration. - </para> - <para> - Assuming that our new implementation class name is <emphasis role="bold">org.project.jcr.impl.storage.MyWorkspaceDataContainer</emphasis>. - </para> - + </orderedlist> + <para> + When the container will be ready to run as JCR persistence storage (e.g. for this level testing), it should be configured in Repository configuration. + </para> + <para> + Assuming that our new implementation class name is <emphasis role="bold">org.project.jcr.impl.storage.MyWorkspaceDataContainer</emphasis>. + </para> + <programlisting language="XML" role="XML"> &lt;repository-service default-repository="repository"&gt; &lt;repositories&gt; &lt;repository name="repository" system-workspace="production" default-workspace="production"&gt; @@ -96,21 +96,21 @@ &lt;/container&gt; </programlisting> - <para> - Container can be configured by using set properties. - </para> + <para> + Container can be configured by using set properties. + </para> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_implement_Workspace_Data_Container-Notes_on_Value_storage_usage"> - <title>Notes on Value storage usage:</title> - <para> - Value storages are pluggable to the container but if they are used, the container implementation should respect set of interfaces and external storage usage principles. - </para> - <para> - If the container has <emphasis role="bold">ValueStoragePluginProvider</emphasis> (e.g. via constructor), it's just a few methods to manipulate external Values data. - </para> - + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_implement_Workspace_Data_Container-Notes_on_Value_storage_usage"> + <title>Notes on Value storage usage:</title> + <para> + Value storages are pluggable to the container but if they are used, the container implementation should respect set of interfaces and external storage usage principles. + </para> + <para> + If the container has <emphasis role="bold">ValueStoragePluginProvider</emphasis> (e.g. via constructor), it's just a few methods to manipulate external Values data. + </para> + <programlisting language="Java" role="Java">// get channel for ValueData write (add or update) ValueIOChannel channel = valueStorageProvider.getApplicableChannel(data, i); if (channel == null) { @@ -133,17 +133,17 @@ ValueData vdata = channel.read(propertyData.getIdentifier(), orderNumber, maxBufferSize); </programlisting> - <important> - <title>Important</title> - <para> - After a sequence of write and/or delete operations on the storage channel, the channel should be committed (or rolled back on an error). See <emphasis role="bold">ValueIOChannel.commit()</emphasis> and <emphasis role="bold">ValueIOChannel.rollback()</emphasis> and how those methods are used in JDBC container. - </para> + <important> + <title>Important</title> + <para> + After a sequence of write and/or delete operations on the storage channel, the channel should be committed (or rolled back on an error). See <emphasis role="bold">ValueIOChannel.commit()</emphasis> and <emphasis role="bold">ValueIOChannel.rollback()</emphasis> and how those methods are used in JDBC container. + </para> - </important> + </important> - </section> - + </section> + -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/data-container.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/data-container.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/data-container.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Workspace_Data_Container"> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Workspace_Data_Container"> <title>JCR Workspace Data Container</title> <para> The JCR Workspace Data Container: @@ -583,6 +583,6 @@ </section> -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/db-cleaner-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/db-cleaner-service.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/db-cleaner-service.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,63 +3,63 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-DBCleanService"> - <title>DBCleanService</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-DBCleanService-API"> - <title>API</title> - <para> - It is special service for removing data from database. - </para> - <note> - <para> - Code that invokes methods of DBCleanService must have JCRRuntimePermissions.MANAGE_REPOSITORY_PERMISSION permission; - </para> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-DBCleanService"> + <title>DBCleanService</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-DBCleanService-API"> + <title>API</title> + <para> + It is special service for removing data from database. + </para> + <note> + <para> + Code that invokes methods of DBCleanService must have JCRRuntimePermissions.MANAGE_REPOSITORY_PERMISSION permission; + </para> - </note> - <para> - There are three methods of DBCleanerService: - </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-API-API"> - <title>API</title> - <tgroup cols="2"> - <tbody> - <row> - <entry> - public static void cleanWorkspaceData(WorkspaceEntry wsEntry) - </entry> - <entry> - Clean workspace data from database. Tables will be removed in case of multiDB, and only records will be removed in case of singleDB. - </entry> + </note> + <para> + There are three methods of DBCleanerService: + </para> + <table id="tabl-Reference_Guide_eXo_JCR_1.14-API-API"> + <title>API</title> + <tgroup cols="2"> + <tbody> + <row> + <entry> + public static void cleanWorkspaceData(WorkspaceEntry wsEntry) + </entry> + <entry> + Clean workspace data from database. Tables will be removed in case of multiDB, and only records will be removed in case of singleDB. + </entry> - </row> - <row> - <entry> - public static void cleanRepositoryData(RepositoryEntry repoEntry) - </entry> - <entry> - Cleanup repository data from database. - </entry> + </row> + <row> + <entry> + public static void cleanRepositoryData(RepositoryEntry repoEntry) + </entry> + <entry> + Cleanup repository data from database. + </entry> - </row> - <row> - <entry> - public static getDBCleaner(Connection jdbcConn, WorkspaceEntry wsEntry) - </entry> - <entry> - Returns DBClean object with defined connection that allow to manual invoke clean method on it. Note: DBClean doesn't perform commit or close connection. It should be done manually. - </entry> + </row> + <row> + <entry> + public static getDBCleaner(Connection jdbcConn, WorkspaceEntry wsEntry) + </entry> + <entry> + Returns DBClean object with defined connection that allow to manual invoke clean method on it. Note: DBClean doesn't perform commit or close connection. It should be done manually. + </entry> - </row> + </row> - </tbody> + </tbody> - </tgroup> + </tgroup> - </table> + </table> - </section> - + </section> + -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/intro.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/intro.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/intro.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,127 +3,127 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Introduction"> - <title>Introduction</title> - <warning> - <title>eXo JCR usage</title> - <para> - The JBoss Enterprise Portal Platform is using a JCR API to store its information for internal usage. We do not support usage of the JCR to store application information. - </para> - <para> - The information below is intended to assist users to understand particular low level details on how the JBoss Enterprise Portal Platform works and how it can be fine-tuned. - </para> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Introduction"> + <title>Introduction</title> + <warning> + <title>eXo JCR usage</title> + <para> + The JBoss Enterprise Portal Platform is using a JCR API to store its information for internal usage. We do not support usage of the JCR to store application information. + </para> + <para> + The information below is intended to assist users to understand particular low level details on how the JBoss Enterprise Portal Platform works and how it can be fine-tuned. + </para> - </warning> - <para> - The term <emphasis role="bold">JCR</emphasis> refers to the Java Content Repository. The JCR is the data store of JBoss Enterprise Portal Platform. All content is stored and managed via the JCR. - </para> - <para> - The eXo JCR included with JBoss Enterprise Portal Platform &VY; is a (<ulink type="http" url="http://www.jcp.org/en/jsr/detail?id=170">JSR-170</ulink>) compliant implementation of the JCR 1.0 specification. The JCR provides versioning, textual search, access control, content event monitoring, and is used to storing text and binary data for the portal internal usage. The back-end storage of the JCR is configurable and can be a file system or a database. - </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Introduction-Concepts"> - <title>Concepts</title> - <variablelist> - <varlistentry> - <term>Repository</term> - <listitem> - <para> - A repository is a form of data storage device. A 'repository' differs from a 'database' in the nature of the information contained. While a database holds hard data in rigid tables, a repository may access the data on a database by using less rigid <emphasis>meta</emphasis>-data. In this sense a repository operates as an 'interpreter' between the database(s) and the user. - </para> - <note> - <para> - The data model for the interface (the repository) is rarely the same as the data model used by the repository's underlying storage subsystems (such as a database), however the repository is able to make persistent data changes in the storage subsystem. - </para> + </warning> + <para> + The term <emphasis role="bold">JCR</emphasis> refers to the Java Content Repository. The JCR is the data store of JBoss Enterprise Portal Platform. All content is stored and managed via the JCR. + </para> + <para> + The eXo JCR included with JBoss Enterprise Portal Platform &VY; is a (<ulink type="http" url="http://www.jcp.org/en/jsr/detail?id=170">JSR-170</ulink>) compliant implementation of the JCR 1.0 specification. The JCR provides versioning, textual search, access control, content event monitoring, and is used to storing text and binary data for the portal internal usage. The back-end storage of the JCR is configurable and can be a file system or a database. + </para> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Introduction-Concepts"> + <title>Concepts</title> + <variablelist> + <varlistentry> + <term>Repository</term> + <listitem> + <para> + A repository is a form of data storage device. A 'repository' differs from a 'database' in the nature of the information contained. While a database holds hard data in rigid tables, a repository may access the data on a database by using less rigid <emphasis>meta</emphasis>-data. In this sense a repository operates as an 'interpreter' between the database(s) and the user. + </para> + <note> + <para> + The data model for the interface (the repository) is rarely the same as the data model used by the repository's underlying storage subsystems (such as a database), however the repository is able to make persistent data changes in the storage subsystem. + </para> - </note> + </note> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>Workspace</term> - <listitem> - <para> - The eXo JCR uses 'workspaces' as the main data abstraction in its data model. The content is stored in a workspace as a hierarchy of <emphasis>items</emphasis> and each workspace has its own hierarchy of items. - </para> - <para> - Repositories access one or more workspaces. Persistent JCR workspaces consist of a directed acyclic graph of <emphasis>items</emphasis> where the edges represent the parent-child relation. - </para> + </varlistentry> + <varlistentry> + <term>Workspace</term> + <listitem> + <para> + The eXo JCR uses 'workspaces' as the main data abstraction in its data model. The content is stored in a workspace as a hierarchy of <emphasis>items</emphasis> and each workspace has its own hierarchy of items. + </para> + <para> + Repositories access one or more workspaces. Persistent JCR workspaces consist of a directed acyclic graph of <emphasis>items</emphasis> where the edges represent the parent-child relation. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>Items</term> - <listitem> - <para> - An <emphasis>item</emphasis> is either a <emphasis>node</emphasis> or a <emphasis>property</emphasis>. Properties contain the data (either simple values or binary data). The nodes of a workspace give it its structure while the properties hold the data itself. - </para> - <variablelist> - <varlistentry> - <term>Nodes</term> - <listitem> - <para> - Nodes are identified using accepted <emphasis>namespacing</emphasis> conventions. Changed nodes may be versioned through an associated version graph to preserve data integrity. - </para> - <para> - Nodes can have various properties or child nodes associated to them. - </para> + </varlistentry> + <varlistentry> + <term>Items</term> + <listitem> + <para> + An <emphasis>item</emphasis> is either a <emphasis>node</emphasis> or a <emphasis>property</emphasis>. Properties contain the data (either simple values or binary data). The nodes of a workspace give it its structure while the properties hold the data itself. + </para> + <variablelist> + <varlistentry> + <term>Nodes</term> + <listitem> + <para> + Nodes are identified using accepted <emphasis>namespacing</emphasis> conventions. Changed nodes may be versioned through an associated version graph to preserve data integrity. + </para> + <para> + Nodes can have various properties or child nodes associated to them. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>Properties</term> - <listitem> - <para> - Properties hold data as values of predefined types, such as: <emphasis role="bold">String</emphasis>, <emphasis role="bold">Binary</emphasis>, <emphasis role="bold">Long</emphasis>, <emphasis role="bold">Boolean</emphasis>, <emphasis role="bold">Double</emphasis>, <emphasis role="bold">Date</emphasis>, <emphasis role="bold">Reference</emphasis> and <emphasis role="bold">Path</emphasis>. - </para> + </varlistentry> + <varlistentry> + <term>Properties</term> + <listitem> + <para> + Properties hold data as values of predefined types, such as: <emphasis role="bold">String</emphasis>, <emphasis role="bold">Binary</emphasis>, <emphasis role="bold">Long</emphasis>, <emphasis role="bold">Boolean</emphasis>, <emphasis role="bold">Double</emphasis>, <emphasis role="bold">Date</emphasis>, <emphasis role="bold">Reference</emphasis> and <emphasis role="bold">Path</emphasis>. + </para> - </listitem> + </listitem> - </varlistentry> + </varlistentry> - </variablelist> + </variablelist> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>The Data Model</term> - <listitem> - <para> - The core of any Content Repository is the data model. The data model defines the 'data elements' (fields, columns, attributes, etc.) that are stored in the CR and the relationships between these elements. - </para> - <para> - Data elements can be singular pieces of information (the value 3.14, for example), or compound values ('<emphasis>pi</emphasis>' = 3.14). A data model uses concepts like 'nodes', 'arrays' and 'links' to define relationships between data elements. - </para> - <para> - The use and structure of these elements forms the content repository's 'data model'. - </para> + </varlistentry> + <varlistentry> + <term>The Data Model</term> + <listitem> + <para> + The core of any Content Repository is the data model. The data model defines the 'data elements' (fields, columns, attributes, etc.) that are stored in the CR and the relationships between these elements. + </para> + <para> + Data elements can be singular pieces of information (the value 3.14, for example), or compound values ('<emphasis>pi</emphasis>' = 3.14). A data model uses concepts like 'nodes', 'arrays' and 'links' to define relationships between data elements. + </para> + <para> + The use and structure of these elements forms the content repository's 'data model'. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>Data Abstraction</term> - <listitem> - <para> - Data abstraction describes the separation between <emphasis>abstract</emphasis> and <emphasis>concrete</emphasis> properties of data stored in a repository. The <emphasis>concrete</emphasis> properties of the data refer to its implementation details. - </para> - <para> - The <emphasis>concrete</emphasis> properties of the data implementation may be changed without affecting the <emphasis>abstract</emphasis> properties of the data itself, which are read by the data client. - </para> - <para> - Consider the presentation of data in a list, graph or table. While the information <emphasis>implementation</emphasis> may change, the data itself is unaffected, and readers to whom the data is presented can perform a mental abstraction to interpret it correctly, regardless of the implementation. - </para> + </varlistentry> + <varlistentry> + <term>Data Abstraction</term> + <listitem> + <para> + Data abstraction describes the separation between <emphasis>abstract</emphasis> and <emphasis>concrete</emphasis> properties of data stored in a repository. The <emphasis>concrete</emphasis> properties of the data refer to its implementation details. + </para> + <para> + The <emphasis>concrete</emphasis> properties of the data implementation may be changed without affecting the <emphasis>abstract</emphasis> properties of the data itself, which are read by the data client. + </para> + <para> + Consider the presentation of data in a list, graph or table. While the information <emphasis>implementation</emphasis> may change, the data itself is unaffected, and readers to whom the data is presented can perform a mental abstraction to interpret it correctly, regardless of the implementation. + </para> - </listitem> + </listitem> - </varlistentry> + </varlistentry> - </variablelist> - <!-- Commented until image can be redrawn for RedHat. + </variablelist> + <!-- Commented until image can be redrawn for RedHat. <mediaobject> <imageobject role="html"> <imagedata fileref="images/Advanced/JCR/repository_diagram.png" format="PNG" align="center" scale="90" /> @@ -146,9 +146,9 @@ Source Author: Day Management AG Source Author email: Source License: http://www.day.com/specs/jcr/2.0/license.html] --> - </section> - + </section> + -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jbosscache-configuration-templates.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jbosscache-configuration-templates.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jbosscache-configuration-templates.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-JBoss_Cache_configuration"> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-JBoss_Cache_configuration"> <title>JBoss Cache configuration</title> <section id="sect-Reference_Guide_eXo_JCR_1.14-JBoss_Cache_configuration-JBoss_cache_configuration_for_indexer_lock_manager_and_data_container"> <title>Indexer, lock manager and data container configuration</title> @@ -278,6 +278,6 @@ </section> -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jbossts-transaction-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jbossts-transaction-service.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jbossts-transaction-service.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,25 +3,25 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-JBossTransactionsService"> - <title>JBossTransactionsService</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JBossTransactionsService-Introduction"> - <title>Introduction</title> - <para> - JBossTransactionsService implements eXo TransactionService and provides access to <ulink url="http://www.jboss.org/jbosstm/">JBoss Transaction Service (JBossTS)</ulink> JTA implementation via eXo container dependency. - </para> - <para> - TransactionService used in JCR cache <emphasis>org.exoplatform.services.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache</emphasis> implementation. - </para> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-JBossTransactionsService"> + <title>JBossTransactionsService</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-JBossTransactionsService-Introduction"> + <title>Introduction</title> + <para> + JBossTransactionsService implements eXo TransactionService and provides access to <ulink url="http://www.jboss.org/jbosstm/">JBoss Transaction Service (JBossTS)</ulink> JTA implementation via eXo container dependency. + </para> + <para> + TransactionService used in JCR cache <emphasis>org.exoplatform.services.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache</emphasis> implementation. + </para> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-JBossTransactionsService-Configuration"> - <title>Configuration</title> - <para> - Example configuration: - </para> - + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-JBossTransactionsService-Configuration"> + <title>Configuration</title> + <para> + Example configuration: + </para> + <programlisting language="XML" role="XML"> &lt;component&gt; &lt;key&gt;org.exoplatform.services.transaction.TransactionService&lt;/key&gt; &lt;type&gt;org.exoplatform.services.transaction.jbosscache.JBossTransactionsService&lt;/type&gt; @@ -32,13 +32,13 @@ &lt;/value-param&gt; &lt;/init-params&gt; &lt;/component&gt;</programlisting> - <para> - timeout - XA transaction timeout in seconds - </para> + <para> + timeout - XA transaction timeout in seconds + </para> - </section> - + </section> + -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jca.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jca.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jca.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,22 +3,22 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter"> - <title>The <emphasis>JCA</emphasis> Resource Adapter</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter-Overview"> - <title>Overview</title> - <para> - eXo JCR supports <emphasis>J2EE Connector Architecture</emphasis> 1.5, thus If you would like to delegate the JCR Session lifecycle to your application server, you can use the JCA Resource Adapter for eXo JCR if your application server supports JCA 1.5. This adapter only supports XA Transaction, in other words you cannot use it for local transactions. Since the JCR Sessions have not been designed to be shareable, the session pooling is simply not covered by the adapter. - </para> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter"> + <title>The <emphasis>JCA</emphasis> Resource Adapter</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter-Overview"> + <title>Overview</title> + <para> + eXo JCR supports <emphasis>J2EE Connector Architecture</emphasis> 1.5, thus If you would like to delegate the JCR Session lifecycle to your application server, you can use the JCA Resource Adapter for eXo JCR if your application server supports JCA 1.5. This adapter only supports XA Transaction, in other words you cannot use it for local transactions. Since the JCR Sessions have not been designed to be shareable, the session pooling is simply not covered by the adapter. + </para> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter-The_SessionFactory"> - <title>The <emphasis>SessionFactory</emphasis></title> - <para> - The equivalent of the <emphasis>javax.resource.cci.ConnectionFactory</emphasis> in JCA terminology is <emphasis>org.exoplatform.connectors.jcr.adapter.SessionFactory</emphasis> in the context of eXo JCR, the resource that you will get thanks to a JNDI lookup is of type <emphasis>SessionFactory</emphasis> and provides the following methods: - </para> - + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter-The_SessionFactory"> + <title>The <emphasis>SessionFactory</emphasis></title> + <para> + The equivalent of the <emphasis>javax.resource.cci.ConnectionFactory</emphasis> in JCA terminology is <emphasis>org.exoplatform.connectors.jcr.adapter.SessionFactory</emphasis> in the context of eXo JCR, the resource that you will get thanks to a JNDI lookup is of type <emphasis>SessionFactory</emphasis> and provides the following methods: + </para> + <programlisting> /** * Get a JCR session corresponding to the repository * defined in the configuration and the default workspace. @@ -59,50 +59,50 @@ */ Session getSession(String workspace, String userName, String password) throws RepositoryException;</programlisting> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter-Configuration"> - <title>Configuration</title> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Configuration-Configuration_Properties"> - <title>Configuration Properties</title> - <tgroup cols="2"> - <tbody> - <row> - <entry> - <emphasis>PortalContainer</emphasis> - </entry> - <entry> - In case of the portal mode, if no portal container can be found in the context of the request, the adapter will use the value of this parameter to get the name of the expected portal container to create the JCR sessions. This parameter is optional, by default the default portal container will be used. - </entry> + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter-Configuration"> + <title>Configuration</title> + <table id="tabl-Reference_Guide_eXo_JCR_1.14-Configuration-Configuration_Properties"> + <title>Configuration Properties</title> + <tgroup cols="2"> + <tbody> + <row> + <entry> + <emphasis>PortalContainer</emphasis> + </entry> + <entry> + In case of the portal mode, if no portal container can be found in the context of the request, the adapter will use the value of this parameter to get the name of the expected portal container to create the JCR sessions. This parameter is optional, by default the default portal container will be used. + </entry> - </row> - <row> - <entry> - <emphasis>Repository</emphasis> - </entry> - <entry> - The repository name used to create JCR sessions. This parameter is optional, by default the current repository will be used. - </entry> + </row> + <row> + <entry> + <emphasis>Repository</emphasis> + </entry> + <entry> + The repository name used to create JCR sessions. This parameter is optional, by default the current repository will be used. + </entry> - </row> + </row> - </tbody> + </tbody> - </tgroup> + </tgroup> - </table> + </table> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter-Deployment"> - <title>Deployment</title> - <para> - As the JCR and its dependencies are provided when you use it with gateIn you will need to deploy only the rar file corresponding to the artifactId <emphasis>exo.jcr.connectors.jca</emphasis> and groupId <emphasis>org.exoplatform.jcr</emphasis>. - </para> - <para> - Then you will need to configure the connector itself, for example for JBoss AS, you need to create in your deploy directory a file of type <emphasis>*-ds.xml</emphasis> (jcr-ds.xml for example) with the following content: - </para> - + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter-Deployment"> + <title>Deployment</title> + <para> + As the JCR and its dependencies are provided when you use it with gateIn you will need to deploy only the rar file corresponding to the artifactId <emphasis>exo.jcr.connectors.jca</emphasis> and groupId <emphasis>org.exoplatform.jcr</emphasis>. + </para> + <para> + Then you will need to configure the connector itself, for example for JBoss AS, you need to create in your deploy directory a file of type <emphasis>*-ds.xml</emphasis> (jcr-ds.xml for example) with the following content: + </para> + <programlisting>&lt;connection-factories&gt; &lt;tx-connection-factory&gt; &lt;jndi-name&gt;jcr/repository&lt;/jndi-name&gt; @@ -118,9 +118,9 @@ &lt;/tx-connection-factory&gt; &lt;/connection-factories&gt;</programlisting> - </section> - + </section> + -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jta.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jta.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/jta.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-JTA"> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-JTA"> <!-- This document was created with Syntext Serna Free. --> <title>Java Transaction API</title> <para> @@ -15,6 +15,6 @@ <para> If you intend to use a managed data source, you will have to configure the service <literal>DataSourceProvider</literal> (for more details please refer to the corresponding section). </para> -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/lock-manager-config.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/lock-manager-config.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/lock-manager-config.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-LockManager"> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-LockManager"> <title>LockManager</title> <para> The LockManager stores lock objects. It can lock or release objects as required. It is also responsible for removing stale locks. @@ -461,6 +461,6 @@ </section> -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/performance-tuning-guide.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/performance-tuning-guide.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/performance-tuning-guide.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Performance_Tuning_Guide"> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Performance_Tuning_Guide"> <title>JCR Performance Tuning Guide</title> <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Performance_Tuning_Guide-Introduction"> <title>Introduction</title> @@ -435,6 +435,6 @@ </section> -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/query-handler-config.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/query-handler-config.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/query-handler-config.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> - <section id="sect-Reference_Guide_eXo_JCR_1.14-QueryHandler_configuration"> + <chapter id="sect-Reference_Guide_eXo_JCR_1.14-QueryHandler_configuration"> <title>QueryHandler configuration</title> <section id="sect-Reference_Guide_eXo_JCR_1.14-QueryHandler_configuration-Indexing_in_clustered_environment"> @@ -537,4 +537,4 @@ </para> </section> </section> - </section> + </chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/repository-check-controller.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/repository-check-controller.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/repository-check-controller.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> - <section> + <chapter> <title>Checking repository integrity and consistency</title> <section> @@ -101,4 +101,4 @@ </itemizedlist> </note> </section> - </section> + </chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/repository-creation-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/repository-creation-service.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/repository-creation-service.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-RepositoryCreationService"> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-RepositoryCreationService"> <title><literal>RepositoryCreationService</literal></title> <section id="sect-Reference_Guide_eXo_JCR_1.14-RepositoryCreationService-Introduction"> <title>Introduction</title> @@ -225,6 +225,6 @@ </section> -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/statistics.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/statistics.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/statistics.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_statistics"> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_statistics"> <title>eXo JCR statistics</title> <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_statistics-Statistics_on_the_Database_Access_Layer"> <title>Statistics on the Database Access Layer</title> @@ -496,6 +496,6 @@ </section> -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/transaction-manager-lookup.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/transaction-manager-lookup.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/transaction-manager-lookup.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,22 +3,22 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-TransactionManagerLookup"> - <title>TransactionManagerLookup</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-TransactionManagerLookup-Configuration"> - <title>Configuration</title> - <para> - <literal>TransactionManagerLookup</literal> is a JBossCache class registered as an eXo container component in the <filename>configuration.xml</filename> file. - </para> - +<chapter id="chap-Reference_Guide_eXo_JCR_1.14-TransactionManagerLookup"> + <title>TransactionManagerLookup</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-TransactionManagerLookup-Configuration"> + <title>Configuration</title> + <para> + <literal>TransactionManagerLookup</literal> is a JBossCache class registered as an eXo container component in the <filename>configuration.xml</filename> file. + </para> + <programlisting language="XML" role="XML"> &lt;component&gt; &lt;key&gt;org.jboss.cache.transaction.TransactionManagerLookup&lt;/key&gt; &lt;type&gt;org.jboss.cache.transaction.GenericTransactionManagerLookup&lt;/type&gt; &lt;/component&gt;</programlisting> - </section> - + </section> + -</section> +</chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr-with-gtn/managed-datasources-under-jboss-as.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr-with-gtn/managed-datasources-under-jboss-as.xml 2011-11-18 02:52:23 UTC (rev 8090) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr-with-gtn/managed-datasources-under-jboss-as.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -3,31 +3,31 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_use_AS_Managed_DataSource_under_JBoss_AS"> - <title>How to use AS Managed DataSource under JBoss AS</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_use_AS_Managed_DataSource_under_JBoss_AS-Configurations_Steps"> - <title>Configurations Steps</title> - <important> - <para> - Checked under Gatein 3.1.0-GA Final - </para> +<chapter id="sect-Reference_Guide_eXo_JCR_1.14-How_to_use_AS_Managed_DataSource_under_JBoss_AS"> + <title>How to use AS Managed DataSource under JBoss AS</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_use_AS_Managed_DataSource_under_JBoss_AS-Configurations_Steps"> + <title>Configurations Steps</title> + <important> + <para> + Checked under Gatein 3.1.0-GA Final + </para> - </important> - <important> - <para> - only no-tx-datasource is supported in JCR 1.12 - </para> + </important> + <important> + <para> + only no-tx-datasource is supported in JCR 1.12 + </para> - </important> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configurations_Steps-Declaring_the_datasources_in_the_AS"> - <title>Declaring the datasources in the AS</title> - <para> - Under JBoss, just put a file XXX-ds.xml in the deploy server (example: \server\default\deploy). In this file, we will configure all datasources which eXo will need. (there should be 4 named: jdbcjcr_portal, jdbcjcr_portal-sample, jdbcidm_portal &amp; jdbcidm_sample-portal). - </para> - <para> - Example: - </para> - + </important> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configurations_Steps-Declaring_the_datasources_in_the_AS"> + <title>Declaring the datasources in the AS</title> + <para> + Under JBoss, just put a file XXX-ds.xml in the deploy server (example: \server\default\deploy). In this file, we will configure all datasources which eXo will need. (there should be 4 named: jdbcjcr_portal, jdbcjcr_portal-sample, jdbcidm_portal &amp; jdbcidm_sample-portal). + </para> + <para> + Example: + </para> + <programlisting language="XML" role="XML">&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;datasources&gt; &lt;no-tx-datasource&gt; @@ -62,50 +62,50 @@ &lt;password&gt;&lt;/password&gt; &lt;/no-tx-datasource&gt; &lt;/datasources&gt;</programlisting> - <para> - Which properties can be set for datasource can be found here: <ulink url="http://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4... JDBC DataSources - The non transactional DataSource configuration schema</ulink> - </para> + <para> + Which properties can be set for datasource can be found here: <ulink url="http://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4... JDBC DataSources - The non transactional DataSource configuration schema</ulink> + </para> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configurations_Steps-Do_not_let_eXo_bind_datasources_explicitly"> - <title>Do not let eXo bind datasources explicitly</title> - <para> - Edit server/default/conf/gatein/configuration.properties and comment out next rows in JCR section: - </para> - + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configurations_Steps-Do_not_let_eXo_bind_datasources_explicitly"> + <title>Do not let eXo bind datasources explicitly</title> + <para> + Edit server/default/conf/gatein/configuration.properties and comment out next rows in JCR section: + </para> + <programlisting>#gatein.jcr.datasource.driver=org.hsqldb.jdbcDriver #gatein.jcr.datasource.url=jdbc:hsqldb:file:${gatein.db.data.dir}/data/jdbcjcr_${name} #gatein.jcr.datasource.username=sa #gatein.jcr.datasource.password=</programlisting> - <para> - and in IDM section: - </para> - + <para> + and in IDM section: + </para> + <programlisting>#gatein.idm.datasource.driver=org.hsqldb.jdbcDriver #gatein.idm.datasource.url=jdbc:hsqldb:file:${gatein.db.data.dir}/data/jdbcidm_${name} #gatein.idm.datasource.username=sa #gatein.idm.datasource.password=</programlisting> - <para> - In jcr-configuration.xml and idm-configuration.xml comment out the plugin InitialContextInitializer. - </para> - + <para> + In jcr-configuration.xml and idm-configuration.xml comment out the plugin InitialContextInitializer. + </para> + <programlisting language="XML" role="XML">&lt;!-- Commented because, Datasources are declared and bound by AS, not in eXo --&gt; &lt;!-- &lt;external-component-plugins&gt; [...] &lt;/external-component-plugins&gt; --&gt;</programlisting> - <para> - Running eXo after these configurations goes well. - </para> + <para> + Running eXo after these configurations goes well. + </para> - </section> - + </section> + - </section> - + </section> + -</section> +</chapter> Copied: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR.xml (from rev 8089, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR.xml) =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR.xml (rev 0) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR.xml 2011-11-18 02:57:59 UTC (rev 8091) @@ -0,0 +1,98 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +%BOOK_ENTITIES; +]> +<part id="part-Reference_Guide_eXo_JCR_1.14-eXo_JCR"> + <title><remark>Java Content Repository</remark></title> + <!--<xi:include href="eXoJCR/eXoJCR/jcr.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />--> + <xi:include href="eXoJCR/jcr/intro.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!-- concepts --> + <!-- <xi:include href="eXoJCR/jcr/concepts/why-jcr.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> + <xi:include href="eXoJCR/jcr/concepts/jcr-exo-implementation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/concepts/jcr-advantages.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/concepts/jcr-compatibility-levels.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/concepts/jcr-usage.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!-- <xi:include href="eXoJCR/jcr/concepts/jcr-extensions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> + <xi:include href="eXoJCR/jcr/concepts/jcr-applications.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/concepts/nodetypes-and-namespaces.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/concepts/nodetype-registration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/concepts/jcr-registry-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/concepts/jcr-namespace-altering.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!-- common configs --> + <xi:include href="eXoJCR/jcr/configuration/exo-jcr-configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/configuration/multilanguage-support.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/configuration/search-configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/configuration/configuration-persister.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/configuration/jdbc-data-container-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/configuration/external-value-storages.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/configuration/workspace-persistence-storage.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/configuration/rest-services-on-groovy.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!-- cluster configs --> + <xi:include href="eXoJCR/jcr/cluster-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/jbosscache-configuration-templates.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/lock-manager-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/query-handler-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/jbossts-transaction-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/transaction-manager-lookup.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/repository-creation-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!-- search --> + <xi:include href="eXoJCR/jcr/searching/jcr-query-usecases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/searching/searching-repository-content.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/searching/fulltext-search-and-settings.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + + <!-- api extensions --> + <xi:include href="eXoJCR/jcr/api-extensions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!-- protocols --> + <xi:include href="eXoJCR/jcr/protocols/webdav.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/protocols/ftp.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!-- backup --> + <xi:include href="eXoJCR/jcr/backup/exojcr-backup-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/backup/backup-client.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/backup/use-external-backup-tool.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!-- other --> + <xi:include href="eXoJCR/jcr/statistics.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/repository-check-controller.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/jta.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/jca.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/other/acl.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/other/acl-ext.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/other/link-producer.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/other/binary-values-processing.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="eXoJCR/jcr/other/jcr-resources.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!-- data container configs --> + <xi:include href="eXoJCR/jcr/data-container.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!-- <xi:include href="eXoJCR/jcr/data-container-howto.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> + + <xi:include href="eXoJCR/jcr/db-cleaner-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!-- tuning guide + DOC NOTE: Could possibly be moved to a specific Tuning Guide later --> + <xi:include href="eXoJCR/jcr/performance-tuning-guide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!--JCR Core + DOC NOTE: This section seems to include items covered elsewhere in this guide, or things that are not relevant to EPP + <xi:include href="eXoJCR/core.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> + + <!-- Web services + DOC NOTE: Red Hat JBoss has two possible Web Services packages. No need to document the eXo offering: + <xi:include href="eXoJCR/ws.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />--> + + <!--GateIn and JCR --> + <xi:include href="eXoJCR/jcr-with-gatein.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + + <!--DOC NOTE: Commented FAQ section out as per advice from Philippe Aristote; "Unfit for publication" --> + <!--<xi:include href="eXoJCR/faq.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />--> +</part> +