Author: smumford Date: 2011-08-28 23:48:03 -0400 (Sun, 28 Aug 2011) New Revision: 7242 Modified: epp/docs/branches/5.1/Installation_Guide/en-US/Accessing.xml epp/docs/branches/5.1/Installation_Guide/en-US/Installation_Guide.xml epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml epp/docs/branches/5.1/Release_Notes/publican.cfg epp/docs/branches/5.1/User_Guide/en-US/Book_Info.xml epp/docs/branches/5.1/User_Guide/en-US/Revision_History.xml Log: Prepping for 5.1.1 release Modified: epp/docs/branches/5.1/Installation_Guide/en-US/Accessing.xml =================================================================== --- epp/docs/branches/5.1/Installation_Guide/en-US/Accessing.xml 2011-08-29 03:43:15 UTC (rev 7241) +++ epp/docs/branches/5.1/Installation_Guide/en-US/Accessing.xml 2011-08-29 03:48:03 UTC (rev 7242) @@ -7,16 +7,16 @@ ]> <chapter id="chap-Install_Guide-Accessing_PRODUCT"> - <title>Accessing JBoss Enterprise Portal Platform</title> - <section id="sect-Install_Guide-Accessing_PRODUCT-Browser_URL"> - <title>Browser URL</title> - <para> - The URL to a locally installed instance of JBoss Enterprise Portal Platform is <ulink type="http" url="http://localhost:8080/portal/public/classic/home" /> - </para> - <para> - This URL will take users to the front page of JBoss Enterprise Portal Platform where they can log in and begin to undertake actions within the portal itself. - </para> - </section> + <title>Accessing JBoss Enterprise Portal Platform</title> + <section id="sect-Install_Guide-Accessing_PRODUCT-Browser_URL"> + <title>Browser URL</title> + <para> + The URL to a locally installed instance of JBoss Enterprise Portal Platform is <ulink type="http" url="http://localhost:8080/portal/public/classic/home" /> + </para> + <para> + This URL will take users to the front page of JBoss Enterprise Portal Platform where they can log in and begin to undertake actions within the portal itself. + </para> + </section> </chapter> Modified: epp/docs/branches/5.1/Installation_Guide/en-US/Installation_Guide.xml =================================================================== --- epp/docs/branches/5.1/Installation_Guide/en-US/Installation_Guide.xml 2011-08-29 03:43:15 UTC (rev 7241) +++ epp/docs/branches/5.1/Installation_Guide/en-US/Installation_Guide.xml 2011-08-29 03:48:03 UTC (rev 7242) @@ -1,23 +1,19 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> -%BOOK_ENTITIES; - ]> <book> - <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Getting_Started.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Post_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Add-ons.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Test_Your_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Uninstall_JBoss.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Getting_Started.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Post_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Add-ons.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Test_Your_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Uninstall_JBoss.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <index /> + <index /> </book> Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml =================================================================== --- epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-08-29 03:43:15 UTC (rev 7241) +++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-08-29 03:48:03 UTC (rev 7242) @@ -250,15 +250,15 @@ User navigation is the set of nodes and pages that are owned by a user. They are part of the user's dashboard. </para> <!-- DOC NOTE: Get an answer on the below!--> - <!--<remark>This Paragraph:</remark>--> + <!-- This Paragraph:--> <para> Two files configure the user navigation (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). They are located in the directory &#34;<filename>02portal.war/WEB-INF/conf/portal/users/{userName}</filename>&#34;. </para> - <!--<remark>Became this paragraph in GateIn r6987</remark> + <!--Became this paragraph in GateIn r6987 <para> Three files configure the user navigation (<filename>navigation.xml</filename>, <filename>pages.xml</filename> and <filename>portlet-preferences.xml</filename>). They are located in the <filename>{templateLocation}/{ownerType}/{predefinedOwner}</filename> directory with <literal>ownerType</literal> is <literal>user</literal> and <literal>predefinedOwner</literal> is username that want to create the navigation. For example, if administrator want to create navigation for user <literal>root</literal>, he has to locate the configuration files in <filename>portal.war/WEB-INF/conf/portal/user/root </filename> </para> - <remark>Which is appropriate for EPP 5.1.1?</remark>--> + Which is appropriate for EPP 5.1.1?--> <para> The file <filename>eXoGadgets.war/WEB-INF/gadget.xml</filename> defines the gadgets that will be available on a user dashboard. </para> Modified: epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml =================================================================== --- epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-08-29 03:43:15 UTC (rev 7241) +++ epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-08-29 03:48:03 UTC (rev 7242) @@ -11,7 +11,7 @@ JBoss Enterprise Portal Platform offers an intuitive, easy to manage user interface and a proven core infrastructure to enable organizations to quickly build dynamic web sites in a highly reusable way. By bringing the principals of Open Choice to the presentation layer, JBoss Enterprise Portal Platform 5 maximizes existing skills and technology investments. </para> <para> - By integrating proven open source frameworks such as JBoss Seam, Hibernate, Tomcat and JBoss Cache JBoss Enterprise Portal Platform takes advantage of innovations in the open source community. As well, JBoss Enterprise Portal Platform version 5.1.1 is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products. + By integrating proven open source frameworks such as JBoss Seam, Hibernate, Tomcat and JBoss Cache JBoss Enterprise Portal Platform takes advantage of innovations in the open source community. As well, JBoss Enterprise Portal Platform version &VZ; is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products. </para> </section> @@ -65,7 +65,7 @@ <term>eXo JCR</term> <listitem> <para> - The eXo Java Content Repository has been upgraded to version 1.12.9. <!--JBEPP-996--> + The eXo Java Content Repository has been upgraded to version 1.12.9-GA. <!--JBEPP-996--> </para> </listitem> </varlistentry> @@ -89,7 +89,7 @@ <term>WSRP</term> <listitem> <para> - The WSRP component has been upgraded to 2.0.1-GA. <!--JBEPP-789--> + The WSRP component has been upgraded to 2.0.1.GA.EPP51. <!--JBEPP-789--> </para> </listitem> </varlistentry> @@ -232,7 +232,7 @@ GateIn WSRP </entry> <entry> - 2.0.1-EPP51-GA + 2.0.1.GA.EPP51 </entry> </row> <row> @@ -371,15 +371,15 @@ <xi:include href="known_issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </section> - <section> + <!--<section> <title><remark>NEEDINFO Issues</remark></title> <xi:include href="need_info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - </section> + </section>--> - <section> + <!--<section> <title><remark>Not Documented Issues</remark></title> <xi:include href="not_documented.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - </section> + </section>--> <section> <title>Security Related Issues</title> <variablelist> @@ -419,12 +419,12 @@ </listitem> </varlistentry> <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-881" /></term> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-1484" /></term> <listitem> <!-- Added on advice from Dave Jorm in the security team --> <para> - It was found that JBoss Seam 2 did not properly block access to JBoss Expression Language (EL) constructs in page exception handling, allowing arbitrary Java methods to be executed. A remote attacker could use this flaw to execute arbitrary code via a specially-crafted URL provided to certain applications based on the JBoss Seam 2 framework. + It was found that JBoss Web Services Native did not properly protect against recursive entity resolution when processing Document Type Definitions (DTD). A remote attacker could exploit this flaw by sending a specially-crafted HTTP POST request to a deployed web service, causing excessive CPU and memory consumption on the system hosting that service. If the attack is repeated to consume all available network sockets, the server will become unavailable. (CVE-2011-1483) </para> <para> This issue has been fixed in JBoss Enterprise Application Platform version 5.1.1, which is incorporated in this release of JBoss Enterprise Portal Platform. Modified: epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml =================================================================== --- epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml 2011-08-29 03:43:15 UTC (rev 7241) +++ epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml 2011-08-29 03:48:03 UTC (rev 7242) @@ -2,28 +2,6 @@ <!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> - -<variablelist> - - <!-- https://issues.jboss.org/browse/JBEPP-1079 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1079" /></term> - <listitem> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - Pre-release testing has found that attempting to edit a category that does not have a description will produce the following error: -<screen>IllegalArgumentException: Must pass a non null String -</screen> - </para> - <para> - A patch that corrects this behavior is available from &lt;CSP&gt;, as are the required installation instructions. - </para> - </warning> - - </listitem> - </varlistentry> - -</variablelist> +<para> + There are no known issues in this release. +</para> Modified: epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml =================================================================== --- epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml 2011-08-29 03:43:15 UTC (rev 7241) +++ epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml 2011-08-29 03:48:03 UTC (rev 7242) @@ -1,125 +1,11 @@ -<?xml version='1.0'?> -<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Book_Name.ent"> +%BOOK_ENTITIES; ]> +<para> + +</para> -<variablelist> - - <!-- https://issues.jboss.org/browse/JBEPP-764 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-764" /></term> - <listitem> - - - <para> - To isolate multiple clusters running on the same network, the JBoss Cache and JGroups configuration files used in JBoss Enterprise Portal Platform have been updated to include partition name (-g) and multicast address (-u) properties used in JBoss Enterprise Application Platform. - </para> - - </listitem> - </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-874 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-874" /></term> - <listitem> - - - <para> - It was found that, in previous versions of JBoss Enterprise Portal Platform, using JCR addNode within a transaction caused a javax.transaction.HeuristicMixedException (internally, org.exoplatform.services.transaction.TransactionException caused by org.jboss.cache.lock.TimeoutException) when the new node was first accessed. This has been corrected by ensuring that loading data into cache occurs outside the current transaction. - </para> - - </listitem> - </varlistentry> - - <!-- https://issues.jboss.org/browse/JBEPP-884 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-884" /></term> - <listitem> - - - <para> - Changed level of error message for JS compressor - </para> - - </listitem> - </varlistentry> - - <!-- https://issues.jboss.org/browse/JBEPP-961 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-961" /></term> - <listitem> - - - <para> - Release Notes need more information about the issue and how it was fixed. - </para> - - </listitem> - </varlistentry> - - <!-- https://issues.jboss.org/browse/JBEPP-1010 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1010" /></term> - <listitem> - - - <para> - This issue requires more information to be included in the 5.1.1 Release Notes. - </para> - - </listitem> - </varlistentry> - - <!-- https://issues.jboss.org/browse/JBEPP-1013 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1013" /></term> - <listitem> - - - <para> - This issue needs more information to be provided for the 5.1.1 Release Notes. - </para> - - </listitem> - </varlistentry> - - <!-- https://issues.jboss.org/browse/JBEPP-1018 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1018" /></term> - <listitem> - - - <para> - If this issue requires a Release Note, more information (about how the problem presented to users and how it was fixed) is required. - </para> - - </listitem> - </varlistentry> - - <!-- https://issues.jboss.org/browse/JBEPP-1023 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1023" /></term> - <listitem> - - - <para> - This issue requires more information about how it was resolved if it requires a 5.1.1 Release Note. - </para> - - </listitem> - </varlistentry> - - <!-- https://issues.jboss.org/browse/JBEPP-1036 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1036" /></term> - <listitem> - - - <para> - This issue requires more information about the underlying cause and the fix implemented if it requires a 5.1.1 Release Note. - </para> - - </listitem> - </varlistentry> - -</variablelist> Modified: epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml =================================================================== --- epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-08-29 03:43:15 UTC (rev 7241) +++ epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-08-29 03:48:03 UTC (rev 7242) @@ -115,6 +115,19 @@ </listitem> </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-764 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-764" /></term> + <listitem> + + + <para> + To isolate multiple clusters running on the same network, the JBoss Cache and JGroups configuration files used in JBoss Enterprise Portal Platform have been updated to take advantage of the partition name (-g) and multicast address (-u) properties used in JBoss Enterprise Application Platform. + </para> + + </listitem> + </varlistentry> <!-- https://issues.jboss.org/browse/JBEPP-771 --> <varlistentry> @@ -331,6 +344,19 @@ </listitem> </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-874 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-874" /></term> + <listitem> + + + <para> + It was found that, in previous versions of JBoss Enterprise Portal Platform, using JCR addNode within a transaction caused a javax.transaction.HeuristicMixedException (internally, org.exoplatform.services.transaction.TransactionException caused by org.jboss.cache.lock.TimeoutException) when the new node was first accessed. This has been corrected by ensuring that loading data into cache occurs outside the current transaction. + </para> + + </listitem> + </varlistentry> <!-- https://issues.jboss.org/browse/JBEPP-883 --> <varlistentry> @@ -345,6 +371,19 @@ </listitem> </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-884 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-884" /></term> + <listitem> + + + <para> + In previous versions of JBoss Enterprise Portal Platform it was possible to disable the Javascript compressor, however this would produce an error that no compressor had been set up. This version (and future versions) of the product will report a warning instead, as disabling the compressor is a deliberate choice by the user. + </para> + + </listitem> + </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-887 --> <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-887" /></term> @@ -423,7 +462,7 @@ <para> - In previous Portal versions, page definitions were held in system memory before being written when starting the Portal. This could cause an Out Of Memory error if a large number of pages were defined in the XML descriptors. The transaction has now been split so that not all page definitions are held in memory prior to being written and the Out Of Memory error is no longer encountered. + In previous Portal versions, page definitions were held in system memory before being written when starting the Portal. This could cause an <systemitem>Out Of Memory</systemitem> error if a large number of pages were defined in the XML descriptors. The transaction has now been split so that not all page definitions are held in memory prior to being written and the <systemitem>Out Of Memory</systemitem> error is no longer encountered. </para> </listitem> @@ -436,7 +475,7 @@ <para> - JBoss Enterprise Portal Platform doesn't set content-type on css-files added via gatein-resources.xml. This causes Internet Explorer 9 to ignore these css-files due to new security policy (a console message states: SEC7113: CSS was ignored due to mime type mismatch). The ResourceRequestFilter.java file has been modified to set the content type so that content-types will be set and Internet Explorer 9 will render the Portal as expected. + JBoss Enterprise Portal Platform doesn't set content-type on css-files added via <filename>gatein-resources.xml</filename>. This causes Internet Explorer 9 to ignore these css-files due to new security policy (a console message states: <systemitem>SEC7113: CSS was ignored due to mime type mismatch</systemitem>). The <filename>ResourceRequestFilter.java</filename> file has been modified to set the content type so that content-types will be set and Internet Explorer 9 will render the Portal as expected. </para> </listitem> @@ -449,7 +488,7 @@ <para> - An error that caused IntegrationCache to not be invalidated when calling invalidateAll() on PicketlinkIDMCacheService MBean has been corrected in this release. + An error that caused IntegrationCache to not be invalidated when calling <systemitem>invalidateAll()</systemitem> on <systemitem>PicketlinkIDMCacheService</systemitem> MBean has been corrected in this release. </para> </listitem> @@ -462,7 +501,7 @@ <para> - Attempting to remove an inexistent ConsumerGroup would cause a NullPointerException. JCRRegistrationPersistenceManager now properly handles the situation. + Attempting to remove an inexistent <systemitem>ConsumerGroup</systemitem> would cause a <systemitem>NullPointerException</systemitem>. <systemitem>JCRRegistrationPersistenceManager</systemitem> now properly handles the situation. </para> </listitem> @@ -475,7 +514,7 @@ <para> - Local state was improperly initialized causing a NullPointerException when attempting to insert a new ConsumerGroup. Properly retrieving the state from the JCR persistence fixed the issue. + Local state was improperly initialized causing a <systemitem>NullPointerException</systemitem> when attempting to insert a new <systemitem>ConsumerGroup</systemitem>. Properly retrieving the state from the JCR persistence fixed the issue. </para> </listitem> @@ -488,12 +527,26 @@ <para> - In previous JBoss Enterprise Portal Platform versions, calling org.exoplatform.webui.form.UIFormCheckBoxInput.setValue() with a String value of 'true', would result in the value being interpreted as 'false' as only Boolean values (not String values) were parsed. This behavior has been corrected by recognizing string values when entered and converting them to boolean values. + In previous JBoss Enterprise Portal Platform versions, calling <systemitem>org.exoplatform.webui.form.UIFormCheckBoxInput.setValue()</systemitem> with a String value of '<literal>true</literal>', would result in the value being interpreted as '<literal>false</literal>' as only Boolean values (not String values) were parsed. This behavior has been corrected by recognizing string values when entered and converting them to boolean values. </para> </listitem> </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-961 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-961" /></term> + <listitem> + + + <para> + Due to improper checks in the JCR persistence of the WSRP producer configuration, a <systemitem>NullPointerException</systemitem> was thrown when the producer did not require consumers to register with it. The issue has been addressed in this release by properly checking that a <systemitem>RegistrationPolicy</systemitem> is provided before attempting to work with it. + </para> + + </listitem> + </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-966 --> <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-966" /></term> @@ -501,7 +554,7 @@ <para> - In previous versions of JBoss Enterprise Portal Platform, the ErrorLoginServlet did not return the HTTP header content-type. This could be problematic when running the portal instance behind Apache loadbalancer. An upstream patch has been incorporated in this release to address the issue. + In previous versions of JBoss Enterprise Portal Platform, the <systemitem>ErrorLoginServlet</systemitem> did not return the HTTP header content-type. This could be problematic when running the portal instance behind Apache loadbalancer. An upstream patch has been incorporated in this release to address the issue. </para> </listitem> @@ -514,16 +567,63 @@ <para> - The JCR cache configuration files in JBoss Enterprise Portal Platform 5.1.1 have been moved from the /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/lib/exo.portal.component.common-&lt;version&gt;.jar to /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/. - -This change created problems when attempting to start upgraded versions of JBoss Enterprise Portal Platform that had the original file path stored in the JCR_CONFIG table in the database. To resolve the issue, duplicates of the configuration files have been retained in the original location. This also ensures backward compatibility, without the need to change the database. - -Note: -After this change, if configuration changes to the JCR cache are required, it is important that the JCR_CONFIG table be updated to use the "war:" prefix instead of "classpath:" (for example; file:war:/conf/jcr/jbosscache/local/config.xml). + The JCR cache configuration files in JBoss Enterprise Portal Platform 5.1.1 have been moved from <filename>/JBOSS_HOME/server/PROFILE/deploy/gatein.ear/lib/exo.portal.component.common-&lt;version&gt;.jar</filename> to <filename>/JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/</filename>. + </para> + <para> + This change created problems when attempting to start upgraded versions of JBoss Enterprise Portal Platform that had the original file path stored in the <systemitem>JCR_CONFIG</systemitem> table in the database. To resolve the issue, duplicates of the configuration files have been retained in the original location. This also ensures backward compatibility, without the need to change the database. + </para> + <para> + Note: After this change, if configuration changes to the JCR cache are required, it is important that the <systemitem>JCR_CONFIG</systemitem> table be updated to use the "war:" prefix instead of "classpath:" (for example; <filename>file:war:/conf/jcr/jbosscache/local/config.xml</filename>). </para> </listitem> </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-1010 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1010" /></term> + <listitem> + + + <para> + This release of JBoss Enterprise Portal Platform makes it possible to optimize the portal when user dashboards are not used. This can be done by modifying the <systemitem>org.exoplatform.portal.config.DataStorage</systemitem> service for a simplified implementation: <systemitem>org.exoplatform.portal.config.ConstantUserNavigationsDataStorageImpl</systemitem>. + </para> + <para> + Portal administrators should note, however, that this action will render the dashboard functionality inoperative. + </para> + + </listitem> + </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-1013 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1013" /></term> + <listitem> + + <para> + In previous versions of JBoss Enterprise Portal Platform, the demonstration iFrame portlet was configured to use the GateIn blog as an example page. However, the new GateIn blog redirects itself out of iFrames and loads in the entire browser window, overriding the current portal page. + </para> + <para> + To prevent this, the address used in the example portlet has been changed to point to the <ulink type="http" url="gatein.org"></ulink> homepage, which does not do any redirection. + </para> + </listitem> + </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-1018 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1018" /></term> + <listitem> + + + <para> + Previous versions of JBoss Enterprise Portal Platform did not honor the location of the WSRP consumer configuration file specified in <filename>wsrp-configuration.xml</filename>. This made it impossible to use any configuration file other than the default. + </para> + <para> + This version of JBoss Enterprise Portal Platform honors the configuration file location by adding the ability to configure consumers from an <systemitem>InputStream</systemitem> similar to the method used by the producer configuration. Administrators can now use custom consumer configuration files instead of needing to modify the default file. + </para> + + </listitem> + </varlistentry> <!-- https://issues.jboss.org/browse/JBEPP-1019 --> <varlistentry> @@ -538,4 +638,36 @@ </listitem> </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-1023 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1023" /></term> + <listitem> + + + <para> + A fix that was implemented to resolve an XSS vulnerabily, affected all textarea inputs and caused any gadget source code entered into the <systemitem>App Registry</systemitem> to be escaped with &lt;&gt; characters and rendered invalid to the portal. This prevented new gadgets being added to the portal as well as preventing any changes being made to existing gadgets. + </para> + <para> + The underlying issue was resolved in a fix for another bug and as a result this issue no longer presents. + </para> + + </listitem> + </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-1036 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1036" /></term> + <listitem> + + + <para> + It was found that editing a dashboard page that contained more than two gadgets would produce a <literal>NullPointerException</literal> in the <systemitem>MOPConsumerStructureProvider</systemitem> class and result in an <guilabel>Unknown error</guilabel> dialog in the User interface. + </para> + <para> + The <systemitem>MOPConsumerStructureProvider</systemitem> class has been updated to handle scenarios wherein the windowName is <literal>null</literal>, resolving this issue. + </para> + + </listitem> + </varlistentry> + </variablelist> Modified: epp/docs/branches/5.1/Release_Notes/publican.cfg =================================================================== --- epp/docs/branches/5.1/Release_Notes/publican.cfg 2011-08-29 03:43:15 UTC (rev 7241) +++ epp/docs/branches/5.1/Release_Notes/publican.cfg 2011-08-29 03:48:03 UTC (rev 7242) @@ -4,7 +4,7 @@ debug: 1 xml_lang: en-US brand: JBoss -show_remarks: 1 +#show_remarks: 1 cvs_branch: DOCS-RHEL-6 cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist cvs_pkg: JBoss_Enterprise_Portal_Platform-5.1.1_Release_Notes-5.1-web-__LANG__ \ No newline at end of file Modified: epp/docs/branches/5.1/User_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.1/User_Guide/en-US/Book_Info.xml 2011-08-29 03:43:15 UTC (rev 7241) +++ epp/docs/branches/5.1/User_Guide/en-US/Book_Info.xml 2011-08-29 03:48:03 UTC (rev 7242) @@ -7,7 +7,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.1</productnumber> <edition>2</edition> - <pubsnumber>5.1.7</pubsnumber> + <pubsnumber>5.1.8</pubsnumber> <abstract> <para> This document provides an easy to follow guide to the functions and Modified: epp/docs/branches/5.1/User_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.1/User_Guide/en-US/Revision_History.xml 2011-08-29 03:43:15 UTC (rev 7241) +++ epp/docs/branches/5.1/User_Guide/en-US/Revision_History.xml 2011-08-29 03:48:03 UTC (rev 7242) @@ -8,6 +8,20 @@ <simpara> <revhistory> <revision> + <revnumber>2-5.1.8</revnumber> + <date>Fri Aug 26 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Added "Non-visible pages and security" admonition.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>2-5.1.7</revnumber> <date>Thu Aug 25 2011</date> <author>