DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6973>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6973

Custom Class loader no longer works in 4.0.3, but works in 3.2.2





------- Additional Comments From [EMAIL PROTECTED]  2002-03-08 18:19 -------
Three more points:

- You might also be suffering from a recently fixed bug that happens
  when JAR files are missing the intervening directory levels.  To see
  if this is happening to you, try a simple servlet that loads the class
  directly.  This bug is fixed in 4.0.4-b1.

- Third party code that creates its own class loaders also need to
  set the parent class loader when they do so.  If they set the parent
  to the webapp class loader, then the /WEB-INF/classes and /WEB-INF/lib
  classes will be visible.  If they don't then they won't -- and that
  means that your class library is broken.  The fact that it worked in
  Tomcat 3.2.2 means that you probably had the classes on the system
  classpath instead of (or in addition to) the webapp, and/or you just
  got lucky with a non-specified feature of Tomcat 3.2.2 that just happened
  to be changed.in Tomcat 4.  Relying on such behaviors is always dangerous.
  Diagnosing why you are getting class not found exceptions (unless it's
  caused by the bug referenced in the previous point) is not possible without
  a reproducible test case.

- In Servlet 2.3, the webapp class loader is required to be made visible
  as the Thread context class loader (to the thread running the request).
  This is for precisely the purpose of making the webapp's own classes
  available to third party code.  If you start your own threads, though,
  it's your responsibility to maintain a reference to that class loader
  if you need it -- the container only does this for its own threads.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to