gatein SVN: r8099 - epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear.
by do-not-reply＠jboss.org
Author: hfnukal
Date: 2011-11-18 09:14:06 -0500 (Fri, 18 Nov 2011)
New Revision: 8099
Modified:
epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml
Log:
JBEPP-1364 EPP-SP: Missing jempbox library in gatein.ear/lib causes error on uploading PDF files
Modified: epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml 2011-11-18 12:07:59 UTC (rev 8098)
+++ epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml 2011-11-18 14:14:06 UTC (rev 8099)
@@ -1158,13 +1158,13 @@
<dependency>
<groupId>org.apache.pdfbox</groupId>
<artifactId>fontbox</artifactId>
- <version>1.1.0</version>
+ <version>1.4.0</version>
</dependency>
<dependency>
<groupId>org.apache.pdfbox</groupId>
<artifactId>jempbox</artifactId>
- <version>1.1.0</version>
+ <version>1.4.0</version>
</dependency>
12 years, 6 months
- 1
- 0
gatein SVN: r8098 - epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear.
by do-not-reply＠jboss.org
Author: hfnukal
Date: 2011-11-18 07:07:59 -0500 (Fri, 18 Nov 2011)
New Revision: 8098
Modified:
epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml
Log:
JBEPP-1364 EPP-SP: Missing jempbox library in gatein.ear/lib causes error on uploading PDF files
Modified: epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml 2011-11-18 11:00:19 UTC (rev 8097)
+++ epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml 2011-11-18 12:07:59 UTC (rev 8098)
@@ -1155,6 +1155,19 @@
</exclusions>
</dependency>
+ <dependency>
+ <groupId>org.apache.pdfbox</groupId>
+ <artifactId>fontbox</artifactId>
+ <version>1.1.0</version>
+ </dependency>
+
+ <dependency>
+ <groupId>org.apache.pdfbox</groupId>
+ <artifactId>jempbox</artifactId>
+ <version>1.1.0</version>
+ </dependency>
+
+
<dependency>
<groupId>commons-codec</groupId>
<artifactId>commons-codec</artifactId>
12 years, 6 months
- 1
- 0
gatein SVN: r8097 - epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-sso.
by do-not-reply＠jboss.org
Author: hfnukal
Date: 2011-11-18 06:00:19 -0500 (Fri, 18 Nov 2011)
New Revision: 8097
Modified:
epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-sso/pom.xml
Log:
JBEPP-1355 Doc and src packaging, git support
Modified: epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-sso/pom.xml
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-sso/pom.xml 2011-11-18 10:59:33 UTC (rev 8096)
+++ epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-sso/pom.xml 2011-11-18 11:00:19 UTC (rev 8097)
@@ -16,7 +16,7 @@
<name>sso</name>
<properties>
- <doc.path>${project.name-apidoc}</doc.path>
+ <doc.path>${project.name}-apidc</doc.path>
<source.path>${project.name}</source.path>
<scm.type>svn</scm.type>
12 years, 6 months
- 1
- 0
gatein SVN: r8096 - in epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src: patch/EAP and 1 other directory.
by do-not-reply＠jboss.org
Author: hfnukal
Date: 2011-11-18 05:59:33 -0500 (Fri, 18 Nov 2011)
New Revision: 8096
Added:
epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/patch/EAP/http-invoker.sar.invoker.war.web.xml.patch
Modified:
epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/build.xml
Log:
JBEPP-1324 Fix CVE-2011-4085 in the next release
Modified: epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/build.xml
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/build.xml 2011-11-18 10:58:40 UTC (rev 8095)
+++ epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/build.xml 2011-11-18 10:59:33 UTC (rev 8096)
@@ -78,6 +78,8 @@
</zip>
</target>
+ <target name="finalTasks" depends="modifyStartupMessage,http-ivoker-PATCH,jbossws-native-PATCH">
+ </target>
<!-- Patching startup message in log when starting portal -->
<target name="modifyStartupMessage">
@@ -114,4 +116,32 @@
<zip destfile="${epp.path}/jboss-as/bin/run.jar" basedir="${basedir}/target/work/run.jar/" update="true">
</zip>
</target>
+
+ <target name="http-ivoker-PATCH">
+ <echo>Patching EAP http-ivoker.sar/invoker.war/web.xml ...</echo>
+ <patch
+ originalfile="${epp.path}/jboss-as/server/production/deploy/httpha-invoker.sar/invoker.war/WEB-INF/web.xml"
+ patchfile="src/patch/EAP/http-invoker.sar.invoker.war.web.xml.patch"
+ failonerror="true"
+ />
+ <patch
+ originalfile="${epp.path}/jboss-as/server/all/deploy/httpha-invoker.sar/invoker.war/WEB-INF/web.xml"
+ patchfile="src/patch/EAP/http-invoker.sar.invoker.war.web.xml.patch"
+ failonerror="true"
+ />
+ <patch
+ originalfile="${epp.path}/jboss-as/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/web.xml"
+ patchfile="src/patch/EAP/http-invoker.sar.invoker.war.web.xml.patch"
+ failonerror="true"
+ />
+ </target>
+ <target name="jbossws-native-PATCH">
+ <echo>One-off patch for JBPAPP-7108</echo>
+ <property name="resource_jar" value="${basedir}/src/main/resources/eap/jbossws-native-PATCH/jbossws-common-1.1.0.SP7-patch-02.jar" />
+ <copy overwrite="true" file="${resource_jar}" tofile="${epp.path}/jboss-as/client/jbossws-common.jar"/>
+ <copy overwrite="true" file="${resource_jar}" tofile="${epp.path}/jboss-as/common/lib/jbossws-common.jar"/>
+ <copy overwrite="true" file="${resource_jar}" tofile="${epp.path}/jboss-as/server/default/deployers/jbossws.deployer/jbossws-common.jar"/>
+ <copy overwrite="true" file="${resource_jar}" tofile="${epp.path}/jboss-as/server/production/deployers/jbossws.deployer/jbossws-common.jar"/>
+ <copy overwrite="true" file="${resource_jar}" tofile="${epp.path}/jboss-as/server/all/deployers/jbossws.deployer/jbossws-common.jar"/>
+ </target>
</project>
\ No newline at end of file
Added: epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/patch/EAP/http-invoker.sar.invoker.war.web.xml.patch
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/patch/EAP/http-invoker.sar.invoker.war.web.xml.patch (rev 0)
+++ epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/patch/EAP/http-invoker.sar.invoker.war.web.xml.patch 2011-11-18 10:59:33 UTC (rev 8096)
@@ -0,0 +1,12 @@
+diff -uNr web.xml.orig web.xml
+--- web.xml.orig 2011-11-15 00:43:07.000000000 +0100
++++ web.xml 2011-11-15 00:43:25.000000000 +0100
+@@ -159,8 +159,6 @@
+ <url-pattern>/JNDIFactory/*</url-pattern>
+ <url-pattern>/EJBInvokerServlet/*</url-pattern>
+ <url-pattern>/JMXInvokerServlet/*</url-pattern>
+- <http-method>GET</http-method>
+- <http-method>POST</http-method>
+ </web-resource-collection>
+ <auth-constraint>
+ <role-name>HttpInvoker</role-name>
12 years, 6 months
- 1
- 0
gatein SVN: r8095 - in epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp: src/main/resources/eap and 1 other directories.
by do-not-reply＠jboss.org
Author: hfnukal
Date: 2011-11-18 05:58:40 -0500 (Fri, 18 Nov 2011)
New Revision: 8095
Added:
epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/main/resources/eap/jbossws-native-PATCH/
epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/main/resources/eap/jbossws-native-PATCH/jbossws-common-1.1.0.SP7-patch-02.jar
Modified:
epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/pom.xml
Log:
JBEPP-1352 A security issue has been identified in jbossws-native that impacts EPP, BZ#692584 (EPP5)
Modified: epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/pom.xml
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/pom.xml 2011-11-18 07:29:44 UTC (rev 8094)
+++ epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/pom.xml 2011-11-18 10:58:40 UTC (rev 8095)
@@ -174,7 +174,7 @@
</ant>
<ant antfile="src/build.xml" inheritRefs="true">
- <target name="modifyStartupMessage"/>
+ <target name="finalTasks"/>
</ant>
</target>
@@ -245,7 +245,7 @@
</ant>
<ant antfile="src/build.xml" inheritRefs="true">
- <target name="modifyStartupMessage"/>
+ <target name="finalTasks"/>
</ant>
</target>
@@ -376,7 +376,7 @@
</ant>
<ant antfile="src/build.xml" inheritRefs="true">
- <target name="modifyStartupMessage"/>
+ <target name="finalTasks"/>
</ant>
</target>
@@ -469,7 +469,7 @@
</ant>
<ant antfile="src/build.xml" inheritRefs="true">
- <target name="modifyStartupMessage"/>
+ <target name="finalTasks"/>
</ant>
</target>
Added: epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/main/resources/eap/jbossws-native-PATCH/jbossws-common-1.1.0.SP7-patch-02.jar
===================================================================
(Binary files differ)
Property changes on: epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/main/resources/eap/jbossws-native-PATCH/jbossws-common-1.1.0.SP7-patch-02.jar
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
12 years, 6 months
- 1
- 0
gatein SVN: r8094 - epp/portal/branches.
by do-not-reply＠jboss.org
Author: mputz
Date: 2011-11-18 02:29:44 -0500 (Fri, 18 Nov 2011)
New Revision: 8094
Added:
epp/portal/branches/EPP_5_1_1_GA_JBEPP-1374/
Log:
JBEPP-1374 - Creation of support patch branch
12 years, 6 months
- 1
- 0
gatein SVN: r8093 - in epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR: jcr/backup and 6 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-11-17 23:01:09 -0500 (Thu, 17 Nov 2011)
New Revision: 8093
Removed:
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.bk
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/backup/backup-client.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/backup-clonsole-dist.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/exojcr-backup-service.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/use-external-backup-tool.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-advantages.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-applications.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-compatibility-levels.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-exo-implementation.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-extensions.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-namespace-altering.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-registry-service.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-usage.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/nodetype-registration.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/nodetypes-and-namespaces.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/why-jcr.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/configuration-persister.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/external-value-storages.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/multilanguage-support.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/rest-services-on-groovy.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/workspace-persistence-storage.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/lock-manager-config.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/acl-ext.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/acl.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/binary-values-processing.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/jcr-resources.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/link-producer.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/protocols/ftp.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/protocols/webdav.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/fulltext-search-and-settings.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/searching-repository-content.xml
Log:
Relocate eXoJCR chapter to Part IV and promote sub-sections
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/backup-client.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/backup-client.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/backup-client.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-HTTPBackupAgent_and_Backup_Client">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_and_Backup_Client">
<title><literal>HTTPBackupAgent</literal> and Backup Client</title>
<warning>
<title>Configuration Persistance</title>
@@ -2266,6 +2266,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/backup-clonsole-dist.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/backup-clonsole-dist.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/backup-clonsole-dist.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Backup_Console_Binary_Distribution">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Backup_Console_Binary_Distribution">
<title>Backup Console Binary Distribution</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-Backup_Console_Binary_Distribution-Introduction">
<title>Introduction</title>
@@ -204,6 +204,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/exojcr-backup-service.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/exojcr-backup-service.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/exojcr-backup-service.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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_Backup_Service">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service">
<title>eXo JCR Backup Service</title>
<note>
<para>
@@ -954,6 +954,6 @@
</para>
</section>
- </section>
+ </chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/use-external-backup-tool.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/use-external-backup-tool.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/backup/use-external-backup-tool.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Use_external_backup_tool">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Use_external_backup_tool">
<title>Use External Backup Tool</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-Use_external_backup_tool-Repository_suspending">
<title>Repository Suspending</title>
@@ -77,6 +77,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-advantages.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-advantages.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-advantages.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Advantages_of_eXo_JCR">
+<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Advantages_of_eXo_JCR">
<title>Advantages of eXo JCR</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-Advantages_of_eXo_JCR-Application_Developers">
<title>Application Developers</title>
@@ -79,6 +79,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-applications.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-applications.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-applications.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-eXo_JCR_Application_Model">
- <title>eXo JCR Application Model</title>
- <para>
- The following image illustrates the interaction between Applications and JCR:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/eXoJCR/concepts/jcr-applications.gif" width="444" />
- </imageobject>
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Application_Model">
+ <title>eXo JCR Application Model</title>
+ <para>
+ The following image illustrates the interaction between Applications and JCR:
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/eXoJCR/concepts/jcr-applications.gif" width="444" />
+ </imageobject>
- </mediaobject>
- <para>
- Every Content (JCR) dependent application interacts with the eXo JCR via JSR-170 and the eXo JCR API extension either directly or through an intermediary Framework.
- </para>
- <note>
- <title>Note:</title>
- <para>
- Neither the application nor the framework should ever rely on the implementation directly.
- </para>
+ </mediaobject>
+ <para>
+ Every Content (JCR) dependent application interacts with the eXo JCR via JSR-170 and the eXo JCR API extension either directly or through an intermediary Framework.
+ </para>
+ <note>
+ <title>Note:</title>
+ <para>
+ Neither the application nor the framework should ever rely on the implementation directly.
+ </para>
- </note>
- <para>
- <emphasis role="bold">Content Application:</emphasis> all applications may use the JCR as a data storage. Some of them are generic and completely decoupled from the JCR API as an interaction protocol (such as a WebDav client) hides Content storage nature. Other applications are partially decoupled (such as Command framework based applications), meaning that they do not use the JCR API directly. Most applications use JSR-170 directly.
- </para>
- <para>
- <emphasis role="bold">Frameworks</emphasis> are a special kind of JCR client that act as an intermediate level between the <literal>Content Repository</literal> and an <literal>End Client Application</literal>.
- </para>
- <para>
- Framworks are categorized as follows:
- </para>
- <variablelist>
- <title></title>
- <varlistentry>
- <term>Protocol Specific Frameworks</term>
- <listitem>
- <para>
- Frameworks that are specific to a networking protocol include WebDav, RMI and FTP servers.
- </para>
+ </note>
+ <para>
+ <emphasis role="bold">Content Application:</emphasis> all applications may use the JCR as a data storage. Some of them are generic and completely decoupled from the JCR API as an interaction protocol (such as a WebDav client) hides Content storage nature. Other applications are partially decoupled (such as Command framework based applications), meaning that they do not use the JCR API directly. Most applications use JSR-170 directly.
+ </para>
+ <para>
+ <emphasis role="bold">Frameworks</emphasis> are a special kind of JCR client that act as an intermediate level between the <literal>Content Repository</literal> and an <literal>End Client Application</literal>.
+ </para>
+ <para>
+ Framworks are categorized as follows:
+ </para>
+ <variablelist>
+ <title></title>
+ <varlistentry>
+ <term>Protocol Specific Frameworks</term>
+ <listitem>
+ <para>
+ Frameworks that are specific to a networking protocol include WebDav, RMI and FTP servers.
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
- <varlistentry>
- <term>Pattern Specific Frameworks</term>
- <listitem>
- <para>
- Frameworks that are pattern specific include Command, Web(servlet), J2EE connector
- </para>
+ </varlistentry>
+ <varlistentry>
+ <term>Pattern Specific Frameworks</term>
+ <listitem>
+ <para>
+ Frameworks that are pattern specific include Command, Web(servlet), J2EE connector
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
+ </varlistentry>
- </variablelist>
- <para>
- It is possible to build a multi-layered (in framework sense) JCR application, for example Web application uses Web framework that uses Command framework underneath.
- </para>
-</section>
+ </variablelist>
+ <para>
+ It is possible to build a multi-layered (in framework sense) JCR application, for example Web application uses Web framework that uses Command framework underneath.
+ </para>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-compatibility-levels.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-compatibility-levels.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-compatibility-levels.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -3,146 +3,146 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent">
%BOOK_ENTITIES;
]>
-<section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels">
- <title>Compatibility Levels</title>
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels-Introduction">
- <title>Introduction</title>
- <para>
- The Java Content Repository specification JSR-170 has been split into two compliance levels as well as a set of optional features. <literal>Level 1</literal> defines a read-only repository while <literal>Level 2</literal> defines methods for writing content and bi-directional interaction with the repository.
- </para>
- <para>
- The eXo JCR supports JSR-170 Level 1 and Level 2 and all optional features. The recent JSR-283 is not yet supported.
- </para>
+<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels">
+ <title>Compatibility Levels</title>
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels-Introduction">
+ <title>Introduction</title>
+ <para>
+ The Java Content Repository specification JSR-170 has been split into two compliance levels as well as a set of optional features. <literal>Level 1</literal> defines a read-only repository while <literal>Level 2</literal> defines methods for writing content and bi-directional interaction with the repository.
+ </para>
+ <para>
+ The eXo JCR supports JSR-170 Level 1 and Level 2 and all optional features. The recent JSR-283 is not yet supported.
+ </para>
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels-Level_1">
- <title>Level 1</title>
- <para>
- Level 1 includes read-only functionality for very simple repositories. It is useful to migrate an existing data repository and step through converting it to a more advanced implementation. The JCR uses a well-known Session abstraction to access the repository data.
- </para>
- <para>
- The features of Level 1:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Initiating a session calling login method with the name of desired workspace and client credentials. It involves some security mechanisms (JAAS) to authenticate the client and in case the client is authorized to use the data from a particular workspace, it can retrieve the session with a workspace tied to it.
- </para>
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels-Level_1">
+ <title>Level 1</title>
+ <para>
+ Level 1 includes read-only functionality for very simple repositories. It is useful to migrate an existing data repository and step through converting it to a more advanced implementation. The JCR uses a well-known Session abstraction to access the repository data.
+ </para>
+ <para>
+ The features of Level 1:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Initiating a session calling login method with the name of desired workspace and client credentials. It involves some security mechanisms (JAAS) to authenticate the client and in case the client is authorized to use the data from a particular workspace, it can retrieve the session with a workspace tied to it.
+ </para>
- </listitem>
- <listitem>
- <para>
- Using the obtained session, the client can retrieve data (items) by traversing the tree, directly accessing a particular item (requesting path or UUID) or traversing the query result. So an application developer can choose the "best" form depending on the content structure and desired operation.
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ Using the obtained session, the client can retrieve data (items) by traversing the tree, directly accessing a particular item (requesting path or UUID) or traversing the query result. So an application developer can choose the "best" form depending on the content structure and desired operation.
+ </para>
- </listitem>
- <listitem>
- <para>
- Reading property values. All content of a repository is ultimately accessed through properties and stored in property values of predefined types (Boolean, Binary Data, Double, Long, String) and special types Name, Reference, and Path. It is possible to read property value without knowing its real name as a primary item.
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ Reading property values. All content of a repository is ultimately accessed through properties and stored in property values of predefined types (Boolean, Binary Data, Double, Long, String) and special types Name, Reference, and Path. It is possible to read property value without knowing its real name as a primary item.
+ </para>
- </listitem>
- <listitem>
- <para>
- Export to XML. The repository supports two XML/JCR data model mappings: <literal>system</literal> and <literal>doc</literal> view. The system view provides complete XML serialization without loss of information and is somewhat difficult for a human to read. In contrast, the document view is human readable but does not completely reflect the state of repository; it is used for Xpath queries.
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ Export to XML. The repository supports two XML/JCR data model mappings: <literal>system</literal> and <literal>doc</literal> view. The system view provides complete XML serialization without loss of information and is somewhat difficult for a human to read. In contrast, the document view is human readable but does not completely reflect the state of repository; it is used for Xpath queries.
+ </para>
- </listitem>
- <listitem>
- <para>
- A query facility with Xpath syntax. Xpath, originally developed for XML, suits the JCR data model as the two models are similar. Xpath is applied to the JCR as it would be applied to the document view of the serialized repository content; returning a table of property names and content matching the query.
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ A query facility with Xpath syntax. Xpath, originally developed for XML, suits the JCR data model as the two models are similar. Xpath is applied to the JCR as it would be applied to the document view of the serialized repository content; returning a table of property names and content matching the query.
+ </para>
- </listitem>
- <listitem>
- <para>
- Discovery of available node types. Every node should have only one primary node type that defines names, types and other characteristics of child nodes and properties. It also can have one or more mixin data types that defines additional characteristics. Level 1 provides methods for discovering available in repository node types and node types of a concrete node.
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ Discovery of available node types. Every node should have only one primary node type that defines names, types and other characteristics of child nodes and properties. It also can have one or more mixin data types that defines additional characteristics. Level 1 provides methods for discovering available in repository node types and node types of a concrete node.
+ </para>
- </listitem>
- <listitem>
- <para>
- Transient namespace remapping. Item name can have prefix, delimited by a single ':' (colon) character that indicates the namespace of this name. It is patterned after XML namespaces, prefix is mapped to URI to minimize names collisions. In Level 1, a prefix can be temporary overridden by another prefix in the scope of a session.
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ Transient namespace remapping. Item name can have prefix, delimited by a single ':' (colon) character that indicates the namespace of this name. It is patterned after XML namespaces, prefix is mapped to URI to minimize names collisions. In Level 1, a prefix can be temporary overridden by another prefix in the scope of a session.
+ </para>
- </listitem>
+ </listitem>
- </itemizedlist>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/eXoJCR/concepts/level_1.gif" />
- </imageobject>
+ </itemizedlist>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/eXoJCR/concepts/level_1.gif" />
+ </imageobject>
- </mediaobject>
+ </mediaobject>
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels-Level_2">
- <title>Level 2</title>
- <para>
- JCR Level 2 includes reading and writing of content functionality, importing other sources and managing content definition and structuring using extensible node types.
- </para>
- <para>
- In addition to the features of Level 1, it also supports the following major features:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Adding, moving, copying and removing items inside workspace and moving, copying and cloning items between workspaces. The client can also compare the persisted state of an item with its unsaved states and either save the new state or discard it.
- </para>
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels-Level_2">
+ <title>Level 2</title>
+ <para>
+ JCR Level 2 includes reading and writing of content functionality, importing other sources and managing content definition and structuring using extensible node types.
+ </para>
+ <para>
+ In addition to the features of Level 1, it also supports the following major features:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Adding, moving, copying and removing items inside workspace and moving, copying and cloning items between workspaces. The client can also compare the persisted state of an item with its unsaved states and either save the new state or discard it.
+ </para>
- </listitem>
- <listitem>
- <para>
- Modifying and writing value of properties. Property types are checked and can be converted to the defined format.
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ Modifying and writing value of properties. Property types are checked and can be converted to the defined format.
+ </para>
- </listitem>
- <listitem>
- <para>
- Importing XML document into the repository as a tree of nodes and properties. If the XML document is an export of JCR system view, the content of repository can be completely restored. If this is not the case, the document is interpreted as a document view and the import procedure builds a tree of JCR nodes and properties that matches the tree structure of the XML document.
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ Importing XML document into the repository as a tree of nodes and properties. If the XML document is an export of JCR system view, the content of repository can be completely restored. If this is not the case, the document is interpreted as a document view and the import procedure builds a tree of JCR nodes and properties that matches the tree structure of the XML document.
+ </para>
- </listitem>
- <listitem>
- <para>
- Assigning node types to nodes. The primary node type is assigned when adding a node. This can be done automatically based on the parent node type definition and mixin node types.
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ Assigning node types to nodes. The primary node type is assigned when adding a node. This can be done automatically based on the parent node type definition and mixin node types.
+ </para>
- </listitem>
- <listitem>
- <para>
- Persistent namespaces changes. Adding, changing and removing namespaces stored in the namespace registry, excluding built-in namespaces required by JCR.
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ Persistent namespaces changes. Adding, changing and removing namespaces stored in the namespace registry, excluding built-in namespaces required by JCR.
+ </para>
- </listitem>
+ </listitem>
- </itemizedlist>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/eXoJCR/concepts/level_2.gif" />
- </imageobject>
+ </itemizedlist>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/eXoJCR/concepts/level_2.gif" />
+ </imageobject>
- </mediaobject>
+ </mediaobject>
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels-Optional_features">
- <title>Optional features</title>
- <para>
- On the top of Level 1 or Level 2, a number of optional features are defined for a more advanced repository functionality. This includes functions such as Versioning, (JTA) Transactions, Query using SQL, Explicit Locking and Content Observation. eXo JCR supports all optional features.
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/eXoJCR/concepts/optional.gif" />
- </imageobject>
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels-Optional_features">
+ <title>Optional features</title>
+ <para>
+ On the top of Level 1 or Level 2, a number of optional features are defined for a more advanced repository functionality. This includes functions such as Versioning, (JTA) Transactions, Query using SQL, Explicit Locking and Content Observation. eXo JCR supports all optional features.
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/eXoJCR/concepts/optional.gif" />
+ </imageobject>
- </mediaobject>
+ </mediaobject>
- </section>
-
+ </section>
+
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-exo-implementation.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-exo-implementation.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-exo-implementation.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Implementation">
+<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Implementation">
<!-- This document was created with Syntext Serna Free. -->
<title>Implementation</title>
<para>
@@ -184,6 +184,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-extensions.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-extensions.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-extensions.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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_Extensions">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Extensions">
<title>JCR Extensions</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Extensions-JCR_Service_Extensions">
<title>JCR Service Extensions</title>
@@ -213,6 +213,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-namespace-altering.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-namespace-altering.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-namespace-altering.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Namespace_Altering">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Namespace_Altering">
<!-- This document was created with Syntext Serna Free. --> <title>Namespace Altering</title>
<para>
Since version 1.11, the eXo JCR implementation supports namespaces altering.
@@ -40,6 +40,6 @@
<programlisting language="Java" role="Java">ExtendedNamespaceRegistry namespaceRegistry = (ExtendedNamespaceRegistry) workspace.getNamespaceRegistry();
namespaceRegistry.registerNamespace("newMapping", "http://dumb.uri/jcr");
namespaceRegistry.unregisterNamespace("newMapping");</programlisting>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-registry-service.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-registry-service.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-registry-service.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -3,23 +3,23 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent">
%BOOK_ENTITIES;
]>
-<section id="sect-Reference_Guide_eXo_JCR_1.14-Registry_Service">
- <title>Registry Service</title>
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Registry_Service-Concept">
- <title>Concept</title>
- <para>
- The Registry Service is one of the key parts of the infrastructure built around eXo JCR. Each JCR that is based on services and applications may have its own configuration, settings, and other data that have to be stored persistently and used by the appropriate service or application (referred to as a <emphasis>Consumer</emphasis>).
- </para>
- <para>
- The service acts as a centralized collector (Registry) for such data. A registry storage is JCR based, that is, it is stored in some JCR workspace (one per Repository) as an Item tree under a <literal>/exo:registry</literal> node.
- </para>
- <para>
- Despite the fact that the structure of the tree is well defined (see the scheme below), it is not recommended for other services to manipulate data using the JCR API directly. So the Registry Service acts as a mediator between a Consumer and its settings.
- </para>
- <para>
- The proposed structure of the Registry Service storage is divided into three logical groups: services, applications and users:
- </para>
-
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Registry_Service">
+ <title>Registry Service</title>
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Registry_Service-Concept">
+ <title>Concept</title>
+ <para>
+ The Registry Service is one of the key parts of the infrastructure built around eXo JCR. Each JCR that is based on services and applications may have its own configuration, settings, and other data that have to be stored persistently and used by the appropriate service or application (referred to as a <emphasis>Consumer</emphasis>).
+ </para>
+ <para>
+ The service acts as a centralized collector (Registry) for such data. A registry storage is JCR based, that is, it is stored in some JCR workspace (one per Repository) as an Item tree under a <literal>/exo:registry</literal> node.
+ </para>
+ <para>
+ Despite the fact that the structure of the tree is well defined (see the scheme below), it is not recommended for other services to manipulate data using the JCR API directly. So the Registry Service acts as a mediator between a Consumer and its settings.
+ </para>
+ <para>
+ The proposed structure of the Registry Service storage is divided into three logical groups: services, applications and users:
+ </para>
+
<programlisting> exo:registry/ <-- registry "root" (exo:registry)
exo:services/ <-- service data storage (exo:registryGroup)
service1/
@@ -33,26 +33,26 @@
user1/
Consumer data (exo:registryEntry)
...</programlisting>
- <para>
- Each upper level Service may store its configuration in the Registry. At first start the service can call its settings from an XML configuration file and, once the settings have been stored, from then on call settings from the Registry.
- </para>
- <para>
- In a configuration file, you can add the <parameter>force-xml-configuration</parameter> parameter to the component to force it to ignore reading parameter initialization from <literal>RegistryService</literal> and to use the configuration file instead:
- </para>
-
+ <para>
+ Each upper level Service may store its configuration in the Registry. At first start the service can call its settings from an XML configuration file and, once the settings have been stored, from then on call settings from the Registry.
+ </para>
+ <para>
+ In a configuration file, you can add the <parameter>force-xml-configuration</parameter> parameter to the component to force it to ignore reading parameter initialization from <literal>RegistryService</literal> and to use the configuration file instead:
+ </para>
+
<programlisting language="XML" role="XML"><value-param>
<name>force-xml-configuration</name>
<value>true</value>
</value-param></programlisting>
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Registry_Service-The_API">
- <title>The API</title>
- <para>
- The main functionality of the Registry Service is described in the Registry abstract class as the following:
- </para>
-
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Registry_Service-The_API">
+ <title>The API</title>
+ <para>
+ The main functionality of the Registry Service is described in the Registry abstract class as the following:
+ </para>
+
<programlisting language="Java" role="Java">public abstract class Registry {
/**
@@ -84,16 +84,16 @@
*/
public abstract void removeEntry(SessionProvider sessionProvider,
String groupName, String entryName) throws RepositoryException;</programlisting>
- <para>
- This is a CRUD interface as the <literal>RegistryEntry</literal> object which wraps registry data for some Consumer as a Registry Entry. The Registry Service itself is unaware of the wrapping data as it is the Consumer's responsibility to manage and use its data in its own way.
- </para>
- <para>
- To create an Entity Consumer you should know how to serialize the data to some XML structure and then create a <literal>RegistryEntry</literal> from these data at once or populate them in a <literal>RegistryEntry</literal> object by using <literal>RegistryEntry(String entryName)</literal> constructor and then obtain and fill a DOM document.
- </para>
- <para>
- An example of <literal>RegistryService</literal> using:
- </para>
-
+ <para>
+ This is a CRUD interface as the <literal>RegistryEntry</literal> object which wraps registry data for some Consumer as a Registry Entry. The Registry Service itself is unaware of the wrapping data as it is the Consumer's responsibility to manage and use its data in its own way.
+ </para>
+ <para>
+ To create an Entity Consumer you should know how to serialize the data to some XML structure and then create a <literal>RegistryEntry</literal> from these data at once or populate them in a <literal>RegistryEntry</literal> object by using <literal>RegistryEntry(String entryName)</literal> constructor and then obtain and fill a DOM document.
+ </para>
+ <para>
+ An example of <literal>RegistryService</literal> using:
+ </para>
+
<programlisting language="Java" role="Java"> RegistryService regService = (RegistryService) container
.getComponentInstanceOfType(RegistryService.class);
@@ -105,14 +105,14 @@
String mySetting = getElementsByTagName("tagname").item(index).getTextContent();
.....</programlisting>
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Registry_Service-Configuration">
- <title>Configuration</title>
- <para>
- <literal>RegistryService</literal> has only one optional properties parameter; <parameter>locations</parameter>. It is used to mention where <literal>exo:registry</literal> is placed for each repository. The name of each property is interpreted as a repository name and its value as a workspace name (a system workspace by default).
- </para>
-
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Registry_Service-Configuration">
+ <title>Configuration</title>
+ <para>
+ <literal>RegistryService</literal> has only one optional properties parameter; <parameter>locations</parameter>. It is used to mention where <literal>exo:registry</literal> is placed for each repository. The name of each property is interpreted as a repository name and its value as a workspace name (a system workspace by default).
+ </para>
+
<programlisting language="XML" role="XML"><component>
<type>org.exoplatform.services.jcr.ext.registry.RegistryService</type>
<init-params>
@@ -123,9 +123,9 @@
</init-params>
</component></programlisting>
- </section>
-
+ </section>
+
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-usage.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-usage.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/jcr-usage.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Using_The_JCR">
+<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Using_The_JCR">
<title>Using The JCR</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-Using_The_JCR-Obtaining_a_Repository_Object">
<title>Obtaining a Repository Object</title>
@@ -247,6 +247,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/nodetype-registration.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/nodetype-registration.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/nodetype-registration.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-NodeType_Registration">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-NodeType_Registration">
<!-- This document was created with Syntext Serna Free. --> <title>NodeType Registration</title>
<para>
The eXo JCR implementation supports two methods of Nodetypes registration:
@@ -546,6 +546,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/nodetypes-and-namespaces.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/nodetypes-and-namespaces.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/nodetypes-and-namespaces.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Node_Types_and_Namespaces">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Node_Types_and_Namespaces">
<title>Node Types and Namespaces</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-Node_Types_and_Namespaces-Introduction">
<title>Introduction</title>
@@ -146,6 +146,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/why-jcr.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/why-jcr.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/concepts/why-jcr.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Java_Content_Repository">
+<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Java_Content_Repository">
<title>Java Content Repository</title>
<para>
A Java Content Repository (<abbrev>JCR</abbrev>) is a java interface used to access contents that are not only web contents, but also other hierarchically stored data. The content is stored in a repository. The repository can be a file system, a relational database or an XML document. The internal structure of JCR data looks similar to an XML document; a document tree with nodes and data, however, in a JCR, the data is stored in <literal>property items</literal>.
@@ -23,6 +23,6 @@
<para>
Roy T. Fielding, <ulink url="http://www.day.com/content/dam/day/whitepapers/JSR_170_White_Paper.pdf">JSR 170 Overview: Standardizing the Content Repository Interface</ulink> (March 13, 2005)
</para>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/configuration-persister.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/configuration-persister.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/configuration-persister.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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_Configuration_persister">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister">
<title>JCR Configuration persister</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister-Concept">
<title>Concept</title>
@@ -144,6 +144,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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_configuration">
+ <chapter id="sect-Reference_Guide_eXo_JCR_1.14-JCR_configuration">
<title>JCR configuration</title>
<para>
@@ -220,7 +220,7 @@
<!--15-->
<area coords="61 60" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-service_lock-manager-timeout" />
</areaspec>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_Configuration/orig.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_Configuration/orig.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<calloutlist>
<!--1-->
@@ -697,4 +697,4 @@
</orderedlist>
</section>
</section>
- </section>
+ </chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/external-value-storages.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/external-value-storages.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/external-value-storages.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-External_Value_Storages">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-External_Value_Storages">
<title>External Value Storages</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-External_Value_Storages-Introduction">
<title>Introduction</title>
@@ -40,7 +40,7 @@
</areaspec>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_external-value-storages/default25.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_external-value-storages/default25.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<calloutlist>
<callout arearefs="area-Reference_Guide_eXo_JCR_1.14-External_Value_Storages-Tree_File_Value_Storage-id">
<para>
@@ -78,7 +78,7 @@
In this example a value matches the 20MB filter <property>min-value-size</property> and will be stored in the path "<literal>data/20Mvalues</literal>". All other filters will be stored in "<literal>data/values</literal>".
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_external-value-storages/default26.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_external-value-storages/default26.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
</section>
@@ -95,7 +95,7 @@
<para>
Holds Values in flat file system files. <property>path</property> property points to root directory in order to store files
</para>
-<programlisting language="Java" role="Java"><xi:include parse="text" href="../../../extras/Advanced_Development_JCR_external-value-storages/default27.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../../../extras/Advanced_Development_JCR_external-value-storages/default27.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<programlisting><value-storage id="Storage #1" class="org.exoplatform.services.jcr.impl.storage.value.fs.SimpleFileValueStorage">
<properties>
<property name="path" value="data/values"/>
@@ -146,7 +146,7 @@
To enable CAS support just configure it in the JCR Repositories configuration with other Value Storages.
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_external-value-storages/default28.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_external-value-storages/default28.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Content_Addressable_Value_storage_CAS_support-CAS_Properties">
<title>CAS Properties</title>
<varlistentry>
@@ -213,6 +213,6 @@
</warning>
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-JDBC_Data_Container_Config">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config">
<title>JDBC Data Container Config</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config-Introduction">
<title>Introduction</title>
@@ -391,7 +391,7 @@
</para>
<programlisting language="XML" role="XML">
-<xi:include href="../../../../../extras/Advanced_Development_JCR_Configuration/example-1.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<xi:include href="../../../../extras/Advanced_Development_JCR_Configuration/example-1.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<substeps>
<step>
<para>
@@ -469,7 +469,7 @@
</para>
<programlisting language="XML" role="XML">
-<xi:include href="../../../../../extras/Advanced_Development_JCR_Configuration/example-2.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<xi:include href="../../../../extras/Advanced_Development_JCR_Configuration/example-2.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<itemizedlist>
<listitem>
<para>
@@ -523,7 +523,7 @@
<title><parameter>jdbcjcr</parameter> Data Container</title>
<programlisting language="XML" role="XML">
-<xi:include href="../../../../../extras/Advanced_Development_JCR_Configuration/example-3.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<xi:include href="../../../../extras/Advanced_Development_JCR_Configuration/example-3.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
</example>
<para>
Configure repository workspaces with this one database. The <parameter>multi-db</parameter> parameter must be set as <literal>false</literal>.
@@ -535,7 +535,7 @@
<title>Example</title>
<programlisting language="XML" role="XML">
-<xi:include href="../../../../../extras/Advanced_Development_JCR_Configuration/example-4.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<xi:include href="../../../../extras/Advanced_Development_JCR_Configuration/example-4.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
</example>
<para>
This configures two persistent workspaces in one database (PostgreSQL).
@@ -731,6 +731,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/multilanguage-support.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/multilanguage-support.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/multilanguage-support.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -3,71 +3,71 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent">
%BOOK_ENTITIES;
]>
-<section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB">
- <title>Multi-language Support the JCR RDB</title>
- <para>
- Whenever a relational database is used to store multilingual text data in the eXo Java Content Repository the configuration must be adapted to support UTF-8 encoding. Dialect is automatically detected for certified database. You can still enforce it in case of failure, see below.
- </para>
- <para>
- The following sections describe enabling UTF-8 support with various databases.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-Oracle" />
- </para>
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB">
+ <title>Multi-language Support the JCR RDB</title>
+ <para>
+ Whenever a relational database is used to store multilingual text data in the eXo Java Content Repository the configuration must be adapted to support UTF-8 encoding. Dialect is automatically detected for certified database. You can still enforce it in case of failure, see below.
+ </para>
+ <para>
+ The following sections describe enabling UTF-8 support with various databases.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-Oracle" />
+ </para>
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-DB2" />
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-DB2" />
+ </para>
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-MySQL" />
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-MySQL" />
+ </para>
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-PostgreSQL" />
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-PostgreSQL" />
+ </para>
- </listitem>
+ </listitem>
- </itemizedlist>
- <note>
- <itemizedlist>
- <listitem>
- <para>
- The configuration file to be modified for these changes is <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/jcr/repository-configuration.xml</filename>.
- </para>
+ </itemizedlist>
+ <note>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The configuration file to be modified for these changes is <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/jcr/repository-configuration.xml</filename>.
+ </para>
- </listitem>
- <listitem>
- <para>
- The datasource <parameter>jdbcjcr</parameter> used in the following examples can be configured via the <literal>InitialContextInitializer</literal> component.
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ The datasource <parameter>jdbcjcr</parameter> used in the following examples can be configured via the <literal>InitialContextInitializer</literal> component.
+ </para>
- </listitem>
+ </listitem>
- </itemizedlist>
+ </itemizedlist>
- </note>
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-Oracle">
- <title>Oracle</title>
- <para>
- In order to run multilanguage JCR on an Oracle backend Unicode encoding for characters set should be applied to the database. Other Oracle globalization parameters do not have any effect. The property to modify is <literal>NLS_CHARACTERSET</literal>.
- </para>
- <para>
- The <literal>NLS_CHARACTERSET = AL32UTF8</literal> entry has been successfully tested with many European and Asian languages.
- </para>
- <para>
- Example of database configuration:
- </para>
-
+ </note>
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-Oracle">
+ <title>Oracle</title>
+ <para>
+ In order to run multilanguage JCR on an Oracle backend Unicode encoding for characters set should be applied to the database. Other Oracle globalization parameters do not have any effect. The property to modify is <literal>NLS_CHARACTERSET</literal>.
+ </para>
+ <para>
+ The <literal>NLS_CHARACTERSET = AL32UTF8</literal> entry has been successfully tested with many European and Asian languages.
+ </para>
+ <para>
+ Example of database configuration:
+ </para>
+
<programlisting>NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
@@ -87,101 +87,101 @@
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16</programlisting>
- <!-- <warning>
+ <!-- <warning>
<para>
JCR 1.12.x doesn't use NVARCHAR columns, so that the value of the parameter NLS_NCHAR_CHARACTERSET does not matter for JCR.
</para>
</warning> --> <para>
- Create database with Unicode encoding and use Oracle dialect for the Workspace Container:
- </para>
-
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_multilanguage-support/default54.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ Create database with Unicode encoding and use Oracle dialect for the Workspace Container:
+ </para>
+
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_multilanguage-support/default54.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-DB2">
- <title>DB2</title>
- <para>
- DB2 Universal Database (DB2 UDB) supports <ulink url="http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.i...">UTF-8 and UTF-16/UCS-2</ulink>. When a Unicode database is created, <parameter>CHAR</parameter>, <parameter>VARCHAR</parameter> and <parameter>LONG VARCHAR</parameter> data are stored in UTF-8 form.
- </para>
- <para>
- This enables JCR multi-lingual support.
- </para>
- <para>
- Below is an example of creating a UTF-8 database using the <parameter>db2</parameter> dialect for a workspace container with DB2 version 9 and higher:
- </para>
-
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-DB2">
+ <title>DB2</title>
+ <para>
+ DB2 Universal Database (DB2 UDB) supports <ulink url="http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.i...">UTF-8 and UTF-16/UCS-2</ulink>. When a Unicode database is created, <parameter>CHAR</parameter>, <parameter>VARCHAR</parameter> and <parameter>LONG VARCHAR</parameter> data are stored in UTF-8 form.
+ </para>
+ <para>
+ This enables JCR multi-lingual support.
+ </para>
+ <para>
+ Below is an example of creating a UTF-8 database using the <parameter>db2</parameter> dialect for a workspace container with DB2 version 9 and higher:
+ </para>
+
<programlisting>DB2 CREATE DATABASE dbname USING CODESET UTF-8 TERRITORY US
</programlisting>
-
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_multilanguage-support/default56.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <note>
- <para>
- For DB2 version 8.<replaceable>x</replaceable> support change the property "dialect" to db2v8.
- </para>
+
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_multilanguage-support/default56.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <note>
+ <para>
+ For DB2 version 8.<replaceable>x</replaceable> support change the property "dialect" to db2v8.
+ </para>
- </note>
+ </note>
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-MySQL">
- <title>MySQL</title>
- <para>
- Using JCR with a MySQL-back end requires a special dialect <ulink url="http://jira.exoplatform.org/browse/JCR-375">MySQL-UTF8</ulink> to be used for internationalization support.
- </para>
- <para>
- The database default charset should be <parameter>latin1</parameter> so as to use limited index space effectively (1000 bytes for an <literal>MyISAM</literal> engine and 767 for <literal>InnoDB</literal>).
- </para>
- <para>
- If the database default charset is multibyte, a JCR database initialization error is encountered concerning index creation failure.
- </para>
- <para>
- JCR can work on any single byte default charset of database, with UTF8 supported by MySQL server. However it has only been tested using the <parameter>latin1</parameter> charset.
- </para>
- <para>
- An example entry:
- </para>
-
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_multilanguage-support/default57.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-MySQL">
+ <title>MySQL</title>
+ <para>
+ Using JCR with a MySQL-back end requires a special dialect <ulink url="http://jira.exoplatform.org/browse/JCR-375">MySQL-UTF8</ulink> to be used for internationalization support.
+ </para>
+ <para>
+ The database default charset should be <parameter>latin1</parameter> so as to use limited index space effectively (1000 bytes for an <literal>MyISAM</literal> engine and 767 for <literal>InnoDB</literal>).
+ </para>
+ <para>
+ If the database default charset is multibyte, a JCR database initialization error is encountered concerning index creation failure.
+ </para>
+ <para>
+ JCR can work on any single byte default charset of database, with UTF8 supported by MySQL server. However it has only been tested using the <parameter>latin1</parameter> charset.
+ </para>
+ <para>
+ An example entry:
+ </para>
+
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_multilanguage-support/default57.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-PostgreSQL">
- <title>PostgreSQL</title>
- <para>
- Multilingual support can be enabled with a PostgreSQL-back end in <ulink url="http://www.postgresql.org/docs/8.3/interactive/charset.html">different ways</ulink>:
- </para>
- <orderedlist>
- <listitem>
- <para>
- Using the locale features of the operating system to provide locale-specific collation order, number formatting, translated messages, and other aspects.
- </para>
- <para>
- UTF-8 is widely used on Linux distributions by default, so it can be useful in such cases.
- </para>
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-PostgreSQL">
+ <title>PostgreSQL</title>
+ <para>
+ Multilingual support can be enabled with a PostgreSQL-back end in <ulink url="http://www.postgresql.org/docs/8.3/interactive/charset.html">different ways</ulink>:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Using the locale features of the operating system to provide locale-specific collation order, number formatting, translated messages, and other aspects.
+ </para>
+ <para>
+ UTF-8 is widely used on Linux distributions by default, so it can be useful in such cases.
+ </para>
- </listitem>
- <listitem>
- <para>
- Providing a number of different character sets defined in the PostgreSQL server, including multiple-byte character sets, to support storing text any language, and providing character set translation between client and server.
- </para>
- <para>
- Using UTF-8 database charset is recommended as it will allow any-to-any conversations and make this issue transparent for the JCR.
- </para>
+ </listitem>
+ <listitem>
+ <para>
+ Providing a number of different character sets defined in the PostgreSQL server, including multiple-byte character sets, to support storing text any language, and providing character set translation between client and server.
+ </para>
+ <para>
+ Using UTF-8 database charset is recommended as it will allow any-to-any conversations and make this issue transparent for the JCR.
+ </para>
- </listitem>
+ </listitem>
- </orderedlist>
- <para>
- Example of a database with UTF-8 encoding using PgSQL dialect for the Workspace Container:
- </para>
-
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_multilanguage-support/default58.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ </orderedlist>
+ <para>
+ Example of a database with UTF-8 encoding using PgSQL dialect for the Workspace Container:
+ </para>
+
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_multilanguage-support/default58.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- </section>
-
+ </section>
+
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/rest-services-on-groovy.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/rest-services-on-groovy.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/rest-services-on-groovy.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-REST_Services_on_Groovy">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-REST_Services_on_Groovy">
<title>REST Services on Groovy</title>
<para>Starting from version 1.9, JCR Service supports REST services
@@ -39,6 +39,6 @@
</init-params>
</component></programlisting>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Search_Configuration">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Search_Configuration">
<title>Search Configuration</title>
<para>
The search function in JCR can be configured to perform in specific ways. This section will discuss configuring the search function to improve search performance and results.
@@ -18,7 +18,7 @@
A code example is included below with a list of the configuration parameters shown below that.
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default61.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default61.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
The table below outlines the Configuration Parameters available, their default setting, which version of eXo JCR they were implemented in and other useful information:
</para>
@@ -669,7 +669,7 @@
</areaspec>
-<programlisting language="Java" role="Java"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default62.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="Java" role="Java"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default62.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<calloutlist>
<callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Search_Configuration-Global_Search_Index-StandardFilter">
<para>
@@ -817,7 +817,7 @@
To configure an application to use a new analyzer, add the <parameter>analyzer</parameter> parameter to each query-handler configuration in <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><VERSION></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/jcr/repository-configuration.xml</filename>:
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default69.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default69.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
The new <literal>SearchIndex</literal> will start to index contents with the specified filters when the JCR is next started.
</para>
@@ -850,7 +850,7 @@
With the configuration below only properties named <parameter>Text</parameter> are indexed for <parameter>nt:unstructured</parameter> node types. This configuration also applies to all nodes whose type extends from <parameter>nt:unstructured</parameter>.
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default71.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default71.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<note>
<title>Namespace Prefixes</title>
<para>
@@ -866,12 +866,12 @@
</formalpara>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default72.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default72.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
If you do not wish to boost the complete node, but only certain properties, you can also provide a boost value for the listed properties:
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default73.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default73.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<formalpara id="form-Reference_Guide_eXo_JCR_1.14-IndexingConfiguration-Conditional_Index_Rules">
<title>Conditional Index Rules</title>
<para>
@@ -880,7 +880,7 @@
</formalpara>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default74.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default74.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
In the above example the first rule only applies if the <parameter>nt:unstructured</parameter> node has a priority property with a value <parameter>high</parameter>. The condition syntax only supports the equals operator and a string literal.
</para>
@@ -888,12 +888,12 @@
Properties may also be referenced on the condition that are not on the current node:
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default75.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default75.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
The indexing configuration allows the type of a node in the condition to be specified. Please note however that the type match must be exact. It does not consider sub types of the specified node type.
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default76.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default76.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<formalpara id="form-Reference_Guide_eXo_JCR_1.14-IndexingConfiguration-Exclusion_from_the_Node_Scope_Index">
<title>Exclusion from the Node Scope Index</title>
<para>
@@ -908,7 +908,7 @@
Properties can be explicitly excluded from the node scope index with:
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default77.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default77.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<formalpara id="form-Reference_Guide_eXo_JCR_1.14-IndexingConfiguration-Index_Aggregates">
<title>Index Aggregates</title>
<para>
@@ -923,22 +923,22 @@
The following example creates an index aggregate on <literal>nt:file</literal> that includes the content of the jcr:content node:
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default78.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default78.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
Included nodes can also be restricted to a certain type:
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default79.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default79.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
The <emphasis role="bold">*</emphasis> wild-card can be used to match all child nodes:
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default80.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default80.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
Nodes to a certain depth below the current node can be included by adding multiple include elements. The <parameter>nt:file</parameter> node may contain a complete XML document under jcr:content for example:
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default81.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default81.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<formalpara id="form-Reference_Guide_eXo_JCR_1.14-IndexingConfiguration-Property_Level_Analyzers">
<title>Property-Level Analyzers</title>
<para>
@@ -947,7 +947,7 @@
</formalpara>
-<programlisting language="XML" role="XML"><xi:include href="../../../../../extras/Advanced_Development_JCR_search-configuration/default82.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default82.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
The configuration above sets lucene <emphasis role="bold">KeywordAnalyzer</emphasis> to index and search the property "<replaceable>mytext</replaceable>" across the entire workspace while the "<replaceable>mytext2</replaceable>" property is searched with the <emphasis role="bold">WhitespaceAnalyzer</emphasis>.
</para>
@@ -1061,4 +1061,4 @@
</itemizedlist>
</section>
-</section>
\ No newline at end of file
+</chapter>
\ No newline at end of file
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/workspace-persistence-storage.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/workspace-persistence-storage.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/configuration/workspace-persistence-storage.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Workspace_Data_Container">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container">
<title>Workspace Data Container</title>
<para>
Each Workspace of the JCR has its own persistent storage to hold that workspace's items data. The eXo JCR can be configured so that it can use one or more workspaces that are logical units of the repository content.
@@ -158,6 +158,6 @@
</programlistingco>
-</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 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/intro.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -3,7 +3,7 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent">
%BOOK_ENTITIES;
]>
-<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Introduction">
+<chapter id="chap-Reference_Guide_eXo_JCR_1.14-eXoJCR-Introduction">
<title>Introduction</title>
<warning>
<title>eXo JCR usage</title>
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 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/lock-manager-config.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -18,7 +18,7 @@
For example:
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_lock-manager-config/default47.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_JCR_lock-manager-config/default47.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<section id="sect-Reference_Guide_eXo_JCR_1.14-LockManager-CacheableLockManagerImpl">
<title>CacheableLockManagerImpl</title>
@@ -35,7 +35,7 @@
The time-out for LockRemover is set as follows (the default value is 30m):
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_lock-manager-config/default48.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_JCR_lock-manager-config/default48.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<!-- Doesn't seem necessary
<formalpara>
<title>Configuration</title>
@@ -106,7 +106,7 @@
</areaspec>
-<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_lock-manager-config/default49.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_JCR_lock-manager-config/default49.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<calloutlist>
<callout arearefs="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-jbosscache-lock-config.xml">
<para>
@@ -134,7 +134,7 @@
</areaspec>
-<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_lock-manager-config/default50.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_JCR_lock-manager-config/default50.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<calloutlist>
<callout arearefs="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-clusterName">
<para>
@@ -304,7 +304,7 @@
</areaspec>
-<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_lock-manager-config/you.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_JCR_lock-manager-config/you.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<calloutlist>
<callout arearefs="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.templates">
<para>
@@ -331,7 +331,7 @@
</areaspec>
-<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_lock-manager-config/default51.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_JCR_lock-manager-config/default51.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<calloutlist>
<callout arearefs="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-udp-mux.xml">
<para>
@@ -360,7 +360,7 @@
<filename>udp-mux.xml</filename>:
</para>
-<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_lock-manager-config/default52.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_JCR_lock-manager-config/default52.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
</section>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/acl-ext.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/acl-ext.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/acl-ext.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Access_Control_Extension">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Access_Control_Extension">
<title>Access Control Extension</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-Access_Control_Extension-Prerequisites">
<title>Prerequisites</title>
@@ -154,6 +154,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/acl.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/acl.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/acl.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Access_Control">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Access_Control">
<title>Access Control</title>
<para>
The eXo JCR component is a complete implementation of the standard JSR 170: <ulink url="http://jcp.org/en/jsr/detail?id=170">Content Repository for Java TM Technology API</ulink>, including <emphasis role="bold">Level 1, Level 2 and Additional Features</emphasis> specified in the JCR Specification.
@@ -594,6 +594,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/binary-values-processing.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/binary-values-processing.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/binary-values-processing.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -3,43 +3,43 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent">
%BOOK_ENTITIES;
]>
-<section id="sect-Reference_Guide_eXo_JCR_1.14-Binary_Values_Processing">
- <title>Binary Values Processing</title>
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Binary_Values_Processing-Configuration">
- <title>Configuration</title>
- <para>
- Binary large object (<abbrev>BLOB</abbrev>) properties can be stored in two ways in the eXo JCR; in the database with items information or in an external storage on host file system. These options can be configured at workspace in the repository configuration file (<filename>repository-configuration.xml</filename>). The database storage can not be completely disabled.
- </para>
- <para>
- The first case is optimal for most of cases which you do not use very large values and/or do not have too many BLOBs. The configuration of the BLOBs size and BLOBs quantity in a repository depend on your database features and hardware.
- </para>
- <para>
- The second case is to use an external values storage. The storage can be located on a built-in hard disk or on an attached storage. But in any cases, you should access to the storage as if it was a regular file(s). The external value storage is optional and can be enabled in a database configuration.
- </para>
- <note>
- <para>
- The eXo JCR Repository service configuration basics is discussed in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-JCR_configuration" />
- </para>
- <para>
- Database and workspace persistence storage configuration is discussed in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config" />
- </para>
- <para>
- Configuration details for <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-External_Value_Storages" />.
- </para>
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Binary_Values_Processing">
+ <title>Binary Values Processing</title>
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Binary_Values_Processing-Configuration">
+ <title>Configuration</title>
+ <para>
+ Binary large object (<abbrev>BLOB</abbrev>) properties can be stored in two ways in the eXo JCR; in the database with items information or in an external storage on host file system. These options can be configured at workspace in the repository configuration file (<filename>repository-configuration.xml</filename>). The database storage can not be completely disabled.
+ </para>
+ <para>
+ The first case is optimal for most of cases which you do not use very large values and/or do not have too many BLOBs. The configuration of the BLOBs size and BLOBs quantity in a repository depend on your database features and hardware.
+ </para>
+ <para>
+ The second case is to use an external values storage. The storage can be located on a built-in hard disk or on an attached storage. But in any cases, you should access to the storage as if it was a regular file(s). The external value storage is optional and can be enabled in a database configuration.
+ </para>
+ <note>
+ <para>
+ The eXo JCR Repository service configuration basics is discussed in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-JCR_configuration" />
+ </para>
+ <para>
+ Database and workspace persistence storage configuration is discussed in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config" />
+ </para>
+ <para>
+ Configuration details for <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-External_Value_Storages" />.
+ </para>
- </note>
+ </note>
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Binary_Values_Processing-Usage">
- <title>Usage</title>
- <para>
- In both of the cases, a developer can set or update the binary Property via <literal>Node.setProperty(String, InputStream)</literal>, <literal>Property.setValue(InputStream)</literal> as described in the spec JSR-170. Also, there is the setter with a ready Value object obtained from <literal>ValueFactory.createValue(InputStream)</literal>.
- </para>
- <para>
- An example of a specification usage:
- </para>
-
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Binary_Values_Processing-Usage">
+ <title>Usage</title>
+ <para>
+ In both of the cases, a developer can set or update the binary Property via <literal>Node.setProperty(String, InputStream)</literal>, <literal>Property.setValue(InputStream)</literal> as described in the spec JSR-170. Also, there is the setter with a ready Value object obtained from <literal>ValueFactory.createValue(InputStream)</literal>.
+ </para>
+ <para>
+ An example of a specification usage:
+ </para>
+
<programlisting language="Java" role="Java">// Set the property value with given stream content.
Property binProp = node.setProperty("BinData", myDataStream);
// Get the property value stream.
@@ -54,37 +54,37 @@
updatedBinProp.setValue(ValueFactory.createValue(newDataStream));
// Get the updated property value stream.
InputStream newStream = updatedBinProp.getStream();</programlisting>
- <para>
- However, updating the property sequentially and with partial content, would require you to edit the entire data stream outside of, then return to, the repository. In cases of large amounts of data, this process would belabor the application and its productivity will suffer. JCR stream setters will also check constraints and perform common validation each time.
- </para>
- <para>
- A feature of the eXo JCR extension can be used for binary values partial writing without frequent session level calls. The main concept is to use a value object obtained from the property as the storage of the property content while writing/reading during runtime.
- </para>
- <para>
- According to the JSR-170 specification, Value interface provides the state of property that can't be edited. The eXo JCR core provides <literal>ReadableBinaryValue</literal> and <literal>EditableBinaryValue</literal> interfaces which themselves extend JCR Value. The interfaces allow the user to partially read and change a value content.
- </para>
- <para>
- <literal>ReadableBinaryValue</literal> value can be casted from any value, i.e. String, Binary, Date etc.
- </para>
-
+ <para>
+ However, updating the property sequentially and with partial content, would require you to edit the entire data stream outside of, then return to, the repository. In cases of large amounts of data, this process would belabor the application and its productivity will suffer. JCR stream setters will also check constraints and perform common validation each time.
+ </para>
+ <para>
+ A feature of the eXo JCR extension can be used for binary values partial writing without frequent session level calls. The main concept is to use a value object obtained from the property as the storage of the property content while writing/reading during runtime.
+ </para>
+ <para>
+ According to the JSR-170 specification, Value interface provides the state of property that can't be edited. The eXo JCR core provides <literal>ReadableBinaryValue</literal> and <literal>EditableBinaryValue</literal> interfaces which themselves extend JCR Value. The interfaces allow the user to partially read and change a value content.
+ </para>
+ <para>
+ <literal>ReadableBinaryValue</literal> value can be casted from any value, i.e. String, Binary, Date etc.
+ </para>
+
<programlisting language="Java" role="Java">// get the property value of type PropertyType.STRING
ReadableBinaryValue extValue = (ReadableBinaryValue) node.getProperty("LargeText").getValue();
// read 200 bytes to a destStream from the position 1024 in the value content
OutputStream destStream = new FileOutputStream("MyTextFile.txt");
extValue.read(destStream, 200, 1024);</programlisting>
- <para>
- However <literal>EditableBinaryValue</literal> can be applied only to <literal>PropertyType.BINARY</literal> type properties. In other cases, a cast to <literal>EditableBinaryValue</literal> will fail.
- </para>
- <para>
- After the value has been edited, the <literal>EditableBinaryValue</literal> value can be applied to the property using the standard setters (<literal>Property.setValue(Value)</literal>, <literal>Property.setValues(Value)</literal>, <literal>Node.setProperty(String, Value)</literal> etc.).
- </para>
- <para>
- Only after the <literal>EditableBinaryValue</literal> has been set to the property, it can be obtained in this session by getters <literal>(Property.getValue()</literal>, <literal>Node.getProperty(String)</literal> etc.).
- </para>
- <para>
- The user can obtain an <literal>EditableBinaryValue</literal> instance and fill it with data in an interaction manner (or any other appropriated to the targets) and return (set) the value to the property after the content will be done.
- </para>
-
+ <para>
+ However <literal>EditableBinaryValue</literal> can be applied only to <literal>PropertyType.BINARY</literal> type properties. In other cases, a cast to <literal>EditableBinaryValue</literal> will fail.
+ </para>
+ <para>
+ After the value has been edited, the <literal>EditableBinaryValue</literal> value can be applied to the property using the standard setters (<literal>Property.setValue(Value)</literal>, <literal>Property.setValues(Value)</literal>, <literal>Node.setProperty(String, Value)</literal> etc.).
+ </para>
+ <para>
+ Only after the <literal>EditableBinaryValue</literal> has been set to the property, it can be obtained in this session by getters <literal>(Property.getValue()</literal>, <literal>Node.getProperty(String)</literal> etc.).
+ </para>
+ <para>
+ The user can obtain an <literal>EditableBinaryValue</literal> instance and fill it with data in an interaction manner (or any other appropriated to the targets) and return (set) the value to the property after the content will be done.
+ </para>
+
<programlisting language="Java" role="Java">// get the property value for PropertyType.BINARY Property
EditableBinaryValue extValue = (EditableBinaryValue) node.getProperty("BinData").getValue();
@@ -96,10 +96,10 @@
// save the Property to persistence
node.save();</programlisting>
- <para>
- A practical example of the iterative usage. In this example, the value is updated with data from the sequence of streams and after the update is done, the value will be applied to the property and be visible during the session.
- </para>
-
+ <para>
+ A practical example of the iterative usage. In this example, the value is updated with data from the sequence of streams and after the update is done, the value will be applied to the property and be visible during the session.
+ </para>
+
<programlisting language="Java" role="Java">// update length bytes from the stream starting from the particular
// position in the existing Value data
int dpos = 1024;
@@ -111,44 +111,44 @@
// apply the edited EditableBinaryValue to the Property
node.setProperty("BinData", extValue);</programlisting>
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Binary_Values_Processing-Value_implementations">
- <title>Value implementations</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/eXoJCR/other/binaryvalue.png" width="444" />
- </imageobject>
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Binary_Values_Processing-Value_implementations">
+ <title>Value implementations</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/eXoJCR/other/binaryvalue.png" width="444" />
+ </imageobject>
- </mediaobject>
- <para>
- <literal>ReadableBinaryValue</literal> has one method to read Value.
- </para>
- <para>
- Read length bytes is counted from the binary value to the given position into the stream.
- </para>
-
+ </mediaobject>
+ <para>
+ <literal>ReadableBinaryValue</literal> has one method to read Value.
+ </para>
+ <para>
+ Read length bytes is counted from the binary value to the given position into the stream.
+ </para>
+
<programlisting language="Java" role="Java">long read(OutputStream stream, long length, long position) throws IOException, RepositoryException ;</programlisting>
- <para>
- <literal>EditableBinaryValue</literal> has two methods to edit value.
- </para>
- <para>
- Update with length bytes from the specified stream to this value data at a position. If the position is lower than <literal>0</literal>, the IOException exception will be thrown. If the position is higher than the current Value length, the Value length will be increased at first to the size of position and length bytes will be added after the position.
- </para>
-
+ <para>
+ <literal>EditableBinaryValue</literal> has two methods to edit value.
+ </para>
+ <para>
+ Update with length bytes from the specified stream to this value data at a position. If the position is lower than <literal>0</literal>, the IOException exception will be thrown. If the position is higher than the current Value length, the Value length will be increased at first to the size of position and length bytes will be added after the position.
+ </para>
+
<programlisting language="Java" role="Java">void update(InputStream stream, long length, long position) throws IOException;</programlisting>
- <para>
- Set the length of the Value in bytes to the specified size. If the size is lower than <literal>0</literal>, the IOException exception will be thrown. This operation can be used to extend or truncate the Value size. This method is used internally in the update operation in case of extending the size to the given position.
- </para>
-
+ <para>
+ Set the length of the Value in bytes to the specified size. If the size is lower than <literal>0</literal>, the IOException exception will be thrown. This operation can be used to extend or truncate the Value size. This method is used internally in the update operation in case of extending the size to the given position.
+ </para>
+
<programlisting language="Java" role="Java">void setLength(long size) throws IOException;</programlisting>
- <para>
- An application can perform JCR binary operations more flexibly and will have less I/O and CPU usage using these methods.
- </para>
+ <para>
+ An application can perform JCR binary operations more flexibly and will have less I/O and CPU usage using these methods.
+ </para>
- </section>
-
+ </section>
+
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/jcr-resources.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/jcr-resources.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/jcr-resources.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -3,23 +3,23 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent">
%BOOK_ENTITIES;
]>
-<section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Resources">
- <title>JCR Resources:</title>
- <para>
- * Java Community Process: <ulink url="http://jcp.org/en/jsr/detail?id=170">JSR 170 </ulink> and <ulink url="http://jcp.org/en/jsr/detail?id=283">JSR 283</ulink>
- </para>
- <para>
- * Tom Wheeler, <ulink url="http://www.tomwheeler.com/java_content_repository_tomwheeler_20071007.pdf">The Java Content Repository</ulink> (2007)
- </para>
- <para>
- * Roy T. Fielding, <ulink url="http://www.day.com/content/dam/day/whitepapers/JSR_170_White_Paper.pdf">JSR 170 Overview: Standardizing the Content Repository Interface</ulink> (March 13, 2005)
- </para>
- <para>
- * David Nuescheler and Janus Boye, <ulink url="http://www.cmswatch.com/Feature/123">JSR-170 What's in it for me?</ulink> (April 20, 2005)
- </para>
- <para>
- * Benjamin Mestrallet, Tuan Nguyen, Gennady Azarenkov, Francois Moron and Brice Revenant <ulink url="http://www.theserverside.com/tt/articles/article.tss?l=eXoPlatform2">eXo Platform v2, Portal, JCR, ECM, Groupware and Business Intelligence</ulink> (January 2006)
- </para>
-</section>
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Resources">
+ <title>JCR Resources:</title>
+ <para>
+ * Java Community Process: <ulink url="http://jcp.org/en/jsr/detail?id=170">JSR 170 </ulink> and <ulink url="http://jcp.org/en/jsr/detail?id=283">JSR 283</ulink>
+ </para>
+ <para>
+ * Tom Wheeler, <ulink url="http://www.tomwheeler.com/java_content_repository_tomwheeler_20071007.pdf">The Java Content Repository</ulink> (2007)
+ </para>
+ <para>
+ * Roy T. Fielding, <ulink url="http://www.day.com/content/dam/day/whitepapers/JSR_170_White_Paper.pdf">JSR 170 Overview: Standardizing the Content Repository Interface</ulink> (March 13, 2005)
+ </para>
+ <para>
+ * David Nuescheler and Janus Boye, <ulink url="http://www.cmswatch.com/Feature/123">JSR-170 What's in it for me?</ulink> (April 20, 2005)
+ </para>
+ <para>
+ * Benjamin Mestrallet, Tuan Nguyen, Gennady Azarenkov, Francois Moron and Brice Revenant <ulink url="http://www.theserverside.com/tt/articles/article.tss?l=eXoPlatform2">eXo Platform v2, Portal, JCR, ECM, Groupware and Business Intelligence</ulink> (January 2006)
+ </para>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/link-producer.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/link-producer.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/other/link-producer.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Link_Producer_Service">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Link_Producer_Service">
<title>Link Producer Service</title>
<para>
The Link Producer Service is a simple service which generates an file that is compatible with the Microsoft link file format. It is an extension of the REST Framework library and is included into the WebDav service. On dispatching a <literal>GET</literal> request the service generates the content of an <filename>.lnk</filename> file, which points to a JCR resource via WebDav.
@@ -92,6 +92,6 @@
<para>
...the file "somefile.extention" will open directly.
</para>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/protocols/ftp.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/protocols/ftp.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/protocols/ftp.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -3,62 +3,62 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent">
%BOOK_ENTITIES;
]>
-<section id="sect-Reference_Guide_eXo_JCR_1.14-FTP">
- <title>FTP</title>
- <section id="sect-Reference_Guide_eXo_JCR_1.14-FTP-Introduction">
- <title>Introduction</title>
- <para>
- The JCR-FTP Server operates as an FTP server with access to a content stored in JCR repositories in the form of <emphasis role="bold">nt:file/nt:folder</emphasis> nodes or their successors. The client of an executed Server can be any FTP client. The FTP server is supported by a standard configuration which can be changed as required.
- </para>
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-FTP">
+ <title>FTP</title>
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-FTP-Introduction">
+ <title>Introduction</title>
+ <para>
+ The JCR-FTP Server operates as an FTP server with access to a content stored in JCR repositories in the form of <emphasis role="bold">nt:file/nt:folder</emphasis> nodes or their successors. The client of an executed Server can be any FTP client. The FTP server is supported by a standard configuration which can be changed as required.
+ </para>
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-FTP-Configuration_Parameters">
- <title>Configuration Parameters</title>
- <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Configuration_Parameters-Parameters">
- <title>Parameters</title>
- <varlistentry>
- <term>command-port:</term>
- <listitem>
-
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-FTP-Configuration_Parameters">
+ <title>Configuration Parameters</title>
+ <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Configuration_Parameters-Parameters">
+ <title>Parameters</title>
+ <varlistentry>
+ <term>command-port:</term>
+ <listitem>
+
<programlisting language="XML" role="XML"><value-param>
<name>command-port</name>
<value>21</value>
</value-param></programlisting>
- <para>
- The value of the command channel port. The value '<literal>21</literal>' is default.
- </para>
- <para>
- If you have already other FTP server installed in your system, this parameter needs to be changed (to <literal>2121</literal>, for example) to avoid conflicts or if the port is protected.
- </para>
+ <para>
+ The value of the command channel port. The value '<literal>21</literal>' is default.
+ </para>
+ <para>
+ If you have already other FTP server installed in your system, this parameter needs to be changed (to <literal>2121</literal>, for example) to avoid conflicts or if the port is protected.
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
- <varlistentry>
- <term>data-min-port & data-max-port</term>
- <listitem>
-
+ </varlistentry>
+ <varlistentry>
+ <term>data-min-port & data-max-port</term>
+ <listitem>
+
<programlisting language="XML" role="XML"><value-param>
<name>data-min-port</name>
<value>52000</value>
</value-param></programlisting>
-
+
<programlisting language="XML" role="XML"><value-param>
<name>data-max-port</name>
<value>53000</value>
</value-param></programlisting>
- <para>
- These two parameters indicate the minimum and maximum values of the range of ports, used by the server. The usage of the additional data channel is required by the FTP protocol, which is used to transfer the contents of files and the listing of catalogues. This range of ports should be free from listening by other server-programs.
- </para>
+ <para>
+ These two parameters indicate the minimum and maximum values of the range of ports, used by the server. The usage of the additional data channel is required by the FTP protocol, which is used to transfer the contents of files and the listing of catalogues. This range of ports should be free from listening by other server-programs.
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
- <varlistentry>
- <term>system</term>
- <listitem>
-
+ </varlistentry>
+ <varlistentry>
+ <term>system</term>
+ <listitem>
+
<programlisting language="XML" role="XML"><value-param>
<name>system</name>
@@ -66,17 +66,17 @@
or
<value>UNIX Type: L8</value>
</value-param></programlisting>
- <para>
- Types of formats of listing of catalogues which are supported.
- </para>
+ <para>
+ Types of formats of listing of catalogues which are supported.
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
- <varlistentry>
- <term>client-side-encoding</term>
- <listitem>
-
+ </varlistentry>
+ <varlistentry>
+ <term>client-side-encoding</term>
+ <listitem>
+
<programlisting language="XML" role="XML"><value-param>
<name>client-side-encoding</name>
@@ -85,124 +85,124 @@
<value>KOI8-R</value>
</value-param></programlisting>
- <para>
- This parameter specifies the coding which is used for dialogue with the client.
- </para>
+ <para>
+ This parameter specifies the coding which is used for dialogue with the client.
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
- <varlistentry>
- <term>def-folder-node-type</term>
- <listitem>
-
+ </varlistentry>
+ <varlistentry>
+ <term>def-folder-node-type</term>
+ <listitem>
+
<programlisting language="XML" role="XML"><value-param>
<name>def-folder-node-type</name>
<value>nt:folder</value>
</value-param></programlisting>
- <para>
- This parameter specifies the type of a node, when an FTP-folder is created.
- </para>
+ <para>
+ This parameter specifies the type of a node, when an FTP-folder is created.
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
- <varlistentry>
- <term>def-file-node-type</term>
- <listitem>
-
+ </varlistentry>
+ <varlistentry>
+ <term>def-file-node-type</term>
+ <listitem>
+
<programlisting language="XML" role="XML"><value-param>
<name>def-file-node-type</name>
<value>nt:file</value>
</value-param></programlisting>
- <para>
- This parameter specifies the type of a node, when an FTP-file is created.
- </para>
+ <para>
+ This parameter specifies the type of a node, when an FTP-file is created.
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
- <varlistentry>
- <term>def-file-mime-type</term>
- <listitem>
-
+ </varlistentry>
+ <varlistentry>
+ <term>def-file-mime-type</term>
+ <listitem>
+
<programlisting language="XML" role="XML"><value-param>
<name>def-file-mime-type</name>
<value>application/zip</value>
</value-param></programlisting>
- <para>
- The mime type of a created file is chosen by using its file extention. In case, a server cannot find the corresponding mime type, this value is used.
- </para>
+ <para>
+ The mime type of a created file is chosen by using its file extention. In case, a server cannot find the corresponding mime type, this value is used.
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
- <varlistentry>
- <term>cache-folder-name</term>
- <listitem>
-
+ </varlistentry>
+ <varlistentry>
+ <term>cache-folder-name</term>
+ <listitem>
+
<programlisting language="XML" role="XML"><value-param>
<name>cache-folder-name</name>
<value>../temp/ftp_cache</value>
</value-param></programlisting>
- <para>
- The Path of the cache folder.
- </para>
+ <para>
+ The Path of the cache folder.
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
- <varlistentry>
- <term>upload-speed-limit</term>
- <listitem>
-
+ </varlistentry>
+ <varlistentry>
+ <term>upload-speed-limit</term>
+ <listitem>
+
<programlisting language="XML" role="XML"><value-param>
<name>upload-speed-limit</name>
<value>20480</value>
</value-param></programlisting>
- <para>
- Restriction of the upload speed. It is measured in bytes.
- </para>
+ <para>
+ Restriction of the upload speed. It is measured in bytes.
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
- <varlistentry>
- <term>download-speed-limit</term>
- <listitem>
-
+ </varlistentry>
+ <varlistentry>
+ <term>download-speed-limit</term>
+ <listitem>
+
<programlisting language="XML" role="XML"><value-param>
<name>download-speed-limit</name>
<value>20480</value>
</value-param></programlisting>
- <para>
- Restriction of the download speed. It is measured in bytes.
- </para>
+ <para>
+ Restriction of the download speed. It is measured in bytes.
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
- <varlistentry>
- <term>timeout</term>
- <listitem>
-
+ </varlistentry>
+ <varlistentry>
+ <term>timeout</term>
+ <listitem>
+
<programlisting language="XML" role="XML"><value-param>
<name>timeout</name>
<value>60</value>
</value-param></programlisting>
- <para>
- Defines the value of a timeout.
- </para>
+ <para>
+ Defines the value of a timeout.
+ </para>
- </listitem>
+ </listitem>
- </varlistentry>
+ </varlistentry>
- </variablelist>
+ </variablelist>
- </section>
-
+ </section>
+
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/protocols/webdav.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/protocols/webdav.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/protocols/webdav.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-WebDAV">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-WebDAV">
<!-- This document was created with Syntext Serna Free. --> <title>WebDAV</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-WebDAV-Introduction">
<title>Introduction</title>
@@ -482,6 +482,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/fulltext-search-and-settings.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/fulltext-search-and-settings.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/fulltext-search-and-settings.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Fulltext_Search_And_Affecting_Settings">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings">
<title>Fulltext Search And Affecting Settings</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings-Property_content_indexing">
<title>Property content indexing</title>
@@ -317,6 +317,6 @@
</section>
-</section>
+</chapter>
Deleted: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.bk
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.bk 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.bk 2011-11-18 04:01:09 UTC (rev 8093)
@@ -1,390 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<section id="JCR.QueryUsecases">
-
- <title>JCR Query Usecases</title>
-
- <section>
- <title>Intro</title>
-
- <para>JCR supports two query languages - JCR and XPath. A query, whether
- XPath or SQL, specifies a subset of nodes within a workspace, called the
- result set. The result set constitutes all the nodes in the workspace that
- meet the constraints stated in the query.</para>
- </section>
-
- <section>
- <title>Query Lifecycle</title>
-
- <section>
- <title>Query Creation and Execution</title>
-
- <para><emphasis role="bold">SQL</emphasis></para>
-
- <programlisting role="Java" language="Java">// get QueryManager
-QueryManager queryManager = workspace.getQueryManager();
-// make SQL query
-Query query = queryManager.createQuery("SELECT * FROM nt:base ", Query.SQL);
-// execute query
-QueryResult result = query.execute();</programlisting>
-
- <para><emphasis role="bold">XPath</emphasis></para>
-
- <programlisting role="Java" language="Java">// get QueryManager
-QueryManager queryManager = workspace.getQueryManager();
-// make XPath query
-Query query = queryManager.createQuery("//element(*,nt:base)", Query.XPATH);
-// execute query
-QueryResult result = query.execute();</programlisting>
- </section>
-
- <section>
- <title>Query Result Processing</title>
-
- <programlisting role="Java" language="Java">// fetch query result
-QueryResult result = query.execute();</programlisting>
-
- <para>Now we can get result in an iterator of nodes:</para>
-
- <programlisting role="Java" language="Java">NodeIterator it = result.getNodes();</programlisting>
-
- <para>or we get the result in a table:</para>
-
- <programlisting role="Java" language="Java">// get column names
-String[] columnNames = result.getColumnNames();
-// get column rows
-RowIterator rowIterator = result.getRows();
-while(rowIterator.hasNext()){
- // get next row
- Row row = rowIterator.nextRow();
- // get all values of row
- Value[] values = row.getValues();
-}</programlisting>
- </section>
-
- <section>
- <title>Scoring</title>
-
- <para>The result returns a score for each row in the result set. The
- score contains a value that indicates a rating of how well the result
- node matches the query. A high value means a better matching than a low
- value. This score can be used for ordering the result.</para>
-
- <para>eXo JCR Scoring is a mapping of Lucene scoring. For a more
- in-depth understanding, please study <ulink
- url="http://lucene.apache.org/java/2_4_1/scoring.html">Lucene
- documentation</ulink>.</para>
-
- <para>jcr:score counted in next way - (lucene score)*1000f.</para>
-
- <para>Score may be increased for specified nodes, see <xref
- linkend="JCR.IndexBoostRule"/></para>
-
- <para>Also, see an example <xref linkend="JCR.OrderByScore"/></para>
- </section>
- </section>
-
- <section>
- <title>Query result settings</title>
-
- <itemizedlist>
- <listitem>
- <para><xref linkend="JCR.SetOffsetandSetLimit"/></para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title>Type Constraints</title>
-
- <itemizedlist>
- <listitem>
- <para><xref linkend="JCR.FindAllNodes"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.FindNodesByPrimaryType"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.FindNodesByMixinType"/></para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title>Property Constraints</title>
-
- <itemizedlist>
- <listitem>
- <para><xref linkend="JCR.PropertyComparison"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.LIKEConstraint"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.EscapinginLIKEStatements"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.NOTConstraint"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.ANDConstraint"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.ORConstraint"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.PropertyExistenceConstraint"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.FindNodesCaseInsensitive"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.DatePropertyComparison"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.NodeNameConstraint"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.MultivaluePropertyComparison"/></para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title>Path Constraint</title>
-
- <itemizedlist>
- <listitem>
- <para><xref linkend="JCR.ExactPathConstraint"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.ChildNodeConstraint"/></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.FindAllDescendantNodes"/></para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title>Ordering specifying</title>
-
- <itemizedlist>
- <listitem>
- <para><xref linkend="JCR.OrderByProperty">Order by
- Property</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.OrderByDescendant">Order by Descendant Node
- Property</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.OrderByScore">Order by Score</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.OrderByPathOrName">Order by Path or
- Name</link></para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title><xref linkend="JCR.FulltextSearchAndSettings">Fulltext
- Search</link></title>
-
- <itemizedlist>
- <listitem>
- <para><xref linkend="JCR.FulltextSearchByProperty">Fulltext Search by
- Property</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.FulltextSearchByAllProperties">Fulltext
- Search by All Properties</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.AggregationRule">Find nt:file document by
- content of child jcr:content node</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.IgnoreAccentSymbols">How to set new Analyzer.
- Accent symblos ignoring</link></para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title>Indexing rules and additional features</title>
-
- <itemizedlist>
- <listitem>
- <para><xref linkend="JCR.AggregationRule">Aggregation
- rule</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.HiglightResultofFulltextSearch">Search Result
- Highlighting</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.IndexBoostRule">Index Boost
- Value</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.NodeScopeIndex">Exclusion from the Node Scope
- Index</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.RegexpIndexingRule">Regular expressions as
- property name in indexing rule</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.SynonimProvider">Synonim
- Provider</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.SpellChecker">Spell Checking</link></para>
- </listitem>
-
- <listitem>
- <para><xref linkend="JCR.FindSimilarNodes">Find Similar
- Nodes</link></para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title>Query Examples</title>
-
- <xi:include href="offset-and-limit.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="find-all-nodes.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="find-nodes-by-primary-type.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="find-nodes-by-mixin-type.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="property-comparison.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="like-constraint.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="escaping-like-statements.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="not-constraint.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="and-constraint.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="or-constraint.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="property-existance-constraint.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="find-nodes-case-insensitive.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="date-property-comparison.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="node-name-constraint.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="multivalue-property-comparison.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="exact-path-constraint.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="child-node-constraint.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="find-all-descendant-nodes.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="order-by-property.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="order-by-descendant.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="order-by-score.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="order-by-path-or-name.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="fulltext-search-by-property.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="fulltext-search-by-all-properties.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="ignore-accent-symbols.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="aggregation-rule.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="index-boost-value.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="node-scope-index.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="regexp-indexing-rule.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="higlight.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="synonim-provider.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="spell-checker.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- <xi:include href="find-similar-nodes.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
- </section>
-
- <section>
- <title>Tips and tricks</title>
-
- <xi:include href="tip-nodename-with-number.xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- </section>
-</section>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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_Query_Usecases">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases">
<title>JCR Query Usecases</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Intro">
<title>Introduction</title>
@@ -368,6 +368,6 @@
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/searching-repository-content.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/searching-repository-content.xml 2011-11-18 03:58:04 UTC (rev 8092)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/searching-repository-content.xml 2011-11-18 04:01:09 UTC (rev 8093)
@@ -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-Searching_Repository_Content">
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content">
<title>Searching Repository Content</title>
<section id="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content-Introduction">
<title>Introduction</title>
@@ -418,6 +418,6 @@
</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 03:58:04 UTC (rev 8092)
+++ 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 04:01:09 UTC (rev 8093)
@@ -3,7 +3,7 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent">
%BOOK_ENTITIES;
]>
-<chapter id="sect-Reference_Guide_eXo_JCR_1.14-How_to_use_AS_Managed_DataSource_under_JBoss_AS">
+<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>
@@ -106,6 +106,6 @@
</section>
-</chapter>
+</section>
12 years, 6 months
- 1
- 0
gatein SVN: r8092 - in epp/docs/branches/5.2/Reference_Guide: en-US and 2 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-11-17 22:58:04 -0500 (Thu, 17 Nov 2011)
New Revision: 8092
Modified:
epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Global_Portlet.xml
epp/docs/branches/5.2/Reference_Guide/publican.cfg
Log:
Port gtn r8080-8082, fix Global Portlet wrt theute feedback, increment
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-11-18 02:57:59 UTC (rev 8091)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-11-18 03:58:04 UTC (rev 8092)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
<edition>5.2.0</edition>
- <pubsnumber>7</pubsnumber>
+ <pubsnumber>8</pubsnumber>
<abstract>
<para>
This Reference Guide is a high-level usage document. It deals with more advanced topics than the Installation and User Guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of the JBoss Enterprise Portal Platform product. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms.
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-11-18 02:57:59 UTC (rev 8091)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-11-18 03:58:04 UTC (rev 8092)
@@ -8,6 +8,20 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>5.2.0-8</revnumber>
+ <date>Tue Nov 15 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Staged for Beta release.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>5.2.0-7</revnumber>
<date>Wed Nov 9 2011</date>
<author>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-18 02:57:59 UTC (rev 8091)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-18 03:58:04 UTC (rev 8092)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<section id="sect-Reference_Guide-SSO_Single_Sign_On">
- <title><remark>SSO - Single Sign On</remark></title>
+ <title>SSO - Single Sign On</title>
<section id="sect-Reference_Guide-SSO_Single_Sign_On-Overview">
<title>Overview</title>
<para>
@@ -83,7 +83,26 @@
This authentication can also be used in any other web applications which may require authentication, <emphasis role="bold">provided that these applications use same roles as the main portal instance</emphasis>. Attempting to use an SSO authentication in an application that uses different roles may create authorization errors (<emphasis role="bold">403</emphasis> errors, for example).
</para>
+ <note>
+ <title>Reauthentication</title>
+
<para>
+ This behavior is coming from the fact that same JAAS principal is added by SSO valve to all HTTP requests, even to other web applications.
+ </para>
+
+ <para>
+ So the same roles are required because of it. There is an alternative that allows you to configure the SSO valve with the <parameter>requireReauthentication=true</parameter> parameter, which will force the SSO valve to perform reauthentication with saved credentials in each HTTP request against security domain of particular web application where the request is coming.
+ </para>
+
+ <para>
+ This will ensure that a new principal for that web application will be created with updated roles for that web application.
+ </para>
+
+ <para>
+ In other words; when <parameter>requireReauthentication</parameter> is <emphasis role="bold">false</emphasis> (the default state), you need to have the same roles among web applications. When <parameter>requireReauthentication</parameter> is <emphasis role="bold">true</emphasis> you need to have same username and passwords.
+ </para>
+ </note>
+ <para>
More info about the JBoss SSO valve can be found at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Web_Platform/5/html/Ad..."></ulink>.
</para>
<para>
@@ -100,10 +119,10 @@
<para>
For a <emphasis>non-clustered</emphasis> implementation, uncomment:
</para>
+<programlisting language="XML" role="XML"><Valve className="org.apache.catalina.authenticator.SingleSignOn" />
+ </programlisting>
+ </listitem>
-<programlisting language="XML" role="XML"><![CDATA[<Valve className="org.apache.catalina.authenticator.SingleSignOn" />
-]]></programlisting>
- </listitem>
<listitem>
<para>
For a <emphasis>clustered</emphasis> implementation, uncomment:
@@ -116,160 +135,115 @@
</step>
<step>
<para>
- To integrate with the JBoss SSO valve, follow <emphasis role="bold">one</emphasis> of the procedures below to make the necessary configuration changes in the Java Authentication and Authorization Service (<emphasis role="bold">JAAS</emphasis>):
+ For implementation of the SSO valve among the different nodes of cluster, all the nodes must share the same domain (<emphasis>node1.yourdomain.com</emphasis> and <emphasis>node2.yourdomain.com</emphasis>, for example).
</para>
- <itemizedlist>
- <listitem>
- <procedure>
- <title>Call the JAAS authentication directly</title>
- <step>
<para>
- Open the <filename>/<replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/login/jsp/login.jsp</filename> file.
+ This domain needs to be configured in the SSO valve parameter <parameter>cookieDomain</parameter>. This is required because the SSO valve adds the cookie <emphasis role="bold">JSESSIONIDSSO</emphasis>, which is, by default bound only to the host where the request is originating.
</para>
- </step>
- <step>
+
<para>
- Change the line that reads:
+ When the <parameter>cookieDomain</parameter> parameter is used, the cookie is bound to the domain (like <emphasis>yourdomain.com</emphasis>), which will ensure that it is shared among both hosts <emphasis>node1.yourdomain.com</emphasis> and <emphasis>node2.yourdomain.com</emphasis>.
</para>
-<programlisting language="XML" role="XML"><![CDATA[<form name="loginForm" action="<%= contextPath + "/login"%>" method="post" style="margin: 0px;">
-]]></programlisting>
<para>
- to read:
+ So in this case, the valve configuration would be:
</para>
-<programlisting language="XML" role="XML"><![CDATA[<form name="loginForm" action="<%= contextPath + "/private/j_security_check"%>" method="post" style="margin: 0px;">
-]]></programlisting>
+<programlisting language="XML" role="XML"><Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn"
+cookieDomain="yourdomain.com" />
+</programlisting>
</step>
<step>
<para>
- Change the line that reads:
+ Another important thing is that both cluster nodes needs to be on same cluster (using same parameter <emphasis role="bold">-g</emphasis> and same parameter <emphasis role="bold">-u</emphasis> and also using parameter <emphasis role="bold">-Dexo.profiles=cluster</emphasis>).
</para>
-<programlisting language="XML" role="XML"><![CDATA[<td><input class="UserName" name="username" value="<%=username%>"/></td>
-]]></programlisting>
- <para>
- to read:
- </para>
-<programlisting language="XML" role="XML"><![CDATA[<td><input class="UserName" name="j_username" value="<%=username%>"/></td>
-]]></programlisting>
- </step>
- <step>
- <para>
- Change the line that reads:
- </para>
-<programlisting language="XML" role="XML"><![CDATA[<td><input class="Password" type="password" name="password" value=""/></td>
-]]></programlisting>
+
<para>
- to read:
+ They must also share the same NFS directory and the same database and apply all the configuration needed for JBoss Enterprise Portal Platform cluster.
</para>
-<programlisting language="XML" role="XML"><![CDATA[<td><input class="Password" type="password" name="j_password" value=""/></td>
-]]></programlisting>
</step>
</procedure>
- </listitem>
- <listitem>
- <procedure id="proc-Reference_Guide-SSO_Integration-Switch_to_BASIC_authentication">
- <title>Switch to <emphasis role="bold">BASIC</emphasis> authentication</title>
- <step>
- <para>
- Change the <parameter>auth-method</parameter> element in <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/web.xml</filename> from <parameter>FORM</parameter> to <parameter>BASIC</parameter>:
- </para>
-<programlisting language="XML" role="XML"><![CDATA[<login-config>
-<auth-method>BASIC</auth-method>
-<realm-name>gatein-domain</realm-name>
-<form-login-config>
- <form-login-page>/initiatelogin</form-login-page>
- <form-error-page>/errorlogin</form-error-page>
-</form-login-config>
-]]></programlisting>
- </step>
- </procedure>
- </listitem>
- </itemizedlist>
- </step>
- </procedure>
- <formalpara>
- <title>Testing the SSO Valve</title>
- <para>
- Once the JBoss SSO Valve has been enabled, it can be tested with the following steps:
+ <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Enabling_SSO_in_a_physical_cluster">
+ <title>Testing SSO in a physical cluster</title> <para>
+ In this example, we will try to simulate testing on more physical machines by simply using virtual hosts on single machine.
</para>
</formalpara>
<procedure id="proc-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Testing_the_SSO_Valve">
<title>Testing the SSO Valve</title>
<step>
<para>
- Copy the <replaceable><PROFILE></replaceable> you enabled the valve in (<literal>all</literal>, for example) into two new profiles called <literal>node1</literal> and <literal>node2</literal>.
+ If you are using a Linux system, you can configure file <emphasis role="bold">/etc/hosts</emphasis> to contain these lines:
</para>
+<programlisting>
+127.0.1.1 machine1.yourdomain.com
+127.0.1.2 machine2.yourdomain.com
+</programlisting>
</step>
<step>
<para>
- Run an instance of JBoss Enterprise Portal Platform using the <literal>node1</literal> profile on a local machine:
+ Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/all/deploy/jbossweb.sar/server.xml</filename> file.
</para>
-<programlisting>./run.sh -c node1 -Djboss.service.binding.set=ports-default -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=0 &
-</programlisting>
+
</step>
<step>
<para>
- Start another instance using the <literal>node2</literal> profile:
+ Uncomment the line:
</para>
-<programlisting>./run.sh -c node2 -Djboss.service.binding.set=ports-01 -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=1 &
+<programlisting language="XML" role="XML"><!--
+<Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" />
+-->
</programlisting>
</step>
<step>
<para>
- Navigate to <ulink type="http" url="http://localhost:8080/portal/private/classic"></ulink> and authenticate with the pre-configured user account "<systemitem>root</systemitem>" (password "<systemitem>gtn</systemitem>").
+ And edit it to match the following:
+ </para>
+<programlisting language="XML" role="XML"><Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn"
+cookieDomain="yourdomain.com" />
+</programlisting>
+ <para>
+ This will ensure the <literal>JSESSIONIDSSO</literal> cookie is used in the correct domain, allowing the SSO authentication to occur.
</para>
</step>
<step>
<para>
- Navigate to <ulink type="http" url="http://localhost:8180/portal/private/classic"></ulink>. You should be automatically authenticated as user <systemitem>root</systemitem> on this node as well.
+ Copy server configuration <emphasis role="bold">all</emphasis> and create another two configurations <emphasis role="bold">node1</emphasis> and <emphasis role="bold">node2</emphasis> from it.
</para>
</step>
- </procedure>
- <formalpara id="form-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Enabling_SSO_in_a_physical_cluster">
- <title>Enabling SSO in a physical cluster</title>
- <para>
- If you require SSO to work across a physical cluster of separate machines you will need to use the <parameter>cookieDomain</parameter> attribute of the SSO valve.
- </para>
- </formalpara>
- <procedure>
+
<step>
<para>
- Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/jbossweb.sar/server.xml</filename> file.
+ Start both cluster nodes with commands:
</para>
+<programlisting>
+./run.sh -c node1 -b machine1.yourdomain.com -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=0 &
+./run.sh -c node2 -b machine2.yourdomain.com -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=1 &
+</programlisting>
</step>
<step>
<para>
- Uncomment the line:
+ Go to <ulink type="http" url="http://machine1.yourdomain.com:8080/portal">http://machine1.yourdomain.com:8080/portal</ulink> and login as a user.
</para>
-<programlisting language="XML" role="XML"><![CDATA[<!--
-<Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" />
--->
-]]></programlisting>
+
</step>
<step>
<para>
- And edit it to match the following:
+ Access a private URL on the second host, such as <ulink type="http" url="http://machine2.yourdomain.com:8080/portal/dologin">http://machine2.yourdomain.com:8080/portal/dologin</ulink>, for example.
</para>
-<programlisting language="XML" role="XML"><![CDATA[<Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" cookieDomain="yourdomain.com" />
-]]></programlisting>
+
<para>
- (Where <literal>yourdomain.com</literal> is the domain used in your cluster. For example; <ulink type="http" url="http://machine1.yourdomain.com:8080/portal/private/classic"></ulink> and <ulink type="http" url="http://machine2.yourdomain.com:8080/portal/private/classic"></ulink>)
+ Now you should be logged directly into <literal>machine2</literal> thanks to SSO valve.
</para>
</step>
<step>
<para>
- Repeat the process in the other nodes in the cluster.
+ Logout from SSO initiating machine1.yourdomain.com should also logged you out from other cluster nodes. So you should be logout directly from machine2 as well.
</para>
</step>
</procedure>
- <para>
- This will ensure the <literal>JSESSIONIDSSO</literal> cookie is used in the correct domain, allowing the SSO authentication to occur.
- </para>
<formalpara id="form-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Enabling_SSO_with_Other_Web_Applications">
- <title>Enabling SSO with Other Web Applications</title>
- <para>
- As mentioned earlier, in order to use SSO authentication between JBoss Enterprise Portal Platform instances and other web applications, the roles defined in the web application must match those used in the portal instance.
+ <title>Enabling SSO with Other Web Applications</title> <para>
+ As mentioned earlier, in order to use SSO authentication between JBoss Enterprise Portal Platform instances and other web applications, the roles defined in the web application must match those used in the portal instance (unless you have the <parameter>requireReauthentication</parameter> parameter set to <literal>true</literal>).
</para>
</formalpara>
<para>
@@ -279,7 +253,7 @@
<title></title>
<step>
<para>
- Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/jmx-console.war/WEB-INF/web.xml</filename> file and edit it as follows:
+ Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/node1/deploy/jmx-console.war/WEB-INF/web.xml</filename> file and edit it as follows:
</para>
<substeps>
<step>
@@ -315,7 +289,7 @@
<para>
Start a portal instance on one node:
</para>
-<programlisting>./run.sh -c node1 -Djboss.service.binding.set=ports-default -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=0 &
+<programlisting>./run.sh -c node1 -b machine1.yourdomain.com -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=0 &
</programlisting>
</step>
<step>
@@ -332,14 +306,14 @@
<formalpara>
<title>Using SSO to Authenticate From the Public Page</title>
<para>
- The previous configuration changes in this section are useful if a user is using a private URL (<ulink type="http" url="http://localhost:8080/portal/private/classic"></ulink>, for example) to log in to the portal instance.
+ The previous configuration changes in this section are useful if a user is using a secured URL (<ulink type="http" url="http://localhost:8080/portal/private/classic"></ulink>, for example) to log in to the portal instance.
</para>
</formalpara>
<para>
Further changes are needed however, if SSO authentication is required to work with the <guilabel>Sign In</guilabel> button on the front page of the portal (<ulink type="http" url="http://localhost:8080/portal/public/classic"></ulink>).
</para>
<para>
- To enable this functionality, the <guilabel>Sign In</guilabel> link must redirect to the <filename>login.jsp</filename> file edited earlier to call the JAAS authentication directly.
+ To enable this functionality, the <guilabel>Sign In</guilabel> link must redirect to some secured URL, which will ensure that JAAS authentication will be enforced directly without showing login dialog.
</para>
<procedure>
<title>Redirect to Use SSO Valve Authentication</title>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Global_Portlet.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Global_Portlet.xml 2011-11-18 02:57:59 UTC (rev 8091)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Global_Portlet.xml 2011-11-18 03:58:04 UTC (rev 8092)
@@ -3,8 +3,8 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "../../Reference_Guide.ent">
%BOOK_ENTITIES;
]>
-<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Shared_portlet.xml">
- <title><remark>Shared <filename>portlet.xml</filename></remark></title>
+<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Shared_portlet.xml">
+ <title>Shared <filename>portlet.xml</filename></title>
<para>
The Java Portlet Specification introduces <literal>PortletFilter</literal> as a standard approach to extend the behaviors of portlet objects. For example, a filter can transform the content of portlet requests and portlet responses.
</para>
@@ -13,19 +13,19 @@
</para>
<procedure>
<step>
- <para>
- Implement a <literal>PortletFilter</literal> object.
- </para>
+ <para>
+ Implement a <literal>PortletFilter</literal> object.
+ </para>
</step>
<step>
- <para>
- Define the filter in portlet application deployment descriptor.
- </para>
+ <para>
+ Define the filter in portlet application deployment descriptor.
+ </para>
</step>
<step>
- <para>
- Define the filter mapping in portlet definitions.
- </para>
+ <para>
+ Define the filter mapping in portlet definitions.
+ </para>
</step>
</procedure>
<para>
@@ -35,48 +35,48 @@
<para>
Global portlet metadata is declared in the <filename>portlet.xml</filename> file and conforms with the Portlet 2.0 XSD.
</para>
-<programlisting language="XML" role="XML"><portlet-app version="1.0" xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd">
-</portlet-app>
+<programlisting language="XML" role="XML"><portlet-app version="1.0" xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd">
+</portlet-app>
</programlisting>
<para>
- The path to the global <filename>portlet.xml</filename> is the value of <literal>gatein.portlet.config</literal> in the <filename>configuration.properties.xml</filename> file. By default The file path is <filename>/<replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/conf/gatein/portlet.xml</filename>
+ The path to the global <filename>portlet.xml</filename> is the value of <literal>gatein.portlet.config</literal> in the <filename>configuration.properties.xml</filename> file. By default The file path is <filename>/<replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/conf/gatein/portlet.xml</filename>
</para>
<para>
<emphasis role="bold">For JBoss</emphasis>: The file path is <filename><replaceable><JBOSS_HOME></replaceable>/server/default/conf/gatein/portlet.xml</filename>.
</para>
- <section id="sect-Reference_Guide-Global_Metadata-Global_Metadata_Elements">
+ <section id="sect-Reference_Guide-Global_Metadata-Global_Metadata_Elements">
<title>Global Metadata Elements</title>
<para>
The global <filename>portlet.xml</filename> file conforms, with some restrictions, to the portlet deployment descriptor schema defined in the Portlet Specification. In this file, the following elements are supported:
</para>
<orderedlist>
<listitem>
- <para>
- <xref linkend="form-Reference_Guide_eXo_JCR_1.14-Global_Metadata_Elements-Portlet_Filter"/>
- </para>
+ <para>
+ <xref linkend="form-Reference_Guide_eXo_JCR_1.14-Global_Metadata_Elements-Portlet_Filter"/>
+ </para>
</listitem>
<listitem>
- <para>
- Portlet Mode
- </para>
+ <para>
+ Portlet Mode
+ </para>
</listitem>
<listitem>
- <para>
- Window State
- </para>
+ <para>
+ Window State
+ </para>
</listitem>
</orderedlist>
- <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Global_Metadata_Elements-Portlet_Filter">
+ <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Global_Metadata_Elements-Portlet_Filter">
<title>Portlet Filter</title>
<para>
Portlet filter mappings declared in the global <filename>portlet.xml</filename> file are applied across portlet applications.
</para>
- </formalpara>
+ </formalpara>
<para>
With the XML configuration below, the filter <literal>ApplicationMonitoringFilter</literal> involves in request handling on any deployed portlet.
</para>
@@ -115,7 +115,7 @@
</listitem>
</orderedlist>
<para>
- The Application Monitoring Filter records statistic information about deployed portlets. The filter alternates the actual monitoring mechanism in WebUI Framework.
+ The Application Monitoring Filter records statistic information about deployed portlets. The filter alternates the actual monitoring mechanism in WebUI Framework.
</para>
</section>
</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide/publican.cfg
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/publican.cfg 2011-11-18 02:57:59 UTC (rev 8091)
+++ epp/docs/branches/5.2/Reference_Guide/publican.cfg 2011-11-18 03:58:04 UTC (rev 8092)
@@ -5,7 +5,7 @@
type: Book
brand: JBoss
debug:1
-show_remarks: 1
+#show_remarks: 1
cvs_branch: DOCS-RHEL-6
cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist
cvs_pkg: JBoss_Enterprise_Portal_Platform-Reference_Guide-5.2-web-__LANG__
\ No newline at end of file
12 years, 6 months
- 1
- 0
gatein SVN: r8091 - in epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules: Advanced and 2 other directories.
by do-not-reply＠jboss.org
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"> <repository-service default-repository="repository">
<repositories>
<repository name="repository" system-workspace="production" default-workspace="production">
@@ -96,21 +96,21 @@
</container>
</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"> <component>
<key>org.exoplatform.services.transaction.TransactionService</key>
<type>org.exoplatform.services.transaction.jbosscache.JBossTransactionsService</type>
@@ -32,13 +32,13 @@
</value-param>
</init-params>
</component></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><connection-factories>
<tx-connection-factory>
<jndi-name>jcr/repository</jndi-name>
@@ -118,9 +118,9 @@
</tx-connection-factory>
</connection-factories></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"> <component>
<key>org.jboss.cache.transaction.TransactionManagerLookup</key>
<type>org.jboss.cache.transaction.GenericTransactionManagerLookup</type>
</component></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 & 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 & jdbcidm_sample-portal).
+ </para>
+ <para>
+ Example:
+ </para>
+
<programlisting language="XML" role="XML"><?xml version="1.0" encoding="UTF-8"?>
<datasources>
<no-tx-datasource>
@@ -62,50 +62,50 @@
<password></password>
</no-tx-datasource>
</datasources></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/html/Conn...">Configuring 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/html/Conn...">Configuring 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"><!-- Commented because, Datasources are declared and bound by AS, not in eXo -->
<!--
<external-component-plugins>
[...]
</external-component-plugins>
--></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>
+
12 years, 6 months
- 1
- 0
gatein SVN: r8090 - in epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US: modules and 3 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-11-17 21:52:23 -0500 (Thu, 17 Nov 2011)
New Revision: 8090
Added:
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.xml
Removed:
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.xml
Modified:
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Reference_Guide_eXo_JCR_1.14.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr-with-gatein.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/framework-for-cross-domain-ajax.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/groovy-scripts-as-rest-services.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/introduction-to-rest.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/overwrite-default-providers.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/restservicelist-service.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/ws.xml
Log:
Relocating eXo JCR chapter to new Part
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Reference_Guide_eXo_JCR_1.14.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Reference_Guide_eXo_JCR_1.14.xml 2011-11-18 02:51:34 UTC (rev 8089)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Reference_Guide_eXo_JCR_1.14.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -13,6 +13,7 @@
<xi:include href="modules/AuthenticationAndIdentity.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="modules/WSRP.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="modules/Advanced.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/eXoJCR.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</book>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced.xml 2011-11-18 02:51:34 UTC (rev 8089)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -6,6 +6,6 @@
<part id="part-Reference_Guide_eXo_JCR_1.14-Advanced_Development">
<title>Advanced Development</title>
<xi:include href="Advanced/Foundations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Advanced/eXoJCR.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+
</part>
Deleted: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml 2011-11-17 21:39:57 UTC (rev 8087)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -1,171 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section 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;
-]>
-<section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type">
- <title>Finding Nodes by Mixin Type</title>
- <para>
- Find all nodes in repository, that contain a mixin type "mix:title".
- </para>
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Repository_structure">
- <title>Repository structure:</title>
- <para>
- The repository contains nodes with different primary types and mixin types.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- root
- </para>
- <itemizedlist>
- <listitem>
- <para>
- document1 primarytype = "nt:unstructured" mixintype = "mix:title"
- </para>
-
- </listitem>
- <listitem>
- <para>
- document2 primarytype = "nt:file" mixintype = "mix:lockable"
- </para>
-
- </listitem>
- <listitem>
- <para>
- document3 primarytype = "nt:file" mixintype = "mix:title"
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </listitem>
-
- </itemizedlist>
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Query_execution">
- <title>Query execution</title>
- <para>
- <emphasis role="bold">SQL</emphasis>
- </para>
-
-<programlisting language="Java" role="Java">// make SQL query
-QueryManager queryManager = workspace.getQueryManager();
-// create query
-String sqlStatement = "SELECT * FROM mix:title";
-Query query = queryManager.createQuery(sqlStatement, Query.SQL);
-// execute query and fetch result
-QueryResult result = query.execute();</programlisting>
- <para>
- <emphasis role="bold">XPath</emphasis>
- </para>
-
-<programlisting language="Java" role="Java">// make XPath query
-QueryManager queryManager = workspace.getQueryManager();
-// create query
-String xpathStatement = "//element(*,mix:title)";
-Query query = queryManager.createQuery(xpathStatement, Query.XPATH);
-// execute query and fetch result
-QueryResult result = query.execute();</programlisting>
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Fetching_result">
- <title>Fetching result</title>
- <para>
- Let's get nodes:
- </para>
-
-<programlisting language="Java" role="Java">NodeIterator it = result.getNodes();
-
-if(it.hasNext())
-{
- Node findedNode = it.nextNode();
-}</programlisting>
- <para>
- The NodeIterator will return "document1" and "document3".
- </para>
- <para>
- We can also get a table:
- </para>
-
-<programlisting language="Java" role="Java">String[] columnNames = result.getColumnNames();
-RowIterator rit = result.getRows();
-while (rit.hasNext())
-{
- Row row = rit.nextRow();
- // get values of the row
- Value[] values = row.getValues();
-}</programlisting>
- <para>
- Table content is
- <table>
- <title>Table content</title>
- <tgroup cols="4">
- <thead>
- <row>
- <entry>
- jcr:title
- </entry>
- <entry>
- ...
- </entry>
- <entry>
- jcr:path
- </entry>
- <entry>
- jcr:score
- </entry>
-
- </row>
-
- </thead>
- <tbody>
- <row>
- <entry>
- First document
- </entry>
- <entry>
- ...
- </entry>
- <entry>
- /document1
- </entry>
- <entry>
- 2674
- </entry>
-
- </row>
- <row>
- <entry>
- Second document
- </entry>
- <entry>
- ...
- </entry>
- <entry>
- /document3
- </entry>
- <entry>
- 2674
- </entry>
-
- </row>
-
- </tbody>
-
- </tgroup>
-
- </table>
-
- </para>
-
- </section>
-
-
-</section>
-
-
Copied: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml (from rev 8088, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml)
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml (rev 0)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -0,0 +1,150 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section 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;
+]>
+<section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type">
+ <title>Finding Nodes by Mixin Type</title>
+ <formalpara>
+ <title>Task:</title>
+ <para>
+ Find all nodes in repository, that contain a mixin type <literal>mix:title</literal>.
+ </para>
+ </formalpara>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Repository_structure">
+ <title>Repository structure:</title>
+ <para>
+ The repository contains nodes with different primary types and mixin types.
+ </para>
+<programlisting>root
+ ├── document1 primarytype = "nt:unstructured" mixintype = "mix:title"
+ ├── document2 primarytype = "nt:file" mixintype = "mix:lockable"
+ └── document3 primarytype = "nt:file" mixintype = "mix:title"
+</programlisting>
+
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Query_execution">
+ <title>Query execution</title>
+ <para>
+ <emphasis role="bold">SQL</emphasis>
+ </para>
+
+<programlisting language="Java" role="Java">// make SQL query
+QueryManager queryManager = workspace.getQueryManager();
+// create query
+String sqlStatement = "SELECT * FROM mix:title";
+Query query = queryManager.createQuery(sqlStatement, Query.SQL);
+// execute query and fetch result
+QueryResult result = query.execute();</programlisting>
+ <para>
+ <emphasis role="bold">XPath</emphasis>
+ </para>
+
+<programlisting language="Java" role="Java">// make XPath query
+QueryManager queryManager = workspace.getQueryManager();
+// create query
+String xpathStatement = "//element(*,mix:title)";
+Query query = queryManager.createQuery(xpathStatement, Query.XPATH);
+// execute query and fetch result
+QueryResult result = query.execute();</programlisting>
+
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Fetching_result">
+ <title>Fetching result</title>
+ <para>
+ Let's get nodes:
+ </para>
+
+<programlisting language="Java" role="Java">NodeIterator it = result.getNodes();
+
+if(it.hasNext())
+{
+ Node findedNode = it.nextNode();
+}</programlisting>
+ <para>
+ The NodeIterator will return "document1" and "document3".
+ </para>
+ <para>
+ We can also get a table:
+ </para>
+
+<programlisting language="Java" role="Java">String[] columnNames = result.getColumnNames();
+RowIterator rit = result.getRows();
+while (rit.hasNext())
+{
+ Row row = rit.nextRow();
+ // get values of the row
+ Value[] values = row.getValues();
+}</programlisting>
+ <para>
+ Table content is
+ <table>
+ <title>Table content</title>
+ <tgroup cols="4">
+ <thead>
+ <row>
+ <entry>
+ jcr:title
+ </entry>
+ <entry>
+ ...
+ </entry>
+ <entry>
+ jcr:path
+ </entry>
+ <entry>
+ jcr:score
+ </entry>
+
+ </row>
+
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ First document
+ </entry>
+ <entry>
+ ...
+ </entry>
+ <entry>
+ /document1
+ </entry>
+ <entry>
+ 2674
+ </entry>
+
+ </row>
+ <row>
+ <entry>
+ Second document
+ </entry>
+ <entry>
+ ...
+ </entry>
+ <entry>
+ /document3
+ </entry>
+ <entry>
+ 2674
+ </entry>
+
+ </row>
+
+ </tbody>
+
+ </tgroup>
+
+ </table>
+
+ </para>
+
+ </section>
+
+
+</section>
+
+
Deleted: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/jcr-query-usecases.xml 2011-11-17 21:39:57 UTC (rev 8087)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -1,370 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section 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;
-]>
-<section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases">
- <title>JCR Query Usecases</title>
- <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Intro">
- <title>Intro</title>
- <para>
- The JCR supports two query languages; JCR and XPath. A query, whether XPath or SQL, specifies a subset of nodes within a workspace, called the result set. The result set constitutes all the nodes in the workspace that meet the constraints stated in the query.
- </para>
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Query_Lifecycle">
- <title>Query Lifecycle</title>
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Query_Lifecycle-Query_Creation_and_Execution">
- <title>Query Creation and Execution</title>
- <formalpara>
- <title>SQL</title>
- <para>
-<programlisting language="Java" role="Java">// get QueryManager
-QueryManager queryManager = workspace.getQueryManager();
-// make SQL query
-Query query = queryManager.createQuery("SELECT * FROM nt:base ", Query.SQL);
-// execute query
-QueryResult result = query.execute();</programlisting>
- </para>
- </formalpara>
- <formalpara>
- <title>XPath</title>
- <para>
-<programlisting language="Java" role="Java">// get QueryManager
-QueryManager queryManager = workspace.getQueryManager();
-// make XPath query
-Query query = queryManager.createQuery("//element(*,nt:base)", Query.XPATH);
-// execute query
-QueryResult result = query.execute();</programlisting>
- </para>
- </formalpara>
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Query_Lifecycle-Query_Result_Processing">
- <title>Query Result Processing</title>
-
-<programlisting language="Java" role="Java">// fetch query result
-QueryResult result = query.execute();</programlisting>
- <para>
- To fetch the nodes:
- </para>
-
-<programlisting language="Java" role="Java">NodeIterator it = result.getNodes();</programlisting>
- <para>
- The results can be formatted in a table:
- </para>
-
-<programlisting language="Java" role="Java">// get column names
-String[] columnNames = result.getColumnNames();
-// get column rows
-RowIterator rowIterator = result.getRows();
-while(rowIterator.hasNext()){
- // get next row
- Row row = rowIterator.nextRow();
- // get all values of row
- Value[] values = row.getValues();
-}</programlisting>
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-Query_Lifecycle-Scoring">
- <title>Scoring</title>
- <para>
- The result returns a score for each row in the result set. The score contains a value that indicates a rating of how well the result node matches the query. A high value means a better matching than a low value. This score can be used for ordering the result.
- </para>
- <para>
- eXo JCR Scoring is a mapping of Lucene scoring. For a more in-depth understanding, please study <ulink url="http://lucene.apache.org/java/2_4_1/scoring.html">Lucene documentation</ulink>.
- </para>
- <para>
- The <literal>jcr:score</literal> is calculated as; <literal>(lucene score)*1000f</literal>.
- </para>
- <para>
- Score may be increased for specified nodes, see <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node" />
- </para>
- <para>
- Also, see an example <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score" />
- </para>
-
- </section>
-
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Query_result_settings">
- <title>Query result settings</title>
- <itemizedlist>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit" />
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Type_Constraints">
- <title>Type Constraints</title>
- <itemizedlist>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Nodes" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Primary_Type" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type" />
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Property_Constraints">
- <title>Property Constraints</title>
- <itemizedlist>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Property_Comparison" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-LIKE_Constraint" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Escaping_in_LIKE_Statements" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-NOT_Constraint" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-AND_Constraint" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-OR_Constraint" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Property_Existence_Constraint" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_in_a_Case_Insensitive_Way" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multivalue_Property_Comparison" />
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Path_Constraint">
- <title>Path Constraint</title>
- <itemizedlist>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Exact_Path_Constraint" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Child_Node_Constraint" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes" />
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Ordering_specifying">
- <title>Ordering specifying</title>
- <itemizedlist>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Sorting_Nodes_by_Property" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Descendant_Nodes_Property_XPath_only" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Path_or_Name" />
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Indexing_rules_and_additional_features">
- <title>Indexing rules and additional features</title>
- <itemizedlist>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_ntfile_node_by_content_of_child_jcrcontent_node" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-High_lighting_Result_of_Fulltext_Search" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Removing_Nodes_Property_From_Indexing_Scope" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Regular_Expression_as_Property_Name_in_Indexing_Rules" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Searching_By_Synonym" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase" />
- </para>
-
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes" />
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Query_Examples">
- <title>Query Examples</title>
- <xi:include href="offset-and-limit.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="find-all-nodes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="find-nodes-by-primary-type.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="find-nodes-by-mixin-type.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="property-comparison.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="like-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="escaping-like-statements.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="not-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="and-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="or-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="property-existance-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="find-nodes-case-insensitive.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="date-property-comparison.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="node-name-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="multivalue-property-comparison.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="exact-path-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="child-node-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="find-all-descendant-nodes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="order-by-property.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="order-by-descendant.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="order-by-score.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="order-by-path-or-name.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="fulltext-search-by-property.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="fulltext-search-by-all-properties.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ignore-accent-symbols.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="aggregation-rule.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="index-boost-value.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="node-scope-index.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="regexp-indexing-rule.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="higlight.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="synonim-provider.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="spell-checker.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="find-similar-nodes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- </section>
-
- <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Tips_and_tricks">
- <title>Tips and tricks</title>
- <xi:include href="tip-nodename-with-number.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- </section>
-
-
-</section>
-
-
Copied: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.xml (from rev 8088, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/jcr-query-usecases.xml)
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.xml (rev 0)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -0,0 +1,373 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section 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;
+]>
+<section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases">
+ <title>JCR Query Usecases</title>
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Intro">
+ <title>Introduction</title>
+ <para>
+ The JCR supports two query languages; JCR and XPath. A query, whether XPath or SQL, specifies a subset of nodes within a workspace, called the result set. The result set constitutes all the nodes in the workspace that meet the constraints stated in the query.
+ </para>
+
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Query_Lifecycle">
+ <title>Query Lifecycle</title>
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Query_Lifecycle-Query_Creation_and_Execution">
+ <title>Query Creation and Execution</title>
+ <formalpara>
+ <title>SQL</title>
+ <para>
+<programlisting language="Java" role="Java">// get QueryManager
+QueryManager queryManager = workspace.getQueryManager();
+// make SQL query
+Query query = queryManager.createQuery("SELECT * FROM nt:base ", Query.SQL);
+// execute query
+QueryResult result = query.execute();</programlisting>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>XPath</title>
+ <para>
+<programlisting language="Java" role="Java">// get QueryManager
+QueryManager queryManager = workspace.getQueryManager();
+// make XPath query
+Query query = queryManager.createQuery("//element(*,nt:base)", Query.XPATH);
+// execute query
+QueryResult result = query.execute();</programlisting>
+ </para>
+ </formalpara>
+
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Query_Lifecycle-Query_Result_Processing">
+ <title>Query Result Processing</title>
+
+<programlisting language="Java" role="Java">// fetch query result
+QueryResult result = query.execute();</programlisting>
+ <para>
+ To fetch the nodes:
+ </para>
+
+<programlisting language="Java" role="Java">NodeIterator it = result.getNodes();</programlisting>
+ <para>
+ The results can be formatted in a table:
+ </para>
+
+<programlisting language="Java" role="Java">// get column names
+String[] columnNames = result.getColumnNames();
+// get column rows
+RowIterator rowIterator = result.getRows();
+while(rowIterator.hasNext()){
+ // get next row
+ Row row = rowIterator.nextRow();
+ // get all values of row
+ Value[] values = row.getValues();
+}</programlisting>
+
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-Query_Lifecycle-Scoring">
+ <title>Scoring</title>
+ <para>
+ The result returns a score for each row in the result set. The score contains a value that indicates a rating of how well the result node matches the query. A high value means a better matching than a low value. This score can be used for ordering the result.
+ </para>
+ <para>
+ eXo JCR Scoring is a mapping of Lucene scoring. For a more in-depth understanding, please study <ulink url="http://lucene.apache.org/java/2_4_1/scoring.html">Lucene documentation</ulink>.
+ </para>
+ <para>
+ The <literal>jcr:score</literal> is calculated as; <literal>(lucene score)*1000f</literal>.
+ </para>
+ <para>
+ Score may be increased for specified nodes, see <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node" />
+ </para>
+ <para>
+ Also, see an example in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score" />
+ </para>
+
+ </section>
+
+
+ </section>
+
+ <!--DOCS NOTE: The following 'ToC' sections are not required in Publican builds if the publican.cfg parameter
+ "generate_section_toc_level:" is set to "3" -->
+
+ <!-- <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Query_result_settings">
+ <title>Query result settings</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit" />
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Type_Constraints">
+ <title>Type Constraints</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Nodes" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Primary_Type" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type" />
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Property_Constraints">
+ <title>Property Constraints</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Property_Comparison" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-LIKE_Constraint" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Escaping_in_LIKE_Statements" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-NOT_Constraint" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-AND_Constraint" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-OR_Constraint" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Property_Existence_Constraint" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_in_a_Case_Insensitive_Way" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multivalue_Property_Comparison" />
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Path_Constraint">
+ <title>Path Constraint</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Exact_Path_Constraint" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Child_Node_Constraint" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes" />
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Ordering_specifying">
+ <title>Ordering specifying</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Sorting_Nodes_by_Property" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Descendant_Nodes_Property_XPath_only" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Path_or_Name" />
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Indexing_rules_and_additional_features">
+ <title>Indexing rules and additional features</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_ntfile_node_by_content_of_child_jcrcontent_node" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-High_lighting_Result_of_Fulltext_Search" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Removing_Nodes_Property_From_Indexing_Scope" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Regular_Expression_as_Property_Name_in_Indexing_Rules" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Searching_By_Synonym" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase" />
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes" />
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </section> -->
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Query_Examples">
+ <title>Query Examples</title>
+ <xi:include href="offset-and-limit.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="find-all-nodes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="find-nodes-by-primary-type.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="find-nodes-by-mixin-type.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="property-comparison.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="like-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="escaping-like-statements.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="not-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="and-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="or-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="property-existance-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="find-nodes-case-insensitive.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="date-property-comparison.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="node-name-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="multivalue-property-comparison.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="exact-path-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="child-node-constraint.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="find-all-descendant-nodes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="order-by-property.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="order-by-descendant.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="order-by-score.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="order-by-path-or-name.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="fulltext-search-by-property.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="fulltext-search-by-all-properties.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ignore-accent-symbols.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="aggregation-rule.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="index-boost-value.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="node-scope-index.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="regexp-indexing-rule.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="higlight.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="synonim-provider.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="spell-checker.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="find-similar-nodes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ </section>
+
+ <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Tips_and_tricks">
+ <title>Tips and tricks</title>
+ <xi:include href="tip-nodename-with-number.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ </section>
+
+
+</section>
+
+
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr-with-gatein.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr-with-gatein.xml 2011-11-17 21:39:57 UTC (rev 8087)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/jcr-with-gatein.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -3,9 +3,9 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent">
%BOOK_ENTITIES;
]>
-<section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_with_GateIn">
- <title>eXo JCR with GateIn</title>
- <!-- <xi:include href="jcr-with-gtn/how-to-extend-my-gatein-instance.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> <xi:include href="jcr-with-gtn/managed-datasources-under-jboss-as.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</section>
+<chapter id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_with_GateIn">
+ <title>eXo JCR with GateIn</title>
+ <!-- <xi:include href="jcr-with-gtn/how-to-extend-my-gatein-instance.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> <xi:include href="jcr-with-gtn/managed-datasources-under-jboss-as.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/framework-for-cross-domain-ajax.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/ws/framework-for-cross-domain-ajax.xml 2011-11-17 21:39:57 UTC (rev 8087)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/framework-for-cross-domain-ajax.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -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>Framework for cross-domain AJAX</title>
@@ -116,4 +116,4 @@
<programlisting language="HTML" role="HTML"><button onclick='test()'>test cross-domain</button></programlisting>
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/groovy-scripts-as-rest-services.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/ws/groovy-scripts-as-rest-services.xml 2011-11-17 21:39:57 UTC (rev 8087)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/groovy-scripts-as-rest-services.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -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>Groovy Scripts as REST Services</title>
@@ -382,4 +382,4 @@
<para>That is all.</para>
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/introduction-to-rest.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/ws/introduction-to-rest.xml 2011-11-17 21:39:57 UTC (rev 8087)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/introduction-to-rest.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -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>Introduction to the Representational State Transfer (REST)</title>
@@ -208,4 +208,4 @@
communication-state between messages. Any state retained by the server
must be modeled as a resource..</para>
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/overwrite-default-providers.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/ws/overwrite-default-providers.xml 2011-11-17 21:39:57 UTC (rev 8087)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/overwrite-default-providers.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -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>OverwriteDefaultProviders</title>
@@ -209,4 +209,4 @@
to/from Resource1. But it will not impact to other services in any kind.
</para>
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/restservicelist-service.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/ws/restservicelist-service.xml 2011-11-17 21:39:57 UTC (rev 8087)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/restservicelist-service.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -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>RestServicesList Service</title>
@@ -211,4 +211,4 @@
<para></para>
</section>
</section>
-</section>
+</chapter>
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/ws.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/ws/ws.xml 2011-11-17 21:39:57 UTC (rev 8087)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/eXoJCR/ws/ws.xml 2011-11-18 02:52:23 UTC (rev 8090)
@@ -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 id="WS.RestFramework">
+<chapter id="WS.RestFramework">
<title>eXo Web Services</title>
@@ -15,4 +15,4 @@
Servlet and cross-domain AJAX web-frameworks and JavaBean-JSON
transformer.</para>
</section>
-</section>
+</chapter>
12 years, 6 months
- 1
- 0