[jboss-cvs] JBossAS SVN: r75515 - in projects/docs/enterprise: 4.3.2/readme/en-US and 1 other directory.

[jboss-cvs-commits at lists.jboss.org]

Author: irooskov at redhat.com
Date: 2008-07-08 20:24:57 -0400 (Tue, 08 Jul 2008)
New Revision: 75515

Modified:
   projects/docs/enterprise/4.2.4/readme/en-US/readme.xml
   projects/docs/enterprise/4.3.2/readme/en-US/readme.xml
Log:
updated release notes with final JIRAs before Docs Freeze today


Modified: projects/docs/enterprise/4.2.4/readme/en-US/readme.xml
===================================================================
--- projects/docs/enterprise/4.2.4/readme/en-US/readme.xml	2008-07-09 00:20:32 UTC (rev 75514)
+++ projects/docs/enterprise/4.2.4/readme/en-US/readme.xml	2008-07-09 00:24:57 UTC (rev 75515)
@@ -315,6 +315,11 @@
 			</listitem>
 			<listitem>
 				<para>
+					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-887">JBPAPP-887</ulink>: JBoss Java API for XML Redistries (JAXR) has been upgraded to version 1.2.0.SP1 which addresses various bugs.
+				</para>
+			</listitem>
+			<listitem>
+				<para>
 					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-877">JBPAPP-877</ulink>: JBoss Serialization version 1.0.3GA would encounter <code>ClassCastExceptions</code> when being used. This update corrects this issue so that serialization functions correctly. 
 				</para>
 			</listitem>
@@ -346,6 +351,11 @@
 			</listitem>
 			<listitem>
 				<para>
+					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-815">JBPAPP-815</ulink>: An issue existed where if a DOCTYPE was added to the file <filename>-ds.xml</filename> and the option to <option>ValidateDTDs</option> was set to true in <filename>jbossjca-services.xml</filename>, validation errors would occur. This was found to be because of an issue with the <property>tx-connection-factory</property> element in <filename>jms-ds.xml</filename> which has since been fixed. 
+				</para>
+			</listitem>
+			<listitem>
+				<para>
 					<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-813">JBPAPP-813</ulink>: The Messaging client included a bug that would make it hang forever, creating a <code>ClusteredConnectionFactory</code> failover; steaming from a socket hang. This issue has now been rectified in this latest EAP release, creating a more stable Messaging component.  
 				</para>
 			</listitem>

Modified: projects/docs/enterprise/4.3.2/readme/en-US/readme.xml
===================================================================
--- projects/docs/enterprise/4.3.2/readme/en-US/readme.xml	2008-07-09 00:20:32 UTC (rev 75514)
+++ projects/docs/enterprise/4.3.2/readme/en-US/readme.xml	2008-07-09 00:24:57 UTC (rev 75515)
@@ -435,12 +435,12 @@
 				<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-891">JBPAPP-891</ulink>: The monitoring tool <emphasis>Twiddle</emphasis> did not print out <code>invoke</code> results, even with the absense of a property editor for the returned object. Corrected within this CP release, <emphasis>Twiddle</emphasis> now calls the <methodname>toString()</methodname> method on returned objects when there is no property editor found. 
 			</para>
 		</formalpara>
-		<formalpara>
+	<!--	<formalpara>
 			<title>JBPAPP-878</title>
 			<para>
 				<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-878">JBPAPP-878</ulink>:  There was a bug that caused the <property>STRICT_SERVLET_COMPLIANCE</property> property to return with false results, in terms of the Technology Compatability Kit (TCK). The property <property>STRICT_SERVLET_COMPLIANCE</property> no longer returns false results. 
 			</para>
-		</formalpara>
+		</formalpara> -->
 		<formalpara>
 			<title>JBPAPP-877</title>
 			<para>
@@ -480,7 +480,13 @@
 			</para>
 		</formalpara>
 		<formalpara>
+			<title>JBPAPP-815</title>
 			<para>
+				<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-815">JBPAPP-815</ulink>: An issue existed where if a DOCTYPE was added to the file <filename>-ds.xml</filename> and the option to <option>ValidateDTDs</option> was set to true in <filename>jbossjca-services.xml</filename>, validation errors would occur. This was found to be because of an issue with the <property>tx-connection-factory</property> element in <filename>jms-ds.xml</filename> which has since been fixed. 
+			</para>
+		</formalpara>
+		<formalpara>
+			<para>
 				<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-805">JBPAPP-805</ulink>: There was a missing java file from the first security example within the server configuration guide, inhibiting the example to be run successfully. The missing <filename>EchoSecurityProxy.java</filename> file has now been restored, enabling the example to be run correctly.
 			</para>
 		</formalpara>