On 3/3/03 09:31 PM Steve Loughran <[EMAIL PROTECTED]> wrote: > dont do that then :) CLASSPATH should be empty. And axis must never go into > JRE/ext. If people mess with the classpath outside the webapp then its their > own faulut.
Hehe. Yes - its a don't do. But I have seen it several times. > hmmm. That does sound wierd. File a bug with axis and jboss. If I find the time to nail down the problem ;) > The problem is choosing which classloader to use. We could consider > standardising on ServletContext.getResourceAsStream(), as it doesnt have to > be a classloader at all. Or we have a method > AxisEngine.getResourceAsStream(String path) that tries the ServletContext > call first, then its own classloader if that fails to find resources. At the > very least, it would give us a single place to instrument and toy with when > trying to fix future problems. > That�s exactly what I am looking for. I could spend another 10 pages about classloaders in EARs/WAR archives - using ServletContext.getResource() or ServletContext.getResourceAsStream() solved all those problems. I don't want to mix up things here, but be aware that some people need to be able to have multiple AxisEngines within one WAR, something which does not work right now (because one AxisServer instance is "cached" in the servlet context). So whatever we do to fix classloading, it should not prevent this setup. Jens
