Hi Nacho,
I was thinking of the dependencies, maybe it would be good to reverse it.
o.a.t.u.depend package is used to record dependencies and handle reloading
( or anything related with deps ).
o.a.t.u.compat is used to allow the use of version-depenent JVM functions,
and provide equivalent ( or dummy ) implementation for older VMs.
The o.a.t.u.depend.DependClassLoader is a wrapper class loader that will
record all the loaded classes and register the deps.
The problem is we need getURLs and getParentLoader to support jasper (
mostly - tomcat internal modules can handle this by keeping track of the
paths ).
I think the "compat" package is more "generic" than "depend" - many apps
would benefit from using the compat, and would not need the depend.
There are 2 solutions:
- use introspection ( not difficult - I can do it quickly ). Main benefit:
it would work with other container's class loaders.
- add a CompatClassLoader interface in o.a.t.u.compat, and have
DependClassLoader implement it. That would add a dep from o.a.t.u.depend
to compat, but that's ok, it's likely we'll need it anyway.
It's not a big priority, I am planning to use depend to manage reloading
for JspServlet anyway. ( in one of the "jasper toolkit" components ), but
it might be nice for people using compat ( without need for depend ).
Costin
On 17 Jun 2001 [EMAIL PROTECTED] wrote:
> nacho 01/06/17 11:09:19
>
> Modified: src/share/org/apache/tomcat/util/compat
> SimpleClassLoader.java Jdk12Support.java
> Jdk11Compat.java
> --- Jdk11Compat.java 2001/02/10 08:12:42 1.4
> +++ Jdk11Compat.java 2001/06/17 18:09:14 1.5
> @@ -58,6 +58,7 @@
> */
>
> package org.apache.tomcat.util.compat;
> +import org.apache.tomcat.util.depend.*;
