I'm losing my mind here. I finally went full standard to see if the changes
in tomcat 7 would allow me to avoid custom class loaders and contexts, but
ran into a catch-22 issue.
I was getting:
java.lang.ClassCastException:
com.sun.xml.ws.transport.http.servlet.WSServletContainerInitializer
ct: RE: context problem
> From: Edward W. Rouse [mailto:ero...@comsquared.com]
> Subject: context problem
> IDWMClassLoader extends WebappClassLoader.
> I have been reading to docs to try and figure out how to get both the
> normal webapp base directories and the outside the ba
Thanks for the response, lets work backwards.
3 yes
2 looked at and not applicable in this case
1 The custom classLoader is set fine and it works, except it doesnt
loader the classes from the webapp base dir, only the outside base dir.
Also, if I leave out the custom classLoader by r
I have a web app that worked in version 5.5, not working in version 7.0. The
Context.xml is:
IDWMFileDirContext extend FileDirContext, IDWMClassLoader extends
WebappClassLoader. When IDWMFileDirContext is called, it is called with the
default (no arg) constructor,
Looking at http://tomcat.apache.org/tomcat-7.0-doc/api/index.html for more
info about org.apache.catalina.loader.WebappClassLoader and I ran up against
a bit of missing information.
The 4th implementation note mentions addJar(), which is what I wanted a bit
more info on, but addJar() is not
