[jboss-cvs] JBossAS SVN: r95887 - projects/docs/enterprise/5.0/Release_Notes_GA/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Nov 1 01:33:25 EDT 2009
Author: laubai
Date: 2009-11-01 01:33:25 -0400 (Sun, 01 Nov 2009)
New Revision: 95887
Modified:
projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml
Log:
Added and corrected Hibernate Known Issues.
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-11-01 05:12:52 UTC (rev 95886)
+++ projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml 2009-11-01 05:33:25 UTC (rev 95887)
@@ -597,19 +597,18 @@
</itemizedlist>
</para>
</formalpara>
- <!--#MODIFY: ADD CHANGES BTW 1.4.3 and 1.4.6.
<formalpara>
<title>JBoss Messaging</title>
<para>
<itemizedlist>
<listitem>
<para>
-
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2924">JBPAPP-2924</ulink>: Between the First Customer Ship and General Availability releases of JBoss Enterprise Application Platform 5.0, the included version of JBoss Messaging was upgraded from 1.4.3 to 1.4.6 to provide better support for JBoss Enterprise Application Platform 5.0. For further information about the differences between JBoss Messaging 1.4.3 and JBoss Messaging 1.4.6, check the JBoss Messaging Release Notes.
</para>
</listitem>
</itemizedlist>
</para>
- </formalpara>-->
+ </formalpara>
<!--<formalpara>
<title>JBoss Cache</title>
<para>
@@ -798,11 +797,6 @@
<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-2892">JBPAPP-2892</ulink>: When Enterprise JavaBean 3.0 entities are used with optimistic caching, <classname>org.jboss.ejb3.entity.OptimisticJBCCache.DataVersionAdapter.newerThan</classname> incorrectly returns <literal>true</literal> for <literal>A.newerThan ( A )</literal>. This causes a <exceptionname>DataVersioningException</exceptionname> when JBoss Cache attempts to remove the entry. The workaround for this issue is to use Multiversion Concurrency Control (<literal>mvcc-entity</literal>) instead of optimistic caching. This is recommended even if the exception has not been observed.
- </para>
- </listitem>
<listitem>
<para>
<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2818">JBPAPP-2818</ulink>: The current <filename>main/src/bin/run.sh</filename> does not allow users to override <filename>$JBOSS_HOME/bin/run.conf</filename> with a profile-specific <filename>$JBOSS_HOME/server/$PROFILE/run.conf</filename>.
@@ -834,6 +828,34 @@
<itemizedlist>
<listitem>
<para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3034">JBPAPP-3034</ulink>: When batch insert statements are ordered, embedded classes are not taken into account. There are two possible workarounds for this issue. The first is to set <varname>ORDER_INSERTS</varname> to <literal>FALSE</literal> when embedded classes are used. The second option is to explicitly call <literal>session.save()</literal> on child objects to enforce their SQL insertion orders.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3032">JBPAPP-3032</ulink>: MySQL does not currently support millisecond and microsecond measurements when returning database values such as <literal>TIME</literal> and <literal>TIMESTAMP</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3031">JBPAPP-3031</ulink>: On Sybase, the <literal>current_timestamp</literal> text is not being recognized by the translator as a <emphasis>method mode</emphasis>. There is currently no way to work around this issue except to avoid relying upon function replacement for <literal>current_timestamp</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3030">JBPAPP-3030</ulink>: On Sybase, <literal>SchemaExport</literal> cannot be used to create stored procedures while in while in chained transaction mode. The workaround for this case is to add the following code immediately after the definition of the new stored prodecure:
+ </para>
+ <programlisting><![CDATA[
+ <database-object>
+ <create>
+ sp_procxmode paramHandling, 'chained'
+ </create>
+ <drop/>
+ </database-object>]]>
+ </programlisting>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2971">JBPAPP-2791</ulink>: Applications that map Hibernate to use <classname>cglib</classname> as a byte provider fail to deploy because of a <exceptionname>java.lang.SecurityException</exceptionname>. An error message similar to the following is displayed:
</para>
<screen>Deployment "persistence.unit:unitName=lobtest.ear/lobtest-ejb-1.0-SNAPSHOT.jar#lobtest-jpa-jndi" is in error due to the following reason(s): java.lang.SecurityException: class "com.redhat.gss.lobtest.jpa.Item$$EnhancerByCGLIB$$defd1a7f"'s signer information does not match signer information of other classes in the same package</screen>
@@ -845,43 +867,63 @@
<!--The workaround for this issue is to replace <filename>jboss-eap-5.0/jboss-as/common/lib/cglib.jar</filename> with an unsigned version of <filename>cglib.jar</filename>, which can be downloaded from <ulink url="http://repository.jboss.com/maven2-brew/cglib/cglib/2.2/cglib-2.2.jar">http://repository.jboss.com/maven2-brew/cglib/cglib/2.2/cglib-2.2.jar</ulink>.-->
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2957">JBPAPP-2957</ulink>: The <code>evictAll()</code> method in <classname>EntityRegionAccessStrategy</classname> and <classname>CollectionRegionAccessStrategy</classname> attempts to remove objects from the cache without regard for transaction isolation. Disregarding transaction isolation is currently unsupported because JBoss Cache is allowed visibility to any active transaction and will therefore use the transaction to control access to data in the cache.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2945">JBPAPP-2945</ulink>: Setting the query timeout for a PreparedStatement is not supported by PostgreSQL 8.3.7. This limitation means that queries will fail if they use an annotation like the following:
+ </para>
+ <programlisting>
+ @QueryHint(name = "org.hibernate.timeout", value = "100")
+ </programlisting>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2892">JBPAPP-2892</ulink>: When Enterprise JavaBean 3.0 entities are used with optimistic caching, <classname>org.jboss.ejb3.entity.OptimisticJBCCache.DataVersionAdapter.newerThan</classname> incorrectly returns <literal>true</literal> for <literal>A.newerThan ( A )</literal>. This causes a <exceptionname>DataVersioningException</exceptionname> when JBoss Cache attempts to remove the entry. The workaround for this issue is to use Multiversion Concurrency Control (<literal>mvcc-entity</literal>) instead of optimistic caching. This is recommended even if the exception has not been observed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2867">JBPAPP-2867</ulink>: Sybase does not currently support Hibernate <literal>Blob</literal>s or <literal>Clob</literal>s, and Hibernate does not support Sybase <literal>text</literal> or <literal>image</literal> data types. The workaround for this issue is to create user-defined types that map to the Sybase <literal>text</literal> and <literal>image</literal> types.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2789">JBPAPP-2789</ulink>: <literal>ShemaExport</literal> fails on Oracle and Sybase when a redundant <code>@Column(unique=true)</code> or <code>UniqueContraint(columnnames={...})</code> annotation is used on a column that is implicitly defined as unique by the declared model. The workaround is to remove the redundant <code>@Column(unique=true)</code> or <code>UniqueContraint(columnnames={...})</code> annotation.
+ </para>
+ </listitem>
<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.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2613">JBPAPP-2613</ulink>: When the DB2 v9.7 driver is used with progressive streaming (the default), operations on <literal>Blob</literal> and <literal>Clob</literal> locators fail. The workaround is to disable progressive streaming using connection properties, as recommended 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>.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2408">JBPAPP-2408</ulink>: An issue exists with the DB2 v9.7 driver when using an identity or native ID generator with Hibernate. The <methodname>Statement.getGeneratedKeys()</methodname> driver method in DB2 returns an empty <emphasis>resultset</emphasis> instead of the generated keys, which causes Hibernate to throw an exception that states that the database returned no natively generated identity value. This issue has been fixed in the version of DB2 9.7 JDBC driver released with Data Studio 2.2 and is available for download from the DB2 website. This is the recommended version for use with Hibernate.
</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.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2278">JBPAPP-2278</ulink>: The <literal>Save</literal> operation 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. If this is not possible, another workaround is to modify either or both cascade and entity mappings to change the order of the cascade paths so that the transient entity is saved before it cascades to the entity that requires it to be non-transient.
</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.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2277">JBPAPP-2277</ulink>: Hibernate uses <methodname>ClassLoader.loadClass()</methodname> for arrays, which is no longer supported by default as of Java 6. The current workaround for this issue is to use the <property>-Dsun.lang.ClassLoader.allowArraySyntax=true</property> property. This workaround is implemented by default as the default in <filename>jboss-eap-5.0/jboss-as/run.conf</filename>.
</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.
+ <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 differ depending on whether JDK 5 or 6 is used. Since the change in column order is consistent across union clauses, the resulting queries are valid; however, this change can potentially affect performance.
</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.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2275">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 interfaces:
</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>
@@ -913,29 +955,6 @@
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>
<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.
@@ -958,24 +977,12 @@
</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.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1554">JBPAPP-1554</ulink>: Sybase only allows only one entry (for example, column name or '*') in a subquery select list. The HQL function, <literal>elements()</literal>, fails when the collection elements have a composite ID, because the generated SQL contains a subquery select list with multiple entries. The workaround is to avoid using HQL <literal>elements()</literal> if the elements have a composite key. Instead, reformulate the HQL so that no subquery has multiple entries 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>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1545">JBPAPP-1545</ulink>: On Sybase, when a query has an ANSI join with three or more joins, and one join involves a union subclass, the query may fail with <exceptionname>SybSQLException</exceptionname> because a column is not within the scope of the joined table expression. The current recommendation is to avoid using join fetches that involve union subclasses.</para>
</listitem>
<listitem>
<para>
@@ -984,21 +991,47 @@
</listitem>
<listitem>
<para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1998">JBPAPP-1998</ulink>: The <classname>testUpdatedAndRemove</classname> and <classname>RemoveTest</classname> tests fail because an incorrect exception is thrown upon an optimistic locking failure when a deleted entity uses <varname>hibernate.jdbc.batch_versioned_data</varname> set to <literal>false</literal>.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1998">JBPAPP-1998</ulink>: <exceptionname>EntityNotFoundException</exceptionname> is incorrectly thrown upon an optimistic locking failure when one <literal>EntityManager</literal> tries to delete an entity that has been updated by a different <literal>EntityManager</literal> and <varname>hibernate.jdbc.batch_versioned_data</varname> is set to <literal>false</literal> (the default value). <exceptionname>OptimisticLockException</exceptionname> should be thrown instead.
</para>
</listitem>
<listitem>
<para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1230">JBPAPP-1230</ulink>: Subqueries that use <literal>DetachedCriteria</literal> are generated incorrectly, which causes a <exceptionname>SybSQLException</exceptionname>. The workaround for this issue is not to use <literal>DetachedCriteria</literal> in a subquery. Instead, we recommend using an HQL query.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1230">JBPAPP-1230</ulink>: When a <literal>DetachedCriteria</literal> is used as a subquery, the generated SQL contains a column alias in the subquery. On Sybase, a <exceptionname>SybSQLException</exceptionname> is thrown because Sybase does not allow column aliases in subqueries. The workaround for this issue is to use an HQL query instead of a <literal>DetachedCriteria</literal> in a subquery.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1123">JBPAPP-1123</ulink>: When <literal>@OrderBy</literal> is used on joined classes (using a join table), the generated SQL is invalid on MySQL, PostgreSQL, Oracle, and MSSQL because the "order by" clause qualifies the columns using the actual table name. The "order by" clause should use the table alias instead.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1082">JBPAPP-1082</ulink>: When a <varname>char</varname> property is used and it is not initialized, then Hibernate initializes it to <literal>0</literal> and persists a string containing the character <literal>\u0000</literal>. PostgreSQL throws an exception because it does not allow character <literal>\u0000</literal> embedded in a string. An email thread describing this problem is available from:
+ </para>
+ <itemizedlist><listitem><para> http://markmail.org/message/jvzlzxw6ui2rcsmv#query:\u0000%20postgresql+page:1+mid:gpu34f4iwanbyjqh+state:results</para></listitem></itemizedlist>
+ <para>
+ There is currently no workaround for persisting <literal>\u0000</literal> in a <varname>char</varname> column using PostgreSQL.
+ </para>
+ <para>
+ If the user intends to persist a NULL for an uninitialized <varname>char</varname> property instead of <literal>\u0000</literal>, then <varname>java.lang.Character</varname> should be used instead of the primitive <varname>char</varname> type. This avoids the exception when the property is initialized. Attempting to persist a <varname>java.lang.Character</varname> property that is set to <literal>\u0000</literal> still results in an exception.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1071">JBPAPP-1071</ulink>: In some cases, when there are foreign key constraints defined on columns in a primary key, <literal>SchemaExport</literal> incorrectly declares them as nullable when it generates <code>CREATE TABLE</code> statements. This fails on MSSQL, DB2, and Sybase because those databases require primary key columns to be non-nullable.
+ </para>
+ <para>
+ The workaround for this issue is to explicitly indicate which columns should be non-nullable, such as:
+ </para>
+ <itemizedlist>
+ <listitem><para>Add <code>nullable=false</code> to <literal>@JoinColumn</literal></para></listitem>
+ <listitem><para>Add <code>optional=false</code> to <literal>@ManyToOne</literal></para></listitem>
+ <listitem><para>Add an <literal>@AttributeOverride</literal> with <code>@Column(name="mapkey", nullable=false)</code> in case of a <literal>@CollectionOfElements</literal> using a Map</para></listitem>
+ <listitem><para>Add <code>nullable=false</code> in <literal>@Column</literal> when inside a <literal>@CollectionId</literal> or inside <literal>@MapKey</literal></para></listitem>
+ </itemizedlist>
+ </listitem>
<listitem>
<para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2957">JBPAPP-2957</ulink>: The <code>evictAll()</code> method in <classname>EntityRegionAccessStrategy</classname> and <classname>CollectionRegionAccessStrategy</classname> attempts to remove objects from the cache without regard for transaction isolation. This is currently unsupported because JBoss Cache's <code>removeNode</code> method does not deal with transactions.
- </para>
- </listitem>
- <listitem>
- <para>
<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3010">JBPAPP-3010</ulink>: The <code>evict(Object)</code> method in <classname>EntityRegionAccessStrategy</classname> and <classname>CollectionRegionAccessStrategy</classname> attempts to remove objects from the cache without regard for transaction isolation. This is currently unsupported because JBoss Cache's <code>removeNode</code> method does not deal with transactions.
</para>
</listitem>
@@ -1018,43 +1051,28 @@
</para>
</formalpara>
<formalpara>
- <title>Seam Known Issues</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2385">JBPAPP-2385</ulink>: Seam's Spring example fails with an <exceptionname>IllegalStateException</exceptionname> when the login form is submitted on the IBM virtual machine. This is due to a defect in the IBM virtual machine. The fix for this issue has been deferred until the IBM virtual machine has been fixed.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2377">JBPAPP-2377</ulink>: The Seamspace example fails with a <exceptionname>NullPointerException</exceptionname> when submitting a new blog entry on the IBM virtual machine. This is due to a defect in the IBM virtual machine. The fix for this issue has been deferred until the IBM virtual machine has been fixed.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3001">JBPAPP-3001</ulink>: The seam script included in this distribution does not have an executable permission set. An executable permission set is planned for inclusion in the next release of JBoss Enterprise Application Platform 5.
- </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>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2733">JBPAPP-2733</ulink>: When the Seam examples are tested with the TestNG plugin in JBDS, a <exceptionname>java.lang.AssertionError</exceptionname> is thrown. There is currently no workaround for this issue.
- </para>
- </listitem>-->
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
<title>JBoss Messaging Known Issues</title>
<para>
<itemizedlist>
<listitem>
<para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3023">JBPAPP-3023</ulink>: The version of JBoss Messaging included in JBoss Enterprise Application Platform 4.3 allowed users to declare message queues with heirarchical names such as <literal>app1/emails</literal>, where the forward slash would create a nested JNDI context of <literal>queueu/app1/emails</literal>. This behavior is not currently supported in JBoss Enterprise Application Platform 5.0. There are two possible workarounds for this issue:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Users can create the queue or topic in the configuration files instead of relying on auto-creation. (This is recommended.)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Users can change the <varname>destination</varname> attribute (which represents the JNDI name of the destination) so that it is non-heirarchical, for example, from <literal>queue/somequeue</literal> to <literal>somequeue</literal>.
+ </para>
+ </listitem>
+ </orderedlist>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="https://jira.jboss.org/jira/browse/JBMESSAGING-1745">JBPAPP-1745</ulink>: When JBoss Transactions is upgraded from version 4.4.0 to version 4.6.1, the JBoss Messaging <literal>XAResourceRecoveryTest</literal> fails. The test is meant to simulate a failure during the commit process to prompt the Recovery Manager to recover the transaction, but with JBoss Transactions 4.6.1, the transaction is not recovered. The workaround for this failure is to manually start the Recovery Manager with the following code:
</para>
<programlisting>
@@ -1075,6 +1093,18 @@
</para>
</formalpara>
<formalpara>
+ <title>JBoss Web Services Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3028">JBPAPP-3028</ulink>: The upgrade from JBoss Web Services 2.0.1.SP to JBoss Web Services Native 3.1.2.SP incorporated many changes and new features. The additional processing time required for several new features (resource injection, support for <literal>@PostConstruct</literal> and <literal>@PreDestroy</literal>, etc.) has resulted in a slight degradation in overall performance.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
<title>RESTEasy Known Issues</title>
<para>
<itemizedlist>
@@ -1110,7 +1140,39 @@
</itemizedlist>
</para>
</formalpara>
- </section>
+ <formalpara>
+ <title>Seam Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2385">JBPAPP-2385</ulink>: Seam's Spring example fails with an <exceptionname>IllegalStateException</exceptionname> when the login form is submitted on the IBM virtual machine. This is due to a defect in the IBM virtual machine. The fix for this issue has been deferred until the IBM virtual machine has been fixed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2377">JBPAPP-2377</ulink>: The Seamspace example fails with a <exceptionname>NullPointerException</exceptionname> when submitting a new blog entry on the IBM virtual machine. This is due to a defect in the IBM virtual machine. The fix for this issue has been deferred until the IBM virtual machine has been fixed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3001">JBPAPP-3001</ulink>: The seam script included in this distribution does not have an executable permission set. An executable permission set is planned for inclusion in the next release of JBoss Enterprise Application Platform 5.
+ </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>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2733">JBPAPP-2733</ulink>: When the Seam examples are tested with the TestNG plugin in JBDS, a <exceptionname>java.lang.AssertionError</exceptionname> is thrown. There is currently no workaround for this issue.
+ </para>
+ </listitem>-->
+ </itemizedlist>
+ </para>
+ </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