David Smith wrote:
> most likely the shared classloader instead. If possible, move the
> handler.jar from shared/lib to WEB-INF/lib of your webapp and the
> problem should go away.
>>It took me a few minutes to realize that this was not a ClassNotFound
>>exception, but something else. Reading do
I think you are assuming the classloader
org.something.DatabaseRequestHandler is using is the webapp's local
classloader. I doubt this is the case. Those with more knowlege of the
classloader architecture may chime in, but the classloader being used is
most likely the shared classloader instead.
Hello Christopher,
> Von: "Christopher Piggott" <[EMAIL PROTECTED]>
> QUESTION: looking at the little diagram in the Tomcat 5.5 Class Loader
> HOW-TO, when I do the above (Class.forName) I am using the Webapp class
> loader, correct?
Yes.
> The handler classes are all in handlers.jar which is in
I have something happening with class loading from within a server, and I don't
understand it.
My servlet defines some classes called:
org.something.server -- the class that extends HttpServlet
org.something.DatabaseRequestHandler -- an interface
When you make a request to the s
