Author: smumford Date: 2010-09-20 03:54:11 -0400 (Mon, 20 Sep 2010) New Revision: 4248 Modified: epp/docs/branches/EPP_5_0_Branch/5.0.1_Release_Notes/en-US/5.0.1_Release_Notes.xml epp/docs/branches/EPP_5_0_Branch/5.0.1_Release_Notes/en-US/Book_Info.xml epp/docs/branches/EPP_5_0_Branch/5.0.1_Release_Notes/en-US/Revision_History.xml Log: JBEPP-377: Updated Release Notes based on review feedback Modified: epp/docs/branches/EPP_5_0_Branch/5.0.1_Release_Notes/en-US/5.0.1_Release_Notes.xml =================================================================== --- epp/docs/branches/EPP_5_0_Branch/5.0.1_Release_Notes/en-US/5.0.1_Release_Notes.xml 2010-09-20 06:00:10 UTC (rev 4247) +++ epp/docs/branches/EPP_5_0_Branch/5.0.1_Release_Notes/en-US/5.0.1_Release_Notes.xml 2010-09-20 07:54:11 UTC (rev 4248) @@ -188,39 +188,30 @@ <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-452"></ulink>... <listitem> <para> - &PRODUCT; used <literal>request.getLocale()</literal> to localize a <literal>ResourceBundle</literal> which only reflected a user's <emphasis>browser</emphasis> language preference, while the rest of the portal employs a more complex logic to determine what locale is used. Under certain circumstances this mismatch caused the localization to switch incorrectly. + &PRODUCT;'s <literal>request.getLocale()</literal> only reflected a user's <emphasis>browser</emphasis> language preference, regardless of what language was set in the portal itself. </para> <para> - A <literal>LocalizationFilter</literal> to wrap <literal>HttpServletRequest</literal> and override <literal>getLocale()</literal> / <literal>getLocales()</literal> and return values that are in sync with the rest of the portal was installed to address this issue. This creates a universal solution for all extra-portal-page resources that are served via non-portal-page URLs, and are outside regular portal page processing pipeline. + A <literal>LocalizationFilter</literal> to wrap <literal>HttpServletRequest</literal> and override <literal>getLocale()</literal> / <literal>getLocales()</literal> and return values that are in sync with the rest of the portal was installed to address this issue. </para> <para> As a result, portlets use the preferred locale of a user and not the locale from the http servlet request. </para> - <para> - This fix has also corrected language issues wherein the locale was not set correctly after a failed login attempt (<ulink type="http" url="https://jira.jboss.org/browse/JBEPP-403"></ulink>) and where language setting for languages with country variants, such as Chinese - China and Chinese - Taiwan, were lost at re-login. (<ulink type="http" url="https://jira.jboss.org/browse/JBEPP-383"></ulink>). - </para> - <note> - <title>DOCS NOTE</title> - <para> - (Information gathered from <ulink type="http" url="https://jira.jboss.org/browse/GTNPORTAL-1355"></ulink>) - </para> - </note> - </listitem> </varlistentry> <varlistentry> - <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-451"></ulink>... + <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-403"></ulink>... <listitem> <para> - <literal>NullPointerExceptions</literal> were being encountered when a new <literal>UIFormMultiValueInputset</literal> was created using a <literal>UIComponent</literal> without some arguments being explicitly set. <filename>UIFormMultiValueInputset.java</filename> has been modified to pass <literal>parameterTypes</literal> and <literal>parameterValues</literal> to a constructor when a new <literal>UIFormMultilValueInputset</literal> is created. This corrects the exceptions encountered when invoking a non-default constructor. + The <literal>LocalizationFilter</literal> fix implemented for <ulink type="http" url="https://jira.jboss.org/browse/JBEPP-452"></ulink> also corrected an issue wherein a failed login attempt would present the login form in an incorrect language (that is; not the language set for the portal). </para> - <note> - <title>DOCS NOTE</title> - + </listitem> + </varlistentry> + <varlistentry> + <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-383"></ulink>... + <listitem> <para> - (Information sourced from <ulink type="http" url="https://jira.jboss.org/browse/GTNPORTAL-1223"></ulin...;, <ulink type="http" url="https://jira.jboss.org/browse/GTNPORTAL-1225"></ulin... and <ulink type="http" url="https://jira.jboss.org/browse/JBEPP-405"></ulink>) + The <literal>LocalizationFilter</literal> fix also corrected an issue which caused language settings for languages with country variants (such as Chinese - China and Chinese - Taiwan) were not stored between logins. </para> - </note> </listitem> </varlistentry> <varlistentry> @@ -230,7 +221,7 @@ The Shindig Gadget Server was reporting malformed security tokens after a gadget was added to a portal. The error was originating from the <literal>org.apache.shindig.gadgets.servlet.RpcServlet</literal>'s <literal>doPost</literal> processing method. This method of reading POST requests from the servlet's input stream was being corrupted if the <literal>InputStream</literal> had already been read (in the recorded case, by <literal>RequestDumperValve</literal>). </para> <para> - This error was resolved with a component upgrade to Apache Shindig 1.0-r790473-Patch03 which allows a reset of the input stream before the <literal>doPost</literal> method is invoked. + This error was resolved with a patch to Apache Shindig which allows a reset of the input stream before the <literal>doPost</literal> method is invoked. </para> </listitem> </varlistentry> @@ -243,18 +234,40 @@ <para> This issue has been fixed with an updated PicketLink jar. </para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-363"></ulink>... + <listitem> <para> - This fix has also resolved an issue encountered when deleting registered portal users from LDAP. Information about users deleted from LDAP would still be retained in the database and those user accounts would appear in the portal user list. If one of these legacy accounts was then edited, the inconsistences would prevent any further login attempts from succeeding until the user session was cleared. (<ulink type="http" url="https://jira.jboss.org/browse/JBEPP-363"></ulink>). + The updated PicketLink jar has also resolved an issue encountered when deleting registered portal users from LDAP. </para> + <para> + Information about users deleted from LDAP would still be retained in the database and those user accounts would appear in the portal user list. If one of these legacy accounts was then edited, the inconsistences would prevent any further login attempts from succeeding until the user session was cleared. + </para> </listitem> </varlistentry> <varlistentry> + <term><ulink type="http" url="https://jira.jboss.org/browse/GTNPORTAL-1309"></ulin... + <listitem> + <para> + The updated PicketLink IDM component removes case-sensitivity from the username field of the portal login page. + </para> + <para> + This allows users whose login names contain capital latters to authenticate successfully, regardless of the case used in the username field of the login form. + </para> + <para> + Note that the password field remains case-sensitive for security. + </para> + </listitem> + </varlistentry> + <varlistentry> <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-368"></ulink>... <listitem> <para> The datasource defined in <filename>jboss-epp-5.0/jboss-as/docs/examples/portal/gatein-sample-portal-ds.xml</filename> has been updated from <literal>local-tx-datasourc</literal> to <literal>no-tx-datasource</literal>. - </para> - <para> + </para> + <para> This update prevents exceptions being thrown by the JCR when the name of the datasource in <filename>server/default/deploy/gatein-ds.xml</filename> is changed to suit operational requirements. </para> </listitem> @@ -263,12 +276,9 @@ <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-342"></ulink>... <listitem> <para> - Node names were being dispalyed incorrectly if the name contained special characters when the site language was changed to a different locale. For example; if the site language was changed to German the SiteMap node would display as <literal>Seiten&amp;uuml&semi;bersicht</literal> instead of <emphasis role="bold">Seitenübersicht</emphasis>. + Node names were being displayed incorrectly if they contained accentuated characters. For example; if the site language was German, the SiteMap node would display as <literal>Seiten&amp;uuml&semi;bersicht</literal> instead of <emphasis role="bold">Seitenübersicht</emphasis>. </para> <para> - Badly escaped special characters caused these characters to render <emphasis>literally</emphasis> on the page instead of being rendered as human-readable special characters. - </para> - <para> Language <filename>.properties</filename> files have been updated to escape special characters correctly and languages that contain special characters now render as expected. </para> </listitem> @@ -285,11 +295,17 @@ <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-167"></ulink>... <listitem> <para> - This release includes a copy of the <filename>jcip-annotations.jar</filename> in the <filename>/server/default/lib</filename> directory. + A bug in the IBM JDK (1.5) would prevent the <literal>HAPartition</literal> service from starting. This, in turn, prevented JBoss AS from starting correctly when using the <literal>all</literal> configuration. The HAPartition would return the following error: </para> +<screen>ERROR [AbstractKernelController] Error installing to Start: name=HAPartition state=Create +org.jboss.cache.config.ConfigurationException: Unable to build interceptor chain +</screen> <para> - This file is needed to avoid an exception causing the <literal>HAPartition</literal> service to fail to start when using IBM JDK 1.5. + This release includes a copy of the <filename>jcip-annotations.jar</filename> in the <filename>/server/default/lib</filename> directory as a workaround. </para> + <para> + This file is needed to avoid the above exception and may be removed in a later release. + </para> </listitem> </varlistentry> </variablelist> @@ -303,11 +319,17 @@ A list of general issues in this release can be found at: </para> <para> - <ulink type="http" url="https://jira.jboss.org/secure/IssueNavigator.jspa?reset=true&am... + <ulink type="http" url="https://jira.jboss.org/secure/IssueNavigator.jspa?mode=hide&... </para> + <warning> + <title>DOC NOTE</title> + <para> + Is this list appropriate to offer readers? It points to a JIRA filter for all Open/Unresolved bugs attached to EPP 5.0.1 (so it doesn't catch related JIRAs for GTN or PLIDM etc, unless they're cloned to JBEPP). + </para> + </warning> </section> - <section> +<!-- <section> <title>Security Issues</title> <variablelist> <varlistentry> @@ -322,43 +344,13 @@ </listitem> </varlistentry> </variablelist> - </section> + </section>--> - <section id="sect-Release_Notes-_Known_Issues_with_this_release_-Component_Specific_Known_Issues"> - <title>Specific Known Issues</title> - <variablelist> - <varlistentry> - <term><ulink type="http" url="https://jira.jboss.org/browse/JBEPP-406"></ulink>... - <listitem> - <para> - This issue has no information and I wasn't able to determine the problem from <ulink type="http" url="https://jira.jboss.org/browse/GTNPORTAL-756"></ulink... or <ulink type="http" url="http://jira.exoplatform.org/browse/PORTAL-3720"></ul...;. - </para> - <para> - Please supply a starter draft paragraph and I will edit it for the next burn of these Release Notes. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink type="http" url="https://jira.jboss.org/">https://jira.jboss.org/</ul... - <listitem> - <para> - Issue. - </para> - </listitem> - </varlistentry> - </variablelist> - </section> - </section> <section> <title>Recommended Practices</title> - <note> - <title>DOC TODO</title> - <para> - Is this section still required/relevant? - </para> - </note> +<!--DOC TODO: This Information should be in the Installtion Guide. Move for 5.1.0 release.--> <para> &PRODUCT; &VERSION; includes four pre-configured user accounts for testing and evaluation puposes. These accounts can be used for direct access to the portal. </para> @@ -414,12 +406,6 @@ </warning> <section> <title>Site Publisher</title> - <note> - <title>DOC TODO</title> - <para> - Is this section still required/relevant? - </para> - </note> <para> &PRODUCT; 5.1 will include an optional web content authoring system add on called Site Publisher. A technical preview of this add on is available for download from the <ulink type="http" url="https://support.redhat.com/jbossnetwork/restricted/softwareDeta... Hat Customer Support Portal</ulink>. </para> Modified: epp/docs/branches/EPP_5_0_Branch/5.0.1_Release_Notes/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/EPP_5_0_Branch/5.0.1_Release_Notes/en-US/Book_Info.xml 2010-09-20 06:00:10 UTC (rev 4247) +++ epp/docs/branches/EPP_5_0_Branch/5.0.1_Release_Notes/en-US/Book_Info.xml 2010-09-20 07:54:11 UTC (rev 4248) @@ -5,7 +5,7 @@ <title>5.0.1 Release Notes</title> <subtitle>For use with JBoss Enterprise Portal Platform 5.0.1</subtitle> <edition>1.0</edition> - <pubsnumber>1.1</pubsnumber> + <pubsnumber>1.2</pubsnumber> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.0</productnumber> <abstract> Modified: epp/docs/branches/EPP_5_0_Branch/5.0.1_Release_Notes/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/EPP_5_0_Branch/5.0.1_Release_Notes/en-US/Revision_History.xml 2010-09-20 06:00:10 UTC (rev 4247) +++ epp/docs/branches/EPP_5_0_Branch/5.0.1_Release_Notes/en-US/Revision_History.xml 2010-09-20 07:54:11 UTC (rev 4248) @@ -5,7 +5,21 @@ <title>Revision History</title> <simpara> <revhistory> - <revision> + <revision> + <revnumber>1.2</revnumber> + <date>Mon Sep 20 2010</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email&gt;smumford(a)redhat.com&lt;/email&gt; + </author> + <revdescription> + <simplelist> + <member>Refined JIRA descriptions and added new JIRA links.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>1.1</revnumber> <date>Mon Sep 06 2010</date> <author>