Author: smumford Date: 2011-03-11 00:43:02 -0500 (Fri, 11 Mar 2011) New Revision: 6005 Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/Common_Content/Conventions.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/Foundations.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/cluster-config.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/configuration-persister.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/intro.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/jbosscache-configuration-templates.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/multilanguage-support.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/search-configuration.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/statistics.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/OrganizationAPI.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PredefinedUserConfiguration.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Configuration/DatabaseConfiguration.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Configuration/EMailServiceConfiguration.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Introduction.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortalDevelopment/LocalizationConfiguration.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/overview.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/portlet_development.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/WSRP.xml Log: Committing aspell corrections Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/Common_Content/Conventions.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/Common_Content/Conventions.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/Common_Content/Conventions.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -49,7 +49,7 @@ </para> <blockquote> <para> - File-related classes include <classname>filesystem</classname> for file systems, <classname>file</classname> for files, and <classname>dir</classname> for directories. Each class has its own associated set of permissions. + File-related classes include <classname>file system</classname> for file systems, <classname>file</classname> for files, and <classname>dir</classname> for directories. Each class has its own associated set of permissions. </para> </blockquote> <para> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/Foundations.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/Foundations.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/Foundations.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -8,7 +8,7 @@ <section id="sect-Reference_Guide-Foundations-The_eXo_Kernel"> <title>The eXo Kernel</title> <para> - &PRODUCT; is built as a set of services on top of a dependency injection kernel. The kernel provides configuration, lifecycle handling, component scopes, and some core services. + &PRODUCT; is built as a set of services on top of a dependency injection kernel. The kernel provides configuration, life-cycle handling, component scopes, and some core services. </para> <para> Service components exist in two scopes. The first scope is represented by the <literal>RootContainer</literal>. It contains services that exist independently of any portal, and can be accessed by all portals. @@ -84,7 +84,7 @@ <section id="sect-Reference_Guide-Configuration_syntax-External_Plugins"> - <title>External Plugins</title> + <title>External Plug-ins</title> <para> The eXo Kernel supports non-component objects that can be configured, instantiated, and injected into registered components using method calls. This &#39;<emphasis>plugin</emphasis>&#39; method allows portal extensions to add additional configurations to core services. </para> @@ -140,7 +140,7 @@ </para> </note> <para> - Through the extension mechanism the servlet context used for resource loading is a <emphasis role="bold">unified servlet context</emphasis> (this is explaned in a later section). + Through the extension mechanism the servlet context used for resource loading is a <emphasis role="bold">unified servlet context</emphasis> (this is explained in a later section). </para> <para> To have an &#39;include&#39; path resolved relative to current classpath (context classloader), use a <code>&#39;jar:&#39;</code> URL schema. Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/cluster-config.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/cluster-config.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/cluster-config.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -15,7 +15,7 @@ <procedure> <step> <para> - Dowload the latest version of the eXo JCR <filename>ear</filename> distribution. + Download the latest version of the eXo JCR <filename>ear</filename> distribution. </para> </step> <step> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/configuration-persister.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/configuration-persister.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/configuration-persister.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -21,7 +21,7 @@ <section id="sect-Reference_Guide-The_JCR_Configuration_persister-Usage"> <title>Usage</title> <para> - On startup, the <classname>RepositoryServiceConfiguration</classname> component checks if a configuration persister has been configured. + On start up, the <classname>RepositoryServiceConfiguration</classname> component checks if a configuration persister has been configured. </para> <para> It one has been, it uses the provided <classname>ConfigurationPersister</classname> implementation class to instantiate the persister object. @@ -67,7 +67,7 @@ The JCR Core implementation contains a persister which stores the repository configuration in the relational database using JDBC calls (<classname>org.exoplatform.services.jcr.impl.config.JDBCConfigurationPersister</classname>). </para> <para> - The implementation will create and use the table <parameter>JCR_CONFIG</parameter> in the provided database. However, a developer can implement another persister for any particular usecase. + The implementation will create and use the table <parameter>JCR_CONFIG</parameter> in the provided database. However, a developer can implement another persister for any particular use case. </para> </section> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -94,7 +94,7 @@ </listitem> <listitem> <para> - <emphasis role="bold">T</emphasis> or <emphasis role="bold">TB</emphasis> for terraBytes. + <emphasis role="bold">T</emphasis> or <emphasis role="bold">TB</emphasis> for terabytes. </para> </listitem> <listitem> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/intro.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/intro.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/intro.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -18,7 +18,7 @@ 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 5.1 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 backend storage of the JCR is configurable and can be a file system or a database. + The eXo JCR included with JBoss Enterprise Portal Platform 5.1 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-Introduction-Concepts"> <title>Concepts</title> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/jbosscache-configuration-templates.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/jbosscache-configuration-templates.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/jbosscache-configuration-templates.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -85,7 +85,7 @@ <section id="sect-Reference_Guide-JBoss_Cache_configuration-JGroups_configuration"> <title>JGroups configuration</title> <para> - JGroups is used by JBoss Cache for network communications and transport in a clustered environment. If the property &#34;<parameter>jgroups-configuration</parameter>&#34; is defined in the component configuration, it will be injected into the JBoss Cache instance on startup. + JGroups is used by JBoss Cache for network communications and transport in a clustered environment. If the property &#34;<parameter>jgroups-configuration</parameter>&#34; is defined in the component configuration, it will be injected into the JBoss Cache instance on start up. </para> <programlisting language="XML" role="XML">&#60;property name=&#34;jgroups-configuration&#34; value=&#34;your/path/to/modified-udp.xml&#34; /&#62; Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -223,7 +223,7 @@ A more detailed configuration of the database is possible through editing the metadata SQL-script files. </para> <para> - If the non-ANSI node name is used, a database with MultiLanguage support is required (refer to <xref linkend="sect-Reference_Guide-Multilanguage_support_in_eXo_JCR_RDB_backend" /> for more information). + If the non-ANSI node name is used, a database with Multilingual support is required (refer to <xref linkend="sect-Reference_Guide-Multilanguage_support_in_eXo_JCR_RDB_backend" /> for more information). </para> <para> Some JDBC drivers need additional parameters for establishing a Unicode friendly connection. @@ -487,7 +487,7 @@ </listitem> </itemizedlist> <para> - The dialect can also be set to &#34;auto&#34; to allow dialect autodetection. + The dialect can also be set to &#34;auto&#34; to allow dialect auto-detection. </para> </listitem> </varlistentry> @@ -561,7 +561,7 @@ &#60;container class=&#34;org.exoplatform.services.jcr.impl.storage.jdbc.JDBCWorkspaceDataContainer&#34;&#62; ... &#60;/workspace&#62; -&#60;/worksapces&#62;</programlisting> +&#60;/workspaces&#62;</programlisting> <para> Simple queries are implemented in such a way so as to support as many database dialects as possible. They do not use sub queries, or left or right joins. </para> @@ -574,7 +574,7 @@ &#60;container class=&#34;org.exoplatform.services.jcr.impl.storage.jdbc.optimisation.CQJDBCWorkspaceDataContainer&#34;&#62; ... &#60;/workspace&#62; -&#60;/worksapces&#62;</programlisting> +&#60;/workspaces&#62;</programlisting> <para> Complex queries are optimized to reduce the number of requests made to a database. </para> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -39,7 +39,7 @@ The LockManager in &PRODUCT; is implemented with <classname>org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl</classname>. </para> <para> - It is is enabled by adding <literal>lock-manager-configuration</literal> to <literal>workspace-configuration</literal>. + It is enabled by adding <literal>lock-manager-configuration</literal> to <literal>workspace-configuration</literal>. </para> <para> For example: Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/multilanguage-support.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/multilanguage-support.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/multilanguage-support.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -4,10 +4,10 @@ %BOOK_ENTITIES; ]> <section id="sect-Reference_Guide-Multilanguage_support_in_eXo_JCR_RDB_backend"> - <title>Multilanguage support in eXo JCR RDB backend</title> + <title>Multi-language support in eXo JCR RDB back end</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 fof failure, see below. + 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. @@ -51,7 +51,7 @@ <section id="sect-Reference_Guide-Multilanguage_support_in_eXo_JCR_RDB_backend-Oracle"> <title>Oracle</title> <para> - In order to run a multi-language instance of JCR on an Oracle backend, Unicode encoding should be applied to the database. + In order to run a multi-language instance of JCR on an Oracle back end, Unicode encoding should be applied to the database. </para> <para> To create a database with Unicode encoding using Oracle dialect for the Workspace Container, implement the following settings: @@ -89,7 +89,7 @@ <section id="sect-Reference_Guide-Multilanguage_support_in_eXo_JCR_RDB_backend-MySQL"> <title>MySQL</title> <para> - Using JCR with a MySQL-backend requires a special dialect <ulink url="http://jira.exoplatform.org/browse/JCR-375">MySQL-UTF8&... to be used for internationalization support. + Using JCR with a MySQL-back end requires a special dialect <ulink url="http://jira.exoplatform.org/browse/JCR-375">MySQL-UTF8&... 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>). @@ -98,7 +98,7 @@ 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 singlebyte default charset of database, with UTF8 supported by MySQL server. However it has only been tested using the <parameter>latin1</parameter> charset. + 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: @@ -111,7 +111,7 @@ <section id="sect-Reference_Guide-Multilanguage_support_in_eXo_JCR_RDB_backend-PostgreSQL"> <title>PostgreSQL</title> <para> - Multilingual support can be enabled with a PostgreSQL-backend in <ulink url="http://www.postgresql.org/docs/8.3/interactive/charset.html&quo... ways</ulink>: + Multilingual support can be enabled with a PostgreSQL-back end in <ulink url="http://www.postgresql.org/docs/8.3/interactive/charset.html&quo... ways</ulink>: </para> <orderedlist> <listitem> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -102,7 +102,7 @@ </callout> <callout arearefs="area-Reference_Guide-QueryHandler_configuration-Configuration-jgroups-multiplexer-stack"> <para> - When the <parameter>jgroups-multiplexer-stack</parameter> property is set to <emphasis>true</emphasis> (and appropriate <parameter>jgroups-configuration</parameter> paramters are set) then Multiplexing stack is enabled in JBoss Cache. + When the <parameter>jgroups-multiplexer-stack</parameter> property is set to <emphasis>true</emphasis> (and appropriate <parameter>jgroups-configuration</parameter> parameters are set) then Multiplexing stack is enabled in JBoss Cache. </para> </callout> <callout arearefs="area-Reference_Guide-QueryHandler_configuration-Configuration-jbosscache-cluster-name"> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/search-configuration.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/search-configuration.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/search-configuration.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -183,7 +183,7 @@ </entry> <entry> <para> - The number of words that are fulltext indexed at most per property. + The number of words that are full-text indexed at most per property. </para> </entry> <entry> @@ -203,7 +203,7 @@ </entry> <entry> <para> - Size of the document number cache. This cache maps uuids to lucene document numbers + Size of the document number cache. This cache maps UUID to lucene document numbers </para> </entry> <entry> @@ -223,7 +223,7 @@ </entry> <entry> <para> - Runs a consistency check on every startup. If false, a consistency check is only performed when the search index detects a prior forced shutdown. + Runs a consistency check on every start up. If false, a consistency check is only performed when the search index detects a prior forced shutdown. </para> </entry> <entry> @@ -448,7 +448,7 @@ </entry> <entry> <para> - If set to true a consistency check is performed depending on the parameter <literal>forceConsistencyCheck</literal>. If set to false no consistency check is performed on startup, even if a redo log had been applied. + If set to true a consistency check is performed depending on the parameter <literal>forceConsistencyCheck</literal>. If set to false no consistency check is performed on start up, even if a redo log had been applied. </para> </entry> <entry> @@ -528,7 +528,7 @@ On subsequent starts this option is no longer needed. The old index is replaced and a back conversion is not possible </para> <para> - It is reccommended that a backup of the index be made before conversion. (Only for migrations from JCR 1.9 and later.) + It is recommended that a backup of the index be made before conversion. (Only for migrations from JCR 1.9 and later.) </para> </entry> <entry> @@ -548,7 +548,7 @@ </entry> <entry> <para> - Class name of a lucene analyzer to use for fulltext indexing of text. + Class name of a lucene analyzer to use for full-text indexing of text. </para> </entry> <entry> @@ -756,7 +756,7 @@ <formalpara id="form-Reference_Guide-IndexingConfiguration-Exclusion_from_the_Node_Scope_Index"> <title>Exclusion from the Node Scope Index</title> <para> - All configured properties are fulltext indexed by default (if they are of type STRING and included in the node scope index). + All configured properties are full-text indexed by default (if they are of type STRING and included in the node scope index). </para> </formalpara> <para> @@ -788,7 +788,7 @@ <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> wildcard can be used to match all child nodes: + 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> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/statistics.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/statistics.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/statistics.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -44,7 +44,7 @@ </listitem> </itemizedlist> <para> - Those figures are also available globaly for all the methods which gives us the global behavior of this layer. + Those figures are also available globally for all the methods which gives us the global behavior of this layer. </para> <para> To enable the statistics, the JVM parameter called <emphasis>JDBCWorkspaceDataContainer.statistics.enabled</emphasis> must be set to <emphasis>true</emphasis>. The corresponding CSV file is <filename>StatisticsJDBCStorageConnection-${creation-timestamp}.csv</filename>. Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -128,7 +128,7 @@ </callout> <callout arearefs="area-Reference_Guide-PicketLink_IDM_integration-Configuration_files-JBossIDMOrganizationServiceImpl"> <para> - The <emphasis role="bold">org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl</emphasis> key is a main entrypoint implementing <emphasis role="bold">org.exoplatform.services.organization.OrganizationService</emphasis> and is dependant on <emphasis role="bold">org.exoplatform.services.organization.idm.PicketLinkIDMService</emphasis> + The <emphasis role="bold">org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl</emphasis> key is a main entrypoint implementing <emphasis role="bold">org.exoplatform.services.organization.OrganizationService</emphasis> and is dependent on <emphasis role="bold">org.exoplatform.services.organization.idm.PicketLinkIDMService</emphasis> </para> <para> The <emphasis role="bold">org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl</emphasis> service has the following options defined as fields of <parameter>object-param</parameter> of type <emphasis role="bold">org.exoplatform.services.organization.idm.Config</emphasis>: Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/OrganizationAPI.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/OrganizationAPI.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/OrganizationAPI.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -100,7 +100,7 @@ The five central API components are designed to be similar to persistent entities and handlers are specified similarly to data access objects (DAO). </para> <para> - <emphasis>Organization API</emphasis> simply describes a contract, meaning it is not a concrete implementation. The described components are interfaces, allowing for different concrete implementations. In practial terms the existing implementation can be replaced with a different one. + <emphasis>Organization API</emphasis> simply describes a contract, meaning it is not a concrete implementation. The described components are interfaces, allowing for different concrete implementations. In practical terms the existing implementation can be replaced with a different one. </para> </section> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PredefinedUserConfiguration.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PredefinedUserConfiguration.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PredefinedUserConfiguration.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -9,7 +9,7 @@ <section id="sect-Reference_Guide-Predefined_User_Configuration-Overview"> <title>Overview</title> <para> - The initial Organization configuration should be specified by editing the content of <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>&lt;PROFILE&gt;</replaceable>/deploy/gatein.ear/02portal.war:/WEB-INF/conf/organization/organization-configuration.xml</filename>. This file uses the portal XML configuration schema. It lists several configuration plugins. + The initial Organization configuration should be specified by editing the content of <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>&lt;PROFILE&gt;</replaceable>/deploy/gatein.ear/02portal.war:/WEB-INF/conf/organization/organization-configuration.xml</filename>. This file uses the portal XML configuration schema. It lists several configuration plug-ins. </para> </section> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -17,7 +17,7 @@ There are many different Identity Management solutions available. In most cases each SSO framework provides a unique way to plug into a Java EE application. </para> <para> - This section will cover the implemenation of four different SSO plugins with &PRODUCT;: + This section will cover the implementation of four different SSO plug-ins with &PRODUCT;: </para> <itemizedlist> <listitem> @@ -549,7 +549,7 @@ </step> <step> <para> - Login as <literal>amadmin</literal>. + Login as <literal>admin</literal>. </para> <important> <para> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Configuration/DatabaseConfiguration.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Configuration/DatabaseConfiguration.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Configuration/DatabaseConfiguration.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -50,7 +50,7 @@ Note that some databases don&#39;t accept &#39;-&#39; in the database name, so you may have to remove <filename><replaceable>JBOSS_AS</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein-sample-portal.ear</filename>) </para> <para> - Make sure the user has rights to create tables on jdbcjcr_portal, and to update them as they will be automatically created during the first startup . + Make sure the user has rights to create tables on jdbcjcr_portal, and to update them as they will be automatically created during the first start up . </para> <para> Also add your database&#39;s JDBC driver into the classpath - you can put it in <replaceable>JBOSS_AS</replaceable>/server/<replaceable>PROFILE</replaceable>/lib (or <replaceable>TOMCAT_HOME</replaceable>/lib, if you are running on Tomcat) Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Configuration/EMailServiceConfiguration.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Configuration/EMailServiceConfiguration.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Configuration/EMailServiceConfiguration.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -33,7 +33,7 @@ gatein.email.smtp.socketFactory.class=javax.net.ssl.SSLSocketFactory </programlisting> <para> - It is preconfigured for GMail, so that any GMail account can easily be used (simply use the full GMail address as username, and fill-in the password. + It is pre-configured for GMail, so that any GMail account can easily be used (simply use the full GMail address as username, and fill-in the password. </para> <para> In corporate environments you will want to use your corporate SMTP gateway. When using it over SSL, like in default configuration, you may need to configure a certificate truststore, containing your SMTP server&#39;s public certificate. Depending on the key sizes, you may then also need to install Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files for your Java Runtime Environment. Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Introduction.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Introduction.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Introduction.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -23,7 +23,7 @@ <title>Related Links</title> <variablelist> <varlistentry> - <term>Tecnical documentation</term> + <term>Technical documentation</term> <listitem> <para> Other technical documentation, including an <emphasis role="bold">Installation Guide</emphasis>, and a <emphasis role="bold">User Guide</emphasis> can be found at <ulink type="http" url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platfo... Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -12,7 +12,7 @@ Managing Javascript scripts in an application like &PRODUCT; is a critical part of the configuration work. Configuring the scripts correctly will result in a faster response time from the portal. </para> <para> - Every portlet can have its own javscript code but in many cases it is more convenient to reuse some existing shared libraries. For that reason, &PRODUCT; has a mechanism to easily register the libraries that will be loaded when the first page is rendered. + Every portlet can have its own javascript code but in many cases it is more convenient to reuse some existing shared libraries. For that reason, &PRODUCT; has a mechanism to easily register the libraries that will be loaded when the first page is rendered. </para> <para> To do so, every WAR deployed in &PRODUCT; can register the <filename>.js</filename> files with the groovy script <filename>WEB-INF/conf/script/groovy/JavascriptScript.groovy</filename>. @@ -45,7 +45,7 @@ To see or use the merged file set this property to <literal>false</literal>. </para> <para> - The property can be passed as a JVM parameter with the <literal>-D</literal> option in your <literal>run.sh</literal> or <literal>run.bat</literal> startup script. + The property can be passed as a JVM parameter with the <literal>-D</literal> option in your <literal>run.sh</literal> or <literal>run.bat</literal> start-up script. </para> <para> Every javascript file is associated with a module name which acts as a namespace. The module name is passed as a first parameter to <literal>JavascriptService.addJavascript()</literal> function as in the following example: Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortalDevelopment/LocalizationConfiguration.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortalDevelopment/LocalizationConfiguration.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortalDevelopment/LocalizationConfiguration.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -71,8 +71,8 @@ <title>Default <literal>LocalePolicy</literal></title> <para> By default, <literal>org.exoplatform.portal.application.localization.DefaultLocalePolicyService</literal>, an implementation - of <literal>LocalePolicy</literal>, is installed to provide the default behaviour. - This, however, can easily be extended and overriden. A completely new implementation can also be written from scratch. + of <literal>LocalePolicy</literal>, is installed to provide the default behavior. + This, however, can easily be extended and overridden. A completely new implementation can also be written from scratch. </para> <para> <literal>DefaultLocalePolicyService</literal> treats logged-in users slightly differently than anonymous users. Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -31,7 +31,7 @@ <term>Window Styles</term> <listitem> <para> - The CSS styles associated with the porlet window decorators. The window decorators contain the control buttons and borders surrounding each portlet. Individual portlets can have their own window decorator selected or be rendered without one. + The CSS styles associated with the portlet window decorators. The window decorators contain the control buttons and borders surrounding each portlet. Individual portlets can have their own window decorator selected or be rendered without one. </para> </listitem> </varlistentry> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -36,7 +36,7 @@ If the request is for a non-JSF resource, the bridge handles the request by acquiring a request dispatcher and forwarding the request to the named resource. </para> <para> - If the request is for a JSF resource, the bridge runs the full JSF lifecycle ensuring that data is processed and the resource (markup) is rendered. + If the request is for a JSF resource, the bridge runs the full JSF life-cycle ensuring that data is processed and the resource (markup) is rendered. </para> <para> See <xref linkend="sect-Reference_Guide-Portlet_2.0_Coordination-Serving_Your_JSF_Resources_in_a_Portlet" /> for details and examples. Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/overview.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/overview.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/overview.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -33,7 +33,7 @@ Part of this implementation acts as a <literal>Faces</literal> controller much as the FacesServlet does in the direct client request environment. </para> <para> - The other part of this implementation is provided by implementating a variety of (standard) <literal>Faces</literal> extensions. + The other part of this implementation is provided by implementing a variety of (standard) <literal>Faces</literal> extensions. </para> <important> <title>Disclaimer</title> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/portlet_development.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/portlet_development.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/portlet_development.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -14,7 +14,7 @@ When your application uses request attributes on a per request basis and you do not want that particular attribute to be managed in the extended bridge request scope, you must use the following configuration in your <filename>faces-config.xml</filename>. </para> <para> - In the code sample below you can see that any attribute namespaced as <literal>foo.bar</literal> or any attribute beginning with <literal>foo.baz(wildcard)</literal> will be excluded from the bridge request scope and only be used per that application&#39;s request. + In the code sample below you can see that any attribute namespaced as <literal>foo.bar</literal> or any attribute beginning with <literal>foo.baz(wild-card)</literal> will be excluded from the bridge request scope and only be used per that application&#39;s request. </para> <programlisting language="XML" role="XML"><xi:include href="../../../extras/PortletBridge_Portlet_Development/default223.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> @@ -57,7 +57,7 @@ <section id="sect-Reference_Guide-Navigating_to_a_modes_last_viewId-Note_to_Portlet_Developers"> <title>Note to Portlet Developers</title> <para> - Depending on the bridge implementation, when using values from these session scoped attributes or any viewIds which may contain query string parameters it may be necessary to use the wildcard syntax when identifying the rule target. In the above, for example, the + Depending on the bridge implementation, when using values from these session scoped attributes or any viewIds which may contain query string parameters it may be necessary to use the wild-card syntax when identifying the rule target. In the above, for example, the </para> <programlisting language="XML" role="XML">&#60;to-view-id&#62; @@ -69,20 +69,20 @@ <programlisting language="XML" role="XML">/viewId?javax.portlet.faces.PortletMode=view&amp;.... </programlisting> <para> - Without wildcarding, when a subsequent navigation occurs from this new view, the navigation rules wouldn&#39;t resolve because there wouldn&#39;t be an exact match. Likewise, the above <literal>edit.jspx</literal> + Without wild-carding, when a subsequent navigation occurs from this new view, the navigation rules wouldn&#39;t resolve because there wouldn&#39;t be an exact match. Likewise, the above <literal>edit.jspx</literal> </para> <programlisting language="XML" role="XML">&#60;from-view-id&#62; </programlisting> <para> - is wildcarded because there are navigation rules that target it that use a query string: + is wild-carded because there are navigation rules that target it that use a query string: </para> <programlisting language="XML" role="XML"> &#60;to-view-id&#62; /edit.jspx?javax.portlet.faces.PortletMode=edit &#60;/to-view-id&#62; </programlisting> <para> - Developers are encouraged to use such wildcarding to ensure they execute properly in the broadest set of bridge implementations. + Developers are encouraged to use such wild-carding to ensure they execute properly in the broadest set of bridge implementations. </para> </section> Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -284,7 +284,7 @@ <section id="sect-Reference_Guide-Deploying_your_first_Portlet-Application_Descriptors"> <title>Application Descriptors</title> <para> - &PRODUCT; requires certain descriptors to be included in a portlet <literal>WAR</literal> file. These descriptors are defined by the Jave EE (<filename>web.xml</filename>) and Portlet Specification (<filename>portlet.xml</filename>). + &PRODUCT; requires certain descriptors to be included in a portlet <literal>WAR</literal> file. These descriptors are defined by the Java EE (<filename>web.xml</filename>) and Portlet Specification (<filename>portlet.xml</filename>). </para> <para> Below is an example of the <filename>SimplestHelloWorldPortlet/WEB-INF/portlet.xml</filename> file. This file must adhere to its definition in the JSR-286 Portlet Specification. More than one portlet application may be defined in this file: Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/WSRP.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/WSRP.xml 2011-03-10 15:46:21 UTC (rev 6004) +++ epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/WSRP.xml 2011-03-11 05:43:02 UTC (rev 6005) @@ -47,7 +47,7 @@ &PRODUCT; provides a <emphasis>Medium</emphasis> level of support for the Consumer, excepting HTML markup (as &PRODUCT; itself does not handle other markup types). Explicit portlet cloning and the <literal>PortletManagement</literal> interface are supported. </para> <para> - The WSRP component has Level 1 Producer and Consumer caching. Cookie handling is supported properly on the Consumer. The Producer requires cookie initialization (as this improves interoperabilty with some consumers). + The WSRP component has Level 1 Producer and Consumer caching. Cookie handling is supported properly on the Consumer. The Producer requires cookie initialization (as this improves interoperability with some consumers). </para> <para> &PRODUCT; does not support custom window states or modes, therefore neither does the WSRP component. It does, however, support CSS on both the Producer (although this is more a function of the portlets than an inherent Producer capability) and Consumer. @@ -527,7 +527,7 @@ <section id="sect-Reference_Guide-Configuring_a_Remote_Producer-Adding_remote_portlets_to_categories"> <title>Adding remote portlets to categories</title> <para> - Clicking on the Portlet link in the Application Registry will now show the remote potlets in the <emphasis role="bold">REMOTE</emphasis> tab in the left column: + Clicking on the Portlet link in the Application Registry will now show the remote portlets in the <emphasis role="bold">REMOTE</emphasis> tab in the left column: </para> <mediaobject> <imageobject role="html"> @@ -740,7 +740,7 @@ </step> <step> <para> - Click on <emphasis role="bold">Modify registration</emphasis> and, if the updated registration details have been been accepted by the remote producer the following should appear: + Click on <emphasis role="bold">Modify registration</emphasis> and, if the updated registration details have been accepted by the remote producer the following should appear: </para> <mediaobject> <imageobject role="html"> @@ -867,7 +867,7 @@ <term>Register/De-register</term> <listitem> <para> - Registers or deregisters a consumer based on whether registration is required and/or acquired. + Registers or de-registers a consumer based on whether registration is required and/or acquired. </para> </listitem> </varlistentry> @@ -1305,7 +1305,7 @@ Note that the our validation algorithm is only relaxed on aspects of the specification that are deemed harmless such as invalid language codes. </para> <para> - By default, the WSRP producer is configured in strict mode. If you experience issues with a given consumer, you may attempt to relax the validation mode. Unchecking the "Use strict WSRP compliance" checkbox on the Producer configuration screen to do this. + By default, the WSRP producer is configured in strict mode. If you experience issues with a given consumer, you may attempt to relax the validation mode. Un-checking the "Use strict WSRP compliance" checkbox on the Producer configuration screen to do this. </para> </section>