[jboss-cvs] JBossAS SVN: r89264 - projects/docs/enterprise/4.3.5/readme/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri May 22 00:52:10 EDT 2009
Author: irooskov at redhat.com
Date: 2009-05-22 00:52:09 -0400 (Fri, 22 May 2009)
New Revision: 89264
Modified:
projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml
Log:
updated release notes with new JIRA
Modified: projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml
===================================================================
--- projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml 2009-05-21 23:46:29 UTC (rev 89263)
+++ projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml 2009-05-22 04:52:09 UTC (rev 89264)
@@ -47,9 +47,9 @@
<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><!--
+ </para>
<itemizedlist>
- <listitem>
+ <!-- <listitem>
<para>
JBoss Application Server 4.2.z
</para>
@@ -109,12 +109,12 @@
JBoss Web Services 2.0.1.SP2_CP06
</para>
</listitem>
- <!-- <listitem>
+ <listitem>
<para>
- JGroups 2.4.5
+ JGroups 2.4.6
</para>
</listitem>
- <listitem>
+ <!-- <listitem>
<para>
JSF 1.2_10
</para>
@@ -128,8 +128,8 @@
<para>
Xalan 2.7.0.patch02
</para>
- </listitem>
- </itemizedlist> -->
+ </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.
@@ -467,6 +467,7 @@
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1750">JBPAPP-1750</ulink>: SOAP 1.2 deployments are supported within JBoss Web Services, however the <classname>wsconsume</classname> tool does not support SOAP 1.2 bindings. To inable this tool to support SOAP 1.2, the files <filename>WSConsume.java</filename> and <filename>WSContractConsumer.java</filename> have been updated to recognise SOAP 1.2, while the files <filename>WSConsumeTask.java</filename> and <filename>SunRIConsumerImpl.java</filename> have been updated to set extensions. </para>
</listitem>
</itemizedlist>
+ </listitem>
<listitem>
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1746">JBPAPP-1746</ulink>: <emphasis>Handler Chains</emphasis> did not work correctly within <emphasis>Dispatch</emphasis> clients causing incorrect behaviour. The dispatch component of Web Services has undergone extensive correction so that it works as a user would expect it to.
@@ -489,9 +490,9 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1687">JBPAPP-1687</ulink>: Each request to the Web Services component would result in an open file descriptor. This caused the application to reach the limit of the maximum amount of file descriptors allowed and then fails on every request after. This issue has been rectified by ensuring that all streams and file descriptors are closed within the different aspects of the Web Services component.
- </para>
- </listitem>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1687">JBPAPP-1687</ulink>: Each request to the Web Services component would result in an open file descriptor. This caused the application to reach the limit of the maximum amount of file descriptors allowed and then fails on every request after. This issue has been rectified by ensuring that all streams and file descriptors are closed within the different aspects of the Web Services component.
+ </para>
+ </listitem>
</itemizedlist>
</listitem>
<listitem>
@@ -501,17 +502,17 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1887">JBPAPP-1887</ulink>: A bug existed within the <filename>wsprovide.bat</filename> file where there is no reference to <filename>jaxb-xjc.jar</filename> in the classpath. This issue has been corrected by adding the following line to the beginning of the <filename>wsprovide.bat</filename> file and thus adding <filename>jaxb-xjc.jar</filename> into the classpath:
- </para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1887">JBPAPP-1887</ulink>: A bug existed within the <filename>wsprovide.bat</filename> file where there is no reference to <filename>jaxb-xjc.jar</filename> in the classpath. This issue has been corrected by adding the following line to the beginning of the <filename>wsprovide.bat</filename> file and thus adding <filename>jaxb-xjc.jar</filename> into the classpath:
+ </para>
<programlisting>
set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/jaxb-xjc.jar
</programlisting>
- </listitem>
+ </listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1784">JBPAPP-1784</ulink>: When starting the Enterprise Application Platform with the <code>-Dcom.sun.management.jmxremote</code> option, a <exceptionname>NullPointerException</exceptionname> would occur. The <filename>SubscriptionManager.java</filename> file was updated to allow for a break in the <classname>MBeanServer</classname> if the <classname>MBeanServer</classname> server class name starts with <emphasis>org.jboss</emphasis>.
- </para>
- </listitem>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1784">JBPAPP-1784</ulink>: When starting the Enterprise Application Platform with the <code>-Dcom.sun.management.jmxremote</code> option, a <exceptionname>NullPointerException</exceptionname> would occur. The <filename>SubscriptionManager.java</filename> file was updated to allow for a break in the <classname>MBeanServer</classname> if the <classname>MBeanServer</classname> server class name starts with <emphasis>org.jboss</emphasis>.
+ </para>
+ </listitem>
</itemizedlist>
</listitem>
<listitem>
@@ -531,71 +532,122 @@
<itemizedlist>
<listitem>
<para>
- <filename>ReceiveUsernameOperation.java</filename> was updated with the removal of the operations for the <classname>Logger</classname> to aquire information about the <varname>username</varname> and <varname>password</varname> of the current <varname>user</varname> variable value.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>WSSecurityOMFactory.java</filename> was updated with new methods for parsing characters and elements as well as the public method <methodname>setValue</methodname> which passes a <varname>value</varname> to the <methodname>role.setName</methodname> method and a test if authorization is necessary for the current <varname>localName</varname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>Config.java</filename> has been updated to include a private <varname>Authorize</varname> class as well as the public methods <methodname>getAuthorize()</methodname> and <methodname>setAuthorize()</methodname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>AuthorizeOperation.java</filename> has been added to authenticate and check the authorisation of the current user.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>SecurityDecoder.java</filename> has been updated to also use the new classes <classname>Authorize</classname> and <classname>AuthorizeOperation</classname>.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>ClientImpl.java</filename> has been updated to include a value of <property>false</property> as the last property of the new <classname>HandlerChainExecutor</classname> being created.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>HandlerChainExecutor.java</filename> has been updated in order to determine specific client side conformance requirements.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>Role.java</filename> has been added in order to provide a role in the program which is authorized to call an endpoint.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>Authorize.java</filename> has been added in order to ensure that a user is authorized to call the endpoint.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>WSSecurityDispatcher.java</filename> has been updated to remove the <classname>SecurityStore</classname> creater and now include private methods to decode the header and test authorization.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>DispatchImpl.java</filename> has been updated to include a value of <property>false</property> as the last property of the new <classname>HandlerChainExecutor</classname> being created.
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>HandlerDelegateJAXWS.java</filename> has been updated to include a value of <property>false</property> as the last property of the new <classname>HandlerChainExecutor</classname> being created.
- </para>
- </listitem>
- </itemizedlist>
+ <filename>ReceiveUsernameOperation.java</filename> was updated with the removal of the operations for the <classname>Logger</classname> to aquire information about the <varname>username</varname> and <varname>password</varname> of the current <varname>user</varname> variable value.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>WSSecurityOMFactory.java</filename> was updated with new methods for parsing characters and elements as well as the public method <methodname>setValue</methodname> which passes a <varname>value</varname> to the <methodname>role.setName</methodname> method and a test if authorization is necessary for the current <varname>localName</varname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>Config.java</filename> has been updated to include a private <varname>Authorize</varname> class as well as the public methods <methodname>getAuthorize()</methodname> and <methodname>setAuthorize()</methodname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>AuthorizeOperation.java</filename> has been added to authenticate and check the authorisation of the current user.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>SecurityDecoder.java</filename> has been updated to also use the new classes <classname>Authorize</classname> and <classname>AuthorizeOperation</classname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>ClientImpl.java</filename> has been updated to include a value of <property>false</property> as the last property of the new <classname>HandlerChainExecutor</classname> being created.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>HandlerChainExecutor.java</filename> has been updated in order to determine specific client side conformance requirements.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>Role.java</filename> has been added in order to provide a role in the program which is authorized to call an endpoint.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>Authorize.java</filename> has been added in order to ensure that a user is authorized to call the endpoint.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>WSSecurityDispatcher.java</filename> has been updated to remove the <classname>SecurityStore</classname> creater and now include private methods to decode the header and test authorization.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>DispatchImpl.java</filename> has been updated to include a value of <property>false</property> as the last property of the new <classname>HandlerChainExecutor</classname> being created.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>HandlerDelegateJAXWS.java</filename> has been updated to include a value of <property>false</property> as the last property of the new <classname>HandlerChainExecutor</classname> being created.
+ </para>
+ </listitem>
+ </itemizedlist>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</para>
</formalpara>
+ <formalpara>
+ <title>JGroups</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2002">JBPAPP-2002</ulink>: The JGroups component of the Enterprise Application Platform has been upgraded to version 2.4.6. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JGRP-975">JGRP-975</ulink>: The JGroups testsuite did not permit a user to specify host and port properties for the <classname>GossipRouter</classname> implementation. This meant that the IP address was fixed at 127.0.0.1 and the port was fixed at 12001. This update allows for the host and port properties to be configurable so that the system can be tested against other values other than only the defaults.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JGRP-961">JGRP-961</ulink>: Running the JGroups testsuite against IPv6 addresses using <property>link-local</property> IPv6 addresses with no zone ID would cause some tests to fail that would normally pass when run against IPv4 addresses. The problem arose if the zone ID was ommitted and the OS assigned a default interface to send the message, which may not have been the one the user was after. To correct this issue so that IPv6 addresses worked correctly with JGroups, scoped <property>link-local</property> addresses had to be used with the <classname>ServerSocketReceiver</classname> and <classname>ServerSocketSender</classname> classes, enablining use of the correct zone ID in each IPv6 address case.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JGRP-949">JGRP-949</ulink>: Format version information was not displayed to the user in the most meaningful way. In order to make sure the the user receives the most useful information the way in which the format version information is provided has changed from:
+ </para>
+<programlisting>
+log.warn(new StringBuffer("packet from ").append(client_addr).append(':').append(client_port).append(" has different version (").append(version).append(") from ours (").append(Version.version).append("). This may cause problems"));
+</programlisting>
+ <para>
+ To:
+ </para>
+<programlisting>
+log.warn(new StringBuffer("packet from ").append(client_addr).append(':').append(client_port).append(" has different version (").append(version).append(") from ours (").append(Version.print(Version.version)).append("). This may cause problems"));
+</programlisting>
+ <para>
+ Of note is the change of <code>Version.version</code> to <code>Version.pring(Version.version)</code>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JGRP-923">JGRP-923</ulink>: GMS address printing did not contain the cluster name in the details it provided. For this Cummulative Patch release GMS address printing has been updated to include the cluster name in order to provide more detail to a user.
+ </para>
+ </listitem>
+ <!-- <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JGRP-893">JGRP-893</ulink>:
+ </para>
+ </listitem> -->
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
<!-- <formalpara>
<title>JBoss Seam</title>
<para>
@@ -614,6 +666,11 @@
<itemizedlist>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1998">JBPAPP-1998</ulink>: The incorrect exception (<exceptionname>EntityNotFoundException</exceptionname>) was being generated for an optimistic locking failure due to a deleted entity using the <property>hibernate.jdbc.batch_versioned_data=false</property> property and value. To correct this a <emphasis>try and catch</emphasis> test has been added to the <methodname>AbstractEntityManagerImpl.wrapStaleStateException</methodname> method in order to catch the <exceptionname>EntityNotFoundException</exceptionname> exception and display the correct <exceptionname>OptimisticLockException</exceptionname> exception instead.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1930">JBPAPP-1930</ulink>: A <exceptionname>NullPointerException</exceptionname> would occur when a native SQL query coupled eager fetching with a many-to-many relationship. Correcting this has beant that the <code>if ( collectionPersister.isOneToMany() ) {</code> line of code in the <filename>SQLQueryReturnProcessor</filename> file has been changed to <code>if ( collectionPersister.isOneToMany() || collectionPersister.isManyToMany()) {</code>, removing the generation of a <exceptionname>NullPointerException</exceptionname>. To note though is that the fix only works with the <filename>hbm.xml</filename> file SQL mapping feature and a named query.
</para>
</listitem>
@@ -697,11 +754,13 @@
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1693">JBPAPP-1693</ulink>: The JBoss Transaction Service component of the Enterprise Application Platform has been upgraded to version 4.2.3.SP5.CP05. A list of the included fixes is as follows:
</para>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1684">JBPAPP-1684</ulink>: A memory leak would be caused in the <classname>BaseTransaction</classname> class because entries in the hash table were never removed, even if a thread was no longer in use. This meant that client transactions could have leaked approximately 600 bytes. To correct this bug, the <filename>BaseTransaction.java</filename> file has been updated to replace the hash table with a <varname>ThreadLocal</varname> implementation which takes an integer as input. In order to allow for the timeout values to work correctly, they now only call the required methods of <methodname>_timeouts.set</methodname> and <methodname>_timeouts.get</methodname>. With these improvements made, the memory leak no longer occurs.
- </para>
- </listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1684">JBPAPP-1684</ulink>: A memory leak would be caused in the <classname>BaseTransaction</classname> class because entries in the hash table were never removed, even if a thread was no longer in use. This meant that client transactions could have leaked approximately 600 bytes. To correct this bug, the <filename>BaseTransaction.java</filename> file has been updated to replace the hash table with a <varname>ThreadLocal</varname> implementation which takes an integer as input. In order to allow for the timeout values to work correctly, they now only call the required methods of <methodname>_timeouts.set</methodname> and <methodname>_timeouts.get</methodname>. With these improvements made, the memory leak no longer occurs.
+ </para>
+ </listitem>
+ </itemizedlist>
</listitem>
</itemizedlist>
</para>
More information about the jboss-cvs-commits
mailing list