[jboss-cvs] JBossAS SVN: r83790 - in projects/docs/enterprise: 4.3.4/readme/en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Feb 2 21:49:21 EST 2009
Author: irooskov at redhat.com
Date: 2009-02-02 21:49:21 -0500 (Mon, 02 Feb 2009)
New Revision: 83790
Modified:
projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml
projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
Log:
updated with new JIRA
Modified: projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml
===================================================================
--- projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml 2009-02-02 23:14:03 UTC (rev 83789)
+++ projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml 2009-02-03 02:49:21 UTC (rev 83790)
@@ -744,6 +744,27 @@
<itemizedlist>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1670">JBPAPP-1670</ulink>: The JacORB component of the EAP has been upgraded to version 2.3.0jboss.patch6-brew. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ A bug existed that would cause <filename>JacORB 2.3.0.jboss5</filename> to become unresponsive during shutdown. In rectifing this issue, the <filename>POA.java</filename> file has been modified so that instead of executing:
+ </para>
+ <programlisting>
+ throw new org.omg.CORBA.OBJECT_NOT_EXIST();
+ </programlisting>
+ <para>
+ the following is now executed:
+ </para>
+ <programlisting>
+ throw new ObjectNotActive();
+ </programlisting>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1636">JBPAPP-1636</ulink>: When an adapter handled the scheduling of work to be performed, the <classname>ExecutionContext</classname> class contains a value in seconds, from which the <methodname>getCompletionTimeout</methodname> method of <classname>org.jboss.resource.work.WorkWrapper</classname> obtains its information. An issue arises with <methodname>getCompletionTimeout</methodname> expecting the value to be in milliseconds, creating an error where the initially set timeout value may be 6 seconds but be passed to the thread pool as 6 milliseconds. The <filename>WorkWrapper.java</filename> file has been updated and correctly converts the timeout value from seconds to milliseconds.
</para>
<important>
@@ -1043,18 +1064,111 @@
<para>
Following is a list of known issues at the time of release.
</para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1286">JBPAPP-1286</ulink>: Footnotes within documentation tables and lists do not appear within PDFs. This issue resides within FOP and currently no workaround exists. Where possible footnotes are not used in the circumstances mentioned, however in documents such as the Release Notes the web address of a JIRA is automaticly generated as a footnote and places a number beside that of the JIRA, referencing a footnote that does not appear.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-909">JBPAPP-909</ulink>: Within the Hibernate component of the EAP the HashMap and HashSet iteration order changed from past releases because of support for JDK 1.6. However this has meant that the order of columns in union clauses and union-subclasses has changed, generating a slight impact on the components performance.
- </para>
- </listitem>
- </itemizedlist>
+ <formalpara>
+ <title>General Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1286">JBPAPP-1286</ulink>: Footnotes within documentation tables and lists do not appear within PDFs. This issue resides within FOP and currently no workaround exists. Where possible footnotes are not used in the circumstances mentioned, however in documents such as the Release Notes the web address of a JIRA is automaticly generated as a footnote and places a number beside that of the JIRA, referencing a footnote that does not appear.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Hibernate Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1613">JBPAPP-1613</ulink>: Null values for columns mapped as boolean in Hibernate, are persisted as zero instead of null. When the <methodname>PreparedStatement.setNull( index, java.sql.Types.BIT ) </methodname> method is executed in the Sybase environment, Sybase JDBC converts the null value to a zero because Sybase does not allow null bit columns.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1555">JBPAPP-1555</ulink>: Currently in Hibernate the SybaseDialect uses Blob and Clob where it should be set up to use image and text. Tests ataining to this currently fail with the message:
+ </para>
+ <screen>
+ The method com.sybase.jdbc2.jdbc.SybResultSet.getBlob(String) is not supported and should not be called.
+ </screen>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1554">JBPAPP-1554</ulink>: The <methodname>FumTest.testCompositeKeyPathExpressions()</methodname> method within Hibernate fails since Sybase currently only allows one column in a subquery select list, with the only exception to this being that a subquery in an <code>EXISTS()</code> predicate can have <code>*</code> as the select list.
+ </para>
+ <para>
+ The current workaround for this is to not use the HQL <methodname>elements()</methodname> method if the elements have a composite key. Instead the HQL should be reformated to ensure there is no subquery with more than one item in the select list.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1545">JBPAPP-1545</ulink>: Currently ANSI joins fail when Hibernate is run in a Sybase environment and there are three or more joins where at least one of the joins involves a union.
+ </para>
+ <para>
+ A workaround for this issue exists where it is reconmended that a user does not use <literal>join fetches</literal> involving <literal>union subclasses</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1230">JBPAPP-1230</ulink>: In the Sybase environment when creating a subquery with an alias in use, the query will be incorrectly generated and cause an <exceptionname>Incorrect syntax near the keyword 'as'</exceptionname> error. This bug impacts the following tests such that at present they are expected to fail: <classname>CriteriaQueryTest.testSubselect</classname>, <classname>CriteriaQueryTest.testDetachedCriteriaAsSubQuery</classname>, <classname>DynamicFilterTest.testCriteriaControl</classname> and <classname>DynamicFilterTest.testCriteriaSubqueryWithFilters</classname>.
+ </para>
+ <para>
+ The known workaround is to use a HQL query instead of using a <methodname>DetachedCriteria</methodname> method in a subquery.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1082">JBPAPP-1082</ulink>: A limitation in the PostgreSQL JDBC driver causes a <exceptionname>javax.persistence.RollbackException</exceptionname>. This occurs when the <code>char</code> property is used without a value set as Hibernate then presists a string contaning the character <code>\u0000</code>, which causes PostgreSQL to generate an exception as it does not allow this character to be embedded in a string.
+ </para>
+ <para>
+ Currently a workaround for persisting the <code>\u0000</code> character in a <code>char</code> column using PostgreSQL does not exist. Instead it is reconmended that to persist a null value for the <code>char</code> property when it is uninitialized, the <methodname>java.lang.Character</methodname> method should be used.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1081">JBPAPP-1081</ulink>: In the Entity Manager documentation it is stated that table aliases are supported in <code>update</code> clauses, however at present this is not the case. To fix this, the code has to be modified to remove the identification variable in SQL for PostgreSQL, Microsoft SQL 2005 and Sybase.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1068">JBPAPP-1068</ulink>: When using Microsoft SQL and <code>@Type(type="text")</code> in creating a table, the field is correctly created as <code>"text"</code> however when a delete opperation is issued the field becomes set as a <varname>varchar</varname>, forcing the Microsoft SQL driver to return the error:
+ </para>
+ <screen>
+ The data types text and nvarchar are incompatible in the equal to operator.
+ </screen>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1063">JBPAPP-1063</ulink>: Currently MySQL does not support milisecond and microsecond measurements when returning database values such as <code>TIME</code> and <code>TIMESTAMP</code>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-953">JBPAPP-953</ulink>: Hibernate Core and Annotations do not currently support the Hypersonic 1.8.0.8 database. Support for the version 1.8.0.8 of the Hypersonic database is planned for future releases.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-946">JBPAPP-946</ulink>: Within the Hibernate Entity Manager three different <exceptionname>NullPointerExceptions</exceptionname> are being investigated in relation to the EJB3 configuration, transaction operations when they are extended and packaging.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-906">JBPAPP-906</ulink>: A bug exists within the Hibernate Core whereby the unstable synchronized Java6 <methodname>ClassLoader.loadClass</methodname> method is utilized creating a deserialized String. This causes a problem where if multiple threads are loading database rows containging arrays of strings, one thread is forced to undertake all the procedure while the other threads are left dormant.
+ </para>
+ <para>
+ The implemented workaround for this issue is to use <code>-Dsun.lang.ClassLoader.allowArraySyntax=true</code>, which can be a default setting within the <filename>run.conf</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-909">JBPAPP-909</ulink>: Within the Hibernate component of the EAP the HashMap and HashSet iteration order changed from past releases because of support for JDK 1.6. However this has meant that the order of columns in union clauses and union-subclasses has changed, generating a slight impact on the components performance.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
</section>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
Modified: projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
===================================================================
--- projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml 2009-02-02 23:14:03 UTC (rev 83789)
+++ projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml 2009-02-03 02:49:21 UTC (rev 83790)
@@ -374,6 +374,19 @@
<itemizedlist>
<listitem>
<para>
+ There was an issue with the <methodname>MessagingXAResource.isSameRM(XAResource)</methodname> method whereby the method delegates checking to the <classname>ResourceManager</classname> <varname>serverID</varname>. This instigates the case where the <methodname>xasess2.start(xid, TMJOIN)</methodname> method is called and the <methodname>MessagingXAResource.isSameRM(XAResource)</methodname> method returns true but the resource manager does not hold the transaction state required to perform a <code>TMJOIN</code>. Further to this when a session is closed the <methodname>SessionAspect.handleClose()</methodname> method is called, yet the <code>tx</code> was removed from the transaction manager meaning it is no longer in the <code>conn1</code> resource manager.
+ </para>
+ <para>
+ To correct this both the <methodname>MessagingXAResource.isSameRM</methodname> method and <classname>ResourceManager</classname> have the same <code>serverID</code> and the same map of transactions, ensuring that if the <classname>ResourceManager</classname> was to ever return true, the call to <methodname>start(TMJOIN)</methodname> would correctly succeed. To note is that the transaction will rollback at completion time and any message delivered in the <code>tx</code> will be redelivered.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Client connection parameters were not being passed to the JBoss Remoting layer, leaving parameters such as <varname>validatorPingPeriod</varname> and <varname>validatorTimeout</varname> to be used with default values within Remoting instead of the configured values. In correcting this issue, the <filename>JMSRemotingConnection.java</filename> file has been updated so that when the <methodname> client.addConnectionListener</methodname> method is called within the <methodname>addConnectionListener</methodname> and <methodname>addPlainConnectionListener</methodname> methods, it also passes the configured parameters.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
The <literal>default</literal> profile for JBoss without any reconfiguration uses the <classname>ClusteredConnectionFactory</classname> with a non-clustered post-office, however warnings would be loged about this behavior when the log messages should be reduced from a <varname>WARN</varname> level to an <varname>INFO</varname> level. The upgrade to this version of JBoss Messaging sees this implemented within the log.
</para>
</listitem>
@@ -570,11 +583,23 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1548">JBPAPP-1548</ulink>: The JBoss Web Services component of the EAP has been upgraded to version 2.2.2.SP11. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1560">JBPAPP-1560</ulink>: The JBoss Web Services <filename>glassfigh-jaxb</filename> component of the EAP has been upgraded to version 2.1.4.patch01. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
<para>
+ The <literal>com.sun.xml.bind.v2.runtime.reflect.opt</literal> package contains classes to optimize field and method access by dynamically generating classes. Within the <classname>Injector</classname> class there is a <literal>HashMap</literal> value that is wrapped within a <literal>WeakReference</literal> however since there is only a <literal>WeakReference</literal> to the <classname>Injector</classname> class within this, the <literal>HashMap</literal> is garbage collected. To fix this the reference has been changed to a <literal>StrongReference</literal> and in order to maintain the original requirements, the <classname>Injector</classname> is now passed a reference to the ClassLoader instead of containing one specifically.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1210">JBPAPP-1210</ulink>: The JBoss Web Services component of the EAP has been upgraded to version 2.0.1.SP2_CP05. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
When deploying JBoss Web Services within EAP without internet access, <classname>JBossWSEntityResolver</classname> would not resolve any schemas causing Web Services for Remote Portlets (WSRP) to produce an error. This issue has been fixed by modifying <classname>JBossWSEntityResolver</classname> within <filename>WSDL11Reader.java</filename> to resolve schemas locally when an internet connection is unavaliable.
</para>
</listitem>
@@ -609,11 +634,6 @@
</listitem>
<listitem>
<para>
- The <literal>com.sun.xml.bind.v2.runtime.reflect.opt</literal> package contains classes to optimize field and method access by dynamically generating classes. Within the <classname>Injector</classname> class there is a <literal>HashMap</literal> value that is wrapped within a <literal>WeakReference</literal> however since there is only a <literal>WeakReference</literal> to the <classname>Injector</classname> class within this, the <literal>HashMap</literal> is garbage collected. To fix this the reference has been changed to a <literal>StrongReference</literal> and in order to maintain the original requirements, the <classname>Injector</classname> is now passed a reference to the ClassLoader instead of containing one specifically.
- </para>
- </listitem>
- <listitem>
- <para>
When creating messages in SOAP 1.2 without attachments, the <classname>SOAPMessageImpl</classname> class sets the <varname>contentType</varname> variable to <literal>text/xml</literal>, which was incorrect. This has now been rectified by amending <varname>contentType</varname> to use the value <literal>application/soap+xml</literal> by adding the <methodname>getSAPContentType()</methodname> method to <filename>SOAPMessageImpl.java</filename> and updating <filename>DispatchImpl.java</filename> to correctly reference the SOAP message context.
</para>
@@ -644,16 +664,6 @@
</para>
</listitem>
<listitem>
- <!--JBPAPP-1440--> <para>
-
- </para>
- </listitem>
- <listitem>
- <!--JBPAPP-1558--> <para>
-
- </para>
- </listitem>
- <listitem>
<para>
When JBoss Web Services is being used as a client, the information within the <methodname>DOMUtils.clearThreadLocals()</methodname> method was not cleared for incoming client calls. In order to fix this the call to <methodname>DOMUtils.clearThreadLocals()</methodname> has been moved to the <classname>MessageContextAssociation</classname> class and is executed once the last message has been processed. The files that have been updated in order to incorporate the fix are: <filename>DOMUtils.java</filename>, <filename>XMLContent.java</filename>, <filename>ProviderImpl.java</filename>, <filename>MessageContextAssociation.java</filename>, <filename>MessageContextJAXWS.java</filename> and <filename>RequestHandlerImpl.java</filename>.
</para>
@@ -663,16 +673,11 @@
When the <varname>webServiceHost</varname> property was not set, the <ulink url="http://localhost:8080/jbossws/services ">http://localhost:8080/jbossws/services</ulink> page presented the host name as <exceptionname>jbossws.undefined.host</exceptionname>. A <methodname>createAddress</methodname> method has been added to <filename>ContextServlet.java</filename> which dynamically updates the WSDL and XSD files with the address from the request URL before displaying information to the user.
</para>
</listitem>
- <listitem>
- <!--JBPAPP-1560--> <para>
-
- </para>
- </listitem>
</itemizedlist>
</listitem>
<note>
<para>
- The JBoss Web Services upgrade 2.2.2.SP11 also includes the security fix <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1548">JBPAPP-1548</ulink>, discussed in the Security Issue section.
+ The JBoss Web Services upgrade 2.0.1.SP2_CP05 also includes the security fix <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1548">JBPAPP-1548</ulink>, discussed in the Security Issue section.
</para>
</note>
</itemizedlist>
@@ -938,6 +943,27 @@
<itemizedlist>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1670">JBPAPP-1670</ulink>: The JacORB component of the EAP has been upgraded to version 2.3.0jboss.patch6-brew. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ A bug existed that would cause <filename>JacORB 2.3.0.jboss5</filename> to become unresponsive during shutdown. In rectifing this issue, the <filename>POA.java</filename> file has been modified so that instead of executing:
+ </para>
+<programlisting>
+throw new org.omg.CORBA.OBJECT_NOT_EXIST();
+</programlisting>
+ <para>
+ the following is now executed:
+ </para>
+<programlisting>
+throw new ObjectNotActive();
+</programlisting>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1636">JBPAPP-1636</ulink>: Affecting only third party adapters was an issue when one of these adapters handled the scheduling of work to be performed. The <classname>ExecutionContext</classname> class contained a value in seconds, from which the <methodname>getCompletionTimeout</methodname> method of <classname>org.jboss.resource.work.WorkWrapper</classname> obtains its information. An issue arises with <methodname>getCompletionTimeout</methodname> expecting the value to be in milliseconds, creating an error where the initially set timeout value may be 6 seconds but be passed to the thread pool as 6 milliseconds. The <filename>WorkWrapper.java</filename> file has been updated and correctly converts the timeout value from seconds to milliseconds.
</para>
</listitem>
@@ -1237,23 +1263,116 @@
<para>
Following is a list of known issues at the time of release.
</para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1286">JBPAPP-1286</ulink>: Footnotes within documentation tables and lists do not appear within PDFs. This issue resides within FOP and currently no workaround exists. Where possible footnotes are not used in the circumstances mentioned, however in documents such as the Release Notes the web address of a JIRA is automaticly generated as a footnote and places a number beside that of the JIRA, referencing a footnote that does not appear.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-909">JBPAPP-909</ulink>: Within the Hibernate component of the EAP the HashMap and HashSet iteration order changed from past releases because of support for JDK 1.6. However this has meant that the order of columns in union clauses and union-subclasses has changed, generating a slight impact on the components performance.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-885">JBPAPP-885</ulink>: An issue exists where if <methodname>DefaultRedeliveryDelay</methodname> or <methodname>RedeliveryDelay</methodname> is set to a value apart from zero, messages will not be redelivered even though the method <methodname>session.rollback()</methodname> had been called. This issue will not be fixed because redelivery delay is handled on the server side and the message is already acknowledged before delivery of the message with a non durable subscription. For the Enterprise Application Platform, this means that redelivery delays with non durable subscriptions cannot be supported.
- </para>
- </listitem>
- </itemizedlist>
+ <formalpara>
+ <title>General Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1286">JBPAPP-1286</ulink>: Footnotes within documentation tables and lists do not appear within PDFs. This issue resides within FOP and currently no workaround exists. Where possible footnotes are not used in the circumstances mentioned, however in documents such as the Release Notes the web address of a JIRA is automaticly generated as a footnote and places a number beside that of the JIRA, referencing a footnote that does not appear.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-885">JBPAPP-885</ulink>: An issue exists where if <methodname>DefaultRedeliveryDelay</methodname> or <methodname>RedeliveryDelay</methodname> is set to a value apart from zero, messages will not be redelivered even though the method <methodname>session.rollback()</methodname> had been called. This issue will not be fixed because redelivery delay is handled on the server side and the message is already acknowledged before delivery of the message with a non durable subscription. For the Enterprise Application Platform, this means that redelivery delays with non durable subscriptions cannot be supported.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Hibernate Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1613">JBPAPP-1613</ulink>: Null values for columns mapped as boolean in Hibernate, are persisted as zero instead of null. When the <methodname>PreparedStatement.setNull( index, java.sql.Types.BIT ) </methodname> method is executed in the Sybase environment, Sybase JDBC converts the null value to a zero because Sybase does not allow null bit columns.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1555">JBPAPP-1555</ulink>: Currently in Hibernate the SybaseDialect uses Blob and Clob where it should be set up to use image and text. Tests ataining to this currently fail with the message:
+ </para>
+ <screen>
+ The method com.sybase.jdbc2.jdbc.SybResultSet.getBlob(String) is not supported and should not be called.
+ </screen>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1554">JBPAPP-1554</ulink>: The <methodname>FumTest.testCompositeKeyPathExpressions()</methodname> method within Hibernate fails since Sybase currently only allows one column in a subquery select list, with the only exception to this being that a subquery in an <code>EXISTS()</code> predicate can have <code>*</code> as the select list.
+ </para>
+ <para>
+ The current workaround for this is to not use the HQL <methodname>elements()</methodname> method if the elements have a composite key. Instead the HQL should be reformated to ensure there is no subquery with more than one item in the select list.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1545">JBPAPP-1545</ulink>: Currently ANSI joins fail when Hibernate is run in a Sybase environment and there are three or more joins where at least one of the joins involves a union.
+ </para>
+ <para>
+ A workaround for this issue exists where it is reconmended that a user does not use <literal>join fetches</literal> involving <literal>union subclasses</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1230">JBPAPP-1230</ulink>: In the Sybase environment when creating a subquery with an alias in use, the query will be incorrectly generated and cause an <exceptionname>Incorrect syntax near the keyword 'as'</exceptionname> error. This bug impacts the following tests such that at present they are expected to fail: <classname>CriteriaQueryTest.testSubselect</classname>, <classname>CriteriaQueryTest.testDetachedCriteriaAsSubQuery</classname>, <classname>DynamicFilterTest.testCriteriaControl</classname> and <classname>DynamicFilterTest.testCriteriaSubqueryWithFilters</classname>.
+ </para>
+ <para>
+ The known workaround is to use a HQL query instead of using a <methodname>DetachedCriteria</methodname> method in a subquery.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1082">JBPAPP-1082</ulink>: A limitation in the PostgreSQL JDBC driver causes a <exceptionname>javax.persistence.RollbackException</exceptionname>. This occurs when the <code>char</code> property is used without a value set as Hibernate then presists a string contaning the character <code>\u0000</code>, which causes PostgreSQL to generate an exception as it does not allow this character to be embedded in a string.
+ </para>
+ <para>
+ Currently a workaround for persisting the <code>\u0000</code> character in a <code>char</code> column using PostgreSQL does not exist. Instead it is reconmended that to persist a null value for the <code>char</code> property when it is uninitialized, the <methodname>java.lang.Character</methodname> method should be used.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1081">JBPAPP-1081</ulink>: In the Entity Manager documentation it is stated that table aliases are supported in <code>update</code> clauses, however at present this is not the case. To fix this, the code has to be modified to remove the identification variable in SQL for PostgreSQL, Microsoft SQL 2005 and Sybase.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1068">JBPAPP-1068</ulink>: When using Microsoft SQL and <code>@Type(type="text")</code> in creating a table, the field is correctly created as <code>"text"</code> however when a delete opperation is issued the field becomes set as a <varname>varchar</varname>, forcing the Microsoft SQL driver to return the error:
+ </para>
+<screen>
+The data types text and nvarchar are incompatible in the equal to operator.
+</screen>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1063">JBPAPP-1063</ulink>: Currently MySQL does not support milisecond and microsecond measurements when returning database values such as <code>TIME</code> and <code>TIMESTAMP</code>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-953">JBPAPP-953</ulink>: Hibernate Core and Annotations do not currently support the Hypersonic 1.8.0.8 database. Support for the version 1.8.0.8 of the Hypersonic database is planned for future releases.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-946">JBPAPP-946</ulink>: Within the Hibernate Entity Manager three different <exceptionname>NullPointerExceptions</exceptionname> are being investigated in relation to the EJB3 configuration, transaction operations when they are extended and packaging.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-906">JBPAPP-906</ulink>: A bug exists within the Hibernate Core whereby the unstable synchronized Java6 <methodname>ClassLoader.loadClass</methodname> method is utilized creating a deserialized String. This causes a problem where if multiple threads are loading database rows containging arrays of strings, one thread is forced to undertake all the procedure while the other threads are left dormant.
+ </para>
+ <para>
+ The implemented workaround for this issue is to use <code>-Dsun.lang.ClassLoader.allowArraySyntax=true</code>, which can be a default setting within the <filename>run.conf</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-909">JBPAPP-909</ulink>: Within the Hibernate component of the EAP the HashMap and HashSet iteration order changed from past releases because of support for JDK 1.6. However this has meant that the order of columns in union clauses and union-subclasses has changed, generating a slight impact on the components performance.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
</section>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
More information about the jboss-cvs-commits
mailing list