[jboss-cvs] JBossAS SVN: r78515 - in projects/docs/enterprise: 4.3.3/readme/en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Sep 14 20:44:54 EDT 2008
Author: irooskov at redhat.com
Date: 2008-09-14 20:44:53 -0400 (Sun, 14 Sep 2008)
New Revision: 78515
Modified:
projects/docs/enterprise/4.2.5/readme/en-US/Release_Notes_CP05.xml
projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml
Log:
updated release notes for 4.3.3 and 4.2.5 with new unresolved JIRAs
Modified: projects/docs/enterprise/4.2.5/readme/en-US/Release_Notes_CP05.xml
===================================================================
--- projects/docs/enterprise/4.2.5/readme/en-US/Release_Notes_CP05.xml 2008-09-14 23:50:25 UTC (rev 78514)
+++ projects/docs/enterprise/4.2.5/readme/en-US/Release_Notes_CP05.xml 2008-09-15 00:44:53 UTC (rev 78515)
@@ -55,7 +55,7 @@
</para>
</section>
<section id="upgrade">
- <title>Upgrading from JBoss Enterprise Application Platform 4.2.0.CP02</title>
+ <title>Upgrading from JBoss Enterprise Application Platform 4.2.0.CP04</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>
@@ -136,7 +136,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="ftp://ftp.redhat.com/pub/redhat/jbeap/4.2.0/en/source/jboss-eap-src-4.2.0-CP03.zip"> ftp://ftp.redhat.com/pub/redhat/jbeap/4.2.0/en/source/jboss-eap-src-4.2.0-CP04.zip</ulink>
+ <ulink url="ftp://ftp.redhat.com/pub/redhat/jbeap/4.2.0/en/source/jboss-eap-src-4.2.0-CP05.zip"> ftp://ftp.redhat.com/pub/redhat/jbeap/4.2.0/en/source/jboss-eap-src-4.2.0-CP05.zip</ulink>
</para>
</listitem>
</itemizedlist>
@@ -275,174 +275,123 @@
<itemizedlist>
<listitem>
<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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1083">JBPAPP-1083</ulink>: Outer join support should be added for aliases of the <classname>DetachedCriteria</classname> class. To do this, the following methods have been added to the class:
</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ All variants of createAlias()
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ All variants of createCriteria()
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ All variants of setLockMode()
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ setComment()
+ </para>
+ </listitem>
+ </itemizedlist>
</listitem>
<listitem>
<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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1053">JBPAPP-1053</ulink>: Seam icefaces would generate an error stipulating that an instance of the <code>compiler.ExpressionFactory</code> feature could not be achieved. In this release, the application deploys successfully and without the instance issue.
</para>
</listitem>
<listitem>
<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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1046">JBPAPP-1046</ulink>: There was an error in the Spring example where if a user created an invalid booking, the example would still allow the booking to proceed. The booking would not be stored and an <exceptionname>IllegalStateException</exceptionname> would be generated when the user tried to start a new conversation. To rectify this issue, a rule element has been added into the <filename>pages.xml</filename> file to insure the validity of the booking.
</para>
</listitem>
<listitem>
<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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1044">JBPAPP-1044</ulink>: When undeploying specific Seam examples after interaction, a Null Pointer Exception (NPE) would occur. The list of affect examples are:
</para>
- </listitem>
- <listitem>
- <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>
- </listitem>
- <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>
+ <itemizedlist>
+ <listitem>
+ <para>
+ chatroom
+ </para>
</listitem>
- <listitem>
+ <listitem>
+ <para>
+ mail
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ registration
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ booking
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ dvdstore
+ </para>
+ </listitem>
+ </itemizedlist>
<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.
+ In this currect release, the NPE no longer occurs.
</para>
</listitem>
<listitem>
<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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1035">JBPAPP-1035</ulink>:All the books for the JBoss Enterprise Application Platform should have the word <emphasis>aspectized</emphasis> removed as this is not a true word and fails to convey any meaningful information. to fix this issue, the word <emphasis>aspectized</emphasis> has been removed from all documentation.
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1024">JBPAPP-1024</ulink>: The Tomcat Web Service component of the Application Server would generate a Null Pointer Exception (NPE) in the <classname>ExtendedFormAuthenticator</classname> class when trying to authenticate in a form after a session had timed out. In fixing this issue, the NPE has been removed from the login page.
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1008">JBPAPP-1008</ulink>: There was an error in the Server Configuration Guide xmbean example where the command given specified a deloyment configuration that did not exist. The deployment commands for the xmbean example now deploy to the default configuration of the server.
</para>
</listitem>
<listitem>
<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>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-969">JBPAPP-969</ulink>: An unchanged persistent entity which is a parent in a one to many relationship, would have its version number incorrectly incremented once a transaction commit had occured. This issue has been rectified by modifying the way objects are retrieved back into the target of the <literal>replace</literal> object within the <filename>CollectionType.java</filename> file.
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-933">JBPAPP-933</ulink>: When deploying an Enterprise JavaBeans 2 (EJB2) after starting a Service Bean with a Naming context associated with the applications class loader, the EJB2 will fail as it binds with the applications UnifiedClassLoader instead.
</para>
</listitem>
<listitem>
<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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-919">JBPAPP-919</ulink>: The Web Services stack was not able to be fully initialized and thus the first <methodname>webmethod </methodname> call is slow. In this latest version of the EAP, the Web Services stack is fully initialized.
</para>
</listitem>
<listitem>
<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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-882">JBPAPP-882</ulink>: The Java Server Faces (JSF) needed its libraries to be upgraded to 1.2_09-b01. This issue has been fixed by upgrading to version 1.2_09 of the libraries, which is no longer in beta.
</para>
</listitem>
<listitem>
<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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-730">JBPAPP-730</ulink>: The Clustering Section of the Server Configuration Guide needed to be updated with the latest information relevant to the EAP. To rectify this issue, the updated community clustering section (along with information from the relevant wiki) has replaced the outdated information.
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-596">JBPAPP-596</ulink>: Nulls were being returned in an array when toArray was called on a list of Xids in the Txmanager because the size of the array may not be the same. To fix this issue relating to JBossMQ, the <methodname>preparedXids.size()</methodname> method is not called to create a new Xid when calling the <methodname>preparedXids.toArray()</methodname> method.
</para>
</listitem>
- <listitem>
- <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>
- </listitem>
- <listitem>
- <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>
- </listitem>
- <listitem>
- <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>
- </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-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>
- <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>
- </listitem>
- <listitem>
- <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>
- </listitem>
- <listitem>
- <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>
- </listitem>
- <listitem>
- <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>
- </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>
- <listitem>
- <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>
- </listitem>
- <listitem>
- <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>
- </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>
- <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>
- <listitem>
- <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>
- </listitem>
- <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>
- <listitem>
- <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>
- </listitem>
- <listitem>
- <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>
- </listitem>
+
<!-- EXAMPLE
<listitem>
<para>
Modified: projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml
===================================================================
--- projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml 2008-09-14 23:50:25 UTC (rev 78514)
+++ projects/docs/enterprise/4.3.3/readme/en-US/Release_Notes_CP03.xml 2008-09-15 00:44:53 UTC (rev 78515)
@@ -52,11 +52,11 @@
<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.
+ 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</title>
+ <title>Upgrading from JBoss Enterprise Application Platform 4.3.0.CP02</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>
@@ -135,7 +135,7 @@
<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>
+ <ulink url="ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-CP03.zip"> ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-CP03.zip</ulink>
</para>
</listitem>
</itemizedlist>
@@ -277,133 +277,158 @@
<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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-885">JBPAPP-885</ulink>: An issue existed where if <methodname>DefaultRedeliveryDelay</methodname> or <methodname>RedeliveryDelay</methodname> was set to a value apart from zero, messages would not be redelivered even though the method <methodname>session.rollback()</methodname> had been called. Rectifying this issue, a redelivery delay of zero has been implemented.
</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>
+ </formalpara>
+ <!-- <formalpara>
<title>JBoss Cache</title>
<para>
<itemizedlist>
<listitem>
- <para>
- </para>
+
</listitem>
</itemizedlist>
</para>
</formalpara> -->
- <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> -->
<formalpara>
- <title>JBoss Web Services</title>
+ <title>JBoss Web</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-882">JBPAPP-882</ulink>: The Java Server Faces (JSF) needed its libraries to be upgraded to 1.2_09-b01. This issue has been fixed by upgrading to version 1.2_09 of the libraries, which is no longer in beta.
</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>
+ <title>JBoss Web Services</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-919">JBPAPP-919</ulink>: The Web Services stack was not able to be fully initialized and thus the first <methodname>webmethod </methodname> call is slow. In this latest version of the EAP, the Web Services stack is fully initialized.
</para>
</listitem>
- </itemizedlist>
+ </itemizedlist>
</para>
</formalpara>
<formalpara>
- <title>JBoss Hibernate</title>
+ <title>JBoss Seam</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>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1053">JBPAPP-1053</ulink>: Seam icefaces would generate an error stipulating that an instance of the <code>compiler.ExpressionFactory</code> feature could not be achieved. In this release, the application deploys successfully and without the instance issue.
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1046">JBPAPP-1046</ulink>: There was an error in the Spring example where if a user created an invalid booking, the example would still allow the booking to proceed. The booking would not be stored and an <exceptionname>IllegalStateException</exceptionname> would be generated when the user tried to start a new conversation. To rectify this issue, a rule element has been added into the <filename>pages.xml</filename> file to insure the validity of the booking.
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1044">JBPAPP-1044</ulink>: When undeploying specific Seam examples after interaction, a Null Pointer Exception (NPE) would occur. The list of affect examples are:
</para>
- </listitem>
- <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ chatroom
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ mail
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ registration
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ booking
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ dvdstore
+ </para>
+ </listitem>
+ </itemizedlist>
<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.
+ In this currect release, the NPE no longer occurs.
</para>
</listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Hibernate</title>
+ <para>
+ <itemizedlist>
<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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1083">JBPAPP-1083</ulink>: Outer join support should be added for aliases of the <classname>DetachedCriteria</classname> class. To do this, the following methods have been added to the class:
</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ All variants of createAlias()
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ All variants of createCriteria()
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ All variants of setLockMode()
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ setComment()
+ </para>
+ </listitem>
+ </itemizedlist>
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-969">JBPAPP-969</ulink>: An unchanged persistent entity which is a parent in a one to many relationship, would have its version number incorrectly incremented once a transaction commit had occured. This issue has been rectified by modifying the way objects are retrieved back into the target of the <literal>replace</literal> object within the <filename>CollectionType.java</filename> file.
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-940">JBPAPP-940</ulink>: The hibernate tests <code>org.hibernate.test.jpa.lock.JPALockTest</code> and <code>org.hibernate.test.tm.CMTTest</code> would not conclude when executed on a DB2 server. To overcome this problem, the method <methodname>doesReadCommittedCauseWritersToBlockReaders()</methodname>, which returns true if executed correctly, has been added to DB2Dialect in order to override Dialect's default settings.
</para>
</listitem>
</itemizedlist>
</para>
</formalpara>
-<!-- <formalpara>
+ <!-- <formalpara>
<title>JBoss Transaction Service (JBossTS)</title>
<para>
<itemizedlist>
<listitem>
- <para>
- </para>
+
</listitem>
</itemizedlist>
</para>
@@ -414,173 +439,50 @@
<itemizedlist>
<listitem>
<para>
- There are no Security Issues addressed with this CP releae.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1024">JBPAPP-1024</ulink>: The Tomcat Web Service component of the Application Server would generate a Null Pointer Exception (NPE) in the <classname>ExtendedFormAuthenticator</classname> class when trying to authenticate in a form after a session had timed out. In fixing this issue, the NPE has been removed from the login page.
</para>
</listitem>
</itemizedlist>
</para>
</formalpara>
<formalpara>
- <title>JBPAPP-1004</title>
+ <title>Documentation</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.
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1035">JBPAPP-1035</ulink>:All the books for the JBoss Enterprise Application Platform should have the word <emphasis>aspectized</emphasis> removed as this is not a true word and fails to convey any meaningful information. to fix this issue, the word <emphasis>aspectized</emphasis> has been removed from all documentation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1008">JBPAPP-1008</ulink>: There was an error in the Server Configuration Guide xmbean example where the command given specified a deloyment configuration that did not exist. The deployment commands for the xmbean example now deploy to the default configuration of the server.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-730">JBPAPP-730</ulink>: The Clustering Section of the Server Configuration Guide needed to be updated with the latest information relevant to the EAP. To rectify this issue, the updated community clustering section (along with information from the relevant wiki) has replaced the outdated information.
+ </para>
+ </listitem>
+ </itemizedlist>
</para>
</formalpara>
<formalpara>
- <title>JBPAPP-972</title>
+ <title>JBPAPP-933</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-933">JBPAPP-933</ulink>: When deploying an Enterprise JavaBeans 2 (EJB2) after starting a Service Bean with a Naming context associated with the applications class loader, the EJB2 will fail as it binds with the applications UnifiedClassLoader instead.
</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-</title>
+
+ </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 -->
More information about the jboss-cvs-commits
mailing list