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

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Mon Jun 15 00:44:38 EDT 2009


Author: irooskov at redhat.com
Date: 2009-06-15 00:44:38 -0400 (Mon, 15 Jun 2009)
New Revision: 90174

Modified:
   projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml
Log:
updated release notes with new Hibernate Annotation 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-15 02:10:48 UTC (rev 90173)
+++ projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml	2009-06-15 04:44:38 UTC (rev 90174)
@@ -948,6 +948,11 @@
 							</listitem>
 							<listitem>
 								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-671">ANN-671</ulink>: When the <classname>Validator</classname> was not present, a message describing this would be logged, however this would occur twice. In this update the <classname>AnnotationConfiguration</classname> class has been modified to only log the occurance of this once for each time.
+								</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>
@@ -958,6 +963,26 @@
 							</listitem>
 							<listitem>
 								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-648">ANN-648</ulink>: The <methodname>o.h.a.Table.comment</methodname> and <methodname>o.h.a.Table.indexes</methodname> methods would fail when used on secondary tables. To correct this issue the <classname>SecondaryTableSecondPass</classname> class has been updated to use the <classname>XAnnotatedElement</classname> class and the <classname>EntityBinder</classname> class now sets the secondary table as the first for when a join needs to occur.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-637">ANN-637</ulink>: The <methodname>Table.appliesTo</methodname> method would incorrectly select the last table when no matching table to the user query exists. This bug has been fixed by allowing the <varname>hibTable</varname> variable within the <classname>EntityBinder</classname> class to contain a value of null when the correct table cannot be found.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-634">ANN-634</ulink>: The <property>@CollectionOfElements</property> property would clash with the <property>@Fetch JOIN</property>, <property>@Filter</property> and <property>@Where</property> properties within the <classname>CollectionBinder</classname> class. The class has now been updated to test for the instance of a <property>SimpleValue</property> in the <property>@CollectionOfElements</property> property, correcting the issue.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-633">ANN-633</ulink>: The <filename>MANIFEST.MF</filename> file in the <filename>hibernate-annotation</filename> JAR file has been improved to contain vendor and versioning information using the default attributes defined in the JAR file specification.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
 									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-621">ANN-621</ulink>: A problem was being caused by the embedded primary key for <classname>ManyToOne</classname> associates containing only transient member variables. This was corrected by adding <property>getter</property> and <property>setter</property> accessors for the respective ID fields and setting both <property>insertable</property> and <property>updatable</property> properties to false.
 								</para>
 							</listitem>
@@ -983,6 +1008,11 @@
 							</listitem>
 							<listitem>
 								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-606">ANN-606</ulink>: The <property>@Immutable</property> annotation would not generate a configuration error or warning when used on a subclass. When <property>@Immutable</property> is not used on a root entity, a warning is now generated to inform the user of this incorrect behavior.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
 									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-602">ANN-602</ulink>: Any <classname>SecondaryTable</classname> with an <classname>EmbeddedId</classname> or <classname>IdClass</classname> containing a <property>ManyToOne</property> attribute would error. In order to fix this a new <classname>SecondaryTableSecondPass</classname> class has been created and the <classname>AnnotationConfiguration</classname> and <classname>AnnotationBinder</classname> classes have been updated to make use of the new class since associations can be built on joins. Implementing these changes causes the <classname>SecondaryTable</classname> class to behave as a user would expect.
 								</para>
 							</listitem>
@@ -993,11 +1023,85 @@
 							</listitem>
 							<listitem>
 								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-567">ANN-567</ulink>: No avenue existed to set the <property>collectionPersister</property> property on a <classname>Collection</classname> via Annotations. The functionality to be able to achieve this has now been added for this release.
