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

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Mon Jul 6 03:20:02 EDT 2009 

Author: laubai
Date: 2009-07-06 03:20:02 -0400 (Mon, 06 Jul 2009)
New Revision: 90825

Modified:
   projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml
Log:
JIRA JBPAPP-2219, 1907, 1905, 1883, 1832, 1785, 1450

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-06 06:36:37 UTC (rev 90824)
+++ projects/docs/enterprise/4.3.5.1/readme/en-US/Release_Notes_CP05_FP01.xml	2009-07-06 07:20:02 UTC (rev 90825)
@@ -551,6 +551,11 @@
 		<itemizedlist>
 			<listitem>
 				<para>
+					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2219">JBPAPP-2219</ulink>: The path to the database driver set during the <command>seam setup</command> command was not displayed as a default value when <command>seam setup</command> was run a second time. A condition has been added to <classname>seam-gen</classname> so that the driver information is retained for subsequent setups.
+				</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>
@@ -599,7 +604,7 @@
 			</listitem>
 			<listitem>
 				<para>
-					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1910">JBPAPP-1910</ulink>: The DVD example that is distributed with the Seam component would generate a <exceptionname>JbpmException</exceptionname> when an order was canceled. The <filename>ordermanagement2.jpdl.xml</filename> and <filename>ordermanagement3.jpdl.xml</filename> files have each had the following line added: <code>&lt;transition name="cancel" to="cancelled"/&gt;</code>. The addition of this line to both files allows for the example to function correctly and not generate an exception.
+					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1910">JBPAPP-1910</ulink>: The DVD example that is distributed with the Seam component would generate a <exceptionname>JbpmException</exceptionname> when an order was canceled. The <filename>ordermanagement2.jpdl.xml</filename> and <filename>ordermanagement3.jpdl.xml</filename> files have each had the following line added: <code>&lt;transition name="cancel" to="cancelled"/&gt;</code>. The addition of this line to both files allows the example to function correctly and not generate an exception.
 				</para>
 			</listitem>
 			<listitem>
@@ -629,6 +634,39 @@
 					</listitem>
 				</itemizedlist>
 			</listitem>
+			<listitem>
+				<para>
+					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1907">JBPAPP-1907</ulink>: When a null value was set in conjunction with a page-scoped component, Seam would return a <exceptionname>NullPointerException</exceptionname> that contained little information about the error. A null check has been added for page-scoped components so that the exception no longer presents.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1905">JBPAPP-1905</ulink>: The DVD Store example application contains non-Latin characters. These characters were being encoded twice: once when they were imported into the database (via <filename>import.sql</filename>), and a second time during rendering. This resulted in HTML entities (for example, &amp;nbsp;) appearing on a rendered page in a browser. All HTML has been removed from the <filename>import.sql</filename> file, and the entities are now rendered correctly in a browser.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1883">JBPAPP-1883</ulink>: The SOA Platform shipped multiple <filename>jbpm-jpdl.jar</filename> files. Because more than one jPDL was available, a <exceptionname>ClassCastException</exceptionname> occurred when <literal>EsbNotifier</literal> or <literal>EsbActionHandler</literal> were called in an application. <literal>ManagedJbpmContext</literal> now closes the jBPM context before the transaction terminates, and creates a new context for subsequent transactions, so that multiple instances of jBPM do not occur.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1832">JBPAPP-1832</ulink>: Stateful session beans were not being removed from the session when a temporary conversation ended. Attempts to use the bean in subsequent conversations would throw a  <exceptionname>NoSuchEJBException</exceptionname> when the bean timed out. A line has been added to <filename>ServerConversationContext.java</filename> to ensure that stateful session beans are removed at the end of a temporary conversation, and the exception no longer presents.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1785">JBPAPP-1785</ulink>: Changes to SessionContext internal data were being immediately reflected on the HttpSession. When SessionContext was accessed concurrently, exceptions such as <exceptionname>ArrayIndexOutOfBoundsException</exceptionname>, <exceptionname>ConcurrentModificationException</exceptionname> and <exceptionname>NullPointerException</exceptionname> could occur when the HttpSession changes were effected. A new instance is now created each time the SessionContext is accessed. Changes are not applied immediately, so the exceptions no longer present when SessionContext is accessed concurrently.
+				</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:

More information about the jboss-cvs-commits mailing list