[jboss-cvs] JBossAS SVN: r88772 - in projects/docs/enterprise: 4.3.5/readme/en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue May 12 22:34:19 EDT 2009
Author: irooskov at redhat.com
Date: 2009-05-12 22:34:18 -0400 (Tue, 12 May 2009)
New Revision: 88772
Modified:
projects/docs/enterprise/4.2.7/readme/en-US/Release_Notes_CP07.xml
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.2.7/readme/en-US/Release_Notes_CP07.xml
===================================================================
--- projects/docs/enterprise/4.2.7/readme/en-US/Release_Notes_CP07.xml 2009-05-13 01:50:52 UTC (rev 88771)
+++ projects/docs/enterprise/4.2.7/readme/en-US/Release_Notes_CP07.xml 2009-05-13 02:34:18 UTC (rev 88772)
@@ -366,9 +366,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>
@@ -425,11 +430,44 @@
<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>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1748">JBPAPP-1748</ulink>: When merging read-only entities that had the <varname>@Immutable</varname> annotation included the following failure would occur:
+ </para>
+<screen>
+org.hibernate.AssertionFailure: Merged entity does not have status set to MANAGED; EntityEntry[com.tll.model.impl.AccountHistory#71794688](READ_ONLY) status=READ_ONLY
+</screen>
+ <para>
+ The <filename>DefaultMergeEventListener.java</filename> file has been updated by editing the following test statement:
+ </para>
+<programlisting>
+if ( entry.getStatus() != Status.MANAGED ) {
+ throw new AssertionFailure( "Merged entity does not have status set to MANAGED; "+entry+" status="+entry.getStatus() );
+}
+</programlisting>
+ <para>
+ modified to test against the possibility that the current <varname>Status</varname> could be <property>READ_ONLY</property>:
+ </para>
+<programlisting>
+if ( entry.getStatus() != Status.MANAGED && entry.getStatus() != Status.READ_ONLY ) {
+ throw new AssertionFailure( "Merged entity does not have status set to MANAGED or READ_ONLY; "+entry+" status="+entry.getStatus() );
+}</programlisting>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1563">JBPAPP-1563</ulink>: The SQL functions <function>mod</function>, <function>bit_length</function> and <function>trim</function> caused faulures in the <classname>ASTParserLoadingTest</classname> because they were not implemented in the Sybase Dialect. The Sybase Dialect has now been updated to import the <classname>org.hibernate.dialect.function.AnsiTrimEmulationFunction</classname> function and implement the <function>mod</function>, <function>bit_length</function> and <function>trim</function> functions.
</para>
</listitem>
@@ -502,6 +540,29 @@
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1976">JBPAPP-1976</ulink>: The <classname>HASingletonElectionPolicySimple</classname> class of the Clustering component retrieved the current view from the <classname>HAPartition</classname> and formulated a decision based on that information that ignored the possibility that the service being managed may nt be running on all cluster members. To fix this issue the <classname>ExtendedElectionPolicySimple</classname> class has been created and when used it fixes not only the above issue but also an issue where using the <code>kill -9</code> command was necessary to start singletons on other nodes. This new class extends the election policy and provides helper methods for stable implementations.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1932">JBPAPP-1932</ulink>: Java 1.4 based clients would not function when trying to use the Java remote method invocation interface over the Internet Inter-Orb Protocol (RMI-IIOP). This occured because sections of placeholder code (which allow the program to function correctly) were needed, however these sections of code were compiled with Java 1.5 without compatibility for version 1.4. In order to correct this bug, the <filename>iiop/build.xml</filename> file has been updated with the removal of:
+ </para>
+<programlisting>
+<javac destdir="${build.classes}/main"
+ optimize="${javac.optimize}"
+ target="${javac.target}"
+ source="${javac.source}"
+</programlisting>
+ <para>
+ and replaced with:
+ </para>
+<programlisting>
+<javac destdir="${build.classes}/main"
+ optimize="${javac.optimize}"
+ target="1.4"
+ source="1.4"
+</programlisting>
+ <para>
+ forcing the <filename>build.xml</filename> file to use Java 1.4.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
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-13 01:50:52 UTC (rev 88771)
+++ projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml 2009-05-13 02:34:18 UTC (rev 88772)
@@ -422,7 +422,7 @@
<itemizedlist>
<listitem>
<para>
-
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-829">JBPAPP-829</ulink>:
</para>
</listitem>
</itemizedlist>
@@ -461,6 +461,30 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1748">JBPAPP-1748</ulink>: When merging read-only entities that had the <varname>@Immutable</varname> annotation included the following failure would occur:
+ </para>
+<screen>
+org.hibernate.AssertionFailure: Merged entity does not have status set to MANAGED; EntityEntry[com.tll.model.impl.AccountHistory#71794688](READ_ONLY) status=READ_ONLY
+</screen>
+ <para>
+ The <filename>DefaultMergeEventListener.java</filename> file has been updated by editing the following test statement:
+ </para>
+<programlisting>
+if ( entry.getStatus() != Status.MANAGED ) {
+ throw new AssertionFailure( "Merged entity does not have status set to MANAGED; "+entry+" status="+entry.getStatus() );
+}
+</programlisting>
+ <para>
+ modified to test against the possibility that the current <varname>Status</varname> could be <property>READ_ONLY</property>:
+ </para>
+<programlisting>
+if ( entry.getStatus() != Status.MANAGED && entry.getStatus() != Status.READ_ONLY ) {
+ throw new AssertionFailure( "Merged entity does not have status set to MANAGED or READ_ONLY; "+entry+" status="+entry.getStatus() );
+}
+</programlisting>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1563">JBPAPP-1563</ulink>: The SQL functions <function>mod</function>, <function>bit_length</function> and <function>trim</function> caused faulures in the <classname>ASTParserLoadingTest</classname> because they were not implemented in the Sybase Dialect. The Sybase Dialect has now been updated to import the <classname>org.hibernate.dialect.function.AnsiTrimEmulationFunction</classname> function and implement the <function>mod</function>, <function>bit_length</function> and <function>trim</function> functions.
</para>
</listitem>
@@ -558,6 +582,29 @@
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1976">JBPAPP-1976</ulink>: The <classname>HASingletonElectionPolicySimple</classname> class of the Clustering component retrieved the current view from the <classname>HAPartition</classname> and formulated a decision based on that information that ignored the possibility that the service being managed may nt be running on all cluster members. To fix this issue the <classname>ExtendedElectionPolicySimple</classname> class has been created and when used it fixes not only the above issue but also an issue where using the <code>kill -9</code> command was necessary to start singletons on other nodes. This new class extends the election policy and provides helper methods for stable implementations.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1932">JBPAPP-1932</ulink>: Java 1.4 based clients would not function when trying to use the Java remote method invocation interface over the Internet Inter-Orb Protocol (RMI-IIOP). This occured because sections of placeholder code (which allow the program to function correctly) were needed, however these sections of code were compiled with Java 1.5 without compatibility for version 1.4. In order to correct this bug, the <filename>iiop/build.xml</filename> file has been updated with the removal of:
+ </para>
+<programlisting>
+<javac destdir="${build.classes}/main"
+ optimize="${javac.optimize}"
+ target="${javac.target}"
+ source="${javac.source}"
+</programlisting>
+ <para>
+ and replaced with:
+ </para>
+<programlisting>
+<javac destdir="${build.classes}/main"
+ optimize="${javac.optimize}"
+ target="1.4"
+ source="1.4"
+</programlisting>
+ <para>
+ forcing the <filename>build.xml</filename> file to use Java 1.4.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
More information about the jboss-cvs-commits
mailing list