[jboss-cvs] JBossAS SVN: r82719 - projects/docs/enterprise/4.3.4/readme/en-US.

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

Author: irooskov at redhat.com
Date: 2009-01-09 01:01:00 -0500 (Fri, 09 Jan 2009)
New Revision: 82719

Modified:
   projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
Log:
updated release notes


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-01-09 02:20:53 UTC (rev 82718)
+++ projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml	2009-01-09 06:01:00 UTC (rev 82719)
@@ -330,6 +330,11 @@
 				<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.
+						</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>
@@ -348,7 +353,7 @@
 				<itemizedlist>
 					<listitem>
 						<para>
-							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>: 
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1553">JBPAPP-1553</ulink>: When the <methodname>parseRequest()</methodname> method of the <classname>org.jboss.seam.web.MultipartRequest</classname> class uploaded a large file, there were occurances when this would cause an endless loop and use 100% of the computers CPU. In order to break out of the loop, a <varname>loopCounter</varname> has been implemented within the <filename>MultipartRequest.java</filename> file. 
 						</para>
 					</listitem>
 				</itemizedlist>
@@ -358,8 +363,18 @@
 			<title>JBoss Hibernate</title>
 			<para>
 				<itemizedlist>
+				<!--	<listitem>
+						<para>
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1556">JBPAPP-1556</ulink>:  
+						</para>
+					</listitem> -->
 					<listitem>
 						<para>
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1529">JBPAPP-1529</ulink>: The composite primary key of 765 bytes fails within the unit test for Sybase, as it exceeds the maximum index length of 600 bytes. In order to rectify this issue, a hard coded length of 32 bytes is now in place for the compasite primary key ID within the <filename>UserGroup.hbm.xml</filename> file.
+						</para>
+					</listitem>
+					<listitem>
+						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1528">JBPAPP-1528</ulink>: When Sybase would convert Java byte into tinyint, failures would arise within tests because of the use of 8 bit values. To correct this the unit tests have been updated to use 7 bit values instead of 8. In order to instigate this correction, the <filename>InterfaceProxyTest.java</filename> and <filename>MixedTest.java</filename> files have been updated. 
 						</para>
 					</listitem>