At 06:40 AM 8/10/2001, Larry Isaacs wrote:
>In Tomcat 3.3, a more complex classloader hierarchy is
>built which separates the server classes (which includes
>the server's XML parser) from the web application's classes.
>Now web applications can have their own XML parser.
Thanks for this tidbit! Fortunately, I run a development server, so going
to 3.3 or 4.0 isn't a problem for me.
Although, I must say, this solution doesn't strike me as the most
elegant. At least in the case of an xml parser. Why should we have
multiple copies of the same damn thing taking up extra resources? I feel,
that the real solution must come from xalan itself. It should be possible
to hand Xalan a list of class loaders that it can use to load extension
functions and elements (actually, most libraries that for whatever reason
do their own class loading should provide such an option).
Regards
Dmitry
