[gatein-commits] gatein SVN: r7038 - epp/docs/branches/5.1/Release_Notes/en-US.

Author: smumford Date: 2011-08-10 03:03:33 -0400 (Wed, 10 Aug 2011) New Revision: 7038 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/Book_Info.xml epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.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/not_documented.xml epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml Log: Updated with new issues for 5.1.1 release 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-10 01:35:44 UTC (rev 7037) +++ epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-08-10 07:03:33 UTC (rev 7038) @@ -21,6 +21,22 @@ <variablelist id="vari-5.1.1_Release_Notes-New_and_Upgraded_Components-Upgraded_Components"> <title></title> + <varlistentry> + <term>eXo Kernel</term> + <listitem> + <para> + The eXo Kernel component has been upgraded to version 2.2.9-GA + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>eXo Core</term> + <listitem> + <para> + The eXo Core component has been upgraded to version 2.3.9-GA + </para> + </listitem> + </varlistentry> <varlistentry> <term>JBoss EAP</term> <listitem> @@ -49,7 +65,7 @@ <term>eXo JCR</term> <listitem> <para> - The eXo Java Content Repository has been upgraded to version 1.12.8-GA. <!--JBEPP-728--> + The eXo Java Content Repository has been upgraded to version 1.12.9. <!--JBEPP-996--> </para> </listitem> </varlistentry> @@ -57,7 +73,7 @@ <term>PicketLink</term> <listitem> <para> - The PicketLink IDM component has been upgraded to version 1.1.8-GA. <!--JBEPP-858--> + The PicketLink IDM component has been upgraded to version 1.1.9-GA. <!--JBEPP-858--> </para> </listitem> </varlistentry> @@ -65,7 +81,7 @@ <term>Seam</term> <listitem> <para> - Seam has been upgraded to 2.2.3.EAP5 (as part of the EAP upgrade). + Seam has been upgraded to 2.2.4.EAP5 (as part of the EAP upgrade). </para> </listitem> </varlistentry> @@ -77,6 +93,14 @@ </para> </listitem> </varlistentry> + <varlistentry> + <term>Portlet Bridge</term> + <listitem> + <para> + The Portlet Bridge component has been upgraded to version 2.1.2.GA.EPP51 + </para> + </listitem> + </varlistentry> </variablelist> <para> More details about the component versions that make up JBoss Enterprise Portal Platform 5.1.1 can be found in <xref linkend="sect-5.1.1_Release_Notes-Component_Versions"/> @@ -128,7 +152,7 @@ eXo kernel </entry> <entry> - 2.2.8-GA + 2.2.9-GA </entry> </row> <row> @@ -136,7 +160,7 @@ eXo Core </entry> <entry> - 2.3.8-GA + 2.3.9-GA </entry> </row> <row> @@ -152,7 +176,7 @@ eXo JCR </entry> <entry> - 1.12.9 + 1.12.9-GA </entry> </row> <row> @@ -240,7 +264,7 @@ PicketLink IDM </entry> <entry> - 1.1.8.GA + 1.1.9.GA </entry> </row> <row> @@ -256,7 +280,7 @@ Portlet Bridge </entry> <entry> - 2.1.1.GA.EPP51 + 2.1.2.GA.EPP51 </entry> </row> <row> @@ -264,7 +288,7 @@ Seam </entry> <entry> - 2.2.3.EAP5-13.ep5.el6 + 2.2.4.EAP5 </entry> </row> <row> @@ -356,15 +380,76 @@ </section> <section> - <title><remark>NEEDINFO</remark></title> + <title><remark>NEEDINFO Issues</remark></title> <xi:include href="need_info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </section> <section> - <title><remark>Not Documented</remark></title> + <title><remark>Not Documented Issues</remark></title> <xi:include href="not_documented.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </section> - + <section> + <title>Security Related Issues</title> + <variablelist> + <title></title> + <!-- https://issues.jboss.org/browse/JBEPP-598 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-598" /></term> + <listitem> + + + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + Security vulnerabilies arising from the execution of XSS javascript entered into various portal form fields have been eradicated in this release. + </para> + <para> + The resolution to this issue also resolves the following related JIRA issues: + <simplelist> + <member><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-847"></ulink&g... + <member><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-997"></ulink&g... + <member><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-914"></ulink&g... + <member><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-365"></ulink&g... + </simplelist> + </para> + </warning> + + </listitem> + </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-597 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-597" /></term> + <listitem> + + + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + The name of a dashboard page entered by user was not properly encoded before being returned on the web browser. This allowed javascript snippets to be executed when creating a new page through the Portal Dashboard. The name of the page is now properly HTML encoded before being returned and javascript is no longer invoked when entered into page fields. + </para> + </warning> + + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-881" /></term> + <listitem> + <!-- Added on advice from Dave Jorm in the security team --> + + <warning> + <title>Not Public Yet - RHT+eXo</title> + <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. + </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. + </para> + </warning> + + </listitem> + </varlistentry> + </variablelist> + </section> <section> <title>Recommended Practices</title> <variablelist> Modified: epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml 2011-08-10 01:35:44 UTC (rev 7037) +++ epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml 2011-08-10 07:03:33 UTC (rev 7038) @@ -9,7 +9,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.1</productnumber> <edition>2.1</edition> - <pubsnumber>5.1.2</pubsnumber> + <pubsnumber>5.1.6</pubsnumber> <abstract> <para> These release notes contain important information related to JBoss Enterprise Portal Platform &VX; that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing the product. Modified: epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml 2011-08-10 01:35:44 UTC (rev 7037) +++ epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml 2011-08-10 07:03:33 UTC (rev 7038) @@ -7,83 +7,121 @@ <title>Revision History</title> <simpara> <revhistory> - <revision> - <revnumber>2.1-5.1.2</revnumber> - <date>Mon Jul 11 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> - </author> - <revdescription> - <simplelist> - <member>Added more resolved issues and 'Not Yet Documented' section.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>2.1-5.1.1</revnumber> - <date>Monday June 27 2011</date> + <revision> + <revnumber>2.1-5.1.6</revnumber> + <date>Wed Aug 10 2011</date> <author> <firstname>Scott</firstname> <surname>Mumford</surname> - <email&gt;smumford(a)redhat.com&lt;/email&gt; + <email></email> </author> - <revdescription> - <simplelist> - <member>Updated for 5.1.1 Release.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>1-1.3</revnumber> - <date>Thu Jun 02 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email&gt;smumford(a)redhat.com&lt;/email&gt; - </author> - <revdescription> - <simplelist> - <member>Added "Recommended Practices" section.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>1-1.1</revnumber> - <date>Wed May 4 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email&gt;smumford(a)redhat.com&lt;/email&gt; - </author> - <revdescription> - <simplelist> - <member>Compiled full Resolved Issues list and added component version details.</member> - </simplelist> - </revdescription> - </revision> + <revdescription> + <simplelist> + <member>Added CVE-2011-1484 to Securty section.</member> + <member>Corrected minor typographicl errors.</member> + </simplelist> + </revdescription> + </revision> <revision> - <revnumber>1-1.0</revnumber> - <date>Thu Apr 28 2011</date> - <author> + <revnumber>2.1-5.1.4</revnumber> + <date>Tue Aug 9 2011</date> + <author> <firstname>Scott</firstname> - <surname>Mumford</surname> - <email&gt;smumford(a)redhat.com&lt;/email&gt; - + <surname>Mumford</surname> + <email></email> </author> - <revdescription> + <revdescription> <simplelist> - <member>Initial draft of Release Notes created.</member> - + <member>Rebuilt using broader JIRA filters.</member> + <member>Added Security Issues section.</member> </simplelist> - </revdescription> - </revision> - + <revision> + <revnumber>2.1-5.1.3</revnumber> + <date>Fri Aug 5 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Updated to incorporate further bug fixes.</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>2.1-5.1.2</revnumber> + <date>Mon Jul 11 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Added more resolved issues and 'Not Yet Documented' section.</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>2.1-5.1.1</revnumber> + <date>Monday June 27 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email&gt;smumford(a)redhat.com&lt;/email&gt; + </author> + <revdescription> + <simplelist> + <member>Updated for 5.1.1 Release.</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>1-1.3</revnumber> + <date>Thu Jun 02 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email&gt;smumford(a)redhat.com&lt;/email&gt; + </author> + <revdescription> + <simplelist> + <member>Added "Recommended Practices" section.</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>1-1.1</revnumber> + <date>Wed May 4 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email&gt;smumford(a)redhat.com&lt;/email&gt; + </author> + <revdescription> + <simplelist> + <member>Compiled full Resolved Issues list and added component version details.</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>1-1.0</revnumber> + <date>Thu Apr 28 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email&gt;smumford(a)redhat.com&lt;/email&gt; + </author> + <revdescription> + <simplelist> + <member>Initial draft of Release Notes created.</member> + </simplelist> + </revdescription> + </revision> </revhistory> - </simpara> </appendix> 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-10 01:35:44 UTC (rev 7037) +++ epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml 2011-08-10 07:03:33 UTC (rev 7038) @@ -1,4 +1,20 @@ +<?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> -There are no known issues in this release. -</para> +<variablelist> + <title></title> + <varlistentry> + <term><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-927"></ulink&g... + <listitem> + <para> + Administrators and users should be aware that adding a gadget to any portal page other than the dashboard, will result in any user set preferences or modifications (adding entries to the TODO gadget, for example) <emphasis role="bold">not</emphasis> being saved in a persistant manner. + </para> + <para> + This limitation will be corrected in a later version of JBoss Enterprise Portal Platform. + </para> + </listitem> + </varlistentry> +</variablelist> 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-10 01:35:44 UTC (rev 7037) +++ epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml 2011-08-10 07:03:33 UTC (rev 7038) @@ -1,4 +1,62 @@ +<?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" [ +]> -<para> -There are no issues that require more information at this time. -</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-811 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-811" /></term> + <listitem> + + + <para> + Some caching and overwriting issues have been encountered when more than one portal user attempts to manipulate the same portal resource concurrently (by editing the same page at the same time, for example). + +This release of JBoss Enterprise Portal Platform includes multiple patches designed to mitigate the issue somewhat. However, this is a complex issue and further development will be required in later iterations to resolve it completely. + </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> + +</variablelist> Modified: epp/docs/branches/5.1/Release_Notes/en-US/not_documented.xml =================================================================== --- epp/docs/branches/5.1/Release_Notes/en-US/not_documented.xml 2011-08-10 01:35:44 UTC (rev 7037) +++ epp/docs/branches/5.1/Release_Notes/en-US/not_documented.xml 2011-08-10 07:03:33 UTC (rev 7038) @@ -1,20 +1,3 @@ -<?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" [ -]> - - -<variablelist> - - <!-- https://issues.jboss.org/browse/JBEPP-987 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-987" /></term> - <listitem> - - <para> - - </para> - - </listitem> - </varlistentry> - -</variablelist> +<para> +All Issues are documented. +</para> 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-10 01:35:44 UTC (rev 7037) +++ epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-08-10 07:03:33 UTC (rev 7038) @@ -4,16 +4,17 @@ <variablelist> - + <!-- https://issues.jboss.org/browse/JBEPP-400 --> <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-400" /></term> <listitem> - + + <para> Warning messages were found in the server log when starting JBoss Enterprise Portal Platform 5 without an active internet connection. This was because the Java EE Webservices Metadata Handler 2.0 schema was requested via the network at start up. The schema is now bundled with the WSRP which allows JBoss Enterprise Portal Platform to start without producing error messages if there is no internet connection. </para> - + </listitem> </varlistentry> @@ -21,11 +22,25 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-459" /></term> <listitem> + + + <para> + A thread safety issue in the breadcrumb portlet could lead to NullPointerException under load.The issue has been fixed. + </para> + + </listitem> + </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-566 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-566" /></term> + <listitem> + + <para> - A thread safety issue in the breadcrumb portlet could lead to NullPointerException under load.The issue has been fixed. + A bug which prompted users to "Save and Close" an Edit Portlet dialogue if a tab in the window was clicked but the mouse cursor was removed from the tab before the mouse button was released has been corrected in this release. </para> - + </listitem> </varlistentry> @@ -33,75 +48,80 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-568" /></term> <listitem> - + + <para> In previous releases of JBoss Enterprise Portal Platform, users found that, when creating sub-nodes of system nodes (portal navigation, group navigation, register etc.), these new nodes where not visible once created. This issue, and a related issue encountered when attempting to 'cut' sub-nodes of system nodes, have been resolved in this latest release. </para> - + </listitem> </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-597 --> + <!-- https://issues.jboss.org/browse/JBEPP-723 --> <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-597" /></term> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-723" /></term> <listitem> - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - The name of a dashboard page entered by user was not properly encoded before being returned on the web browser. This allowed javascript snippets to be executed when creating a new page through the Portal Dashboard. The name of the page is now properly HTML encoded before being returned and javascript is no longer invoked when entered into page fields. - </para> - </warning> - + + + <para> + A bug in the UIUserInGroup.setValues() code caused previous versions of JBoss Enterprise Portal Platform to throw an error when users attempted to navigate to a new page withing the Group management view of the Organization portlet by any method other than the page indicator buttons. This release includes a patch which resolves this issue and allows users to navigate between pages using various UI elements. + </para> + <para> + Further details can be found in <ulink type="http" url="https://issues.jboss.org/browse/GTNPORTAL-1356"></ul... + </para> + </listitem> </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-598 --> + <!-- https://issues.jboss.org/browse/JBEPP-733 --> <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-598" /></term> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-733" /></term> <listitem> - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - Security vulnerabilies arising from the execution of XSS javascript entered into various portal form fields have been eradicated in this release. - </para> - <para> - The resolution to this issue also resolves the following related JIRA issues: - <simplelist> - <member><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-847"></ulink&g... - <member><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-997"></ulink&g... - </simplelist> - </para> - </warning> - + + + <para> + A bug cause the JBoss Enterprise Portal Platform upload service to not work properly with Internet Explorer 7. As a result, any application using the upload service (such as Site Publisher) would not behave correctly with this web browser unless a name was provided. The bug has been fixed and the upload service now works as expected in all browsers (including IE7). + </para> + </listitem> </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-723 --> + <!-- https://issues.jboss.org/browse/JBEPP-768 --> <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-723" /></term> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-768" /></term> <listitem> - + + <para> - A bug in the <parameter>UIUserInGroup.setValues()</parameter> code caused previous versions of EPP to throw an error when users attempted to navigate to a new page withing the Group management view of the Organization portlet by any method other than the page indicator buttons. This release includes a patch which resolves this issue and allows users to navigate between pages using various UI elements. + An issue with the FileUpload demo not populating file information fields has been corrected with an upgrade to the Portlet Bridge component. </para> + + </listitem> + </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-771 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-771" /></term> + <listitem> + + <para> - Further details can be found in <ulink type="http" url="https://issues.jboss.org/browse/GTNPORTAL-1356"></ul...;. + Prior to this release, CAS ticket validation failed when the JBoss Enterprise Portal Platform instance was set up with SSL. This has been fixed with an upgrade to the SSO component. CAS ticket validation now works as expected with http and https addresses. </para> - + </listitem> </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-733 --> + <!-- https://issues.jboss.org/browse/JBEPP-772 --> <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-733" /></term> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-772" /></term> <listitem> - + + <para> - A bug cause the JBoss Enterprise Portal Platform upload service to not work properly with Internet Explorer 7. As a result, any application using the upload service (such as Site Publisher) would not behave correctly with this web browser unless a name was provided. The bug has been fixed and the upload service now works as expected in all browsers (including IE7). + In this release of JBoss Enterprise Portal Platform, JndiMultiplexedJBossCacheRegionFactory is used for IDM second level caching. This makes it easier to switch to TCP. </para> - + </listitem> </varlistentry> @@ -109,11 +129,12 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-773" /></term> <listitem> - + + <para> - A bug prevented the 'Preferences' tab from appearing in some portlets. The tab would only appear in portlets that were customized during the first deployment through the portal.xml descriptor. Non-customized portlets would not show a 'Preferences' tab. The <filename>UIFormInputSet.java</filename> and <filename>UIPortletForm.java</filename> files have been patched to fix the issue and now the tab now appears in all portlets that have configurable preferences. + A bug prevented the 'Preferences' tab from appearing in some portlets. The tab would only appear in portlets that were customized during the first deployment through the portal.xml descriptor. Non-customized portlets would not show a 'Preferences' tab. The UIFormInputSet.java and UIPortletForm.java files have been patched to fix the issue and now the tab now appears in all portlets that have configurable preferences. </para> - + </listitem> </varlistentry> @@ -121,11 +142,12 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-780" /></term> <listitem> - + + <para> - The two JBoss Cache instances created by PicketLink were calling on the same configuration file in <filename>idm-configuration.xml</filename> and, as a result, were using the same cluster names. This could lead to conflicts as the same JBoss Cache instance could join the same channel twice. Separate configuration files were added to the distribution package and the Portal configuration was customized to call on the different files. JBoss Cache instances can now run simultaneously without conflict. + The two JBoss Cache instances created by PicketLink were calling on the same configuration file in idm-configuration.xml and, as a result, were using the same cluster names. This could lead to conflicts as the same JBoss Cache instance could join the same channel twice. Separate configuration files were added to the distribution package and the Portal configuration was customized to call on the different files. JBoss Cache instances can now run simultaneously without conflict. </para> - + </listitem> </varlistentry> @@ -133,11 +155,12 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-782" /></term> <listitem> - + + <para> - It was found that separate instances of epp 5.1 deployed on the same network and started with the 'Default' server profile would communicate as if in a cluster. This behavior has been resolved with new cluster configuration. + It was found that separate instances of JBoss Enterprise Portal Platform 5.1 deployed on the same network and started with the 'Default' server profile would communicate as if in a cluster. This behavior has been resolved with new cluster configuration. </para> - + </listitem> </varlistentry> @@ -145,11 +168,12 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-786" /></term> <listitem> - + + <para> - An error in the XML definition in the <filename>gatein_objects_1_0</filename> file was found to cause errors in Eclipse environments when using the default <filename>pages.xml</filename> or <filename>navigation.xml</filename> files. This was because the file did not include '<parameter>VISIBLE</parameter>' in the allowed values of the '<literal>visibility</literal>' element. This error has been corrected. + An error in the XML definition in the gatein_objects_1_0 file was found to cause errors in Eclipse environments when using the default pages.xml or navigation.xml files. This was because the file did not include 'VISIBLE' in the allowed values of the 'visibility' element. This error has been corrected. </para> - + </listitem> </varlistentry> @@ -157,14 +181,13 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-788" /></term> <listitem> - + + <para> - In previous versions of JBoss Enterprise Portal Platform, WSRP strict mode was not properly restored when the product was started. This has now been resolved. + Custom WSRP RegistrationPolicy implementations were not properly handled in previous versions of JBoss Enterprise Portal Platform. +This caused an exception when the product was started. This issue has been resolved. </para> - <para> - <remark>Possibly the same issue as JBEPP-857. Awaiting feedback from Chris Laprun.</remark> - </para> - + </listitem> </varlistentry> @@ -172,11 +195,25 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-794" /></term> <listitem> + + + <para> + When adding resources (js, css, etc) to the Head of the HTML response with the doHeaders method a bug was encountered which caused those resources to be added twice. A patch has been applied to fix the bug and new resources are now only linked once. + </para> + + </listitem> + </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-813 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-813" /></term> + <listitem> + + <para> - When adding resources (js, css, etc) to the Head of the HTML response with the <literal>doHeaders</literal> method a bug was encountered which caused those resources to be added twice. A patch has been applied to fix the bug and new resources are now only linked once. + An issue with navigational elements not being correctly translated into languages with a country variant has been resolved in this release. Navigation elements are now translated correctly. </para> - + </listitem> </varlistentry> @@ -184,11 +221,25 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-848" /></term> <listitem> + + + <para> + A bug in data caching prevented some changes to Portal navigation from reloading in real time. When changing a group navigation priority, the reordering of the groups was only happening after a log-out. The UIPageNavigationForm.java has been patched to correct this and navigation changes now update immediately, without the user needing to log-out. + </para> + + </listitem> + </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-856 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-856" /></term> + <listitem> + + <para> - A bug in data caching prevented some changes to Portal navigation from reloading in real time. When changing a group navigation priority, the reordering of the groups was only happening after a log-out. The <filename>UIPageNavigationForm.java</filename> has been patched to correct this and navigation changes now update immediately, without the user needing to log-out. + Problems encountered when trying to run various gadgets (including the RSS Reader) in a portal instance using secure https mode has been resolved in this release. All gadgets should now render and behave as expect in both http and https modes. </para> - + </listitem> </varlistentry> @@ -196,26 +247,64 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-857" /></term> <listitem> + + + <para> + WSRP Strict mode was previously set only via listeners, which were not triggered at start up since they don't yet exist at that time. This meant that WSRP Strict Mode was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from persistent state at start up. + </para> + + </listitem> + </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-873 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-873" /></term> + <listitem> + + <para> - WSRP Strict mode was previously set only via listeners, which were not triggered at startup since they don't yet exist at that time. This meant that WSRP Strict Mode was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from persistent state at startup. - </para> - <para> - <remark>Possibly the same issue as JBEPP-788. Awaiting feedback from Chris Laprun.</remark> + Previous versions of JBoss Enterprise Portal Platform encountered problems when attempting to access files though the WebDAV interface if the file name included special characters. An upstream patch ensures characters are escaped correctly and resolves the issue. </para> + + </listitem> + </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-883 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-883" /></term> + <listitem> + + + <para> + Some mistranslations in webui_ja.properties have been corrected in this release of JBoss Enterprise Portal Platform. + </para> + </listitem> </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-887 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-887" /></term> + <listitem> + + + <para> + A conflict between the javax.portlet.faces.extension.resetModeViewId the portlet.xml configuration file and the error page specified by the error-page tag in web.xml has been resolved in an upgrade to the JBoss Portlet Bridge component. + </para> + + </listitem> + </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-890 --> <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-890" /></term> <listitem> - + + <para> - Exceptions thrown by the <literal>handleFaceletNotFound</literal> method (when a facelet file was not found) were being obscured by <literal>FaceletViewHandler</literal> as the response object was not a subtype of <literal>HttpServletResponse</literal> (it is a instance of PortletResponse). <filename>FaceletPortletViewHandler.java</filename> has been updated to handle instances of both <literal>HttpServletResponse</literal> and <literal>PortletResponse</literal> response objects. + Exceptions thrown by the handleFaceletNotFound method (when a facelet file was not found) were being obscured by FaceletViewHandler as the response object was not a subtype of HttpServletResponse (it is a instance of PortletResponse). FaceletPortletViewHandler.java has been updated to handle instances of both HttpServletResponse and PortletResponse response objects. </para> - + </listitem> </varlistentry> @@ -223,11 +312,12 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-896" /></term> <listitem> - + + <para> - The Single Sign On (SSO) <literal>AbstractLogoutFilter</literal> in JBoss Enterprise Portal Platform would read request parameters before setting the character encoding. When a form was submitted with non-UTF-8 characters (while SSO was enabled) the values could be garbled on output. An upgrade of the SSO component to version 1.0.2-epp-GA (which includes a patch to the <literal>AbstractLogoutFilter</literal> code) resolves this issue and Non-UTF-8 characters are now specified correctly. + The Single Sign On (SSO) AbstractLogoutFilter in JBoss Enterprise Portal Platform would read request parameters before setting the character encoding. When a form was submitted with non-UTF-8 characters (while SSO was enabled) the values could be garbled on output. An upgrade of the SSO component to version 1.0.2-EPP-GA (which includes a patch to the AbstractLogoutFilter code) resolves this issue and Non-UTF-8 characters are now specified correctly. </para> - + </listitem> </varlistentry> @@ -235,11 +325,12 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-902" /></term> <listitem> - + + <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. </para> - + </listitem> </varlistentry> @@ -247,16 +338,46 @@ <varlistentry> <term><ulink url="https://issues.jboss.org/browse/JBEPP-904" /></term> <listitem> + + + <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. + </para> + + </listitem> + </varlistentry> + <!-- https://issues.jboss.org/browse/JBEPP-966 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-966" /></term> + <listitem> + + <para> - 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 and output a console message: + 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. + </para> + + </listitem> + </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-987 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-987" /></term> + <listitem> + + + <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-&amp;lt;version&amp;gt;.jar to /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/. </para> -<screen>SEC7113: CSS was ignored due to mime type mismatch -</screen> <para> - 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. + 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. </para> - + <note> + <title>JCR_CONFIG Prefixes:</title> + <para> + 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). + </para> + </note> </listitem> </varlistentry>