[jboss-cvs] JBossAS SVN: r82299 - in projects/docs/enterprise: 4.3.3.1/readme/en-US and 1 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Dec 16 00:49:19 EST 2008
Author: irooskov at redhat.com
Date: 2008-12-16 00:49:18 -0500 (Tue, 16 Dec 2008)
New Revision: 82299
Modified:
projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml
projects/docs/enterprise/4.3.3.1/readme/en-US/Release_Notes_CP03_FP01.xml
projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
Log:
updated release notes with new JIRAs
Modified: projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml
===================================================================
--- projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml 2008-12-16 05:08:01 UTC (rev 82298)
+++ projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml 2008-12-16 05:49:18 UTC (rev 82299)
@@ -272,17 +272,200 @@
<para>
Following is a list of issues fixed in this release:
</para>
- <itemizedlist>
-
-<!-- EXAMPLE
- <listitem>
- <para>
- <ulink url="http://jira.jboss.org/jira/browse/JBPAPP-806">JBPAPP-806</ulink>: SSLSessionInterceptor had a copy/paste error in the invokeHome method
-
- </para>
- </listitem>
--->
- </itemizedlist>
+ <formalpara>
+ <title>JBoss Cache</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Remoting</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Web</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1493">JBPAPP-1493</ulink>: An error would be shown on occassion by <emphasis>Internet Explorer</emphasis> because xml content would not be sent when <emphasis>PROPFIND</emphasis> requests were being used. This has been fixed by creating a new method within <filename>WebdavServlet.java</filename> that overrides the <methodname>DefaultServlet</methodname> implementation for servlet request processing and testing for input before launching the <methodname>DocumentBuilder</methodname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1470">JBPAPP-1470</ulink>: When using APR (Apache Portable Runtime) on any operating system other than those which use the Linux Kernal 2.4 or newer, the <parameter>deferAccept</parameter> option would be set to false in the <methodname>AprEndpoint</methodname>. This may lead to a <exceptionname>NullPointerException</exceptionname> as the <methodname>accepter</methodname> thread starts to process a request while also calling for a <methodname>poller</methodname> before initialization. The issue has been resolved by moving the <methodname>acceptor</methodname> threads to being executed last when starting the <methodname>AprEndpoint</methodname>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Web Services</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <!-- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1439">JBPAPP-1439</ulink>: -->
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Seam</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Hibernate</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1496">JBPAPP-1496</ulink>: A memory leak existed because of an unclosed <emphasis>ResultSet</emphasis> when using the <emphasis>Identity</emphasis> generator option. To close the memory leak, the <emphasis>ResultSet</emphasis> is checked to make sure it is closed before returning the generated itentity value.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1480">JBPAPP-1480</ulink>: Hibernate would attempt to read from an invalid column in the collection result set when the following conditions were present:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Instances of a subclass were contained in a collection.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The subclasses were single-table and used a <join> (table-per-subclass with discriminator).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <join> portion of the subclass contained at least 3 of its own columns.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <join> tables were fetched by select and not the default method for this task.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ To fix this isue the <filename>AbstractEntityPersister.java</filename> file was updated so that the <varname>columnNumber</varname> variable is passed to the <methodname>subclassColumnSelectableClosure</methodname> method instead of an increment of the for loop variable <varname>i</varname>.
+ </para>
+ <para>
+ <filename>CollectionTest.java</filename> has also been updated and <filename>Animal.java</filename>, <filename>Mammal.java</filename>, <filename>Zoo.hbm.xml</filename> and <filename>Zoo.java</filename> have been added for testing purposes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1467">JBPAPP-1467</ulink>: A <exceptionname>PropertyValueException</exceptionname> would occur when merging a detached instance of a <classname>One</classname> class that contains a new <classname>Many</classname> class instance and if and only if the <classname>One</classname> class was previously loaded as a proxy during the same transaction. The files <filename>StatefulPersistenceContext.java</filename>, <filename>BackrefPropertyAccessor.java</filename>, <filename>BackrefTest.java</filename> and <filename>Child.java</filename> have been updated to check for the proxy issue in the mergining and once the proxy entity is found the <methodname>mergeMap</methodname> is updated to deal with this eventuality.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <!-- <formalpara>
+ <title>JBoss Transaction Service (JBossTS)</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara> -->
+ <formalpara>
+ <title>Security Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Documentation</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Core Server</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1479">JBPAPP-1479</ulink>: Within the different distributions of the EAP that are 4.2 and 4.3, both the <filename>JBossMQ</filename> and <filename>JBoss Messaging</filename> application policies have been present within the <filename>login-config.xml</filename> file, when <filename>JBossMQ</filename> is only included in the 4.2 distribution and <filename>JBoss Messaging</filename> is similarly only included in the 4.3 distribution.
+ </para>
+ <para>
+ This has been rectified in this release by modifying <filename>build.xml</filename> and <filename>login-config.xml</filename> to differentiate between requirements for each individial distribution.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1460">JBPAPP-1460</ulink>: The JavaServer Faces (JSF) has been updated to version 1.2_10 for this EAP release. This update corrects numerious bugs and details on these fixes can be found at <ulink url="https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html">https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1366">JBPAPP-1366</ulink>: Creation of the EJB <filename>TIMERS</filename> table fails when the <option>Oracle</option> schema is specified. To correct this the <filename>GeneralPurposeDatabasePersistencePlugin.java</filename> file has been updated with a calling to an new <methodname>SQLUtil.fixConstraintName</methodname> function which changes all dots in a constraint name to underscores. This ensures that constraint names are compatable with Oracle.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1307">JBPAPP-1307</ulink>: The Persistence Unit (PU) root was incorrectly detected within deployments that contained nested <filename>.jar</filename> files. The root PU was being detected as the first nested <filename>.jar</filename> encountered instead of being the deployment which contains the <filename>persistence.xml</filename> file. To make sure that the PU root is always set correctly, the <filename>JmxDeploymentUnit.java</filename> file has been updated with the removal of testing for the url being null and the <parameter>deploymentInfo.parent</parameter> not being null. This means that the url is now always taken straight from the <parameter>extractDescriptorUrl</parameter> of <filename>META-INF/persistence.xml</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1267">JBPAPP-1267</ulink>: <classname>UserTransaction</classname> (UT) was not able to be deployed with a clustered proxy that supported sticky transactions correctly. This has been fixed by modifying numerious files which make <classname>UserTransaction</classname> deployable with transaction sticky load balance policies.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1002">JBPAPP-1002</ulink>: Bean Managed Transactions (BMT) Stateful Session Beans used to be logged when transactions were not completed between invocations. However this was an error as BMT Stateful Session Beans are allowed to have this occurance and so this logging measure has been removed in this EAP update.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-529">JBPAPP-529</ulink>: JMX source code was being exposed to the user when a <exceptionname>HTTP Status 500</exceptionname> exception would occur. To correct this, an error page <filename>genericError.jsp</filename> has been created and is now displayed whenever a <exceptionname>HTTP Status 500</exceptionname> exception occurs.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
</section>
<section id="Known_Issues_with_this_release">
<title>
Modified: projects/docs/enterprise/4.3.3.1/readme/en-US/Release_Notes_CP03_FP01.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/readme/en-US/Release_Notes_CP03_FP01.xml 2008-12-16 05:08:01 UTC (rev 82298)
+++ projects/docs/enterprise/4.3.3.1/readme/en-US/Release_Notes_CP03_FP01.xml 2008-12-16 05:49:18 UTC (rev 82299)
@@ -1,6 +1,6 @@
<?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">
-<article id="JBEAP-Release-Notes" status="draft">
+<article id="JBEAP-Release-Notes">
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/>
<section id="Overview">
<title>Overview</title>
Modified: projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
===================================================================
--- projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml 2008-12-16 05:08:01 UTC (rev 82298)
+++ projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml 2008-12-16 05:49:18 UTC (rev 82299)
@@ -277,11 +277,12 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
</para>
</listitem>
</itemizedlist>
</para>
+ </formalpara>
<formalpara>
<title>JBoss Cache</title>
<para>
@@ -300,7 +301,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-2</ulink>:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
</para>
</listitem>
</itemizedlist>
@@ -312,9 +313,14 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1493">JBPAPP-1493</ulink>: An error would be shown on occassion by <emphasis>Internet Explorer</emphasis> because xml content would not be sent when <emphasis>PROPFIND</emphasis> requests were being used. This has been fixed by creating a new method within <filename>WebdavServlet.java</filename> that overrides the <methodname>DefaultServlet</methodname> implementation for servlet request processing and testing for input before launching the <methodname>DocumentBuilder</methodname>.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1470">JBPAPP-1470</ulink>: When using APR (Apache Portable Runtime) on any operating system other than those which use the Linux Kernal 2.4 or newer, the <parameter>deferAccept</parameter> option would be set to false in the <methodname>AprEndpoint</methodname>. This may lead to a <exceptionname>NullPointerException</exceptionname> as the <methodname>accepter</methodname> thread starts to process a request while also calling for a <methodname>poller</methodname> before initialization. The issue has been resolved by moving the <methodname>acceptor</methodname> threads to being executed last when starting the <methodname>AprEndpoint</methodname>.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
@@ -324,12 +330,12 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
+ <!-- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1439">JBPAPP-1439</ulink>: -->
</para>
</listitem>
</itemizedlist>
</para>
- </formalpara>
+ </formalpara>
<formalpara>
<title>JBoss Seam</title>
<para>
@@ -348,9 +354,47 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1496">JBPAPP-1496</ulink>: A memory leak existed because of an unclosed <emphasis>ResultSet</emphasis> when using the <emphasis>Identity</emphasis> generator option. To close the memory leak, the <emphasis>ResultSet</emphasis> is checked to make sure it is closed before returning the generated itentity value.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1480">JBPAPP-1480</ulink>: Hibernate would attempt to read from an invalid column in the collection result set when the following conditions were present:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Instances of a subclass were contained in a collection.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The subclasses were single-table and used a <join> (table-per-subclass with discriminator).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <join> portion of the subclass contained at least 3 of its own columns.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <join> tables were fetched by select and not the default method for this task.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ To fix this isue the <filename>AbstractEntityPersister.java</filename> file was updated so that the <varname>columnNumber</varname> variable is passed to the <methodname>subclassColumnSelectableClosure</methodname> method instead of an increment of the for loop variable <varname>i</varname>.
+ </para>
+ <para>
+ <filename>CollectionTest.java</filename> has also been updated and <filename>Animal.java</filename>, <filename>Mammal.java</filename>, <filename>Zoo.hbm.xml</filename> and <filename>Zoo.java</filename> have been added for testing purposes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1467">JBPAPP-1467</ulink>: A <exceptionname>PropertyValueException</exceptionname> would occur when merging a detached instance of a <classname>One</classname> class that contains a new <classname>Many</classname> class instance and if and only if the <classname>One</classname> class was previously loaded as a proxy during the same transaction. The files <filename>StatefulPersistenceContext.java</filename>, <filename>BackrefPropertyAccessor.java</filename>, <filename>BackrefTest.java</filename> and <filename>Child.java</filename> have been updated to check for the proxy issue in the mergining and once the proxy entity is found the <methodname>mergeMap</methodname> is updated to deal with this eventuality.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
@@ -389,9 +433,48 @@
</para>
</formalpara>
<formalpara>
- <title>JBPAPP-</title>
+ <title>Core Server</title>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1479">JBPAPP-1479</ulink>: Within the different distributions of the EAP that are 4.2 and 4.3, both the <filename>JBossMQ</filename> and <filename>JBoss Messaging</filename> application policies have been present within the <filename>login-config.xml</filename> file, when <filename>JBossMQ</filename> is only included in the 4.2 distribution and <filename>JBoss Messaging</filename> is similarly only included in the 4.3 distribution.
+ </para>
+ <para>
+ This has been rectified in this release by modifying <filename>build.xml</filename> and <filename>login-config.xml</filename> to differentiate between requirements for each individial distribution.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1460">JBPAPP-1460</ulink>: The JavaServer Faces (JSF) has been updated to version 1.2_10 for this EAP release. This update corrects numerious bugs and details on these fixes can be found at <ulink url="https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html">https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1366">JBPAPP-1366</ulink>: Creation of the EJB <filename>TIMERS</filename> table fails when the <option>Oracle</option> schema is specified. To correct this the <filename>GeneralPurposeDatabasePersistencePlugin.java</filename> file has been updated with a calling to an new <methodname>SQLUtil.fixConstraintName</methodname> function which changes all dots in a constraint name to underscores. This ensures that constraint names are compatable with Oracle.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1307">JBPAPP-1307</ulink>: The Persistence Unit (PU) root was incorrectly detected within deployments that contained nested <filename>.jar</filename> files. The root PU was being detected as the first nested <filename>.jar</filename> encountered instead of being the deployment which contains the <filename>persistence.xml</filename> file. To make sure that the PU root is always set correctly, the <filename>JmxDeploymentUnit.java</filename> file has been updated with the removal of testing for the url being null and the <parameter>deploymentInfo.parent</parameter> not being null. This means that the url is now always taken straight from the <parameter>extractDescriptorUrl</parameter> of <filename>META-INF/persistence.xml</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1267">JBPAPP-1267</ulink>: <classname>UserTransaction</classname> (UT) was not able to be deployed with a clustered proxy that supported sticky transactions correctly. This has been fixed by modifying numerious files which make <classname>UserTransaction</classname> deployable with transaction sticky load balance policies.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1002">JBPAPP-1002</ulink>: Bean Managed Transactions (BMT) Stateful Session Beans used to be logged when transactions were not completed between invocations. However this was an error as BMT Stateful Session Beans are allowed to have this occurance and so this logging measure has been removed in this EAP update.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-529">JBPAPP-529</ulink>: JMX source code was being exposed to the user when a <exceptionname>HTTP Status 500</exceptionname> exception would occur. To correct this, an error page <filename>genericError.jsp</filename> has been created and is now displayed whenever a <exceptionname>HTTP Status 500</exceptionname> exception occurs.
+ </para>
+ </listitem>
+ </itemizedlist>
</para>
</formalpara>
</section>
More information about the jboss-cvs-commits
mailing list