[jboss-cvs] JBossAS SVN: r89856 - projects/docs/enterprise/4.3.5/readme/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Jun 5 00:56:27 EDT 2009
Author: irooskov at redhat.com
Date: 2009-06-05 00:56:27 -0400 (Fri, 05 Jun 2009)
New Revision: 89856
Modified:
projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml
Log:
updated release notes with new hibernate 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-06-05 00:40:20 UTC (rev 89855)
+++ projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml 2009-06-05 04:56:27 UTC (rev 89856)
@@ -54,23 +54,28 @@
JBoss Application Server 4.2.z
</para>
</listitem>
- <!-- <listitem>
+ <listitem>
<para>
- Hibernate Core 3.2.4.SP1.CP07
+ Hibernate Core 3.2.4.SP1.CP08
</para>
</listitem>
<listitem>
<para>
- Hibernate Annotations 3.2.1.GA.CP03
+ Hibernate Annotations 3.3.1.GA
</para>
</listitem>
<listitem>
<para>
- Hibernate Entity Manager 3.2.1.GA_CP04
+ Hibernate Entity Manager 3.3.2.GA
</para>
</listitem>
<listitem>
<para>
+ Hibernate Validator 3.0.0.GA
+ </para>
+ </listitem>
+ <!-- <listitem>
+ <para>
JAF 1.2_10
</para>
</listitem> -->
@@ -881,6 +886,63 @@
<title>JBoss Hibernate</title>
<para>
<itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2002">JBPAPP-2002</ulink>: The Hibernate Annotations component of the Enterprise Application Platform has been upgraded to version 3.3.1. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-701">ANN-701</ulink>: The error message given when using the <property>@CollectionId</property> property incorrectly did not give useful information to the user. Correcting this, the <filename>CollectionBinder.java</filename> file has been updated to generate an exception with all relevant information given the improper use of the <property>@CollectionId</property> property for individual cases.
+ </para>
+ </listitem>
+ <!-- <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-698">ANN-698</ulink>:
+ </para>
+ </listitem> -->
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-696">ANN-696</ulink>: When a Hibernate map existed that had both <property>key</property> and <property>value</property> elements, the <property>@Type</property> annotation would affect both. To generate desired results the <filename>MapBinder.java</filename> and <filename>MapKey.java</filename> files have ben updated to include and use a <classname>MapKey</classname> <property>@Type</property>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-694">ANN-694</ulink>: An incorrect report of a Foreign Key circularity error was occuring when the <property>@*ToOne</property> property name started with the identifier property name. The issue has been fixed by modifying the <filename>ToOneFkSecondPass.java</filename> file to make the <methodname>ToOneFkSecondPass</methodname> method a public method.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-683">ANN-683</ulink>: When <property>hashCode</property> collisions occurred within <classname>AnnotationConfiguration</classname>, random binding failures would occur. To fix this issue, the <filename>FkSecondPass.java</filename> file has been updated to use a unique counter in order to differenciate between two instances of <classname>FkSecondPass</classname> so that they can be compared as the IBM VM would sometimes return the same <varname>hashCode</varname> for two different objects. The <filename>AnnotationConfiguration.java</filename> file has also been updated to utilize the changes made to <filename>FkSecondPass.java</filename>.
+ </para>
+ </listitem>
+ <!-- <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-676">ANN-676</ulink>:
+ </para>
+ </listitem> -->
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-673">ANN-673</ulink>: <classname>AnnotationConfiguration</classname> did not define stable ordering for foreign key columns, allowing them to appear in any order within a generated SQL schema. Also of issue was when the <classname>hbm2ddl</classname> tool was being used to see a generated schema. The ordering of a foreign key column within a table could change if an unrelated modification was made inside the mapping of a different table. This issue was fixed by the solution for <emphasis>ANN-683</emphasis> that is specified within these release notes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-653">ANN-653</ulink>: The ability to use <property>@AssociationOverride</property> when overriding a collection delivered undesired results in the form of an exception. This functionality has now been fixed and works as expected.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-590">ANN-590</ulink>: An alphabetical ordering issue caused errors when the <property>@ManyToOne</property> and <property>referencedColumnName</property> properties were being used in the <classname>PrimaryKey</classname>. To correct this the <filename>ToOneFkSecondPass.java</filename> file was updated to try using an embedded property for a <classname>persistentClass</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-509">ANN-509</ulink>: Using a foreign key value for the <property>referecedColumnName</property> value would cause a <exceptionname>MappingException</exceptionname> to occur. The reason for this issue has stemed through the need for correct ordering of steps and to fix this a <classname>RecoverableException</classname> class has been created which is used to catch the exception and allow the program to perform passes to assist in correcting the issue. If however this is unsuccessful then the loop is exited and the original exception is displayed to the user.
+ </para>
+ </listitem>
+ </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.
More information about the jboss-cvs-commits
mailing list