> Am I just screwed or is there some cool trick that I am
> missing?
As far as I know, this is not possible.
I have another question, which has been nagging me for
a while: Why does the class loader for a web-app "see"
the classes in the lib folder of the servlet engine
(or the classpath of the java engine).
For example if a servlet engine is using an XML parser
(say Xerces, some old version like 1.0.x) and includes
the SAX and DOM interfaces, but only version/level 1.
Now my cool web-app wants to use Xerces 1.3.0 and take
advantage of the new version/level 2 of the interfaces,
I have to fiddle with the lib folder of the servlet
engine (something I don't want to do), and even in
this example I'm doomed, because interface changes in
Xerces between these two versions make them incompatible!
(I know Tomcat does not use Xerces, this was just a
fictious example)
Now I pose the same question as Arthur Ash:
Am I just screwed or is there some cool trick that I am
missing?
If I'm right about the problem I suggest separating the
classloaders for the servlet engine on one hand, and
the web-apps on the other hand, using a common classloader
for the servlet interface and other common servlet stuff.
Is this possible?
Regards,
Gummi Haf
