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

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

Author: irooskov at redhat.com
Date: 2009-06-26 00:38:07 -0400 (Fri, 26 Jun 2009)
New Revision: 90608

Modified:
   projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml
Log:
updated release notes with new hibernate information


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-06-26 04:32:44 UTC (rev 90607)
+++ projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml	2009-06-26 04:38:07 UTC (rev 90608)
@@ -61,7 +61,7 @@
 			</listitem>
 			<listitem>
 				<para>
-					Hibernate Annotations 3.3.1.GA
+					Hibernate Annotations 3.3.1.GA_CP01
 				</para>
 			</listitem>
 			<listitem>
@@ -979,11 +979,6 @@
 									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-282">EJB-282</ulink>: The <filename>ORM.xml</filename> file was being ignored when the <property>excludeUnlistedClass</property> property was set to <emphasis>true</emphasis> in the container mode. This bug has been rectified by modifying the <classname>Ejb3Configuration</classname> class to ensure that the <filename>ORM.xml</filename> file is searched even when the <property>excludeUnlistedClass</property> property is set to <emphasis>true</emphasis>.
 								</para>
 							</listitem>
-						<!--	<listitem>
-								<para>
-									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-280">EJB-280</ulink>: 
-								</para>
-							</listitem> -->
 							<listitem>
 								<para>
 									<ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-277">EJB-277</ulink>: String values could not be used as query hint values within Hibernate. This functionality has now been added to Hibernate EntityManager by modifying the <classname>ConfigurationHelper</classname> class to accept string values and the <classname>QueryImpl</classname> class to utilize these changes.
@@ -1151,7 +1146,7 @@
 					</listitem>
 					<listitem>
 						<para>
-							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2002">JBPAPP-2002</ulink>: The Hibernate Annotations component of the Enterprise Application Platform has been upgraded to version 3.3.1. A list of the included fixes is as follows:
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2078">JBPAPP-2078</ulink>: The Hibernate Annotations component of the Enterprise Application Platform has been upgraded to version 3.3.1. A list of the included fixes is as follows:
 						</para>
 						<itemizedlist>
 							<listitem>
@@ -1662,9 +1657,14 @@
 		<formalpara>
 			<title>General Known Issues</title>
 			<para>
-			<!--	<itemizedlist>
+				<itemizedlist>
 					<listitem>
 						<para>
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1774">JBPAPP-1774</ulink>: The JBoss Enterprise Application Platform RPM cannot be installed with only the OpenJDK distribution.
+						</para>
+					</listitem>
+				<!--	<listitem>
+						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1286">JBPAPP-1286</ulink>: Footnotes within documentation tables and lists do not appear within PDFs. This issue resides within FOP and currently no workaround exists. Where possible footnotes are not used in the circumstances mentioned, however in documents such as the Release Notes the web address of a JIRA is automatically generated as a footnote and places a number beside that of the JIRA, referencing a footnote that does not appear.  
 						</para>
 					</listitem>
@@ -1672,8 +1672,8 @@
 						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-885">JBPAPP-885</ulink>: An issue exists where if <methodname>DefaultRedeliveryDelay</methodname> or <methodname>RedeliveryDelay</methodname> is set to a value apart from zero, messages will not be redelivered even though the method <methodname>session.rollback()</methodname> had been called. This issue will not be fixed because redelivery delay is handled on the server side and the message is already acknowledged before delivery of the message with a non durable subscription. For the Enterprise Application Platform, this means that redelivery delays with non durable subscriptions cannot be supported.
 						</para>
-					</listitem>
-				</itemizedlist> -->
+					</listitem> -->
+				</itemizedlist> 
 			</para>
 		</formalpara>
 		<formalpara>