[jboss-cvs] JBossAS SVN: r77924 - projects/docs/enterprise/4.3.3/readme/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Sep 3 21:01:06 EDT 2008
Author: irooskov at redhat.com
Date: 2008-09-03 21:01:06 -0400 (Wed, 03 Sep 2008)
New Revision: 77924
Added:
projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes.ent
projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes.xml
Removed:
projects/docs/enterprise/4.3.3/readme/en-US/readme.ent
projects/docs/enterprise/4.3.3/readme/en-US/readme.xml
Log:
publican version update
Added: projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes.ent
===================================================================
--- projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes.ent (rev 0)
+++ projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes.ent 2008-09-04 01:01:06 UTC (rev 77924)
@@ -0,0 +1,3 @@
+<!ENTITY HOLDER "Red Hat, Inc">
+<!ENTITY YEAR "2008">
+<!ENTITY VERSION "4.3.0.CP02">
Added: projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes.xml
===================================================================
--- projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes.xml (rev 0)
+++ projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes.xml 2008-09-04 01:01:06 UTC (rev 77924)
@@ -0,0 +1,628 @@
+<?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 4.3</title>
+ <section id="Messaging">
+ <title>JBoss Messaging</title>
+ <para>
+ In JBoss Enterprise Application Platform 4.3, 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 JBoss Enterprise Application Platform 4.3 and will now provide a complete implementation of JAX-WS.
+ </para>
+ </section>
+
+ </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.3</title>
+ <formalpara>
+ <title>Using CSP/JON</title>
+ <para>Refer to <ulink url="https://network.jboss.com/confluence/display/DOC/Installing+a+Patch">https://network.jboss.com/confluence/display/DOC/Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch.</para>
+ </formalpara>
+ <!--
+ <para>JBoss MQ is now replaced with JBoss Messaging as the JMS implementation shipped within JBoss Enterprise Application Platform &VERSION;. 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.3.0/en/source/jboss-eap-src-4.3.0-CP01.zip"> ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-CP02.zip</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ </section>
+ </section>
+ <section id="Product-Support-and-License-Links">
+ <title>
+ Product Support and License Website Links
+ </title>
+ <formalpara>
+ <title>Support Processes</title>
+ <para>
+ <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ Production Support Scope of Coverage
+ </title>
+ <para>
+ <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink>
+ </para>
+ </formalpara>
+
+
+ <formalpara>
+ <title>
+ Production Support Service Level Agreement
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ Developer Support Scope of Coverage
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ Developer Support Service Level Agreement
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ Product Update and Support Policy by Product
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ JBoss End User License Agreement
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink>
+ </para>
+ </formalpara>
+ </section>
+
+ <section id="Documentation">
+ <title>
+ Documentation
+ </title>
+ <para>
+ Refer to the index.html file in the documentation directory for a list of included documentation.
+ </para>
+ <para>
+ In the zip distribution, documentation for the Platform and its individual components is distributed in a separate zip file, <filename>jboss-eap-docs-<version>.zip</filename>.
+ </para>
+
+ <para>
+ On a Linux system, the documentation is found in two rpms that will need to be installed manually. These rpms are <filename>jboss-seam-docs-<version>.noarch.rpm</filename>, and <filename>rh-eap-docs-<version>.noarch.rpm</filename>. For help with installing rpm packages on Red Hat Enterprise Linux, please refer to the Red Hat Knowledge base article located at <ulink url="http://kbase.redhat.com/faq/FAQ_35_198.shtm">http://kbase.redhat.com/faq/FAQ_35_198.shtm</ulink>
+ </para>
+ <para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>Installation Guide</filename> explains how to install and verify the installation of JBoss Enteprise 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 will be supported in version 4.3.
+ </para>
+ </section>-->
+
+ <section id="Issues-fixed-in-this-release">
+ <title>
+ Issues fixed in this release
+ </title>
+
+ <para>
+ Following is a list of issues fixed in this release:
+ </para>
+ <formalpara>
+ <title>JBoss Messaging</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-925">JBPAPP-925</ulink>: JBoss Messaging has been upgraded to version 1.4.0.SP3_CP03. This update includes numerious bug fixes that improves the overall component.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-920">JBPAPP-920</ulink>: The JBoss Messaging documentation was outdated. This CP release contains the JBoss Messaging 1.4.0.SP3_CP03 User Guide.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-900">JBPAPP-900</ulink>: The SQL default configuration had errors, causing an issue within hsqldb which uses this configuration. The issue with the default configuration has now been corrected.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-813">JBPAPP-813</ulink>: The Messaging client included a bug that would make it hang forever, creating a <code>ClusteredConnectionFactory</code> failover; steaming from a socket hang. This issue has now been rectified in this latest EAP release, creating a more stable Messaging component.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+<!-- <formalpara>
+ <title>JBoss Cache</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara> -->
+ <formalpara>
+ <title>JBoss Remoting</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-735">JBPAPP-735</ulink>: The JBoss Remoting component of the EAP has been upgraded to version 2.2.2.SP8. This upgrade includes numerious bug fixes.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Web Services</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-930">JBPAPP-930</ulink>: The upgrade to JBossWS Common 1.0.0.GA_CP01 is included wihtin this CP release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-887">JBPAPP-887</ulink>: JBoss Java API for XML Redistries (JAXR) has been upgraded to version 1.2.0.SP1 which addresses various bugs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-791">JBPAPP-791</ulink>: The JBoss Web Services Component has been upgraded to version 2.0.1.SP2_CP02. This upgrade incorporates various bug fixes and enhancements.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Seam</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-755">JBPAPP-755</ulink>: The Seam source readme.txt file required updated links to seamframework.org and mention the EAP instead of the JBoss AS. This file has been updated with the above changes for this release.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Hibernate</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-938">JBPAPP-938</ulink>: An unchanged parent entity would incorrectly have its version value incremented when part of a one to many relationship. This error has been rectified with this latest CP release by correcting an issue in the <filename>CollectionType.java</filename> file and adding the a new method called <methodname>testNoExtraUpdatesOnPersistentMergeVersionedWithCollection()</methodname> to <filename>MergeTest.java</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-936">JBPAPP-936</ulink>: The <methodname>AnnotationBinder.mustBeSkipped</methodname> method had an incorrect hardcoded String-Reference to the <classname>org.hibernate.tool.instrument.javassist.FieldHandler</classname> class. This error has meant that the <emphasis>junitinstrument</emphasis> test was not running correctly. This issue has been fixed, with the correct package location of the class being referenced with the class name <classname>org.hibernate.bytecode.javassist.FieldHandler</classname> and the <emphasis>junitinstrument</emphasis> test now runs successfully.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-915">JBPAPP-915</ulink>: A merge operation would fail when there was a transient entity that was reachable by multiple paths and at least one of these paths did not cascade when undertaking a merge. This issue is fixed with the EAP 4.3 now supporting JDK 6.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-908">JBPAPP-908</ulink>: Hibernate proxy serialization was broken because the <classname>AbstractLazyInitializer</classname> class was not Serializable. This is now corrected within this CP release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-899">JBPAPP-899</ulink>: There was an error within the entity manager where the methods <methodname>getSingleResult()</methodname> and <methodname>fetch()</methodname> would return a <code>NonUniqueResultException</code> because elements were now unique. This issue has been corrected with this CP release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-859">JBPAPP-859</ulink>: The <classname>SchemaUpdate</classname> class has been enhanced with <option>output file name</option>, <option>delimiter</option>, <option>halt on error</option>, <option>format</option> options now avaliable.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-782">JBPAPP-782</ulink>: The <classname>MapBinder</classname> class had the ability to generate SQL statements that would not be supported by the Oracle 10g database. This was of particular concern for some EJB3 Persistence users on EAP and Oracle. This issue has now been rectified in this CP release.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+<!-- <formalpara>
+ <title>JBoss Transaction Service (JBossTS)</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara> -->
+ <formalpara>
+ <title>Security Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ There are no Security Issues addressed with this CP releae.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-1004</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1004">JBPAPP-1004</ulink>: Previous versions of the EAP contained an incorrect <property>serialVersionUID</property> number, which interfered with backwards compatability. The correct <property>serialVersionUID</property> number is included with this release.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-972</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-972">JBPAPP-972</ulink>: JBoss Aspect-Oriented Programming (AOP) has been upgraded to version 1.5.GA_CP02.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-971</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-971">JBPAPP-971</ulink>: Javassist has been upgraded to version 3.8.0.GA, fixing numerious issues related to this class library.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-961</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-961">JBPAPP-961</ulink>: JBoss Web has been upgraded to version 2.0.0.GA CP06.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-944</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-944">JBPAPP-944</ulink>: <classname>ClusteredSession</classname> included logic that would skip session metadata replication if the only change was the timestamp. This issue was corrected by changing the default maximum interval between requests. The default interval is now 60 seconds and the value is now configurable. This attribute can be changed by adding an atribute to the <filename>jboss-service.xml</filename> file that resembles <programlisting><attribute name="MaxUnreplicatedInterval">30</attribute></programlisting>.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-926</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-926">JBPAPP-926</ulink>: A section in the Server Configuration Guide called <emphasis>Existing Entity Commands</emphasis> specified the wrong packages for some classes. This updated version of the Server Configuration Guide included with this CP, contains the correct package information for the classes affected.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-907</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-907">JBPAPP-907</ulink>: There was an issue where a deserialization bottleneck would occur in arrays for JDK 1.6. In order to rectify this issue, the following has been added to the <filename>run.conf</filename> file: <programlisting>-Dsun.lang.ClassLoader.allowArraySyntax=true</programlisting>.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-897</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-897">JBPAPP-897</ulink>: JBoss Transaction Services has been upgraded to version 4.2.3 SP5 CP02.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-895</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-895">JBPAPP-895</ulink>: The Java Messaging Service (JMS) connections needed to be consistently closed in reference to the J2EE Connector Architecture (JCA). These connections are now always closed to restrict exceptions.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-891</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-891">JBPAPP-891</ulink>: The monitoring tool <emphasis>Twiddle</emphasis> did not print out <code>invoke</code> results, even with the absense of a property editor for the returned object. Corrected within this CP release, <emphasis>Twiddle</emphasis> now calls the <methodname>toString()</methodname> method on returned objects when there is no property editor found.
+ </para>
+ </formalpara>
+ <!-- <formalpara>
+ <title>JBPAPP-878</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-878">JBPAPP-878</ulink>: There was a bug that caused the <property>STRICT_SERVLET_COMPLIANCE</property> property to return with false results, in terms of the Technology Compatability Kit (TCK). The property <property>STRICT_SERVLET_COMPLIANCE</property> no longer returns false results.
+ </para>
+ </formalpara> -->
+ <formalpara>
+ <title>JBPAPP-877</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-877">JBPAPP-877</ulink>: JBoss Serialization version 1.0.3GA would encounter <code>ClassCastExceptions</code> when being used. This update corrects this issue so that serialization functions correctly.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-867</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-867">JBPAPP-867</ulink>: An <interfacename>ExceptionSorter</interfacename> interface implementation should be provided for users of the IBM DB2 Data Server. This enhancement to the EAP is included within this CP release.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-864</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-864">JBPAPP-864</ulink>: Clustered proxy factories did not bind home proxies. This issue has been rectified by now supporting clustered home proxies for EJB3 beans. However, in order to
+ avoid backwards compatibility issues, the load balance policy for home proxies has
+ been hard coded to round robin. This is also the default policy for EJB2 home proxies.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-858</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-858">JBPAPP-858</ulink>: Allow for multiple instances to be setup on one machine using a subpackage method. This functionality has been added in this release with -bin files.
+ </para>
+ </formalpara>
+ <para>
+ It is important to note that a regular jbossas installation is required on the server first before installtion of the -bin. The -bin is for an additional installation only and cannot be used in place of a regular RPM jbossas installation. If you only have one version of the AS, it will have to be the regular RPM installation (or ZIP or installer for older versions).
+ </para>
+ <formalpara>
+ <title>JBPAPP-857</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-857">JBPAPP-857</ulink>: The .rar file <filename>mail-ra.rar</filename> used within the application server to recieve email from using the JavaMail API, was missing from the distribution. This missing file has now been re-included.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-856</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-856">JBPAPP-856</ulink>: Support of the DeliveryActive MDB activation configuration property when deploying. This mechanism enables the ability to start and stop the consumption of Messages during deployment and is supported with this release.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-844</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-844">JBPAPP-844</ulink>: The MSSQL data source example was incompatible with SQL Server 2005. To fix this compatability issue, the <code>driver-class</code> has been updated from <code>com.microsoft.jdbc.sqlserver.SQLServerDriver</code> to <code>com.microsoft.sqlserver.jdbc.SQLServerDriver</code> and the default port for the <code>connection-url</code> has been changed from 1433 to 3918. With these changes the example now functions correctly under SQL Server 2005.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-815</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-815">JBPAPP-815</ulink>: An issue existed where if a DOCTYPE was added to the file <filename>-ds.xml</filename> and the option to <option>ValidateDTDs</option> was set to true in <filename>jbossjca-services.xml</filename>, validation errors would occur. This was found to be because of an issue with the <property>tx-connection-factory</property> element in <filename>jms-ds.xml</filename> which has since been fixed.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-805</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-805">JBPAPP-805</ulink>: There was a missing java file from the first security example within the server configuration guide, inhibiting the example to be run successfully. The missing <filename>EchoSecurityProxy.java</filename> file has now been restored, enabling the example to be run correctly.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-799</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-799">JBPAPP-799</ulink>: the seamejb3 example would generate a <code>FaceletException</code> error. This issue was caused from the inclusion of incorrect .jar files for the example. This CP update includes the correct .jar files, correcting the issue and allowing the example to execute correctly.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-783</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-783">JBPAPP-783</ulink>: There was an issue where a mechanism did not exist to shutdown JMS connections when an MDB encountered a <code>RuntimeException</code>. The ability to accomplish this is now included.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-746</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-746">JBPAPP-746</ulink>: There was a bug within the JavaServer Pages (JSP) compiler affecting Tomcat where the body of the doTag() method was empty. This meant that no html would be emitted. This fix for this Tomcat related issue has been included within this CP release.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-729</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-729">JBPAPP-729</ulink>: A wrong character set was being used for the decoding of URL parameters after a servlet redirect had occurred. Now fixed within this CP, URLs are decoded correctly after servelt redirects.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-529</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-529">JBPAPP-529</ulink>: JavaServer Pages (JSP) source code was exposed within the jmx-console when an error page was encountered. This issue is addressed by checking if the class is using an existing Bean from the requested scope or if it has instantiated a new one. If the one from the request scope is null the user is redirected to the displayMbeans page.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-295</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-295">JBPAPP-295</ulink>: The replicated Stateful Session Bean (SFSB) required optimization for use with Buddy Replication. After extensive testing and fixes, the optimization required is now included within this CP release.
+ </para>
+ </formalpara>
+
+<!-- Beginning of Core EAP issues -->
+
+ <!--<formalpara>
+ <title>JBPAPP-</title>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>: Information here
+ </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>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-909">JBPAPP-909</ulink>: Within the Hibernate component of the EAP the HashMap and HashSet iteration order changed from past releases because of support for JDK 1.6. However this has meant that the order of columns in union clauses and union-subclasses has changed, generating a slight impact on the components performance.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </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. Further details on these issues can be found in <ulink url="http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311486">JIRA</ulink>.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-351">JPBAPP-351</ulink>: During server shutdown, a NullPointerException occurs when using JBossAOP.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ -->
+<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
+
+</article>
Deleted: projects/docs/enterprise/4.3.3/readme/en-US/readme.ent
===================================================================
--- projects/docs/enterprise/4.3.3/readme/en-US/readme.ent 2008-09-04 01:00:04 UTC (rev 77923)
+++ projects/docs/enterprise/4.3.3/readme/en-US/readme.ent 2008-09-04 01:01:06 UTC (rev 77924)
@@ -1,3 +0,0 @@
-<!ENTITY HOLDER "Red Hat, Inc">
-<!ENTITY YEAR "2008">
-<!ENTITY VERSION "4.3.0.CP02">
Deleted: projects/docs/enterprise/4.3.3/readme/en-US/readme.xml
===================================================================
--- projects/docs/enterprise/4.3.3/readme/en-US/readme.xml 2008-09-04 01:00:04 UTC (rev 77923)
+++ projects/docs/enterprise/4.3.3/readme/en-US/readme.xml 2008-09-04 01:01:06 UTC (rev 77924)
@@ -1,626 +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 4.3</title>
- <section id="Messaging">
- <title>JBoss Messaging</title>
- <para>
- In JBoss Enterprise Application Platform 4.3, 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 JBoss Enterprise Application Platform 4.3 and will now provide a complete implementation of JAX-WS.
- </para>
- </section>
-
- </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.3</title>
- <formalpara>
- <title>Using CSP/JON</title>
- <para>Refer to <ulink url="https://network.jboss.com/confluence/display/DOC/Installing+a+Patch">https://network.jboss.com/confluence/display/DOC/Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch.</para>
- </formalpara>
- <!--
- <para>JBoss MQ is now replaced with JBoss Messaging as the JMS implementation shipped within JBoss Enterprise Application Platform &VERSION;. 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.3.0/en/source/jboss-eap-src-4.3.0-CP01.zip"> ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-CP02.zip</ulink>
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- </section>
- </section>
- <section id="Product-Support-and-License-Links">
- <title>
- Product Support and License Website Links
- </title>
- <formalpara>
- <title>Support Processes</title>
- <para>
- <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- Production Support Scope of Coverage
- </title>
- <para>
- <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink>
- </para>
- </formalpara>
-
-
- <formalpara>
- <title>
- Production Support Service Level Agreement
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- Developer Support Scope of Coverage
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- Developer Support Service Level Agreement
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- Product Update and Support Policy by Product
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- JBoss End User License Agreement
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink>
- </para>
- </formalpara>
- </section>
-
- <section id="Documentation">
- <title>
- Documentation
- </title>
- <para>
- Refer to the index.html file in the documentation directory for a list of included documentation.
- </para>
- <para>
- In the zip distribution, documentation for the Platform and its individual components is distributed in a separate zip file, <filename>jboss-eap-docs-<version>.zip</filename>.
- </para>
-
- <para>
- On a Linux system, the documentation is found in two rpms that will need to be installed manually. These rpms are <filename>jboss-seam-docs-<version>.noarch.rpm</filename>, and <filename>rh-eap-docs-<version>.noarch.rpm</filename>. For help with installing rpm packages on Red Hat Enterprise Linux, please refer to the Red Hat Knowledge base article located at <ulink url="http://kbase.redhat.com/faq/FAQ_35_198.shtm">http://kbase.redhat.com/faq/FAQ_35_198.shtm</ulink>
- </para>
- <para>
-
- <itemizedlist>
- <listitem>
- <para>
- <filename>Installation Guide</filename> explains how to install and verify the installation of JBoss Enteprise 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 will be supported in version 4.3.
- </para>
- </section>-->
-
- <section id="Issues-fixed-in-this-release">
- <title>
- Issues fixed in this release
- </title>
-
- <para>
- Following is a list of issues fixed in this release:
- </para>
- <formalpara>
- <title>JBoss Messaging</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-925">JBPAPP-925</ulink>: JBoss Messaging has been upgraded to version 1.4.0.SP3_CP03. This update includes numerious bug fixes that improves the overall component.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-920">JBPAPP-920</ulink>: The JBoss Messaging documentation was outdated. This CP release contains the JBoss Messaging 1.4.0.SP3_CP03 User Guide.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-900">JBPAPP-900</ulink>: The SQL default configuration had errors, causing an issue within hsqldb which uses this configuration. The issue with the default configuration has now been corrected.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-813">JBPAPP-813</ulink>: The Messaging client included a bug that would make it hang forever, creating a <code>ClusteredConnectionFactory</code> failover; steaming from a socket hang. This issue has now been rectified in this latest EAP release, creating a more stable Messaging component.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
-<!-- <formalpara>
- <title>JBoss Cache</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara> -->
- <formalpara>
- <title>JBoss Remoting</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-735">JBPAPP-735</ulink>: The JBoss Remoting component of the EAP has been upgraded to version 2.2.2.SP8. This upgrade includes numerious bug fixes.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Web Services</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-930">JBPAPP-930</ulink>: The upgrade to JBossWS Common 1.0.0.GA_CP01 is included wihtin this CP release.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-887">JBPAPP-887</ulink>: JBoss Java API for XML Redistries (JAXR) has been upgraded to version 1.2.0.SP1 which addresses various bugs.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-791">JBPAPP-791</ulink>: The JBoss Web Services Component has been upgraded to version 2.0.1.SP2_CP02. This upgrade incorporates various bug fixes and enhancements.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Seam</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-755">JBPAPP-755</ulink>: The Seam source readme.txt file required updated links to seamframework.org and mention the EAP instead of the JBoss AS. This file has been updated with the above changes for this release.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Hibernate</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-938">JBPAPP-938</ulink>: An unchanged parent entity would incorrectly have its version value incremented when part of a one to many relationship. This error has been rectified with this latest CP release by correcting an issue in the <filename>CollectionType.java</filename> file and adding the a new method called <methodname>testNoExtraUpdatesOnPersistentMergeVersionedWithCollection()</methodname> to <filename>MergeTest.java</filename>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-936">JBPAPP-936</ulink>: The <methodname>AnnotationBinder.mustBeSkipped</methodname> method had an incorrect hardcoded String-Reference to the <classname>org.hibernate.tool.instrument.javassist.FieldHandler</classname> class. This error has meant that the <emphasis>junitinstrument</emphasis> test was not running correctly. This issue has been fixed, with the correct package location of the class being referenced with the class name <classname>org.hibernate.bytecode.javassist.FieldHandler</classname> and the <emphasis>junitinstrument</emphasis> test now runs successfully.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-915">JBPAPP-915</ulink>: A merge operation would fail when there was a transient entity that was reachable by multiple paths and at least one of these paths did not cascade when undertaking a merge. This issue is fixed with the EAP 4.3 now supporting JDK 6.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-908">JBPAPP-908</ulink>: Hibernate proxy serialization was broken because the <classname>AbstractLazyInitializer</classname> class was not Serializable. This is now corrected within this CP release.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-899">JBPAPP-899</ulink>: There was an error within the entity manager where the methods <methodname>getSingleResult()</methodname> and <methodname>fetch()</methodname> would return a <code>NonUniqueResultException</code> because elements were now unique. This issue has been corrected with this CP release.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-859">JBPAPP-859</ulink>: The <classname>SchemaUpdate</classname> class has been enhanced with <option>output file name</option>, <option>delimiter</option>, <option>halt on error</option>, <option>format</option> options now avaliable.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-782">JBPAPP-782</ulink>: The <classname>MapBinder</classname> class had the ability to generate SQL statements that would not be supported by the Oracle 10g database. This was of particular concern for some EJB3 Persistence users on EAP and Oracle. This issue has now been rectified in this CP release.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
-<!-- <formalpara>
- <title>JBoss Transaction Service (JBossTS)</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara> -->
- <formalpara>
- <title>Security Issues</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- There are no Security Issues addressed with this CP releae.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-1004</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1004">JBPAPP-1004</ulink>: Previous versions of the EAP contained an incorrect <property>serialVersionUID</property> number, which interfered with backwards compatability. The correct <property>serialVersionUID</property> number is included with this release.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-972</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-972">JBPAPP-972</ulink>: JBoss Aspect-Oriented Programming (AOP) has been upgraded to version 1.5.GA_CP02.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-971</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-971">JBPAPP-971</ulink>: Javassist has been upgraded to version 3.8.0.GA, fixing numerious issues related to this class library.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-961</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-961">JBPAPP-961</ulink>: JBoss Web has been upgraded to version 2.0.0.GA CP06.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-944</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-944">JBPAPP-944</ulink>: <classname>ClusteredSession</classname> included logic that would skip session metadata replication if the only change was the timestamp. This issue was corrected by changing the default maximum interval between requests. The default interval is now 60 seconds and the value is now configurable. This attribute can be changed by adding an atribute to the <filename>jboss-service.xml</filename> file that resembles <programlisting><attribute name="MaxUnreplicatedInterval">30</attribute></programlisting>.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-926</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-926">JBPAPP-926</ulink>: A section in the Server Configuration Guide called <emphasis>Existing Entity Commands</emphasis> specified the wrong packages for some classes. This updated version of the Server Configuration Guide included with this CP, contains the correct package information for the classes affected.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-907</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-907">JBPAPP-907</ulink>: There was an issue where a deserialization bottleneck would occur in arrays for JDK 1.6. In order to rectify this issue, the following has been added to the <filename>run.conf</filename> file: <programlisting>-Dsun.lang.ClassLoader.allowArraySyntax=true</programlisting>.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-897</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-897">JBPAPP-897</ulink>: JBoss Transaction Services has been upgraded to version 4.2.3 SP5 CP02.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-895</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-895">JBPAPP-895</ulink>: The Java Messaging Service (JMS) connections needed to be consistently closed in reference to the J2EE Connector Architecture (JCA). These connections are now always closed to restrict exceptions.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-891</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-891">JBPAPP-891</ulink>: The monitoring tool <emphasis>Twiddle</emphasis> did not print out <code>invoke</code> results, even with the absense of a property editor for the returned object. Corrected within this CP release, <emphasis>Twiddle</emphasis> now calls the <methodname>toString()</methodname> method on returned objects when there is no property editor found.
- </para>
- </formalpara>
- <!-- <formalpara>
- <title>JBPAPP-878</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-878">JBPAPP-878</ulink>: There was a bug that caused the <property>STRICT_SERVLET_COMPLIANCE</property> property to return with false results, in terms of the Technology Compatability Kit (TCK). The property <property>STRICT_SERVLET_COMPLIANCE</property> no longer returns false results.
- </para>
- </formalpara> -->
- <formalpara>
- <title>JBPAPP-877</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-877">JBPAPP-877</ulink>: JBoss Serialization version 1.0.3GA would encounter <code>ClassCastExceptions</code> when being used. This update corrects this issue so that serialization functions correctly.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-867</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-867">JBPAPP-867</ulink>: An <interfacename>ExceptionSorter</interfacename> interface implementation should be provided for users of the IBM DB2 Data Server. This enhancement to the EAP is included within this CP release.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-864</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-864">JBPAPP-864</ulink>: Clustered proxy factories did not bind home proxies. This issue has been rectified by now supporting clustered home proxies for EJB3 beans. However, in order to
- avoid backwards compatibility issues, the load balance policy for home proxies has
- been hard coded to round robin. This is also the default policy for EJB2 home proxies.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-858</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-858">JBPAPP-858</ulink>: Allow for multiple instances to be setup on one machine using a subpackage method. This functionality has been added in this release with -bin files.
- </para>
- </formalpara>
- <para>
- It is important to note that a regular jbossas installation is required on the server first before installtion of the -bin. The -bin is for an additional installation only and cannot be used in place of a regular RPM jbossas installation. If you only have one version of the AS, it will have to be the regular RPM installation (or ZIP or installer for older versions).
- </para>
- <formalpara>
- <title>JBPAPP-857</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-857">JBPAPP-857</ulink>: The .rar file <filename>mail-ra.rar</filename> used within the application server to recieve email from using the JavaMail API, was missing from the distribution. This missing file has now been re-included.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-856</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-856">JBPAPP-856</ulink>: Support of the DeliveryActive MDB activation configuration property when deploying. This mechanism enables the ability to start and stop the consumption of Messages during deployment and is supported with this release.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-844</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-844">JBPAPP-844</ulink>: The MSSQL data source example was incompatible with SQL Server 2005. To fix this compatability issue, the <code>driver-class</code> has been updated from <code>com.microsoft.jdbc.sqlserver.SQLServerDriver</code> to <code>com.microsoft.sqlserver.jdbc.SQLServerDriver</code> and the default port for the <code>connection-url</code> has been changed from 1433 to 3918. With these changes the example now functions correctly under SQL Server 2005.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-815</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-815">JBPAPP-815</ulink>: An issue existed where if a DOCTYPE was added to the file <filename>-ds.xml</filename> and the option to <option>ValidateDTDs</option> was set to true in <filename>jbossjca-services.xml</filename>, validation errors would occur. This was found to be because of an issue with the <property>tx-connection-factory</property> element in <filename>jms-ds.xml</filename> which has since been fixed.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-805</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-805">JBPAPP-805</ulink>: There was a missing java file from the first security example within the server configuration guide, inhibiting the example to be run successfully. The missing <filename>EchoSecurityProxy.java</filename> file has now been restored, enabling the example to be run correctly.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-799</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-799">JBPAPP-799</ulink>: the seamejb3 example would generate a <code>FaceletException</code> error. This issue was caused from the inclusion of incorrect .jar files for the example. This CP update includes the correct .jar files, correcting the issue and allowing the example to execute correctly.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-783</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-783">JBPAPP-783</ulink>: There was an issue where a mechanism did not exist to shutdown JMS connections when an MDB encountered a <code>RuntimeException</code>. The ability to accomplish this is now included.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-746</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-746">JBPAPP-746</ulink>: There was a bug within the JavaServer Pages (JSP) compiler affecting Tomcat where the body of the doTag() method was empty. This meant that no html would be emitted. This fix for this Tomcat related issue has been included within this CP release.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-729</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-729">JBPAPP-729</ulink>: A wrong character set was being used for the decoding of URL parameters after a servlet redirect had occurred. Now fixed within this CP, URLs are decoded correctly after servelt redirects.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-529</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-529">JBPAPP-529</ulink>: JavaServer Pages (JSP) source code was exposed within the jmx-console when an error page was encountered. This issue is addressed by checking if the class is using an existing Bean from the requested scope or if it has instantiated a new one. If the one from the request scope is null the user is redirected to the displayMbeans page.
- </para>
- </formalpara>
- <formalpara>
- <title>JBPAPP-295</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-295">JBPAPP-295</ulink>: The replicated Stateful Session Bean (SFSB) required optimization for use with Buddy Replication. After extensive testing and fixes, the optimization required is now included within this CP release.
- </para>
- </formalpara>
-
-<!-- Beginning of Core EAP issues -->
-
- <!--<formalpara>
- <title>JBPAPP-</title>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>: Information here
- </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>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-909">JBPAPP-909</ulink>: Within the Hibernate component of the EAP the HashMap and HashSet iteration order changed from past releases because of support for JDK 1.6. However this has meant that the order of columns in union clauses and union-subclasses has changed, generating a slight impact on the components performance.
- </para>
- </listitem>
- </itemizedlist>
- </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. Further details on these issues can be found in <ulink url="http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311486">JIRA</ulink>.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-351">JPBAPP-351</ulink>: During server shutdown, a NullPointerException occurs when using JBossAOP.
- </para>
- </listitem>
- </itemizedlist>
- </section>
- -->
-</article>
More information about the jboss-cvs-commits
mailing list