[jboss-cvs] JBossAS SVN: r96398 - projects/docs/enterprise/4.3.7/Release_Notes/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Nov 15 23:10:59 EST 2009
Author: laubai
Date: 2009-11-15 23:10:58 -0500 (Sun, 15 Nov 2009)
New Revision: 96398
Added:
projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.ent
projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.xml
Removed:
projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP06.ent
projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP06.xml
Log:
Updated .xml file names.
Deleted: projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP06.ent
===================================================================
--- projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP06.ent 2009-11-16 03:56:20 UTC (rev 96397)
+++ projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP06.ent 2009-11-16 04:10:58 UTC (rev 96398)
@@ -1,3 +0,0 @@
-<!ENTITY HOLDER "Red Hat, Inc">
-<!ENTITY YEAR "2009">
-<!ENTITY VERSION "4.3.0.CP06">
Deleted: projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP06.xml
===================================================================
--- projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP06.xml 2009-11-16 03:56:20 UTC (rev 96397)
+++ projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP06.xml 2009-11-16 04:10:58 UTC (rev 96398)
@@ -1,469 +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="Component_Versions">
- <title>Component Versions</title>
- <para>
- This section details the versions of the components which create the Enterprise Application Platform 4.3 that can be found in this Cumulative Patch release.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- JBoss Application Server 4.2.z
- </para>
- </listitem>
- <listitem>
- <para>
- Hibernate Core 3.2.4.SP1.CP08
- </para>
- </listitem>
- <listitem>
- <para>
- Hibernate Annotations 3.3.1.GA_CP01
- </para>
- </listitem>
- <listitem>
- <para>
- Hibernate Entity Manager 3.3.2.GA
- </para>
- </listitem>
- <listitem>
- <para>
- Hibernate Validator 3.0.0.GA
- </para>
- </listitem>
- <listitem>
- <para>
- JAF 1.2_10
- </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 Messaging 1.4.0.SP3-CP08.patch01
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Remoting 2.2.3
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Transactions 4.2.3.SP5.CP05
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Web 2.0.0.CP10
- </para>
- </listitem>
- <listitem>
- <para>
- JBoss Web Services 2.0.1.SP2_CP06
- </para>
- </listitem>
- <listitem>
- <para>
- JGroups 2.4.6
- </para>
- </listitem>
- <listitem>
- <para>
- JSF 1.2_10
- </para>
- </listitem>
- <listitem>
- <para>
- Seam 1.2.1.AP
- </para>
- </listitem>
- <listitem>
- <para>
- Xalan 2.7.0.patch02
- </para>
- </listitem>
- </itemizedlist>
- <note>
- <para>
- The Enterprise Application Platform Server has been redefined for the enterprise market to a level where direct association to a community release can no longer be drawn.
- </para>
- </note>
- </section>
- <section id="Installation_Notes">
- <title>Installation and Migration Notes</title>
- <para>
- This section contains information related to installing or upgrading to JBoss Enterprise Application Platform version &VERSION;, including hardware and platform requirements and prerequisites.
- </para>
- <important>
- <para>
- The Enterprise Application Platform 4.3.0.CP05_FP01 release will work on this Cumulative Patch release; there will be no 4.3.0.CP06_FP01 release.
- </para>
- </important>
- <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 or 1.6. 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.0.CP05</title>
- <formalpara>
- <title>Using CSP/JON</title>
- <para>Refer to <ulink url="https://network.jboss.com/confluence/display/DOC/Installing+a+Patch">https://network.jboss.com/confluence/display/DOC/Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch.</para>
- </formalpara>
- <!--
- <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-CP06.zip"> ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-CP06.zip</ulink>
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- </section>
- </section>
- <section id="Product-Support-and-License-Links">
- <title>
- Product Support and License Website Links
- </title>
- <formalpara>
- <title>Support Processes</title>
- <para>
- <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- Production Support Scope of Coverage
- </title>
- <para>
- <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink>
- </para>
- </formalpara>
-
-
- <formalpara>
- <title>
- Production Support Service Level Agreement
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- Developer Support Scope of Coverage
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- Developer Support Service Level Agreement
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- Product Update and Support Policy by Product
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink>
- </para>
- </formalpara>
-
- <formalpara>
- <title>
- JBoss End User License Agreement
- </title>
-
- <para>
- <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink>
- </para>
- </formalpara>
- </section>
-
- <section id="Documentation">
- <title>
- Documentation
- </title>
- <para>
- Refer to the index.html file in the documentation directory for a list of included documentation.
- </para>
- <para>
- In the zip distribution, documentation for the Platform and its individual components is distributed in a separate zip file, <filename>jboss-eap-docs-<version>.zip</filename>.
- </para>
-
- <para>
- On a Linux system, the documentation is found in two rpms that will need to be installed manually. These rpms are <filename>jboss-seam-docs-<version>.noarch.rpm</filename>, and <filename>rh-eap-docs-<version>.noarch.rpm</filename>. For help with installing rpm packages on Red Hat Enterprise Linux, please refer to the Red Hat Knowledge base article located at <ulink url="http://kbase.redhat.com/faq/FAQ_35_198.shtm">http://kbase.redhat.com/faq/FAQ_35_198.shtm</ulink>
- </para>
- <para>
-
- <itemizedlist>
- <listitem>
- <para>
- <filename>Installation Guide</filename> explains how to install and verify the installation of JBoss Enterprise Application Platform using different installation modes.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>Getting Started</filename> details the directory structure of the platform and a quick tour of the Application Server and different configuration sets and services. Using a simple web application it illustrates the use of JSF-EJB3 components and how to use Seam to integrate the JSF and EJB3 components.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>Server Configuration Guide</filename> explains all administrative and configuration functions in detail.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- <para>
- Updated versions of the documentation with errata and additional information, example application code, as well as the most recent version of the release notes may be accessed via the web from <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>.
- </para>
- </section>
- <!--<section id="JSR-181">
- <title>
- JSR-181 support
- </title>
-
- <para>
- JSR-181 related functionality is not supported in this version of the JBoss Enterprise Application Platform. This functionality 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>
- The JBoss Messaging component of the Enterprise Application Platform has been upgraded to version 1.4.0.SP3-CP08.patch01. A list of the included fixes is as follows:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2259">JBPAPP-2259</ulink>: By increasing the allowed number of servers that are connected to a single host to 65535 in the <ulink url="http://jira.jboss.com/jira/browse/JBMESSAGING-1614">JBMESSAGING-1614</ulink> feature update, a unique key violation could occur. If the sending rate of messages within one node was equal to or greater than 32767 messages per millisecond (short.MAX_VALUE), and those messages were all stored in the database at the time, this would lead to a circumstance where two messages may have had identical ID numbers.
- </para>
- <para>
- This Cumulative Patch release corrects this issue by updating the <filename>RotatingID.java</filename> and <filename>NullPersistenceManager.java</filename> files to decrease the allowed number of servers that are connected to a single host to 1023. The <filename>RotatingID.java</filename> file has also been modified to alter the message counter so that the format is now (beginning at the highest bit):
- </para>
- <itemizedlist>
- <listitem>
- <para>
- First 10 bits are the node ID
- </para>
- </listitem>
- <listitem>
- <para>
- Next 39 bits are the 4th to 42nd bits of system time
- </para>
- </listitem>
- <listitem>
- <para>
- Next 15 bits are the rotating counter
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- </section>
- <section id="Known_Issues_with_this_release">
- <title>
- Known Issues with this release
- </title>
- <para>
- Following is a list of known issues at the time of release.
- </para>
- <formalpara>
- <title>General Known Issues</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1774">JBPAPP-1774</ulink>: The JBoss Enterprise Application Platform RPM cannot be installed with only the OpenJDK distribution.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1286">JBPAPP-1286</ulink>: Footnotes within documentation tables and lists do not appear within PDFs. This issue resides within FOP and currently no workaround exists. Where possible footnotes are not used in the circumstances mentioned, however in documents such as the Release Notes the web address of a documented issue is automatically generated as a footnote and places a number beside that of the documented issue, referencing a footnote that does not appear.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- <formalpara>
- <title>Hibernate Known Issues</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1709">JBPAPP-1709</ulink>: The JPA spec defines the constant with a value that has a typo in the class name:
- </para>
-<programlisting>
-javax.persistence.Persistence.PERSISTENCE_PROVIDER = "javax.persistence.spi.PeristenceProvider"
-</programlisting>
- <para>
- The version of <filename>ejb3-persistence.jar</filename> released in EAP is non-compliant with the JPA spec because it sets the correct classname (without the typo) for this constant.
- </para>
- <para>
- Javadoc for <methodname>javax.persistence.Query.getSingleResult()</methodname> says that the <exceptionname>EntityNotFoundException</exceptionname> will be generated if there is no result. The Javadoc should have mentioned the <exceptionname>NoResultException</exceptionname> instead.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-953">JBPAPP-953</ulink>: Hibernate Core and Annotations do not currently support the Hypersonic 1.8.0.8 database. Support for the version 1.8.0.8 of the Hypersonic database is no longer planned for future releases.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </formalpara>
- </section>
-<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
-
-</article>
Added: projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.ent
===================================================================
--- projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.ent (rev 0)
+++ projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.ent 2009-11-16 04:10:58 UTC (rev 96398)
@@ -0,0 +1,3 @@
+<!ENTITY HOLDER "Red Hat, Inc">
+<!ENTITY YEAR "2009">
+<!ENTITY VERSION "4.3.0.CP06">
Added: projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.xml
===================================================================
--- projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.xml (rev 0)
+++ projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.xml 2009-11-16 04:10:58 UTC (rev 96398)
@@ -0,0 +1,469 @@
+<?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="Component_Versions">
+ <title>Component Versions</title>
+ <para>
+ This section details the versions of the components which create the Enterprise Application Platform 4.3 that can be found in this Cumulative Patch release.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ JBoss Application Server 4.2.z
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Core 3.2.4.SP1.CP08
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Annotations 3.3.1.GA_CP01
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Entity Manager 3.3.2.GA
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Hibernate Validator 3.0.0.GA
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JAF 1.2_10
+ </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 Messaging 1.4.0.SP3-CP08.patch01
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Remoting 2.2.3
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Transactions 4.2.3.SP5.CP05
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Web 2.0.0.CP10
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JBoss Web Services 2.0.1.SP2_CP06
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JGroups 2.4.6
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JSF 1.2_10
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Seam 1.2.1.AP
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Xalan 2.7.0.patch02
+ </para>
+ </listitem>
+ </itemizedlist>
+ <note>
+ <para>
+ The Enterprise Application Platform Server has been redefined for the enterprise market to a level where direct association to a community release can no longer be drawn.
+ </para>
+ </note>
+ </section>
+ <section id="Installation_Notes">
+ <title>Installation and Migration Notes</title>
+ <para>
+ This section contains information related to installing or upgrading to JBoss Enterprise Application Platform version &VERSION;, including hardware and platform requirements and prerequisites.
+ </para>
+ <important>
+ <para>
+ The Enterprise Application Platform 4.3.0.CP05_FP01 release will work on this Cumulative Patch release; there will be no 4.3.0.CP06_FP01 release.
+ </para>
+ </important>
+ <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 or 1.6. 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.0.CP05</title>
+ <formalpara>
+ <title>Using CSP/JON</title>
+ <para>Refer to <ulink url="https://network.jboss.com/confluence/display/DOC/Installing+a+Patch">https://network.jboss.com/confluence/display/DOC/Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch.</para>
+ </formalpara>
+ <!--
+ <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-CP06.zip"> ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-CP06.zip</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ </section>
+ </section>
+ <section id="Product-Support-and-License-Links">
+ <title>
+ Product Support and License Website Links
+ </title>
+ <formalpara>
+ <title>Support Processes</title>
+ <para>
+ <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ Production Support Scope of Coverage
+ </title>
+ <para>
+ <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink>
+ </para>
+ </formalpara>
+
+
+ <formalpara>
+ <title>
+ Production Support Service Level Agreement
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ Developer Support Scope of Coverage
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ Developer Support Service Level Agreement
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ Product Update and Support Policy by Product
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink>
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>
+ JBoss End User License Agreement
+ </title>
+
+ <para>
+ <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink>
+ </para>
+ </formalpara>
+ </section>
+
+ <section id="Documentation">
+ <title>
+ Documentation
+ </title>
+ <para>
+ Refer to the index.html file in the documentation directory for a list of included documentation.
+ </para>
+ <para>
+ In the zip distribution, documentation for the Platform and its individual components is distributed in a separate zip file, <filename>jboss-eap-docs-<version>.zip</filename>.
+ </para>
+
+ <para>
+ On a Linux system, the documentation is found in two rpms that will need to be installed manually. These rpms are <filename>jboss-seam-docs-<version>.noarch.rpm</filename>, and <filename>rh-eap-docs-<version>.noarch.rpm</filename>. For help with installing rpm packages on Red Hat Enterprise Linux, please refer to the Red Hat Knowledge base article located at <ulink url="http://kbase.redhat.com/faq/FAQ_35_198.shtm">http://kbase.redhat.com/faq/FAQ_35_198.shtm</ulink>
+ </para>
+ <para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>Installation Guide</filename> explains how to install and verify the installation of JBoss Enterprise Application Platform using different installation modes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>Getting Started</filename> details the directory structure of the platform and a quick tour of the Application Server and different configuration sets and services. Using a simple web application it illustrates the use of JSF-EJB3 components and how to use Seam to integrate the JSF and EJB3 components.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>Server Configuration Guide</filename> explains all administrative and configuration functions in detail.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ Updated versions of the documentation with errata and additional information, example application code, as well as the most recent version of the release notes may be accessed via the web from <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>.
+ </para>
+ </section>
+ <!--<section id="JSR-181">
+ <title>
+ JSR-181 support
+ </title>
+
+ <para>
+ JSR-181 related functionality is not supported in this version of the JBoss Enterprise Application Platform. This functionality 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>
+ The JBoss Messaging component of the Enterprise Application Platform has been upgraded to version 1.4.0.SP3-CP08.patch01. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2259">JBPAPP-2259</ulink>: By increasing the allowed number of servers that are connected to a single host to 65535 in the <ulink url="http://jira.jboss.com/jira/browse/JBMESSAGING-1614">JBMESSAGING-1614</ulink> feature update, a unique key violation could occur. If the sending rate of messages within one node was equal to or greater than 32767 messages per millisecond (short.MAX_VALUE), and those messages were all stored in the database at the time, this would lead to a circumstance where two messages may have had identical ID numbers.
+ </para>
+ <para>
+ This Cumulative Patch release corrects this issue by updating the <filename>RotatingID.java</filename> and <filename>NullPersistenceManager.java</filename> files to decrease the allowed number of servers that are connected to a single host to 1023. The <filename>RotatingID.java</filename> file has also been modified to alter the message counter so that the format is now (beginning at the highest bit):
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ First 10 bits are the node ID
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Next 39 bits are the 4th to 42nd bits of system time
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Next 15 bits are the rotating counter
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ </section>
+ <section id="Known_Issues_with_this_release">
+ <title>
+ Known Issues with this release
+ </title>
+ <para>
+ Following is a list of known issues at the time of release.
+ </para>
+ <formalpara>
+ <title>General Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1774">JBPAPP-1774</ulink>: The JBoss Enterprise Application Platform RPM cannot be installed with only the OpenJDK distribution.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1286">JBPAPP-1286</ulink>: Footnotes within documentation tables and lists do not appear within PDFs. This issue resides within FOP and currently no workaround exists. Where possible footnotes are not used in the circumstances mentioned, however in documents such as the Release Notes the web address of a documented issue is automatically generated as a footnote and places a number beside that of the documented issue, referencing a footnote that does not appear.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Hibernate Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1709">JBPAPP-1709</ulink>: The JPA spec defines the constant with a value that has a typo in the class name:
+ </para>
+<programlisting>
+javax.persistence.Persistence.PERSISTENCE_PROVIDER = "javax.persistence.spi.PeristenceProvider"
+</programlisting>
+ <para>
+ The version of <filename>ejb3-persistence.jar</filename> released in EAP is non-compliant with the JPA spec because it sets the correct classname (without the typo) for this constant.
+ </para>
+ <para>
+ Javadoc for <methodname>javax.persistence.Query.getSingleResult()</methodname> says that the <exceptionname>EntityNotFoundException</exceptionname> will be generated if there is no result. The Javadoc should have mentioned the <exceptionname>NoResultException</exceptionname> instead.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-953">JBPAPP-953</ulink>: Hibernate Core and Annotations do not currently support the Hypersonic 1.8.0.8 database. Support for the version 1.8.0.8 of the Hypersonic database is no longer planned for future releases.
+ </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