[jboss-cvs] JBossAS SVN: r95378 - projects/docs/enterprise/5.0/Release_Notes_GA/en-US.

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

Author: laubai
Date: 2009-10-22 02:48:25 -0400 (Thu, 22 Oct 2009)
New Revision: 95378

Modified:
   projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml
Log:
Added JBPAPP-2971, 2957.

Modified: projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml
===================================================================
--- projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml	2009-10-22 06:23:21 UTC (rev 95377)
+++ projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml	2009-10-22 06:48:25 UTC (rev 95378)
@@ -591,6 +591,11 @@
                     <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2306">JBPAPP-2306</ulink>: The HP-UX init script in the First Customer Ship, <filename>jboss_init_hpux.sh</filename>, did not let users define a bind address with the <code>-b</code> option. Support for this option has since been added to the script.
                   </para>
                 </listitem>
+                <listitem>
+                  <para>
+                    <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2952">JBPAPP-2952</ulink>: 
+                  </para>
+                </listitem>
               </itemizedlist>            
             </para>
         </formalpara>
@@ -827,6 +832,18 @@
 			<title>Hibernate Known Issues</title>
 			<para>
 				<itemizedlist>
+                    <listitem>
+                      <para>
+                        <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2971">JBPAPP-2791</ulink>: Applications that map Hibernate to use <classname>cglib</classname> as a byte provider fail to deploy because of a <exceptionname>java.lang.SecurityException</exceptionnname>. An error message similar to the following is displayed:
+                      </para>
+                      <screen>Deployment "persistence.unit:unitName=lobtest.ear/lobtest-ejb-1.0-SNAPSHOT.jar#lobtest-jpa-jndi" is in error due to the following reason(s): java.lang.SecurityException: class "com.redhat.gss.lobtest.jpa.Item$$EnhancerByCGLIB$$defd1a7f"'s signer information does not match signer information of other classes in the same package</screen>
+                      <para>
+                        This occurs because the <filename>cglib.jar</filename> in JBoss Enterprise Application Platform 5.0 is signed, and the cglib-instrumented proxy uses the <filename>cglib.jar</filename> signer information instead of the signer information of the application target class.
+                      </para>
+                      <para>
+                        The workaround for this issue is to replace <filename>jboss-eap-5.0/jboss-as/common/lib/cglib.jar</filename> with an unsigned version of <filename>cglib.jar</filename>, which can be downloaded from <ulink url="http://repository.jboss.com/maven2-brew/cglib/cglib/2.2/cglib-2.2.jar">http://repository.jboss.com/maven2-brew/cglib/cglib/2.2/cglib-2.2.jar</ulink>.
+                      </para>
+                    </listitem>
 					<listitem>
 						<para>
 							<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2613">JBPAPP-2613</ulink>: When the DB2 v9.7 driver is in use, the <literal>Blob</literal> and <literal>Clob</literal> locators fail. Recommendations reguarding the use of DB2 v9.7 connection properties and Hibernate can be found in the linked JIRA issue.
@@ -974,7 +991,11 @@
                   <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1230">JBPAPP-1230</ulink>: Subqueries that use <literal>DetachedCriteria</literal> are generated incorrectly, which causes a <exceptionname>SybSQLException</exception>. The workaround for this issue is not to use <literal>DetachedCriteria</literal> in a subquery. Instead, we recommend using an HQL query.
                 </para>
                </listitem>
-        
+                <listitem>
+                  <para>
+                    <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2957">JBPAPP-2957</ulink>: The <code>evict(Object key)</code> and <code>evictAll()</code> methods in <classname>EntityRegionAccessStrategy</classname> and <classname>CollectionRegionAccessStrategy</classname> attempt to remove objects from the cache without regard for transaction isolation. This is currently unsupported because JBoss Cache's <code>removeNode</code> method does not deal with transactions.
+                  </para>
+                </listitem>
 
 
 <!--               <listitem>