[jboss-cvs] JBossAS SVN: r84602 - 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-22 23:38:23 -0500 (Sun, 22 Feb 2009)
New Revision: 84602

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


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-23 04:24:05 UTC (rev 84601)
+++ projects/docs/enterprise/4.3.4.1/readme/en-US/Release_Notes_CP04_FP01.xml	2009-02-23 04:38:23 UTC (rev 84602)
@@ -541,6 +541,11 @@
 			</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. 
+				</para>
+			</listitem>
+			<listitem>
+				<para>
 					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1476">JBPAPP-1476</ulink>: The <code>&lt;script&gt;</code> tag was not allowed in the <literal>seam pageflow xsd</literal>, generating a validation error if it was used. The <filename>pageflow-2.1.xsd</filename> file has been modified with the adition of <code>&lt;xs:element ref="script"/&gt;</code> which now allows for the tag to be used within the <literal>seam pageflow xsd</literal>.
 				</para>
 			</listitem>
@@ -576,6 +581,11 @@
 					</listitem>
 				</itemizedlist>
 			</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. 
+				</para>
+			</listitem>
 		</itemizedlist>
 	</section>
 	<section id="Known-issues-in-this-release">