Author: smumford Date: 2011-11-15 23:52:13 -0500 (Tue, 15 Nov 2011) New Revision: 8079 Removed: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr.xml Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations.xml 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/jcr/configuration/jdbc-data-container-config.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/jbosscache-configuration-templates.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/protocols/webdav.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/query-handler-config.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/child-node-constraint.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/find-all-nodes.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/fulltext-search-and-settings.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/index-boost-value.xml 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/Advanced/eXoJCR/jcr/searching/node-name-constraint.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/not-constraint.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/spell-checker.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/PortletDevelopment/Global_Portlet.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/publican.cfg Log: Edits of eXo JCR section Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -9,7 +9,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.0</edition> - <pubsnumber>4</pubsnumber> + <pubsnumber>5</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-eXoJCR-1.14/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -8,6 +8,20 @@ <simpara> <revhistory> <revision> + <revnumber>5.2.0-5</revnumber> + <date>Tue Nov 15 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Staging for beta release.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>5.2.0-4</revnumber> <date>Wed Nov 9 2011</date> <author> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -4,7 +4,7 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Reference_Guide_eXo_JCR_1.14-Foundations_"> - <title><remark>Foundations</remark></title> + <title>Foundations</title> <xi:include href="Foundations/Kernel.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Foundations/Config_Retrieval.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Foundations/Advanced_Concepts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/configuration/jdbc-data-container-config.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/configuration/jdbc-data-container-config.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/configuration/jdbc-data-container-config.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -6,11 +6,11 @@ <section 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><remark>Introduction</remark></title> - <para>eXo JCR persistent data container can work in two configuration + <title>Introduction</title> + <para>eXo JCR persistent data container can work in two configuration modes: - </para> - <itemizedlist> + </para> + <itemizedlist> <listitem> <para><phrase>Multi-database</phrase>: One database for each workspace (used in standalone eXo JCR service mode)</para> @@ -33,7 +33,6 @@ Author [w/email]: Nicholas Filetto: nicolas.filotto(a)exoplatform.com License: NA --> -<remark>Below list updated as per email from Nicholas Filetto to jbossexoD(a)googlegroups.com on 10/18/2011</remark> <itemizedlist> <listitem> <para> @@ -142,7 +141,7 @@ The JCR requires at least the <parameter>READ_COMMITED</parameter> isolation level and other RDBMS configurations can cause some side-effects and issues. So, please, make sure proper isolation level is configured on database server side. </para> </note> - <note> + <note> <para>One more mandatory JCR requirement for underlying databases is a case sensitive collation. Microsoft SQL Server both 2005 and 2008 customers must configure their server with collation corresponding to @@ -358,7 +357,7 @@ <para> If a non-ANSI node name is used, you must use a database with MultiLanguage support. Some JDBC drivers need additional parameters for establishing a Unicode friendly connection. For example under mysql it is necessary to add an additional parameter for the JDBC driver at the end of JDBC URL: </para> - <para>There are preconfigured configuration files for HSQLDB. Look for + <para>There are preconfigured configuration files for HSQLDB. Look for these files in /conf/portal and /conf/standalone folders of the jar-file <package>exo.jcr.component.core-XXX.XXX.jar</package> or source-distribution of eXo JCR implementation.</para> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/jbosscache-configuration-templates.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/jbosscache-configuration-templates.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/jbosscache-configuration-templates.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -11,7 +11,7 @@ Each mentioned component uses instances of the JBoss Cache product for caching in clustered environment. So every element has its own transport and has to be configured correctly. As usual, workspaces have similar configuration differing only in cluster-names (and, possibly, some other parameters). The simplest way to configure them is to define their own configuration files for each component in each workspace: </para> -<programlisting language="XML" role="XML">&lt;property name="jbosscache-configuration" value="conf/<remark>standalone</remark> +<programlisting language="XML" role="XML">&lt;property name="jbosscache-configuration" value="conf/standalone /test-jbosscache-lock-db1-ws1.xml" /&gt;</programlisting> <para> But if there are few workspaces, configuring them in such a way can be painful and hard-manageable. eXo JCR offers a template-based configuration for JBoss Cache instances. You can have one template for Lock Manager, one for Indexer and one for data container and use them in all the workspaces, defining the map of substitution parameters in a main configuration file. Just simply define ${jbosscache-&lt;parameter name&gt;} inside xml-template and list correct value in JCR configuration file just below "jbosscache-configuration", as shown: Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/protocols/webdav.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/protocols/webdav.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/protocols/webdav.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -4,52 +4,52 @@ %BOOK_ENTITIES; ]> <section 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> - <para> - The <application>WebDAV</application> protocol enables you to use third party tools to communicate with hierarchical content servers via the HTTP protocol. It is possible to add and remove documents or a set of documents from a path on the server. - </para> - <para> - <application>DeltaV</application> is an extension of the WebDav protocol that allows managing document versioning. The <emphasis>Locking</emphasis> feature guarantees protection against multiple access when writing resources. The ordering support allows changing the position of the resource in the list and sort the directory to make the directory tree viewed conveniently. The full-text search makes it easy to find the necessary documents. You can search by using two languages: SQL and XPATH. - </para> - <para> - In the eXo JCR, the WebDAV layer (based on the code taken from the extension modules of the reference implementation) is plugged in on top of our JCR implementation. This makes it possible to browse a workspace using the third party tools regardless of operating system environments. You can use a Java WebDAV client, such as <application>DAVExplorer</application> or <application>Internet Explorer</application> using <menuchoice><guimenu>File</guimenu><guimenuitem>Open as a Web Folder</guimenuitem></menuchoice>. - </para> - <para> - WebDav is an extension of the REST service. To get the WebDav server ready, you must deploy the REST application. Then, you can access any workspaces of your repository by using the following URL: - </para> - <para> - <ulink type="http" url="http://host:port/portal/rest/private/jcr/{RepositoryName}/{WorkspaceName}/{Path}" /> - </para> - <para> - When accessing the WebDAV server via <ulink type="http" url="http://localhost:8080/rest/jcr/repository/production" />, you can substitute <ulink type="http" url="http://localhost:8080/rest/jcr/repository/production">production</ulink> with <ulink type="http" url="http://localhost:8080/rest/jcr/repository/collaboration">collaboration</ulink>. - </para> - <para> - You will be asked to enter your login credentials. These will then be checked by using the organization service that can be implemented thanks to an InMemory (dummy) module or a DB module or an LDAP one and the JCR user session will be created with the correct JCR Credentials. - </para> - <note> - <title>Note:</title> - <remark>DOCS NOTE: I have no idea what this means!</remark> - <para> - If you try the "in ECM" option, add "@ecm" to the user's password. Alternatively, you may modify jaas.conf by adding the <emphasis role="bold">domain=ecm</emphasis> option as follows: - </para> - + <!-- 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> + <para> + The <application>WebDAV</application> protocol enables you to use third party tools to communicate with hierarchical content servers via the HTTP protocol. It is possible to add and remove documents or a set of documents from a path on the server. + </para> + <para> + <application>DeltaV</application> is an extension of the WebDav protocol that allows managing document versioning. The <emphasis>Locking</emphasis> feature guarantees protection against multiple access when writing resources. The ordering support allows changing the position of the resource in the list and sort the directory to make the directory tree viewed conveniently. The full-text search makes it easy to find the necessary documents. You can search by using two languages: SQL and XPATH. + </para> + <para> + In the eXo JCR, the WebDAV layer (based on the code taken from the extension modules of the reference implementation) is plugged in on top of our JCR implementation. This makes it possible to browse a workspace using the third party tools regardless of operating system environments. You can use a Java WebDAV client, such as <application>DAVExplorer</application> or <application>Internet Explorer</application> using <menuchoice><guimenu>File</guimenu><guimenuitem>Open as a Web Folder</guimenuitem></menuchoice>. + </para> + <para> + WebDav is an extension of the REST service. To get the WebDav server ready, you must deploy the REST application. Then, you can access any workspaces of your repository by using the following URL: + </para> + <para> + <ulink type="http" url="http://host:port/portal/rest/private/jcr/{RepositoryName}/{WorkspaceName}/{Path}" /> + </para> + <para> + When accessing the WebDAV server via <ulink type="http" url="http://localhost:8080/rest/jcr/repository/production" />, you can substitute <ulink type="http" url="http://localhost:8080/rest/jcr/repository/production">production</ulink> with <ulink type="http" url="http://localhost:8080/rest/jcr/repository/collaboration">collaboration</ulink>. + </para> + <para> + You will be asked to enter your login credentials. These will then be checked by using the organization service that can be implemented thanks to an InMemory (dummy) module or a DB module or an LDAP one and the JCR user session will be created with the correct JCR Credentials. + </para> + <note> + <title>Note:</title> + <!-- <remark>DOCS NOTE: I have no idea what this means!</remark>--> + <para> + If you try the "in ECM" option, add "@ecm" to the user's password. Alternatively, you may modify jaas.conf by adding the <emphasis role="bold">domain=ecm</emphasis> option as follows: + </para> + <programlisting>exo-domain { org.exoplatform.services.security.jaas.BasicLoginModule required domain=ecm; };</programlisting> - </note> + </note> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-WebDAV-WebDAV_Configuration"> - <title>WebDAV Configuration</title> - <para> - The WebDAV configuration is defined in the <remark><filename>DOC NOTE: where/is/this/file.xml</filename></remark> - file: - </para> - + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-WebDAV-WebDAV_Configuration"> + <title>WebDAV Configuration</title> + <para> + The WebDAV configuration file: <!--is defined in the <remark><filename>DOC NOTE: where/is/this/file.xml</filename></remark>--> + + </para> + <programlisting language="XML" role="XML">&lt;component&gt; &lt;key&gt;org.exoplatform.services.webdav.WebDavServiceImpl&lt;/key&gt; &lt;type&gt;org.exoplatform.services.webdav.WebDavServiceImpl&lt;/type&gt; @@ -133,354 +133,354 @@ &lt;/init-params &lt;/component&gt;</programlisting> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-WebDAV-Corresponding_WebDav_and_JCR_actions"> - <title>Corresponding WebDav and JCR actions</title> - <table> - <title></title> - <tgroup cols="2"> - <thead> - <row> - <entry> - WebDav - </entry> - <entry> - JCR - </entry> + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-WebDAV-Corresponding_WebDav_and_JCR_actions"> + <title>Corresponding WebDav and JCR actions</title> + <table> + <title></title> + <tgroup cols="2"> + <thead> + <row> + <entry> + WebDav + </entry> + <entry> + JCR + </entry> - </row> + </row> - </thead> - <tbody> - <row> - <entry> - COPY - </entry> - <entry> - Workspace.copy(...) - </entry> + </thead> + <tbody> + <row> + <entry> + COPY + </entry> + <entry> + Workspace.copy(...) + </entry> - </row> - <row> - <entry> - DELETE - </entry> - <entry> - Node.remove() - </entry> + </row> + <row> + <entry> + DELETE + </entry> + <entry> + Node.remove() + </entry> - </row> - <row> - <entry> - GET - </entry> - <entry> - Node.getProperty(...); Property.getValue() - </entry> + </row> + <row> + <entry> + GET + </entry> + <entry> + Node.getProperty(...); Property.getValue() + </entry> - </row> - <row> - <entry> - HEAD - </entry> - <entry> - Node.getProperty(...); Property.getLength() - </entry> + </row> + <row> + <entry> + HEAD + </entry> + <entry> + Node.getProperty(...); Property.getLength() + </entry> - </row> - <row> - <entry> - MKCOL - </entry> - <entry> - Node.addNode(...) - </entry> + </row> + <row> + <entry> + MKCOL + </entry> + <entry> + Node.addNode(...) + </entry> - </row> - <row> - <entry> - MOVE - </entry> - <entry> - Session.move(...) or Workspace.move(...) - </entry> + </row> + <row> + <entry> + MOVE + </entry> + <entry> + Session.move(...) or Workspace.move(...) + </entry> - </row> - <row> - <entry> - PROPFIND - </entry> - <entry> - Session.getNode(...); Node.getNode(...); Node.getNodes(...); Node.getProperties() - </entry> + </row> + <row> + <entry> + PROPFIND + </entry> + <entry> + Session.getNode(...); Node.getNode(...); Node.getNodes(...); Node.getProperties() + </entry> - </row> - <row> - <entry> - PROPPATCH - </entry> - <entry> - Node.setProperty(...); Node.getProperty(...).remove() - </entry> + </row> + <row> + <entry> + PROPPATCH + </entry> + <entry> + Node.setProperty(...); Node.getProperty(...).remove() + </entry> - </row> - <row> - <entry> - PUT - </entry> - <entry> - Node.addNode("node","nt:file"); Node.setProperty("jcr:data", "data") - </entry> + </row> + <row> + <entry> + PUT + </entry> + <entry> + Node.addNode("node","nt:file"); Node.setProperty("jcr:data", "data") + </entry> - </row> - <row> - <entry> - CHECKIN - </entry> - <entry> - Node.checkin() - </entry> + </row> + <row> + <entry> + CHECKIN + </entry> + <entry> + Node.checkin() + </entry> - </row> - <row> - <entry> - CHECKOUT - </entry> - <entry> - Node.checkout() - </entry> + </row> + <row> + <entry> + CHECKOUT + </entry> + <entry> + Node.checkout() + </entry> - </row> - <row> - <entry> - REPORT - </entry> - <entry> - Node.getVersionHistory(); VersionHistory.getAllVersions(); Version.getProperties() - </entry> + </row> + <row> + <entry> + REPORT + </entry> + <entry> + Node.getVersionHistory(); VersionHistory.getAllVersions(); Version.getProperties() + </entry> - </row> - <row> - <entry> - RESTORE - </entry> - <entry> - Node.restore(...) - </entry> + </row> + <row> + <entry> + RESTORE + </entry> + <entry> + Node.restore(...) + </entry> - </row> - <row> - <entry> - UNCHECKOUT - </entry> - <entry> - Node.restore(...) - </entry> + </row> + <row> + <entry> + UNCHECKOUT + </entry> + <entry> + Node.restore(...) + </entry> - </row> - <row> - <entry> - VERSION-CONTROL - </entry> - <entry> - Node.addMixin("mix:versionable") - </entry> + </row> + <row> + <entry> + VERSION-CONTROL + </entry> + <entry> + Node.addMixin("mix:versionable") + </entry> - </row> - <row> - <entry> - LOCK - </entry> - <entry> - Node.lock(...) - </entry> + </row> + <row> + <entry> + LOCK + </entry> + <entry> + Node.lock(...) + </entry> - </row> - <row> - <entry> - UNLOCK - </entry> - <entry> - Node.unlock() - </entry> + </row> + <row> + <entry> + UNLOCK + </entry> + <entry> + Node.unlock() + </entry> - </row> - <row> - <entry> - ORDERPATCH - </entry> - <entry> - Node.orderBefore(...) - </entry> + </row> + <row> + <entry> + ORDERPATCH + </entry> + <entry> + Node.orderBefore(...) + </entry> - </row> - <row> - <entry> - SEARCH - </entry> - <entry> - Workspace.getQueryManager(); QueryManager.createQuery(); Query.execute() - </entry> + </row> + <row> + <entry> + SEARCH + </entry> + <entry> + Workspace.getQueryManager(); QueryManager.createQuery(); Query.execute() + </entry> - </row> + </row> - </tbody> + </tbody> - </tgroup> + </tgroup> - </table> + </table> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-WebDAV-WebDAV_Considerations"> - <title>WebDAV Considerations</title> - <para> - There are some restrictions for WebDAV in different operating systems. - </para> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-WebDAV_Considerations-Windows_7"> - <title>Windows 7</title> - <para> - When attemping to set up a web folder through <guilabel>Add a Network Location</guilabel> or <guilabel>Map a Network Drive</guilabel> through <guilabel>My Computer</guilabel>, an error message stating <guilabel>The folder you entered does not appear to be valid. Please choose another</guilabel> or <guilabel>Windows cannot access … Check the spelling of the name. Otherwise, there might be …</guilabel> may be encountered. These errors may appear when you are using SSL or non-SSL. - </para> + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-WebDAV-WebDAV_Considerations"> + <title>WebDAV Considerations</title> + <para> + There are some restrictions for WebDAV in different operating systems. + </para> + <formalpara id="form-Reference_Guide_eXo_JCR_1.14-WebDAV_Considerations-Windows_7"> + <title>Windows 7</title> + <para> + When attemping to set up a web folder through <guilabel>Add a Network Location</guilabel> or <guilabel>Map a Network Drive</guilabel> through <guilabel>My Computer</guilabel>, an error message stating <guilabel>The folder you entered does not appear to be valid. Please choose another</guilabel> or <guilabel>Windows cannot access … Check the spelling of the name. Otherwise, there might be …</guilabel> may be encountered. These errors may appear when you are using SSL or non-SSL. + </para> - </formalpara> - <para> - To fix this, do as follows: - </para> - <orderedlist> - <listitem> - <para> - Go to Windows Registry Editor. - </para> + </formalpara> + <para> + To fix this, do as follows: + </para> + <orderedlist> + <listitem> + <para> + Go to Windows Registry Editor. + </para> - </listitem> - <listitem> - <para> - Find a key: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\services\WebClient\Parameters\BasicAuthLevel . - </para> + </listitem> + <listitem> + <para> + Find a key: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\services\WebClient\Parameters\BasicAuthLevel . + </para> - </listitem> - <listitem> - <para> - Change the value to 2. - </para> + </listitem> + <listitem> + <para> + Change the value to 2. + </para> - </listitem> + </listitem> - </orderedlist> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-WebDAV_Considerations-Microsoft_Office_2010"> - <title>Microsoft Office 2010</title> - <para> - If you have: - </para> + </orderedlist> + <formalpara id="form-Reference_Guide_eXo_JCR_1.14-WebDAV_Considerations-Microsoft_Office_2010"> + <title>Microsoft Office 2010</title> + <para> + If you have: + </para> - </formalpara> - <itemizedlist> - <listitem> - <para> - Microsoft Office 2007/2010 applications installed on a client computer AND... - </para> + </formalpara> + <itemizedlist> + <listitem> + <para> + Microsoft Office 2007/2010 applications installed on a client computer AND... + </para> - </listitem> - <listitem> - <para> - The client computer is connected to a web server configured for Basic authentication VIA... - </para> + </listitem> + <listitem> + <para> + The client computer is connected to a web server configured for Basic authentication VIA... + </para> - </listitem> - <listitem> - <para> - A connection that does not use Secure Sockets Layer (SSL) AND... - </para> + </listitem> + <listitem> + <para> + A connection that does not use Secure Sockets Layer (SSL) AND... + </para> - </listitem> - <listitem> - <para> - You try to access an Office file that is stored on the remote server... - </para> + </listitem> + <listitem> + <para> + You try to access an Office file that is stored on the remote server... + </para> - </listitem> - <listitem> - <para> - You might experience the following symptoms when you try to open or to download the file: - </para> - <itemizedlist> - <listitem> - <para> - The Office file does not open or download. - </para> + </listitem> + <listitem> + <para> + You might experience the following symptoms when you try to open or to download the file: + </para> + <itemizedlist> + <listitem> + <para> + The Office file does not open or download. + </para> - </listitem> - <listitem> - <para> - You do not receive a Basic authentication password prompt when you try to open or to download the file. - </para> + </listitem> + <listitem> + <para> + You do not receive a Basic authentication password prompt when you try to open or to download the file. + </para> - </listitem> - <listitem> - <para> - You do not receive an error message when you try to open the file. The associated Office application starts. However, the selected file does not open. - </para> + </listitem> + <listitem> + <para> + You do not receive an error message when you try to open the file. The associated Office application starts. However, the selected file does not open. + </para> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </listitem> + </listitem> - </itemizedlist> - <para> - These outcomes can be circumvented by enabling Basic authentication on the client machine. - </para> - <para> - To enable Basic authentication on the client computer, follow these steps: - </para> - <orderedlist> - <listitem> - <para> - Click Start, type <literal>regedit</literal> in the Start Search box, and then press Enter. - </para> + </itemizedlist> + <para> + These outcomes can be circumvented by enabling Basic authentication on the client machine. + </para> + <para> + To enable Basic authentication on the client computer, follow these steps: + </para> + <orderedlist> + <listitem> + <para> + Click Start, type <literal>regedit</literal> in the Start Search box, and then press Enter. + </para> - </listitem> - <listitem> - <para> - Locate and then click the following registry subkey: - </para> - <para> - <envar>HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Internet</envar> - </para> + </listitem> + <listitem> + <para> + Locate and then click the following registry subkey: + </para> + <para> + <envar>HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Internet</envar> + </para> - </listitem> - <listitem> - <para> - On the <guilabel>Edit</guilabel> menu, point to <guilabel>New</guilabel>, and then click <guilabel>DWORD Value</guilabel>. - </para> + </listitem> + <listitem> + <para> + On the <guilabel>Edit</guilabel> menu, point to <guilabel>New</guilabel>, and then click <guilabel>DWORD Value</guilabel>. + </para> - </listitem> - <listitem> - <para> - Type <literal>BasicAuthLevel</literal>, and then press <keycap>Enter</keycap>. - </para> + </listitem> + <listitem> + <para> + Type <literal>BasicAuthLevel</literal>, and then press <keycap>Enter</keycap>. + </para> - </listitem> - <listitem> - <para> - Right-click <literal>BasicAuthLevel</literal>, and then click <guilabel>Modify</guilabel>. - </para> + </listitem> + <listitem> + <para> + Right-click <literal>BasicAuthLevel</literal>, and then click <guilabel>Modify</guilabel>. + </para> - </listitem> - <listitem> - <para> - In the Value data box, type <literal>2</literal>, and then click <guilabel>OK</guilabel>. - </para> + </listitem> + <listitem> + <para> + In the Value data box, type <literal>2</literal>, and then click <guilabel>OK</guilabel>. + </para> - </listitem> + </listitem> - </orderedlist> + </orderedlist> - </section> - + </section> + </section> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/query-handler-config.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/query-handler-config.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/query-handler-config.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -423,7 +423,7 @@ &lt;locking useLockStriping="false" concurrencyLevel="50000" lockParentForChildInsertRemove="false" lockAcquisitionTimeout="20000" /&gt; &lt;!-- Configure the TransactionManager --&gt; - &lt;transaction transactionManagerLookupClass="org.jboss.cache.transaction.JBoss<remark>Standalone</remark> + &lt;transaction transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandalone JTAManagerLookup" /&gt; &lt;clustering mode="replication" clusterName="${jbosscache-cluster-name}"&gt; &lt;stateRetrieval timeout="20000" fetchInMemoryState="false" /&gt; Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/child-node-constraint.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/child-node-constraint.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/child-node-constraint.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -19,11 +19,11 @@ The repository is filled by "<literal>nt:folder</literal>" nodes. The nodes are placed in a multilayer tree. </para> <screen>root -└── folder1 (nt:folder) - └── folder2 (nt:folder) - ├── folder3 (nt:folder) // This node we want to find - │ └── folder4 (nt:folder) // This node is not child but a descendant of '/folder1/folder2/' - └── folder5 (nt:folder) // This node we want to find + └── folder1 (nt:folder) + └── folder2 (nt:folder) + ├── folder3 (nt:folder) // This node we want to find + │ └── folder4 (nt:folder) // This node is not child but a descendant of '/folder1/folder2/' + └── folder5 (nt:folder) // This node we want to find </screen> </section> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/find-all-nodes.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/find-all-nodes.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/find-all-nodes.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -23,11 +23,11 @@ Repository contains many different nodes. </para> <programlisting>root -└── folder1 (nt:folder) - ├── document1 (nt:file) - └── folder2 (nt:folder) - ├── document2 (nt:unstructured) - └── document3 (nt:folder) + └── folder1 (nt:folder) + ├── document1 (nt:file) + └── folder2 (nt:folder) + ├── document2 (nt:unstructured) + └── document3 (nt:folder) </programlisting> </section> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/fulltext-search-and-settings.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/fulltext-search-and-settings.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/fulltext-search-and-settings.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -4,334 +4,302 @@ %BOOK_ENTITIES; ]> <section 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> - <para> - Each property of a node (if it is indexable) is processed with Lucene analyzer and stored in Lucene index. That's called indexing of a property. After that we can perform a fulltext search among these indexed properties. - </para> + <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> + <para> + Each property of a node (if it is indexable) is processed with Lucene analyzer and stored in Lucene index. That's called indexing of a property. After that we can perform a fulltext search among these indexed properties. + </para> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings-Lucene_Analyzers"> - <title>Lucene Analyzers</title> - <para> - The sense of analyzers is to transform all strings stored in the index in a well-defined condition. The same analyzer(s) is/are used when searching in order to adapt the query string to the index reality. - </para> - <para> - Therefore, performing the same query using different analyzers can return different results. - </para> - <para> - Now, let's see how the same string is transformed by different analyzers. - </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Lucene_Analyzers-The_quick_brown_fox_jumped_over_the_lazy_dogs"> - <title>"The quick brown fox jumped over the lazy dogs"</title> - <tgroup cols="2"> - <thead> - <row> - <entry> - Analyzer - </entry> - <entry> - Parsed - </entry> + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings-Lucene_Analyzers"> + <title>Lucene Analyzers</title> + <para> + The sense of analyzers is to transform all strings stored in the index in a well-defined condition. The same analyzer(s) is/are used when searching in order to adapt the query string to the index reality. + </para> + <para> + Therefore, performing the same query using different analyzers can return different results. + </para> + <para> + Now, let's see how the same string is transformed by different analyzers. + </para> + <table id="tabl-Reference_Guide_eXo_JCR_1.14-Lucene_Analyzers-The_quick_brown_fox_jumped_over_the_lazy_dogs"> + <title>"The quick brown fox jumped over the lazy dogs"</title> + <tgroup cols="2"> + <thead> + <row> + <entry> + Analyzer + </entry> + <entry> + Parsed + </entry> - </row> + </row> - </thead> - <tbody> - <row> - <entry> - org.apache.lucene.analysis.WhitespaceAnalyzer - </entry> - <entry> - [The] [quick] [brown] [fox] [jumped] [over] [the] [lazy] [dogs] - </entry> + </thead> + <tbody> + <row> + <entry> + org.apache.lucene.analysis.WhitespaceAnalyzer + </entry> + <entry> + [The] [quick] [brown] [fox] [jumped] [over] [the] [lazy] [dogs] + </entry> - </row> - <row> - <entry> - org.apache.lucene.analysis.SimpleAnalyzer - </entry> - <entry> - [the] [quick] [brown] [fox] [jumped] [over] [the] [lazy] [dogs] - </entry> + </row> + <row> + <entry> + org.apache.lucene.analysis.SimpleAnalyzer + </entry> + <entry> + [the] [quick] [brown] [fox] [jumped] [over] [the] [lazy] [dogs] + </entry> - </row> - <row> - <entry> - org.apache.lucene.analysis.StopAnalyzer - </entry> - <entry> - [quick] [brown] [fox] [jumped] [over] [lazy] [dogs] - </entry> + </row> + <row> + <entry> + org.apache.lucene.analysis.StopAnalyzer + </entry> + <entry> + [quick] [brown] [fox] [jumped] [over] [lazy] [dogs] + </entry> - </row> - <row> - <entry> - org.apache.lucene.analysis.standard.StandardAnalyzer - </entry> - <entry> - [quick] [brown] [fox] [jumped] [over] [lazy] [dogs] - </entry> + </row> + <row> + <entry> + org.apache.lucene.analysis.standard.StandardAnalyzer + </entry> + <entry> + [quick] [brown] [fox] [jumped] [over] [lazy] [dogs] + </entry> - </row> - <row> - <entry> - org.apache.lucene.analysis.snowball.SnowballAnalyzer - </entry> - <entry> - [quick] [brown] [fox] [jump] [over] [lazi] [dog] - </entry> + </row> + <row> + <entry> + org.apache.lucene.analysis.snowball.SnowballAnalyzer + </entry> + <entry> + [quick] [brown] [fox] [jump] [over] [lazi] [dog] + </entry> - </row> - <row> - <entry> - org.apache.lucene.analysis.standard.StandardAnalyzer (configured without stop word - jcr default analyzer) - </entry> - <entry> - [the] [quick] [brown] [fox] [jumped] [over] [the] [lazy] [dogs] - </entry> + </row> + <row> + <entry> + org.apache.lucene.analysis.standard.StandardAnalyzer (configured without stop word - jcr default analyzer) + </entry> + <entry> + [the] [quick] [brown] [fox] [jumped] [over] [the] [lazy] [dogs] + </entry> - </row> + </row> - </tbody> + </tbody> - </tgroup> + </tgroup> - </table> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Lucene_Analyzers-XYampZ_Corporation_xyzexample.com"> - <title>"XY&amp;Z Corporation - xyz(a)example.com&quot;&lt;/title&gt; - <tgroup cols="2"> - <thead> - <row> - <entry> - Analyzer - </entry> - <entry> - Parsed - </entry> + </table> + <table id="tabl-Reference_Guide_eXo_JCR_1.14-Lucene_Analyzers-XYampZ_Corporation_xyzexample.com"> + <title>"XY&amp;Z Corporation - xyz(a)example.com&quot;&lt;/title&gt; + <tgroup cols="2"> + <thead> + <row> + <entry> + Analyzer + </entry> + <entry> + Parsed + </entry> - </row> + </row> - </thead> - <tbody> - <row> - <entry> - org.apache.lucene.analysis.WhitespaceAnalyzer - </entry> - <entry> - [XY&amp;Z] [Corporation] [-] [xyz(a)example.com] - </entry> + </thead> + <tbody> + <row> + <entry> + org.apache.lucene.analysis.WhitespaceAnalyzer + </entry> + <entry> + [XY&amp;Z] [Corporation] [-] [xyz(a)example.com] + </entry> - </row> - <row> - <entry> - org.apache.lucene.analysis.SimpleAnalyzer - </entry> - <entry> - [xy] [z] [corporation] [xyz] [example] [com] - </entry> + </row> + <row> + <entry> + org.apache.lucene.analysis.SimpleAnalyzer + </entry> + <entry> + [xy] [z] [corporation] [xyz] [example] [com] + </entry> - </row> - <row> - <entry> - org.apache.lucene.analysis.StopAnalyzer - </entry> - <entry> - [xy] [z] [corporation] [xyz] [example] [com] - </entry> + </row> + <row> + <entry> + org.apache.lucene.analysis.StopAnalyzer + </entry> + <entry> + [xy] [z] [corporation] [xyz] [example] [com] + </entry> - </row> - <row> - <entry> - org.apache.lucene.analysis.standard.StandardAnalyzer - </entry> - <entry> - [xy&amp;z] [corporation] [xyz@example] [com] - </entry> + </row> + <row> + <entry> + org.apache.lucene.analysis.standard.StandardAnalyzer + </entry> + <entry> + [xy&amp;z] [corporation] [xyz@example] [com] + </entry> - </row> - <row> - <entry> - org.apache.lucene.analysis.snowball.SnowballAnalyzer - </entry> - <entry> - [xy&amp;z] [corpor] [xyz@exampl] [com] - </entry> + </row> + <row> + <entry> + org.apache.lucene.analysis.snowball.SnowballAnalyzer + </entry> + <entry> + [xy&amp;z] [corpor] [xyz@exampl] [com] + </entry> - </row> - <row> - <entry> - org.apache.lucene.analysis.standard.StandardAnalyzer (configured without stop word - jcr default analyzer) - </entry> - <entry> - [xy&amp;z] [corporation] [xyz@example] [com] - </entry> + </row> + <row> + <entry> + org.apache.lucene.analysis.standard.StandardAnalyzer (configured without stop word - jcr default analyzer) + </entry> + <entry> + [xy&amp;z] [corporation] [xyz@example] [com] + </entry> - </row> + </row> - </tbody> + </tbody> - </tgroup> + </tgroup> - </table> - <note> - <para> - StandardAnalyzer is the default analyzer in exo's jcr search engine. But we do not use stop words. - </para> + </table> + <note> + <para> + StandardAnalyzer is the default analyzer in exo's jcr search engine. But we do not use stop words. + </para> - </note> - <para> - You can assign your analyzer as described in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Search_Configuration" /> - </para> + </note> + <para> + You can assign your analyzer as described in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Search_Configuration" /> + </para> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings-How_are_different_properties_indexed"> - <title>How are different properties indexed?</title> - <para> - Different properties are indexed in different ways, this affects to if it can be searched like fulltext by property or not. - </para> - <para> - Only two property types are indexed as fulltext searcheable: STRING and BINARY. - </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-How_are_different_properties_indexed-Fulltext_search_by_different_properties"> - <title>Fulltext search by different properties</title> - <tgroup cols="3"> - <thead> - <row> - <entry> - Property Type - </entry> - <entry> - Fulltext search by all properties - </entry> - <entry> - Fulltext search by exact property - </entry> + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings-How_are_different_properties_indexed"> + <title>How are different properties indexed?</title> + <para> + Different properties are indexed in different ways, this affects to if it can be searched like fulltext by property or not. + </para> + <para> + Only two property types are indexed as fulltext searcheable: STRING and BINARY. + </para> + <table id="tabl-Reference_Guide_eXo_JCR_1.14-How_are_different_properties_indexed-Fulltext_search_by_different_properties"> + <title>Fulltext search by different properties</title> + <tgroup cols="3"> + <thead> + <row> + <entry> + Property Type + </entry> + <entry> + Fulltext search by all properties + </entry> + <entry> + Fulltext search by exact property + </entry> - </row> + </row> - </thead> - <tbody> - <row> - <entry> - STRING - </entry> - <entry> - YES - </entry> - <entry> - YES - </entry> + </thead> + <tbody> + <row> + <entry> + STRING + </entry> + <entry> + YES + </entry> + <entry> + YES + </entry> - </row> - <row> - <entry> - BINARY - </entry> - <entry> - YES - </entry> - <entry> - NO - </entry> + </row> + <row> + <entry> + BINARY + </entry> + <entry> + YES + </entry> + <entry> + NO + </entry> - </row> + </row> - </tbody> + </tbody> - </tgroup> + </tgroup> - </table> - <para> - For example, ưe have property jcr:data (it' BINARY). It's stored well, but you will never find any string with query like: - </para> - + </table> + <para> + For example, ưe have property jcr:data (it' BINARY). It's stored well, but you will never find any string with query like: + </para> + <programlisting>SELECT * FROM nt:resource WHERE CONTAINS(jcr:data, 'some string')</programlisting> - <para> - Because,  BINARY is not searchable by fulltext search on exact property. - </para> - <para> - But, next query will return result (off course if node has searched data): - </para> - + <para> + Because,  BINARY is not searchable by fulltext search on exact property. + </para> + <para> + But, next query will return result (off course if node has searched data): + </para> + <programlisting>SELECT * FROM nt:resource WHERE CONTAINS( * , 'some string')</programlisting> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings-Fulltext_search_query_examples"> - <title>Fulltext search query examples</title> - <itemizedlist> - <listitem> - <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_Property" /> - </para> + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings-Different_analyzers_in_action"> + <title>Different analyzers in action</title> + <para> + First of all, we will fill repository by nodes with mixin type 'mix:title' and different values of 'jcr:description' property. + </para> + <itemizedlist> + <listitem> + <para> + root + </para> + <itemizedlist> + <listitem> + <para> + document1 (mix:title) jcr:description = "The quick brown fox jumped over the lazy dogs" + </para> - </listitem> - <listitem> - <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_All_Properties_in_Node" /> - </para> + </listitem> + <listitem> + <para> + document2 (mix:title) jcr:description = "Brown fox live in forest." + </para> - </listitem> - <listitem> - <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Finding_ntfile_node_by_content_of_child_jcrcontent_node" /> - </para> + </listitem> + <listitem> + <para> + document3 (mix:title) jcr:description = "Fox is a nice animal." + </para> - </listitem> - <listitem> - <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Ignoring_Accent_Symbols._New_Analyzer_Setting." /> - </para> + </listitem> - </listitem> + </itemizedlist> - </itemizedlist> + </listitem> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings-Different_analyzers_in_action"> - <title>Different analyzers in action</title> - <para> - First of all, we will fill repository by nodes with mixin type 'mix:title' and different values of 'jcr:description' property. - </para> - <itemizedlist> - <listitem> - <para> - root - </para> - <itemizedlist> - <listitem> - <para> - document1 (mix:title) jcr:description = "The quick brown fox jumped over the lazy dogs" - </para> - - </listitem> - <listitem> - <para> - document2 (mix:title) jcr:description = "Brown fox live in forest." - </para> - - </listitem> - <listitem> - <para> - document3 (mix:title) jcr:description = "Fox is a nice animal." - </para> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - <para> - Let's see analyzers effect closer. In first case, we use base jcr settings, so, as mentioned above, string "The quick brown fox jumped over the lazy dogs" will be transformed to set {[the] [quick] [brown] [fox] [jumped] [over] [the] [lazy] [dogs] } - </para> - + </itemizedlist> + <para> + Let's see analyzers effect closer. In first case, we use base jcr settings, so, as mentioned above, string "The quick brown fox jumped over the lazy dogs" will be transformed to set {[the] [quick] [brown] [fox] [jumped] [over] [the] [lazy] [dogs] } + </para> + <programlisting language="Java" role="Java">// make SQL query QueryManager queryManager = workspace.getQueryManager(); String sqlStatement = "SELECT * FROM mix:title WHERE CONTAINS(jcr:description, 'the')"; @@ -339,15 +307,15 @@ Query query = queryManager.createQuery(sqlStatement, Query.SQL); // execute query and fetch result QueryResult result = query.execute();</programlisting> - <para> - NodeIterator will return "document1". - </para> - <para> - Now change the default analyzer to org.apache.lucene.analysis.StopAnalyzer. Fill repository again (new Analyzer must process nodes properties) and run the same query again. It will return nothing, because stop words like "the" will be excluded from parsed string set. - </para> + <para> + NodeIterator will return "document1". + </para> + <para> + Now change the default analyzer to org.apache.lucene.analysis.StopAnalyzer. Fill repository again (new Analyzer must process nodes properties) and run the same query again. It will return nothing, because stop words like "the" will be excluded from parsed string set. + </para> - </section> - + </section> + </section> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/index-boost-value.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/index-boost-value.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/index-boost-value.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -6,7 +6,7 @@ <section id="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node"> <title>Changing Priority of Node</title> <formalpara> - <title></title> + <title>Task:</title> <para> Set different boost values for predefined nodes, and check the effect of this change by selecting those nodes and order them by <literal>jcr:score</literal>. </para> Modified: 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/Advanced/eXoJCR/jcr/searching/jcr-query-usecases.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/jcr-query-usecases.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -8,7 +8,7 @@ <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Intro"> <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. + 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> @@ -17,26 +17,28 @@ <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> - <para> - <emphasis role="bold">SQL</emphasis> - </para> - + <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> - <emphasis role="bold">XPath</emphasis> - </para> - + </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> @@ -46,12 +48,12 @@ <programlisting language="Java" role="Java">// fetch query result QueryResult result = query.execute();</programlisting> <para> - Now we can get result in an iterator of nodes: + To fetch the nodes: </para> <programlisting language="Java" role="Java">NodeIterator it = result.getNodes();</programlisting> <para> - or we get the result in a table: + The results can be formatted in a table: </para> <programlisting language="Java" role="Java">// get column names @@ -76,7 +78,7 @@ 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. + 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" /> @@ -89,7 +91,7 @@ </section> - + <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Query_result_settings"> <title>Query result settings</title> <itemizedlist> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/node-name-constraint.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/node-name-constraint.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/node-name-constraint.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -5,12 +5,17 @@ ]> <section id="sect-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint"> <title>Node Name Constraint</title> - <para> - Find all nodes with primary type 'nt:file' whose node name is 'document'. The node name is accessible by a function called "fn:name()". - </para> + <formalpara> + <title>Task:</title> + <para> + Find all nodes with primary type <literal>nt:file</literal> whose node name is <parameter>document</parameter>. The node name is accessible by a function called <code>fn:name()</code>. + </para> + </formalpara> + <note> + <title>Note</title> <para> - fn:name() can be used ONLY with an equal('=') comparison. + <code>fn:name()</code> can be used ONLY with an equal(<literal>=</literal>) comparison. </para> </note> @@ -19,45 +24,20 @@ <para> The repository contains nt:file nodes with different names. </para> - <itemizedlist> - <listitem> - <para> - root - </para> - <itemizedlist> - <listitem> - <para> - document1 (nt:file) - </para> +<programlisting>root + ├── document1 (nt:file) + ├── file (nt:file) + └── somename (nt:file) +</programlisting> - </listitem> - <listitem> - <para> - file (nt:file) - </para> - </listitem> - <listitem> - <para> - somename (nt:file) - </para> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint-Query_execution"> <title>Query execution</title> - <para> - <emphasis role="bold">SQL</emphasis> - </para> - + <formalpara> + <title>SQL</title> + <para> <programlisting language="Java" role="Java">// make SQL query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -65,10 +45,11 @@ Query query = queryManager.createQuery(sqlStatement, Query.SQL); // execute query and fetch result QueryResult result = query.execute();</programlisting> - <para> - <emphasis role="bold">XPath</emphasis> - </para> - + </para> + </formalpara> + <formalpara> + <title>XPath</title> + <para> <programlisting language="Java" role="Java">// make XPath query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -76,13 +57,15 @@ Query query = queryManager.createQuery(xpathStatement, Query.XPATH); // execute query and fetch result QueryResult result = query.execute();</programlisting> + </para> + </formalpara> </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint-Fetching_the_Result"> <title>Fetching the Result</title> <para> - Let's get nodes: + To fetch appropriate nodes: </para> <programlisting language="Java" role="Java">NodeIterator it = result.getNodes(); @@ -92,10 +75,10 @@ Node findedNode = it.nextNode(); }</programlisting> <para> - The NodeIterator will return the node whose fn:name equals "document". + The <literal>NodeIterator</literal> will return the node whose <literal>fn:name</literal> equals <emphasis>document</emphasis>. </para> <para> - Also we can get a table: + The results can also be formatted as a table: </para> <programlisting language="Java" role="Java">String[] columnNames = result.getColumnNames(); Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/not-constraint.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/not-constraint.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/not-constraint.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -5,53 +5,32 @@ ]> <section id="sect-Reference_Guide_eXo_JCR_1.14-NOT_Constraint"> <title>NOT Constraint</title> - <para> - Find all nodes with a mixin type 'mix:title' and where the property 'jcr:title' does NOT start with a 'P' symbol - </para> + <formalpara> + <title>Task:</title> + <para> + Find all nodes with a mixin type <literal>mix:title</literal> and where the property <parameter>jcr:title</parameter> does <emphasis role="bold">not</emphasis> start with a <literal>P</literal> symbol. + </para> + </formalpara> + <section id="sect-Reference_Guide_eXo_JCR_1.14-NOT_Constraint-Repository_Structure"> <title>Repository Structure</title> <para> The repository contains a mix:title nodes, where the jcr:title has different values. </para> - <itemizedlist> - <listitem> - <para> - root - </para> - <itemizedlist> - <listitem> - <para> - document1 (mix:title) jcr:title="Star wars" jcr:description="Dart rules!!" - </para> +<programlisting>root + ├── document1 (mix:title) jcr:title="Star wars" jcr:description="Darth rules!!" + ├── document2 (mix:title) jcr:title="Prison break" jcr:description="Run, Forest, run ))" + └── document3 (mix:title) jcr:title="Panopticum" jcr:description="It's imagine film" +</programlisting> - </listitem> - <listitem> - <para> - document2 (mix:title) jcr:title="Prison break" jcr:description="Run, Forest, run ))" - </para> - - </listitem> - <listitem> - <para> - document3 (mix:title) jcr:title="Panopticum" jcr:description="It's imagine film" - </para> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-NOT_Constraint-Query_execution"> <title>Query execution</title> - <para> - <emphasis role="bold">SQL</emphasis> - </para> - + + <formalpara> + <title>SQL</title> + <para> <programlisting language="Java" role="Java">// make SQL query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -59,10 +38,11 @@ Query query = queryManager.createQuery(sqlStatement, Query.SQL); // execute query and fetch result QueryResult result = query.execute();</programlisting> - <para> - <emphasis role="bold">XPath</emphasis> - </para> - + </para> + </formalpara> + <formalpara> + <title>XPath</title> + <para> <programlisting language="Java" role="Java">// make XPath query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -70,13 +50,15 @@ Query query = queryManager.createQuery(xpathStatement, Query.XPATH); // execute query and fetch result QueryResult result = query.execute();</programlisting> + </para> + </formalpara> </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-NOT_Constraint-Fetching_the_result"> <title>Fetching the result</title> <para> - Let's get the nodes: + To fetch the matching nodes: </para> <programlisting language="Java" role="Java">NodeIterator it = result.getNodes(); @@ -86,10 +68,10 @@ Node findedNode = it.nextNode(); }</programlisting> <para> - NodeIterator will return "document1". + The <literal>NodeIterator</literal> will return <emphasis>document1</emphasis>. </para> <para> - We can also get a table: + The results can also be formatted as a table: </para> <programlisting language="Java" role="Java">String[] columnNames = result.getColumnNames(); Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/spell-checker.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/spell-checker.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/spell-checker.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -5,9 +5,13 @@ ]> <section id="sect-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase"> <title>Checking the spelling of Phrase</title> - <para> - Check the correct spelling of phrase 'quik OR (-foo bar)' according to data already stored in index. - </para> + <formalpara> + <title>Task:</title> + <para> + Check the correct spelling of phrase '<emphasis>quik OR (-foo bar)</emphasis>' according to data already stored in index. + </para> + </formalpara> + <note> <para> Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content" /> for information about SpellChecker configuration. @@ -15,12 +19,10 @@ </note> <para> - SpellChecker must be settled in query-handler config. + The SpellChecker must be set in query-handler configuration. </para> - <para> - test-jcr-config.xml: - </para> - +<example> + <title>test-jcr-config.xml:</title> <programlisting language="XML" role="XML">&lt;query-handler class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex"&gt; &lt;properties&gt; ... @@ -28,41 +30,28 @@ ... &lt;/properties&gt; &lt;/query-handler&gt;</programlisting> +</example> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase-Repository_structure"> <title>Repository structure:</title> <para> Repository contains node, with string property "The quick brown fox jumps over the lazy dog." </para> - <itemizedlist> - <listitem> - <para> - root - </para> - <itemizedlist> - <listitem> - <para> - node1 property="The quick brown fox jumps over the lazy dog." - </para> +<programlisting>root + └── node1 property="The quick brown fox jumps over the lazy dog." +</programlisting> - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase-Query_execution"> <title>Query execution</title> <para> - Query looks only for root node, because spell checker looks for suggestions by full index. So complicated query is redundant. + The query looks only for the <literal>root</literal> node, because the spell checker looks for suggestions by full index. Therefore a complicated query is unecessary. </para> - <para> - <emphasis role="bold">SQL</emphasis> - </para> - + <formalpara> + <title>SQL</title> + <para> <programlisting language="Java" role="Java">// make SQL query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -70,10 +59,11 @@ Query query = queryManager.createQuery(sqlStatement, Query.SQL); // execute query and fetch result QueryResult result = query.execute();</programlisting> - <para> - <emphasis role="bold">XPath</emphasis> - </para> - + </para> + </formalpara> + <formalpara> + <title>XPath</title> + <para> <programlisting language="Java" role="Java">// make XPath query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -81,13 +71,15 @@ Query query = queryManager.createQuery(xpathStatement, Query.XPATH); // execute query and fetch result QueryResult result = query.execute();</programlisting> + </para> + </formalpara> </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase-Fetching_result"> <title>Fetching result</title> <para> - Get suggestion of correct spelling our phrase: + To get suggestions of the correct spelling of the nominated phrase: </para> <programlisting language="Java" role="Java">RowIterator it = result.getRows(); @@ -95,7 +87,7 @@ Value v = r.getValue("rep:spellcheck()"); String correctPhrase = v.getString();</programlisting> <para> - So, correct spelling for phrase "quik OR (-foo bar)" is "quick OR (-fox bar)". + The result would offer "<literal>quick OR (-fox bar)</literal>" as the correct spelling for the phrase "<literal>quik OR (-foo bar)</literal>" . </para> </section> Deleted: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -1,81 +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-eXoJCR"> - <title>Java Content Repository</title> - - <xi:include href="jcr/intro.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- concepts --> - <!-- <xi:include href="jcr/concepts/why-jcr.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> - <xi:include href="jcr/concepts/jcr-exo-implementation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/concepts/jcr-advantages.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/concepts/jcr-compatibility-levels.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/concepts/jcr-usage.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- <xi:include href="jcr/concepts/jcr-extensions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> - <xi:include href="jcr/concepts/jcr-applications.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/concepts/nodetypes-and-namespaces.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/concepts/nodetype-registration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/concepts/jcr-registry-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/concepts/jcr-namespace-altering.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- common configs --> - <xi:include href="jcr/configuration/exo-jcr-configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/configuration/multilanguage-support.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/configuration/search-configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/configuration/configuration-persister.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/configuration/jdbc-data-container-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/configuration/external-value-storages.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/configuration/workspace-persistence-storage.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/configuration/rest-services-on-groovy.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- cluster configs --> - <xi:include href="jcr/cluster-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/jbosscache-configuration-templates.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/lock-manager-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/query-handler-config.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/jbossts-transaction-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/transaction-manager-lookup.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/repository-creation-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <!-- search --> - <xi:include href="jcr/searching/jcr-query-usecases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/searching/searching-repository-content.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/searching/fulltext-search-and-settings.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- api extensions --> - <xi:include href="jcr/api-extensions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- protocols --> - <xi:include href="jcr/protocols/webdav.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/protocols/ftp.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- backup --> - <xi:include href="jcr/backup/exojcr-backup-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/backup/backup-client.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/backup/use-external-backup-tool.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- other --> - <xi:include href="jcr/statistics.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/repository-check-controller.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/jta.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/jca.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/other/acl.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/other/acl-ext.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/other/link-producer.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/other/binary-values-processing.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jcr/other/jcr-resources.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - - <!-- data container configs --> - <xi:include href="jcr/data-container.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <!-- <xi:include href="jcr/data-container-howto.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> - <xi:include href="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="jcr/performance-tuning-guide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -</section> - - Modified: 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-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -4,9 +4,83 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Reference_Guide_eXo_JCR_1.14-eXo_JCR"> - <title><remark>eXo JCR</remark> - </title> - <xi:include href="eXoJCR/jcr.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <title>eXo JCR</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" /> + + + <!--#####################################################################################--> + + <xi:include href="eXoJCR/core.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="eXoJCR/ws.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="eXoJCR/jcr-with-gatein.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -4,7 +4,7 @@ %BOOK_ENTITIES; ]> <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On"> - <title><remark>SSO - Single Sign On</remark></title> + <title>SSO - Single Sign On</title> <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On-Overview"> <title>Overview</title> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/PortletDevelopment/Global_Portlet.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/PortletDevelopment/Global_Portlet.xml 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/PortletDevelopment/Global_Portlet.xml 2011-11-16 04:52:13 UTC (rev 8079) @@ -4,7 +4,7 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Reference_Guide_eXo_JCR_1.14-Shared_portlet.xml"> - <title><remark>Shared <filename>portlet.xml</filename></remark></title> + <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. @@ -91,15 +91,15 @@ With the XML configuration below, the filter <literal>ApplicationMonitoringFilter</literal> involves in request handling on any deployed portlet. </para> -<programlisting role="XML" language="XML"><![CDATA[<filter> -<filter-name>org.exoplatform.portal.application.ApplicationMonitoringFilter</filter-name> -<filter-class>org.exoplatform.portal.application.ApplicationMonitoringFilter</filter-class> - <lifecycle>ACTION_PHASE</lifecycle> - <lifecycle>RENDER_PHASE</lifecycle> - <lifecycle>EVENT_PHASE</lifecycle> - <lifecycle>RESOURCE_PHASE</lifecycle> -</filter> -]]></programlisting> +<programlisting role="XML" language="XML"><![CDATA[<filter> +<filter-name>org.exoplatform.portal.application.ApplicationMonitoringFilter</filter-name> +<filter-class>org.exoplatform.portal.application.ApplicationMonitoringFilter</filter-class> + <lifecycle>ACTION_PHASE</lifecycle> + <lifecycle>RENDER_PHASE</lifecycle> + <lifecycle>EVENT_PHASE</lifecycle> + <lifecycle>RESOURCE_PHASE</lifecycle> +</filter> +]]></programlisting> <para> <emphasis role="bold">Application Monitoring Filter</emphasis> supports four lifecycle phases in the order below: </para> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/publican.cfg =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/publican.cfg 2011-11-16 02:48:49 UTC (rev 8078) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/publican.cfg 2011-11-16 04:52:13 UTC (rev 8079) @@ -3,7 +3,7 @@ cvs_root: ":ext:cvs.devel.redhat.com:/cvs/dist" cvs_branch: "DOCS-RHEL-6" -show_remarks: 1 +#show_remarks: 1 cvs_pkg: "JBoss_Enterprise_Portal_Platform-Reference_Guide_eXo_JCR_1.14-5.2-web-__LANG__" xml_lang: "en-US" brand: JBoss