Author: smumford Date: 2010-11-10 02:02:23 -0500 (Wed, 10 Nov 2010) New Revision: 5001 Modified: epp/docs/branches/EPP_5_1_Branch/Release_Notes/en-US/5.1.0_Release_Notes.xml Log: JBEPP-603: Added more JIRA descriptions. Removed some based on new input from theute. Modified: epp/docs/branches/EPP_5_1_Branch/Release_Notes/en-US/5.1.0_Release_Notes.xml =================================================================== --- epp/docs/branches/EPP_5_1_Branch/Release_Notes/en-US/5.1.0_Release_Notes.xml 2010-11-10 07:00:09 UTC (rev 5000) +++ epp/docs/branches/EPP_5_1_Branch/Release_Notes/en-US/5.1.0_Release_Notes.xml 2010-11-10 07:02:23 UTC (rev 5001) @@ -239,6 +239,33 @@ <variablelist> <title><emphasis role="bold">Issues fixed in the product:</emphasis></title> <varlistentry> + <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-546"></ulink>... + <listitem> + <para> + A bug that affected the selection of users being added to a group has been fixed. + </para> + <para> + Prior to this release, user selections made on the first page of the user list, should the list span multiple pages, were lost when navigating to subsequent pages. + </para> + <para> + The user selections are now persistent across pages. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-577"></ulink>... + <listitem> + <para> + Previous versions of &PRODUCT; used <literal>HashMap</literal> in the <literal>ConfigurationManager</literal> class for multithreaded environments. This caused the following message to appear in logs while using the product under heavy load: + </para> +<screen>java.lang.Exception: Cannot find the configuration for the component org.exoplatform.portal.webui.container.UIContainerList, configId null +</screen> + <para> + In the latest release, <literal>HashMap</literal> has been replaced with <literal>ConcurrentHashMap</literal>, which accepts default values for initial capacity, load factor and <literal>concurrencyLevel</literal> and resolves the exception. + </para> + </listitem> + </varlistentry> + <varlistentry> <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-508" /></term> <listitem> <para> @@ -383,6 +410,39 @@ </para> </listitem> </varlistentry> + <varlistentry> + <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-579"></ulink>... + <listitem> + <para> + In previous releases, a <literal>NullPointerException</literal> would be encountered if no <filename>navigation.xml</filename> had been created for an LDAP user. + </para> + <para> + A change to code in <filename>UIUserToolBarDashboardPortlet.gtmpl</filename> has corrected this issue by including a clause for this circumstance. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-484"></ulink>... + <listitem> + <para> + Users who attempted to use the inline composer to change a portal's language locale to be country specific (Chinese, for example), would find that the locale reverted to English after the change was saved. + </para> + <para> + This has been corrected with an update to code in <filename>UIPortalForm.java</filename>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-470"></ulink>... + <listitem> + <para> + Hardcoded portlet ID format expectations in the Application Registry produced an exception when adding a new remotable portlet to a category if EPP was the producer (either self-consuming or from another EPP instance). + </para> + <para> + A workaround has been introduced to the code to avoid this issue. + </para> + </listitem> + </varlistentry> </variablelist> <!--Close list: Fixed in Product--> <variablelist> @@ -414,6 +474,39 @@ </para> </listitem> </varlistentry> + <varlistentry> + <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-490"></ulink>... + <listitem> + <para> + When editing a portal page layout by deleting a container that has <literal>PageBody</literal> content, users were able to continue deleting the container (by clicking the <guilabel>Finish</guilabel> button) while a warning message was displayed. + </para> + <para> + This issue has been corrected. The <guilabel>Finish</guilabel> button no longer operates while warnings are displayed. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-482"></ulink>... + <listitem> + <para> + Page and portlet titles were not localizable in previous releases of &PRODUCT;. + </para> + <para> + These titles can now be localized either through keys in <filename>pages.xml</filename> or via the administration interface. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-480"></ulink>... + <listitem> + <para> + The LDAP implementation has been updated to support paginated queries. + </para> + <para> + Queries that return entries exceeding the limitations of the LDAP server are now separated into smaller queries that fall within the LDAP limitations. + </para> + </listitem> + </varlistentry> </variablelist> <!--Close list: New Features--> <variablelist> @@ -435,27 +528,7 @@ The following is a list of known issues in this release: </para> <variablelist> - - <varlistentry> - <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-546"></ulink>... - <listitem> - <para> - A bug has been found that affects the selection of users being added to a group. User selections made on the first page of the user list, should the list span multiple pages, are lost when navigating to subsequent pages. - </para> - <para> - The user selections should be persistent across pages. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-579"></ulink>... - <listitem> - <para> - A <emphasis role="bold">NullPointerException</emphasis> is encountered if no <filename>navigation.xml</filename> file has been created for an LDAP user. - </para> - </listitem> - </varlistentry> - <varlistentry> + <varlistentry> <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-600"></ulink>... <listitem> <para> @@ -486,14 +559,6 @@ </listitem> </varlistentry> <varlistentry> - <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-592"></ulink>... - <listitem> - <para> - Editing the <emphasis role="bold">Template</emphasis> field of the banner or footer portlet preferences to any non-default value can result in changes not being validated as the portlets, by default, require a groovy template. - </para> - </listitem> - </varlistentry> - <varlistentry> <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-570"></ulink>... <listitem> <para> @@ -525,7 +590,7 @@ Customers should be aware that passwords entered into the portal login form and submitted with the <emphasis>Remember me</emphasis> option are stored in the JCR database in plain text. This presents a possible security vulnerability. </para> <important> - <title><emphasis role="bold">DOC NOTE</emphasis></title> + <title><emphasis role="bold"></emphasis></title> <para> As yet there is no workaround/solution to this security issue. </para> @@ -533,10 +598,10 @@ </listitem> </varlistentry> <varlistentry> - <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-593"></ulink>... + <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-614"></ulink>... <listitem> <para> - Safari and Firefox 3.6 users are advised that the 'captcha' security device may not refresh when registering new users, meaning that the same alphanumeric code will be presented when adding another user. + An issue has been reported about EPP caching recently changed passwords. After a user changes their password, both the old and new password will allow them to log into the portal. This situation persists until the portal is restarted. </para> <important> <title><emphasis role="bold">DOC NOTE</emphasis></title> @@ -563,7 +628,6 @@ <para> Red Hat JBoss Customer Support can be accessed <ulink type="http" url="https://www.redhat.com/apps/support/">here</ulink>;. </para> - </section> <section id="sect-Release_Notes-Site_Publisher">