[jboss-cvs] JBossAS SVN: r91133 - projects/docs/enterprise/4.3.5.1/readme/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: irooskov at redhat.com
Date: 2009-07-12 19:01:40 -0400 (Sun, 12 Jul 2009)
New Revision: 91133

Modified:
   projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml
Log:
moved 1450 to the known issues section and re-wrote the note


Modified: projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml	2009-07-12 03:38:18 UTC (rev 91132)
+++ projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml	2009-07-12 23:01:40 UTC (rev 91133)
@@ -700,11 +700,6 @@
 					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1455">JBPAPP-1455</ulink>: The booking example that is included with Seam would generate a <exceptionname>NotLoggedInException</exceptionname> in the server log after a user logged in and proceeded to the <filename>change-password-page</filename> through the <guimenuitem>Settings</guimenuitem> link and then clicked the <guibutton>Logout</guibutton> button. The application itself would undertake the expected behavior of returning to the login screen, yet the exception would still be logged. The bug of the logged exception has been rectified by modifying the <filename>examples/booking/resources/WEB-INF/pages.xml</filename> file so that the navigation rule no longer only cheks if a password has been changed, but also that the user is logged in.
 				</para>
 			</listitem>
-			<listitem>
-				<para>
-					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1450">JBPAPP-1450</ulink>: When the ICEFaces example was undeployed, a <exceptionname>NoSuchEJBException</exceptionname> would occur if the EAR was undeployed before the application datasource undeployment had completed. A greater interval has been inserted between datasource and EAR undeployment, which resolves this issue.
-				</para>
-			</listitem>
 	<!--		<listitem>
 				<para>
 					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>: Some components within the Feature Pack have been upgraded to the same version within the Enterprise Application Platform 4.3.0.CP05 release. A list of these components follows with further indepth information avaliable for each in the release notes for 4.3.0.CP05 avaliable at <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.3.0.cp05/html-single/readme/index.html">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.3.0.cp05/html-single/readme/index.html</ulink>. The list of updated components are:
@@ -730,6 +725,11 @@
 		<itemizedlist>
 			<listitem>
 				<para>
+					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1450">JBPAPP-1450</ulink>: When the ICEFaces example was undeployed, a <exceptionname>NoSuchEJBException</exceptionname> would occur if the EAR was undeployed before the application datasource undeployment had completed. The current workaround is to wait until the application datasource has been successfully undeployed before performing JBoss Enterprise Application Platform undeployment.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
 					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1448">JBPAPP-1448</ulink>: When logging information using the <methodname>SeamResourceBundle.getBundle</methodname> method without passing a <literal>Local</literal> value using the <methodname>LocaleSelector.instance().getLocale()</methodname> method, the default <literal>Local</literal> value will be used, which can be incorrect. However since the <methodname>SeamResourceBundle.getBundle</methodname> method is a <literal>static final</literal> method type, Seam cannot override it. The suggested workaround for this is to always pass the <literal>Local</literal> value when using the <methodname>log.info</methodname> method. 
 				</para>
 			</listitem>