[jboss-cvs] JBossAS SVN: r89236 - projects/docs/enterprise/4.3.5/readme/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu May 21 00:09:21 EDT 2009
Author: irooskov at redhat.com
Date: 2009-05-21 00:09:21 -0400 (Thu, 21 May 2009)
New Revision: 89236
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 02:28:11 UTC (rev 89235)
+++ projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml 2009-05-21 04:09:21 UTC (rev 89236)
@@ -434,80 +434,162 @@
<itemizedlist>
<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>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1974">JBPAPP-1974</ulink>: The optimisation within the <classname>JBossXSModel</classname> implementation for traversing a XML schema was insufficient, allowing for high deployment overhead when dealing with complex schemas. Correcting this has been a process of modifying the <filename>JBossXSModel.java</filename> file by adding calls to clear the <classname>HashSet</classname> periodically throughout the traversing process.
</para>
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1732">JBPAPP-1732</ulink>: The MTOM/XOP message always set the <property>start-info</property> property to <code>text/xml</code> when it should have been set to <code>application/soap+xml</code>. This bug was introduced through an upgrade from SOAP 1.1 to SOAP 1.2. The SOAP HTTP binding in the <property>Content-type</property> header has now been updated to the correct value.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1956">JBPAPP-1956</ulink>: The <classname>wscompile</classname> class would fail to create a valid package name when the namespace contained a capitalised reserved keyword. Rectifying this issue has seen the <filename>NameConverter.java</filename> file modified to include code that transforms all characters in the namespace to lower case.
</para>
</listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-829">JBPAPP-829</ulink>: Authentication and authorization needed to be added for POJO endpoints where credentials are supplied using Web Services Security. In order to rectify this issue the following list of files were updated or added as specified:
- </para>
- <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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1773">JBPAPP-1773</ulink>: Previously MTOM was only enabled for types annotated with <property>@XmlMimeType</property> where the content-type headers from the incoming messages should be sufficient to determine if MTOM is required. To fix this bug, MTOM has been enabled for incomming requests where the content type is <property>application/xop+xml</property>. To achieve this outcome both the <filename>MessageFactoryImpl.java</filename> and <filename>ServiceEndpointInvoker.java</filename> files have been updated to retrieve the message type and set the outbound context properties before calling the request handler chain respectively.
</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>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1760">JBPAPP-1760</ulink>: If a substantial amount of SOAP requests were received by the JBoss Enterprise Application Platform during application deployment the <classname>HandlerResolverImpl</classname> class would cause a <exceptionname>ConcurrentModificationException</exceptionname>. Though this would not cause the application to cease opperation, it would result in the strage behaviour of every request going only through the JAXWS handler twice and not go into service implementation. In order to correct this bug, the code responsible for initiating handler chains within the <filename>HandlerDelegateJAXWS.java</filename> and <filename>HandlerDelegateJAXRPC.java</filename> has been synchronized.
</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>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1752">JBPAPP-1752</ulink>: The fault handler was not being called when user application exceptions were being generated. The implementation of the fault handler has been reworked for this Cummulative Patch release to catch the application exceptions and all other kinds of exceptions.
</para>
</listitem>
<listitem>
<para>
- <filename>AuthorizeOperation.java</filename> has been added to authenticate and check the authorisation of the current user.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1749">JBPAPP-1749</ulink>: The SPI component of JBoss Web Services has been upgraded to version 1.0.0.GA_CP02. A list of the included fixes is as follows:
</para>
- </listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <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>
<para>
- <filename>SecurityDecoder.java</filename> has been updated to also use the new classes <classname>Authorize</classname> and <classname>AuthorizeOperation</classname>.
+ <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.
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1743">JBPAPP-1743</ulink>: <classname>WeakReferences</classname> handling within <classname>ConfigObservable</classname> was not handled correctly causing errors as the value of the <classname>WeakReferences</classname> became set to null. This has been corrected by adding a <classname>ReferenceQueue</classname> that identifies the references that require removal. These references are cleared only when a future registration or notification occurs.
</para>
</listitem>
<listitem>
<para>
- <filename>HandlerChainExecutor.java</filename> has been updated in order to determine specific client side conformance requirements.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1732">JBPAPP-1732</ulink>: The MTOM/XOP message always set the <property>start-info</property> property to <code>text/xml</code> when it should have been set to <code>application/soap+xml</code>. This bug was introduced through an upgrade from SOAP 1.1 to SOAP 1.2. The SOAP HTTP binding in the <property>Content-type</property> header has now been updated to the correct value.
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1688">JBPAPP-1688</ulink>: The Common component of JBoss Web Services has been upgraded to version 1.0.0.GA_CP04. A list of the included fixes is as follows:
</para>
+ <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>
+ </itemizedlist>
+ </listitem>
<listitem>
<para>
- <filename>Authorize.java</filename> has been added in order to ensure that a user is authorized to call the endpoint.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1655">JBPAPP-1655</ulink>: The Framework component of JBoss Web Services has been upgraded to version 2.0.1.GA_CP04. A list of the included fixes is as follows:
</para>
+ <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>
+ <programlisting>
+ set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/jaxb-xjc.jar
+ </programlisting>
</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>
+ </itemizedlist>
+ </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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1644">JBPAPP-1644</ulink>: WSDL schema imports did not successfully publish in earlier versions of the JBoss Enterprise Application Platform. Correcting this issue, the <filename>WSDLFilePublisher.java</filename> file has been updated with the <code>return</code> code changed to <code>continue</code> within the infinity loop prevention when the file being published contains a location URL or a schema location value.
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-991">JBPAPP-991</ulink>: When deployment failed an endpoint could be left registered and undeployment would not remove this registration, forcing further deployments to fail. To fix this the <filename>ArchiveDeployerHook.java</filename> file was updated so that even in the event of a deployment aspect failing to deploy, all endpoints will still be called on undeployment in order to ensure registration removal.
</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.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-829">JBPAPP-829</ulink>: Authentication and authorization needed to be added for POJO endpoints where credentials are supplied using Web Services Security. In order to rectify this issue the following list of files were updated or added as specified:
</para>
+ <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>
</listitem>
</itemizedlist>
</listitem>
More information about the jboss-cvs-commits
mailing list