[jboss-cvs] JBossAS SVN: r74591 - projects/docs/enterprise/4.3.2/readme/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jun 16 02:05:05 EDT 2008
Author: irooskov at redhat.com
Date: 2008-06-16 02:05:05 -0400 (Mon, 16 Jun 2008)
New Revision: 74591
Modified:
projects/docs/enterprise/4.3.2/readme/en-US/readme.xml
Log:
updated 4.3.2 release notes
Modified: projects/docs/enterprise/4.3.2/readme/en-US/readme.xml
===================================================================
--- projects/docs/enterprise/4.3.2/readme/en-US/readme.xml 2008-06-16 05:19:20 UTC (rev 74590)
+++ projects/docs/enterprise/4.3.2/readme/en-US/readme.xml 2008-06-16 06:05:05 UTC (rev 74591)
@@ -277,6 +277,7 @@
<itemizedlist>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-879">JBPAPP-879</ulink>: The <filename>null-persistence-service.xml</filename> file was missing from the JBoss Messaging examples folder. This missing file is now included with this release.
</para>
</listitem>
</itemizedlist>
@@ -310,6 +311,11 @@
<itemizedlist>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-874">JBPAPP-874</ulink>: The Web Service Definition Language (WSDL) with Java, generates <interfacename>service-interface</interfacename> and <interfacename>service-endpoint-interface</interfacename> interfaces correctly. However the references generated for JAX-RPC were incorrect with the types having lower case first letters. This release sees this issue rectified with correctly generated JAX-RPC references.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-849">JBPAPP-849</ulink>: The Web Service Definition Language (WSDL) with an imported custom schema would raise a <code>java.lang.OutOfMemoryError</code> when the schema featured circular dependencies. The issue is now corrected, allowing for circular dependencies under the mentioned conditions.
</para>
</listitem>
@@ -318,6 +324,35 @@
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-848">JBPAPP-848</ulink>: The WSSecurityHandlerServer handler required the SOAP Header element even though this should have been optional. In this release, the client now recieves the correct exception that the required <code>wsse:Security</code> tag is missing.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-834">JBPAPP-834</ulink>: When using Java Virtual Machines (JVMs) other than those from <trademark>Sun</trademark>, the remoting properties are not reset to their defaults. This release adds support for the user to set the following properties: <property>REMOTING_KEY_ALIAS</property>
+ <property>REMOTING_KEY_STORE_ALGORITHM</property>
+ <property>REMOTING_SSL_PROTOCOL</property>
+ <property>REMOTING_SSL_PROVIDER_NAME</property>
+ <property>REMOTING_TRUST_STORE_ALGORITHM</property>, which allows for other JVMs to now be used.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-833">JBPAPP-833</ulink>: The recursion for collections such as arrays or lists, did not work correctly within <filename>ReflectiveAttachmentRefScanner.java</filename>. This meant that the annotations were searched in the array of list type and not in the contained type. This issue is now rectified within this release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-832">JBPAPP-832</ulink>: JAXBIntros was not taken into consideration when generating the Web Service Definition Language (WSDL). JAXBIntros is now taken into consideration when generating the WSDL.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-831">JBPAPP-831</ulink>: When using the method <methodname>service.getPort()</methodname> with complex types within a WSDL, it may take a considerable amount of time as JAXBContext instances are created for every wrapper type. This releases corrects this by correcting the use of JAXB-RI within JBOSS-JAXWS, and in tern fixing the JAXBContext error.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-819">JBPAPP-819</ulink>: There was an issue with finding local schema's, relative to their urls. This issue is corrected within this release.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
@@ -338,7 +373,10 @@
<itemizedlist>
<listitem>
<para>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-838">JBPAPP-838</ulink>: When using a DetachedCriteria subquery, the class <classname>SubqueryExpression</classname> would output a <code>ClassCastException</code> because of an incorrect underlying Criteria object, <emphasis>CriteriaImpl.Subcriteria</emphasis>. This issue is corrected with this release by providing the correct Criteria object.
</para>
+ </para>
</listitem>
</itemizedlist>
</para>
@@ -378,6 +416,24 @@
<ulink url="http://jira.jboss.org/jira/browse/JBPAPP-850">JBPAPP-850</ulink>: EJB 2.1 proxies would not be updated when the bean for the proxy is undeplyed within a different node, causing the proxies to contain incorrect server references. This issue has been rectified by correcting an error in the <classname>UnifiedInvokerHAProxy</classname> class.
</para>
</formalpara>
+ <formalpara>
+ <title>JBPAPP-835</title>
+ <para>
+ <ulink url="http://jira.jboss.org/jira/browse/JBPAPP-835">JBPAPP-835</ulink>: Within the <filename>run.sh</filename> file for configuring the Application Server, there is a property called <property>JBOSSCONF</property> which should define what the default configuration is when running the server in default mode. However reguardless of the value assigned to the property, <filename>run.sh</filename> would always use the <emphasis>production</emphasis> server settings when the server was not started with a <code>-c</code> switch. In this release, the issue is rectified and the property <property>JBOSSCONF</property> works correctly by using its given value as the default configuration.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-825</title>
+ <para>
+ <ulink url="http://jira.jboss.org/jira/browse/JBPAPP-825">JBPAPP-825</ulink>: A patch has been created which corrects an occurance where <classname>UnifiedInvokerHAProxy</classname> could output a <code>NullPointerException</code> when under load. The patch that rectifies the aformentioned issue is now supported in this latest release.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBPAPP-818</title>
+ <para>
+ <ulink url="http://jira.jboss.org/jira/browse/JBPAPP-818">JBPAPP-818</ulink>: The wrong Simple API for XML (SAX) parser was used when pacakged with an Enterprise ARchive (EAR). The correct SAX is now used.
+ </para>
+ </formalpara>
<!-- Beginning of Core EAP issues -->
More information about the jboss-cvs-commits
mailing list