[jboss-cvs] JBossAS SVN: r92719 - projects/docs/enterprise/5.0/Release_Notes/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Aug 23 23:28:23 EDT 2009
Author: irooskov at redhat.com
Date: 2009-08-23 23:28:22 -0400 (Sun, 23 Aug 2009)
New Revision: 92719
Modified:
projects/docs/enterprise/5.0/Release_Notes/en-US/Release_Notes.xml
Log:
updated release notes with Hibernate Known Issues
Modified: projects/docs/enterprise/5.0/Release_Notes/en-US/Release_Notes.xml
===================================================================
--- projects/docs/enterprise/5.0/Release_Notes/en-US/Release_Notes.xml 2009-08-24 00:58:29 UTC (rev 92718)
+++ projects/docs/enterprise/5.0/Release_Notes/en-US/Release_Notes.xml 2009-08-24 03:28:22 UTC (rev 92719)
@@ -775,14 +775,6 @@
</listitem>
<listitem>
<para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2577">JBPAPP-2577</ulink>: An issue exists with the DB2 v9.7 driver when using a <emphasis>native</emphasis> ID generator with Hibernate. The generator uses <emphasis>identity</emphasis> and the <methodname>Statement.getGeneratedKeys()</methodname> method in DB2 and returns a <emphasis>resultset</emphasis>, however the DB2 driver would still return an empty set. In this case Hibernate states that <errortext>The database returned no natively generated identity value</errortext>.
- </para>
- <para>
- The current workaround for this is to use the DB2 v9.1 driver instead of the DB2 v9.7 driver. This issue is scheduled to be fixed in the next release.
- </para>
- </listitem>
- <listitem>
- <para>
<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2576">JBPAPP-2576</ulink>: The MySQL JDBC driver does not currently implement XA Recovery correctly.
</para>
</listitem>
@@ -794,19 +786,109 @@
</itemizedlist>
</para>
</formalpara>
- <!-- <formalpara>
+ <formalpara>
<title>Hibernate Known Issues</title>
<para>
<itemizedlist>
<listitem>
<para>
-
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2613">JBPAPP-2613</ulink>: When the DB2 v9.7 driver is in use, the <literal>Blob</literal> and <literal>Clob</literal> locators fail. Recommendations reguarding the use of DB2 v9.7 connection properties and Hibernate can be found in the linked JIRA issue.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2577">JBPAPP-2577</ulink>: An issue exists with the DB2 v9.7 driver when using a <emphasis>native</emphasis> ID generator with Hibernate. The generator uses <emphasis>identity</emphasis> and the <methodname>Statement.getGeneratedKeys()</methodname> method in DB2 and returns a <emphasis>resultset</emphasis>, however the DB2 driver would still return an empty set. In this case Hibernate states that <errortext>The database returned no natively generated identity value</errortext>.
+ </para>
+ <para>
+ The current workaround for this is to use the DB2 v9.1 driver instead of the DB2 v9.7 driver. This issue is scheduled to be fixed in the next release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2293">JBPAPP-2293</ulink>: Hibernate Core does not implement the correct Javadoc stylesheet for JBoss Enterprise Application Platform 5. The standard Javadoc stylesheet will be added for the next release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2278">JBPAPP-2278</ulink>: The <literal>Save</literal> opperation may fail when a transient entity is reachable by multiple paths and at least one of those paths does not cascade for the <literal>Save</literal> opperation. The current workaround for this is to save the transient entity before executing the save that had previously failed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2277">JBPAPP-2277</ulink>: Hibernate includes incorrect usage of the <methodname>ClassLoader.loadClass()</methodname> method in <classname>SerializationHelper$CustomObjectInputStream</classname> for Java 6, which causes a deserialization battleneck for created arrays. The current workaround for this issue is to use the <property>-Dsun.lang.ClassLoader.allowArraySyntax=true</property> property, which can be set as the default in the <filename>run.conf</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2276">JBPAPP-2276</ulink>: The iteration order of <literal>HashMaps</literal> and <literal>HashSets</literal> for JDK 6 causes the order of columns in union clauses or union subclasses to change, generating a large impact on performance.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2276">JBPAPP-2275</ulink>: Hibernate cannot be compiled under JDK 6. This occurs because the following classes require methods to be added in order to fully implement JDK 6:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <classname>org.hibernate.jdbc.ResultSetWrapper</classname>
+ </para>
+ </listitem>
+ dlist>
+ <listitem>
+ <para>
+ <classname>org.hibernate.lob.BlobImpl</classname> to implement <classname>java.sql.Blob</classname>
+ </para>
+ </listitem>
+ dlist>
+ <listitem>
+ <para>
+ <classname>org.hibernate.lob.ClobImpl</classname>
+ </para>
+ </listitem>
+ dlist>
+ <listitem>
+ <para>
+ <classname>org.hibernate.lob.SerializableBlob</classname>
+ </para>
+ </listitem>
+ dlist>
+ <listitem>
+ <para>
+ <classname>org.hibernate.lob.SerializableClob</classname>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ If the application you are running requires a method missing from the above classes, a <errorname>NoSuchMethodError</errorname> will be generated.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2082">JBPAPP-2082</ulink>: In Hibernate Annotations, the bidirectional indexed collection is mapped incorrectly. This may cause failures due to a bug within MySQL that refers to self-referencing foreign keys.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1722">JBPAPP-1722</ulink>: On Sybase, an insert into an <literal>identity</literal> column fails but no exception occurs. The current workaround for this issue is to set the application to validate entity properties to ensure that they do not overflow what is already defined for the underlying column.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1701">JBPAPP-1701</ulink>: When Hibernate components are built offline, the html links (HREF attributes) are missing from the build. The current workaround for this is to add the following code segment to the <literal>configuration</literal> and <literal>reporting</literal> sections:
+ </para>
+<programlisting>
+<offlineLinks>
+ <offlineLink>
+ <url>http://java.sun.com/j2se/1.5/docs/api</url>
+ <location>/path/of/your/api/folder</location>
+ </offlineLink>
+</offlineLinks>
+</programlisting>
+ </listitem>
</itemizedlist>
</para>
- </formalpara> -->
-<!-- </section> -->
+ </formalpara>
+ </section>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
</article>
More information about the jboss-cvs-commits
mailing list