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

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

Author: irooskov at redhat.com
Date: 2009-06-04 20:40:20 -0400 (Thu, 04 Jun 2009)
New Revision: 89855

Modified:
   projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml
Log:
updated release notes with new JIRA


Modified: projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml
===================================================================
--- projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml	2009-06-04 23:19:05 UTC (rev 89854)
+++ projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml	2009-06-05 00:40:20 UTC (rev 89855)
@@ -881,11 +881,11 @@
 			<title>JBoss Hibernate</title>
 			<para>
 				<itemizedlist>
-					<listitem>
+				<!--	<listitem>
 						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1998">JBPAPP-1998</ulink>: The incorrect exception (<exceptionname>EntityNotFoundException</exceptionname>) was being generated for an optimistic locking failure due to a deleted entity using the <property>hibernate.jdbc.batch_versioned_data=false</property> property and value. To correct this a <emphasis>try and catch</emphasis> test has been added to the <methodname>AbstractEntityManagerImpl.wrapStaleStateException</methodname> method in order to catch the <exceptionname>EntityNotFoundException</exceptionname> exception and display the correct <exceptionname>OptimisticLockException</exceptionname> exception instead.
 						</para>
-					</listitem>
+					</listitem> -->
 					<listitem>
 						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1930">JBPAPP-1930</ulink>: A <exceptionname>NullPointerException</exceptionname> would occur when a native SQL query coupled eager fetching with a many-to-many relationship. Correcting this has beant that the <code>if ( collectionPersister.isOneToMany() ) {</code> line of code in the <filename>SQLQueryReturnProcessor</filename> file has been changed to <code>if ( collectionPersister.isOneToMany() || collectionPersister.isManyToMany()) {</code>, removing the generation of a <exceptionname>NullPointerException</exceptionname>. To note though is that the fix only works with the <filename>hbm.xml</filename> file SQL mapping feature and a named query.