[gatein-commits] gatein SVN: r2906 - in portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules: PortalDevelopment and 1 other directory.

Author: smumford Date: 2010-04-29 19:59:46 -0400 (Thu, 29 Apr 2010) New Revision: 2906 Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/cluster-config.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/configuration-persister.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/external-value-storages.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalPermissionConfiguration.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml Log: JBEPP-276: publican clean_ids, minor xml coding, some image work Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/cluster-config.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/cluster-config.xml 2010-04-29 23:05:07 UTC (rev 2905) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/cluster-config.xml 2010-04-29 23:59:46 UTC (rev 2906) @@ -113,7 +113,7 @@ &lt;property name="swap-directory" value="../temp/swap/production" /&gt; &lt;/properties&gt; &lt;value-storages&gt; - see "<link linkend="list-Reference_Guide-conf_value_storage">Value storage configuration</link>" part. + <emphasis>(See item 1 in the list in <xref linkend="sect-Reference_Guide-Requirements-Environment_requirements"/>)</emphasis> &lt;/value-storages&gt; &lt;/container&gt; &lt;initializer class="org.exoplatform.services.jcr.impl.core.ScratchWorkspaceInitializer"&gt; @@ -122,13 +122,13 @@ &lt;/properties&gt; &lt;/initializer&gt; &lt;cache enabled="true" class="org.exoplatform.services.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache"&gt; - see "<link linkend="list-Reference_Guide-conf_cache">Cache configuration</link>" part. + <emphasis>(See item 2 in the list in <xref linkend="sect-Reference_Guide-Requirements-Environment_requirements"/>)</emphasis> &lt;/cache&gt; &lt;query-handler class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex"&gt; - see "<link linkend="list-Reference_Guide-conf_indexer">Indexer configuration</link>" part. + <emphasis>(See item 3 in the list in <xref linkend="sect-Reference_Guide-Requirements-Environment_requirements"/>)</emphasis> &lt;/query-handler&gt; &lt;lock-manager class="org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl"&gt; - see "<link linkend="list-Reference_Guide-conf_lock_manager">Lock Manager configuration</link>" part. + <emphasis>(See item 4 in the list in <xref linkend="sect-Reference_Guide-Requirements-Environment_requirements"/>)</emphasis> &lt;/lock-manager&gt; &lt;/workspace&gt; &lt;workspace name="ws2"&gt; @@ -192,8 +192,8 @@ <para> Configuration of every workspace in repository must contains of such parts: </para> - <itemizedlist> - <listitem id="list-Reference_Guide-conf_value_storage"> + <orderedlist> + <listitem> <para> Value Storage configuration: </para> @@ -267,7 +267,8 @@ &lt;/lock-manager&gt; </programlisting> </listitem> - </itemizedlist> + </orderedlist> + </section> </section> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/configuration-persister.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/configuration-persister.xml 2010-04-29 23:05:07 UTC (rev 2905) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/configuration-persister.xml 2010-04-29 23:59:46 UTC (rev 2906) @@ -66,12 +66,12 @@ <itemizedlist> <listitem> <para> - <parameter>source-name</parameter> - JNDI source name configured in <classname>InitialContextInitializer</classname> component. (<parameter>sourceName</parameter> prior v.1.9.) Find more in <link linkend="sect-Reference_Guide-eXo_JCR_configuration">database configuration</link>. + <parameter>source-name</parameter> - JNDI source name configured in <classname>InitialContextInitializer</classname> component. (<parameter>sourceName</parameter> prior v.1.9.) Find more in <xref linkend="sect-Reference_Guide-eXo_JCR_configuration"/>. </para> </listitem> <listitem> <para> - <parameter>dialect</parameter> - SQL dialect which will be used with database from <parameter>source-name</parameter>. Find more in <link linkend="sect-Reference_Guide-eXo_JCR_configuration">database configuration</link>. + <parameter>dialect</parameter> - SQL dialect which will be used with database from <parameter>source-name</parameter>. Find more in <xref linkend="sect-Reference_Guide-eXo_JCR_configuration"/>. </para> </listitem> <listitem> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml 2010-04-29 23:05:07 UTC (rev 2905) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml 2010-04-29 23:59:46 UTC (rev 2906) @@ -10,17 +10,17 @@ <itemizedlist> <listitem> <para> - <link linkend="sect-Reference_Guide-Search_Configuration">Search Configuration</link> + <xref linkend="sect-Reference_Guide-Search_Configuration"/> </para> </listitem> <listitem> <para> - <link linkend="sect-Reference_Guide-JDBC_Data_Container_Config">JDBC Data Container config</link> + <xref linkend="sect-Reference_Guide-JDBC_Data_Container_Config"/> </para> </listitem> <listitem> <para> - <link linkend="sect-Reference_Guide-External_Value_Storages">External Value Storages</link> + <xref linkend="sect-Reference_Guide-External_Value_Storages"/> </para> </listitem> </itemizedlist> @@ -234,164 +234,361 @@ &lt;/repositories&gt; &lt;/repository-service&gt; </programlisting> - <para> - Repository Service configuration: - </para> - <para> - default-repository - the name of a default repository (one returned by RepositoryService.getRepository()) - </para> - <para> - repositories - the list of repositories - </para> - <para> - Repository configuration: - </para> - <para> - name - the name of a repository - </para> - <para> - default-workspace - the name of a workspace obtained using Session's login() or login(Credentials) methods (ones without an explicit workspace name) - </para> - <para> - system-workspace - name of workspace where /jcr:system node is placed - </para> - <para> - security-domain - the name of a security domain for JAAS authentication - </para> - <para> - access-control - the name of an access control policy. There can be 3 types: optional - ACL is created on-demand(default), disable - no access control, mandatory - an ACL is created for each added node(not supported yet) - </para> - <para> - authentication-policy - the name of an authentication policy class - </para> - <para> - workspaces - the list of workspaces - </para> - <para> - session-max-age - the time after which an idle session will be removed (called logout). If not set, the idle session will never be removed. - </para> - <para> - Workspace configuration: - </para> - <para> - name - the name of a workspace - </para> - <para> - auto-init-root-nodetype - DEPRECATED in JCR 1.9 (use initializer). The node type for root node initialization - </para> - <para> - container - workspace data container (physical storage) configuration - </para> - <para> - initializer - workspace initializer configuration - </para> - <para> - cache - workspace storage cache configuration - </para> - <para> - query-handler - query handler configuration - </para> - <para> - Workspace data container configuration: - </para> - <para> - class - A workspace data container class name - </para> - <para> - properties - the list of properties (name-value pairs) for the concrete Workspace data container - </para> - <para> - value-storages - the list of value storage plugins - </para> - <para> - Value Storage plugin configuration (optional feature): - </para> + + <variablelist> + <title>Repository Service configuration:</title> + <varlistentry> + <term>default-repository</term> + <listitem> + <para> + The name of a default repository (one returned by RepositoryService.getRepository()) + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>repositories</term> + <listitem> + <para> + The list of repositories. + </para> + </listitem> + </varlistentry> + </variablelist> + + <variablelist> + <title>Repository configuration:</title> + <varlistentry> + <term>name</term> + <listitem> + <para> + The name of a repository. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>default-workspace</term> + <listitem> + <para> + The name of a workspace obtained using Session's login() or login(Credentials) methods (ones without an explicit workspace name). + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>system-workspace</term> + <listitem> + <para> + The name of workspace where /jcr:system node is placed. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>security-domain</term> + <listitem> + <para> + The name of a security domain for JAAS authentication + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>access-control</term> + <listitem> + <para> + The name of an access control policy. There can be 3 types: optional - ACL is created on-demand(default), disable - no access control, mandatory - an ACL is created for each added node(not supported yet) + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>authentication-policy</term> + <listitem> + <para> + The name of an authentication policy class + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>workspaces</term> + <listitem> + <para> + The list of workspaces. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>session-max-age</term> + <listitem> + <para> + The time after which an idle session will be removed (called logout). If not set, the idle session will never be removed. + </para> + </listitem> + </varlistentry> + </variablelist> + + <variablelist> + <title>Workspace configuration:</title> + <varlistentry> + <term>name</term> + <listitem> + <para> + The name of a workspace. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>auto-init-root-nodetype</term> + <listitem> + <para> + DEPRECATED in JCR 1.9 (use initializer). The node type for root node initialization. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>container</term> + <listitem> + <para> + Workspace data container (physical storage) configuration. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>initializer</term> + <listitem> + <para> + Workspace initializer configuration. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>cache</term> + <listitem> + <para> + Workspace storage cache configuration. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>query-handler</term> + <listitem> + <para> + Query handler configuration. + </para> + </listitem> + </varlistentry> + </variablelist> + <formalpara> + <title>Workspace data container configuration:</title> + <para></para> + </formalpara> + <variablelist> + <varlistentry> + <term>class</term> + <listitem> + <para> + A workspace data container class name. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>properties</term> + <listitem> + <para> + The list of properties (name-value pairs) for the concrete Workspace data container. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>value-storages</term> + <listitem> + <para> + The list of value storage plugins. + </para> + </listitem> + </varlistentry> + </variablelist> + + <variablelist> + <title>Value Storage plugin configuration (optional feature):</title> + <varlistentry> + <term>value-storage</term> + <listitem> + <para> + Optional value Storage plugin definition. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>class</term> + <listitem> + <para> + A value storage plugin class name (attribute) + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>properties</term> + <listitem> + <para> + The list of properties (name-value pairs) for a concrete Value Storage plugin. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>filters</term> + <listitem> + <para> + The list of filters defining conditions when this plugin is applicable. + </para> + </listitem> + </varlistentry> + </variablelist> <note> <para> The value-storage element is optional. If you don't include it, the values will be stored as BLOBs inside the database. </para> </note> - <para> - value-storage - Optional value Storage plugin definition - </para> - <para> - class- a value storage plugin class name (attribute) - </para> - <para> - properties - the list of properties (name-value pairs) for a concrete Value Storage plugin - </para> - <para> - filters - the list of filters defining conditions when this plugin is applicable - </para> - <para> - Initializer configuration (optional): - </para> - <para> - class - initializer implementation class. - </para> - <para> - properties - the list of properties (name-value pairs). Properties are supported: - </para> - <para> - root-nodetype - The node type for root node initialization - </para> - <para> - root-permissions - Default permissions of the root node. It is defined as a set of semicolon-delimited permissions containing a group of space-delimited identities (user, group etc, see Organization service documentation for details) and the type of permission. For example any read;:/admin read;:/admin add_node;:/admin set_property;:/admin remove means that users from group admin have all permissions and other users have only a 'read' permission. - </para> - <para> - Configurable initializer adds a capability to override workspace initial startup procedure. - </para> - <para> - Cache configuration: - </para> - <para> - enabled - if workspace cache is enabled - </para> - <para> - class - cache implementation class, optional from 1.9. Default value is org.exoplatform.services.jcr.impl.dataflow.persistent.LinkedWorkspaceStorageCacheImpl. - </para> - <para> - Cache can be configured to use concrete implementation of WorkspaceStorageCache interface. JCR core has two implementation to use: * LinkedWorkspaceStorageCacheImpl - default, with configurable read behavior and statistic. * WorkspaceStorageCacheImpl - pre 1.9, still can be used. - </para> - <para> - properties - the list of properties (name-value pairs) for Workspace cache: - </para> - <para> - max-size - cache maximum size. - </para> - <para> - live-time - cached item live time. - </para> - <para> - LinkedWorkspaceStorageCacheImpl supports additional optional parameters TODO - </para> - <para> - Query Handler configuration: - </para> - <para> - class - A Query Handler class name - </para> - <para> - properties - the list of properties (name-value pairs) for a Query Handler (indexDir) properties and advanced features described in *Search Configuration* - </para> - <para> - Lock Manager configuration: - </para> - <para> - time-out - time after which the unused global lock will be removed. - </para> - <para> - persister - a class for storing lock information for future use. For example, remove lock after jcr restart. - </para> - <para> - path - a lock folder, each workspace has its own. - </para> - <para> - </para> - <para> - Configuration definition: - </para> - + + <variablelist> + <title>Initializer configuration (optional):</title> + <varlistentry> + <term>class</term> + <listitem> + <para> + Initializer implementation class. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>properties</term> + <listitem> + <para> + The list of properties (name-value pairs). Properties are supported: + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>root-nodetype</term> + <listitem> + <para> + The node type for root node initialization + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>root-permissions</term> + <listitem> + <para> + Default permissions of the root node. It is defined as a set of semicolon-delimited permissions containing a group of space-delimited identities (user, group etc, see Organization service documentation for details) and the type of permission. For example any read;:/admin read;:/admin add_node;:/admin set_property;:/admin remove means that users from group admin have all permissions and other users have only a 'read' permission. + </para> + <para> + Configurable initializer adds a capability to override workspace initial startup procedure. + </para> + </listitem> + </varlistentry> + </variablelist> + + <variablelist> + <title>Cache configuration:</title> + <varlistentry> + <term>enabled</term> + <listitem> + <para> + If workspace cache is enabled. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>class</term> + <listitem> + <para> + Cache implementation class, optional from 1.9. Default value is <literal>org.exoplatform.services.jcr.impl.dataflow.persistent.LinkedWorkspaceStorageCacheImpl</literal>. + </para> + <para> + Cache can be configured to use concrete implementation of WorkspaceStorageCache interface. JCR core has two implementation to use: * LinkedWorkspaceStorageCacheImpl - default, with configurable read behavior and statistic. * WorkspaceStorageCacheImpl - pre 1.9, still can be used. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>properties</term> + <listitem> + <para> + The list of properties (name-value pairs) for Workspace cache: + </para> + <variablelist> + <varlistentry> + <term>max-size</term> + <listitem> + <para> + Cache maximum size. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>live-time</term> + <listitem> + <para> + Cached item live time. + </para> + </listitem> + </varlistentry> + </variablelist> + <para> + LinkedWorkspaceStorageCacheImpl supports additional optional parameters TODO + </para> + </listitem> + </varlistentry> + </variablelist> + + <variablelist> + <title>Query Handler configuration:</title> + <varlistentry> + <term>class</term> + <listitem> + <para> + A Query Handler class name. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>properties</term> + <listitem> + <para> + The list of properties (name-value pairs) for a Query Handler (indexDir) properties and advanced features described in *Search Configuration*. + </para> + </listitem> + </varlistentry> + </variablelist> + + <variablelist> + <title>Lock Manager configuration:</title> + <varlistentry> + <term>time-out</term> + <listitem> + <para> + Time after which the unused global lock will be removed. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>persister</term> + <listitem> + <para> + A class for storing lock information for future use. For example, remove lock after jcr restart. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>path</term> + <listitem> + <para> + A lock folder, each workspace has its own. + </para> + </listitem> + </varlistentry> + </variablelist> + <formalpara> + <title>Configuration definition:</title> + <para></para> + </formalpara> + <programlisting>&lt;!ELEMENT repository-service (repositories)&gt; &lt;!ATTLIST repository-service default-repository NMTOKEN #REQUIRED&gt; &lt;!ELEMENT repositories (repository)&gt; Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/external-value-storages.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/external-value-storages.xml 2010-04-29 23:05:07 UTC (rev 2905) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/external-value-storages.xml 2010-04-29 23:59:46 UTC (rev 2906) @@ -11,7 +11,7 @@ By default JCR Values are stored in the Workspace Data container along with the JCR structure (i.e. Nodes and Properties). eXo JCR offers an additional option of storing JCR Values separately from Workspace Data container, which can be extremely helpful to keep Binary Large Objects (BLOBs) for example (see [TODOBinary values processing link]). </para> <para> - Value storage configuration is a part of Repository configuration, find more details <link linkend="sect-Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration">there</link>. + Value storage configuration is a part of Repository configuration, find more details in <xref linkend="sect-Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration"/>. </para> <para> Tree-based storage is recommended for most of cases. If you run an application on Amazon EC2 - the S3 option may be interesting for architecture. Simple 'flat' storage is good in speed of creation/deletion of values, it might be a compromise for a small storages. Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml 2010-04-29 23:05:07 UTC (rev 2905) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml 2010-04-29 23:59:46 UTC (rev 2906) @@ -83,7 +83,7 @@ By default the configuration files are located in service jars <filename>/conf/portal/configuration.xml</filename> (eXo services including JCR Repository Service) and <filename>exo-jcr-config.xml</filename> (repositories configuration). In eXo portal product JCR is configured in portal web application <filename>portal/WEB-INF/conf/jcr/jcr-configuration.xml</filename> (JCR Repository Service and related serivces) and repository-configuration.xml (repositories configuration). </para> <para> - Read more about <link linkend="sect-Reference_Guide-eXo_JCR_configuration">Repository configuration</link>. + Read more about <xref linkend="sect-Reference_Guide-eXo_JCR_configuration"/>. </para> </section> @@ -319,7 +319,7 @@ </para> <note> <para> - Starting from v.1.9 <link linkend="sect-Reference_Guide-eXo_JCR_configuration">repository configuration</link> parameters supports human-readable formats of values (e.g. 200K - 200 Kbytes, 30m - 30 minutes etc) + Starting from v.1.9 <xref linkend="sect-Reference_Guide-eXo_JCR_configuration"/> parameters supports human-readable formats of values (e.g. 200K - 200 Kbytes, 30m - 30 minutes etc) </para> </note> </section> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml 2010-04-29 23:05:07 UTC (rev 2905) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml 2010-04-29 23:59:46 UTC (rev 2906) @@ -60,7 +60,7 @@ LockManagerImpl is simple implementation of LockManager, and also faster than CacheableLockManager. It stores Lock objects in HashMap and may also persist Locks if LockPersister is configured. LockManagerImpl do not support replication in any way. </para> <para> - See more about LockManager Configuration <link linkend="sect-Reference_Guide-eXo_JCR_configuration">here</link>. + See more about LockManager Configuration in <xref linkend="sect-Reference_Guide-eXo_JCR_configuration"/>. </para> </section> @@ -84,7 +84,7 @@ Replication requirements are same as for Cache </para> <para> - Full JCR configuration example you can see <link linkend="sect-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration">here</link>. + Full JCR configuration example can be seen in <xref linkend="sect-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration"/>. </para> <para> Common tips: Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml 2010-04-29 23:05:07 UTC (rev 2905) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml 2010-04-29 23:59:46 UTC (rev 2906) @@ -38,7 +38,7 @@ A little bit about indexing process (no matter, cluster or not) Indexer do not writes changes to FS lucene index immediately. At first, Indexer writes changes to Volatile index. If Volatile index size become 1Mb or more it is flushed to FS. Also there is timer, that flushes volatile index by timeout. Volatile index timeout configured by "max-volatile-time" paremeter. </para> <para> - See more about <link linkend="sect-Reference_Guide-Search_Configuration">Search Configuration</link>. + See more in <xref linkend="sect-Reference_Guide-Search_Configuration"/>. </para> <para> Common scheme of Shared Index @@ -200,7 +200,7 @@ </programlisting> </para> <para> - See more about template configurations <link linkend="sect-Reference_Guide-JBoss_Cache_configuration">here</link>. + See more about template configurations in <xref linkend="sect-Reference_Guide-JBoss_Cache_configuration"/>. </para> </section> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalPermissionConfiguration.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalPermissionConfiguration.xml 2010-04-29 23:05:07 UTC (rev 2905) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalPermissionConfiguration.xml 2010-04-29 23:59:46 UTC (rev 2906) @@ -55,7 +55,6 @@ </listitem> </varlistentry> </variablelist> - <programlisting role="XML">&lt;component&gt; &lt;key&gt;org.exoplatform.portal.config.UserACL&lt;/key&gt; &lt;type&gt;org.exoplatform.portal.config.UserACL&lt;/type&gt; Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2010-04-29 23:05:07 UTC (rev 2905) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2010-04-29 23:59:46 UTC (rev 2906) @@ -62,6 +62,7 @@ </varlistentry> </variablelist> <note> + <title>CSS Classes</title> <para> The window decorators and the default portlet specification css classes should be considered separate types of skinning components, but they need to be included as part of the overall portal skin. The portal skin must include these components' css classes or they will not be displayed correctly. </para> @@ -151,6 +152,7 @@ &lt;/head&gt; </programlisting> <note> + <title>CSS classes</title> <para> Window styles and the portlet specification CSS classes are included within the portal skin. </para> @@ -217,6 +219,7 @@ </programlisting> <note> + <title><literal>display-name</literal></title> <para> The <literal>display-name</literal> element will also need to be specified in the <literal>web.xml</literal> for the skinning service to work properly with the web application. </para> @@ -329,6 +332,7 @@ <programlisting>@import url(/eXoResources/skin/Portlet/Stylesheet.css); </programlisting> <note> + <title>Stylesheet Merging</title> <para> When the portal skin is added to the page, it merge all the css stylesheets into a single file. </para> @@ -363,6 +367,7 @@ The default portal skin and window styles are defined in <filename>01eXoResources.war/WEB-INF/gatein-resources.xml</filename>. </para> <note> + <title>CSS</title> <para> The css for the portal skin needs to contain the css for all the window decorations and the portlet specification css classes. </para> @@ -375,9 +380,12 @@ When selecting a skin it is possible to see a preview of what the skin will look like. The current skin needs to know about the skin icons for all the available skins, otherwise it will not be able to show the previews. When creating a new portal it is recommended to include the preview icons of the other skins and to update the other skins with your new portal skin preview. </para> <mediaobject> - <imageobject> - <imagedata fileref="images/PortalDevelopment/Skinning/portal-change-skin.png" format="PNG" width="444" /> + <imageobject role="html"> + <imagedata fileref="images/PortalDevelopment/Skinning/portal-change-skin.png" format="PNG" align="center" scale="100" /> </imageobject> + <imageobject role="fo"> + <imagedata fileref="images/PortalDevelopment/Skinning/portal-change-skin.png" format="PNG" align="center" contentwidth="150mm" /> + </imageobject> </mediaobject> <para> The portal skin preview icon is specified through the CSS of the portal skin. In order for the current portal skin to be able to display the preview it must specify a specific CSS class and set the icon as the background. @@ -410,12 +418,15 @@ <para> Window styles are the CSS applied to window decoration. When an administrator choose a new application to add on a page he can decide which style of decoration would go around the window if any. </para> - <para> - <mediaobject> - <imageobject> - <imagedata fileref="images/PortalDevelopment/Skinning/windowStyles.png" format="PNG" width="444" /> - </imageobject> - </mediaobject> + <para>PortalDevelopment/Skinning/windowStyles + <mediaobject> + <imageobject role="html"> + <imagedata fileref="images/PortalDevelopment/Skinning/windowStyles.png" format="PNG" align="center" scale="100" /> + </imageobject> + <imageobject role="fo"> + <imagedata fileref="images/PortalDevelopment/Skinning/windowStyles.png" format="PNG" align="center" contentwidth="150mm" /> + </imageobject> + </mediaobject> </para> <section id="sect-Reference_Guide-Creating_a_New_Window_Style-Window_Style_Configuration"> <title>Window Style Configuration</title> @@ -440,8 +451,9 @@ The windows style configuration for the default skin is configured in: <filename>01eXoResources.war/WEB-INF/gatein-resources.xml</filename>. </para> <note> + <title>Window Styles and Portal Skins</title> <para> - When a window style is defined in gatein-resources.xml file, it will be available to all portlets regardless if the current portal skin support the window decorator or not. It is recommended that when a new window decorator is added that it is added to all portal skins or that portal skins share a common stylesheet for window decorators. + When a window style is defined in <filename>gatein-resources.xml</filename> file, it will be available to all portlets regardless if the current portal skin supports the window decorator or not. It is recommended that when a new window decorator is added that it is added to all portal skins or that portal skins share a common stylesheet for window decorators. </para> </note> </section> @@ -596,8 +608,9 @@ To set the default window style to be used for a portal, you will to specify the css classes for a theme called <literal>DefaultTheme</literal>. </para> <note> + <title>DefaultTheme</title> <para> - You do not need to specify the DefaultTheme in gatein-resources.xml + You do not need to specify the DefaultTheme in <filename>gatein-resources.xml</filename>. </para> </note> </section> @@ -633,6 +646,7 @@ This will load the DefaultStylesheet.css when the Default skin is used and the OtherSkinStylesheet.css when the OtherSkin is used. </para> <note> + <title>Updating portlet skins</title> <para> If the current portal skin is not defined as part of the supported skins, then the portlet css class will not be loaded. It is recommended to update portlet skins whenever a new portal skin is created. </para> @@ -663,6 +677,7 @@ </listitem> </itemizedlist> <note> + <title>Portlet icons directory</title> <para> You must use <literal>skin/DefaultSkin/portletIcons/</literal> for the directory to store the portlet icon regardless of what skin is going to be used. </para>