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

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

Author: irooskov at redhat.com
Date: 2009-02-24 18:03:06 -0500 (Tue, 24 Feb 2009)
New Revision: 84683

Modified:
   projects/docs/enterprise/4.3.4.1/readme/en-US/Release_Notes_CP04_FP01.xml
Log:
updated release notes with corrections


Modified: projects/docs/enterprise/4.3.4.1/readme/en-US/Release_Notes_CP04_FP01.xml
===================================================================
--- projects/docs/enterprise/4.3.4.1/readme/en-US/Release_Notes_CP04_FP01.xml	2009-02-24 22:59:55 UTC (rev 84682)
+++ projects/docs/enterprise/4.3.4.1/readme/en-US/Release_Notes_CP04_FP01.xml	2009-02-24 23:03:06 UTC (rev 84683)
@@ -48,7 +48,7 @@
 				</listitem>
 				<listitem>
 					<para>
-						Integration with RichFaces 3.1
+						Integration with RichFaces 3.3
 					</para>
 				</listitem>
 			</itemizedlist>
@@ -593,7 +593,7 @@
 			</listitem>
 			<listitem>
 				<para>
-					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1495">JBPAPP-1495</ulink>: In the previous version of the Enterprise Application Platform Feature Pack, the Seam Booking example would generate a <exceptionname>NoSuchEJBException</exceptionname> when run in a cluster. This example has now been amended to include functionality for execution on a cluster. 
+					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1495">JBPAPP-1495</ulink>: In the previous version of the Enterprise Application Platform Feature Pack, the Seam Booking example would generate a <exceptionname>java.io.NotSeriazableException</exceptionname> when run in a cluster. This example has now been amended to include functionality for execution on a cluster. 
 				</para>
 			</listitem>
 			<listitem>
@@ -603,7 +603,7 @@
 			</listitem>
 			<listitem>
 				<para>
-					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1469">JBPAPP-1469</ulink>: The included HQL query editor did not work for new <literal>Seam-web</literal> projects and would generate a <exceptionname>QuerySyntaxException</exceptionname>. Creating tables would work as expected, however when performing a query on one of these tables the error would occur. In correcting this the <filename>SeamgenerateEntitiesWizard.java</filename> file has been modified to include a new <methodname>performFinish()</methodname> method which calls the <methodname>config.reset()</methodname> method if the console configuration has been updated.
+					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1469">JBPAPP-1469</ulink>: The JBoss Developer Studio plugin HQL query editor did not work for new <literal>Seam-web</literal> projects with the underlying Enterprise Application Platform Feature Pack, generating a <exceptionname>QuerySyntaxException</exceptionname>. Creating tables worked as expected, however when performing a query on one of these tables the error would occur. In correcting this the <filename>SeamgenerateEntitiesWizard.java</filename> file has been modified to include a new <methodname>performFinish()</methodname> method which calls the <methodname>config.reset()</methodname> method if the console configuration has been updated.
 				</para>
 			</listitem>
 			<listitem>
@@ -635,7 +635,7 @@
 			</listitem>
 			<listitem>
 				<para>
-					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1427">JBPAPP-1427</ulink>: In previous versions of Seam for the JBoss Enterprise Application Platform Feature Pack, the call in which an exception occurred was not necessarily dealt with correctly, raising an exception. Within the <filename>ExceptionFilter.java</filename> file, the code <code>Lifecycle.endRequest();</code> has been added to ensure that each call in which an exception occurs, is handled correctly without causing another exception. 
+					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1427">JBPAPP-1427</ulink>: In previous versions of Seam for the JBoss Enterprise Application Platform Feature Pack, the call in which an exception occurred was not necessarily dealt with correctly and the <classname>ConversationEntry</classname> could not be released. Within the <filename>ExceptionFilter.java</filename> file, the code <code>Lifecycle.endRequest();</code> has been added to ensure that each call in which an exception occurs, is handled correctly without retaining a <classname>ConversationEntry</classname> lock.
 				</para>
 			</listitem>
 		</itemizedlist>