>Yes it does, it uses exactly the same mechanism as RMI.
>Actually, I am not sure to understand the exact problem. For me, remote
>class loading is essentially a matter of setting the
>appropriate codebase
>property. Am I wrong ?
In RMI, classes can be loaded using the system codebase property or the class
annotation. When an object is bound to the RMI registry, the class anotation
contains the classpath of the URLClassloader that was used to load the class
of the object being bound. With this mechanism, the registry is able to load
and serve classes coming from various classpath and even several version of
the same class without conflicts.
from the specifications:
For all of the loadClass methods, the codebase path is used
in conjunction with the current thread's context class loader
(determined by invoking getContextClassLoader on the current
thread) to determine the internal class loader instance to
attempt to load the class from. The RMI runtime maintains a
table of internal class loader instances, keyed by the pair
consisting of the parent class loader and the loader's codebase
path (an ordered list of URLs). A loadClass method looks in the
table for a URLClassLoader instance with the desired codebase
path and the current thread's context class loader as its parent.
If no such loader exists, then one is created and added to the
table. Finally, the loadClass method is called on the chosen
class loader with the specified class name.
Thanks,
christophe
Christophe Ney - mailto:[EMAIL PROTECTED]
Enhydra Project - http://www.enhydra.org
Lutris Technologies - http://www.lutris.com
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
