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

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

Author: irooskov at redhat.com
Date: 2009-06-15 23:16:11 -0400 (Mon, 15 Jun 2009)
New Revision: 90229

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-16 03:05:52 UTC (rev 90228)
+++ projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml	2009-06-16 03:16:11 UTC (rev 90229)
@@ -931,7 +931,7 @@
 									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-2">HV-2</ulink>: String suport for both <property>@Past</property> and <property>@Future</property> validating Strings has been deprecated as there was no absolute way to be sure of the date and time format or the locale that may be used.
 								</para>
 							</listitem>
-							listitem>
+							<listitem>
 							<para>
 								<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-1">HV-1</ulink>: A new feature has been added to Hibernate Validator that sets the <classname>ClassValidator</classname> as being independ of Hibernate Annotations. This ensures that if a users wishes, Hibernate Validator does not have to be used with Hibernate Annotations. 
 							</para>
@@ -958,11 +958,11 @@
 									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-699">ANN-699</ulink>: The <methodname>AnnotationBinder.mustBeSkipped</methodname> contains a hardcoded reference to the <classname>org.hibernate.tool.instrument.javassist.FieldHandler</classname> class. The issue that arises from this is that the class is actually contained within a different package and by having the incorrect reference it caused all <classname>javassist-instrumented</classname> classes to not function correctly. In order to rectify this issue the reference to the <classname>FieldHandler</classname> class has been changed within the <methodname>AnnotationBinder.mustBeSkipped</methodname> method to be <classname>org.hibernate.bytecode.javassist.FieldHandler</classname>.
 								</para>
 							</listitem>
-						<!--	<listitem>
+							<listitem>
 								<para>
-									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-698">ANN-698</ulink>: 
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-698">ANN-698</ulink>: Having an unbound property when default field access is used would lead to an unbound <exceptionname>AnnotationException</exceptionname>. The generated exception is now caught by the program and a more meaningful <exceptionname>AnnotationException</exceptionname> is generated and displayed to the user instead. These changes have been made to the <classname>AnnotationBinder</classname> class.
 								</para>
-							</listitem> -->
+							</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>.
@@ -988,11 +988,6 @@
 									<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.