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

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Tue Jul 7 01:24:33 EDT 2009


Author: laubai
Date: 2009-07-07 01:24:32 -0400 (Tue, 07 Jul 2009)
New Revision: 90872

Modified:
   projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml
Log:
JIRA JBPAPP-2051, 1962, 1912, 1904, 1751

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-07 01:16:03 UTC (rev 90871)
+++ projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml	2009-07-07 05:24:32 UTC (rev 90872)
@@ -556,11 +556,21 @@
 			</listitem>
 			<listitem>
 				<para>
+					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2051">JBPAPP-2051</ulink>: The Seam documentation contained a reference to the <literal>clientSideComponents</literal> initialisation setting, which no longer applies. This has been corrected, and the reference removed.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
 					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1969">JBPAPP-1969</ulink>: The anchor in the pdf header and footer would fail and generate a <exceptionname>RuntimeException</exceptionname> detailing that not all of the annotations could be added to the document. This <emphasis>itext</emphasis> issue has been fixed by modifying the <classname>UIDocument</classname> classes <methodname>encodeEnd</methodname> method so that the document Header and Footer are reset so that information can be successfully added. 
 				</para>
 			</listitem>
 			<listitem>
 				<para>
+					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1962">JBPAPP-1962</ulink>: Several typographical errors in the Framework chapter of the Seam documentation have been corrected.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
 					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1928">JBPAPP-1928</ulink>: Within the <filename>Seambay</filename> example, if a user submitted an empty registration it would generate a debug page because of a <exceptionname>org.hibernate.validator.InvalidStateException</exceptionname>. This bug has been fixed by adding form validation to the example through the modification of the <filename>register.xhtml</filename> files form registration section.
 				</para>
 			</listitem>
@@ -597,6 +607,11 @@
 					To fix this security vulnerability the <classname>AuthenticatorAction</classname> class of the booking example has been fixed by note requiring any inwards information. This has been achieved by adding and setting the <property>@In(required=false)</property> property correctly.
 				</para>
 			</listitem>
+<listitem>
+	<para>
+		<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1912">JBPAPP-1912</ulink>: A typographical error in the Tutorial chapter of the Seam documentation has been corrected.
+	</para>
+</listitem>
 			<listitem>
 				<para>
 					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1911">JBPAPP-1911</ulink>: An unclosed input stream existed within the <methodname>writeResource</methodname> method of the <classname>Remoting</classname> class, causing a warning to be displayed to a user upon redeployment on GlassFish. The <classname>Remoting</classname> class has been modified with the inclusion of a try and catch block added to encompass the code and make sure the exception is not displayed.
@@ -651,6 +666,11 @@
 			</listitem>
 			<listitem>
 				<para>
+					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1904">JBPAPP-1904</ulink>: Several security events were named incorrectly in the Seam documentation. The event names have been updated.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
 					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1903">JBPAPP-1903</ulink>:  The JBoss EL component has been upgraded to version 1.0_02.CR3, fixing a cleanup thread and memory leak that existed in the Reference Utility. This has been achieved by the addition of the <classname>JBossELReferenceCache</classname> class that provides the initiation and termination of the Reflection Utility, ensuring that no application leak occurs. 
 				</para>
 			</listitem>
@@ -671,6 +691,11 @@
 			</listitem>
 			<listitem>
 				<para>
+					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1751">JBPAPP-1751</ulink>: <filename>jboss-embedded-all.jar</filename> contained multiple copies of classes with the same fully-qualified name, which caused problems for some users when the <filename>jar</filename> was extracted. The <literal>duplicate="preserve"</literal> property has been added to the duplicate classes. This preserves the first instance of the class, and skips duplicates, which resolves the issue.
+				</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>




More information about the jboss-cvs-commits mailing list