[jboss-cvs] JBossAS SVN: r83835 - 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
Tue Feb 3 19:57:32 EST 2009
Author: irooskov at redhat.com
Date: 2009-02-03 19:57:32 -0500 (Tue, 03 Feb 2009)
New Revision: 83835
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 latest JIRAs
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-03 21:07:55 UTC (rev 83834)
+++ projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml 2009-02-04 00:57:32 UTC (rev 83835)
@@ -99,11 +99,11 @@
JBoss Web 2.0.0-6.CP09
</para>
</listitem>
-<!-- <listitem>
+ <listitem>
<para>
JBoss Web Services 1.2.1.GA_CP04
</para>
- </listitem> -->
+ </listitem>
<listitem>
<para>
JGroups 2.4.5
@@ -366,7 +366,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1533">JBPAPP-1533</ulink>: The JBoss Cache component of the EAP has been upgraded to version 1.4.1.SP11. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1533">JBPAPP-1533</ulink>: The JBoss Cache component of the Enterprise Application Platform has been upgraded to version 1.4.1.SP11. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -390,7 +390,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1531">JBPAPP-1531</ulink>: The JBoss Remoting 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-1531">JBPAPP-1531</ulink>: The JBoss Remoting component of the Enterprise Application Platform has been upgraded to version 2.2.2.SP11. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -474,7 +474,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1334">JBPAPP-1334</ulink>: The JBoss Web component of the EAP has been upgraded to version 2.0.0-6.CP09. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1334">JBPAPP-1334</ulink>: The JBoss Web component of the Enterprise Application Platform has been upgraded to version 2.0.0-6.CP09. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -487,14 +487,30 @@
</itemizedlist>
</para>
</formalpara>
- <!-- <formalpara>
+ <formalpara>
<title>JBoss Web Services</title>
<para>
<itemizedlist>
-
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-734">JBPAPP-734</ulink>: The JBoss Web Services component of the Enterprise Application Platform has been upgraded to version 1.2.1.GA_CP04. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Before the upgrade, the <methodname>org.jboss.ws.extensions.security.SignatureVerificationOperation.process()</methodname> method would generate an exception if the <classname>org.jboss.ws package</classname> <varname>loglevel</varname> value for both the client and the service was not set to <varname>DEBUG</varname>. The issue was discovered to be with the SOAP content model as some message logs were not procuded, preventing the model from progressing to the correct representation before the signature was computed. To correct this the <filename>SOAPContentElement.java</filename> file has been modified to include the new methods <methodname>getPreviousSibling()</methodname> and <methodname>getNextSibling()</methodname>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <note>
+ <para>
+ The JBoss Web Services upgrade 1.2.1.GA_CP04 also includes the security fix <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1565">JBPAPP-1565</ulink>, discussed in the Security Issue section.
+ </para>
+ </note>
</itemizedlist>
</para>
- </formalpara> -->
+ </formalpara>
<formalpara>
<title>JBoss Seam</title>
<para>
@@ -506,7 +522,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1494">JBPAPP-1494</ulink>: The portal example that was previously included with the Seam EAP distribution has been removed in order to avoid confusion that Seam 1.2.1 included with the EAP supports portal.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1494">JBPAPP-1494</ulink>: The portal example that was previously included with the Seam Enterprise Application Platform distribution has been removed in order to avoid confusion that Seam 1.2.1 included with the EAP supports portal.
</para>
</listitem>
<listitem>
@@ -523,7 +539,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1580">JBPAPP-1580</ulink>: The JBoss Hibernate Core component of the EAP has been upgraded to version 3.2.4.SP1.CP07. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1580">JBPAPP-1580</ulink>: The JBoss Hibernate Core component of the Enterprise Application Platform has been upgraded to version 3.2.4.SP1.CP07. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -536,7 +552,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1582">JBPAPP-1582</ulink>: A new Sybase dialect called <classname>SybaseASE15Dialect</classname> is included with this CP release to support Sybase ASE 15 and this dialect now becomes apart of the EAP certified configuration. Previous Sybase dialects are now considered deprecated and may be removed from future releases; however support will still be maintained for users who do not wish to move to the new dialect.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1582">JBPAPP-1582</ulink>: A new Sybase dialect called <classname>SybaseASE15Dialect</classname> is included with this CP release to support Sybase ASE 15 and this dialect now becomes apart of the Enterprise Application Platform certified configuration. Previous Sybase dialects are now considered deprecated and may be removed from future releases; however support will still be maintained for users who do not wish to move to the new dialect.
</para>
</listitem>
<!-- <listitem>
@@ -624,7 +640,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1259">JBPAPP-1259</ulink>: When using <methodname>dynamicUpdate</methodname> to generate SQL and the version field is specified by the user to not be updated, the <methodname>AbstractEntityPersiter.getPropertiesToUpdate</methodname> method would still update the field causing exceptions to appear in certain cases. Within this EAP update <filename>AbstractEntityPersister.java</filename> has been corrected to check if the user has explicitly said that the version field should not be updated and does not update the field if this is the case.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1259">JBPAPP-1259</ulink>: When using <methodname>dynamicUpdate</methodname> to generate SQL and the version field is specified by the user to not be updated, the <methodname>AbstractEntityPersiter.getPropertiesToUpdate</methodname> method would still update the field causing exceptions to appear in certain cases. Within this Enterprise Application Platform update <filename>AbstractEntityPersister.java</filename> has been corrected to check if the user has explicitly said that the version field should not be updated and does not update the field if this is the case.
</para>
</listitem>
<listitem>
@@ -651,7 +667,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1510">JBPAPP-1510</ulink>: The JBoss Transaction Service component of the EAP has been upgraded to version 4.2.3.SP5.CP04. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1510">JBPAPP-1510</ulink>: The JBoss Transaction Service component of the Enterprise Application Platform has been upgraded to version 4.2.3.SP5.CP04. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -710,7 +726,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1565">JBPAPP-1565</ulink>: An exploit existed within the JBoss Web Services component of the EAP that would allow anyone to view any xml file from any location if <literal>&resource=path/of/an/xmlfile.xml</literal> was applied to the end of any WSDL (Web Services Definition Language) access URL. The <filename>WSDLRequestHandler.java</filename> file has been updated to only allow the parent of a WSDL file, a servers data or WSDL or overridden WSDL publish directories access to xml file resources. Additional test files are also included which were created to ensure proper operation was being undertaken. (CVE-2009-0027 )
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1565">JBPAPP-1565</ulink>: An exploit existed within the JBoss Web Services component of the Enterprise Application Platform that would allow anyone to view any xml file from any location if <literal>&resource=path/of/an/xmlfile.xml</literal> was applied to the end of any WSDL (Web Services Definition Language) access URL. The <filename>WSDLRequestHandler.java</filename> file has been updated to only allow the parent of a WSDL file, a servers data or WSDL or overridden WSDL publish directories access to xml file resources. Additional test files are also included which were created to ensure proper operation was being undertaken. (CVE-2009-0027 )
</para>
</listitem>
</itemizedlist>
@@ -727,7 +743,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1362">JBPAPP-1362</ulink>: The Getting Started Guide section 2.3 has been updated to include information about the <code>-b</code> option (and equivalents) that can be used on the command line to change the binding addresses of the EAP for remote connectivity.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1362">JBPAPP-1362</ulink>: The Getting Started Guide section 2.3 has been updated to include information about the <code>-b</code> option (and equivalents) that can be used on the command line to change the binding addresses of the Enterprise Application Platform for remote connectivity.
</para>
</listitem>
<listitem>
@@ -744,7 +760,7 @@
<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:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1670">JBPAPP-1670</ulink>: The JacORB component of the Enterprise Application Platform has been upgraded to version 2.3.0jboss.patch6-brew. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -785,12 +801,12 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1540">JBPAPP-1540</ulink>: Within the cluster section of the EAP, the <classname>GossipRouter</classname> and <classname>GossipClient</classname> (TCPGOSSIP) did not have socket read timeouts, socket linger timeouts and backlog set to provide the best behavior when heavily utilized or under network situations in need of improvement. This fix provides default values and configuration options for these in order to avoid problematic situations.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1540">JBPAPP-1540</ulink>: Within the cluster section of the Enterprise Application Platform, the <classname>GossipRouter</classname> and <classname>GossipClient</classname> (TCPGOSSIP) did not have socket read timeouts, socket linger timeouts and backlog set to provide the best behavior when heavily utilized or under network situations in need of improvement. This fix provides default values and configuration options for these in order to avoid problematic situations.
</para>
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1539">JBPAPP-1539</ulink>: When running parallel instances of the EAP on Linux a bug existed where messages between the JGroups component of each instance would be picked up by both because all messages sent to the port number for Multicast Sockets would be picked up by both instances. The issue has been fixed by re-writing the code for Multicast Sockets so that the constructor uses a group address along with the port number as identifiers. This ensures that an instance of the EAP only receives messages pertaining to its specific group and thus inhibits channel crosstalk.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1539">JBPAPP-1539</ulink>: When running parallel instances of the Enterprise Application Platform on Linux a bug existed where messages between the JGroups component of each instance would be picked up by both because all messages sent to the port number for Multicast Sockets would be picked up by both instances. The issue has been fixed by re-writing the code for Multicast Sockets so that the constructor uses a group address along with the port number as identifiers. This ensures that an instance of the Enterprise Application Platform only receives messages pertaining to its specific group and thus inhibits channel crosstalk.
</para>
</listitem>
<listitem>
@@ -810,7 +826,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1532">JBPAPP-1532</ulink>: The JGroups clustering component of the EAP has been upgraded to version 2.4.5. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1532">JBPAPP-1532</ulink>: The JGroups clustering component of the Enterprise Application Platform has been upgraded to version 2.4.5. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -852,12 +868,12 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1521">JBPAPP-1521</ulink>: The <classname>CleanShutdownInterceptor</classname> class would log a <exceptionname>GenericClusteringException</exceptionname> when the container had failed to shut down correctly or failed to start correctly and because of this behavior the error message displayed because of the exception should be updated to indicate that it may be an issue with the container failing to start instead of only failing to shut down. In this latest EAP update, the error message has been updated to reflect both situations which may be the cause of the exception.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1521">JBPAPP-1521</ulink>: The <classname>CleanShutdownInterceptor</classname> class would log a <exceptionname>GenericClusteringException</exceptionname> when the container had failed to shut down correctly or failed to start correctly and because of this behavior the error message displayed because of the exception should be updated to indicate that it may be an issue with the container failing to start instead of only failing to shut down. In this latest Enterprise Application Platform update, the error message has been updated to reflect both situations which may be the cause of the exception.
</para>
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1479">JBPAPP-1479</ulink>: Within the different distributions of the EAP that are 4.2 and 4.3, both the <filename>JBossMQ</filename> and <filename>JBoss Messaging</filename> application policies have been present within the <filename>login-config.xml</filename> file, when <filename>JBossMQ</filename> is only included in the 4.2 distribution and <filename>JBoss Messaging</filename> is similarly only included in the 4.3 distribution.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1479">JBPAPP-1479</ulink>: Within the different distributions of the Enterprise Application Platform that are 4.2 and 4.3, both the <filename>JBossMQ</filename> and <filename>JBoss Messaging</filename> application policies have been present within the <filename>login-config.xml</filename> file, when <filename>JBossMQ</filename> is only included in the 4.2 distribution and <filename>JBoss Messaging</filename> is similarly only included in the 4.3 distribution.
</para>
<para>
This has been rectified in this release by modifying <filename>build.xml</filename> and <filename>login-config.xml</filename> to differentiate between requirements for each individual distribution.
@@ -870,7 +886,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1460">JBPAPP-1460</ulink>: The JavaServer Faces (JSF) has been updated to version 1.2_10 for this EAP release. This update corrects numerous bugs and details on these fixes can be found at <ulink url="https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html">https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html</ulink>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1460">JBPAPP-1460</ulink>: The JavaServer Faces (JSF) has been updated to version 1.2_10 for this Enterprise Application Platform release. This update corrects numerous bugs and details on these fixes can be found at <ulink url="https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html">https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html</ulink>
</para>
</listitem>
<listitem>
@@ -885,7 +901,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1289">JBPAPP-1289</ulink>: The JBoss JAXR component of the EAP has been upgraded to version 1.2.0.SP2. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1289">JBPAPP-1289</ulink>: The JBoss JAXR component of the Enterprise Application Platform has been upgraded to version 1.2.0.SP2. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -897,7 +913,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1275">JBPAPP-1275</ulink>: The Xalan part of the EAP has been upgraded from version 2.7.0 to 2.7.0.patch02. This upgrade removes the circumstance where an application which heavily used Xalan within large multi-threaded environments would encounter blocking situations.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1275">JBPAPP-1275</ulink>: The Xalan part of the Enterprise Application Platform has been upgraded from version 2.7.0 to 2.7.0.patch02. This upgrade removes the circumstance where an application which heavily used Xalan within large multi-threaded environments would encounter blocking situations.
</para>
</listitem>
<listitem>
@@ -907,7 +923,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1249">JBPAPP-1249</ulink>: The JSF component of the EAP has been upgraded to version 1.2_10. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1249">JBPAPP-1249</ulink>: The JSF component of the Enterprise Application Platform has been upgraded to version 1.2_10. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -1004,12 +1020,12 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1099">JBPAPP-1099</ulink>: The <filename>commons-beanutils.jar</filename> file within the EAP had the incorrect version in the <filename>manifest.mf</filename> file. Through the course of correcting this bug, it was found that the <literal>beanutils</literal> component was outdated and a newer version contained many advantages. In this update to the EAP <literal>beanutils</literal> has been upgraded to version 1.8.0, which sees the significant improvement that fixes a memory leak caused by a circular reference concerning the <classname>WeakHashMap</classname>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1099">JBPAPP-1099</ulink>: The <filename>commons-beanutils.jar</filename> file within the Enterprise Application Platform had the incorrect version in the <filename>manifest.mf</filename> file. Through the course of correcting this bug, it was found that the <literal>beanutils</literal> component was outdated and a newer version contained many advantages. In this update to the EAP <literal>beanutils</literal> has been upgraded to version 1.8.0, which sees the significant improvement that fixes a memory leak caused by a circular reference concerning the <classname>WeakHashMap</classname>.
</para>
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1002">JBPAPP-1002</ulink>: Bean Managed Transactions (BMT) Stateful Session Beans used to be logged when transactions were not completed between invocations. However this was an error as BMT Stateful Session Beans are allowed to have this occurrence and so this logging measure has been removed in this EAP update.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1002">JBPAPP-1002</ulink>: Bean Managed Transactions (BMT) Stateful Session Beans used to be logged when transactions were not completed between invocations. However this was an error as BMT Stateful Session Beans are allowed to have this occurrence and so this logging measure has been removed in this Enterprise Application Platform update.
</para>
</listitem>
<listitem>
@@ -1045,7 +1061,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-713">JBPAPP-713</ulink>: A Classloader leak existed causing a <errorname>OutOfMemoryError: PermGen</errorname> error. To correct this issue the EAP now uses <filename>beanutils 1.8.0</filename> which fixes this <errorname>OutOfMemoryError</errorname>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-713">JBPAPP-713</ulink>: A Classloader leak existed causing a <errorname>OutOfMemoryError: PermGen</errorname> error. To correct this issue the Enterprise Application Platform now uses <filename>beanutils 1.8.0</filename> which fixes this <errorname>OutOfMemoryError</errorname>.
</para>
</listitem>
<listitem>
@@ -1103,6 +1119,19 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1546">JBPAPP-1546</ulink>: When using Sybase, <methodname>SchemaExport</methodname> cannot be used to create stored procedures while in chained transaction mode. The suggested workaround for this case is to add the following code follwing the defining of the new stored procedure:
+ </para>
+<programlisting>
+<database-object>
+ <create>
+ sp_procxmode paramHandling, 'chained'
+ </create>
+ <drop/>
+</database-object>
+</programlisting>
+ </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>
@@ -1163,7 +1192,7 @@
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-909">JBPAPP-909</ulink>: Within the Hibernate component of the Enterprise Application Platform 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>
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-03 21:07:55 UTC (rev 83834)
+++ projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml 2009-02-04 00:57:32 UTC (rev 83835)
@@ -369,7 +369,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1615">JBPAPP-1615</ulink>: The JBoss Messaging component of the EAP has been upgraded to version 1.4.0.SP3-CP05. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1615">JBPAPP-1615</ulink>: The JBoss Messaging component of the Enterprise Application Platform has been upgraded to version 1.4.0.SP3-CP05. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -456,7 +456,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1533">JBPAPP-1533</ulink>: The JBoss Cache component of the EAP has been upgraded to version 1.4.1.SP11. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1533">JBPAPP-1533</ulink>: The JBoss Cache component of the Enterprise Application Platform has been upgraded to version 1.4.1.SP11. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -480,7 +480,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1531">JBPAPP-1531</ulink>: The JBoss Remoting 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-1531">JBPAPP-1531</ulink>: The JBoss Remoting component of the Enterprise Application Platform has been upgraded to version 2.2.2.SP11. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -564,7 +564,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1334">JBPAPP-1334</ulink>: The JBoss Web component of the EAP has been upgraded to version 2.0.0-6.CP09. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1334">JBPAPP-1334</ulink>: The JBoss Web component of the Enterprise Application Platform has been upgraded to version 2.0.0-6.CP09. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -583,7 +583,7 @@
<itemizedlist>
<listitem>
<para>
- <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:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1560">JBPAPP-1560</ulink>: The JBoss Web Services <filename>glassfigh-jaxb</filename> component of the Enterprise Application Platform has been upgraded to version 2.1.4.patch01. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -595,12 +595,12 @@
</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:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1210">JBPAPP-1210</ulink>: The JBoss Web Services component of the Enterprise Application Platform 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 unavailable.
+ When deploying JBoss Web Services within Enterprise Application Platform 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 unavailable.
</para>
</listitem>
<listitem>
@@ -645,7 +645,7 @@
</listitem>
<listitem>
<para>
- WSDL dynamic address replacement was not working correctly in previous versions of the EAP since port and protocol numbers were not being considered. The <filename>WSDLRequestHandler.java</filename> file has been modified to use a new URL and protocol instead of the original URL and protocol in order to use the dynamically generated port and protocol numbers.
+ WSDL dynamic address replacement was not working correctly in previous versions of the Enterprise Application Platform since port and protocol numbers were not being considered. The <filename>WSDLRequestHandler.java</filename> file has been modified to use a new URL and protocol instead of the original URL and protocol in order to use the dynamically generated port and protocol numbers.
</para>
</listitem>
<listitem>
@@ -655,7 +655,7 @@
</listitem>
<listitem>
<para>
- JAAS certificate authentication support was not supported in the JBoss Web Services Security implementation, meaning that authentication via this method could not take place based on the certificate the client used to sign the message. Support for this has been added to JBoss Web Services and in tern the EAP with this component upgrade.
+ JAAS certificate authentication support was not supported in the JBoss Web Services Security implementation, meaning that authentication via this method could not take place based on the certificate the client used to sign the message. Support for this has been added to JBoss Web Services and in tern the Enterprise Application Platform with this component upgrade.
</para>
</listitem>
<listitem>
@@ -694,7 +694,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1494">JBPAPP-1494</ulink>: The portal example that was previously included with the Seam EAP distribution has been removed in order to avoid confusion that Seam 1.2.1 included with the EAP supports portal.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1494">JBPAPP-1494</ulink>: The portal example that was previously included with the Seam Enterprise Application Platform distribution has been removed in order to avoid confusion that Seam 1.2.1 included with the EAP supports portal.
</para>
</listitem>
<listitem>
@@ -711,7 +711,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1580">JBPAPP-1580</ulink>: The JBoss Hibernate Core component of the EAP has been upgraded to version 3.2.4.SP1.CP07. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1580">JBPAPP-1580</ulink>: The JBoss Hibernate Core component of the Enterprise Application Platform has been upgraded to version 3.2.4.SP1.CP07. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -724,7 +724,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1582">JBPAPP-1582</ulink>: A new Sybase dialect called <classname>SybaseASE15Dialect</classname> is included with this CP release to support Sybase ASE 15 and this dialect now becomes apart of the EAP certified configuration. Previous Sybase dialects are now considered deprecated and may be removed from future releases; however support will still be maintained for users who do not wish to move to the new dialect.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1582">JBPAPP-1582</ulink>: A new Sybase dialect called <classname>SybaseASE15Dialect</classname> is included with this CP release to support Sybase ASE 15 and this dialect now becomes apart of the Enterprise Application Platform certified configuration. Previous Sybase dialects are now considered deprecated and may be removed from future releases; however support will still be maintained for users who do not wish to move to the new dialect.
</para>
</listitem>
<!-- <listitem>
@@ -812,7 +812,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1259">JBPAPP-1259</ulink>: When using <methodname>dynamicUpdate</methodname> to generate SQL and the version field is specified by the user to not be updated, the <methodname>AbstractEntityPersiter.getPropertiesToUpdate</methodname> method would still update the field causing exceptions to appear in certain cases. Within this EAP update <filename>AbstractEntityPersister.java</filename> has been corrected to check if the user has explicitly said that the version field should not be updated and does not update the field if this is the case.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1259">JBPAPP-1259</ulink>: When using <methodname>dynamicUpdate</methodname> to generate SQL and the version field is specified by the user to not be updated, the <methodname>AbstractEntityPersiter.getPropertiesToUpdate</methodname> method would still update the field causing exceptions to appear in certain cases. Within this Enterprise Application Platform update <filename>AbstractEntityPersister.java</filename> has been corrected to check if the user has explicitly said that the version field should not be updated and does not update the field if this is the case.
</para>
</listitem>
<listitem>
@@ -839,7 +839,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1510">JBPAPP-1510</ulink>: The JBoss Transaction Service component of the EAP has been upgraded to version 4.2.3.SP5.CP04. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1510">JBPAPP-1510</ulink>: The JBoss Transaction Service component of the Enterprise Application Platform has been upgraded to version 4.2.3.SP5.CP04. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -898,7 +898,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1548">JBPAPP-1548</ulink>: An exploit existed within the JBoss Web Services component of the EAP that would allow anyone to view any xml file from any location if <literal>&resource=path/of/an/xmlfile.xml</literal> was applied to the end of any WSDL (Web Services Definition Language) access URL. The <filename>WSDLRequestHandler.java</filename> file has been updated to only allow the parent of a WSDL file, a servers data or WSDL or overridden WSDL publish directories access to xml file resources. Additional test files are also included which were created to ensure proper operation was being undertaken. (CVE-2009-0027 )
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1548">JBPAPP-1548</ulink>: An exploit existed within the JBoss Web Services component of the Enterprise Application Platform that would allow anyone to view any xml file from any location if <literal>&resource=path/of/an/xmlfile.xml</literal> was applied to the end of any WSDL (Web Services Definition Language) access URL. The <filename>WSDLRequestHandler.java</filename> file has been updated to only allow the parent of a WSDL file, a servers data or WSDL or overridden WSDL publish directories access to xml file resources. Additional test files are also included which were created to ensure proper operation was being undertaken. (CVE-2009-0027 )
</para>
</listitem>
</itemizedlist>
@@ -910,7 +910,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1649">JBPAPP-1649</ulink>: The documentation on the isolation of JGroup channels within the Server Configuration Guide was missing two parameters specific to the EAP 4.3 distribution. The parameters of
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1649">JBPAPP-1649</ulink>: The documentation on the isolation of JGroup channels within the Server Configuration Guide was missing two parameters specific to the Enterprise Application Platform 4.3 distribution. The parameters of
<varname>-Djboss.messaging.controlchanneludpport</varname> and <varname>-Djboss.messaging.datachanneludpport</varname> have been includedin section 19.7.10 with example ports and the text addressing the concern of <emphasis>Why do I need to change the multicast port if I change the address?</emphasis> has been updated to reflect what is happening in an improved way.
</para>
</listitem>
@@ -926,7 +926,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1362">JBPAPP-1362</ulink>: The Getting Started Guide section 2.3 has been updated to include information about the <code>-b</code> option (and equivalents) that can be used on the command line to change the binding addresses of the EAP for remote connectivity.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1362">JBPAPP-1362</ulink>: The Getting Started Guide section 2.3 has been updated to include information about the <code>-b</code> option (and equivalents) that can be used on the command line to change the binding addresses of the Enterprise Application Platform for remote connectivity.
</para>
</listitem>
<listitem>
@@ -943,7 +943,7 @@
<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:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1670">JBPAPP-1670</ulink>: The JacORB component of the Enterprise Application Platform has been upgraded to version 2.3.0jboss.patch6-brew. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -979,12 +979,12 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1540">JBPAPP-1540</ulink>: Within the cluster section of the EAP, the <classname>GossipRouter</classname> and <classname>GossipClient</classname> (TCPGOSSIP) did not have socket read timeouts, socket linger timeouts and backlog set to provide the best behavior when heavily utilized or under network situations in need of improvement. This fix provides default values and configuration options for these in order to avoid problematic situations.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1540">JBPAPP-1540</ulink>: Within the cluster section of the Enterprise Application Platform, the <classname>GossipRouter</classname> and <classname>GossipClient</classname> (TCPGOSSIP) did not have socket read timeouts, socket linger timeouts and backlog set to provide the best behavior when heavily utilized or under network situations in need of improvement. This fix provides default values and configuration options for these in order to avoid problematic situations.
</para>
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1539">JBPAPP-1539</ulink>: When running parallel instances of the EAP on Linux a bug existed where messages between the JGroups component of each instance would be picked up by both because all messages sent to the port number for Multicast Sockets would be picked up by both instances. The issue has been fixed by re-writing the code for Multicast Sockets so that the constructor uses a group address along with the port number as identifiers. This ensures that an instance of the EAP only receives messages pertaining to its specific group and thus inhibits channel crosstalk.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1539">JBPAPP-1539</ulink>: When running parallel instances of the Enterprise Application Platform on Linux a bug existed where messages between the JGroups component of each instance would be picked up by both because all messages sent to the port number for Multicast Sockets would be picked up by both instances. The issue has been fixed by re-writing the code for Multicast Sockets so that the constructor uses a group address along with the port number as identifiers. This ensures that an instance of the EAP only receives messages pertaining to its specific group and thus inhibits channel crosstalk.
</para>
</listitem>
<listitem>
@@ -1004,7 +1004,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1532">JBPAPP-1532</ulink>: The JGroups clustering component of the EAP has been upgraded to version 2.4.5. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1532">JBPAPP-1532</ulink>: The JGroups clustering component of the Enterprise Application Platform has been upgraded to version 2.4.5. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -1046,7 +1046,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1521">JBPAPP-1521</ulink>: The <classname>CleanShutdownInterceptor</classname> class would log a <exceptionname>GenericClusteringException</exceptionname> when the container had failed to shut down correctly or failed to start correctly and because of this behavior the error message displayed because of the exception should be updated to indicate that it may be an issue with the container failing to start instead of only failing to shut down. In this latest EAP update, the error message has been updated to reflect both situations which may be the cause of the exception.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1521">JBPAPP-1521</ulink>: The <classname>CleanShutdownInterceptor</classname> class would log a <exceptionname>GenericClusteringException</exceptionname> when the container had failed to shut down correctly or failed to start correctly and because of this behavior the error message displayed because of the exception should be updated to indicate that it may be an issue with the container failing to start instead of only failing to shut down. In this latest Enterprise Application Platform update, the error message has been updated to reflect both situations which may be the cause of the exception.
</para>
</listitem>
<listitem>
@@ -1056,7 +1056,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1479">JBPAPP-1479</ulink>: Within the different distributions of the EAP that are 4.2 and 4.3, both the <filename>JBossMQ</filename> and <filename>JBoss Messaging</filename> application policies have been present within the <filename>login-config.xml</filename> file, when <filename>JBossMQ</filename> is only included in the 4.2 distribution and <filename>JBoss Messaging</filename> is similarly only included in the 4.3 distribution.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1479">JBPAPP-1479</ulink>: Within the different distributions of the Enterprise Application Platform that are 4.2 and 4.3, both the <filename>JBossMQ</filename> and <filename>JBoss Messaging</filename> application policies have been present within the <filename>login-config.xml</filename> file, when <filename>JBossMQ</filename> is only included in the 4.2 distribution and <filename>JBoss Messaging</filename> is similarly only included in the 4.3 distribution.
</para>
<para>
This has been rectified in this release by modifying <filename>build.xml</filename> and <filename>login-config.xml</filename> to differentiate between requirements for each individual distribution.
@@ -1069,7 +1069,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1460">JBPAPP-1460</ulink>: The JavaServer Faces (JSF) has been updated to version 1.2_10 for this EAP release. This update corrects numerous bugs and details on these fixes can be found at <ulink url="https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html">https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html</ulink>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1460">JBPAPP-1460</ulink>: The JavaServer Faces (JSF) has been updated to version 1.2_10 for this Enterprise Application Platform release. This update corrects numerous bugs and details on these fixes can be found at <ulink url="https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html">https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html</ulink>
</para>
</listitem>
<listitem>
@@ -1084,7 +1084,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1289">JBPAPP-1289</ulink>: The JBoss JAXR component of the EAP has been upgraded to version 1.2.0.SP2. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1289">JBPAPP-1289</ulink>: The JBoss JAXR component of the Enterprise Application Platform has been upgraded to version 1.2.0.SP2. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -1096,7 +1096,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1275">JBPAPP-1275</ulink>: The Xalan part of the EAP has been upgraded from version 2.7.0 to 2.7.0.patch02. This upgrade removes the circumstance where an application which heavily used Xalan within large multi-threaded environments would encounter blocking situations.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1275">JBPAPP-1275</ulink>: The Xalan part of the Enterprise Application Platform has been upgraded from version 2.7.0 to 2.7.0.patch02. This upgrade removes the circumstance where an application which heavily used Xalan within large multi-threaded environments would encounter blocking situations.
</para>
</listitem>
<listitem>
@@ -1106,7 +1106,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1249">JBPAPP-1249</ulink>: The JSF component of the EAP has been upgraded to version 1.2_10. A list of the included fixes is as follows:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1249">JBPAPP-1249</ulink>: The JSF component of the Enterprise Application Platform has been upgraded to version 1.2_10. A list of the included fixes is as follows:
</para>
<itemizedlist>
<listitem>
@@ -1203,12 +1203,12 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1099">JBPAPP-1099</ulink>: The <filename>commons-beanutils.jar</filename> file within the EAP had the incorrect version in the <filename>manifest.mf</filename> file. Through the course of correcting this bug, it was found that the <literal>beanutils</literal> component was outdated and a newer version contained many advantages. In this update to the EAP <literal>beanutils</literal> has been upgraded to version 1.8.0, which sees the significant improvement that fixes a memory leak caused by a circular reference concerning the <classname>WeakHashMap</classname>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1099">JBPAPP-1099</ulink>: The <filename>commons-beanutils.jar</filename> file within the Enterprise Application Platform had the incorrect version in the <filename>manifest.mf</filename> file. Through the course of correcting this bug, it was found that the <literal>beanutils</literal> component was outdated and a newer version contained many advantages. In this update to the EAP <literal>beanutils</literal> has been upgraded to version 1.8.0, which sees the significant improvement that fixes a memory leak caused by a circular reference concerning the <classname>WeakHashMap</classname>.
</para>
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1002">JBPAPP-1002</ulink>: Bean Managed Transactions (BMT) Stateful Session Beans used to be logged when transactions were not completed between invocations. However this was an error as BMT Stateful Session Beans are allowed to have this occurrence and so this logging measure has been removed in this EAP update.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1002">JBPAPP-1002</ulink>: Bean Managed Transactions (BMT) Stateful Session Beans used to be logged when transactions were not completed between invocations. However this was an error as BMT Stateful Session Beans are allowed to have this occurrence and so this logging measure has been removed in this Enterprise Application Platform update.
</para>
</listitem>
<listitem>
@@ -1244,7 +1244,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-713">JBPAPP-713</ulink>: A Classloader leak existed causing a <errorname>OutOfMemoryError: PermGen</errorname> error. To correct this issue the EAP now uses <filename>beanutils 1.8.0</filename> which fixes this <errorname>OutOfMemoryError</errorname>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-713">JBPAPP-713</ulink>: A Classloader leak existed causing a <errorname>OutOfMemoryError: PermGen</errorname> error. To correct this issue the Enterprise Application Platform now uses <filename>beanutils 1.8.0</filename> which fixes this <errorname>OutOfMemoryError</errorname>.
</para>
</listitem>
<listitem>
@@ -1307,6 +1307,19 @@
</listitem>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1546">JBPAPP-1546</ulink>: When using Sybase, <methodname>SchemaExport</methodname> cannot be used to create stored procedures while in chained transaction mode. The suggested workaround for this case is to add the following code follwing the defining of the new stored procedure:
+ </para>
+<programlisting>
+<database-object>
+ <create>
+ sp_procxmode paramHandling, 'chained'
+ </create>
+ <drop/>
+</database-object>
+</programlisting>
+ </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>
@@ -1367,7 +1380,7 @@
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-909">JBPAPP-909</ulink>: Within the Hibernate component of the Enterprise Application Platform 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>
More information about the jboss-cvs-commits
mailing list