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

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

Author: irooskov at redhat.com
Date: 2009-05-11 01:32:02 -0400 (Mon, 11 May 2009)
New Revision: 88590

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


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-05-11 03:17:38 UTC (rev 88589)
+++ projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml	2009-05-11 05:32:02 UTC (rev 88590)
@@ -381,9 +381,14 @@
 				<itemizedlist>
 					<listitem>
 						<para>
-							
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1995">JBPAPP-1995</ulink>: The <methodname>RegionManager.createRegion</methodname> method would allow duplicate region names and when this occurs all future cache operations would happen only on the second instance of the region, while the <methodname>EvictionTimerTask</methodname> will only watch the first instance, causing the eviction queue of the second instance to fill. To correct this bug, the <methodname>RegionManager.checkConflict</methodname> method now counts a duplicate as a conflict and causes the <methodname>RegionManager.createRegion</methodname> method to generate an exception.
 						</para>
 					</listitem>
+					<listitem>
+						<para>
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1994">JBPAPP-1994</ulink>: The <methodname>findNode</methodname> method of TreeCache generated a <exceptionname>NullPointerException</exceptionname> when the <methodname>findInternal</methodname> method returned a null value. The <methodname>findNode</methodname> method can now handle a null value returned from the <methodname>findInternal</methodname> method by checking within the <filename>TreeCache.java</filename> file if the <varname>toReturn</varname> value is null as well as the <varname>version</varname>
+						</para>
+					</listitem>
 				</itemizedlist>
 			</para>
 		</formalpara>
@@ -441,6 +446,16 @@
 				<itemizedlist>
 					<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.
+						</para>
+					</listitem>
+					<listitem>
+						<para>
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1922">JBPAPP-1922</ulink>: A bottleneck existed within the <filename>EntityModeToTuplizerMapping.java</filename> file when a high number of threads attempted to initialize sets and had to wait for the same monitor. In correcting this issue, the <filename>EntityModeToTuplizerMapping.java</filename> file has been modified to removie the <code>private final Map tuplizers = Collections.synchronizedMap( new SequencedHashMap() ); </code> line of code and replace it with only <code>private final Map tuplizers;</code> and two new public methods to assist in the mapping.
+						</para>
+					</listitem>
+					<listitem>
+						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1859">JBPAPP-1859</ulink>: The <classname>ManyToOneJoinTest</classname> distributed with Hibernate would fail because a primary key would be set on a <code>nullable</code> column. The <filename>OneToOneSecondPass.java</filename> file has been modified to use the <methodname>buildJoinFromMappedBySide</methodname> method instead of the <methodname>buildJoin</methodname> method. Inacting this change has meant that the calls to the <methodname>join.createPrimaryKey()</methodname> and <methodname>join.createForeignKey()</methodname> methods within this file have also been removed.
 						</para>
 					</listitem>