[gatein-commits] gatein SVN: r3162 - in portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US: modules and 6 other directories.

Author: smumford Date: 2010-05-21 02:43:22 -0400 (Fri, 21 May 2010) New Revision: 3162 Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/images/PortletDevelopment/Standard/jsp_portlet/output.png portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/Foundations.xml 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.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/intro.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/jbossts-transaction-service.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/search-configuration.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/statistics.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/transaction-manager-lookup.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/GadgetDevelopment/Gadgets.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Introduction.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/configuration.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/WSRP.xml Log: JBEPP-276: QE recommendations edits Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/images/PortletDevelopment/Standard/jsp_portlet/output.png =================================================================== (Binary files differ) Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/Foundations.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/Foundations.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/Foundations.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -569,8 +569,9 @@ The <emphasis role="bold">Unified servlet context</emphasis>, and <emphasis role="bold">unified classloader</emphasis> are part of the <emphasis role="bold">extension mechanism</emphasis> (which is detailed in the next section). </para> <para> - They provide standard API (<literal>ServletContext</literal>, <literal>ClassLoader</literal>) with specific resource loading behavior, such as visibility into associated web application archives, configured with dependencies property of <literal>PortalContainerDefinition</literal>. + They provide the standard API (<literal>ServletContext</literal>, <literal>ClassLoader</literal>) with specific resource loading behavior, such as visibility into associated web application archives, configured with dependencies property of <literal>PortalContainerDefinition</literal>. </para> +<!-- DOC TODO: Confirm if 'visibility into' is the approapriate phrase to use here --> <para> Resources from other web applications are queried in the order specified by the dependencies. The later entries in the list override the previous ones. </para> 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-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/cluster-config.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -19,17 +19,17 @@ </step> <step> <para> - Copy the <filename>jcr.ear</filename> into <filename>%jboss_home%/server/default/deploy</filename>. + Copy the <filename>jcr.ear</filename> into <filename>$JBOSS_HOME/server/default/deploy</filename>. </para> </step> <step> <para> - Save the <filename>exo-configuration.xml</filename> into the root <filename>%jboss_home%/exo-configuration.xml</filename>. + Save the <filename>exo-configuration.xml</filename> into the root <filename>$JBOSS_HOME/exo-configuration.xml</filename>. </para> </step> <step> <para> - Configure JAAS by inserting the XML fragment shown below into <filename>%jboss_home%/server/default/conf/login-config.xml</filename>. + Configure JAAS by inserting the XML fragment shown below into <filename>$JBOSS_HOME/server/default/conf/login-config.xml</filename>. </para> <programlisting language="XML" role="XML"><![CDATA[<application-policy name="exo-domain"> @@ -46,7 +46,7 @@ <para> The <filename>exo-configuration.xml</filename> must contain the following parts: </para> - +<!-- DOC TODO: There is no exo-configuration.xml file in the jar or in the svn trunk/. Does this file exist? --> <programlisting language="XML" role="XML"><![CDATA[<component> <key>org.jboss.cache.transaction.TransactionManagerLookup</key> <type>org.jboss.cache.GenericTransactionManagerLookup</type>^ 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-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -11,6 +11,7 @@ <para> The JCR Service can use multiple repositories and each repository can have multiple workspaces. </para> +<!--DOC TODO Add more definition of respositories and workspaces --> <para> The repository configuration parameters support human-readable formats of values. They are not case-sensitive. </para> @@ -105,6 +106,7 @@ <section id="sect-Reference_Guide-eXo_JCR_configuration-Portal_and_Standalone_configuration"> <title>Portal and Standalone configuration</title> +<!-- DOC TODO Do we need to discuss JCR in Satandalone mode, is this relevant?--> <para> Like other eXo services, eXo JCR can be configured and used in portal (or embedded) mode (as a service embedded in EPP5) and in standalone mode. </para> @@ -169,7 +171,7 @@ <area coords="10" id="area-Reference_Guide-eXo_JCR_configuration-Portal_and_Standalone_configuration-JCR_Service_Configuration-conf-path" /> <area coords="15" id="area-Reference_Guide-eXo_JCR_configuration-Portal_and_Standalone_configuration-JCR_Service_Configuration-working-conf" /> </areaspec> - +<!-- DOC TODO: There is no exo-configuration.xml file in the jar or in the svn trunk/. Does this file exist? --> <programlisting language="XML" role="XML"><![CDATA[<component> <key>org.exoplatform.services.jcr.RepositoryService</key> <type>org.exoplatform.services.jcr.impl.RepositoryServiceImpl</type> @@ -213,12 +215,14 @@ <para> The default configuration of the Repository Service is defined in <filename><replaceable>jar:</replaceable>/conf/portal/exo-jcr-config.xml</filename>. It is available in both portal and standalone modes. </para> +<!-- DOC TODO: There is no exo-configuration.xml file in the jar or in the svn trunk/. Does this file exist? --> <para> In portal mode it is overriden and located in the portal web application <filename>portal/WEB-INF/conf/jcr/repository-configuration.xml</filename>. </para> <para> An example of the Repository Service configuration for standalone mode is included below: </para> +<!-- DOC TODO: convert the varlists below this code sample to callouts, and ensure tags and attributes are marked up appropriately--> <!-- <programlistingco> 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-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/external-value-storages.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -128,7 +128,7 @@ <section id="sect-Reference_Guide-External_Value_Storages-Content_Addressable_Value_storage_CAS_support"> <title>Content Addressable Value storage (CAS) support</title> <para> - eXo JCR supports the <phrase>Content-addressable storage</phrase> feature for <phrase>Values</phrase> storing. + eXo JCR supports the <phrase>Content-addressable storage</phrase> feature for <phrase>values</phrase> storing. </para> <para> Content-addressable storage, also referred to as associative storage and abbreviated as <emphasis role="bold">CAS</emphasis>, is a mechanism for storing information that can be retrieved based on its content, not its storage location. Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/intro.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/intro.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/intro.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -6,10 +6,10 @@ <section id="sect-Reference_Guide-Introduction"> <title>Introduction</title> <para> - The Java Content Repository (JCR) API was created within the Java Community Process (JCP)<ulink type="http" url="http://jcp.org/">http://jcp.org/</ulink>) as a collaboration between an expert group and the Java community. + The Java Content Repository (JCR) API was created within the Java Community Process (<ulink type="http" url="http://jcp.org/">http://jcp.org/</ulink>) as a collaboration between an expert group and the Java community. </para> <para> - Within the JCP, JCR is known as Java Specification Request-170 (JSR-170) <ulink type="http" url="http://www.jcp.org/en/jsr/detail?id=170">http://www.jcp...;. + Within the Java Community Process (JCP), JCR is known as Java Specification Request-170 (JSR-170) <ulink type="http" url="http://www.jcp.org/en/jsr/detail?id=170">http://www.jcp...;. </para> <section id="sect-Reference_Guide-JCR_JSR_170_API_main_concepts-The_Data_model"> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/jbossts-transaction-service.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/jbossts-transaction-service.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/jbossts-transaction-service.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -11,7 +11,7 @@ JBossTransactionsService implements eXo <xref linkend="chap-Reference_Guide-eXoJCR"/> and provides access to <ulink type="http" url="http://www.jboss.org/jbosstm/">JBoss Transaction Service (JBossTS)</ulink> JTA implementation via eXo container dependency. </para> <para> - TransactionService used in JCR cache <emphasis>org.exoplatform.services.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache</emphasis> implementaion. See <ulink url="cluster-config.html">Cluster configuration</ulink> for example. + TransactionService used in JCR cache <emphasis>org.exoplatform.services.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache</emphasis> implementation. </para> </section> @@ -21,17 +21,16 @@ Example configuration: </para> -<programlisting> &lt;component&gt; - &lt;key&gt;org.exoplatform.services.transaction.TransactionService&lt;/key&gt; - &lt;type&gt;org.exoplatform.services.transaction.jbosscache.JBossTransactionsService&lt;/type&gt; - &lt;init-params&gt; - &lt;value-param&gt; - &lt;name&gt;timeout&lt;/name&gt; - &lt;value&gt;3000&lt;/value&gt; - &lt;/value-param&gt; - &lt;/init-params&gt; - &lt;/component&gt; -</programlisting> +<programlisting language="XML" role="XML"><![CDATA[<component> + <key&gt;org.exoplatform.services.transaction.TransactionService&lt;/key> + <type&gt;org.exoplatform.services.transaction.jbosscache.JBossTransactionsService&lt;/type> + <init-params> + <value-param> + <name&gt;timeout&lt;/name> + <value&gt;3000&lt;/value> + </value-param> + </init-params> + </component>]]></programlisting> <para> timeout - XA transaction timeout in seconds </para> 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-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -34,6 +34,7 @@ <para> Currently the data container is tested with the following Rational Database Management Systems (RDBMS): </para> +<!-- Commented out in favor of more extensive list found in EPP 5.0 ERD (and converted to XML for Release Notes) <itemizedlist> <listitem> <para> @@ -75,8 +76,136 @@ HSQLDB (1.8.0.7) </para> </listitem> - </itemizedlist> + </itemizedlist> --> + <table id="tabl-Release_Notes-Certified_Environments-Database_Support_"> + <title>Database Support </title> + <tgroup cols="3"> + <thead> + <row> + <entry> + RDBMS + </entry> + <entry> + Server + </entry> + <entry> + JBDC Driver + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + MySQL + </entry> + <entry> + <para> + 5.1 (certified) + </para> + <para> + 5.0 (compatible) + </para> + </entry> + <entry> + <para> + MYSQL Connector/J 5.1.8 (certified) + </para> + <para> + MySQL Connector/J 5.0.8 (compatible) + </para> + </entry> + </row> + <row> + <entry> + Oracle DB + </entry> + <entry> + <para> + 10g R2 (10.2.0.4) (certified) + </para> + <para> + 11g R1 (11.1.0.7.0) (compatible) + </para> + <para> + 11g RAC (11.1.0.7.0) (compatible) + </para> + </entry> + <entry> + <para> + Oracle 10g R2 (10.2.0.4) (certified) + </para> + <para> + Oracle 11g R1 (11.1.0.7) (compatible) + </para> + <para> + Oracle 11g R1 (11.1.0.7) (compatible) + </para> + </entry> + </row> + <row> + <entry> + MS SQL Server + </entry> + <entry> + <para> + 2005 SP3 (certified) + </para> + <para> + 2008 SP1 (certified) + </para> + </entry> + <entry> + JDBC Driver 2.0 (certified) + </entry> + </row> + <row> + <entry> + PostgresSQL + </entry> + <entry> + <para> + 8.3.7 (certified) + </para> + <para> + 8.2.4 (compatible) + </para> + </entry> + <entry> + <para> + JDBC4 Driver, Ver 8.3-605 (certified) + </para> + <para> + JDBC4 Driver, Ver 8.2-510 (compatible) + </para> + </entry> + </row> + <row> + <entry> + DB2 + </entry> + <entry> + 9.7 (certified) + </entry> + <entry> + IBM Data Server Driver for JDBC and SQLJ (JCC Driver) Version: 9.1 (fixpack 3a) (certified) + </entry> + </row> + <row> + <entry> + Sybase + </entry> + <entry> + 15.0.2 (certified) + </entry> + <entry> + JConnect v6.0.5 (Build 26564 / 11 Jun 2009) (certified) + </entry> + </row> + </tbody> + </tgroup> + </table> + <para> Each of these database managers supports ANSI SQL standards but each has its own specifics as well. Consequently, each database has its own configuration in eXo JCR as a database dialect parameter. </para> @@ -126,76 +255,75 @@ The following example is in standalone mode with two data containers <parameter>jdbcjcr</parameter> (a local HSQLDB) and <parameter>jdbcjcr1</parameter> (a remote MySQL container): </para> -<programlisting language="XML" role="XML">&lt;component&gt; - &lt;key&gt;org.exoplatform.services.naming.InitialContextInitializer&lt;/key&gt; - &lt;type&gt;org.exoplatform.services.naming.InitialContextInitializer&lt;/type&gt; - &lt;component-plugins&gt; - &lt;component-plugin&gt; - &lt;name&gt;bind.datasource&lt;/name&gt; - &lt;set-method&gt;addPlugin&lt;/set-method&gt; - &lt;type&gt;org.exoplatform.services.naming.BindReferencePlugin&lt;/type&gt; - &lt;init-params&gt; - &lt;value-param&gt; - &lt;name&gt;bind-name&lt;/name&gt; - &lt;value&gt;jdbcjcr&lt;/value&gt; - &lt;/value-param&gt; - &lt;value-param&gt; - &lt;name&gt;class-name&lt;/name&gt; - &lt;value&gt;javax.sql.DataSource&lt;/value&gt; - &lt;/value-param&gt; - &lt;value-param&gt; - &lt;name&gt;factory&lt;/name&gt; - &lt;value&gt;org.apache.commons.dbcp.BasicDataSourceFactory&lt;/value&gt; - &lt;/value-param&gt; - &lt;properties-param&gt; - &lt;name&gt;ref-addresses&lt;/name&gt; - &lt;description&gt;ref-addresses&lt;/description&gt; - &lt;property name="driverClassName" value="org.hsqldb.jdbcDriver"/&gt; - &lt;property name="url" value="jdbc:hsqldb:file:target/temp/data/portal"/&gt; - &lt;property name="username" value="sa"/&gt; - &lt;property name="password" value=""/&gt; - &lt;/properties-param&gt; - &lt;/init-params&gt; - &lt;/component-plugin&gt; - &lt;component-plugin&gt; - &lt;name&gt;bind.datasource&lt;/name&gt; - &lt;set-method&gt;addPlugin&lt;/set-method&gt; - &lt;type&gt;org.exoplatform.services.naming.BindReferencePlugin&lt;/type&gt; - &lt;init-params&gt; - &lt;value-param&gt; - &lt;name&gt;bind-name&lt;/name&gt; - &lt;value&gt;jdbcjcr1&lt;/value&gt; - &lt;/value-param&gt; - &lt;value-param&gt; - &lt;name&gt;class-name&lt;/name&gt; - &lt;value&gt;javax.sql.DataSource&lt;/value&gt; - &lt;/value-param&gt; - &lt;value-param&gt; - &lt;name&gt;factory&lt;/name&gt; - &lt;value&gt;org.apache.commons.dbcp.BasicDataSourceFactory&lt;/value&gt; - &lt;/value-param&gt; - &lt;properties-param&gt; - &lt;name&gt;ref-addresses&lt;/name&gt; - &lt;description&gt;ref-addresses&lt;/description&gt; - &lt;property name="driverClassName" value="com.mysql.jdbc.Driver"/&gt; - &lt;property name="url" value="jdbc:mysql://exoua.dnsalias.net/jcr"/&gt; - &lt;property name="username" value="exoadmin"/&gt; - &lt;property name="password" value="exo12321"/&gt; - &lt;property name="maxActive" value="50"/&gt; - &lt;property name="maxIdle" value="5"/&gt; - &lt;property name="initialSize" value="5"/&gt; - &lt;/properties-param&gt; - &lt;/init-params&gt; - &lt;/component-plugin&gt; - &lt;component-plugins&gt; - &lt;init-params&gt; - &lt;value-param&gt; - &lt;name&gt;default-context-factory&lt;/name&gt; - &lt;value&gt;org.exoplatform.services.naming.SimpleContextFactory&lt;/value&gt; - &lt;/value-param&gt; - &lt;/init-params&gt; - &lt;/component&gt; -</programlisting> +<programlisting language="XML" role="XML"><![CDATA[<component> + <key>org.exoplatform.services.naming.InitialContextInitializer</key> + <type>org.exoplatform.services.naming.InitialContextInitializer</type> + <component-plugins> + <component-plugin> + <name>bind.datasource</name> + <set-method>addPlugin</set-method> + <type>org.exoplatform.services.naming.BindReferencePlugin</type> + <init-params> + <value-param> + <name>bind-name</name> + <value>jdbcjcr</value> + </value-param> + <value-param> + <name>class-name</name> + <value>javax.sql.DataSource</value> + </value-param> + <value-param> + <name>factory</name> + <value>org.apache.commons.dbcp.BasicDataSourceFactory</value> + </value-param> + <properties-param> + <name>ref-addresses</name> + <description>ref-addresses</description> + <property name="driverClassName" value="org.hsqldb.jdbcDriver"/> + <property name="url" value="jdbc:hsqldb:file:target/temp/data/portal"/> + <property name="username" value="sa"/> + <property name="password" value=""/> + </properties-param> + </init-params> + </component-plugin> + <component-plugin> + <name>bind.datasource</name> + <set-method>addPlugin</set-method> + <type>org.exoplatform.services.naming.BindReferencePlugin</type> + <init-params> + <value-param> + <name>bind-name</name> + <value>jdbcjcr1</value> + </value-param> + <value-param> + <name>class-name</name> + <value>javax.sql.DataSource</value> + </value-param> + <value-param> + <name>factory</name> + <value>org.apache.commons.dbcp.BasicDataSourceFactory</value> + </value-param> + <properties-param> + <name>ref-addresses</name> + <description>ref-addresses</description> + <property name="driverClassName" value="com.mysql.jdbc.Driver"/> + <property name="url" value="jdbc:mysql://exoua.dnsalias.net/jcr"/> + <property name="username" value="exoadmin"/> + <property name="password" value="exo12321"/> + <property name="maxActive" value="50"/> + <property name="maxIdle" value="5"/> + <property name="initialSize" value="5"/> + </properties-param> + </init-params> + </component-plugin> + <component-plugins> + <init-params> + <value-param> + <name>default-context-factory</name> + <value>org.exoplatform.services.naming.SimpleContextFactory</value> + </value-param> + </init-params> + </component>]]></programlisting> </step> <step> <para> @@ -504,7 +632,7 @@ </programlisting> <para> - To configure multiple repository workspaces with one database the "multi-db" parameter must be switched off (set the value to "false"). + To configure multiple repository workspaces with a single database the "multi-db" parameter must be switched off (set the value to "false"). </para> <para> The following example shows configuration for two workspaces <parameter>ws</parameter> (jdbcjcr) and <parameter>ws1</parameter> (jdbcjcr) which will be persisted in one <application>PostgreSQL</application> database: @@ -685,7 +813,7 @@ <section id="sect-Reference_Guide-JDBC_Data_Container_Config-Forse_Query_Hints"> <title>Force Query Hints</title> <para> - Some databases (such as <application>Oracle</application> and <application>MySQL</application>)support hints to increase query performance. + Some databases (such as <application>Oracle</application> and <application>MySQL</application>) support hints to increase query performance. </para> <para> eXo JCR has a separate complex query implementation for the <application>Oracle</application> dialect which uses query hints to increase performance for important queries. @@ -694,13 +822,12 @@ To enable this option complete the configuration property as shown below: </para> -<programlisting>&lt;workspace name="ws" auto-init-root-nodetype="nt:unstructured"&gt; - &lt;container class="org.exoplatform.services.jcr.impl.storage.jdbc.JDBCWorkspaceDataContainer"&gt; - &lt;properties&gt; - &lt;property name="dialect" value="oracle"/&gt; - &lt;property name="force.query.hints" value="true" /&gt; - ...... -</programlisting> +<programlisting language="XML" role="XML"><![CDATA[<workspace name="ws" auto-init-root-nodetype="nt:unstructured"> + <container class="org.exoplatform.services.jcr.impl.storage.jdbc.JDBCWorkspaceDataContainer"> + <properties> + <property name="dialect" value="oracle"/> + <property name="force.query.hints" value="true" /> + ......]]></programlisting> <note> <para> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/search-configuration.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/search-configuration.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/search-configuration.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -6,9 +6,12 @@ <section id="sect-Reference_Guide-Search_Configuration"> <title>Search Configuration</title> <para> -Search can be configured to perform in a specified way. - </para> - <para> + The search function in JCR can be configured to perform in specific ways. This section will discuss configuring the search function to improve search performance and results. + </para> + <para> + Below is an example of the configuration file that governs search behaviors. Refer to <xref linkend="sect-Reference_Guide-Search_Configuration-Global_Search_Index"/> for how searching operates in JCR and discussions about customized searches. + </para> + <para> The JCR index configuration file is located at <filename>/portal/WEB-INF/conf/jcr/repository-configuration.xml</filename>. </para> <para> @@ -48,7 +51,8 @@ </note> <table pgwide="0" align="left" > <title>Configuration parameters</title> - <tgroup cols="4"> +<!--Removing 'version' column <tgroup cols="4"> --> + <tgroup cols="3"> <thead> <row> <entry> @@ -60,9 +64,9 @@ <entry> Description </entry> - <entry> + <!-- <entry> Version - </entry> + </entry> --> </row> </thead> <tbody> @@ -76,9 +80,9 @@ <entry> The location of the index directory. This parameter is mandatory. It is called "<literal>indexDir</literal>" in versions prior to version 1.9. </entry> - <entry> + <!--<entry> 1.0 - </entry> + </entry> --> </row> <row> <entry> @@ -90,10 +94,10 @@ <entry> Advises lucene to use compound files for the index files. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> min-merge-docs @@ -104,10 +108,10 @@ <entry> The minimum number of nodes in an index until segments are merged. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> volatile-idle-time @@ -118,10 +122,10 @@ <entry> Idle time in seconds until the volatile index part is moved to a persistent index even though <literal>minMergeDocs</literal> is not reached. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> max-merge-docs @@ -132,10 +136,10 @@ <entry> The maximum number of nodes in segments that will be merged. The default value changed to <literal>Integer.MAX_VALUE</literal> in JCR version 1.9. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> merge-factor @@ -146,10 +150,10 @@ <entry> Determines how often segment indices are merged. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> max-field-length @@ -160,10 +164,10 @@ <entry> The number of words that are fulltext indexed at most per property. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> cache-size @@ -174,10 +178,10 @@ <entry> Size of the document number cache. This cache maps uuids to lucene document numbers </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> force-consistencycheck @@ -188,10 +192,10 @@ <entry> Runs a consistency check on every startup. If false, a consistency check is only performed when the search index detects a prior forced shutdown. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> auto-repair @@ -202,10 +206,10 @@ <entry> Errors detected by a consistency check are automatically repaired. If false, errors are only written to the log. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> query-class @@ -216,10 +220,10 @@ <entry> Classname that implements the javax.jcr.query.Query interface.This class must also extend from the class: org.exoplatform.services.jcr.impl.core.query.AbstractQueryImpl. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> document-order @@ -230,10 +234,10 @@ <entry> If true and the query does not contain an 'order by' clause, result nodes will be in document order. For better performance set to 'false' when queries return many nodes. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> result-fetch-size @@ -244,10 +248,10 @@ <entry> The number of results when a query is executed. Default value: <literal>Integer.MAX_VALUE</literal>. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> excerptprovider-class @@ -258,10 +262,10 @@ <entry> The name of the class that implements <literal>$lucene.ExcerptProvider</literal>. This should be used for the <literal>rep:excerpt()</literal> function in a query. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> support-highlighting @@ -272,10 +276,10 @@ <entry> If set to true additional information is stored in the index to support highlighting using the <literal>rep:excerpt()</literal> function. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> synonymprovider-class @@ -286,10 +290,10 @@ <entry> The name of a class that implements <literal>$lucene.SynonymProvider</literal>. The default value is null. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> synonymprovider-config-path @@ -300,10 +304,10 @@ <entry> The path to the synonym provider configuration file. This path is interpreted relative to the path parameter. If there is a path element inside the <literal>SearchIndex</literal> element, then this path is interpreted relative to the root path of the path. Whether this parameter is mandatory depends on the synonym provider implementation. The default value is null. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> indexing-configuration-path @@ -314,10 +318,10 @@ <entry> The path to the indexing configuration file. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> indexing-configuration-class @@ -328,10 +332,10 @@ <entry> The name of the class that implements <literal>$lucene.IndexingConfiguration</literal>. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> force-consistencycheck @@ -342,10 +346,10 @@ <entry> 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. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> spellchecker-class @@ -356,10 +360,10 @@ <entry> The name of a class that implements <literal>$lucene.SpellChecker</literal>. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> errorlog-size @@ -370,10 +374,10 @@ <entry> The default size of error log file in Kb. </entry> - <entry> +<!-- <entry> 1.9 </entry> - </row> + --> </row> <row> <entry> upgrade-index @@ -401,10 +405,10 @@ It is reccommended that a backup of the index be made before conversion. (Only for migrations from JCR 1.9 and later.) </para> </entry> - <entry> +<!-- <entry> 1.12 </entry> - </row> + --> </row> <row> <entry> analyzer @@ -415,10 +419,10 @@ <entry> Class name of a lucene analyzer to use for fulltext indexing of text. </entry> - <entry> +<!-- <entry> 1.12 </entry> - </row> + --> </row> </tbody> </tgroup> </table> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/statistics.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/statistics.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/statistics.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -315,10 +315,10 @@ The statistics manager manages all the statistics provided by eXo JCR. It is responsible for printing the data into the CSV files but also exposing the statistics through JMX or Rest, or both. </para> <para> - The statistics manager will create all the CSV files for each category of statistics that it manages. The format of those files is <emphasis>Statistics<replaceable>${category-name}</replaceable>-<replaceable>${creation-timestamp}</replaceable>.csv</emphasis>. + The statistics manager will create Comma-Separated Values (CSV) files for each category of statistics that it manages. The format of those files is <emphasis>Statistics<replaceable>${category-name}</replaceable>-<replaceable>${creation-timestamp}</replaceable>.csv</emphasis>. </para> <para> - Those files will be created in the user directory if it is possible, otherwise they will be placed into the temporary directory. The format of those files is <envar>CSV</envar> (i.e. Comma-Separated Values). One new line will be added regularly (every five seconds by default) and one last line will be added at JVM exit. Each line will be composed of the five figures described below for each method and globally for all the methods. + Those files will be created in the user directory if it is possible, otherwise they will be placed into the temporary directory. Those files are formatted as CSV. One new line will be added regularly (every five seconds by default) and one last line will be added at JVM exit. Each line will be composed of the five figures described below for each method and globally for all the methods. </para> <table id="tabl-Reference_Guide-Statistics_Manager-Metric_Alias"> @@ -372,7 +372,7 @@ The persistence of the statistics can be disabled by setting the JVM parameter; <emphasis>JCRStatisticsManager.persistence.enabled</emphasis> to <emphasis>false</emphasis>. It is set to <emphasis>true</emphasis> by default. </para> <para> - The period of time between each record (i.e. line of data into the file) can be defined by setting the JVM parameter; <emphasis>JCRStatisticsManager.persistence.timeout</emphasis> to the desired value expressed in milliseconds. It is set to <emphasis>5000</emphasis> by default. + The period of time between each record (that is, the line of data into the file) can be defined by setting the JVM parameter; <emphasis>JCRStatisticsManager.persistence.timeout</emphasis> to the desired value expressed in milliseconds. It is set to <emphasis>5000</emphasis> by default. </para> <para> The statistics can also be accessed via JMX. The available methods are: Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/transaction-manager-lookup.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/transaction-manager-lookup.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/transaction-manager-lookup.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -11,11 +11,10 @@ It's JBossCache class registered as eXo container component in configuration.xml file. </para> -<programlisting> &lt;component&gt; - &lt;key&gt;org.jboss.cache.transaction.TransactionManagerLookup&lt;/key&gt; - &lt;type&gt;org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup&lt;/type&gt; - &lt;/component&gt; -</programlisting> +<programlisting language="XML" role="XML"><![CDATA[ <component> + <key&gt;org.jboss.cache.transaction.TransactionManagerLookup&lt;/key> + <type&gt;org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup&lt;/type> + </component>]]></programlisting> <para> JBossStandaloneJTAManagerLookup used in standalone environment. But for Application Server environment use GenericTransactionManagerLookup. </para> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/GadgetDevelopment/Gadgets.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/GadgetDevelopment/Gadgets.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/GadgetDevelopment/Gadgets.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -74,11 +74,13 @@ </listitem> </varlistentry> </variablelist> +<!-- DOC TODO <important> <para> The following sections require more textual information. </para> - </important> + </important> --> + <section id="sect-Reference_Guide-Gadgets-Existing_Gadgets"> <title>Existing Gadgets</title> <mediaobject> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Introduction.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Introduction.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Introduction.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -41,7 +41,7 @@ <imagedata fileref="images/Common/Non-tech-docs.png" format="PNG" align="center" scale="90" /> </imageobject> <imageobject role="fo"> - <imagedata fileref="images/Common/Non-tech-docs.png" format="PNG" align="center" contentwidth="150mm" /> + <imagedata fileref="images/Common/Non-tech-docs.png" format="PNG" align="center" contentwidth="130mm" /> </imageobject> </mediaobject> </listitem> @@ -57,7 +57,7 @@ <imagedata fileref="images/Common/Videos.png" format="PNG" align="center" scale="90" /> </imageobject> <imageobject role="fo"> - <imagedata fileref="images/Common/Videos.png" format="PNG" align="center" contentwidth="150mm" /> + <imagedata fileref="images/Common/Videos.png" format="PNG" align="center" contentwidth="130mm" /> </imageobject> </mediaobject> </listitem> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -8,7 +8,7 @@ <section id="sect-Reference_Guide-Default_Portal_Configuration-Overview"> <title>Overview</title> <para> - &PRODUCT;'s default home page URL is <literal>http://{hostname}:{port}/portal/</literal>. There may be multiple independent portals deployed in parallel at any given time, each of which has its root context (i.e.: <literal>http://{hostname}:{port}/sample-portal/</literal>). + &PRODUCT;'s default home page URL is <literal>http://{hostname}:{port}/portal/</literal>. There may be multiple independent portals deployed in parallel at any given time, each of which has its root context (<literal>http://{hostname}:{port}/sample-portal/</literal>, for example). </para> <para> Each portal is internally composed of one or more 'portals'. This is because there needs to be at least one such portal available. The default portal is called '<emphasis>Classic</emphasis>'. When accessing &PRODUCT;'s default URL, you are automatically directed to the '<emphasis>Classic</emphasis>' portal. Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -126,7 +126,7 @@ <calloutlist> <callout arearefs="area-Reference_Guide-i18n.locales.configuration.locale"> <para> - <emphasis>locale</emphasis>: The locale has to be defined such as defined here <ulink type="http" url="http://ftp.ics.uci.edu-pub-ietf-http-related-iso639.txt" />. In this example "<emphasis>ar</emphasis>" is Arabic. + <emphasis>locale</emphasis>: The locale has to be defined as per the codes defined <ulink type="http" url="http://ftp.ics.uci.edu/pub/ietf/http/related/iso639.txt"&g...;. In this example "<emphasis>ar</emphasis>" is Arabic. </para> </callout> <callout arearefs="area-Reference_Guide-i18n.locales.configuration.output-encoding"> @@ -293,7 +293,7 @@ When translating an application it can sometimes be difficult to find the right key for a given property. </para> <para> - Execute the portal in <emphasis role="bold">debug mode</emphasis> and select, from the available languages, select the special language; <emphasis role="bold">Magic locale</emphasis>. + Execute the portal in <emphasis role="bold">debug mode</emphasis> and select, from the available languages, the special language; <emphasis role="bold">Magic locale</emphasis>. </para> <para> This feature translates a key to the same key value. Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -32,7 +32,7 @@ <section id="sect-Reference_Guide-XML_Resources_Bundles-XML_format"> <title>XML format</title> <para> - The XML format is very simple and has been developed based on the <emphasis>DRY</emphasis> (<ulink type="http" url="http://www.artima.com/intv/dry.html">Don't Repeat Yourself</ulink>) principle. Usually resource bundle keys are hierarchically defined and we can leverage the hierarchic nature of the XML for that purpose. Here is an example of turning a property file into an XML resource bundle file: + The XML format is very simple and has been developed based on the 'Don't Repeat Yourself' (DRY) principle. Usually resource bundle keys are hierarchically defined and we can leverage the hierarchic nature of the XML for that purpose. Here is an example of turning a property file into an XML resource bundle file: </para> <programlisting>UIAccountForm.tab.label.AccountInputSet = ... Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/configuration.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/configuration.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/configuration.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -322,9 +322,10 @@ <para> Just like with any portlet 2.0 event consumer and receiver, you must define them in the <filename>portlet.xml</filename>. </para> +<!--Unsure if community reference is appropriate enterprise doc. As per QE concern (anross <para> To see a working example, checkout the Seam Booking Demo portlet. <ulink url="http://anonsvn.jboss.org/repos/portletbridge/tags/2.0.0.FINAL/e... /> - </para> + </para> --> <para> You must also define the following <emphasis>init params</emphasis> in your <filename>portlet.xml</filename>. </para> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -117,7 +117,7 @@ <section id="sect-Reference_Guide-Getting_started_with_JBoss_Portlet_Bridge-Maven_Archetypes"> <title>Maven Archetypes</title> <para> - This project utilizes <ulink url="http://maven.apache.org/guides/introduction/introduction-to-arc... archetypes</ulink> which allow you get up and running with different flavors of the bridge quickly. + This product utilizes <ulink url="http://maven.apache.org/guides/introduction/introduction-to-arc... archetypes</ulink> which allow you get up and running with different flavors of the bridge quickly. <table frame="all" id="tabl-Reference_Guide-Maven_Archetypes-Available_Archetypes"> <title>Available Archetypes</title> <tgroup align="left" cols="5" colsep="1" rowsep="1"> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -34,7 +34,7 @@ </para> <mediaobject> <imageobject role="html"> - <imagedata fileref="images/PortletDevelopment/Standard/SpecPortalDef.png" format="PNG" align="center" scale="100" /> + <imagedata fileref="images/PortletDevelopment/Standard/SpecPortalDef.png" format="PNG" align="center" scale="95" /> </imageobject> <imageobject role="fo"> <imagedata fileref="images/PortletDevelopment/Standard/SpecPortalDef.png" format="PNG" align="center" contentwidth="140mm" /> @@ -488,8 +488,8 @@ <area coords="25" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class.requestDispatcher" /> <area coords="26" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class.include" /> </areaspec> -<!-- TODO highlight once Publican 1.6.3 installed (JAVA)--> -<programlisting><![CDATA[package org.gatein.portal.examples.portlets; + +<programlisting language="Java" role="JAVA"><![CDATA[package org.gatein.portal.examples.portlets; import java.io.IOException; @@ -556,8 +556,8 @@ <para> The generic portlet that is inherited dispatches the different views to the methods: <literal>doView</literal> , <literal>doHelp</literal> and <literal>doEdit</literal>. </para> -<!-- TODO highlight once Publican 1.6.3 installed (JAVA)--> -<programlisting><![CDATA[... + +<programlisting language="Java" role="JAVA"><![CDATA[... protected void doHelp(RenderRequest rRequest, RenderResponse rResponse) throws PortletException, IOException, UnavailableException { @@ -589,8 +589,8 @@ <area coords="5" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class.getActionParameter" /> <area coords="6" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class.setRenderParameter" /> </areaspec> -<!-- TODO highlight once Publican 1.6.3 installed (JAVA)--> -<programlisting><![CDATA[... + +<programlisting language="Java" role="JAVA"><![CDATA[... public void processAction(ActionRequest aRequest, ActionResponse aResponse) throws PortletException, IOException, UnavailableException { Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/WSRP.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/WSRP.xml 2010-05-20 22:03:47 UTC (rev 3161) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/WSRP.xml 2010-05-21 06:43:22 UTC (rev 3162) @@ -326,31 +326,10 @@ <important> <title>Chunked Encoding</title> <para> - Oracle does not support chunked encoding. Therefore if <emphasis role="bold">Oracle</emphasis>'s WSDL is used as a producer the following error will occur: + Some WSRP producers, such as Oracle, do not support chunked encoding. Using an Oracle WSRP producer will therefore produce an error. </para> - -<screen>05:15:32,125 ERROR [SOAPFaultHelperJAXWS] SOAP request exception -java.io.IOException: Could not transmit message - at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:265) - at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71) - at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:340) - at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290) - -.......... -Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker after 1 attempt(s) - at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:249) - at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:161) - at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:165) - at org.jboss.remoting.Client.invoke(Client.java:1724) - at org.jboss.remoting.Client.invoke(Client.java:629) - at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:243) - ... 135 more -Caused by: org.jboss.ws.WSException: Invalid HTTP server response [503] - Service Unavailable - at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75) - at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:570) -</screen> <para> - A workaround for this issue involves editing the chunksize setting in the <filename>standard-jaxws-client-config.xml</filename> file. + A workaround for this issue involves editing the <parameter>chunksize</parameter> setting in the <filename>standard-jaxws-client-config.xml</filename> file. </para> <para> Refer to <ulink type="http" url="http://community.jboss.org/wiki/Workaroundwhenchunkedencodingis... for more information.