[jboss-remoting-commits] JBoss Remoting SVN: r5206 - remoting2/branches/2.2/docs/guide/en.

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

Author: ron.sigal at jboss.com
Date: 2009-05-13 00:05:31 -0400 (Wed, 13 May 2009)
New Revision: 5206

Modified:
   remoting2/branches/2.2/docs/guide/en/chap-classloaders.xml
Log:
JBREM-1127: Added discussion of parameter "useCurrentThreadClassLoader".

Modified: remoting2/branches/2.2/docs/guide/en/chap-classloaders.xml
===================================================================
--- remoting2/branches/2.2/docs/guide/en/chap-classloaders.xml	2009-05-12 06:45:00 UTC (rev 5205)
+++ remoting2/branches/2.2/docs/guide/en/chap-classloaders.xml	2009-05-13 04:05:31 UTC (rev 5206)
@@ -88,6 +88,17 @@
     the implication that this discussion about classloading in client invokers
     applies not only to clients in the ordinary client server sense, but also to
     clients running inside the server.</para>
+    
+    <para><emphasis role="bold">Note.</emphasis> Prior to Remoting release 2.2.3, a
+    bug in the implementation of the classloading behavior caused the reference
+    to the thread context classloader to be, in fact, to the context classloader
+    of the thread in which the unmarshaller was originally created.  A subsequent
+    invocation in a different thread would ignore the current thread context
+    classloader.  To get the correct behavior, it is necessary to set the
+    parameter <code>org.jboss.remoting.Remoting.USE_CURRENT_THREAD_CLASS_LOADER</code>
+    (actual value "useCurrentThreadClassLoader") to "true".  
+    
+    </para>
   </section>
  
   <section id="section-server-classloading"