[jboss-cvs] JBossAS SVN: r96400 - projects/docs/enterprise/4.2.8/readme/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Nov 15 23:18:47 EST 2009
Author: laubai
Date: 2009-11-15 23:18:47 -0500 (Sun, 15 Nov 2009)
New Revision: 96400
Added:
projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP08.ent
projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP08.xml
Removed:
projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP07.ent
projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP07.xml
Modified:
projects/docs/enterprise/4.2.8/readme/en-US/Author_Group.xml
projects/docs/enterprise/4.2.8/readme/en-US/Book_Info.xml
Log:
Updated files for CP08.
Modified: projects/docs/enterprise/4.2.8/readme/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/4.2.8/readme/en-US/Author_Group.xml 2009-11-16 04:12:29 UTC (rev 96399)
+++ projects/docs/enterprise/4.2.8/readme/en-US/Author_Group.xml 2009-11-16 04:18:47 UTC (rev 96400)
@@ -4,8 +4,8 @@
<authorgroup>
<author>
- <firstname>Isaac</firstname>
- <surname>Rooskov</surname>
- <email>irooskov at redhat.com</email>
+ <firstname>Laura</firstname>
+ <surname>Bailey</surname>
+ <email>lbailey at redhat.com</email>
</author>
</authorgroup>
Modified: projects/docs/enterprise/4.2.8/readme/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.8/readme/en-US/Book_Info.xml 2009-11-16 04:12:29 UTC (rev 96399)
+++ projects/docs/enterprise/4.2.8/readme/en-US/Book_Info.xml 2009-11-16 04:18:47 UTC (rev 96400)
@@ -3,15 +3,15 @@
]>
<articleinfo>
- <title>Release Notes CP07</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 7</subtitle>
+ <title>Release Notes CP08</title>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 8</subtitle>
<edition>1.0</edition>
- <pubsnumber>6</pubsnumber>
+ <pubsnumber>1</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
<productnumber>4.2</productnumber>
<abstract>
<para>
- These release notes contain important information related to JBoss Enterprise Application Platform 4.2.0.CP07 that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing JBoss Enterprise Application Platform 4.2.0.CP07.
+ These release notes contain important information related to JBoss Enterprise Application Platform 4.2.0.CP08 that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing JBoss Enterprise Application Platform 4.2.0.CP08.
</para>
</abstract>
<isbn>N/A</isbn>
Deleted: projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP07.ent
===================================================================
--- projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP07.ent 2009-11-16 04:12:29 UTC (rev 96399)
+++ projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP07.ent 2009-11-16 04:18:47 UTC (rev 96400)
@@ -1,3 +0,0 @@
-<!ENTITY HOLDER "Red Hat, Inc">
-<!ENTITY YEAR "2009">
-<!ENTITY VERSION "4.2">
Deleted: projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP07.xml
===================================================================
--- projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP07.xml 2009-11-16 04:12:29 UTC (rev 96399)
+++ projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP07.xml 2009-11-16 04:18:47 UTC (rev 96400)
@@ -1,1516 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-<!ENTITY % RH_ENTITIES SYSTEM "./Common_Config/rh-entities.ent">
-%RH_ENTITIES;
-]>
-<article id="JBEAP-Release-Notes">
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/>
- <section id="Introduction">
- <title>
- Introduction
- </title>
- <para>
- These release notes contain important information related to JBoss Enterprise Application Platform &VERSION;. New features, known problems, resources, and other current issues are addressed here.
- </para>
- <section id="Overview">
- <title>Overview</title>
- <para>
- JBoss Enterprise Application Platform is the next evolutionary step in open source enterprise software. It is a powerful tool for developing rich, high performance, Web 2.0 applications on a pure Java Platform.
- </para>
- <para>
- JBoss Enterprise Application Platform provides complete compatibility with existing J2EE 1.4 enterprise Java applications. At the same time, almost all the key features and components defined in the Java EE 5.0 specification are supported. So your new enterprise Java applications can take immediate advantage of the Java EE 5.0's significantly simpler POJO-based programming model.
- </para>
- <para>
- Further, by integrating best-of-breed open source frameworks such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache the Platform takes advantage of innovations in the open source community. As well, JBoss Enterprise Application Platform is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.
- </para>
- <para>
- All of which means you can develop your new application taking advantage of Java EE 5.0 technologies immediately and with the confidence of knowing it will remain forward-compatible with future versions of the JBoss Platform.
- </para>
- </section>
- </section>
- <!--<section id="New_Features">
- <title>New Features in JBoss Enterprise Application Platform &VERSION;</title>
- <section id="Messaging">
- <title>JBoss Messaging</title>
- <para>
- In this release, JBoss MQ 1.3 has been replaced with JBoss Messaging 1.4. JBoss Messaging provides a high performance messaging infrastructure for JBoss Enterprise Application Platform.
- </para>
- </section>
- <section id="JAX_WS">
- <title>JBoss Web Services 2.0.1</title>
- <para>
- JBoss Web Services is upgraded to 2.0.1 in this release and will now provide a complete implementation of JAX-WS.
- </para>
- </section>
- </section> -->
- <section id="Component_Versions">
- <title>Component Versions</title>
- <para>
- This section details the versions of the components which create the Enterprise Application Platform 4.3 that can be found in this Cumulative Patch release.
- </para>
- <!-- <itemizedlist>
- <listitem>
- <para>
- JBoss Application Server 4.2.z
- </para>
- </listitem>
- <listitem>
- <para>
- Hibernate Core 3.2.4.SP1.CP07
- </para>
- </listitem>
- <listitem>
- <para>
- Hibernate Annotations 3.2.1.GA.CP03
- </para>
- </listitem>
- <listitem>
- <para>
- Hibernate Entity Manager 3.2.1.GA_CP04
- </para>
- </listitem>
- <listitem>
- <para>
- JAF 1.2_10
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Cache 1.4.1.SP11
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss JAXR 1.2.0.SP2
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Remoting 2.2.2.SP11
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Transactions 4.2.3.SP5.CP04
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Web 2.0.0-6.CP09
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Web Services 1.2.1.GA_CP05
- </para>
- </listitem>
- <listitem>
- <para>
- JGroups 2.4.5
- </para>
- </listitem>
- <listitem>
- <para>
- JSF 1.2_10
- </para>
- </listitem>
- <listitem>
- <para>
- Seam 1.2.1.AP
- </para>
- </listitem>
- <listitem>
- <para>
- Xalan 2.7.0.patch02
- </para>
- </listitem>
- </itemizedlist> -->
- <note>
- <para>
- The Enterprise Application Platform Server has been redefined for the enterprise market to a level where direct association to a community release can no longer be drawn.
- </para>
- </note>
- </section>
- <section id="Installation_Notes">
- <title>Installation and Migration Notes</title>
- <para>
- This section contains information related to installing or upgrading to JBoss Enterprise Application Platform version &VERSION;, including hardware and platform requirements and prerequisites.
- </para>
- <section id="install">
- <title>Installation Notes</title>
- <para>
- You must have adequate disk space to install JDK and JBoss Enterprise Application Platform while also allowing enough space for your applications. You must have a working installation of JDK 1.5. For the latest information on supported Operating System / JVM combinations, supported Database platforms and current information on the revision level of included components, please refer to <ulink url="http://www.jboss.com/products/platforms/application/testedconfigurations">http://www.jboss.com/products/platforms/application/testedconfigurations</ulink>. Refer to the installation guide available online from <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> for detailed instructions to install and verify JBoss Enterprise Application Platform.
- </para>
- </section>
- <section id="upgrade">
- <title>Upgrading from JBoss Enterprise Application Platform 4.2.0.CP05</title>
- <formalpara>
- <title>Using CSP/JON</title>
- <para>Refer to <ulink url="https://network.jboss.com/confluence/display/DOC/Installing+a+Patch">https://network.jboss.com/confluence/display/DOC/Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch.</para>
- </formalpara>
- <!--<formalpara>
- <title>Using RHN</title>
- <para></para>
- </formalpara>-->
- <!--<para>JBoss MQ is now replaced with JBoss Messaging as the JMS implementation shipped within JBoss Enterprise Application Platform 4.3. Since JBoss Messaging is JMS 1.1 and JMS 1.0.2b compatible, the JMS code written against JBossMQ will run with JBoss Messaging without any changes.</para>
- <para>JBoss Messaging only runs with Java 5 or later. It does not have wire format compatibility with JBoss MQ. Even though JBoss Messaging deployment descriptors are very similar to JBoss MQ deployment descriptors, they are <emphasis>not</emphasis> identical. Also, the database data model is completely different, so don't attempt to use JBoss Messaging with a JBoss MQ data schema and vice-versa.</para>
- <para>Refer to the JBoss Messaging User Guide for more information.</para> -->
- </section>
- </section>
- <section id="Important_Notes">
- <title>Important Notes</title>
- <section id="Seam_Applications">
- <title>
- Running the example Seam Applications
- </title>
- <para>
- It is recommended to run the example Seam applications that are included with the documentation using the production configuration. Using another configuration may result in memory issues. Note that the default configuration for the server to start with, if no other configuration is specified, is the production configuration.
- </para>
- <warning>
- <para>
- To avoid memory issues, adjust the memory settings before deploying the applications. You can do this by updating <literal>JAVA_OPTS</literal> settings in the file <filename>JBOSS_DIST/jboss-as/server/production/run.conf</filename> with these recommended values:
-<programlisting>
--Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m
-</programlisting>
- </para>
- </warning>
- <para>
- Refer to the "Seam Reference Guide" included in the documentation set (<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>) for important information regarding the deployment of Seam examples and detailed information on developing applications using Seam.
- <note>
- <para>Seam version used in this release is 1.2.1.GA.</para>
- </note>
- </para>
- </section>
- <section id="Default_Security_Settings">
- <title>
- Default Security Settings
- </title>
- <para>
- If you are using the rpm, or the zip distribution, please note that by default, authentication is enabled and no user accounts are set up. This is done to prevent unauthorized access to various services of JBoss AS. Please refer to the Installation Guide, or see <ulink url="http://kbase.redhat.com/faq/FAQ_107_9963.shtm">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</ulink> for information on how to make the services accessible again.
- </para>
- </section>
- <section id="Hypersonic_Database">
- <title>
- Embedded Hypersonic Database
- </title>
- <para>
- Hypersonic SQL provides default "out of the box" database functionality for evaluation and development use only. It is NOT recommended or supported as a production-use database. Technical support is not available for this component, and while we are happy to accept bugs filed against this component, we do not make any commitment to fix them within a specific timeframe.
- </para>
- </section>
- <section id="source">
- <title> Source Files </title>
- <formalpara>
- <title>SRPMs</title>
- <para>
- <itemizedlist>
- <listitem>
- <para><ulink url="ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS">ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS</ulink>
- </para>
- </listitem>
- <listitem>
- <para><ulink url="ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS">ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS</ulink>
- </para>
- </listitem>
- <listitem>
- <para><ulink url="ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS">ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS</ulink>
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>Source ZIP</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="ftp://ftp.redhat.com/pub/redhat/jbeap/4.2.0/en/source/jboss-eap-src-4.2.0-CP06.zip"> ftp://ftp.redhat.com/pub/redhat/jbeap/4.2.0/en/source/jboss-eap-src-4.2.0-CP06.zip</ulink>
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- </section>
- </section>
- <section id="Product-Support-and-License-Links">
- <title>
- Product Support and License Website Links
- </title>
- <formalpara>
- <title>Support Processes</title>
- <para>
- <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- Production Support Scope of Coverage
- </title>
- <para>
- <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink>
- </para>
- </formalpara>
-
-
- <formalpara>
- <title>
- Production Support Service Level Agreement
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- Developer Support Scope of Coverage
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- Developer Support Service Level Agreement
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- Product Update and Support Policy by Product
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- JBoss End User License Agreement
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink>
- </para>
- </formalpara>
- </section>
-
- <section id="Documentation">
- <title>
- Documentation
- </title>
- <para>
- Refer to the index.html file in the documentation directory for a list of included documentation.
- </para>
- <para>
- In the zip distribution, documentation for the Platform and its individual components is distributed in a separate zip file, <filename>jboss-eap-docs-<version>.zip</filename>.
- </para>
-
- <para>
- On a Linux system, the documentation is found in two rpms that will need to be installed manually. These rpms are <filename>jboss-seam-docs-<version>.noarch.rpm</filename>, and <filename>rh-eap-docs-<version>.noarch.rpm</filename>. For help with installing rpm packages on Red Hat Enterprise Linux, please refer to the Red Hat Knowledge base article located at <ulink url="http://kbase.redhat.com/faq/FAQ_35_198.shtm">http://kbase.redhat.com/faq/FAQ_35_198.shtm</ulink>
- </para>
- <para>
-
- <itemizedlist>
- <listitem>
- <para>
- <filename>Installation Guide</filename> explains how to install and verify the installation of JBoss Enterprise Application Platform using different installation modes.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>Getting Started</filename> details the directory structure of the platform and a quick tour of the Application Server and different configuration sets and services. Using a simple web application it illustrates the use of JSF-EJB3 components and how to use Seam to integrate the JSF and EJB3 components.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>Server Configuration Guide</filename> explains all administrative and configuration functions in detail.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- <para>
- Updated versions of the documentation with errata and additional information, example application code, as well as the most recent version of the release notes may be accessed via the web from <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>.
- </para>
- </section>
- <section id="JSR-181">
- <title>
- JSR-181 support
- </title>
-
- <para>
- JSR-181 related functionality is not supported in this version of the JBoss Enterprise Application Platform. This functionality is supported in version 4.3.
- </para>
- </section>
-
- <section id="Issues-fixed-in-this-release">
- <title>
- Issues fixed in this release
- </title>
-
- <para>
- Following is a list of issues fixed in this release:
- </para>
- <formalpara>
- <title>JBoss Cache</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1993">JBPAPP-1993</ulink>: The JBoss Cache component of the Enterprise Application Platform has been upgraded to version 1.4.1_SP13. A list of the included fixes is as follows:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1995">JBPAPP-1995</ulink>: The <methodname>RegionManager.createRegion</methodname> method would allow duplicate region names and when this occurs all future cache operations would happen only on the second instance of the region, while the <methodname>EvictionTimerTask</methodname> will only watch the first instance, causing the eviction queue of the second instance to fill. To correct this bug, the <methodname>RegionManager.checkConflict</methodname> method now counts a duplicate as a conflict and causes the <methodname>RegionManager.createRegion</methodname> method to generate an exception.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1994">JBPAPP-1994</ulink>: The <methodname>findNode</methodname> method of TreeCache generated a <exceptionname>NullPointerException</exceptionname> when the <methodname>findInternal</methodname> method returned a null value. The <methodname>findNode</methodname> method can now handle a null value returned from the <methodname>findInternal</methodname> method by checking within the <filename>TreeCache.java</filename> file if the <varname>toReturn</varname> value is null as well as the <varname>version</varname>
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Remoting</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1996">JBPAPP-1996</ulink>: The JBoss Remoting component of the Enterprise Application Platform has been upgraded to version 2.2.3. A list of the included fixes is as follows:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1129">JBREM-1129</ulink>: It was possible for <emphasis>PING</emphasis> messages to arrive out of order because socket and bisocket transports use a pool of connections. To fix this bug when a <classname>org.jboss.remoting.Lease</classname> is created a timestamp is associated with it and carried by an initial <emphasis>PING</emphasis> message. The contents of an updated <emphasis>PING</emphasis> message will now be discarded if its timestamp is older than the previously processed timestamp. In the occurrence that the initiating <emphasis>PING</emphasis> message does not have a time stamp, the lease will assume that the client is using an older version of JBoss Remoting and it will accept all updated <emphasis>PING</emphasis> messages.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1128">JBREM-1128</ulink>: Connection identity for the <classname>LeasePinger</classname> and <classname>Lease</classname> pair has been added by setting the parameter <property>org.jboss.remoting.Remoting.USE_CLIENT_CONNECTION_IDENTITY</property> to <emphasis>true</emphasis>. JBoss Remoting then identifies a connection with a <classname>LeasePinger</classname> and <classname>Lease</classname> pair and a client participates in a connection when it is connected by way of the new method <methodname>connect(ConnectionListener listener, Map metadata)</methodname>. This method serves to connect the client to the server by way of a new or existing client invoker, and it also registers the <classname>ConnectionListener</classname> with the client's new or exiting <classname>ConnectionValidator</classname>, while also registering the <classname>ConnectionValidator</classname> with the client invoker's <classname>LeasePinge!
r</classname>. Subsequently, if any <classname>ConnectionValidator</classname> registered with that <classname>LeasePinger</classname> detects a connection failure, it will (if the <property>stopLeaseOnFailure</property> parameter is set to <emphasis>true</emphasis>) stop the <classname>LeasePinger</classname>, and the <classname>LeasePinger</classname> will cause each registered <classname>ConnectionValidator</classname> to notify each of its registered <classname>ConnectionListeners</classname> of the connection failure. If a client is reconnected by a call to the <methodname>Client.connect()</methodname> method, it will be associated with a new <classname>LeasePinger</classname> and be treated as a new connection.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1127">JBREM-1127</ulink>: <exceptionname>ClassCastExceptions</exceptionname> would arise from the caching of <classname>Unmarsharller</classname> and <classname>Classloader</classname> in the <classname>MicroRemoteClientInvoker</classname> and performing classloading when accessing a remote bean from separate isolated EARs. In fixing this issue the <filename>MicroRemoteClientInvoker.java</filename> file has been updated to modify the use of <methodname>useCurrentThreadClassLoader</methodname>, the variable <varname>useCurrentThreadClassLoader</varname> has been added to <filename>RemotingClassLoader.java</filename>, and <filename>JavaSerializationManager.java</filename> has been modified to update the <classname>ObjectInputStream</classname> classloader if the <varname>useCurrentThreadClassLoader</varname> variable of <classname>RemotingClassLoader</classname> has a value of true.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1125">JBREM-1125</ulink>: When a <classname>java.util.Timer</classname> class no longer had <classname>TimerTasks</classname> in its queue, it would allow itself to shut down. This behavior caused subsequent calls to the <methodname>Timer.schedule()</methodname> method to generate a <exceptionname>java.lang.IllegalStateException</exceptionname>. The exception has been overcome by modifying the <filename>AbstractDetector.java</filename> file to test for an <exceptionname>IllegalStateException</exceptionname> when scheduling on the <classname>heartbeatTimer</classname> and <classname>Timer</classname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1121">JBREM-1121</ulink>: Functionality has been added to the client <classname>SocketFactory</classname> that allows it to be configurable by the <classname>InvokerLocator</classname> so that all the parameters from the <classname>InvokerLocator</classname> are available instead of only those in the configuration map.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1119">JBREM-1119</ulink>: If the application called the <methodname>org.jboss.remoting.Client.removeListener()</methodname> method, then <classname>ServerInvoker</classname> would remove references to <classname>ServerInvokerCallbackHandler</classname>, and it would call the <methodname>ServerInvocationHandler.removeListener()</methodname> method, granting the application a chance to remove the reference it held. An issue arose if the connection from the client was to break as that would cause none of the above to be executed, leading to a memory leak in the program. To fix the problem, <classname>ConnectionNotifier</classname> now uses copies of lists in order to avoid a <exceptionname>ConcurrentModificationException</exceptionname>, a <methodname>shutdown()</methodname> method has been added to the <classname>ServerInvokerCallbackHandler</classname>, and within the <classname>ServerInvoker</classname> the <metho!
dname>removeCallbackHandler()</methodname> method has been made public and a <methodname>shutdownCallbackHandler()</methodname> method has been added. These changes mean that the <methodname>shutdown()</methodname> method within the <classname>ServerInvokerCallbackHandler</classname> can be used by the application to remove the necessary references by utilizing the <classname>ServerInvoker</classname> and the applications <classname>ServerInvocationHandler</classname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1112">JBREM-1112</ulink>: Upon a connection failure there was occurrences of a race condition occurring between the <classname>ConnectionValidator</classname> and <classname>ConnectionListener</classname> as <classname>ConnectionValidator</classname> may be able to execute the <methodname>Client.getDisconnectTImeout()</methodname> method before a <classname>ConnectionListener</classname> executes <methodname>Client.setDisconnectTimeout()</methodname>, causing the program to behave unexpectedly. This issue has been fixed by introducing a new parameter called <property>ConnectionValidator.FAILURE_DISCONNECT_TIMEOUT</property> (with the actual value of <varname>failureDisconnectTimeout</varname>). If the <property>org.jboss.remoting.Client.USE_ALL_PARAMS</property> property (with the actual value of <varname>useAllParams</varname>) is set to <emphasis>true</emphasis>, this parameter can be set in the <classname>Invok!
erLocator</classname>, the client's configuration map, or the metadata map passed to the <methodname>Client.addConnectionListener()</methodname> method. If <emphasis>failureDisconnectTimeout</emphasis> is set to an integer value other than -1, then <classname>ConnectionValidator</classname> will use that value when it calls the <methodname>ClientInvoker.terminateLease()</methodname> method, otherwise the value returned by the <methodname>Client.getDisconnectTimeout()</methodname> method is used.
-
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1111">JBREM-1111</ulink>: In <classname>LeasePinger</classname> when all the <classname>TimerTasks</classname> that ran in <classname>java.util.TimerTask</classname> were shut down the <classname>Timer</classname> would also shut down and will not accept any further <classname>TimerTasks</classname>. If a new <classname>Timer</classname> was to be created and a <classname>TimerTask</classname> scheduled for it, an exception would occur. In order to successfully replace the <classname>Timer</classname> if it has shut down, the <methodname>Wrapped timer.schedule()</methodname> is now utilized.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1110">JBREM-1110</ulink>: The method <methodname>org.jboss.remoting.InvokerLocator.getParameters()</methodname> would return null if the URL had no parameters. In this updated release, the method returns an empty <varname>Map</varname> instead to ensure safer execution.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1109">JBREM-1109</ulink>: Within the <methodname>org.jboss.remoting.MicroRemoteClientInvoker.getDataType()</methodname> method when the <varname>dataType</varname> variable was set to the value of the <methodname>getDataType(getLocator())</methodname> method, the variable would temporarily be set to null if the <classname>InvokerLocator</classname> had no datatype parameter. This caused issues because another thread may use the <varname>dataType</varname> variable and return a value of null. Correcting this bug has lead to using a local variable called <varname>localDataType</varname> while a check occurs to see if <classname>InvokerLocator</classname> contains a datatype value. The number of threads has also been reduced to 1000 in order to avoid an <exceptionname>OutOfMemoryError</exceptionname> that may have occurred.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1104">JBREM-1104</ulink>: When the <methodname>org.jboss.remoting.ident.Identity.get()</methodname> method would fail in a call to <methodname>InetAddress.getLocalHost()</methodname>, the runtime exception <exceptionname>java.lang.RuntimeException: Exception creating identity: myhost: myhost</exceptionname> would be generated. The issue was that the exception message did not give any information to the user concerning the underlying problem relating to the host name. This output has been fixed to display to the user the correct information in relation to the main host name issue.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1102">JBREM-1102</ulink>: A feature was requested that would make the configuration map available to the <classname>marshalFactory</classname>. In order to support this the new parameter <property>org.jboss.remoting.Remoting.PASS_CONFIG_MAP_TO_MARSHAL_FACTORY</property> has been added, which requires a setting of <emphasis>true</emphasis> in order to have the configuration map passed to the <classname>marshalFactory</classname>. If the parameter contains a value of <emphasis>false</emphasis> then the original behavior will be executed.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1100">JBREM-1100</ulink>: A feature was requested whereby <classname>ServerInvokerServlet</classname> instances could be linked to <classname>Connectors</classname> by MBean names rather than locator URLs. In order to achieve this the parameter <property>org.jboss.remoting.transport.servlet.ServletServerInvoker.CREATE_UNIQUE_OBJECT_NAME</property> has been added. When set to <emphasis>true</emphasis>, <methodname>ServletServerInvoker.getMBeanObjectName()</methodname> will call <methodname>org.jboss.remoting.ServerInvoker.getMBeanObjectName()</methodname> and return an <emphasis>ObjectName</emphasis> derived by the same algorithm that is used for all transports. To ensure the original default behavior remains, the default value is <emphasis>false</emphasis>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1099">JBREM-1099</ulink>: The multicast detector did not work correctly in environments where many JBoss Remoting invokers were being used. The <methodname>org.jboss.remoting.detection.AbstractDetector.createDetection()</methodname> method would create a detection message based on the number of server invokers registered locally. In the JBoss Enterprise Application Server this would cause an error as the message size would exceed the 4000 limit. A <property>buffersize</property> attribute has been created for <classname>org.jboss.remoting.detection.multicast.MulticastDetector</classname> and <classname>org.jboss.remoting.detection.multicast.MulticastDetectorMBean</classname> that defaults to a value of 10000.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1088">JBREM-1088</ulink>: If the server hostname DNS mapping was not available at the client during a <methodname>org.jboss.remoting.Client.connect()</methodname> call, the <methodname>org.jboss.remoting.transport.socket.MicroSocketClientInvoker.setup() getAddressByName</methodname> produces a <exceptionname>java.net.UnknownHostException</exceptionname> in relation to the hostname. However when the method <methodname>MicroSocketClientInvoker(InvokerLocator locator, Map configuration)</methodname> is called the exception is captured and then displayed using <methodname>throw new RuntimeException(ex.getMessage())</methodname>. By displaying the exception in this way, information important in understanding the cause of the exception, is lost. This has been rectified by changing <methodname>throw new RuntimeException(ex.getMessage());</methodname> to <methodname>throw new RuntimeException(ex.getMessage(), ex);</method!
name>, enabling the actual exception content to be displayed to the user.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1085">JBREM-1085</ulink>: The log level of the <methodname>ServerSocketWrapper.close()</methodname> method log messages has been reduced in order to remove unwanted information. Instead of using the <methodname>log.debug()</methodname> call, the method now uses <methodname>log.trace()</methodname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1084">JBREM-1084</ulink>: When <methodname>org.jboss.remoting.Client.addConnectionListener()</methodname> created a <classname>CallbackPoller</classname>, a reference to itself and a metadata map would be passed. The issue arose from the <classname>CallbackPoller</classname> only accessing parameters in the metadata map. To rectify this issue the <property>Client.USE_ALL_PARAMS</property> parameter is checked within the <classname>InvokerLocator</classname>, the client's configuration map and the metadata map that is passed to the <methodname>Client.addListener()</methodname> method respectively. If the <property>useALLParams</property> property is found and set to a value of <emphasis>true</emphasis>, the <classname>InvokerLocator</classname>, the client's configuration map and the metadata map will be searched respectively for all parameters used by <classname>CallbackPoller</classname>, otherwise only the metad!
ata map will be used, which is the default behavior.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1082">JBREM-1082</ulink>: When <methodname>org.jboss.remoting.Client.addConnectionListener()</methodname> created a <classname>ConnectionValidator</classname>, a reference to itself would be passed and the <classname>ConnectionValidator</classname> would access the client's configuration map. The issue arose from the client's configuration map not including the <classname>InvokerLocator</classname> parameters. To rectify this issue the <classname>ConnectionValidator</classname> now searches for the <property>Client.USE_ALL_PARAMS</property> parameter in the <classname>InvokerLocator</classname>, the client's configuration map and the metadata map that is passed to the <methodname>Client.addConnectionListener()</methodname> method respectively. If the <property>useALLParams</property> property is found and set to a value of <emphasis>true</emphasis>, the <classname>ConnectionValidator</classname> will search for pa!
rameter values in the <classname>InvokerLocator</classname>, the client's configuration map and the metadata map respectively.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBREM-1081">JBREM-1081</ulink>: When the method <methodname>ServerInvokerCallbackHandler.destroy()</methodname> shut down <classname>When org.jboss.remoting.callback.ServerInvokerCallback</classname>, the variables <varname>callBackClient</varname> and <varname>callbackStore</varname> were set to null. If the <methodname>ServerInvokerCallbackHandler.handleCallback()</methodname> is then called a <exceptionname>NullPointerException</exceptionname> arises because that variables <varname>callBackClient</varname> and <varname>callbackStore</varname> are set to null. This bug has been corrected in this latest release by the <methodname>ServerInvokerCallbackHandler.destroy()</methodname> method no longer assigning a value of null to the variables <varname>callBackClient</varname> and <varname>callbackStore</varname>.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Web</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2067">JBPAPP-2067</ulink>: The release of Tomcat 6.0.20 saw a set of security vulnerabilities fixed that have now been backported to JBoss Web. These vulnerabilities are:
- </para>
- <itemizedlist>
- <!-- <listitem>
- <para>
- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0033">CVE-2009-0033</ulink>: For Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when the <filename>Java AJP</filename> connector and <filename>mod_jk</filename> load balancing were used it would allow for remote attackers to cause a denial of service (application outage) attack via a crafted request with invalid headers. This would occur in relation to the temporary blocking of connectors that had encountered errors, as demonstrated by an error involving a malformed <filename>HTTP Host</filename> header. This update has been rated as having important security impact by the Red Hat Security Response Team.
- </para>
- </listitem> -->
- <listitem>
- <para>
- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5515">CVE-2008-5515</ulink>: Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, 6.0.0 through 6.0.18, and possibly earlier versions normalized the target pathname before filtering the query string when using the <methodname>RequestDispatcher</methodname> method, which allowed remote attackers to bypass intended access restrictions and conduct directory traversal attacks via <code>..</code> (dot dot) sequences and the <filename>WEB-INF</filename> directory in a <classname>Request</classname>. This update has been rated as having important security impact by the Red
- Hat Security Response Team.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0783">CVE-2009-0783</ulink>: Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18 would permit web applications to replace an XML parser used for other web applications. This would allow local users to read or modify the <filename>web.xml</filename>, <filename>context.xml</filename>, or <filename>tld</filename> files of arbitrary web applications via a crafted application that is loaded earlier than the target application. This update has been rated as having low security impact by the Red Hat Security Response Team.
- </para>
- </listitem>
- <!-- <listitem>
- <para>
- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0781">CVE-2009-0781</ulink>: A Cross-site scripting (XSS) vulnerability existed within the <filename>jsp/cal/cal2.jsp</filename> calendar examples web application for Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18. This vulnerability would allow remote attackers to inject arbitrary web script or HTML via the time parameter, related to <emphasis>invalid HTML</emphasis>. This update has been rated as having low security impact by the Red Hat Security Response Team.
- </para>
- </listitem> -->
- <listitem>
- <para>
- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0580">CVE-2009-0580</ulink>: For Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when <property>FORM</property> authentication was used, this would allow remote attackers to enumerate valid usernames via requests to <filename>/j_security_check</filename>. This would be achieved with malformed URL encoding of passwords, related to improper error checking in the <classname>MemoryRealm</classname>, <classname>DataSourceRealm</classname>, and <classname>JDBCRealm</classname> authentication realms, as demonstrated by a <code>%</code> (percent) value for the <property>j_password</property> parameter. This update has been rated as having low security impact by the Red Hat Security Response Team.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2050">JBPAPP-2050</ulink>: When attempting to view a <emphasis>mbean</emphasis> graph through the <emphasis>web-console</emphasis> an exception was being generated by the applet because the <filename>jcommon.jar</filename> library was not included within the ZIP version of the previous release. This library file is now included with this release and <emphasis>mbean</emphasis> graphs are now viewable through the <emphasis>web-console</emphasis>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1874">JBPAPP-1874</ulink>: The JBoss Web component of the Enterprise Application Platform has been upgraded to version 2.0.0.CP10. A list of the included fixes is as follows:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1992">JBPAPP-1992</ulink>: Apache Tomcat 5 and 6 did not properly handle double quote (<emphasis>"</emphasis>) characters and the encoded backslash (%5C) sequences in cookie values. These bugs may have allowed for sensitive information such as session IDs to be leaked to remote attackers and permit session hijack attacks. This has been rectified by the modification of <filename>ApplicationContext.java</filename> to generate a <exceptionname>MalformedURLException</exceptionname> if a path starts with an encoded backslash and the modification of <filename>ServerCookie.java</filename> to escape double quote characters. (CVE-2007-5333)
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1950">JBPAPP-1950</ulink>: After the <methodname>HttpServletResponse.reset</methodname> method was executed, any subsequent calls to <methodname>response.setContentType</methodname> or <methodname>response.setCharacterEncoding</methodname> had no effect on the content type. This latest release incorporates a fix that allows the <methodname>response.setContentType</methodname> and <methodname>response.setCharacterEncoding</methodname> methods to function correctly after a <methodname>HttpServletResponse.reset</methodname> call and modify the content type. To achieve this outcome the following method executions have been added to the <methodname>reset()</methodname> method of the <classname>Response</classname> class:
- </para>
-<programlisting>
-usingOutputStream = false;
-usingWriter = false;
-isCharacterEncodingSet = false;
-</programlisting>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1873">JBPAPP-1873</ulink>: When the <parameter>LIMIT_BUFFER</parameter> parameter was set to <code>true</code> an <exceptionname>ArrayIndexOutOfBoundsException</exceptionname> would occur. The <filename>BodyContentImpl.java</filename> file has been updated to correct this bug by removing the <varname>bufferSizeSave</varname> variable and removing the case where the <varname>writer</varname> variable isn't null. To replace these a case has been written to execute the <methodname>clearBody</methodname> method when the <varname>writer</varname> variable is equal to null. By implementing these changes the <classname>JspWriter</classname> buffer size and remaining bytes are calculated correctly, removing the <exceptionname>ArrayIndexOutOfBoundsException</exceptionname>.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Web Services</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1971">JBPAPP-1971</ulink>: The JBoss Web Services component of the Enterprise Application Platform has been upgraded to version 1.2.1.GA_CP05. A list of the included fixes is as follows:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1972">JBPAPP-1972</ulink>: MIME boundaries in the <classname>MultipartRelatedDecoder</classname> were handled incorrectly. This bug has been fixed by modifying the <classname>MultipartRelatedDecoder</classname> class to use a new instance of the <classname>PushbackInputStream</classname> in the creation of the <classname>BoundaryDelimitedInputStream</classname>.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <!-- <formalpara>
- <title>JBoss Seam</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
-
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara> -->
- <formalpara>
- <title>JGroups</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2002">JBPAPP-2002</ulink>: The JGroups component of the Enterprise Application Platform has been upgraded to version 2.4.6. A list of the included fixes is as follows:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JGRP-975">JGRP-975</ulink>: The JGroups testsuite did not permit a user to specify host and port properties for the <classname>GossipRouter</classname> implementation. This meant that the IP address was fixed at 127.0.0.1 and the port was fixed at 12001. This update allows for the host and port properties to be configurable so that the system can be tested against other values other than only the defaults.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JGRP-961">JGRP-961</ulink>: Running the JGroups testsuite against IPv6 addresses using <property>link-local</property> IPv6 addresses with no zone ID would cause some tests to fail that would normally pass when run against IPv4 addresses. The problem arose if the zone ID was omitted and the OS assigned a default interface to send the message, which may not have been the one the user was after. To correct this issue so that IPv6 addresses worked correctly with JGroups, scoped <property>link-local</property> addresses had to be used with the <classname>ServerSocketReceiver</classname> and <classname>ServerSocketSender</classname> classes, enabling use of the correct zone ID in each IPv6 address case.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JGRP-949">JGRP-949</ulink>: Format version information was not displayed to the user in the most meaningful way. In order to make sure the the user receives the most useful information the way in which the format version information is provided has changed from:
- </para>
-<programlisting>
-log.warn(new StringBuffer("packet from ").append(client_addr).append(':').append(client_port).append(" has different version (").append(version).append(") from ours (").append(Version.version).append("). This may cause problems"));
-</programlisting>
- <para>
- To:
- </para>
-<programlisting>
-log.warn(new StringBuffer("packet from ").append(client_addr).append(':').append(client_port).append(" has different version (").append(version).append(") from ours (").append(Version.print(Version.version)).append("). This may cause problems"));
-</programlisting>
- <para>
- Of note is the change of <code>Version.version</code> to <code>Version.pring(Version.version)</code>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JGRP-923">JGRP-923</ulink>: GMS address printing did not contain the cluster name in the details it provided. For this Cumulative Patch release GMS address printing has been updated to include the cluster name in order to provide more detail to a user.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JGRP-893">JGRP-893</ulink>: Previously JGroups could not parse IPv6 addresses in the stack configuration correctly as it used a double colon (::) as a delimiter. These characters are now parsed correctly in JGroups so that IPv6 addresses can be used in a stack configuration correctly.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Hibernate</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2118">JBPAPP-2118</ulink>: The Hibernate EntityManager component of the Enterprise Application Platform has been upgraded to version 3.3.2. A list of the included fixes is as follows:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-341">EJB-341</ulink>: If a user attempted to create a named query that did not exist, a <exceptionname>PersistenceException</exceptionname> would be generated where an <exceptionname>IllegalArgumentException</exceptionname> should have been raised, and the current transaction would be rolled back. The <classname>AbstractEntityManagerImpl</classname> class has been updated to catch the <exceptionname>MappingException</exceptionname> and return an <exceptionname>IllegalArgumentException</exceptionname> to the user, as well as attempt to return a new named query using <classname>QueryImpl</classname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-340">EJB-340</ulink>: The <methodname>onLoad</methodname> method was not invoked on an <classname>EJB3Interceptor</classname>, though it was in the basic Hibernate environment. This issue has been fixed by editing the <classname>EventListenerConfigurator</classname> class to include the default Hibernate Core <classname>PreLoadEventListener</classname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-333">EJB-333</ulink>: A space was present in the path during deployment within the JBoss Enterprise Application Platform and this space would cause an error. In order to fix this, the <classname>ExplodedJarVisitor</classname>, <classname>FileZippedJarVisitor</classname> and <classname>JarVisitorFactory</classname> classes have been updated to cater for a space in a java URL file name.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-330">EJB-330</ulink>: If the <classname>Ejb3Configuration</classname> had classes that contained <property>@PostLoad</property> callbacks and had been added with the <methodname>addAnnotatedClass</methodname> method, these would no longer work if the <methodname>configure</methodname> method was executed before the addition of <classname>@Entity-annotated</classname> classes, through the use of the <methodname>addAnnotatedClass</methodname> method. This bug has been fixed by delaying the call to the <methodname>configure</methodname> method in order to allow for the correct addition of all annotated classes.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-326">EJB-326</ulink>: The persistence unit root that exists in a <filename>.war</filename> file was not being correctly handled. This issues has been fixed by changing the way in which the EJB3 submits the persistence root URL to Hibernate.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-325">EJB-325</ulink>: The <classname>Ejb3Configuration</classname> class has been updated to ensure that <exceptionname>PersistenceExceptions</exceptionname> state the <classname>persistenceUnit</classname> that is generating the exception.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-316">EJB-316</ulink>: The <property>PERSISTENCE_PROVIDER</property> string should be coded as a <property>final</property> string type. The <classname>Persistence</classname> class has been updated for this release to include the <property>PERSISTENCE_PROVIDER</property> string as a <property>final</property> string type.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-305">EJB-305</ulink>: As a new feature, a configuration option has been added that grants the ability to define a session scoped interceptor through the use of the <property>hibernate.ejb.interceptor.session_scoped</property> property.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-299">EJB-299</ulink>: If a <property>package-info.class</property> attribute existed within the default package the <methodname>JarVisitor.addElement</methodname> method would fail and generate a <exceptionname>StringIndexOutOfBoundsException</exceptionname>. Updating the <classname>AbstractJarVisitor</classname> class so that if the name length of the entry is set it the length of the <property>package-info.class</property> attribute, the name is left blank, otherwise the name property is the length of the entries specified name.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-284">EJB-284</ulink>: A bug existed within the <classname>ArchiveBrowser</classname> where it would not abstract a file path for <filename>orm.xml</filename> correctly when Hibernate was run on the Windows operating system. In this new version of Hibernate EntityManager, the ArchiveBrowser has been replaced with the <classname>JarVisitor</classname>. This process has caused this issue to be fixed.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-282">EJB-282</ulink>: The <filename>ORM.xml</filename> file was being ignored when the <property>excludeUnlistedClass</property> property was set to <emphasis>true</emphasis> in the container mode. This bug has been rectified by modifying the <classname>Ejb3Configuration</classname> class to ensure that the <filename>ORM.xml</filename> file is searched even when the <property>excludeUnlistedClass</property> property is set to <emphasis>true</emphasis>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-277">EJB-277</ulink>: String values could not be used as query hint values within Hibernate. This functionality has now been added to Hibernate EntityManager by modifying the <classname>ConfigurationHelper</classname> class to accept string values and the <classname>QueryImpl</classname> class to utilize these changes.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-275">EJB-275</ulink>: Since IBM WebSphere does now return an encoded URL from the <methodname>cl.getResources</methodname> method, the <classname>JarVisitor</classname> would fail due to white space errors. The <classname>JarVisitor</classname> class has now been updated to ensure that URLs returned by IBM WebSphere is striped of any white space that may cause the program to produce an error.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-271">EJB-271</ulink>: The <classname>EJB3OverridenAnnotationReader</classname> class has been improved by raising a warning when deployment descriptors refer to an unknown property. This has been achieved by checking for orphan properties.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-269">EJB-269</ulink>: Hibernate EntityManager would fail to deploy a persistence archive in the <emphasis>Weblogic Server</emphasis>. This issue has been rectified by including a <filename>.jar file</filename> for archive browser handling for the <emphasis>Weblogic Server</emphasis>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-266">EJB-266</ulink>: Hibernate would initialize lazy objects that were being traversed by the <methodname>persist</methodname> operation. This release sees the Hibernate EntityManager avoid collection loading during a cascaded <methodname>persist</methodname>, allowing for increased performance on heavily cascaded object graphs.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-263">EJB-263</ulink>: Within the <classname>QueryImpl</classname> class, elements were not being made unique before <methodname>getSingleResult</methodname> method exceptions were being raised. This allowed for a <exceptionname>NonUniqueResultException</exceptionname> to be generated incorrectly. For this release, elements within the <classname>QueryImpl</classname> class are now made unique before any <methodname>getSingleResult</methodname> method exceptions are raised.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-262">EJB-262</ulink>: An improvement has been made to the <classname>Ejb3Configuration</classname> class that provides the XML file name when a parsing error occurs. In completing this task the new class <classname>NamedInputStream</classname> has been created.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-259">EJB-259</ulink>: <filename>ORM.xml</filename> files that appear in any referenced <filename>.jar</filename> files were not evaluated by Hibernate EntityManager. In order to be in line with the EJB3 specifications, the <classname>Ejb3Configuration</classname> class has been updated to make sure all <filename>ORM.xml</filename> files are evaluated.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-257">EJB-257</ulink>: The <classname>EJB3Configuration</classname> class should be able to work successfully without needing to use any <methodname>configure</methodname> methods. This update allows for the <classname>EJB3Configuration</classname> class to work correctly without the need for any <methodname>configure</methodname> methods by copying the programmatically defined properties and using them with the new <classname>AnnotationConfiguration</classname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-242">EJB-242</ulink>: The <classname>InputStreamZippedJarVisitor</classname> class has been updated to produce an exception instead of an IO exception so that Eclipse does not produce a <exceptionname>NullPointerException</exceptionname> but instead just logs a warning message. This allows for Hibernate and Eclipse to function easier together.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-46">EJB-46</ulink>: The <methodname>PrePersist</methodname> callback method was not being utilized if the <property>primary key</property> of the entity was set to null. The way in which the Hibernate EntityManager would operate when a <property>primary key</property> of the entity was set to null has been changed so that the <methodname>PrePersist</methodname> callback method can be correctly utilized.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2110">JBPAPP-2110</ulink>: The Hibernate Validator component of the Enterprise Application Platform has been upgraded to version 3.0.0. A list of the included fixes is as follows:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-10">HV-10</ulink>: The Luhn algorithm has been implemented in Hibernate Validator and the <classname>@CreditCardNumber</classname> interface created. The Luhn algorithm implementation requires a valid credit card number and checks for user error. This class does not check for credit card validity.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-9">HV-9</ulink>: The <classname>@Digits</classname> interface has been added to Hibernate Validator. This interface allows for digits to be expressed as integers and fractions. This new interface resides within the <filename>Digits.java</filename> file.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-8">HV-8</ulink>: Hibernate Validator now supports pure <emphasis>JavaPersistence</emphasis> players. Though when used through <classname>EntityListeners</classname>, parameters such as <property>interpolator</property> are not supported due to the listener lifecycle not being defined and no avenue exists to pass the PU properties.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-7">HV-7</ulink>: Two level <property>@Valid</property> annotation did not work as a user would have expected. A <exceptionname>NullPointerException</exceptionname> would be generated when initialization occurred in the <classname>ClassValidator</classname>. This bug has since been fixed by initializing the <classname>reflectionManager</classname> within the <classname>ClassValidator</classname> constructor.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-6">HV-6</ulink>: The <property>@EAN</property> annotation type has been added to Hibernate Validator. This element checks if the string is a correctly formated EAN-13 or UPC-A code; it does not check for number validity.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-5">HV-5</ulink>: The ability to have multiple validators of the same type for each element has been added to Hibernate Validator. Though Hibernate Validator could already achieve this functionality to an extent, this improvement allows for greater ease of use for the user.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-3">HV-3</ulink>: The <property>@Email</property> validating string would fail if the string contained a null value. The <classname>EmailValidator</classname> class has been modified to include checking for a null value and to handle this case correctly so that the validation does not fail.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-2">HV-2</ulink>: String support for both <property>@Past</property> and <property>@Future</property> validating Strings has been deprecated as there was no absolute way to be sure of the date and time format or the locale that may be used.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-1">HV-1</ulink>: A new feature has been added to Hibernate Validator that sets the <classname>ClassValidator</classname> as being independant of Hibernate Annotations. This ensures that if a users wishes, Hibernate Validator does not have to be used with Hibernate Annotations.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2118">JBPAPP-2037</ulink>: The Hibernate Core component of the Enterprise Application Platform has been upgraded to version 3.2.4.SP1_CP08. A list of the included fixes is as follows:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1930">JBPAPP-1930</ulink>: A <exceptionname>NullPointerException</exceptionname> would occur when a native SQL query coupled eager fetching with a many-to-many relationship. Correcting this has meant that the <code>if ( collectionPersister.isOneToMany() ) {</code> line of code in the <filename>SQLQueryReturnProcessor</filename> file has been changed to <code>if ( collectionPersister.isOneToMany() || collectionPersister.isManyToMany()) {</code>, removing the generation of a <exceptionname>NullPointerException</exceptionname>. To note though is that the fix only works with the <filename>hbm.xml</filename> file SQL mapping feature and a named query.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1922">JBPAPP-1922</ulink>: A bottleneck existed within the <filename>EntityModeToTuplizerMapping.java</filename> file when a high number of threads attempted to initialize sets and had to wait for the same monitor. In correcting this issue, the <filename>EntityModeToTuplizerMapping.java</filename> file has been modified to remove the <code>private final Map tuplizers = Collections.synchronizedMap( new SequencedHashMap() ); </code> line of code and replace it with only <code>private final Map tuplizers;</code> and two new public methods to assist in the mapping.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1797">JBPAPP-1797</ulink>: Transient entities could be inserted twice when a merge was performed. To correct this bug the <filename>DefaultMergeEventListener.java</filename> file has been updated to use the new <classname>CopyCache</classname> class. Within the <filename>DefaultMergeEventListener.java</filename> file, logic has been added to retrieve transient entities and retry a merge once if an error is encountered. Following this, if the merge continues unsuccessfully a <exceptionname>TransientObjectException</exceptionname> will be generated. The <classname>CopyCache</classname> class has been created to be the <varname>Map</varname> implementation used by <classname>DefaultMergeEventListener</classname> in order to keep track of entities and the copies that are being merged into the session. This implementation also tracks whether a an entity in the <classname>CopyCache</classname> is included in the merge.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1748">JBPAPP-1748</ulink>: When merging read-only entities that had the <varname>@Immutable</varname> annotation included the following failure would occur:
- </para>
-<screen>
-org.hibernate.AssertionFailure: Merged entity does not have status set to MANAGED; EntityEntry[com.tll.model.impl.AccountHistory#71794688](READ_ONLY) status=READ_ONLY
-</screen>
- <para>
- The <filename>DefaultMergeEventListener.java</filename> file has been updated by editing the following test statement:
- </para>
-<programlisting>
-if ( entry.getStatus() != Status.MANAGED ) {
- throw new AssertionFailure( "Merged entity does not have status set to MANAGED; "+entry+" status="+entry.getStatus() );
-}
-</programlisting>
- <para>
- modified to test against the possibility that the current <varname>Status</varname> could be <property>READ_ONLY</property>:
- </para>
-<programlisting>
-if ( entry.getStatus() != Status.MANAGED && entry.getStatus() != Status.READ_ONLY ) {
- throw new AssertionFailure( "Merged entity does not have status set to MANAGED or READ_ONLY; "+entry+" status="+entry.getStatus() );
-}
-</programlisting>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1564">JBPAPP-1564</ulink>: The SQL <methodname>trim</methodname> function and support for <property>mod</property> and <property>bit_length</property> were not present in the Sybase Dialect. This release sees these available for use within the <filename>SybaseASE15Dialect</filename>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1563">JBPAPP-1563</ulink>: The SQL functions <function>mod</function>, <function>bit_length</function> and <function>trim</function> caused failures in the <classname>ASTParserLoadingTest</classname> because they were not implemented in the Sybase Dialect. The Sybase Dialect has now been updated to import the <classname>org.hibernate.dialect.function.AnsiTrimEmulationFunction</classname> function and implement the <function>mod</function>, <function>bit_length</function> and <function>trim</function> functions.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2078">JBPAPP-2078</ulink>: The Hibernate Annotations component of the Enterprise Application Platform has been upgraded to version 3.3.1. A list of the included fixes is as follows:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-701">ANN-701</ulink>: The error message given when using the <property>@CollectionId</property> property incorrectly did not give useful information to the user. Correcting this, the <filename>CollectionBinder.java</filename> file has been updated to generate an exception with all relevant information given the improper use of the <property>@CollectionId</property> property for individual cases.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-700">ANN-700</ulink>: The <classname>NamedQuery</classname> class of Hibernate had the <property>flushMode</property> attribute set to <property>AUTO</property> by default. This caused inconsistencies throughout the program and the <property>flushMode</property> attribute to never contain the correct value. To correct this the default value of the <property>flushMode</property> attribute is now set to a newly introduced <property>PERSISTENCE_CONTEXT</property>. This new value makes sure that the <property>flushMode</property> is consistent with the persistence context at the time the query is executed, alleviating inconsistency issues.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-699">ANN-699</ulink>: The <methodname>AnnotationBinder.mustBeSkipped</methodname> contains a hardcoded reference to the <classname>org.hibernate.tool.instrument.javassist.FieldHandler</classname> class. The issue that arises from this is that the class is actually contained within a different package and by having the incorrect reference it caused all <classname>javassist-instrumented</classname> classes to not function correctly. In order to rectify this issue the reference to the <classname>FieldHandler</classname> class has been changed within the <methodname>AnnotationBinder.mustBeSkipped</methodname> method to be <classname>org.hibernate.bytecode.javassist.FieldHandler</classname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-698">ANN-698</ulink>: Having an unbound property when default field access is used would lead to an unbound <exceptionname>AnnotationException</exceptionname>. The generated exception is now caught by the program and a more meaningful <exceptionname>AnnotationException</exceptionname> is generated and displayed to the user instead. These changes have been made to the <classname>AnnotationBinder</classname> class.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-696">ANN-696</ulink>: When a Hibernate map existed that had both <property>key</property> and <property>value</property> elements, the <property>@Type</property> annotation would affect both. To generate desired results the <filename>MapBinder.java</filename> and <filename>MapKey.java</filename> files have been updated to include and use a <classname>MapKey</classname> <property>@Type</property>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-695">ANN-695</ulink>: New Hibernate Search collection even listeners have been integrated with the addition of the new classes <classname>CollectionSearchConfiguration</classname> and <classname>SearchConfiguration</classname>, and the amendment of the <classname>AnnotationConfiguration</classname> class to use the new <classname>SearchConfiguration</classname> class instead of embedding the search functionality within the <classname>AnnotationConfiguration</classname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-694">ANN-694</ulink>: An incorrect report of a Foreign Key circularity error was occurring when the <property>@*ToOne</property> property name started with the identifier property name. The issue has been fixed by modifying the <filename>ToOneFkSecondPass.java</filename> file to make the <methodname>ToOneFkSecondPass</methodname> method a public method.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-690">ANN-690</ulink>: Previous releases did not allow for method chaining within the <classname>AnnotationConfiguration</classname> class. This functionality has now been added by overriding all relevant configuration methods that reside within the <classname>AnnotationConfiguration</classname> class.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-683">ANN-683</ulink>: When <property>hashCode</property> collisions occurred within <classname>AnnotationConfiguration</classname>, random binding failures would occur. To fix this issue, the <filename>FkSecondPass.java</filename> file has been updated to use a unique counter in order to differentiate between two instances of <classname>FkSecondPass</classname> so that they can be compared as the IBM VM would sometimes return the same <varname>hashCode</varname> for two different objects. The <filename>AnnotationConfiguration.java</filename> file has also been updated to utilize the changes made to <filename>FkSecondPass.java</filename>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-673">ANN-673</ulink>: <classname>AnnotationConfiguration</classname> did not define stable ordering for foreign key columns, allowing them to appear in any order within a generated SQL schema. Also of issue was when the <classname>hbm2ddl</classname> tool was being used to see a generated schema. The ordering of a foreign key column within a table could change if an unrelated modification was made inside the mapping of a different table. This issue was fixed by the solution for <emphasis>ANN-683</emphasis> that is specified within these release notes.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-671">ANN-671</ulink>: When the <classname>Validator</classname> was not present, a message describing this would be logged, however this would occur twice. In this update the <classname>AnnotationConfiguration</classname> class has been modified to only log the occurrence of this once for each time.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-653">ANN-653</ulink>: The ability to use <property>@AssociationOverride</property> when overriding a collection delivered undesired results in the form of an exception. This functionality has now been fixed and works as expected.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-650">ANN-650</ulink>: In previous versions the <classname>@Version</classname> class could be set within an <classname>@Embedded</classname> class without any checking and generate a <exceptionname>java.lang.ArrayIndexOutOfBoundsException</exceptionname> that would not display enough detail about the error for a user to understand the cause. This has since be altered to check for this occurrence and generate an <exceptionname>AnnotationException</exceptionname> with useful information so that a user can correct any issues.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-648">ANN-648</ulink>: The <methodname>o.h.a.Table.comment</methodname> and <methodname>o.h.a.Table.indexes</methodname> methods would fail when used on secondary tables. To correct this issue the <classname>SecondaryTableSecondPass</classname> class has been updated to use the <classname>XAnnotatedElement</classname> class and the <classname>EntityBinder</classname> class now sets the secondary table as the first for when a join needs to occur.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-637">ANN-637</ulink>: The <methodname>Table.appliesTo</methodname> method would incorrectly select the last table when no matching table to the user query exists. This bug has been fixed by allowing the <varname>hibTable</varname> variable within the <classname>EntityBinder</classname> class to contain a value of null when the correct table cannot be found.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-634">ANN-634</ulink>: The <property>@CollectionOfElements</property> property would clash with the <property>@Fetch JOIN</property>, <property>@Filter</property> and <property>@Where</property> properties within the <classname>CollectionBinder</classname> class. The class has now been updated to test for the instance of a <property>SimpleValue</property> in the <property>@CollectionOfElements</property> property, correcting the issue.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-633">ANN-633</ulink>: The <filename>MANIFEST.MF</filename> file in the <filename>hibernate-annotation</filename> JAR file has been improved to contain vendor and versioning information using the default attributes defined in the JAR file specification.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-621">ANN-621</ulink>: A problem was being caused by the embedded primary key for <classname>ManyToOne</classname> associates containing only transient member variables. This was corrected by adding <property>getter</property> and <property>setter</property> accessors for the respective ID fields and setting both <property>insertable</property> and <property>updatable</property> properties to false.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-619">ANN-619</ulink>: When <classname>@OneToOne</classname> was placed within a composite key, the Hibernate application would generate an <exceptionname>ExceptionInInitializerError</exceptionname>. This has been fixed by recoding how a user application that does not use a true <classname>OneToOne</classname> relationships tested.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-617">ANN-617</ulink>: A <exceptionname>NullPointerException</exceptionname> would occur when a property of a composite ID would be used for ordering. This bug has been fixed by modifying the <classname>CollectionBinder</classname> class to check if the <classname>PersistentClass</classname> is null before checking if it is not an <property>associatedClass</property>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-613">ANN-613</ulink>: A <exceptionname>NullPointerException</exceptionname> would be generated when the <property>mappedBy</property> property was incorrect in a <classname>@OneToOne</classname> mapping. In order to make sure a <exceptionname>NullPointerException</exceptionname> does not occur, when the <property>otherSideProperty</property> parameter contains a null vale within the <classname>OneToOneSecondPass</classname> class, an <exceptionname>AnnotationException</exceptionname> is generated detailing that the <property>mappedBy</property> property is incorrect and where.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-608">ANN-608</ulink>: A bug existed within the <classname>EJB3OverridenAnnotationReader</classname> class where the <classname>annotationsMap</classname> would not be correctly initialized, causing a <exceptionname>NullPointerException</exceptionname> in the <classname>AnnotationConfiguration</classname> class. The issue has been fixed by modifying the <filename>EJB3OverridenAnnotationReader.java</filename> file to remove an internal <classname>Annotation</classname> <code>for</code> loop and replace it with the code <code>annotationsMap = new HashMap<Class, Annotation>( annotations.length + 5 );</code> instead. This change now allows for the <classname>annotationsMap</classname> to be correctly initialized.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-606">ANN-606</ulink>: The <property>@Immutable</property> annotation would not generate a configuration error or warning when used on a subclass. When <property>@Immutable</property> is not used on a root entity, a warning is now generated to inform the user of this incorrect behavior.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-602">ANN-602</ulink>: Any <classname>SecondaryTable</classname> with an <classname>EmbeddedId</classname> or <classname>IdClass</classname> containing a <property>ManyToOne</property> attribute would error. In order to fix this a new <classname>SecondaryTableSecondPass</classname> class has been created and the <classname>AnnotationConfiguration</classname> and <classname>AnnotationBinder</classname> classes have been updated to make use of the new class since associations can be built on joins. Implementing these changes causes the <classname>SecondaryTable</classname> class to behave as a user would expect.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-590">ANN-590</ulink>: An alphabetical ordering issue caused errors when the <property>@ManyToOne</property> and <property>referencedColumnName</property> properties were being used in the <classname>PrimaryKey</classname>. To correct this the <filename>ToOneFkSecondPass.java</filename> file was updated to try using an embedded property for a <classname>persistentClass</classname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-567">ANN-567</ulink>: No avenue existed to set the <property>collectionPersister</property> property on a <classname>Collection</classname> via Annotations. The functionality to be able to achieve this has now been added for this release.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-560">ANN-560</ulink>: Quoting issues existed with the default values in the <classname>NamingStrategy</classname> interface. In order to rectify this, the <filename>Ejb3JoinColumn.java</filename> and <filename>TableBinder.java</filename> files have been updated to quote the result and unquote the source before any other action is taken if the source is quoted.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-559">ANN-559</ulink>: An undefined filter definition would lead to a <exceptionname>NullPointerException</exceptionname> instead of generating a meaningful exception. This has been changed for the release so that this circumstance does not arise, instead a default filter definition is applied if one is undefined.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-556">ANN-556</ulink>: The <property>@OneToOne</property> relationship relied on strict alphabetical ordering that caused the <property>mappedBy</property> property to fail. The <classname>AnnotationBinder</classname> and <classname>AnnotationConfiguration</classname> classes have been updated to make sure that the <classname>OneToManySecondPass</classname> is processed in order.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-555">ANN-555</ulink>: A typo existed within the <classname>Tables</classname> class whereby the interface declaration contained <code>Table[] values();</code> instead of <code>Table[] value();</code>. This small bug has been fixed for this release, allowing the <methodname>Tables.value</methodname> method to function correctly.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-554">ANN-554</ulink>: A <exceptionname>NullPointerException</exceptionname> would be generated when the <property>@Id</property> property was used on a <property>@OneToOne</property> relationship. Correction of this bug has been handled by modifying the <classname>OneToOneSecondPass</classname> class to avoid a <exceptionname>NullPointerException</exceptionname> in this case and instead generate a meaningful <exceptionname>AnnotationException</exceptionname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-553">ANN-553</ulink>: The classpath dependency (<filename>hibernate-validator.jar)</filename> file between Hibernate Annotations and Hibernate Validator has been removed and the <filename>ejb3-persistence.jar</filename> file has become a required dependency.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-552">ANN-552</ulink>: A major new feature for Hibernate Annotations is the transparent event registration and integration for Hibernate Search and Hibernate Validator if they are in the classpath.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-551">ANN-551</ulink>: Columns in a SQL insert query have to be ordered in the same way that Hibernate internally sorts its properties in order for the query to be successful. This was an issue for users as some would use numerous application servers, all of which would order these properties in different ways. The issue has been solved by modifying the <classname>AnnotationBinder</classname> class so that the parameters of a query are ordered internally to the order that Hibernate supports.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-549">ANN-549</ulink>: When an association table is involved in a table join, the key column would be set to null. The correct behavior is to have this key column forced to be not null. This has been achieved by modifying the <classname>MapBinder</classname> class to test if the collection is anything but a <property>OneToMany</property> relationship then the key column should not be null.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-544">ANN-544</ulink>: The <classname>CollectionBinder</classname> class used the <methodname>setCustomSQLDelete</methodname> method when testing if the <methodname>sqlDeleteAll</methodname> method was not null. This would prevent the execution of the <methodname>col.clear</methodname> method on the collection in the case that all the elements are removed. The functionality of <classname>CollectionBinder</classname> has been updated to now use the <methodname>setCustomSQLDeleteAll</methodname> method to ensure correct operation.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-542">ANN-542</ulink>: The <property>@Immutable</property> annotation has been added for entities and collections. This has seen the modification of the <classname>CollectionBinder</classname> and <classname>EntityBinder</classname> classes, as well as the addition of the new <classname>Immutable</classname> class.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-535">ANN-535</ulink>: When the <property>@Generated</property> annotation is used, the ability to insert and update a property should be forced. This improvement has been made to Hibernate Annotations through modification of the <classname>PropertyBinder</classname> class.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-532">ANN-532</ulink>: The exception handling of the <property>@UniqueConstraint</property> has been improved for cases when it refers to an incorrect column name. This has been achieved through the modification of the <classname>AnnotationConfiguration</classname> and <classname>Mappings</classname> classes.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-529">ANN-529</ulink>: Hibernate used the optional keyword <emphasis>as</emphasis> in the from clause within the <classname>MapBinder</classname> class. This behavior caused Hibernate Annotations to not be compatible with Oracle 10g. The optional keyword is now removed from the from clause and Hibernate Annotations is successfully compatible with Oracle 10g.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-525">ANN-525</ulink>: The <property>@ForeignKey</property> annotation that is used to specify readable names to foreign key constraints could not be applied at the class level and so could not be utilized in providing readable names to constraints between the super and sub classes using the <property>InheritanceType.JOINED</property> property. In this release the <property>@ForeignKey</property> annotation is now supported at the class level for all joined subclasses and is an attribute of the <classname>o.h.a.Table</classname> for secondary tables.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-517">ANN-517</ulink>: The <varname>EntityMode.DOM4J</varname> value would only work when a <filename>.hbm.xml</filename> mapping file is create and could not be used when only Hibernate Annotations was being used in business entities. The <classname>EntityBinder</classname>, <classname>PropertyBinder</classname> and <classname>CollectionBinder</classname> classes have been updated so that they call the <methodname>setNodeName</methodname> method. The error was that this was not being done by the <classname>AnnotationBinder</classname>, causing the <classname>Dom4j</classname> tuplizer to not be instantiated when only Hibernate Annotations was being used.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-516">ANN-516</ulink>: The <property>@OrderBy</property> attribute would be added to the incorrect table when used in an inheritance relationship. Condition testing has been added to the <classname>CollectionBinder</classname> class, ensuring that if the tables <classname>PersistentClass</classname> does not contain a value of <varname>associatedClass</varname>, the tables quoted name is retrieved; otherwise the table is assumed to be empty.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-515">ANN-515</ulink>: Fields were not correctly quoted in a <property>@OneToMany</property> relationship when they were specified, leading to a <exceptionname>SQLGrammarException</exceptionname>. The <filename>Ejb3JoinColumn.java</filename> file has been amended to use the method <methodname>column.getQuotedName</methodname> in the <methodname>linkValueUsingAColumnCopy</methodname> method, instead of <methodname>column.getName</methodname>. </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-509">ANN-509</ulink>: Using a foreign key value for the <property>referecedColumnName</property> value would cause a <exceptionname>MappingException</exceptionname> to occur. The reason for this issue has stemmed through the need for correct ordering of steps and to fix this a <classname>RecoverableException</classname> class has been created which is used to catch the exception and allow the program to perform passes to assist in correcting the issue. If however this is unsuccessful then the loop is exited and the original exception is displayed to the user.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-505">ANN-505</ulink>: Support for the <property>@Tuplizer</property> annotation and interface annotations has been added to Hibernate Annotations. A tupilizer manages a particular representation of a piece of data, given the <property>EntityMode</property> of the representation.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-502">ANN-502</ulink>: Integration with Hibernate Validator was not completely possible as it is used in metamodel construction and could not be disabled. In order to allow for this functionality the <property>hibernate.validator.apply_to_ddl</property> has been added and can be set to false to remove Hibernate Validator integration with metamodel construction.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-444">ANN-444</ulink>: In Hibernate Core, the <code><join></code> tag in <filename>.hbm.xml</filename> files contain an attribute called <property>optional</property> that allows for configuration of Hibernate to either use inner joins or outer joins, however this same functionality was not included in Hibernate Annotations. This feature has now been added to Hibernate Annotations through the modification of the <classname>EntityBinder</classname> and <classname>Table</classname> classes.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-442">ANN-442</ulink>: Support for more than one generic generator in the <filename>package-info.java</filename> file has been added by adding the new <classname>GenericGenerators</classname> interface, and updating the <classname>AnnotationBinder</classname> to incorporate the use of the new interface.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-434">ANN-434</ulink>: The exception that was generated when attempting to create an entity with an <classname>EmbeddedId</classname> and automatically generated IDs did not give useful information to a user. This has been corrected by modifying the <classname>AnnotationBinder</classname> class to generate an <exceptionname>AnnotationException</exceptionname> that outputs the class name of the component with information explaining that this class must not have <classname>ID</classname> properties when used as an <classname>EmbeddedID</classname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-252">ANN-252</ulink>: The <classname>AnnotationConfiguration</classname> class would ignore classes that were annotated with an incorrect <property>Entity</property> or contained no annotation. The <classname>AnnotationBinder</classname> class has been updated to log a warning message if any of the mentioned circumstances occurs.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-122">ANN-122</ulink>: The <property>@NaturalId</property> annotation that was added to Hibernate previously, has now been added to Hibernate Annotations. This allows for a property to be specified as part of the natural id of an entity.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-104">ANN-104</ulink>: CRUD SQL customization is now allowed on secondary tables within Hibernate Annotations.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-103">ANN-103</ulink>: The ability to specify a fetching strategy for a secondary table has been added to Hibernate Annotations.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-28">ANN-28</ulink>: The <property>@Any</property> and <property>@ManyToAny</property> mapping values have been added as a new feature to Hibernate Annotations. With these features added, it allows for a more robust and diverse database environment.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-26">ANN-26</ulink>: Support for the ability to exclude a property from the optimistic locking has been added to Hibernate Annotations.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- <!-- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1998">JBPAPP-1998</ulink>: The incorrect exception (<exceptionname>EntityNotFoundException</exceptionname>) was being generated for an optimistic locking failure due to a deleted entity using the <property>hibernate.jdbc.batch_versioned_data=false</property> property and value. To correct this a <emphasis>try and catch</emphasis> test has been added to the <methodname>AbstractEntityManagerImpl.wrapStaleStateException</methodname> method in order to catch the <exceptionname>EntityNotFoundException</exceptionname> exception and display the correct <exceptionname>OptimisticLockException</exceptionname> exception instead.
- </para>
- </listitem> -->
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2032">JBPAPP-2032</ulink>: The Hibernate Annotations upgrade that has occurred between the last JBoss Enterprise Application Platform Cumulative Patch and this one may cause backwards-compatibility issues for some users due to the changes introduced to applications that use <classname>SchemaExport</classname> in production. The following instances are circumstances where an issue may arise:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Users who rely on the <classname>hbm2ddl</classname> component of Hibernate Annotations must now check their manually created indexes as there is a high possibility that the order of these will have to change to avoid a performance penalty. An example of this would be that if the index was B, A and Hibernate Annotations now queries based on A, B then the index will not be used.
- </para>
- </listitem>
- <listitem>
- <para>
- Users who rely on custom Hibernate CRUD operations are required to manually check if their SQL is up-to-date. An example of when this would be required is if a user has a table with the structure NAME(string), FK1(int), FK2(int) and the FK's point to a table which has overlapping or the same ID set. With this Hibernate Annotations upgrade it is now assumed that the structure is NAME(string), FK2(int), FK1(int). This change will not cause CRUD operations to fail at runtime but the semantics of the update will be incorrect.
- </para>
- </listitem>
- </itemizedlist>
- <warning>
- <para>
- If these concerns are not addressed by affected users then noticeable data consistencies and performance issues may arise. The new configuration parameter <property>hibernate.legacy.foreignkey.use_identity_hashcode_to_compare</property> should also not be utilized as it will restore indeterminate behavior.
- </para>
- </warning>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1859">JBPAPP-1859</ulink>: The <classname>ManyToOneJoinTest</classname> distributed with Hibernate would fail because a primary key would be set on a <code>nullable</code> column. The <filename>OneToOneSecondPass.java</filename> file has been modified to use the <methodname>buildJoinFromMappedBySide</methodname> method instead of the <methodname>buildJoin</methodname> method. Enacting this change has meant that the calls to the <methodname>join.createPrimaryKey()</methodname> and <methodname>join.createForeignKey()</methodname> methods within this file have also been removed.
- </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 using table alias' in an update query causes a program failure. In order to correct this the <filename>QueryTest.java</filename> file has been updated with the removal for the allowance of table alias'.
- </para>
- </listitem>
- <!-- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1529">JBPAPP-1529</ulink>: The composite primary key of 765 bytes fails within the unit test for Sybase, as it exceeds the maximum index length of 600 bytes. In order to rectify this issue, a hard coded length of 32 bytes is now in place for the compasite primary key ID within the <filename>UserGroup.hbm.xml</filename> file.
- </para>
- </listitem> -->
- <!-- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1528">JBPAPP-1528</ulink>: When Sybase would convert Java byte into tinyint, failures would arise within tests because of the use of 8 bit values. To correct this the unit tests have been updated to use 7 bit values instead of 8. In order to instigate this correction, the <filename>InterfaceProxyTest.java</filename> and <filename>MixedTest.java</filename> files have been updated.
- </para>
- </listitem> -->
- <!-- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1527">JBPAPP-1527</ulink>: Limitations of the Sybase ResultSet implementation would cause unit test failures because the data would not be read before closing the ResultSet. The <filename>AggressiveReleaseTest.java</filename>, <filename>CMTTest.java</filename> and <filename>StatsTest.java</filename> files have been updated so that the ResultSet is read correctly for Sybase so that no <exceptionname>NullPointerException</exceptionname> is thrown.
- </para>
- </listitem> -->
- <!-- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1523">JBPAPP-1523</ulink>: The test supplied for the <methodname>str()</methodname> method is invalid for SQL Server and Sybase as optional parameters for controlling the number of characters for decimal plus decimal values is 0 and the test uses these values by default for SQL Server and Sybase, returning null values. The test has been updated for these dialects so that the values passed are appropriate and do not return null.
- </para>
- </listitem> -->
- <!-- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1520">JBPAPP-1520</ulink>: The <methodname>FooBarTest.testCollectionsInSelect()</methodname> tests fails for Sybase because implicit support for conversion between <varname>VARCHAR</varname> to <varname>INT</varname>.The files <filename>NativeQueryTest.java</filename> and <filename>FooBar.test</filename> have been updated to correct this issue.
- </para>
- </listitem> -->
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Transaction Service (JBossTS)</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1693">JBPAPP-1693</ulink>: The JBoss Transaction Service component of the Enterprise Application Platform has been upgraded to version 4.2.3.SP5.CP05. A list of the included fixes is as follows:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1684">JBPAPP-1684</ulink>: A memory leak would be caused in the <classname>BaseTransaction</classname> class because entries in the hash table were never removed, even if a thread was no longer in use. This meant that client transactions could have leaked approximately 600 bytes. To correct this bug, the <filename>BaseTransaction.java</filename> file has been updated to replace the hash table with a <varname>ThreadLocal</varname> implementation which takes an integer as input. In order to allow for the timeout values to work correctly, they now only call the required methods of <methodname>_timeouts.set</methodname> and <methodname>_timeouts.get</methodname>. With these improvements made, the memory leak no longer occurs.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>Security Issues</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2067">JBPAPP-2067</ulink>: The release of Tomcat 6.0.20 saw a set of security vulnerabilities fixed that have now been backported to JBoss Web. These vulnerabilities are:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0033">CVE-2009-0033</ulink>: For Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when the <filename>Java AJP</filename> connector and <filename>mod_jk</filename> load balancing were used it would allow for remote attackers to cause a denial of service (application outage) attack via a crafted request with invalid headers. This would occur in relation to the temporary blocking of connectors that had encountered errors, as demonstrated by an error involving a malformed <filename>HTTP Host</filename> header. This update has been rated as having important security impact by the Red Hat Security Response Team.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5515">CVE-2008-5515</ulink>: Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, 6.0.0 through 6.0.18, and possibly earlier versions normalized the target pathname before filtering the query string when using the <methodname>RequestDispatcher</methodname> method, which allowed remote attackers to bypass intended access restrictions and conduct directory traversal attacks via <code>..</code> (dot dot) sequences and the <filename>WEB-INF</filename> directory in a <classname>Request</classname>. This update has been rated as having important security impact by the Red
- Hat Security Response Team.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0783">CVE-2009-0783</ulink>: Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18 would permit web applications to replace an XML parser used for other web applications. This would allow local users to read or modify the <filename>web.xml</filename>, <filename>context.xml</filename>, or <filename>tld</filename> files of arbitrary web applications via a crafted application that is loaded earlier than the target application. This update has been rated as having low security impact by the Red Hat Security Response Team.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0781">CVE-2009-0781</ulink>: A Cross-site scripting (XSS) vulnerability existed within the <filename>jsp/cal/cal2.jsp</filename> calendar examples web application for Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18. This vulnerability would allow remote attackers to inject arbitrary web script or HTML via the time parameter, related to <emphasis>invalid HTML</emphasis>. This update has been rated as having low security impact by the Red Hat Security Response Team.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0580">CVE-2009-0580</ulink>: For Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when <property>FORM</property> authentication was used, this would allow remote attackers to enumerate valid usernames via requests to <filename>/j_security_check</filename>. This would be achieved with malformed URL encoding of passwords, related to improper error checking in the <classname>MemoryRealm</classname>, <classname>DataSourceRealm</classname>, and <classname>JDBCRealm</classname> authentication realms, as demonstrated by a <code>%</code> (percent) value for the <property>j_password</property> parameter. This update has been rated as having low security impact by the Red Hat Security Response Team.
- </para>
- </listitem>
- </itemizedlist>
- <para>
- These bug fixes are part of the JBoss Web 2.0.0.CP10 upgrade.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>Documentation</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1782">JBPAPP-1782</ulink>: Chapter 7.2 named <emphasis>Adjusting memory settings</emphasis> within the <filename>Installation Guide</filename>, stated that a user should modify the <filename>run.conf</filename> file in order to increase the available memory to the program. This however is incorrect when running the JBoss Enterprise Application Platform on a Windows operating system. In this case the <filename>run.bat</filename> file should be modified and the documentation now reflects this difference.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1768">JBPAPP-1768</ulink>: On page 37 of the PDF for the <filename>Hibernate Annotations Reference Guide</filename> book an example would overflow the allowed area because of the way in which the software to build the PDF deals with names that contain full stops without spaces. In order to rectify the overflow problem without invalidating the code that a user could copy and paste into a command line window, the file name has been broken with the escape character <code>\</code> used to escape a hard return.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1689">JBPAPP-1689</ulink>: The <filename>Server Configuration Guide</filename>, section 16.5 contained an error regarding the name of the directory where JBoss Web is deployed. Instead of the path to the <filename>jboss-service.xml</filename> file being <filename>JBOSS_HOME/server/all/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xml</filename> it should be <filename>JBOSS_HOME/server/all/deploy/jboss-web.deployer/META-INF/jboss-service.xml</filename>. For this CP release, the file path has been corrected.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1584">JBPAPP-1584</ulink>: Information about the <classname>LdapExtLoginModule</classname> was missing from the documentation on login modules within the <filename>Server Configuration Guide</filename>. The information about this module has now been added to the <emphasis>Using JBoss Login Modules</emphasis> section of the guide.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>Core Server</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1976">JBPAPP-1976</ulink>: The <classname>HASingletonElectionPolicySimple</classname> class of the Clustering component retrieved the current view from the <classname>HAPartition</classname> and formulated a decision based on that information that ignored the possibility that the service being managed may not be running on all cluster members. To fix this issue the <classname>ExtendedElectionPolicySimple</classname> class has been created and when used it fixes not only the above issue but also an issue where using the <code>kill -9</code> command was necessary to start singletons on other nodes. This new class extends the election policy and provides helper methods for stable implementations.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1932">JBPAPP-1932</ulink>: Java 1.4 based clients would not function when trying to use the Java remote method invocation interface over the Internet Inter-Orb Protocol (RMI-IIOP). This occurred because sections of placeholder code (which allow the program to function correctly) were needed, however these sections of code were compiled with Java 1.5 without compatibility for version 1.4. In order to correct this bug, the <filename>iiop/build.xml</filename> file has been updated with the removal of:
- </para>
-<programlisting>
-<javac destdir="${build.classes}/main"
- optimize="${javac.optimize}"
- target="${javac.target}"
- source="${javac.source}"
-</programlisting>
- <para>
- and replaced with:
- </para>
-<programlisting>
-<javac destdir="${build.classes}/main"
- optimize="${javac.optimize}"
- target="1.4"
- source="1.4"
-</programlisting>
- <para>
- forcing the <filename>build.xml</filename> file to use Java 1.4.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1685">JBPAPP-1685</ulink>: Apache-slide has been upgraded to version 2.1.jdk15-brew. In this change is the renaming of <filename>jakarta-slide-webdavlib.jar</filename> to <filename>webdavlib.jar</filename> and the <filename>commons-httpclient.jar</filename> has been removed from the distribution because it was dependant on an excluded <filename>commons-codec.jar</filename>. Removal of the <filename>commons-httpclient.jar</filename> file does not impact correct functioning of the JBoss Enterprise Application Platform.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1100">JBPAPP-1100</ulink>: <filename>hsqldb</filename> has been upgraded to version 1.8.0.8.patch02-brew. In this change is a change to the <filename>MANIFEST.MF</filename> file. In previous releases the version information was displayed as a timestamp, an example would be:
- </para>
-<screen>
-private-2007/12/18-11:59:06
-</screen>
- <para>
- This release correctly shows the version of <filename>hsqldb</filename> correctly within the <filename>MANIFEST.MF</filename> file as:
- </para>
-<screen>
-1.8.0.8.patch02
-</screen> </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- </section>
- <section id="Known_Issues_with_this_release">
- <title>
- Known Issues with this release
- </title>
- <para>
- Following is a list of known issues at the time of release.
- </para>
- <formalpara>
- <title>General Known Issues</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1774">JBPAPP-1774</ulink>: The JBoss Enterprise Application Platform RPM cannot be installed with only the OpenJDK distribution.
- </para>
- </listitem>
- <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 documented issue is automatically generated as a footnote and places a number beside that of the documented issue, 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-1709">JBPAPP-1709</ulink>: The JPA spec defines the constant with a value that has a typo in the class name:
- </para>
-<programlisting>
-javax.persistence.Persistence.PERSISTENCE_PROVIDER = "javax.persistence.spi.PeristenceProvider"
-</programlisting>
- <para>
- The version of <filename>ejb3-persistence.jar</filename> released in EAP is non-compliant with the JPA spec because it sets the correct classname (without the typo) for this constant.
- </para>
- <para>
- Javadoc for <methodname>javax.persistence.Query.getSingleResult()</methodname> says that the <exceptionname>EntityNotFoundException</exceptionname> will be generated if there is no result. The Javadoc should have mentioned the <exceptionname>NoResultException</exceptionname> instead.
- </para>
- </listitem>
- <!-- <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 attaining 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 reformatted 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-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>
- 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 persists a string containing 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-1068">JBPAPP-1068</ulink>: When using Microsoft SQL and <code>@Type(type="text")</code> in creating a table, the field is correctly created as <varname>text</varname> however when a delete operation 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 <varname>text</varname> and <varname>varchar</varname> 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 millisecond 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 containing 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 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>
- </para>
- </formalpara>
- </section>
-<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
-
-</article>
Added: projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP08.ent
===================================================================
--- projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP08.ent (rev 0)
+++ projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP08.ent 2009-11-16 04:18:47 UTC (rev 96400)
@@ -0,0 +1,3 @@
+<!ENTITY HOLDER "Red Hat, Inc">
+<!ENTITY YEAR "2009">
+<!ENTITY VERSION "4.2">
Added: projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP08.xml
===================================================================
--- projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP08.xml (rev 0)
+++ projects/docs/enterprise/4.2.8/readme/en-US/Release_Notes_CP08.xml 2009-11-16 04:18:47 UTC (rev 96400)
@@ -0,0 +1,1516 @@
+<?xml version="1.0"?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+<!ENTITY % RH_ENTITIES SYSTEM "./Common_Config/rh-entities.ent">
+%RH_ENTITIES;
+]>
+<article id="JBEAP-Release-Notes">
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/>
+ <section id="Introduction">
+ <title>
+ Introduction
+ </title>
+ <para>
+ These release notes contain important information related to JBoss Enterprise Application Platform &VERSION;. New features, known problems, resources, and other current issues are addressed here.
+ </para>
+ <section id="Overview">
+ <title>Overview</title>
+ <para>
+ JBoss Enterprise Application Platform is the next evolutionary step in open source enterprise software. It is a powerful tool for developing rich, high performance, Web 2.0 applications on a pure Java Platform.
+ </para>
+ <para>
+ JBoss Enterprise Application Platform provides complete compatibility with existing J2EE 1.4 enterprise Java applications. At the same time, almost all the key features and components defined in the Java EE 5.0 specification are supported. So your new enterprise Java applications can take immediate advantage of the Java EE 5.0's significantly simpler POJO-based programming model.
+ </para>
+ <para>
+ Further, by integrating best-of-breed open source frameworks such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache the Platform takes advantage of innovations in the open source community. As well, JBoss Enterprise Application Platform is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.
+ </para>
+ <para>
+ All of which means you can develop your new application taking advantage of Java EE 5.0 technologies immediately and with the confidence of knowing it will remain forward-compatible with future versions of the JBoss Platform.
+ </para>
+ </section>
+ </section>
+ <!--<section id="New_Features">
+ <title>New Features in JBoss Enterprise Application Platform &VERSION;</title>
+ <section id="Messaging">
+ <title>JBoss Messaging</title>
+ <para>
+ In this release, JBoss MQ 1.3 has been replaced with JBoss Messaging 1.4. JBoss Messaging provides a high performance messaging infrastructure for JBoss Enterprise Application Platform.
+ </para>
+ </section>
+ <section id="JAX_WS">
+ <title>JBoss Web Services 2.0.1</title>
+ <para>
+ JBoss Web Services is upgraded to 2.0.1 in this release and will now provide a complete implementation of JAX-WS.
+ </para>
+ </section>
+ </section> -->
+ <section id="Component_Versions">
+ <title>Component Versions</title>
+ <para>
+ This section details the versions of the components which create the Enterprise Application Platform 4.3 that can be found in this Cumulative Patch release.
+ </para>
+ <!-- <itemizedlist>
+ <listitem>
+ <para>
+ JBoss Application Server 4.2.z
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Core 3.2.4.SP1.CP07
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Annotations 3.2.1.GA.CP03
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Entity Manager 3.2.1.GA_CP04
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JAF 1.2_10
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Cache 1.4.1.SP11
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss JAXR 1.2.0.SP2
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Remoting 2.2.2.SP11
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Transactions 4.2.3.SP5.CP04
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Web 2.0.0-6.CP09
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Web Services 1.2.1.GA_CP05
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JGroups 2.4.5
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JSF 1.2_10
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Seam 1.2.1.AP
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Xalan 2.7.0.patch02
+ </para>
+ </listitem>
+ </itemizedlist> -->
+ <note>
+ <para>
+ The Enterprise Application Platform Server has been redefined for the enterprise market to a level where direct association to a community release can no longer be drawn.
+ </para>
+ </note>
+ </section>
+ <section id="Installation_Notes">
+ <title>Installation and Migration Notes</title>
+ <para>
+ This section contains information related to installing or upgrading to JBoss Enterprise Application Platform version &VERSION;, including hardware and platform requirements and prerequisites.
+ </para>
+ <section id="install">
+ <title>Installation Notes</title>
+ <para>
+ You must have adequate disk space to install JDK and JBoss Enterprise Application Platform while also allowing enough space for your applications. You must have a working installation of JDK 1.5. For the latest information on supported Operating System / JVM combinations, supported Database platforms and current information on the revision level of included components, please refer to <ulink url="http://www.jboss.com/products/platforms/application/testedconfigurations">http://www.jboss.com/products/platforms/application/testedconfigurations</ulink>. Refer to the installation guide available online from <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> for detailed instructions to install and verify JBoss Enterprise Application Platform.
+ </para>
+ </section>
+ <section id="upgrade">
+ <title>Upgrading from JBoss Enterprise Application Platform 4.2.0.CP05</title>
+ <formalpara>
+ <title>Using CSP/JON</title>
+ <para>Refer to <ulink url="https://network.jboss.com/confluence/display/DOC/Installing+a+Patch">https://network.jboss.com/confluence/display/DOC/Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch.</para>
+ </formalpara>
+ <!--<formalpara>
+ <title>Using RHN</title>
+ <para></para>
+ </formalpara>-->
+ <!--<para>JBoss MQ is now replaced with JBoss Messaging as the JMS implementation shipped within JBoss Enterprise Application Platform 4.3. Since JBoss Messaging is JMS 1.1 and JMS 1.0.2b compatible, the JMS code written against JBossMQ will run with JBoss Messaging without any changes.</para>
+ <para>JBoss Messaging only runs with Java 5 or later. It does not have wire format compatibility with JBoss MQ. Even though JBoss Messaging deployment descriptors are very similar to JBoss MQ deployment descriptors, they are <emphasis>not</emphasis> identical. Also, the database data model is completely different, so don't attempt to use JBoss Messaging with a JBoss MQ data schema and vice-versa.</para>
+ <para>Refer to the JBoss Messaging User Guide for more information.</para> -->
+ </section>
+ </section>
+ <section id="Important_Notes">
+ <title>Important Notes</title>
+ <section id="Seam_Applications">
+ <title>
+ Running the example Seam Applications
+ </title>
+ <para>
+ It is recommended to run the example Seam applications that are included with the documentation using the production configuration. Using another configuration may result in memory issues. Note that the default configuration for the server to start with, if no other configuration is specified, is the production configuration.
+ </para>
+ <warning>
+ <para>
+ To avoid memory issues, adjust the memory settings before deploying the applications. You can do this by updating <literal>JAVA_OPTS</literal> settings in the file <filename>JBOSS_DIST/jboss-as/server/production/run.conf</filename> with these recommended values:
+<programlisting>
+-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m
+</programlisting>
+ </para>
+ </warning>
+ <para>
+ Refer to the "Seam Reference Guide" included in the documentation set (<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>) for important information regarding the deployment of Seam examples and detailed information on developing applications using Seam.
+ <note>
+ <para>Seam version used in this release is 1.2.1.GA.</para>
+ </note>
+ </para>
+ </section>
+ <section id="Default_Security_Settings">
+ <title>
+ Default Security Settings
+ </title>
+ <para>
+ If you are using the rpm, or the zip distribution, please note that by default, authentication is enabled and no user accounts are set up. This is done to prevent unauthorized access to various services of JBoss AS. Please refer to the Installation Guide, or see <ulink url="http://kbase.redhat.com/faq/FAQ_107_9963.shtm">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</ulink> for information on how to make the services accessible again.
+ </para>
+ </section>
+ <section id="Hypersonic_Database">
+ <title>
+ Embedded Hypersonic Database
+ </title>
+ <para>
+ Hypersonic SQL provides default "out of the box" database functionality for evaluation and development use only. It is NOT recommended or supported as a production-use database. Technical support is not available for this component, and while we are happy to accept bugs filed against this component, we do not make any commitment to fix them within a specific timeframe.
+ </para>
+ </section>
+ <section id="source">
+ <title> Source Files </title>
+ <formalpara>
+ <title>SRPMs</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para><ulink url="ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS">ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para><ulink url="ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS">ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para><ulink url="ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS">ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Source ZIP</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="ftp://ftp.redhat.com/pub/redhat/jbeap/4.2.0/en/source/jboss-eap-src-4.2.0-CP06.zip"> ftp://ftp.redhat.com/pub/redhat/jbeap/4.2.0/en/source/jboss-eap-src-4.2.0-CP06.zip</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ </section>
+ </section>
+ <section id="Product-Support-and-License-Links">
+ <title>
+ Product Support and License Website Links
+ </title>
+ <formalpara>
+ <title>Support Processes</title>
+ <para>
+ <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ Production Support Scope of Coverage
+ </title>
+ <para>
+ <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink>
+ </para>
+ </formalpara>
+
+
+ <formalpara>
+ <title>
+ Production Support Service Level Agreement
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ Developer Support Scope of Coverage
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ Developer Support Service Level Agreement
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ Product Update and Support Policy by Product
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ JBoss End User License Agreement
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink>
+ </para>
+ </formalpara>
+ </section>
+
+ <section id="Documentation">
+ <title>
+ Documentation
+ </title>
+ <para>
+ Refer to the index.html file in the documentation directory for a list of included documentation.
+ </para>
+ <para>
+ In the zip distribution, documentation for the Platform and its individual components is distributed in a separate zip file, <filename>jboss-eap-docs-<version>.zip</filename>.
+ </para>
+
+ <para>
+ On a Linux system, the documentation is found in two rpms that will need to be installed manually. These rpms are <filename>jboss-seam-docs-<version>.noarch.rpm</filename>, and <filename>rh-eap-docs-<version>.noarch.rpm</filename>. For help with installing rpm packages on Red Hat Enterprise Linux, please refer to the Red Hat Knowledge base article located at <ulink url="http://kbase.redhat.com/faq/FAQ_35_198.shtm">http://kbase.redhat.com/faq/FAQ_35_198.shtm</ulink>
+ </para>
+ <para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>Installation Guide</filename> explains how to install and verify the installation of JBoss Enterprise Application Platform using different installation modes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>Getting Started</filename> details the directory structure of the platform and a quick tour of the Application Server and different configuration sets and services. Using a simple web application it illustrates the use of JSF-EJB3 components and how to use Seam to integrate the JSF and EJB3 components.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>Server Configuration Guide</filename> explains all administrative and configuration functions in detail.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ Updated versions of the documentation with errata and additional information, example application code, as well as the most recent version of the release notes may be accessed via the web from <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>.
+ </para>
+ </section>
+ <section id="JSR-181">
+ <title>
+ JSR-181 support
+ </title>
+
+ <para>
+ JSR-181 related functionality is not supported in this version of the JBoss Enterprise Application Platform. This functionality is supported in version 4.3.
+ </para>
+ </section>
+
+ <section id="Issues-fixed-in-this-release">
+ <title>
+ Issues fixed in this release
+ </title>
+
+ <para>
+ Following is a list of issues fixed in this release:
+ </para>
+ <formalpara>
+ <title>JBoss Cache</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1993">JBPAPP-1993</ulink>: The JBoss Cache component of the Enterprise Application Platform has been upgraded to version 1.4.1_SP13. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1995">JBPAPP-1995</ulink>: The <methodname>RegionManager.createRegion</methodname> method would allow duplicate region names and when this occurs all future cache operations would happen only on the second instance of the region, while the <methodname>EvictionTimerTask</methodname> will only watch the first instance, causing the eviction queue of the second instance to fill. To correct this bug, the <methodname>RegionManager.checkConflict</methodname> method now counts a duplicate as a conflict and causes the <methodname>RegionManager.createRegion</methodname> method to generate an exception.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1994">JBPAPP-1994</ulink>: The <methodname>findNode</methodname> method of TreeCache generated a <exceptionname>NullPointerException</exceptionname> when the <methodname>findInternal</methodname> method returned a null value. The <methodname>findNode</methodname> method can now handle a null value returned from the <methodname>findInternal</methodname> method by checking within the <filename>TreeCache.java</filename> file if the <varname>toReturn</varname> value is null as well as the <varname>version</varname>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Remoting</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1996">JBPAPP-1996</ulink>: The JBoss Remoting component of the Enterprise Application Platform has been upgraded to version 2.2.3. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1129">JBREM-1129</ulink>: It was possible for <emphasis>PING</emphasis> messages to arrive out of order because socket and bisocket transports use a pool of connections. To fix this bug when a <classname>org.jboss.remoting.Lease</classname> is created a timestamp is associated with it and carried by an initial <emphasis>PING</emphasis> message. The contents of an updated <emphasis>PING</emphasis> message will now be discarded if its timestamp is older than the previously processed timestamp. In the occurrence that the initiating <emphasis>PING</emphasis> message does not have a time stamp, the lease will assume that the client is using an older version of JBoss Remoting and it will accept all updated <emphasis>PING</emphasis> messages.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1128">JBREM-1128</ulink>: Connection identity for the <classname>LeasePinger</classname> and <classname>Lease</classname> pair has been added by setting the parameter <property>org.jboss.remoting.Remoting.USE_CLIENT_CONNECTION_IDENTITY</property> to <emphasis>true</emphasis>. JBoss Remoting then identifies a connection with a <classname>LeasePinger</classname> and <classname>Lease</classname> pair and a client participates in a connection when it is connected by way of the new method <methodname>connect(ConnectionListener listener, Map metadata)</methodname>. This method serves to connect the client to the server by way of a new or existing client invoker, and it also registers the <classname>ConnectionListener</classname> with the client's new or exiting <classname>ConnectionValidator</classname>, while also registering the <classname>ConnectionValidator</classname> with the client invoker's <classname>LeasePinge!
r</classname>. Subsequently, if any <classname>ConnectionValidator</classname> registered with that <classname>LeasePinger</classname> detects a connection failure, it will (if the <property>stopLeaseOnFailure</property> parameter is set to <emphasis>true</emphasis>) stop the <classname>LeasePinger</classname>, and the <classname>LeasePinger</classname> will cause each registered <classname>ConnectionValidator</classname> to notify each of its registered <classname>ConnectionListeners</classname> of the connection failure. If a client is reconnected by a call to the <methodname>Client.connect()</methodname> method, it will be associated with a new <classname>LeasePinger</classname> and be treated as a new connection.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1127">JBREM-1127</ulink>: <exceptionname>ClassCastExceptions</exceptionname> would arise from the caching of <classname>Unmarsharller</classname> and <classname>Classloader</classname> in the <classname>MicroRemoteClientInvoker</classname> and performing classloading when accessing a remote bean from separate isolated EARs. In fixing this issue the <filename>MicroRemoteClientInvoker.java</filename> file has been updated to modify the use of <methodname>useCurrentThreadClassLoader</methodname>, the variable <varname>useCurrentThreadClassLoader</varname> has been added to <filename>RemotingClassLoader.java</filename>, and <filename>JavaSerializationManager.java</filename> has been modified to update the <classname>ObjectInputStream</classname> classloader if the <varname>useCurrentThreadClassLoader</varname> variable of <classname>RemotingClassLoader</classname> has a value of true.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1125">JBREM-1125</ulink>: When a <classname>java.util.Timer</classname> class no longer had <classname>TimerTasks</classname> in its queue, it would allow itself to shut down. This behavior caused subsequent calls to the <methodname>Timer.schedule()</methodname> method to generate a <exceptionname>java.lang.IllegalStateException</exceptionname>. The exception has been overcome by modifying the <filename>AbstractDetector.java</filename> file to test for an <exceptionname>IllegalStateException</exceptionname> when scheduling on the <classname>heartbeatTimer</classname> and <classname>Timer</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1121">JBREM-1121</ulink>: Functionality has been added to the client <classname>SocketFactory</classname> that allows it to be configurable by the <classname>InvokerLocator</classname> so that all the parameters from the <classname>InvokerLocator</classname> are available instead of only those in the configuration map.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1119">JBREM-1119</ulink>: If the application called the <methodname>org.jboss.remoting.Client.removeListener()</methodname> method, then <classname>ServerInvoker</classname> would remove references to <classname>ServerInvokerCallbackHandler</classname>, and it would call the <methodname>ServerInvocationHandler.removeListener()</methodname> method, granting the application a chance to remove the reference it held. An issue arose if the connection from the client was to break as that would cause none of the above to be executed, leading to a memory leak in the program. To fix the problem, <classname>ConnectionNotifier</classname> now uses copies of lists in order to avoid a <exceptionname>ConcurrentModificationException</exceptionname>, a <methodname>shutdown()</methodname> method has been added to the <classname>ServerInvokerCallbackHandler</classname>, and within the <classname>ServerInvoker</classname> the <metho!
dname>removeCallbackHandler()</methodname> method has been made public and a <methodname>shutdownCallbackHandler()</methodname> method has been added. These changes mean that the <methodname>shutdown()</methodname> method within the <classname>ServerInvokerCallbackHandler</classname> can be used by the application to remove the necessary references by utilizing the <classname>ServerInvoker</classname> and the applications <classname>ServerInvocationHandler</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1112">JBREM-1112</ulink>: Upon a connection failure there was occurrences of a race condition occurring between the <classname>ConnectionValidator</classname> and <classname>ConnectionListener</classname> as <classname>ConnectionValidator</classname> may be able to execute the <methodname>Client.getDisconnectTImeout()</methodname> method before a <classname>ConnectionListener</classname> executes <methodname>Client.setDisconnectTimeout()</methodname>, causing the program to behave unexpectedly. This issue has been fixed by introducing a new parameter called <property>ConnectionValidator.FAILURE_DISCONNECT_TIMEOUT</property> (with the actual value of <varname>failureDisconnectTimeout</varname>). If the <property>org.jboss.remoting.Client.USE_ALL_PARAMS</property> property (with the actual value of <varname>useAllParams</varname>) is set to <emphasis>true</emphasis>, this parameter can be set in the <classname>Invok!
erLocator</classname>, the client's configuration map, or the metadata map passed to the <methodname>Client.addConnectionListener()</methodname> method. If <emphasis>failureDisconnectTimeout</emphasis> is set to an integer value other than -1, then <classname>ConnectionValidator</classname> will use that value when it calls the <methodname>ClientInvoker.terminateLease()</methodname> method, otherwise the value returned by the <methodname>Client.getDisconnectTimeout()</methodname> method is used.
+
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1111">JBREM-1111</ulink>: In <classname>LeasePinger</classname> when all the <classname>TimerTasks</classname> that ran in <classname>java.util.TimerTask</classname> were shut down the <classname>Timer</classname> would also shut down and will not accept any further <classname>TimerTasks</classname>. If a new <classname>Timer</classname> was to be created and a <classname>TimerTask</classname> scheduled for it, an exception would occur. In order to successfully replace the <classname>Timer</classname> if it has shut down, the <methodname>Wrapped timer.schedule()</methodname> is now utilized.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1110">JBREM-1110</ulink>: The method <methodname>org.jboss.remoting.InvokerLocator.getParameters()</methodname> would return null if the URL had no parameters. In this updated release, the method returns an empty <varname>Map</varname> instead to ensure safer execution.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1109">JBREM-1109</ulink>: Within the <methodname>org.jboss.remoting.MicroRemoteClientInvoker.getDataType()</methodname> method when the <varname>dataType</varname> variable was set to the value of the <methodname>getDataType(getLocator())</methodname> method, the variable would temporarily be set to null if the <classname>InvokerLocator</classname> had no datatype parameter. This caused issues because another thread may use the <varname>dataType</varname> variable and return a value of null. Correcting this bug has lead to using a local variable called <varname>localDataType</varname> while a check occurs to see if <classname>InvokerLocator</classname> contains a datatype value. The number of threads has also been reduced to 1000 in order to avoid an <exceptionname>OutOfMemoryError</exceptionname> that may have occurred.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1104">JBREM-1104</ulink>: When the <methodname>org.jboss.remoting.ident.Identity.get()</methodname> method would fail in a call to <methodname>InetAddress.getLocalHost()</methodname>, the runtime exception <exceptionname>java.lang.RuntimeException: Exception creating identity: myhost: myhost</exceptionname> would be generated. The issue was that the exception message did not give any information to the user concerning the underlying problem relating to the host name. This output has been fixed to display to the user the correct information in relation to the main host name issue.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1102">JBREM-1102</ulink>: A feature was requested that would make the configuration map available to the <classname>marshalFactory</classname>. In order to support this the new parameter <property>org.jboss.remoting.Remoting.PASS_CONFIG_MAP_TO_MARSHAL_FACTORY</property> has been added, which requires a setting of <emphasis>true</emphasis> in order to have the configuration map passed to the <classname>marshalFactory</classname>. If the parameter contains a value of <emphasis>false</emphasis> then the original behavior will be executed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1100">JBREM-1100</ulink>: A feature was requested whereby <classname>ServerInvokerServlet</classname> instances could be linked to <classname>Connectors</classname> by MBean names rather than locator URLs. In order to achieve this the parameter <property>org.jboss.remoting.transport.servlet.ServletServerInvoker.CREATE_UNIQUE_OBJECT_NAME</property> has been added. When set to <emphasis>true</emphasis>, <methodname>ServletServerInvoker.getMBeanObjectName()</methodname> will call <methodname>org.jboss.remoting.ServerInvoker.getMBeanObjectName()</methodname> and return an <emphasis>ObjectName</emphasis> derived by the same algorithm that is used for all transports. To ensure the original default behavior remains, the default value is <emphasis>false</emphasis>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1099">JBREM-1099</ulink>: The multicast detector did not work correctly in environments where many JBoss Remoting invokers were being used. The <methodname>org.jboss.remoting.detection.AbstractDetector.createDetection()</methodname> method would create a detection message based on the number of server invokers registered locally. In the JBoss Enterprise Application Server this would cause an error as the message size would exceed the 4000 limit. A <property>buffersize</property> attribute has been created for <classname>org.jboss.remoting.detection.multicast.MulticastDetector</classname> and <classname>org.jboss.remoting.detection.multicast.MulticastDetectorMBean</classname> that defaults to a value of 10000.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1088">JBREM-1088</ulink>: If the server hostname DNS mapping was not available at the client during a <methodname>org.jboss.remoting.Client.connect()</methodname> call, the <methodname>org.jboss.remoting.transport.socket.MicroSocketClientInvoker.setup() getAddressByName</methodname> produces a <exceptionname>java.net.UnknownHostException</exceptionname> in relation to the hostname. However when the method <methodname>MicroSocketClientInvoker(InvokerLocator locator, Map configuration)</methodname> is called the exception is captured and then displayed using <methodname>throw new RuntimeException(ex.getMessage())</methodname>. By displaying the exception in this way, information important in understanding the cause of the exception, is lost. This has been rectified by changing <methodname>throw new RuntimeException(ex.getMessage());</methodname> to <methodname>throw new RuntimeException(ex.getMessage(), ex);</method!
name>, enabling the actual exception content to be displayed to the user.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1085">JBREM-1085</ulink>: The log level of the <methodname>ServerSocketWrapper.close()</methodname> method log messages has been reduced in order to remove unwanted information. Instead of using the <methodname>log.debug()</methodname> call, the method now uses <methodname>log.trace()</methodname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1084">JBREM-1084</ulink>: When <methodname>org.jboss.remoting.Client.addConnectionListener()</methodname> created a <classname>CallbackPoller</classname>, a reference to itself and a metadata map would be passed. The issue arose from the <classname>CallbackPoller</classname> only accessing parameters in the metadata map. To rectify this issue the <property>Client.USE_ALL_PARAMS</property> parameter is checked within the <classname>InvokerLocator</classname>, the client's configuration map and the metadata map that is passed to the <methodname>Client.addListener()</methodname> method respectively. If the <property>useALLParams</property> property is found and set to a value of <emphasis>true</emphasis>, the <classname>InvokerLocator</classname>, the client's configuration map and the metadata map will be searched respectively for all parameters used by <classname>CallbackPoller</classname>, otherwise only the metad!
ata map will be used, which is the default behavior.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1082">JBREM-1082</ulink>: When <methodname>org.jboss.remoting.Client.addConnectionListener()</methodname> created a <classname>ConnectionValidator</classname>, a reference to itself would be passed and the <classname>ConnectionValidator</classname> would access the client's configuration map. The issue arose from the client's configuration map not including the <classname>InvokerLocator</classname> parameters. To rectify this issue the <classname>ConnectionValidator</classname> now searches for the <property>Client.USE_ALL_PARAMS</property> parameter in the <classname>InvokerLocator</classname>, the client's configuration map and the metadata map that is passed to the <methodname>Client.addConnectionListener()</methodname> method respectively. If the <property>useALLParams</property> property is found and set to a value of <emphasis>true</emphasis>, the <classname>ConnectionValidator</classname> will search for pa!
rameter values in the <classname>InvokerLocator</classname>, the client's configuration map and the metadata map respectively.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBREM-1081">JBREM-1081</ulink>: When the method <methodname>ServerInvokerCallbackHandler.destroy()</methodname> shut down <classname>When org.jboss.remoting.callback.ServerInvokerCallback</classname>, the variables <varname>callBackClient</varname> and <varname>callbackStore</varname> were set to null. If the <methodname>ServerInvokerCallbackHandler.handleCallback()</methodname> is then called a <exceptionname>NullPointerException</exceptionname> arises because that variables <varname>callBackClient</varname> and <varname>callbackStore</varname> are set to null. This bug has been corrected in this latest release by the <methodname>ServerInvokerCallbackHandler.destroy()</methodname> method no longer assigning a value of null to the variables <varname>callBackClient</varname> and <varname>callbackStore</varname>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Web</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2067">JBPAPP-2067</ulink>: The release of Tomcat 6.0.20 saw a set of security vulnerabilities fixed that have now been backported to JBoss Web. These vulnerabilities are:
+ </para>
+ <itemizedlist>
+ <!-- <listitem>
+ <para>
+ <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0033">CVE-2009-0033</ulink>: For Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when the <filename>Java AJP</filename> connector and <filename>mod_jk</filename> load balancing were used it would allow for remote attackers to cause a denial of service (application outage) attack via a crafted request with invalid headers. This would occur in relation to the temporary blocking of connectors that had encountered errors, as demonstrated by an error involving a malformed <filename>HTTP Host</filename> header. This update has been rated as having important security impact by the Red Hat Security Response Team.
+ </para>
+ </listitem> -->
+ <listitem>
+ <para>
+ <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5515">CVE-2008-5515</ulink>: Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, 6.0.0 through 6.0.18, and possibly earlier versions normalized the target pathname before filtering the query string when using the <methodname>RequestDispatcher</methodname> method, which allowed remote attackers to bypass intended access restrictions and conduct directory traversal attacks via <code>..</code> (dot dot) sequences and the <filename>WEB-INF</filename> directory in a <classname>Request</classname>. This update has been rated as having important security impact by the Red
+ Hat Security Response Team.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0783">CVE-2009-0783</ulink>: Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18 would permit web applications to replace an XML parser used for other web applications. This would allow local users to read or modify the <filename>web.xml</filename>, <filename>context.xml</filename>, or <filename>tld</filename> files of arbitrary web applications via a crafted application that is loaded earlier than the target application. This update has been rated as having low security impact by the Red Hat Security Response Team.
+ </para>
+ </listitem>
+ <!-- <listitem>
+ <para>
+ <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0781">CVE-2009-0781</ulink>: A Cross-site scripting (XSS) vulnerability existed within the <filename>jsp/cal/cal2.jsp</filename> calendar examples web application for Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18. This vulnerability would allow remote attackers to inject arbitrary web script or HTML via the time parameter, related to <emphasis>invalid HTML</emphasis>. This update has been rated as having low security impact by the Red Hat Security Response Team.
+ </para>
+ </listitem> -->
+ <listitem>
+ <para>
+ <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0580">CVE-2009-0580</ulink>: For Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when <property>FORM</property> authentication was used, this would allow remote attackers to enumerate valid usernames via requests to <filename>/j_security_check</filename>. This would be achieved with malformed URL encoding of passwords, related to improper error checking in the <classname>MemoryRealm</classname>, <classname>DataSourceRealm</classname>, and <classname>JDBCRealm</classname> authentication realms, as demonstrated by a <code>%</code> (percent) value for the <property>j_password</property> parameter. This update has been rated as having low security impact by the Red Hat Security Response Team.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2050">JBPAPP-2050</ulink>: When attempting to view a <emphasis>mbean</emphasis> graph through the <emphasis>web-console</emphasis> an exception was being generated by the applet because the <filename>jcommon.jar</filename> library was not included within the ZIP version of the previous release. This library file is now included with this release and <emphasis>mbean</emphasis> graphs are now viewable through the <emphasis>web-console</emphasis>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1874">JBPAPP-1874</ulink>: The JBoss Web component of the Enterprise Application Platform has been upgraded to version 2.0.0.CP10. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1992">JBPAPP-1992</ulink>: Apache Tomcat 5 and 6 did not properly handle double quote (<emphasis>"</emphasis>) characters and the encoded backslash (%5C) sequences in cookie values. These bugs may have allowed for sensitive information such as session IDs to be leaked to remote attackers and permit session hijack attacks. This has been rectified by the modification of <filename>ApplicationContext.java</filename> to generate a <exceptionname>MalformedURLException</exceptionname> if a path starts with an encoded backslash and the modification of <filename>ServerCookie.java</filename> to escape double quote characters. (CVE-2007-5333)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1950">JBPAPP-1950</ulink>: After the <methodname>HttpServletResponse.reset</methodname> method was executed, any subsequent calls to <methodname>response.setContentType</methodname> or <methodname>response.setCharacterEncoding</methodname> had no effect on the content type. This latest release incorporates a fix that allows the <methodname>response.setContentType</methodname> and <methodname>response.setCharacterEncoding</methodname> methods to function correctly after a <methodname>HttpServletResponse.reset</methodname> call and modify the content type. To achieve this outcome the following method executions have been added to the <methodname>reset()</methodname> method of the <classname>Response</classname> class:
+ </para>
+<programlisting>
+usingOutputStream = false;
+usingWriter = false;
+isCharacterEncodingSet = false;
+</programlisting>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1873">JBPAPP-1873</ulink>: When the <parameter>LIMIT_BUFFER</parameter> parameter was set to <code>true</code> an <exceptionname>ArrayIndexOutOfBoundsException</exceptionname> would occur. The <filename>BodyContentImpl.java</filename> file has been updated to correct this bug by removing the <varname>bufferSizeSave</varname> variable and removing the case where the <varname>writer</varname> variable isn't null. To replace these a case has been written to execute the <methodname>clearBody</methodname> method when the <varname>writer</varname> variable is equal to null. By implementing these changes the <classname>JspWriter</classname> buffer size and remaining bytes are calculated correctly, removing the <exceptionname>ArrayIndexOutOfBoundsException</exceptionname>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Web Services</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1971">JBPAPP-1971</ulink>: The JBoss Web Services component of the Enterprise Application Platform has been upgraded to version 1.2.1.GA_CP05. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1972">JBPAPP-1972</ulink>: MIME boundaries in the <classname>MultipartRelatedDecoder</classname> were handled incorrectly. This bug has been fixed by modifying the <classname>MultipartRelatedDecoder</classname> class to use a new instance of the <classname>PushbackInputStream</classname> in the creation of the <classname>BoundaryDelimitedInputStream</classname>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <!-- <formalpara>
+ <title>JBoss Seam</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara> -->
+ <formalpara>
+ <title>JGroups</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2002">JBPAPP-2002</ulink>: The JGroups component of the Enterprise Application Platform has been upgraded to version 2.4.6. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JGRP-975">JGRP-975</ulink>: The JGroups testsuite did not permit a user to specify host and port properties for the <classname>GossipRouter</classname> implementation. This meant that the IP address was fixed at 127.0.0.1 and the port was fixed at 12001. This update allows for the host and port properties to be configurable so that the system can be tested against other values other than only the defaults.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JGRP-961">JGRP-961</ulink>: Running the JGroups testsuite against IPv6 addresses using <property>link-local</property> IPv6 addresses with no zone ID would cause some tests to fail that would normally pass when run against IPv4 addresses. The problem arose if the zone ID was omitted and the OS assigned a default interface to send the message, which may not have been the one the user was after. To correct this issue so that IPv6 addresses worked correctly with JGroups, scoped <property>link-local</property> addresses had to be used with the <classname>ServerSocketReceiver</classname> and <classname>ServerSocketSender</classname> classes, enabling use of the correct zone ID in each IPv6 address case.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JGRP-949">JGRP-949</ulink>: Format version information was not displayed to the user in the most meaningful way. In order to make sure the the user receives the most useful information the way in which the format version information is provided has changed from:
+ </para>
+<programlisting>
+log.warn(new StringBuffer("packet from ").append(client_addr).append(':').append(client_port).append(" has different version (").append(version).append(") from ours (").append(Version.version).append("). This may cause problems"));
+</programlisting>
+ <para>
+ To:
+ </para>
+<programlisting>
+log.warn(new StringBuffer("packet from ").append(client_addr).append(':').append(client_port).append(" has different version (").append(version).append(") from ours (").append(Version.print(Version.version)).append("). This may cause problems"));
+</programlisting>
+ <para>
+ Of note is the change of <code>Version.version</code> to <code>Version.pring(Version.version)</code>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JGRP-923">JGRP-923</ulink>: GMS address printing did not contain the cluster name in the details it provided. For this Cumulative Patch release GMS address printing has been updated to include the cluster name in order to provide more detail to a user.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JGRP-893">JGRP-893</ulink>: Previously JGroups could not parse IPv6 addresses in the stack configuration correctly as it used a double colon (::) as a delimiter. These characters are now parsed correctly in JGroups so that IPv6 addresses can be used in a stack configuration correctly.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Hibernate</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2118">JBPAPP-2118</ulink>: The Hibernate EntityManager component of the Enterprise Application Platform has been upgraded to version 3.3.2. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-341">EJB-341</ulink>: If a user attempted to create a named query that did not exist, a <exceptionname>PersistenceException</exceptionname> would be generated where an <exceptionname>IllegalArgumentException</exceptionname> should have been raised, and the current transaction would be rolled back. The <classname>AbstractEntityManagerImpl</classname> class has been updated to catch the <exceptionname>MappingException</exceptionname> and return an <exceptionname>IllegalArgumentException</exceptionname> to the user, as well as attempt to return a new named query using <classname>QueryImpl</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-340">EJB-340</ulink>: The <methodname>onLoad</methodname> method was not invoked on an <classname>EJB3Interceptor</classname>, though it was in the basic Hibernate environment. This issue has been fixed by editing the <classname>EventListenerConfigurator</classname> class to include the default Hibernate Core <classname>PreLoadEventListener</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-333">EJB-333</ulink>: A space was present in the path during deployment within the JBoss Enterprise Application Platform and this space would cause an error. In order to fix this, the <classname>ExplodedJarVisitor</classname>, <classname>FileZippedJarVisitor</classname> and <classname>JarVisitorFactory</classname> classes have been updated to cater for a space in a java URL file name.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-330">EJB-330</ulink>: If the <classname>Ejb3Configuration</classname> had classes that contained <property>@PostLoad</property> callbacks and had been added with the <methodname>addAnnotatedClass</methodname> method, these would no longer work if the <methodname>configure</methodname> method was executed before the addition of <classname>@Entity-annotated</classname> classes, through the use of the <methodname>addAnnotatedClass</methodname> method. This bug has been fixed by delaying the call to the <methodname>configure</methodname> method in order to allow for the correct addition of all annotated classes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-326">EJB-326</ulink>: The persistence unit root that exists in a <filename>.war</filename> file was not being correctly handled. This issues has been fixed by changing the way in which the EJB3 submits the persistence root URL to Hibernate.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-325">EJB-325</ulink>: The <classname>Ejb3Configuration</classname> class has been updated to ensure that <exceptionname>PersistenceExceptions</exceptionname> state the <classname>persistenceUnit</classname> that is generating the exception.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-316">EJB-316</ulink>: The <property>PERSISTENCE_PROVIDER</property> string should be coded as a <property>final</property> string type. The <classname>Persistence</classname> class has been updated for this release to include the <property>PERSISTENCE_PROVIDER</property> string as a <property>final</property> string type.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-305">EJB-305</ulink>: As a new feature, a configuration option has been added that grants the ability to define a session scoped interceptor through the use of the <property>hibernate.ejb.interceptor.session_scoped</property> property.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-299">EJB-299</ulink>: If a <property>package-info.class</property> attribute existed within the default package the <methodname>JarVisitor.addElement</methodname> method would fail and generate a <exceptionname>StringIndexOutOfBoundsException</exceptionname>. Updating the <classname>AbstractJarVisitor</classname> class so that if the name length of the entry is set it the length of the <property>package-info.class</property> attribute, the name is left blank, otherwise the name property is the length of the entries specified name.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-284">EJB-284</ulink>: A bug existed within the <classname>ArchiveBrowser</classname> where it would not abstract a file path for <filename>orm.xml</filename> correctly when Hibernate was run on the Windows operating system. In this new version of Hibernate EntityManager, the ArchiveBrowser has been replaced with the <classname>JarVisitor</classname>. This process has caused this issue to be fixed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-282">EJB-282</ulink>: The <filename>ORM.xml</filename> file was being ignored when the <property>excludeUnlistedClass</property> property was set to <emphasis>true</emphasis> in the container mode. This bug has been rectified by modifying the <classname>Ejb3Configuration</classname> class to ensure that the <filename>ORM.xml</filename> file is searched even when the <property>excludeUnlistedClass</property> property is set to <emphasis>true</emphasis>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-277">EJB-277</ulink>: String values could not be used as query hint values within Hibernate. This functionality has now been added to Hibernate EntityManager by modifying the <classname>ConfigurationHelper</classname> class to accept string values and the <classname>QueryImpl</classname> class to utilize these changes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-275">EJB-275</ulink>: Since IBM WebSphere does now return an encoded URL from the <methodname>cl.getResources</methodname> method, the <classname>JarVisitor</classname> would fail due to white space errors. The <classname>JarVisitor</classname> class has now been updated to ensure that URLs returned by IBM WebSphere is striped of any white space that may cause the program to produce an error.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-271">EJB-271</ulink>: The <classname>EJB3OverridenAnnotationReader</classname> class has been improved by raising a warning when deployment descriptors refer to an unknown property. This has been achieved by checking for orphan properties.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-269">EJB-269</ulink>: Hibernate EntityManager would fail to deploy a persistence archive in the <emphasis>Weblogic Server</emphasis>. This issue has been rectified by including a <filename>.jar file</filename> for archive browser handling for the <emphasis>Weblogic Server</emphasis>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-266">EJB-266</ulink>: Hibernate would initialize lazy objects that were being traversed by the <methodname>persist</methodname> operation. This release sees the Hibernate EntityManager avoid collection loading during a cascaded <methodname>persist</methodname>, allowing for increased performance on heavily cascaded object graphs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-263">EJB-263</ulink>: Within the <classname>QueryImpl</classname> class, elements were not being made unique before <methodname>getSingleResult</methodname> method exceptions were being raised. This allowed for a <exceptionname>NonUniqueResultException</exceptionname> to be generated incorrectly. For this release, elements within the <classname>QueryImpl</classname> class are now made unique before any <methodname>getSingleResult</methodname> method exceptions are raised.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-262">EJB-262</ulink>: An improvement has been made to the <classname>Ejb3Configuration</classname> class that provides the XML file name when a parsing error occurs. In completing this task the new class <classname>NamedInputStream</classname> has been created.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-259">EJB-259</ulink>: <filename>ORM.xml</filename> files that appear in any referenced <filename>.jar</filename> files were not evaluated by Hibernate EntityManager. In order to be in line with the EJB3 specifications, the <classname>Ejb3Configuration</classname> class has been updated to make sure all <filename>ORM.xml</filename> files are evaluated.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-257">EJB-257</ulink>: The <classname>EJB3Configuration</classname> class should be able to work successfully without needing to use any <methodname>configure</methodname> methods. This update allows for the <classname>EJB3Configuration</classname> class to work correctly without the need for any <methodname>configure</methodname> methods by copying the programmatically defined properties and using them with the new <classname>AnnotationConfiguration</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-242">EJB-242</ulink>: The <classname>InputStreamZippedJarVisitor</classname> class has been updated to produce an exception instead of an IO exception so that Eclipse does not produce a <exceptionname>NullPointerException</exceptionname> but instead just logs a warning message. This allows for Hibernate and Eclipse to function easier together.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-46">EJB-46</ulink>: The <methodname>PrePersist</methodname> callback method was not being utilized if the <property>primary key</property> of the entity was set to null. The way in which the Hibernate EntityManager would operate when a <property>primary key</property> of the entity was set to null has been changed so that the <methodname>PrePersist</methodname> callback method can be correctly utilized.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2110">JBPAPP-2110</ulink>: The Hibernate Validator component of the Enterprise Application Platform has been upgraded to version 3.0.0. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-10">HV-10</ulink>: The Luhn algorithm has been implemented in Hibernate Validator and the <classname>@CreditCardNumber</classname> interface created. The Luhn algorithm implementation requires a valid credit card number and checks for user error. This class does not check for credit card validity.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-9">HV-9</ulink>: The <classname>@Digits</classname> interface has been added to Hibernate Validator. This interface allows for digits to be expressed as integers and fractions. This new interface resides within the <filename>Digits.java</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-8">HV-8</ulink>: Hibernate Validator now supports pure <emphasis>JavaPersistence</emphasis> players. Though when used through <classname>EntityListeners</classname>, parameters such as <property>interpolator</property> are not supported due to the listener lifecycle not being defined and no avenue exists to pass the PU properties.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-7">HV-7</ulink>: Two level <property>@Valid</property> annotation did not work as a user would have expected. A <exceptionname>NullPointerException</exceptionname> would be generated when initialization occurred in the <classname>ClassValidator</classname>. This bug has since been fixed by initializing the <classname>reflectionManager</classname> within the <classname>ClassValidator</classname> constructor.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-6">HV-6</ulink>: The <property>@EAN</property> annotation type has been added to Hibernate Validator. This element checks if the string is a correctly formated EAN-13 or UPC-A code; it does not check for number validity.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-5">HV-5</ulink>: The ability to have multiple validators of the same type for each element has been added to Hibernate Validator. Though Hibernate Validator could already achieve this functionality to an extent, this improvement allows for greater ease of use for the user.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-3">HV-3</ulink>: The <property>@Email</property> validating string would fail if the string contained a null value. The <classname>EmailValidator</classname> class has been modified to include checking for a null value and to handle this case correctly so that the validation does not fail.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-2">HV-2</ulink>: String support for both <property>@Past</property> and <property>@Future</property> validating Strings has been deprecated as there was no absolute way to be sure of the date and time format or the locale that may be used.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/HV-1">HV-1</ulink>: A new feature has been added to Hibernate Validator that sets the <classname>ClassValidator</classname> as being independant of Hibernate Annotations. This ensures that if a users wishes, Hibernate Validator does not have to be used with Hibernate Annotations.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2118">JBPAPP-2037</ulink>: The Hibernate Core component of the Enterprise Application Platform has been upgraded to version 3.2.4.SP1_CP08. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1930">JBPAPP-1930</ulink>: A <exceptionname>NullPointerException</exceptionname> would occur when a native SQL query coupled eager fetching with a many-to-many relationship. Correcting this has meant that the <code>if ( collectionPersister.isOneToMany() ) {</code> line of code in the <filename>SQLQueryReturnProcessor</filename> file has been changed to <code>if ( collectionPersister.isOneToMany() || collectionPersister.isManyToMany()) {</code>, removing the generation of a <exceptionname>NullPointerException</exceptionname>. To note though is that the fix only works with the <filename>hbm.xml</filename> file SQL mapping feature and a named query.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1922">JBPAPP-1922</ulink>: A bottleneck existed within the <filename>EntityModeToTuplizerMapping.java</filename> file when a high number of threads attempted to initialize sets and had to wait for the same monitor. In correcting this issue, the <filename>EntityModeToTuplizerMapping.java</filename> file has been modified to remove the <code>private final Map tuplizers = Collections.synchronizedMap( new SequencedHashMap() ); </code> line of code and replace it with only <code>private final Map tuplizers;</code> and two new public methods to assist in the mapping.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1797">JBPAPP-1797</ulink>: Transient entities could be inserted twice when a merge was performed. To correct this bug the <filename>DefaultMergeEventListener.java</filename> file has been updated to use the new <classname>CopyCache</classname> class. Within the <filename>DefaultMergeEventListener.java</filename> file, logic has been added to retrieve transient entities and retry a merge once if an error is encountered. Following this, if the merge continues unsuccessfully a <exceptionname>TransientObjectException</exceptionname> will be generated. The <classname>CopyCache</classname> class has been created to be the <varname>Map</varname> implementation used by <classname>DefaultMergeEventListener</classname> in order to keep track of entities and the copies that are being merged into the session. This implementation also tracks whether a an entity in the <classname>CopyCache</classname> is included in the merge.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1748">JBPAPP-1748</ulink>: When merging read-only entities that had the <varname>@Immutable</varname> annotation included the following failure would occur:
+ </para>
+<screen>
+org.hibernate.AssertionFailure: Merged entity does not have status set to MANAGED; EntityEntry[com.tll.model.impl.AccountHistory#71794688](READ_ONLY) status=READ_ONLY
+</screen>
+ <para>
+ The <filename>DefaultMergeEventListener.java</filename> file has been updated by editing the following test statement:
+ </para>
+<programlisting>
+if ( entry.getStatus() != Status.MANAGED ) {
+ throw new AssertionFailure( "Merged entity does not have status set to MANAGED; "+entry+" status="+entry.getStatus() );
+}
+</programlisting>
+ <para>
+ modified to test against the possibility that the current <varname>Status</varname> could be <property>READ_ONLY</property>:
+ </para>
+<programlisting>
+if ( entry.getStatus() != Status.MANAGED && entry.getStatus() != Status.READ_ONLY ) {
+ throw new AssertionFailure( "Merged entity does not have status set to MANAGED or READ_ONLY; "+entry+" status="+entry.getStatus() );
+}
+</programlisting>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1564">JBPAPP-1564</ulink>: The SQL <methodname>trim</methodname> function and support for <property>mod</property> and <property>bit_length</property> were not present in the Sybase Dialect. This release sees these available for use within the <filename>SybaseASE15Dialect</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1563">JBPAPP-1563</ulink>: The SQL functions <function>mod</function>, <function>bit_length</function> and <function>trim</function> caused failures in the <classname>ASTParserLoadingTest</classname> because they were not implemented in the Sybase Dialect. The Sybase Dialect has now been updated to import the <classname>org.hibernate.dialect.function.AnsiTrimEmulationFunction</classname> function and implement the <function>mod</function>, <function>bit_length</function> and <function>trim</function> functions.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2078">JBPAPP-2078</ulink>: The Hibernate Annotations component of the Enterprise Application Platform has been upgraded to version 3.3.1. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-701">ANN-701</ulink>: The error message given when using the <property>@CollectionId</property> property incorrectly did not give useful information to the user. Correcting this, the <filename>CollectionBinder.java</filename> file has been updated to generate an exception with all relevant information given the improper use of the <property>@CollectionId</property> property for individual cases.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-700">ANN-700</ulink>: The <classname>NamedQuery</classname> class of Hibernate had the <property>flushMode</property> attribute set to <property>AUTO</property> by default. This caused inconsistencies throughout the program and the <property>flushMode</property> attribute to never contain the correct value. To correct this the default value of the <property>flushMode</property> attribute is now set to a newly introduced <property>PERSISTENCE_CONTEXT</property>. This new value makes sure that the <property>flushMode</property> is consistent with the persistence context at the time the query is executed, alleviating inconsistency issues.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-699">ANN-699</ulink>: The <methodname>AnnotationBinder.mustBeSkipped</methodname> contains a hardcoded reference to the <classname>org.hibernate.tool.instrument.javassist.FieldHandler</classname> class. The issue that arises from this is that the class is actually contained within a different package and by having the incorrect reference it caused all <classname>javassist-instrumented</classname> classes to not function correctly. In order to rectify this issue the reference to the <classname>FieldHandler</classname> class has been changed within the <methodname>AnnotationBinder.mustBeSkipped</methodname> method to be <classname>org.hibernate.bytecode.javassist.FieldHandler</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-698">ANN-698</ulink>: Having an unbound property when default field access is used would lead to an unbound <exceptionname>AnnotationException</exceptionname>. The generated exception is now caught by the program and a more meaningful <exceptionname>AnnotationException</exceptionname> is generated and displayed to the user instead. These changes have been made to the <classname>AnnotationBinder</classname> class.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-696">ANN-696</ulink>: When a Hibernate map existed that had both <property>key</property> and <property>value</property> elements, the <property>@Type</property> annotation would affect both. To generate desired results the <filename>MapBinder.java</filename> and <filename>MapKey.java</filename> files have been updated to include and use a <classname>MapKey</classname> <property>@Type</property>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-695">ANN-695</ulink>: New Hibernate Search collection even listeners have been integrated with the addition of the new classes <classname>CollectionSearchConfiguration</classname> and <classname>SearchConfiguration</classname>, and the amendment of the <classname>AnnotationConfiguration</classname> class to use the new <classname>SearchConfiguration</classname> class instead of embedding the search functionality within the <classname>AnnotationConfiguration</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-694">ANN-694</ulink>: An incorrect report of a Foreign Key circularity error was occurring when the <property>@*ToOne</property> property name started with the identifier property name. The issue has been fixed by modifying the <filename>ToOneFkSecondPass.java</filename> file to make the <methodname>ToOneFkSecondPass</methodname> method a public method.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-690">ANN-690</ulink>: Previous releases did not allow for method chaining within the <classname>AnnotationConfiguration</classname> class. This functionality has now been added by overriding all relevant configuration methods that reside within the <classname>AnnotationConfiguration</classname> class.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-683">ANN-683</ulink>: When <property>hashCode</property> collisions occurred within <classname>AnnotationConfiguration</classname>, random binding failures would occur. To fix this issue, the <filename>FkSecondPass.java</filename> file has been updated to use a unique counter in order to differentiate between two instances of <classname>FkSecondPass</classname> so that they can be compared as the IBM VM would sometimes return the same <varname>hashCode</varname> for two different objects. The <filename>AnnotationConfiguration.java</filename> file has also been updated to utilize the changes made to <filename>FkSecondPass.java</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-673">ANN-673</ulink>: <classname>AnnotationConfiguration</classname> did not define stable ordering for foreign key columns, allowing them to appear in any order within a generated SQL schema. Also of issue was when the <classname>hbm2ddl</classname> tool was being used to see a generated schema. The ordering of a foreign key column within a table could change if an unrelated modification was made inside the mapping of a different table. This issue was fixed by the solution for <emphasis>ANN-683</emphasis> that is specified within these release notes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-671">ANN-671</ulink>: When the <classname>Validator</classname> was not present, a message describing this would be logged, however this would occur twice. In this update the <classname>AnnotationConfiguration</classname> class has been modified to only log the occurrence of this once for each time.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-653">ANN-653</ulink>: The ability to use <property>@AssociationOverride</property> when overriding a collection delivered undesired results in the form of an exception. This functionality has now been fixed and works as expected.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-650">ANN-650</ulink>: In previous versions the <classname>@Version</classname> class could be set within an <classname>@Embedded</classname> class without any checking and generate a <exceptionname>java.lang.ArrayIndexOutOfBoundsException</exceptionname> that would not display enough detail about the error for a user to understand the cause. This has since be altered to check for this occurrence and generate an <exceptionname>AnnotationException</exceptionname> with useful information so that a user can correct any issues.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-648">ANN-648</ulink>: The <methodname>o.h.a.Table.comment</methodname> and <methodname>o.h.a.Table.indexes</methodname> methods would fail when used on secondary tables. To correct this issue the <classname>SecondaryTableSecondPass</classname> class has been updated to use the <classname>XAnnotatedElement</classname> class and the <classname>EntityBinder</classname> class now sets the secondary table as the first for when a join needs to occur.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-637">ANN-637</ulink>: The <methodname>Table.appliesTo</methodname> method would incorrectly select the last table when no matching table to the user query exists. This bug has been fixed by allowing the <varname>hibTable</varname> variable within the <classname>EntityBinder</classname> class to contain a value of null when the correct table cannot be found.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-634">ANN-634</ulink>: The <property>@CollectionOfElements</property> property would clash with the <property>@Fetch JOIN</property>, <property>@Filter</property> and <property>@Where</property> properties within the <classname>CollectionBinder</classname> class. The class has now been updated to test for the instance of a <property>SimpleValue</property> in the <property>@CollectionOfElements</property> property, correcting the issue.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-633">ANN-633</ulink>: The <filename>MANIFEST.MF</filename> file in the <filename>hibernate-annotation</filename> JAR file has been improved to contain vendor and versioning information using the default attributes defined in the JAR file specification.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-621">ANN-621</ulink>: A problem was being caused by the embedded primary key for <classname>ManyToOne</classname> associates containing only transient member variables. This was corrected by adding <property>getter</property> and <property>setter</property> accessors for the respective ID fields and setting both <property>insertable</property> and <property>updatable</property> properties to false.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-619">ANN-619</ulink>: When <classname>@OneToOne</classname> was placed within a composite key, the Hibernate application would generate an <exceptionname>ExceptionInInitializerError</exceptionname>. This has been fixed by recoding how a user application that does not use a true <classname>OneToOne</classname> relationships tested.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-617">ANN-617</ulink>: A <exceptionname>NullPointerException</exceptionname> would occur when a property of a composite ID would be used for ordering. This bug has been fixed by modifying the <classname>CollectionBinder</classname> class to check if the <classname>PersistentClass</classname> is null before checking if it is not an <property>associatedClass</property>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-613">ANN-613</ulink>: A <exceptionname>NullPointerException</exceptionname> would be generated when the <property>mappedBy</property> property was incorrect in a <classname>@OneToOne</classname> mapping. In order to make sure a <exceptionname>NullPointerException</exceptionname> does not occur, when the <property>otherSideProperty</property> parameter contains a null vale within the <classname>OneToOneSecondPass</classname> class, an <exceptionname>AnnotationException</exceptionname> is generated detailing that the <property>mappedBy</property> property is incorrect and where.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-608">ANN-608</ulink>: A bug existed within the <classname>EJB3OverridenAnnotationReader</classname> class where the <classname>annotationsMap</classname> would not be correctly initialized, causing a <exceptionname>NullPointerException</exceptionname> in the <classname>AnnotationConfiguration</classname> class. The issue has been fixed by modifying the <filename>EJB3OverridenAnnotationReader.java</filename> file to remove an internal <classname>Annotation</classname> <code>for</code> loop and replace it with the code <code>annotationsMap = new HashMap<Class, Annotation>( annotations.length + 5 );</code> instead. This change now allows for the <classname>annotationsMap</classname> to be correctly initialized.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-606">ANN-606</ulink>: The <property>@Immutable</property> annotation would not generate a configuration error or warning when used on a subclass. When <property>@Immutable</property> is not used on a root entity, a warning is now generated to inform the user of this incorrect behavior.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-602">ANN-602</ulink>: Any <classname>SecondaryTable</classname> with an <classname>EmbeddedId</classname> or <classname>IdClass</classname> containing a <property>ManyToOne</property> attribute would error. In order to fix this a new <classname>SecondaryTableSecondPass</classname> class has been created and the <classname>AnnotationConfiguration</classname> and <classname>AnnotationBinder</classname> classes have been updated to make use of the new class since associations can be built on joins. Implementing these changes causes the <classname>SecondaryTable</classname> class to behave as a user would expect.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-590">ANN-590</ulink>: An alphabetical ordering issue caused errors when the <property>@ManyToOne</property> and <property>referencedColumnName</property> properties were being used in the <classname>PrimaryKey</classname>. To correct this the <filename>ToOneFkSecondPass.java</filename> file was updated to try using an embedded property for a <classname>persistentClass</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-567">ANN-567</ulink>: No avenue existed to set the <property>collectionPersister</property> property on a <classname>Collection</classname> via Annotations. The functionality to be able to achieve this has now been added for this release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-560">ANN-560</ulink>: Quoting issues existed with the default values in the <classname>NamingStrategy</classname> interface. In order to rectify this, the <filename>Ejb3JoinColumn.java</filename> and <filename>TableBinder.java</filename> files have been updated to quote the result and unquote the source before any other action is taken if the source is quoted.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-559">ANN-559</ulink>: An undefined filter definition would lead to a <exceptionname>NullPointerException</exceptionname> instead of generating a meaningful exception. This has been changed for the release so that this circumstance does not arise, instead a default filter definition is applied if one is undefined.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-556">ANN-556</ulink>: The <property>@OneToOne</property> relationship relied on strict alphabetical ordering that caused the <property>mappedBy</property> property to fail. The <classname>AnnotationBinder</classname> and <classname>AnnotationConfiguration</classname> classes have been updated to make sure that the <classname>OneToManySecondPass</classname> is processed in order.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-555">ANN-555</ulink>: A typo existed within the <classname>Tables</classname> class whereby the interface declaration contained <code>Table[] values();</code> instead of <code>Table[] value();</code>. This small bug has been fixed for this release, allowing the <methodname>Tables.value</methodname> method to function correctly.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-554">ANN-554</ulink>: A <exceptionname>NullPointerException</exceptionname> would be generated when the <property>@Id</property> property was used on a <property>@OneToOne</property> relationship. Correction of this bug has been handled by modifying the <classname>OneToOneSecondPass</classname> class to avoid a <exceptionname>NullPointerException</exceptionname> in this case and instead generate a meaningful <exceptionname>AnnotationException</exceptionname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-553">ANN-553</ulink>: The classpath dependency (<filename>hibernate-validator.jar)</filename> file between Hibernate Annotations and Hibernate Validator has been removed and the <filename>ejb3-persistence.jar</filename> file has become a required dependency.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-552">ANN-552</ulink>: A major new feature for Hibernate Annotations is the transparent event registration and integration for Hibernate Search and Hibernate Validator if they are in the classpath.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-551">ANN-551</ulink>: Columns in a SQL insert query have to be ordered in the same way that Hibernate internally sorts its properties in order for the query to be successful. This was an issue for users as some would use numerous application servers, all of which would order these properties in different ways. The issue has been solved by modifying the <classname>AnnotationBinder</classname> class so that the parameters of a query are ordered internally to the order that Hibernate supports.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-549">ANN-549</ulink>: When an association table is involved in a table join, the key column would be set to null. The correct behavior is to have this key column forced to be not null. This has been achieved by modifying the <classname>MapBinder</classname> class to test if the collection is anything but a <property>OneToMany</property> relationship then the key column should not be null.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-544">ANN-544</ulink>: The <classname>CollectionBinder</classname> class used the <methodname>setCustomSQLDelete</methodname> method when testing if the <methodname>sqlDeleteAll</methodname> method was not null. This would prevent the execution of the <methodname>col.clear</methodname> method on the collection in the case that all the elements are removed. The functionality of <classname>CollectionBinder</classname> has been updated to now use the <methodname>setCustomSQLDeleteAll</methodname> method to ensure correct operation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-542">ANN-542</ulink>: The <property>@Immutable</property> annotation has been added for entities and collections. This has seen the modification of the <classname>CollectionBinder</classname> and <classname>EntityBinder</classname> classes, as well as the addition of the new <classname>Immutable</classname> class.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-535">ANN-535</ulink>: When the <property>@Generated</property> annotation is used, the ability to insert and update a property should be forced. This improvement has been made to Hibernate Annotations through modification of the <classname>PropertyBinder</classname> class.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-532">ANN-532</ulink>: The exception handling of the <property>@UniqueConstraint</property> has been improved for cases when it refers to an incorrect column name. This has been achieved through the modification of the <classname>AnnotationConfiguration</classname> and <classname>Mappings</classname> classes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-529">ANN-529</ulink>: Hibernate used the optional keyword <emphasis>as</emphasis> in the from clause within the <classname>MapBinder</classname> class. This behavior caused Hibernate Annotations to not be compatible with Oracle 10g. The optional keyword is now removed from the from clause and Hibernate Annotations is successfully compatible with Oracle 10g.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-525">ANN-525</ulink>: The <property>@ForeignKey</property> annotation that is used to specify readable names to foreign key constraints could not be applied at the class level and so could not be utilized in providing readable names to constraints between the super and sub classes using the <property>InheritanceType.JOINED</property> property. In this release the <property>@ForeignKey</property> annotation is now supported at the class level for all joined subclasses and is an attribute of the <classname>o.h.a.Table</classname> for secondary tables.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-517">ANN-517</ulink>: The <varname>EntityMode.DOM4J</varname> value would only work when a <filename>.hbm.xml</filename> mapping file is create and could not be used when only Hibernate Annotations was being used in business entities. The <classname>EntityBinder</classname>, <classname>PropertyBinder</classname> and <classname>CollectionBinder</classname> classes have been updated so that they call the <methodname>setNodeName</methodname> method. The error was that this was not being done by the <classname>AnnotationBinder</classname>, causing the <classname>Dom4j</classname> tuplizer to not be instantiated when only Hibernate Annotations was being used.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-516">ANN-516</ulink>: The <property>@OrderBy</property> attribute would be added to the incorrect table when used in an inheritance relationship. Condition testing has been added to the <classname>CollectionBinder</classname> class, ensuring that if the tables <classname>PersistentClass</classname> does not contain a value of <varname>associatedClass</varname>, the tables quoted name is retrieved; otherwise the table is assumed to be empty.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-515">ANN-515</ulink>: Fields were not correctly quoted in a <property>@OneToMany</property> relationship when they were specified, leading to a <exceptionname>SQLGrammarException</exceptionname>. The <filename>Ejb3JoinColumn.java</filename> file has been amended to use the method <methodname>column.getQuotedName</methodname> in the <methodname>linkValueUsingAColumnCopy</methodname> method, instead of <methodname>column.getName</methodname>. </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-509">ANN-509</ulink>: Using a foreign key value for the <property>referecedColumnName</property> value would cause a <exceptionname>MappingException</exceptionname> to occur. The reason for this issue has stemmed through the need for correct ordering of steps and to fix this a <classname>RecoverableException</classname> class has been created which is used to catch the exception and allow the program to perform passes to assist in correcting the issue. If however this is unsuccessful then the loop is exited and the original exception is displayed to the user.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-505">ANN-505</ulink>: Support for the <property>@Tuplizer</property> annotation and interface annotations has been added to Hibernate Annotations. A tupilizer manages a particular representation of a piece of data, given the <property>EntityMode</property> of the representation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-502">ANN-502</ulink>: Integration with Hibernate Validator was not completely possible as it is used in metamodel construction and could not be disabled. In order to allow for this functionality the <property>hibernate.validator.apply_to_ddl</property> has been added and can be set to false to remove Hibernate Validator integration with metamodel construction.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-444">ANN-444</ulink>: In Hibernate Core, the <code><join></code> tag in <filename>.hbm.xml</filename> files contain an attribute called <property>optional</property> that allows for configuration of Hibernate to either use inner joins or outer joins, however this same functionality was not included in Hibernate Annotations. This feature has now been added to Hibernate Annotations through the modification of the <classname>EntityBinder</classname> and <classname>Table</classname> classes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-442">ANN-442</ulink>: Support for more than one generic generator in the <filename>package-info.java</filename> file has been added by adding the new <classname>GenericGenerators</classname> interface, and updating the <classname>AnnotationBinder</classname> to incorporate the use of the new interface.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-434">ANN-434</ulink>: The exception that was generated when attempting to create an entity with an <classname>EmbeddedId</classname> and automatically generated IDs did not give useful information to a user. This has been corrected by modifying the <classname>AnnotationBinder</classname> class to generate an <exceptionname>AnnotationException</exceptionname> that outputs the class name of the component with information explaining that this class must not have <classname>ID</classname> properties when used as an <classname>EmbeddedID</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-252">ANN-252</ulink>: The <classname>AnnotationConfiguration</classname> class would ignore classes that were annotated with an incorrect <property>Entity</property> or contained no annotation. The <classname>AnnotationBinder</classname> class has been updated to log a warning message if any of the mentioned circumstances occurs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-122">ANN-122</ulink>: The <property>@NaturalId</property> annotation that was added to Hibernate previously, has now been added to Hibernate Annotations. This allows for a property to be specified as part of the natural id of an entity.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-104">ANN-104</ulink>: CRUD SQL customization is now allowed on secondary tables within Hibernate Annotations.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-103">ANN-103</ulink>: The ability to specify a fetching strategy for a secondary table has been added to Hibernate Annotations.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-28">ANN-28</ulink>: The <property>@Any</property> and <property>@ManyToAny</property> mapping values have been added as a new feature to Hibernate Annotations. With these features added, it allows for a more robust and diverse database environment.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/ANN-26">ANN-26</ulink>: Support for the ability to exclude a property from the optimistic locking has been added to Hibernate Annotations.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <!-- <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1998">JBPAPP-1998</ulink>: The incorrect exception (<exceptionname>EntityNotFoundException</exceptionname>) was being generated for an optimistic locking failure due to a deleted entity using the <property>hibernate.jdbc.batch_versioned_data=false</property> property and value. To correct this a <emphasis>try and catch</emphasis> test has been added to the <methodname>AbstractEntityManagerImpl.wrapStaleStateException</methodname> method in order to catch the <exceptionname>EntityNotFoundException</exceptionname> exception and display the correct <exceptionname>OptimisticLockException</exceptionname> exception instead.
+ </para>
+ </listitem> -->
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2032">JBPAPP-2032</ulink>: The Hibernate Annotations upgrade that has occurred between the last JBoss Enterprise Application Platform Cumulative Patch and this one may cause backwards-compatibility issues for some users due to the changes introduced to applications that use <classname>SchemaExport</classname> in production. The following instances are circumstances where an issue may arise:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Users who rely on the <classname>hbm2ddl</classname> component of Hibernate Annotations must now check their manually created indexes as there is a high possibility that the order of these will have to change to avoid a performance penalty. An example of this would be that if the index was B, A and Hibernate Annotations now queries based on A, B then the index will not be used.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Users who rely on custom Hibernate CRUD operations are required to manually check if their SQL is up-to-date. An example of when this would be required is if a user has a table with the structure NAME(string), FK1(int), FK2(int) and the FK's point to a table which has overlapping or the same ID set. With this Hibernate Annotations upgrade it is now assumed that the structure is NAME(string), FK2(int), FK1(int). This change will not cause CRUD operations to fail at runtime but the semantics of the update will be incorrect.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <warning>
+ <para>
+ If these concerns are not addressed by affected users then noticeable data consistencies and performance issues may arise. The new configuration parameter <property>hibernate.legacy.foreignkey.use_identity_hashcode_to_compare</property> should also not be utilized as it will restore indeterminate behavior.
+ </para>
+ </warning>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1859">JBPAPP-1859</ulink>: The <classname>ManyToOneJoinTest</classname> distributed with Hibernate would fail because a primary key would be set on a <code>nullable</code> column. The <filename>OneToOneSecondPass.java</filename> file has been modified to use the <methodname>buildJoinFromMappedBySide</methodname> method instead of the <methodname>buildJoin</methodname> method. Enacting this change has meant that the calls to the <methodname>join.createPrimaryKey()</methodname> and <methodname>join.createForeignKey()</methodname> methods within this file have also been removed.
+ </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 using table alias' in an update query causes a program failure. In order to correct this the <filename>QueryTest.java</filename> file has been updated with the removal for the allowance of table alias'.
+ </para>
+ </listitem>
+ <!-- <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1529">JBPAPP-1529</ulink>: The composite primary key of 765 bytes fails within the unit test for Sybase, as it exceeds the maximum index length of 600 bytes. In order to rectify this issue, a hard coded length of 32 bytes is now in place for the compasite primary key ID within the <filename>UserGroup.hbm.xml</filename> file.
+ </para>
+ </listitem> -->
+ <!-- <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1528">JBPAPP-1528</ulink>: When Sybase would convert Java byte into tinyint, failures would arise within tests because of the use of 8 bit values. To correct this the unit tests have been updated to use 7 bit values instead of 8. In order to instigate this correction, the <filename>InterfaceProxyTest.java</filename> and <filename>MixedTest.java</filename> files have been updated.
+ </para>
+ </listitem> -->
+ <!-- <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1527">JBPAPP-1527</ulink>: Limitations of the Sybase ResultSet implementation would cause unit test failures because the data would not be read before closing the ResultSet. The <filename>AggressiveReleaseTest.java</filename>, <filename>CMTTest.java</filename> and <filename>StatsTest.java</filename> files have been updated so that the ResultSet is read correctly for Sybase so that no <exceptionname>NullPointerException</exceptionname> is thrown.
+ </para>
+ </listitem> -->
+ <!-- <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1523">JBPAPP-1523</ulink>: The test supplied for the <methodname>str()</methodname> method is invalid for SQL Server and Sybase as optional parameters for controlling the number of characters for decimal plus decimal values is 0 and the test uses these values by default for SQL Server and Sybase, returning null values. The test has been updated for these dialects so that the values passed are appropriate and do not return null.
+ </para>
+ </listitem> -->
+ <!-- <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1520">JBPAPP-1520</ulink>: The <methodname>FooBarTest.testCollectionsInSelect()</methodname> tests fails for Sybase because implicit support for conversion between <varname>VARCHAR</varname> to <varname>INT</varname>.The files <filename>NativeQueryTest.java</filename> and <filename>FooBar.test</filename> have been updated to correct this issue.
+ </para>
+ </listitem> -->
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Transaction Service (JBossTS)</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1693">JBPAPP-1693</ulink>: The JBoss Transaction Service component of the Enterprise Application Platform has been upgraded to version 4.2.3.SP5.CP05. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1684">JBPAPP-1684</ulink>: A memory leak would be caused in the <classname>BaseTransaction</classname> class because entries in the hash table were never removed, even if a thread was no longer in use. This meant that client transactions could have leaked approximately 600 bytes. To correct this bug, the <filename>BaseTransaction.java</filename> file has been updated to replace the hash table with a <varname>ThreadLocal</varname> implementation which takes an integer as input. In order to allow for the timeout values to work correctly, they now only call the required methods of <methodname>_timeouts.set</methodname> and <methodname>_timeouts.get</methodname>. With these improvements made, the memory leak no longer occurs.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Security Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2067">JBPAPP-2067</ulink>: The release of Tomcat 6.0.20 saw a set of security vulnerabilities fixed that have now been backported to JBoss Web. These vulnerabilities are:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0033">CVE-2009-0033</ulink>: For Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when the <filename>Java AJP</filename> connector and <filename>mod_jk</filename> load balancing were used it would allow for remote attackers to cause a denial of service (application outage) attack via a crafted request with invalid headers. This would occur in relation to the temporary blocking of connectors that had encountered errors, as demonstrated by an error involving a malformed <filename>HTTP Host</filename> header. This update has been rated as having important security impact by the Red Hat Security Response Team.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5515">CVE-2008-5515</ulink>: Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, 6.0.0 through 6.0.18, and possibly earlier versions normalized the target pathname before filtering the query string when using the <methodname>RequestDispatcher</methodname> method, which allowed remote attackers to bypass intended access restrictions and conduct directory traversal attacks via <code>..</code> (dot dot) sequences and the <filename>WEB-INF</filename> directory in a <classname>Request</classname>. This update has been rated as having important security impact by the Red
+ Hat Security Response Team.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0783">CVE-2009-0783</ulink>: Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18 would permit web applications to replace an XML parser used for other web applications. This would allow local users to read or modify the <filename>web.xml</filename>, <filename>context.xml</filename>, or <filename>tld</filename> files of arbitrary web applications via a crafted application that is loaded earlier than the target application. This update has been rated as having low security impact by the Red Hat Security Response Team.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0781">CVE-2009-0781</ulink>: A Cross-site scripting (XSS) vulnerability existed within the <filename>jsp/cal/cal2.jsp</filename> calendar examples web application for Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18. This vulnerability would allow remote attackers to inject arbitrary web script or HTML via the time parameter, related to <emphasis>invalid HTML</emphasis>. This update has been rated as having low security impact by the Red Hat Security Response Team.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0580">CVE-2009-0580</ulink>: For Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when <property>FORM</property> authentication was used, this would allow remote attackers to enumerate valid usernames via requests to <filename>/j_security_check</filename>. This would be achieved with malformed URL encoding of passwords, related to improper error checking in the <classname>MemoryRealm</classname>, <classname>DataSourceRealm</classname>, and <classname>JDBCRealm</classname> authentication realms, as demonstrated by a <code>%</code> (percent) value for the <property>j_password</property> parameter. This update has been rated as having low security impact by the Red Hat Security Response Team.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ These bug fixes are part of the JBoss Web 2.0.0.CP10 upgrade.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Documentation</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1782">JBPAPP-1782</ulink>: Chapter 7.2 named <emphasis>Adjusting memory settings</emphasis> within the <filename>Installation Guide</filename>, stated that a user should modify the <filename>run.conf</filename> file in order to increase the available memory to the program. This however is incorrect when running the JBoss Enterprise Application Platform on a Windows operating system. In this case the <filename>run.bat</filename> file should be modified and the documentation now reflects this difference.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1768">JBPAPP-1768</ulink>: On page 37 of the PDF for the <filename>Hibernate Annotations Reference Guide</filename> book an example would overflow the allowed area because of the way in which the software to build the PDF deals with names that contain full stops without spaces. In order to rectify the overflow problem without invalidating the code that a user could copy and paste into a command line window, the file name has been broken with the escape character <code>\</code> used to escape a hard return.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1689">JBPAPP-1689</ulink>: The <filename>Server Configuration Guide</filename>, section 16.5 contained an error regarding the name of the directory where JBoss Web is deployed. Instead of the path to the <filename>jboss-service.xml</filename> file being <filename>JBOSS_HOME/server/all/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xml</filename> it should be <filename>JBOSS_HOME/server/all/deploy/jboss-web.deployer/META-INF/jboss-service.xml</filename>. For this CP release, the file path has been corrected.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1584">JBPAPP-1584</ulink>: Information about the <classname>LdapExtLoginModule</classname> was missing from the documentation on login modules within the <filename>Server Configuration Guide</filename>. The information about this module has now been added to the <emphasis>Using JBoss Login Modules</emphasis> section of the guide.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Core Server</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1976">JBPAPP-1976</ulink>: The <classname>HASingletonElectionPolicySimple</classname> class of the Clustering component retrieved the current view from the <classname>HAPartition</classname> and formulated a decision based on that information that ignored the possibility that the service being managed may not be running on all cluster members. To fix this issue the <classname>ExtendedElectionPolicySimple</classname> class has been created and when used it fixes not only the above issue but also an issue where using the <code>kill -9</code> command was necessary to start singletons on other nodes. This new class extends the election policy and provides helper methods for stable implementations.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1932">JBPAPP-1932</ulink>: Java 1.4 based clients would not function when trying to use the Java remote method invocation interface over the Internet Inter-Orb Protocol (RMI-IIOP). This occurred because sections of placeholder code (which allow the program to function correctly) were needed, however these sections of code were compiled with Java 1.5 without compatibility for version 1.4. In order to correct this bug, the <filename>iiop/build.xml</filename> file has been updated with the removal of:
+ </para>
+<programlisting>
+<javac destdir="${build.classes}/main"
+ optimize="${javac.optimize}"
+ target="${javac.target}"
+ source="${javac.source}"
+</programlisting>
+ <para>
+ and replaced with:
+ </para>
+<programlisting>
+<javac destdir="${build.classes}/main"
+ optimize="${javac.optimize}"
+ target="1.4"
+ source="1.4"
+</programlisting>
+ <para>
+ forcing the <filename>build.xml</filename> file to use Java 1.4.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1685">JBPAPP-1685</ulink>: Apache-slide has been upgraded to version 2.1.jdk15-brew. In this change is the renaming of <filename>jakarta-slide-webdavlib.jar</filename> to <filename>webdavlib.jar</filename> and the <filename>commons-httpclient.jar</filename> has been removed from the distribution because it was dependant on an excluded <filename>commons-codec.jar</filename>. Removal of the <filename>commons-httpclient.jar</filename> file does not impact correct functioning of the JBoss Enterprise Application Platform.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1100">JBPAPP-1100</ulink>: <filename>hsqldb</filename> has been upgraded to version 1.8.0.8.patch02-brew. In this change is a change to the <filename>MANIFEST.MF</filename> file. In previous releases the version information was displayed as a timestamp, an example would be:
+ </para>
+<screen>
+private-2007/12/18-11:59:06
+</screen>
+ <para>
+ This release correctly shows the version of <filename>hsqldb</filename> correctly within the <filename>MANIFEST.MF</filename> file as:
+ </para>
+<screen>
+1.8.0.8.patch02
+</screen> </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ </section>
+ <section id="Known_Issues_with_this_release">
+ <title>
+ Known Issues with this release
+ </title>
+ <para>
+ Following is a list of known issues at the time of release.
+ </para>
+ <formalpara>
+ <title>General Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1774">JBPAPP-1774</ulink>: The JBoss Enterprise Application Platform RPM cannot be installed with only the OpenJDK distribution.
+ </para>
+ </listitem>
+ <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 documented issue is automatically generated as a footnote and places a number beside that of the documented issue, 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-1709">JBPAPP-1709</ulink>: The JPA spec defines the constant with a value that has a typo in the class name:
+ </para>
+<programlisting>
+javax.persistence.Persistence.PERSISTENCE_PROVIDER = "javax.persistence.spi.PeristenceProvider"
+</programlisting>
+ <para>
+ The version of <filename>ejb3-persistence.jar</filename> released in EAP is non-compliant with the JPA spec because it sets the correct classname (without the typo) for this constant.
+ </para>
+ <para>
+ Javadoc for <methodname>javax.persistence.Query.getSingleResult()</methodname> says that the <exceptionname>EntityNotFoundException</exceptionname> will be generated if there is no result. The Javadoc should have mentioned the <exceptionname>NoResultException</exceptionname> instead.
+ </para>
+ </listitem>
+ <!-- <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 attaining 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 reformatted 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-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>
+ 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 persists a string containing 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-1068">JBPAPP-1068</ulink>: When using Microsoft SQL and <code>@Type(type="text")</code> in creating a table, the field is correctly created as <varname>text</varname> however when a delete operation 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 <varname>text</varname> and <varname>varchar</varname> 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 millisecond 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 containing 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 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>
+ </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