[jboss-cvs] JBossAS SVN: r94921 - projects/docs/enterprise/5.0/Release_Notes_GA/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Oct 15 02:20:21 EDT 2009
Author: laubai
Date: 2009-10-15 02:20:21 -0400 (Thu, 15 Oct 2009)
New Revision: 94921
Modified:
projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml
Log:
Added JIRAs: 2162, 2765, 2922, 2792, 2613, 1613, 1554, 1545, 2384.
Modified: projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml
===================================================================
--- projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml 2009-10-15 06:07:00 UTC (rev 94920)
+++ projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml 2009-10-15 06:20:21 UTC (rev 94921)
@@ -320,11 +320,11 @@
<entry>3.3.1.GA</entry>
<entry>N/A</entry>
</row>
- <row>
+ <!--<row>
<entry>RESTEasy</entry>
<entry>1.1.GA</entry>
<entry>N/A</entry>
- </row>
+ </row>-->
<row>
<entry>JON JASA Console</entry>
<entry>1.3.1.GA</entry>
@@ -780,9 +780,35 @@
</listitem>
<listitem>
<para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2871">JBPAPP-2871</ulink>: High CPU utilization and reduced performance and transaction throughput has been observed when MySQL 5.0.41 with optimized settings is in use, as described in <ulink url="https://jira.jboss.org/jira/browse/JBQA-2610">JBQA-2610</ulink>. We recommend upgrading to MySQL 5.0.86 and applying optimized settings as described in <ulink url="https://jira.jboss.org/jira/browse/JBQA-2610">JBQA-2610</ulink> to reduce CPU utilization and increase performance.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2871">JBPAPP-2871</ulink>: High CPU utilization and reduced performance and transaction throughput has been observed when MySQL 5.0.41 when optimized settings are in use, as described in <ulink url="https://jira.jboss.org/jira/browse/JBQA-2610">JBQA-2610</ulink>. We recommend upgrading to MySQL 5.0.86 and applying optimized settings as described in <ulink url="https://jira.jboss.org/jira/browse/JBQA-2610">JBQA-2610</ulink> to reduce CPU utilization and increase performance.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2162">JBPAPP-2162</ulink>: Sun JAXB silently accepts messages with non-fatal errors where they should be rejected. The fix for <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2114">JBPAPP-2114</ulink> corrects this, so that badly-formed messages are rejected.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2765">JBPAPP-2765</ulink>: <literal>LoadMgr3</literal> logs a failure to load a class as an error even when the failure to load is expected and intentional. (Seam, for example, catches exceptions in order to disable unnecessary components if a particular class is not found.)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2894">JBPAPP-2894</ulink>: Setting the <literal>hibernate.bytecode.provider</literal> system property in <filename>jpa-deployers-jboss-beans.xml</filename> is unreliable. The workaround for this issue is to add <code>-Dhibernate.bytecode.provider=cglib</code> to <literal>$JAVA_OPTS</literal> in <filename>jboss-as/bin/run.conf</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2384">JBPAPP-2384</ulink>: The Seam Chatroom example throws an <exceptionname>EJBTransactionRolledbackException</exceptionname> when a user attempts to log in. This exception does not influence the application's functionality.
+ </para>
+ </listitem>
+
+<!-- <listitem>
+ <para>
+
+ </para>
+ </listitem>-->
<!-- <listitem>
<para>
<ulink url="https://jira.jboss.org/jira/browse/JBAS-6966">JBAS-6966</ulink>: The IBM distribution of JDK 6 does not support the <classname>SSLv2Hello</classname> protocol and generates a <errorname>ERROR [AbstractKernelController]</errorname> when used. It is recommended to currently not use this protocol.
@@ -886,6 +912,51 @@
</offlineLinks>
</programlisting>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2922">JBPAPP-2922</ulink>: Hibernate warns that <code>The CGLIB BytecodeProvider impl is considered deprecated and not recommended for use</code>. <literal>cglib</literal> is not deprecated, so this warning can be safely ignored.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2792">JBPAPP-2792</ulink>: Sybase fails to insert a new entity if it overflows its column. However, it does not throw an exception, so Hibernate cannot tell that the insert failed. To work around this issue, the application must validate entity properties to ensure that they do not overflow the underlying column.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1613">JBPAPP-1613</ulink>: Null values for columns mapped as <literal>Boolean</literal> in Sybase are persisted as <literal>0</literal> instead of <literal>null</literal>. The workaround for this issue is to map <code>type="org.hibernate.test.where.NumericTrueFalseType"</code> instead of <code>type="boolean"</code>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1554">JBPAPP-1554</ulink>: <code>FumTest.testCompositeKeyPathExpressions()</code> fails if a subquery includes multiple columns in its select list. We recommend avoiding the use of HQL <literal>elements()</literal> if the elements have a composite key. Instead, reformulate the HQL so that no subquery has multiple items in its select list.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1545">JBPAPP-1545</ulink>: If an ANSI join with three or more joins is attempted, and one join involves a union subclass, the following unit tests are expected to fail in Sybase:
+ </para>
+ <itemizedlist>
+ <listitem><para>
+ <literal>UnionSubclassTest.testUnionSubclassFetchMode()</literal>
+ </para></listitem>
+ <listitem><para>
+ <literal>UnionSubclassPropertyRefTest.testOneToOnePropertyRef()</literal>
+ </para></listitem>
+ </itemizedlist>
+ <para>
+ The current recommendation is to not use join fetches that involve union subclasses.
+ </para>
+ </listitem>
+
+
+
+
+<!-- <listitem>
+ <para>
+ <ulink url="">JBPAPP- </ulink>:
+ </para>
+ </listitem>-->
</itemizedlist>
</para>
</formalpara>
More information about the jboss-cvs-commits
mailing list