Author: smumford Date: 2011-06-01 01:31:35 -0400 (Wed, 01 Jun 2011) New Revision: 6582 Modified: epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.ent 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/resolved_issues.xml Log: Updated for 5.1.1 Release Modified: epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.ent =================================================================== --- epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.ent 2011-05-31 15:12:57 UTC (rev 6581) +++ epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.ent 2011-06-01 05:31:35 UTC (rev 6582) @@ -7,3 +7,8 @@ <!-- Corporate Specifics: --> <!ENTITY YEAR "2011"> <!ENTITY HOLDER "Red Hat, Inc"> + +<!-- Version Specifcs: --> +<!ENTITY VX "5"> +<!ENTITY VY "5.1"> +<!ENTITY VZ "5.1.1"> \ No newline at end of file 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-05-31 15:12:57 UTC (rev 6581) +++ epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-06-01 05:31:35 UTC (rev 6582) @@ -369,7 +369,7 @@ <section id="sect-5.1.1_Release_Notes-Known_Issues"> <title>Known Issues</title> <para> - There are no known issues in this release of JBoss Enterprise Portal Platform + There are no known issues in this release of JBoss Enterprise Portal Platform. </para> <!-- <para> The following is a list of known issues in this release: @@ -377,11 +377,32 @@ <xi:include href="known_issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --> </section> - <!-- <section> + <section> + <title>Recommended Practices</title> + <variablelist> + <!-- https://issues.jboss.org/browse/JBEPP-610 --> + <varlistentry> + <term>Plain Text Passwords</term> + <listitem> + <para> + JBoss Enterprise Portal Platform administrators should be aware that passwords saved by users who chose the <guilabel>Remember Me</guilabel> option when logging in are stored in the underlying JCR in plain text. This creates a possible security risk as user passwords could be obtained with an SQL query. + </para> + <para> + While this is the default behavior of JBoss Enterprise Portal Platform, administrators can negate this risk by either disabling the <guilabel>Remember Me</guilabel> option or encrypting the passwords stored in the JCR. + </para> + <para> + Instructions for implementing both of these solutions are included in section 14.1 of the JBoss Enterprise Portal Platform Reference Guide which is available at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platf...;. + </para> + </listitem> + </varlistentry> + </variablelist> + </section> + + <!-- <section> <title><remark>NEEDINFO</remark></title> <xi:include href="need_info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </section> --> - + <section id="sect-5.1.1_Release_Notes-Migration"> <title>Migration</title> <para> @@ -399,9 +420,7 @@ </section> <section id="sect-5.1.1_Release_Notes-Site_Publisher"> - <title><remark>Site Publisher</remark> - </title> - <remark>DOCS NOTE: Do we still want this here?</remark> + <title>Site Publisher</title> <para> Site Publisher provides many additional features for organizations looking to enable line of business resources to directly manage sites, pages and content within the context of the portal versus through integration with an external web content management system. </para> 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-05-31 15:12:57 UTC (rev 6581) +++ epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml 2011-06-01 05:31:35 UTC (rev 6582) @@ -6,10 +6,10 @@ <articleinfo id="arti-5.1.1_Release_Notes-a5.1.1_Release_Notes"> <title>5.1.1 Release Notes</title> <subtitle>For use with JBoss Enterprise Portal Platform 5.1.1</subtitle> - <edition>1</edition> - <pubsnumber>1.1</pubsnumber> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.1</productnumber> + <edition>1</edition> + <pubsnumber>1.2</pubsnumber> <abstract> <para> These release notes contain important information related to JBoss Enterprise Portal Platform 5.1.1 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-05-31 15:12:57 UTC (rev 6581) +++ epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml 2011-06-01 05:31:35 UTC (rev 6582) @@ -8,6 +8,20 @@ <simpara> <revhistory> <revision> + <revnumber>1-1.2</revnumber> + <date>Mon May 23 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> 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-05-31 15:12:57 UTC (rev 6581) +++ epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-06-01 05:31:35 UTC (rev 6582) @@ -1,159 +1,139 @@ -<?xml version='1.0' encoding='utf-8' ?> +<?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" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "5.1.1_Release_Notes.ent"> -%BOOK_ENTITIES; ]> -<variablelist> - <!-- release notes text customfield_12310211 --> <!-- 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> +<!-- release notes text customfield_12310211 --> - </listitem> - </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-459 --> <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> +<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> - </listitem> + <!-- https://issues.jboss.org/browse/JBEPP-459 --> + <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> - </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-597 --> <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-597" /></term> - <listitem> - <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> + <!-- https://issues.jboss.org/browse/JBEPP-597 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-597" /></term> + <listitem> + <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> + </listitem> + </varlistentry> - </listitem> + <!-- https://issues.jboss.org/browse/JBEPP-733 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-733" /></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). + </para> + </listitem> + </varlistentry> - </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-610 --> <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-610" /></term> - <listitem> - <para> - Previous versions of JBoss Enterprise Portal Platform wrote saved passwords to the JCR database in plain text. This created a possible security risk as user passwords could be obtained with an SQL query. Passwords are now encrypted when written to the database, negating the security risk. - </para> + <!-- https://issues.jboss.org/browse/JBEPP-773 --> + <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 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> - </listitem> + <!-- https://issues.jboss.org/browse/JBEPP-780 --> + <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 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> - </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-733 --> <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-733" /></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). - </para> + <!-- https://issues.jboss.org/browse/JBEPP-794 --> + <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> - </listitem> + <!-- https://issues.jboss.org/browse/JBEPP-848 --> + <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> - </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-773 --> <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 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> + <!-- https://issues.jboss.org/browse/JBEPP-857 --> + <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 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> + </listitem> + </varlistentry> - </listitem> + <!-- 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 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> - </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-780 --> <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 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> + <!-- https://issues.jboss.org/browse/JBEPP-896 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-896" /></term> + <listitem> + <para> + 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> - </listitem> + <!-- https://issues.jboss.org/browse/JBEPP-902 --> + <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> - </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-794 --> <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> + <!-- https://issues.jboss.org/browse/JBEPP-904 --> + <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> - </listitem> - - </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-848 --> <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-857 --> <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 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> - - </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 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> - <!-- https://issues.jboss.org/browse/JBEPP-896 --> <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-896" /></term> - <listitem> - <para> - 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> - <!-- https://issues.jboss.org/browse/JBEPP-899 --> <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-899" /></term> - <listitem> - <para> - MOPPortalStructuralAccess was improperly closing the POMSession that was under control of another Portal component, leaving that component unable to properly access JCR state. An NPE was thrown when other components tried to access the closed POMSession. MOPPortalStructureAccess now simply saves the session instead of saving *and* closing it. Since MOPPortalStructuralAccess doesn't close the POMSession anymore, it can still be used by components upstream without issue. - </para> - - </listitem> - - </varlistentry> - <!-- https://issues.jboss.org/browse/JBEPP-902 --> <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> - <!-- https://issues.jboss.org/browse/JBEPP-904 --> <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> - </variablelist> -