+								</para>
+							</listitem>
+						<!--	<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-560">ANN-560</ulink>: Quoting issues existed with the default values in the 
+								</para>
+							</listitem> -->
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-559">ANN-559</ulink>: An undefined filter definition would lead to a <exceptionname>NullPointerException</exceptionname> instead of generating a meaningful exception. This has been changed for the release so that this circumstance does not arise, instead a default filter definition is applied if one is undefined.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-556">ANN-556</ulink>: The <property>@OneToOne</property> relationship relied on strict alphebetical ordering that caused the <property>mappedBy</property> property to fail. The <classname>AnnotationBinder</classname> and <classname>AnnotationConfiguration</classname> classes have been updated to make sure that the <classname>OneToManySecondPass</classname> is processed in order.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-555">ANN-555</ulink>: A typo existed within the <classname>Tables</classname> class whereby the interface declaration contained <code>Table[] values();</code> instead of <code>Table[] value();</code>. This small bug has been fixed for this release, allowing the <methodname>Tables.value</methodname> method to function correctly.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-554">ANN-554</ulink>: A <exceptionname>NullPointerException</exceptionname> would be generated when the <property>@Id</property> property was used on a <property>@OneToOne</property> relationship. Correction of this bug has been handled by modifying the <classname>OneToOneSecondPass</classname> class to avoid a <exceptionname>NullPointerException</exceptionname> in this case and instead generate a meaningful <exceptionname>AnnotationException</exceptionname>.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-551">ANN-551</ulink>: Columns in a SQL insert query have to be ordered in the same way that Hibernate internally sorts its properties in order for the query to be successful. This was an issue for users as some would use numerious application servers, all of which would order these properties in different ways. The issue has been solved by modifying the <classname>AnnotationBinder</classname> class so that the parameters of a query are ordered internally to the order that Hibernate supports.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-549">ANN-549</ulink>: When an association table is involved in a table join, the key column would be set to null. The correct behavior is to have this key column forced to be not null. This has been achieved by modifying the <classname>MapBinder</classname> class to test if the collection is anything but a <property>OneToMany</property> relationship then the key column should not be null.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-544">ANN-544</ulink>: The <classname>CollectionBinder</classname> class used the <methodname>setCustomSQLDelete</methodname> method when testing if the <methodname>sqlDeleteAll</methodname> method was not null. This would prevent the execution of the <methodname>col.clear</methodname> method on the collection in the case that all the elements are removed. The functionality of <classname>CollectionBinder</classname> has been updated to now use the <methodname>setCustomSQLDeleteAll</methodname> method to ensure correct operation.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-525">ANN-525</ulink>: The <property>@ForeignKey</property> annotation that is used to specify readable names to foreign key constraints could not be applied at the class level and so could not be utilized in providing readable names to constrints between the super and sub classes using the <property>InheritanceType.JOINED</property> property. In this release the <property>@ForeignKey</property> annotation is now supported at the class level for all joined subclasses and is an attribute of the <classname>o.h.a.Table</classname> for secondary tables.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-517">ANN-517</ulink>: The <varname>EntityMode.DOM4J</varname> value would only work when a <filename>.hbm.xml</filename> mapping file is create and could not be used when only Hibernate Annotations was being used in business entities. The <classname>EntityBinder</classname>, <classname>PropertyBinder</classname> and <classname>CollectionBinder</classname> classes have been updated so that they call the <methodname>setNodeName</methodname> method. The error was that this was not being done by the <classname>AnnotationBinder</classname>, causing the <classname>Dom4j</classname> tuplizer to not be instantiated when only Hibernate Annotations was being used.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-516">ANN-516</ulink>: The <property>@OrderBy</property> attribute would be added to the incorrect table when used in an inheritance relationship. Condition testing has been added to the <classname>CollectionBinder</classname> class, ensuring that if the tables <classname>PersistentClass</classname> does not contain a value of <varname>associatedClass</varname>, the tables quoted name is retrieved; otherwise the table is assumed to be empty.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-515">ANN-515</ulink>: Fields were not correctly quoted in a <property>@OneToMany</property> relationship when they were specified, leading to a <exceptionname>SQLGrammarException</exceptionname>. The <filename>Ejb3JoinColumn.java</filename> file has been amended to use the method <methodname>column.getQuotedName</methodname> in the <methodname>linkValueUsingAColumnCopy</methodname> method, instead of <methodname>column.getName</methodname>.									</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>
 							<listitem>
 								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-502">ANN-502</ulink>: Intergration with Hibernate Validator was not completely possible as it is used in metamodel construction and could not be disabled. In order to allow for this functionality the <property>hibernate.validator.apply_to_ddl</property> has been added and can be set to false to remove Hibernate Validator intergration with metamodel construction.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-444">ANN-444</ulink>: In Hibernate Core, the <code>&lt;join&gt;</code> tag in <filename>.hbm.xml</filename> files contain an attribute called <property>optional</property> that allows for configuration on Hibernate to either use inner joins or outer joins, however this same functionality was not included in Hibernate Annotations. This feature has now been added to Hibernate Annotations through the modification of the <classname>EntityBinder</classname> and <classname>Table</classname> classes.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
 									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-442">ANN-442</ulink>: Support for more than one generic generator in the <filename>package-info.java</filename> file has been added by adding the new <classname>GenericGenerators</classname> interface, and updating the <classname>AnnotationBinder</classname> to incorporate the use of the new interface.
 								</para>
 							</listitem>
@@ -1006,6 +1110,31 @@
 									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-434">ANN-434</ulink>:  The exception that was generated when attempting to create an entity with an <classname>EmbeddedId</classname> and automatically generated IDs did not give useful information to a user. This has been corrected by modifying the <classname>AnnotationBinder</classname> class to generate an <exceptionname>AnnotationException</exceptionname> that outputs the class name of the component with information explaining that this class must not have <classname>ID</classname> properties when used as an <classname>EmbeddedID</classname>.
 								</para>
 							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-252">ANN-252</ulink>: The <classname>AnnotationConfiguration</classname> class would ignore classes that were annotated with an incorrect <property>Entity</property> or contained no annotation. The <classname>AnnotationBinder</classname> class has been updated to log a warning message if any of the mentioned circumstances occurs.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-122">ANN-122</ulink>: The <property>@NaturalId</property> annotation that was added to Hibernate previously, has now been added to Hibernate Annotations. This allows for a property to be specified as part of the natural id of an entity.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-104">ANN-104</ulink>: CRUD SQL customization is now allowed on secondary tables within Hibernate Annotations.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-28">ANN-28</ulink>: The <property>@Any</property> and <property>@ManyToAny</property> mapping values have been added as a new feature to Hibernate Annotations. With these features added, it allows for a more robust and diverse database environment.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
+									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-26">ANN-26</ulink>: Support for the ability to exculde a property from the optimistic locking has been added to Hibernate Annotations. 
+								</para>
+							</listitem>
 						</itemizedlist>
 					</listitem>
 				<!--	<listitem>




More information about the jboss-cvs-commits mailing list