[jboss-cvs] JBossAS SVN: r105699 - projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Jun 4 01:02:35 EDT 2010
Author: rebecca_newton
Date: 2010-06-04 01:02:34 -0400 (Fri, 04 Jun 2010)
New Revision: 105699
Added:
projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP09.ent
projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP09.xml
Removed:
projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP08.ent
projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP08.xml
Modified:
projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Book_Info.xml
Log:
Updating package for push to brew
Modified: projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Book_Info.xml 2010-06-04 04:59:21 UTC (rev 105698)
+++ projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Book_Info.xml 2010-06-04 05:02:34 UTC (rev 105699)
@@ -3,7 +3,7 @@
]>
<articleinfo>
- <title>Release Notes CP08</title>
+ <title>Release Notes CP09</title>
<subtitle>for Use with JBoss Enterprise Application Platform 4.2 Cumulative Patch 8</subtitle>
<edition>1.0</edition>
<pubsnumber>6</pubsnumber>
Deleted: projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP08.ent
===================================================================
--- projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP08.ent 2010-06-04 04:59:21 UTC (rev 105698)
+++ projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP08.ent 2010-06-04 05:02:34 UTC (rev 105699)
@@ -1,3 +0,0 @@
-<!ENTITY HOLDER "Red Hat, Inc">
-<!ENTITY YEAR "2009">
-<!ENTITY VERSION "4.2">
Deleted: projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP08.xml
===================================================================
--- projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP08.xml 2010-06-04 04:59:21 UTC (rev 105698)
+++ projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP08.xml 2010-06-04 05:02:34 UTC (rev 105699)
@@ -1,1017 +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.2 that can be found in this Cumulative Patch release.
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- JBoss Application Server 4.2.z
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Microcontainer 1.0.2
- </para>
- </listitem>
- <listitem>
- <para>
- Hibernate Core 3.2.4.SP1_CP09
- </para>
- </listitem>
- <listitem>
- <para>
- Hibernate Annotations 3.3.1.GA_CP02
- </para>
- </listitem>
- <listitem>
- <para>
- Hibernate Entity Manager 3.3.2.GA_CP01
- </para>
- </listitem>
- <listitem>
- <para>
- Hibernate Validator 3.0.0.GA
- </para>
- </listitem>
- <listitem>
- <para>
- Apache Xalan 2.7.0.patch02
- </para>
- </listitem>
- <listitem>
- <para>
- JacORB 2.3.0jboss.patch7
- </para>
- </listitem>
- <listitem>
- <para>
- JAF 1.1.0
- </para>
- </listitem>
- <listitem>
- <para>
- JavaServer Faces 1.2_13
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss AOP 1.5.5.GA_CP04
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Cache 1.4.1.SP13
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss JAXR 1.2.0.SP2
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Remoting 2.2.3.SP1
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Serialization 1.0.3.GA
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Transactions 4.2.3.SP5_CP07
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss XB 1.0.0.SP3
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Web 2.0.0.GA_CP12
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Web Services 1.2.1.GA_CP05
- </para>
- </listitem>
- <listitem>
- <para>
- JGroups 2.4.7.GA
- </para>
- </listitem>
- <listitem>
- <para>
- Seam 1.2.1.GA
- </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.CP07</title>
- <formalpara>
- <title>Using CSP/JON</title>
- <para>
- <orderedlist>
- <title>Installing a Cumulative Patch</title>
- <listitem>
- <para>
- Use <guibutton>Browse Resources</guibutton> to navigate to the resource you wish to patch.
- </para>
- </listitem>
- <listitem>
- <para>
- Click on the <guibutton>Software</guibutton> tab. All patches applicable to your resource and all patches that have been previously installed by JON on this resource will be displayed.
- </para>
- </listitem>
- <listitem>
- <para>
- An <guibutton>Install</guibutton> link will be listed beside all patches that can be installed by JON. Any patches without this link must be installed manually. Any patch that appears beside a <guibutton>Manually Uninstall</guibutton> link must be uninstalled manually before the new patch can be installed.
- </para>
- <para>
- For more information about installing a patch with CSP/JON, see the <ulink url="http://jon01.qa.atl2.redhat.com:8080/display/DOC/Installing+a+Patch">JON documentation</ulink>.
- </para>
- </listitem>
- </orderedlist>
- </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-CP08.zip"> ftp://ftp.redhat.com/pub/redhat/jbeap/4.2.0/en/source/jboss-eap-src-4.2.0-CP08.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 <filename>index.html</filename> 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>Security</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2872">JBPAPP-2872</ulink>: Twiddle logged all command line arguments, including the JMX password, to <filename>twiddle.log</filename>, which has public read permissions, and is created in the current working directory. The password is now masked in the log, removing the risk to security. This issue has been assigned CVE-2009-3554.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2312">JBPAPP-2312</ulink>: A new <classname>PrincipalSessionAttributeFilter</classname> has been created to include the principal session as an attribute of the HTTP Session. This attribute is checked upon session expiry and the authenticated cache will be flushed if found. In order to use this filter, uncomment the filter in Tomcat's <filename>web.xml</filename>.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Application Server</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2905">JBPAPP-2905</ulink>: The <varname>ScanPeriod</varname> in the <literal>production</literal> configuration is set to sixty seconds. If the deployment scanner thread was sleeping when shutdown was initiated, shutdown waited for the length of the deployment scanner's sleep time. The deployment scanner thread is now stopped when shutdown is initiated, and the wait no longer occurs.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2764">JBPAPP-2764</ulink>: <classname>LoadMgr3</classname> logged a failure to load a class as an error, but in certain situations this should be regarded as correct. The <literal>ERROR</literal> message has been downgraded to a <literal>WARNING</literal>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2578">JBPAPP-2578</ulink>: Configuration information for the JBoss Messaging service in <filename>sample-bindings.xml</filename> has been updated to make use of new settings.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>Clustering</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2854">JBPAPP-2854</ulink>: When multiple nodes were started concurrently, an address mismatch would occur between cluster members and message senders. This caused inconsistent internal state in <literal>NAKACK</literal>, which would log errors similar to the following:
- </para>
- <programlisting>
-WARN [org.jgroups.protocols.pbcast.NAKACK]
- (IncomingPacketHandler (channel=Tomcat-DefaultPartition):)
- node2:1234] discarded message from non-member node3:1234,
- my view is [node1:1234|2] [node1:1234, node2:1234, node3:1234]
-
-ERROR [org.jgroups.protocols.pbcast.NAKACK] (Timer-3:)
- sender node3:1234 not found in received_msgs
- </programlisting>
- <para>
- This mismatch has been corrected and the errors no longer present.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Web</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2039">JBPAPP-2039</ulink>: The fix for <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1992">JBPAPP-1992</ulink> means that Version 1 cookies are used in JBoss Web instead of Version 0. This older version is linked to a security issue, described in <ulink url="https://www.redhat.com/security/data/cve/CVE-2007-5333.html">CVE-2007-5333</ulink>. To return to the previous behavior despite this, add a <filename>conf/catalina.properties</filename> file and set the following property in it:
- </para>
- <programlisting>
-org.apache.tomcat.util.http.ServerCookie.VERSION_SWITCH=false
- </programlisting>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Seam</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2967">JBPAPP-2967</ulink>: A shared value binding returned a <literal>null</literal> value when under load, which caused a <exceptionname>javax.el.PropertyNotFoundException</exceptionname>. The value binding is no longer shared and the issue no longer presents.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>EJB3</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2782">JBPAPP-2782</ulink>: When EJB3 entities were used with optimistic caching, the <methodname>newerThan</methodname> method would incorrectly return <literal>true</literal> for <code>A.newerThan ( A )</code>. This caused a <exceptionname>DataVersioningException</exceptionname> when attempting to remove the entry from the cache. The EJB3 entity cache service is now configured to use pessimistic caching to avoid this issue.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Hibernate</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3060">JBPAPP-3060</ulink>: <literal>@JoinColumn</literal> mapping assumed that the column definition was void even if it was also defined by <literal>@ManyToOne</literal>. <filename>Ejb3JoinColumn.java</filename> has been updated so that defined column properties like <varname>length</varname>, <varname>precision</varname> and <varname>scale</varname> are observed in <literal>@JoinColumn</literal> mapping.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3052">JBPAPP-3052</ulink>: When <classname>org.hibernate.id.enhanced.SequenceStyleGenerator</classname> generates identifiers, the select script generated is as follows:
- </para>
- <programlisting>
-select next_val id_val from hibernate_sequence for update
- </programlisting>
- <para>
- However, in PostgreSQL, <literal>as</literal> is required between <literal>next_val</literal> and <literal>id_val</literal>. See <ulink url="http://sql-info.de/en/postgresql/postgres-gotchas.html#1_1">http://sql-info.de/en/postgresql/postgres-gotchas.html#1_1</ulink> for further details.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3038">JBPAPP-3038</ulink>: Hibernate Core has been upgraded to version 3.2.4.SP1.CP09. Hibernate Annotations has been upgraded to version 3.3.1.GA.CP02. Hibernate Entity Manager has been upgraded to version 3.3.2.GA.CP01.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2900">JBPAPP-2900</ulink>: MySQL uses the <literal>TEMPORARY</literal> keyword to bypass implicit transaction commits. Previously, Hibernate used <literal><CREATE TEMPORARY TABLE></literal> with <literal><DROP TABLE></literal>. Omitting the <literal>TEMPORARY</literal> keyword caused an implicit commit, and immediate failure within an XA Transaction. <literal><DROP TEMPORARY TABLE></literal> is now supported and this issue no longer presents.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2049">JBPAPP-2049</ulink>: the HQL translator attempted to render <literal>IS NULL</literal> and <literal>IS NOT NULL</literal> checks against a component by using tuple syntax. Exploded syntax is now used instead, to make SQL more readable.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1998">JBPAPP-1998</ulink>: <exceptionname>EntityNotFoundException</exceptionname> is incorrectly thrown upon an optimistic locking failure when one <literal>EntityManager</literal> tries to delete an entity that has been updated by a different <literal>EntityManager</literal> and <varname>hibernate.jdbc.batch_versioned_data</varname> is set to <literal>false</literal> (the default value). <exceptionname>OptimisticLockException</exceptionname>, the correct exception for this situation, is now thrown instead.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1547">JBPAPP-1547</ulink>: By default, Sybase ASE 15 string comparisons are case-insensitive. The <methodname>org.hibernate.dialect.SybaseASE15Dialect.areStringComparisonsCaseInsensitive()</methodname> method now returns <literal>true</literal>.
- </para>
- <para>
- If the Sybase database is configured to perform case-sensitive operations, this setting will be incorrect. However, since Hibernate only uses this method for unit tests, this change has no effect on Hibernate's internal processing.
- </para>
- </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="https://jira.jboss.org/jira/browse/JBPAPP-3145">JBPAPP-3145</ulink>: The <filename>wsrunclient.sh</filename> scripts are missing a library and fail with a <exceptionname>ClassNotFoundException</exceptionname>. To work around this issue on Linux, execute the following statements before executing <filename>wsrunclient.sh</filename>:
- </para>
- <programlisting><![CDATA[
-export JBOSS_HOME=<path to your JBoss EAP installation>
-WSRUNCLIENT_CLASSPATH="$JBOSS_HOME/client/wsdl4j.jar"
-export WSRUNCLIENT_CLASSPATH
- ]]></programlisting>
- <para>
- To work around this issue on Windows, execute the following before executing <filename>wsrunclient.bat</filename>:
- </para>
- <programlisting><![CDATA[
-set JBOSS_HOME=<path to your JBoss EAP installation>
-set WSRUNCLIENT_CLASSPATH=%JBOSS_HOME%/client/wsdl4j.jar
- ]]></programlisting>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3143">JBPAPP-3143</ulink>: The <filename>wsprovide.sh</filename> and <filename>wsprovide.bat</filename> scripts fail when generating a WSDL file from the examples. To work around this issue on Linux, execute the following statements before running <filename>wsprovide.sh</filename>:
- </para>
- <programlisting><![CDATA[
-export JBOSS_HOME=<path to your JBoss EAP installation>
-WSPROVIDE_CLASSPATH="$JBOSS_HOME/client/jaxb-xjc.jar"
-WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jboss-ejb3x.jar"
-WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/wsdl4j.jar"
-export WSPROVIDE_CLASSPATH
- ]]></programlisting>
- <para>
- To work around this issue on Windows, execute the following statements before running <filename>wsprovide.bat</filename>:
- </para>
- <programlisting><![CDATA[
-set JBOSS_HOME=<path to your JBoss EAP installation>
-set WSPROVIDE_CLASSPATH=%JBOSS_HOME%/client/jaxb-xjc.jar
-set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/jboss-ejb3x.jar
-set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/wsdl4j.jar
- ]]></programlisting>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3117">JBPAPP-3117</ulink>: If an incorrect <varname>mcast_addr</varname> value is set, users are pointed to an outdated URL for information about cross talking. If you experience problems with <varname>mcast_addr</varname> and cross talking, the updated URL for further information is <ulink url="https://www.jboss.org/community/docs/DOC-9469">https://www.jboss.org/community/docs/DOC-9469</ulink>.
- </para>
- </listitem>
- <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="https://jira.jboss.org/jira/browse/JBPAPP-3105">JBPAPP-3105</ulink>: The number of elements that can be included in a single <methodname>IN</methodname> expression is limited to a certain number (for Oracle, 1000). If an Array or Collection is passed into the <methodname>IN</methodname> method, Oracle throws an error stating that the <methodname>IN</methodname> clause must contain at most 1000 items. This affects both HQL and Criteria API. To work around this issue, users should split large arrays and collections into sub-arrays or sub-collections. If 'in', use the form <code>in(1,2,...,1000) or in(1001+)</code>; if 'not in', use the form <code>not(1,2,...,1000) or in(1001+)</code>, as described in the JIRA.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3098">JBPAPP-3098</ulink>: When a filter with a <varname>collection-type</varname> parameter is used, and the number of parameters in that collection changes during the lifetime of the <classname>SessionFactory</classname>, the SQL is not updated to reflect the change in the number of parameters. This typically results in the following error:
- </para>
- <programlisting>
-java.sql.SQLException: Parameter index out of bounds. 2 is not between valid values of 1 and 1
- </programlisting>
- <para>
- This occurs only with HQL, not Criteria. There is currently no workaround, but the fix has been applied in the Hibernate Cumulative Patch branch and will be included in the next Cumulative Patch release.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3089">JBPAPP-3089</ulink>: A long <literal>IN</literal> list can cause a stack overflow error during parsing. A query element like:
- </para>
- <programlisting>
-where x in (:x)
- </programlisting>
- <para>
- or a manually constructed:
- </para>
- <programlisting>
-where x in (1,2,3,...)
- </programlisting>
- <para>
- can generate a stack overflow if the number of elements referenced by <literal>x</literal> exceeds a certain number which depends upon the amount of available stack space. For many Java Virtual Machines, the limit is between 9000 and 10000, assuming a relatively empty stack at the point of query execution. To work around this issue, users should split large numbers of elements into sub-groups. If 'in', use the form <code>in(1,2,...,1000) or in(1001+)</code>; if 'not in', use the form <code>not(1,2,...,1000) or in(1001+)</code>, as described in the JIRA.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3075">JBPAPP-3075</ulink>: If a database reserved keyword is used as a property name with a Hibernate Validator annotation (for example, <literal>@Min</literal> or <literal>@Max</literal>), it will cause exceptions in <literal>SchemaExport</literal>, even if you specify a column name. This is because Hibernate ignores the name specified. The workaround is to map the property name to another that is not a database reserved keyword with <literal>@Column</literal> annotation. The fix for this issue is expected in Hibernate 4.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3069">JBPAPP-3069</ulink>: The <literal>QueryByExampleTest.testJunctionNotExpressionQBE</literal> test fails in Sybase because <varname>ansinull</varname> is set to <literal>off</literal> by default. This test builds a disjunction predicate such as <code>( OR^ (ex) (NOT ex) )</code>. This should match everything in the database, but because ANSI SQL evaluates all comparisons involving <literal>NULL</literal> values as <literal>UNKNOWN</literal>, not all matches are returned.
- </para>
- <para>
- To work around this issue, append this string to the JDBC URL:
- </para>
- <programlisting>
-?SQLINITSTRING=set ansinull on
- </programlisting>
- <para>
- If this is not possible, an alternative is to execute the following Java code (or similar) after getting a Hibernate Session, <literal>s</literal>.
- </para>
- <programlisting role="JAVA">
-s.connection().createStatement().execute("set ansinull on");
- </programlisting>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3068">JBPAPP-3068</ulink>: Mapping an Enum as <literal>@Id</literal> on MySQL causes a <exceptionname>SchemaExport</exceptionname> exception with error messages similar to the following:
- </para>
- <programlisting>
-Unsuccessful: create table PlanetCheatSheet (planet tinyblob
-not null,mass double precision not null, numberOfInhabitants
-bigint not null, radius double precision not null, primary
-key (planet)) ENGINE=InnoDB
-BLOB/TEXT column 'planet' used in key specification without
-a key length
- </programlisting>
- <para>
- Currently, Hibernate binds the <varname>id</varname> property of an Enum type as a <literal>tinyBlob</literal> (on MySQL) without a <varname>length</varname> property. The workaround for this issue is currently to write your own DDL if your Enum property must be mapped as <literal>@Id</literal>
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3056">JBPAPP-3056</ulink>: The Hibernate test <literal>org.hibernate.test.hql.ASTParserLoadingTest.java</literal> fails on DB2 with an SQL Error because of invalid use of a parameter marker. This occurs because DB2 does not support untyped parameters. To work around this issue, modify your queries so that the parameters are cast to an appropriate data type.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2945">JBPAPP-2945</ulink>: The Hibernate test <filename>org.hibernate.test.annotations.query.QueryAndSQLTest.java</filename> fails on PostgreSQL 8.3.7 with the following log messages:
- </para>
- <screen>
-Caused by: org.postgresql.util.PSQLException: Method org.postgresql.jdbc3.Jdbc3PreparedStatement.setQueryTimeout(int) is not yet implemented.
- </screen>
- <para>
- This occurs because PostgreSQL JDBC driver does not support the <methodname>Statement.setQueryTimeout</methodname> method.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2839">JBPAPP-2839</ulink>: Failing to re-inject the interceptors for instrumented entities causes <exceptionname>NullPointerException</exceptionname>s when entities are retrieved from a deserialized <literal>PersistenceContext</literal>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2440">JBPAPP-2440</ulink>: When a cache provider cannot be found, a <errorname>NoClassDefFoundError</errorname> is thrown with the message:
- </para>
- <programlisting>net/sf/ehcache/CacheException</programlisting>
- <para>
- When a connection provider cannot be found, a <exceptionname>HibernateException</exceptionname> is thrown with the following message:
- </para>
- <programlisting>Could not instantiate connection provider: " + providerClass</programlisting>
- <para>
- If you experience these errors, we suggest checking the cache or connection provider configuration to ensure that the provider is included in the classpath.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2316">JBPAPP-2316</ulink>: Hibernate does not currently provide property types that enable applications to process data in a long string or binary column as a Java String. This feature is expected in JBoss Enterprise Application Platform 5.1.0.GA.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2315">JBPAPP-2315</ulink>: Hibernate does not currently provide property types that enable applications to process data in a <literal>java.sql.Types.LONGVARCHAR</literal> or <literal>java.sql.Types.CLOB</literal> column as a Java String. Processing of a <literal>java.sql.Types.LONGVARBINARY</literal> or <literal>java.sql.Types.BLOB</literal> as a Java <literal>byte[]</literal> is also unavailable. These features are expected in JBoss Enterprise Application Platform 5.1.0.GA.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1722">JBPAPP-1722</ulink>: Sybase fails to insert a new entity if the entity overflows the column. However, it does not throw an exception, so Hibernate cannot tell that the insert has failed. To work around this issue, your application must validate entity properties to ensure that the value will not overflow the underlying column.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1709">JBPAPP-1709</ulink>: The version of <filename>ejb3-persistence.jar</filename> shipped with the current version of JBoss Enterprise Application Platform 4.x is incorrect. Hibernate Entity Manager currently ships <filename>ejb3-persistence.jar</filename> 1.0.0.GA, but it should use <filename>ejb3-persistence.jar</filename> 1.0.1.GA.
- </para>
- <para>
- There are two changes between the 1.0.0.GA and 1.0.1.GA versions of the JAR:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- The JPA specification defines the constant with a value that has a typo in the classname:
- </para>
- <programlisting>javax.persistence.Persistence.PERSISTENCE_PROVIDER = "javax.persistence.spi.PeristenceProvider"</programlisting>
- <para>
- Because the JAR inluded in the JBoss Enterprise Application Platform does not include this typo, it is not compliant with the JPA specification. See <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-321">http://opensource.atlassian.com/projects/hibernate/browse/EJB-321</ulink> for details.
- </para>
- </listitem>
- <listitem>
- <para>
- The Javadoc for <methodname>javax.persistence.Query.getSingleResult()</methodname> states that <exceptionname>EntityNotFoundException</exceptionname> will be thrown if there is no result. It should say <exceptionname>NoResultException</exceptionname>.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1613">JBPAPP-1613</ulink>: Null values for columns mapped as Boolean in Sybase are persisted as <literal>0</literal> instead of <literal>null</literal>. The current workaround for this issue is to map these values as <literal>type="org.hibernate.test.where.NumericTrueFalseType"</literal> instead of <literal>type="boolean"</literal>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1555">JBPAPP-1555</ulink>: Sybase uses <literal>image</literal> and <literal>text</literal> instead of <literal>Blob</literal> and <literal>Clob</literal>, so there is no support for <literal>Blob</literal> and <literal>Clob</literal> on Sybase. This feature is expected in JBoss Enterprise Application Platform 5.1.0.GA. Currently, user-defined types can be created to process Sybase <literal>text</literal> and <literal>image</literal> properties.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1554">JBPAPP-1554</ulink>: Sybase only allows only one entry (for example, column name or '*') in a subquery select list. The HQL function, <methodname>elements()</methodname>, fails when the collection elements have a composite ID, because the generated SQL contains a subquery select list with multiple entries. The workaround is to avoid using HQL <methodname>elements()</methodname> if the elements have a composite key. Instead, reformulate the HQL so that no subquery has multiple entries in its select list.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1551">JBPAPP-1551</ulink>: Embedded classes are not considered when batch insert statements are ordered. There are two possible workarounds for this issue:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Leave <varname>ORDER_INSERTS</varname> at the default value (<literal>FALSE</literal>) when embedded classes are used.
- </para>
- </listitem>
- <listitem>
- <para>
- Explicitly call <methodname>session.save()</methodname> on child objects to enforce their SQL insertion orders.
- </para>
- </listitem>
- </itemizedlist>
- </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="https://jira.jboss.org/jira/browse/JBPAPP-1545">JBPAPP-1545</ulink>: On Sybase, when a query has an ANSI join with three or more joins, and one join involves a union subclass, the query may fail with <exceptionname>SybSQLException</exceptionname> because a column is not within the scope of the joined table expression. The current recommendation is to avoid using join fetches that involve union subclasses.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1328">JBPAPP-1328</ulink>: When attempting to perform a delete or update statement with a subselect, the generated SQL will refer to an unknown table alias and cause the query to fail.
- </para>
- <para>
- Currently the workaround is to reverse the conditions in the <literal>where</literal> clause.
- </para>
- <para>Incorrect:</para>
- <programlisting>update Person set name = ?1 where id in (select c.id from Customer c) and name <> ?2</programlisting>
- <para>Correct:</para>
- <programlisting>update Person set name = ?1 where name <> ?2 and id in (select c.id from Customer c)</programlisting>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1230">JBPAPP-1230</ulink>: When a <literal>DetachedCriteria</literal> is used as a subquery, the generated SQL contains a column alias in the subquery. On Sybase, a <exceptionname>SybSQLException</exceptionname> is thrown because Sybase does not allow column aliases in subqueries. The workaround for this issue is to use an HQL query instead of a <literal>DetachedCriteria</literal> in a subquery.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1229">JBPAPP-1229</ulink>: On Sybase, the text <literal>current_timestamp</literal> is not being recognised as a method mode by the translator. Only SQL function calls with parentheses are recognized as method modes. There is no workaround for this issue except to avoid relying upon function replacement for <literal>current_timestamp</literal>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1123">JBPAPP-1123</ulink>: When <literal>@OrderBy</literal> is used on joined classes (using a join table), the generated SQL is invalid on MySQL, PostgreSQL, Oracle, and MSSQL because the "order by" clause qualifies the columns using the actual table name. The "order by" clause should use the table alias instead.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1082">JBPAPP-1082</ulink>: When a <varname>char</varname> property is used and it is not initialized, then Hibernate initializes it to <literal>0</literal> and persists a string containing the character <literal>\u0000</literal>. PostgreSQL throws an exception because it does not allow character <literal>\u0000</literal> embedded in a string. An email thread describing this problem is available from:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- http://markmail.org/message/jvzlzxw6ui2rcsmv#query:\u0000%20postgresql+page:1+mid:gpu34f4iwanbyjqh+state:results
- </para>
- </listitem>
- </itemizedlist>
- <para>
- There is currently no workaround for persisting <literal>\u0000</literal> in a <varname>char</varname> column using PostgreSQL.
- </para>
- <para>
- If the user intends to persist a NULL for an uninitialized char property instead of <literal>\u0000</literal>, then <varname>java.lang.Character</varname> should be used instead of the primitive <varname>char</varname> type. This avoids the exception when the property is initialized. Attempting to persist a <varname>java.lang.Character</varname> property that is set to <literal>\u0000</literal> still results in an exception.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1075">JBPAPP-1075</ulink>: <literal>SchemaExport</literal> fails on Oracle and Sybase when a redundant <code>@Column( unique = true )</code> or <code>@UniqueConstraint( columnNames = { ... } )</code> annotation is used for a column that is implicitly defined as unique by the declared model. The workaround is to remove the redundant <code>@Column</code> annotation.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1071">JBPAPP-1071</ulink>: In some cases, when there are foreign key constraints defined on columns in a primary key, <literal>SchemaExport</literal> incorrectly declares them as nullable when it generates <code>CREATE TABLE</code> statements. This fails on MSSQL, DB2, and Sybase because those databases require primary key columns to be non-nullable.
- </para>
- <para>
- The workaround for this issue is to explicitly indicate which columns should be non-nullable, such as:
- </para>
- <itemizedlist>
- <listitem><para>Add <code>nullable=false</code> to <literal>@JoinColumn</literal></para></listitem>
- <listitem><para>Add <code>optional=false</code> to <literal>@ManyToOne</literal></para></listitem>
- <listitem><para>Add an <literal>@AttributeOverride</literal> with <code>@Column(name="mapkey", nullable=false)</code> in case of a <literal>@CollectionOfElements</literal> using a Map</para></listitem>
- <listitem><para>Add <code>nullable=false</code> in <literal>@Column</literal> when inside a <literal>@CollectionId</literal> or inside <literal>@MapKey</literal></para></listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>
- <ulink url="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 <literal>TIME</literal> and <literal>TIMESTAMP</literal>.
- </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-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-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>
- <formalpara>
- <title>Documentation</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2809">JBPAPP-2809</ulink>: The <citetitle>Server Configuration Guide CP08</citetitle> contained in the packaged documentation bundle contains an error. In Section 5.5.1, <emphasis>JNDI Binding Manager</emphasis>, the first code example contains an incorrect line:
- </para>
- <programlisting>
- xmlns:jndi="urn:jboss:jndi-binding-service:10"
- </programlisting>
- <para>
- This line should be:
- </para>
- <programlisting>
- xmlns:jndi="urn:jboss:jndi-binding-service:1.0"
- </programlisting>
- <para>
- This has been corrected in the online documentation, available 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>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>Seam Known Issues</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3138">JBPAPP-3138</ulink>: Several BlogTest unit test methods (<methodname>test.BlogTest.testEntry()</methodname> and <methodname>test.BlogTest.testLatest()</methodname>) fail on all platforms. In addition, <methodname>test.BlogTest.testSearch()</methodname> fails on certain platforms. For further information, see the console output in the JIRA.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3176">JBPAPP-3176</ulink>: The <methodname>testMapWrapper</methodname> unit test method in <classname>org.jboss.seam.test.RemotingTest</classname> fails with an <errorname>AssertionError</errorname>.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- </section>
-<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
-
-</article>
Copied: projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP09.ent (from rev 105695, projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP08.ent)
===================================================================
--- projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP09.ent (rev 0)
+++ projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP09.ent 2010-06-04 05:02:34 UTC (rev 105699)
@@ -0,0 +1,3 @@
+<!ENTITY HOLDER "Red Hat, Inc">
+<!ENTITY YEAR "2009">
+<!ENTITY VERSION "4.2">
Copied: projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP09.xml (from rev 105695, projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP08.xml)
===================================================================
--- projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP09.xml (rev 0)
+++ projects/docs/enterprise/EAP/releases/4.2/4.2.9/readme/en-US/Release_Notes_CP09.xml 2010-06-04 05:02:34 UTC (rev 105699)
@@ -0,0 +1,1017 @@
+<?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.2 that can be found in this Cumulative Patch release.
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ JBoss Application Server 4.2.z
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Microcontainer 1.0.2
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Core 3.2.4.SP1_CP09
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Annotations 3.3.1.GA_CP02
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Entity Manager 3.3.2.GA_CP01
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Validator 3.0.0.GA
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Apache Xalan 2.7.0.patch02
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JacORB 2.3.0jboss.patch7
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JAF 1.1.0
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JavaServer Faces 1.2_13
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss AOP 1.5.5.GA_CP04
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Cache 1.4.1.SP13
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss JAXR 1.2.0.SP2
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Remoting 2.2.3.SP1
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Serialization 1.0.3.GA
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Transactions 4.2.3.SP5_CP07
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss XB 1.0.0.SP3
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Web 2.0.0.GA_CP12
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Web Services 1.2.1.GA_CP05
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JGroups 2.4.7.GA
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Seam 1.2.1.GA
+ </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.CP07</title>
+ <formalpara>
+ <title>Using CSP/JON</title>
+ <para>
+ <orderedlist>
+ <title>Installing a Cumulative Patch</title>
+ <listitem>
+ <para>
+ Use <guibutton>Browse Resources</guibutton> to navigate to the resource you wish to patch.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Click on the <guibutton>Software</guibutton> tab. All patches applicable to your resource and all patches that have been previously installed by JON on this resource will be displayed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ An <guibutton>Install</guibutton> link will be listed beside all patches that can be installed by JON. Any patches without this link must be installed manually. Any patch that appears beside a <guibutton>Manually Uninstall</guibutton> link must be uninstalled manually before the new patch can be installed.
+ </para>
+ <para>
+ For more information about installing a patch with CSP/JON, see the <ulink url="http://jon01.qa.atl2.redhat.com:8080/display/DOC/Installing+a+Patch">JON documentation</ulink>.
+ </para>
+ </listitem>
+ </orderedlist>
+ </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-CP08.zip"> ftp://ftp.redhat.com/pub/redhat/jbeap/4.2.0/en/source/jboss-eap-src-4.2.0-CP08.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 <filename>index.html</filename> 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>Security</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2872">JBPAPP-2872</ulink>: Twiddle logged all command line arguments, including the JMX password, to <filename>twiddle.log</filename>, which has public read permissions, and is created in the current working directory. The password is now masked in the log, removing the risk to security. This issue has been assigned CVE-2009-3554.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2312">JBPAPP-2312</ulink>: A new <classname>PrincipalSessionAttributeFilter</classname> has been created to include the principal session as an attribute of the HTTP Session. This attribute is checked upon session expiry and the authenticated cache will be flushed if found. In order to use this filter, uncomment the filter in Tomcat's <filename>web.xml</filename>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Application Server</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2905">JBPAPP-2905</ulink>: The <varname>ScanPeriod</varname> in the <literal>production</literal> configuration is set to sixty seconds. If the deployment scanner thread was sleeping when shutdown was initiated, shutdown waited for the length of the deployment scanner's sleep time. The deployment scanner thread is now stopped when shutdown is initiated, and the wait no longer occurs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2764">JBPAPP-2764</ulink>: <classname>LoadMgr3</classname> logged a failure to load a class as an error, but in certain situations this should be regarded as correct. The <literal>ERROR</literal> message has been downgraded to a <literal>WARNING</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2578">JBPAPP-2578</ulink>: Configuration information for the JBoss Messaging service in <filename>sample-bindings.xml</filename> has been updated to make use of new settings.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Clustering</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2854">JBPAPP-2854</ulink>: When multiple nodes were started concurrently, an address mismatch would occur between cluster members and message senders. This caused inconsistent internal state in <literal>NAKACK</literal>, which would log errors similar to the following:
+ </para>
+ <programlisting>
+WARN [org.jgroups.protocols.pbcast.NAKACK]
+ (IncomingPacketHandler (channel=Tomcat-DefaultPartition):)
+ node2:1234] discarded message from non-member node3:1234,
+ my view is [node1:1234|2] [node1:1234, node2:1234, node3:1234]
+
+ERROR [org.jgroups.protocols.pbcast.NAKACK] (Timer-3:)
+ sender node3:1234 not found in received_msgs
+ </programlisting>
+ <para>
+ This mismatch has been corrected and the errors no longer present.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Web</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2039">JBPAPP-2039</ulink>: The fix for <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1992">JBPAPP-1992</ulink> means that Version 1 cookies are used in JBoss Web instead of Version 0. This older version is linked to a security issue, described in <ulink url="https://www.redhat.com/security/data/cve/CVE-2007-5333.html">CVE-2007-5333</ulink>. To return to the previous behavior despite this, add a <filename>conf/catalina.properties</filename> file and set the following property in it:
+ </para>
+ <programlisting>
+org.apache.tomcat.util.http.ServerCookie.VERSION_SWITCH=false
+ </programlisting>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Seam</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2967">JBPAPP-2967</ulink>: A shared value binding returned a <literal>null</literal> value when under load, which caused a <exceptionname>javax.el.PropertyNotFoundException</exceptionname>. The value binding is no longer shared and the issue no longer presents.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>EJB3</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2782">JBPAPP-2782</ulink>: When EJB3 entities were used with optimistic caching, the <methodname>newerThan</methodname> method would incorrectly return <literal>true</literal> for <code>A.newerThan ( A )</code>. This caused a <exceptionname>DataVersioningException</exceptionname> when attempting to remove the entry from the cache. The EJB3 entity cache service is now configured to use pessimistic caching to avoid this issue.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Hibernate</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3060">JBPAPP-3060</ulink>: <literal>@JoinColumn</literal> mapping assumed that the column definition was void even if it was also defined by <literal>@ManyToOne</literal>. <filename>Ejb3JoinColumn.java</filename> has been updated so that defined column properties like <varname>length</varname>, <varname>precision</varname> and <varname>scale</varname> are observed in <literal>@JoinColumn</literal> mapping.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3052">JBPAPP-3052</ulink>: When <classname>org.hibernate.id.enhanced.SequenceStyleGenerator</classname> generates identifiers, the select script generated is as follows:
+ </para>
+ <programlisting>
+select next_val id_val from hibernate_sequence for update
+ </programlisting>
+ <para>
+ However, in PostgreSQL, <literal>as</literal> is required between <literal>next_val</literal> and <literal>id_val</literal>. See <ulink url="http://sql-info.de/en/postgresql/postgres-gotchas.html#1_1">http://sql-info.de/en/postgresql/postgres-gotchas.html#1_1</ulink> for further details.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3038">JBPAPP-3038</ulink>: Hibernate Core has been upgraded to version 3.2.4.SP1.CP09. Hibernate Annotations has been upgraded to version 3.3.1.GA.CP02. Hibernate Entity Manager has been upgraded to version 3.3.2.GA.CP01.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2900">JBPAPP-2900</ulink>: MySQL uses the <literal>TEMPORARY</literal> keyword to bypass implicit transaction commits. Previously, Hibernate used <literal><CREATE TEMPORARY TABLE></literal> with <literal><DROP TABLE></literal>. Omitting the <literal>TEMPORARY</literal> keyword caused an implicit commit, and immediate failure within an XA Transaction. <literal><DROP TEMPORARY TABLE></literal> is now supported and this issue no longer presents.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2049">JBPAPP-2049</ulink>: the HQL translator attempted to render <literal>IS NULL</literal> and <literal>IS NOT NULL</literal> checks against a component by using tuple syntax. Exploded syntax is now used instead, to make SQL more readable.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1998">JBPAPP-1998</ulink>: <exceptionname>EntityNotFoundException</exceptionname> is incorrectly thrown upon an optimistic locking failure when one <literal>EntityManager</literal> tries to delete an entity that has been updated by a different <literal>EntityManager</literal> and <varname>hibernate.jdbc.batch_versioned_data</varname> is set to <literal>false</literal> (the default value). <exceptionname>OptimisticLockException</exceptionname>, the correct exception for this situation, is now thrown instead.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1547">JBPAPP-1547</ulink>: By default, Sybase ASE 15 string comparisons are case-insensitive. The <methodname>org.hibernate.dialect.SybaseASE15Dialect.areStringComparisonsCaseInsensitive()</methodname> method now returns <literal>true</literal>.
+ </para>
+ <para>
+ If the Sybase database is configured to perform case-sensitive operations, this setting will be incorrect. However, since Hibernate only uses this method for unit tests, this change has no effect on Hibernate's internal processing.
+ </para>
+ </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="https://jira.jboss.org/jira/browse/JBPAPP-3145">JBPAPP-3145</ulink>: The <filename>wsrunclient.sh</filename> scripts are missing a library and fail with a <exceptionname>ClassNotFoundException</exceptionname>. To work around this issue on Linux, execute the following statements before executing <filename>wsrunclient.sh</filename>:
+ </para>
+ <programlisting><![CDATA[
+export JBOSS_HOME=<path to your JBoss EAP installation>
+WSRUNCLIENT_CLASSPATH="$JBOSS_HOME/client/wsdl4j.jar"
+export WSRUNCLIENT_CLASSPATH
+ ]]></programlisting>
+ <para>
+ To work around this issue on Windows, execute the following before executing <filename>wsrunclient.bat</filename>:
+ </para>
+ <programlisting><![CDATA[
+set JBOSS_HOME=<path to your JBoss EAP installation>
+set WSRUNCLIENT_CLASSPATH=%JBOSS_HOME%/client/wsdl4j.jar
+ ]]></programlisting>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3143">JBPAPP-3143</ulink>: The <filename>wsprovide.sh</filename> and <filename>wsprovide.bat</filename> scripts fail when generating a WSDL file from the examples. To work around this issue on Linux, execute the following statements before running <filename>wsprovide.sh</filename>:
+ </para>
+ <programlisting><![CDATA[
+export JBOSS_HOME=<path to your JBoss EAP installation>
+WSPROVIDE_CLASSPATH="$JBOSS_HOME/client/jaxb-xjc.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jboss-ejb3x.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/wsdl4j.jar"
+export WSPROVIDE_CLASSPATH
+ ]]></programlisting>
+ <para>
+ To work around this issue on Windows, execute the following statements before running <filename>wsprovide.bat</filename>:
+ </para>
+ <programlisting><![CDATA[
+set JBOSS_HOME=<path to your JBoss EAP installation>
+set WSPROVIDE_CLASSPATH=%JBOSS_HOME%/client/jaxb-xjc.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/jboss-ejb3x.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/wsdl4j.jar
+ ]]></programlisting>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3117">JBPAPP-3117</ulink>: If an incorrect <varname>mcast_addr</varname> value is set, users are pointed to an outdated URL for information about cross talking. If you experience problems with <varname>mcast_addr</varname> and cross talking, the updated URL for further information is <ulink url="https://www.jboss.org/community/docs/DOC-9469">https://www.jboss.org/community/docs/DOC-9469</ulink>.
+ </para>
+ </listitem>
+ <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="https://jira.jboss.org/jira/browse/JBPAPP-3105">JBPAPP-3105</ulink>: The number of elements that can be included in a single <methodname>IN</methodname> expression is limited to a certain number (for Oracle, 1000). If an Array or Collection is passed into the <methodname>IN</methodname> method, Oracle throws an error stating that the <methodname>IN</methodname> clause must contain at most 1000 items. This affects both HQL and Criteria API. To work around this issue, users should split large arrays and collections into sub-arrays or sub-collections. If 'in', use the form <code>in(1,2,...,1000) or in(1001+)</code>; if 'not in', use the form <code>not(1,2,...,1000) or in(1001+)</code>, as described in the JIRA.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3098">JBPAPP-3098</ulink>: When a filter with a <varname>collection-type</varname> parameter is used, and the number of parameters in that collection changes during the lifetime of the <classname>SessionFactory</classname>, the SQL is not updated to reflect the change in the number of parameters. This typically results in the following error:
+ </para>
+ <programlisting>
+java.sql.SQLException: Parameter index out of bounds. 2 is not between valid values of 1 and 1
+ </programlisting>
+ <para>
+ This occurs only with HQL, not Criteria. There is currently no workaround, but the fix has been applied in the Hibernate Cumulative Patch branch and will be included in the next Cumulative Patch release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3089">JBPAPP-3089</ulink>: A long <literal>IN</literal> list can cause a stack overflow error during parsing. A query element like:
+ </para>
+ <programlisting>
+where x in (:x)
+ </programlisting>
+ <para>
+ or a manually constructed:
+ </para>
+ <programlisting>
+where x in (1,2,3,...)
+ </programlisting>
+ <para>
+ can generate a stack overflow if the number of elements referenced by <literal>x</literal> exceeds a certain number which depends upon the amount of available stack space. For many Java Virtual Machines, the limit is between 9000 and 10000, assuming a relatively empty stack at the point of query execution. To work around this issue, users should split large numbers of elements into sub-groups. If 'in', use the form <code>in(1,2,...,1000) or in(1001+)</code>; if 'not in', use the form <code>not(1,2,...,1000) or in(1001+)</code>, as described in the JIRA.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3075">JBPAPP-3075</ulink>: If a database reserved keyword is used as a property name with a Hibernate Validator annotation (for example, <literal>@Min</literal> or <literal>@Max</literal>), it will cause exceptions in <literal>SchemaExport</literal>, even if you specify a column name. This is because Hibernate ignores the name specified. The workaround is to map the property name to another that is not a database reserved keyword with <literal>@Column</literal> annotation. The fix for this issue is expected in Hibernate 4.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3069">JBPAPP-3069</ulink>: The <literal>QueryByExampleTest.testJunctionNotExpressionQBE</literal> test fails in Sybase because <varname>ansinull</varname> is set to <literal>off</literal> by default. This test builds a disjunction predicate such as <code>( OR^ (ex) (NOT ex) )</code>. This should match everything in the database, but because ANSI SQL evaluates all comparisons involving <literal>NULL</literal> values as <literal>UNKNOWN</literal>, not all matches are returned.
+ </para>
+ <para>
+ To work around this issue, append this string to the JDBC URL:
+ </para>
+ <programlisting>
+?SQLINITSTRING=set ansinull on
+ </programlisting>
+ <para>
+ If this is not possible, an alternative is to execute the following Java code (or similar) after getting a Hibernate Session, <literal>s</literal>.
+ </para>
+ <programlisting role="JAVA">
+s.connection().createStatement().execute("set ansinull on");
+ </programlisting>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3068">JBPAPP-3068</ulink>: Mapping an Enum as <literal>@Id</literal> on MySQL causes a <exceptionname>SchemaExport</exceptionname> exception with error messages similar to the following:
+ </para>
+ <programlisting>
+Unsuccessful: create table PlanetCheatSheet (planet tinyblob
+not null,mass double precision not null, numberOfInhabitants
+bigint not null, radius double precision not null, primary
+key (planet)) ENGINE=InnoDB
+BLOB/TEXT column 'planet' used in key specification without
+a key length
+ </programlisting>
+ <para>
+ Currently, Hibernate binds the <varname>id</varname> property of an Enum type as a <literal>tinyBlob</literal> (on MySQL) without a <varname>length</varname> property. The workaround for this issue is currently to write your own DDL if your Enum property must be mapped as <literal>@Id</literal>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3056">JBPAPP-3056</ulink>: The Hibernate test <literal>org.hibernate.test.hql.ASTParserLoadingTest.java</literal> fails on DB2 with an SQL Error because of invalid use of a parameter marker. This occurs because DB2 does not support untyped parameters. To work around this issue, modify your queries so that the parameters are cast to an appropriate data type.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2945">JBPAPP-2945</ulink>: The Hibernate test <filename>org.hibernate.test.annotations.query.QueryAndSQLTest.java</filename> fails on PostgreSQL 8.3.7 with the following log messages:
+ </para>
+ <screen>
+Caused by: org.postgresql.util.PSQLException: Method org.postgresql.jdbc3.Jdbc3PreparedStatement.setQueryTimeout(int) is not yet implemented.
+ </screen>
+ <para>
+ This occurs because PostgreSQL JDBC driver does not support the <methodname>Statement.setQueryTimeout</methodname> method.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2839">JBPAPP-2839</ulink>: Failing to re-inject the interceptors for instrumented entities causes <exceptionname>NullPointerException</exceptionname>s when entities are retrieved from a deserialized <literal>PersistenceContext</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2440">JBPAPP-2440</ulink>: When a cache provider cannot be found, a <errorname>NoClassDefFoundError</errorname> is thrown with the message:
+ </para>
+ <programlisting>net/sf/ehcache/CacheException</programlisting>
+ <para>
+ When a connection provider cannot be found, a <exceptionname>HibernateException</exceptionname> is thrown with the following message:
+ </para>
+ <programlisting>Could not instantiate connection provider: " + providerClass</programlisting>
+ <para>
+ If you experience these errors, we suggest checking the cache or connection provider configuration to ensure that the provider is included in the classpath.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2316">JBPAPP-2316</ulink>: Hibernate does not currently provide property types that enable applications to process data in a long string or binary column as a Java String. This feature is expected in JBoss Enterprise Application Platform 5.1.0.GA.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2315">JBPAPP-2315</ulink>: Hibernate does not currently provide property types that enable applications to process data in a <literal>java.sql.Types.LONGVARCHAR</literal> or <literal>java.sql.Types.CLOB</literal> column as a Java String. Processing of a <literal>java.sql.Types.LONGVARBINARY</literal> or <literal>java.sql.Types.BLOB</literal> as a Java <literal>byte[]</literal> is also unavailable. These features are expected in JBoss Enterprise Application Platform 5.1.0.GA.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1722">JBPAPP-1722</ulink>: Sybase fails to insert a new entity if the entity overflows the column. However, it does not throw an exception, so Hibernate cannot tell that the insert has failed. To work around this issue, your application must validate entity properties to ensure that the value will not overflow the underlying column.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1709">JBPAPP-1709</ulink>: The version of <filename>ejb3-persistence.jar</filename> shipped with the current version of JBoss Enterprise Application Platform 4.x is incorrect. Hibernate Entity Manager currently ships <filename>ejb3-persistence.jar</filename> 1.0.0.GA, but it should use <filename>ejb3-persistence.jar</filename> 1.0.1.GA.
+ </para>
+ <para>
+ There are two changes between the 1.0.0.GA and 1.0.1.GA versions of the JAR:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The JPA specification defines the constant with a value that has a typo in the classname:
+ </para>
+ <programlisting>javax.persistence.Persistence.PERSISTENCE_PROVIDER = "javax.persistence.spi.PeristenceProvider"</programlisting>
+ <para>
+ Because the JAR inluded in the JBoss Enterprise Application Platform does not include this typo, it is not compliant with the JPA specification. See <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-321">http://opensource.atlassian.com/projects/hibernate/browse/EJB-321</ulink> for details.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Javadoc for <methodname>javax.persistence.Query.getSingleResult()</methodname> states that <exceptionname>EntityNotFoundException</exceptionname> will be thrown if there is no result. It should say <exceptionname>NoResultException</exceptionname>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1613">JBPAPP-1613</ulink>: Null values for columns mapped as Boolean in Sybase are persisted as <literal>0</literal> instead of <literal>null</literal>. The current workaround for this issue is to map these values as <literal>type="org.hibernate.test.where.NumericTrueFalseType"</literal> instead of <literal>type="boolean"</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1555">JBPAPP-1555</ulink>: Sybase uses <literal>image</literal> and <literal>text</literal> instead of <literal>Blob</literal> and <literal>Clob</literal>, so there is no support for <literal>Blob</literal> and <literal>Clob</literal> on Sybase. This feature is expected in JBoss Enterprise Application Platform 5.1.0.GA. Currently, user-defined types can be created to process Sybase <literal>text</literal> and <literal>image</literal> properties.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1554">JBPAPP-1554</ulink>: Sybase only allows only one entry (for example, column name or '*') in a subquery select list. The HQL function, <methodname>elements()</methodname>, fails when the collection elements have a composite ID, because the generated SQL contains a subquery select list with multiple entries. The workaround is to avoid using HQL <methodname>elements()</methodname> if the elements have a composite key. Instead, reformulate the HQL so that no subquery has multiple entries in its select list.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1551">JBPAPP-1551</ulink>: Embedded classes are not considered when batch insert statements are ordered. There are two possible workarounds for this issue:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Leave <varname>ORDER_INSERTS</varname> at the default value (<literal>FALSE</literal>) when embedded classes are used.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Explicitly call <methodname>session.save()</methodname> on child objects to enforce their SQL insertion orders.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </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="https://jira.jboss.org/jira/browse/JBPAPP-1545">JBPAPP-1545</ulink>: On Sybase, when a query has an ANSI join with three or more joins, and one join involves a union subclass, the query may fail with <exceptionname>SybSQLException</exceptionname> because a column is not within the scope of the joined table expression. The current recommendation is to avoid using join fetches that involve union subclasses.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1328">JBPAPP-1328</ulink>: When attempting to perform a delete or update statement with a subselect, the generated SQL will refer to an unknown table alias and cause the query to fail.
+ </para>
+ <para>
+ Currently the workaround is to reverse the conditions in the <literal>where</literal> clause.
+ </para>
+ <para>Incorrect:</para>
+ <programlisting>update Person set name = ?1 where id in (select c.id from Customer c) and name <> ?2</programlisting>
+ <para>Correct:</para>
+ <programlisting>update Person set name = ?1 where name <> ?2 and id in (select c.id from Customer c)</programlisting>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1230">JBPAPP-1230</ulink>: When a <literal>DetachedCriteria</literal> is used as a subquery, the generated SQL contains a column alias in the subquery. On Sybase, a <exceptionname>SybSQLException</exceptionname> is thrown because Sybase does not allow column aliases in subqueries. The workaround for this issue is to use an HQL query instead of a <literal>DetachedCriteria</literal> in a subquery.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1229">JBPAPP-1229</ulink>: On Sybase, the text <literal>current_timestamp</literal> is not being recognised as a method mode by the translator. Only SQL function calls with parentheses are recognized as method modes. There is no workaround for this issue except to avoid relying upon function replacement for <literal>current_timestamp</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1123">JBPAPP-1123</ulink>: When <literal>@OrderBy</literal> is used on joined classes (using a join table), the generated SQL is invalid on MySQL, PostgreSQL, Oracle, and MSSQL because the "order by" clause qualifies the columns using the actual table name. The "order by" clause should use the table alias instead.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1082">JBPAPP-1082</ulink>: When a <varname>char</varname> property is used and it is not initialized, then Hibernate initializes it to <literal>0</literal> and persists a string containing the character <literal>\u0000</literal>. PostgreSQL throws an exception because it does not allow character <literal>\u0000</literal> embedded in a string. An email thread describing this problem is available from:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ http://markmail.org/message/jvzlzxw6ui2rcsmv#query:\u0000%20postgresql+page:1+mid:gpu34f4iwanbyjqh+state:results
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ There is currently no workaround for persisting <literal>\u0000</literal> in a <varname>char</varname> column using PostgreSQL.
+ </para>
+ <para>
+ If the user intends to persist a NULL for an uninitialized char property instead of <literal>\u0000</literal>, then <varname>java.lang.Character</varname> should be used instead of the primitive <varname>char</varname> type. This avoids the exception when the property is initialized. Attempting to persist a <varname>java.lang.Character</varname> property that is set to <literal>\u0000</literal> still results in an exception.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1075">JBPAPP-1075</ulink>: <literal>SchemaExport</literal> fails on Oracle and Sybase when a redundant <code>@Column( unique = true )</code> or <code>@UniqueConstraint( columnNames = { ... } )</code> annotation is used for a column that is implicitly defined as unique by the declared model. The workaround is to remove the redundant <code>@Column</code> annotation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1071">JBPAPP-1071</ulink>: In some cases, when there are foreign key constraints defined on columns in a primary key, <literal>SchemaExport</literal> incorrectly declares them as nullable when it generates <code>CREATE TABLE</code> statements. This fails on MSSQL, DB2, and Sybase because those databases require primary key columns to be non-nullable.
+ </para>
+ <para>
+ The workaround for this issue is to explicitly indicate which columns should be non-nullable, such as:
+ </para>
+ <itemizedlist>
+ <listitem><para>Add <code>nullable=false</code> to <literal>@JoinColumn</literal></para></listitem>
+ <listitem><para>Add <code>optional=false</code> to <literal>@ManyToOne</literal></para></listitem>
+ <listitem><para>Add an <literal>@AttributeOverride</literal> with <code>@Column(name="mapkey", nullable=false)</code> in case of a <literal>@CollectionOfElements</literal> using a Map</para></listitem>
+ <listitem><para>Add <code>nullable=false</code> in <literal>@Column</literal> when inside a <literal>@CollectionId</literal> or inside <literal>@MapKey</literal></para></listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="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 <literal>TIME</literal> and <literal>TIMESTAMP</literal>.
+ </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-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-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>
+ <formalpara>
+ <title>Documentation</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2809">JBPAPP-2809</ulink>: The <citetitle>Server Configuration Guide CP08</citetitle> contained in the packaged documentation bundle contains an error. In Section 5.5.1, <emphasis>JNDI Binding Manager</emphasis>, the first code example contains an incorrect line:
+ </para>
+ <programlisting>
+ xmlns:jndi="urn:jboss:jndi-binding-service:10"
+ </programlisting>
+ <para>
+ This line should be:
+ </para>
+ <programlisting>
+ xmlns:jndi="urn:jboss:jndi-binding-service:1.0"
+ </programlisting>
+ <para>
+ This has been corrected in the online documentation, available 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>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Seam Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3138">JBPAPP-3138</ulink>: Several BlogTest unit test methods (<methodname>test.BlogTest.testEntry()</methodname> and <methodname>test.BlogTest.testLatest()</methodname>) fail on all platforms. In addition, <methodname>test.BlogTest.testSearch()</methodname> fails on certain platforms. For further information, see the console output in the JIRA.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3176">JBPAPP-3176</ulink>: The <methodname>testMapWrapper</methodname> unit test method in <classname>org.jboss.seam.test.RemotingTest</classname> fails with an <errorname>AssertionError</errorname>.
+ </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