[jboss-cvs] JBossAS SVN: r83753 - in projects/docs/enterprise: 4.3.4/readme/en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Feb 1 23:15:24 EST 2009
Author: irooskov at redhat.com
Date: 2009-02-01 23:15:24 -0500 (Sun, 01 Feb 2009)
New Revision: 83753
Modified:
projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml
projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
Log:
updated 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 2009-02-02 01:16:00 UTC (rev 83752)
+++ projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml 2009-02-02 04:15:24 UTC (rev 83753)
@@ -99,11 +99,11 @@
JBoss Web 2.0.0-6.CP09
</para>
</listitem>
- <listitem>
+<!-- <listitem>
<para>
JBoss Web Services 1.2.1.GA_CP04
</para>
- </listitem>
+ </listitem> -->
<listitem>
<para>
JGroups 2.4.5
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 2009-02-02 01:16:00 UTC (rev 83752)
+++ projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml 2009-02-02 04:15:24 UTC (rev 83753)
@@ -570,25 +570,111 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1552">JBPAPP-1552</ulink>: When deploying JBoss Web Services within EAP without internet access, <classname>JBossWSEntityResolver</classname> would not resolve any schemas causing Web Services for Remote Portlets (WSRP) to produce an error. This issue has been fixed by modifying <classname>JBossWSEntityResolver</classname> within <filename>WSDL11Reader.java</filename> to resolve schemas locally when an internet connection is unavaliable.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1548">JBPAPP-1548</ulink>: The JBoss Web Services component of the EAP has been upgraded to version 2.2.2.SP11. A list of the included fixes is as follows:
</para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1449">JBPAPP-1449</ulink>: WSProvide would ignore a <literal>SOAPBinding</literal> declaration specified in the EJB3 stateless session bean. To correct this and allow <literal>SOAPBinding</literal> to work as expected the following files have been modified: <filename>WSDLGenerator.java</filename>, <filename>SOAPEndpoint.java</filename>, <filename>Constants.java</filename>, <filename>WSDLWriter.java</filename>, <filename>SOAPBindingTestCase.java</filename> and <filename>WSDL11Writer.java</filename>.
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1439">JBPAPP-1439</ulink>: The component <emphasis>Xerces</emphasis> of JBoss Web Services has a feature that optimises the parsing of messages called <methodname>Deffered Node Expansion</methodname>.This defers node expansion until the nodes are accessed, improving performance where not all nodes need to be visited. However memory overheads are increased, which can be considerable for large messages.
- </para>
- <para>
- This release grants the user an option to disable the <methodname>Deffered Node Expansion</methodname> feature and have all nodes expand. To achieve this the following system property needs to be set:
- </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ When deploying JBoss Web Services within EAP without internet access, <classname>JBossWSEntityResolver</classname> would not resolve any schemas causing Web Services for Remote Portlets (WSRP) to produce an error. This issue has been fixed by modifying <classname>JBossWSEntityResolver</classname> within <filename>WSDL11Reader.java</filename> to resolve schemas locally when an internet connection is unavaliable.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ WSProvide would ignore a <literal>SOAPBinding</literal> declaration specified in the EJB3 stateless session bean. To correct this and allow <literal>SOAPBinding</literal> to work as expected the following files have been modified: <filename>WSDLGenerator.java</filename>, <filename>SOAPEndpoint.java</filename>, <filename>Constants.java</filename>, <filename>WSDLWriter.java</filename>, <filename>SOAPBindingTestCase.java</filename> and <filename>WSDL11Writer.java</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The component <emphasis>Xerces</emphasis> of JBoss Web Services has a feature that optimises the parsing of messages called <methodname>Deffered Node Expansion</methodname>.This defers node expansion until the nodes are accessed, improving performance where not all nodes need to be visited. However memory overheads are increased, which can be considerable for large messages.
+ </para>
+ <para>
+ This release grants the user an option to disable the <methodname>Deffered Node Expansion</methodname> feature and have all nodes expand. To achieve this the following system property needs to be set:
+ </para>
<programlisting>
-Dorg.jboss.ws.disable_deferred_node_expansion=true
</programlisting>
+ </listitem>
+ <listitem>
+ <para>
+ A regression with <literal>TCK5 SAAJ</literal> in the <classname>SOAPBody</classname> class was introduced with a fix to a previous bug and this has now been rectified by modifying the <filename>SOAPBodyImpl.java</filename> file to perform a <code>break</code> after assigning the <varname>childElement</varname> property.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The end points for a <literal>transport-guarantee</literal> that is set to be confidential would see an attempt to exactly map the URL pattern in the WSDL. However since the servlet and security constrints will not be defined exactly the same a bug occured whereby JBoss Web Services would assume the <literal>transport-guarantee</literal> was not confidential when generating the address, causing the WSDL to be generated with a http address. The <literal>transport-guarantee</literal> would still be enforced by JBoss Web Services as confidential but the WSDL would contain the wrong address, leading to clients attempting to connect to an incorrect address.
+ </para>
+ <para>
+ In order to rectify this occurance, the <filename>MetaDataBuilder.java</filename> file has been modified so that when testing the servlet pattern it also tests correctly for the security constraint instead of assuming both with be of the same value.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal>com.sun.xml.bind.v2.runtime.reflect.opt</literal> package contains classes to optimize field and method access by dynamically generating classes. Within the <classname>Injector</classname> class there is a <literal>HashMap</literal> value that is wrapped within a <literal>WeakReference</literal> however since there is only a <literal>WeakReference</literal> to the <classname>Injector</classname> class within this, the <literal>HashMap</literal> is garbage collected. To fix this the reference has been changed to a <literal>StrongReference</literal> and in order to maintain the original requirements, the <classname>Injector</classname> is now passed a reference to the ClassLoader instead of containing one specifically.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When creating messages in SOAP 1.2 without attachments, the <classname>SOAPMessageImpl</classname> class sets the <varname>contentType</varname> variable to <literal>text/xml</literal>, which was incorrect. This has now been rectified by amending <varname>contentType</varname> to use the value <literal>application/soap+xml</literal> by adding the <methodname>getSAPContentType()</methodname> method to <filename>SOAPMessageImpl.java</filename> and updating <filename>DispatchImpl.java</filename> to correctly reference the SOAP message context.
+
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Deployments of JAX-WS nature would fail for JBoss AOP instrumented endpoints, generating an <exceptionname>IllegalAnnotationsException</exceptionname> as JBoss Web Services attempted to process the JBoss AOP methods. <filename>JAXWSMetaDataBuilder.java</filename> has been udpated to mark JBoss AOP methods as synthetic which allows them to be skipped.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ WSDL dynamic address replacement was not working correctly in previous versions of the EAP since port and protocol numbers were not being considered. The <filename>WSDLRequestHandler.java</filename> file has been modified to use a new URL and protocol instead of the original URL and protocol in order to use the dynamicly generated port and protocol numbers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In converting WSDL to Java, anonymous types that are nested within anonymous types generated a JAX-RPC mapping that did not match the source. The <filename>MappingFileGeneratorHelper.java</filename> file has been corrected to ensure that the generated mapping matches the source of the informaiton.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JAAS certificate authentication support was not supported in the JBoss Web Services Security implementation, meaning that authentication via this method could not take place based on the certificate the client used to sign the message. Support for this has been added to JBoss Web Services and in tern the EAP with this component upgrade.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When the default port for a protocol was being used within JBoss Web Services, the port number still appeared at the end of the URL even though this was unnecessary. In order to remove the port number from the end of the URL, the <filename>MetaDataBuilder.java</filename> has been modified for each individual service that uses the default port.
+ </para>
+ </listitem>
+ <listitem>
+ <!--JBPAPP-1440--> <para>
+
+ </para>
+ </listitem>
+ <listitem>
+ <!--JBPAPP-1558--> <para>
+
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When JBoss Web Services is being used as a client, the information within the <methodname>DOMUtils.clearThreadLocals()</methodname> method was not cleared for incoming client calls. In order to fix this the call to <methodname>DOMUtils.clearThreadLocals()</methodname> has been moved to the <classname>MessageContextAssociation</classname> class and is executed once the last message has been processed. The files that have been updated in order to incorporate the fix are: <filename>DOMUtils.java</filename>, <filename>XMLContent.java</filename>, <filename>ProviderImpl.java</filename>, <filename>MessageContextAssociation.java</filename>, <filename>MessageContextJAXWS.java</filename> and <filename>RequestHandlerImpl.java</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When the <varname>webServiceHost</varname> property was not set, the <ulink url="http://localhost:8080/jbossws/services ">http://localhost:8080/jbossws/services</ulink> page presented the host name as <exceptionname>jbossws.undefined.host</exceptionname>. A <methodname>createAddress</methodname> method has been added to <filename>ContextServlet.java</filename> which dynamically updates the WSDL and XSD files with the address from the request URL before displaying information to the user.
+ </para>
+ </listitem>
+ <listitem>
+ <!--JBPAPP-1560--> <para>
+
+ </para>
+ </listitem>
+ </itemizedlist>
</listitem>
+ <note>
+ <para>
+ The JBoss Web Services upgrade 2.2.2.SP11 also includes the security fix <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1548">JBPAPP-1548</ulink>, discussed in the Security Issue section.
+ </para>
+ </note>
</itemizedlist>
</para>
</formalpara>
More information about the jboss-cvs-commits
mailing list