Eyal Hirsch wrote:
>
>I will shortly test to see whether this is the
>problem. However, I know this doesn't relate to
>EJB directly, however I'd appriciate if you could
>elaborate on how do I solve this problem should this
>indeed be the problem.
>
>Many thanks,
> eyal.
One sure way to not having this type of problem is putting all the classes
in a single jar and make sure that the guilty class is in only one jar file
and make sure that there is only one class loader for that jar.
However, this might not be possible or even wishable.
To be able to solve the problem, you must study the deployment and class loading
strategy of your server.
Usually, there is tree of class loaders. The root of the tree is the system class
loader. Each node in the tree is a specialized class loader (RMI, servlet, beans,
...).
The number and purpose of each class loader depends on the architecture of
your server.
If the servlet class loader can't be the same as the bean class loader,
than you have to make sure that all shared classes are loaded by a class loader
that is a common parent to both (servlet and bean) class loaders.
Hope this help a little,
Benoit Tremblay (Clea informatique)
at Ericsson Research Canada
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
