Matthias, you asked how you can do the ClassLoader printing I suggested.
It depends on who "you" are. Axis users can't do it; my suggestion is
aimed at Axis implementors. I'm suggesting that Axis (and Tomcat) code
should be alert for class-loading exceptions&errors and do us all the
favor of
On Thursday 14 November 2002 16:02, Steve Loughran wrote:
> Likely cause is the shared jar needs access to classes in
> axis.jar, which is in the 'lower' classloader and hence invisible.
> Move axis and needed jars up, perhaps
Thanks, you are right. Did I mention that I loathe this class loading
- Original Message -
From: "Matthias Brunner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 14, 2002 05:43
Subject: Class loader madness and useless error reporting
Hello,
I do not know whether this is a bug in tomcat or axis or both (in
fa
On Thursday 14 November 2002 15:44, Mike Spreitzer wrote:
> For exceptions like these, wouldn't it help if the contents of the
> ClassLoader & ancestors were printed out? Try it: you'll find
> they're all URLClassLoaders, and you can query them for the URLs
> they contain.
How do I achieve this?
For exceptions like these, wouldn't it help if the contents of the
ClassLoader & ancestors were printed out? Try it: you'll find they're all
URLClassLoaders, and you can query them for the URLs they contain.
Mike
Hello,
I do not know whether this is a bug in tomcat or axis or both (in
fact, I do not even know if it is it a bug at all or it is me how is
dumb).
But for now I will only report it here please correct me if I am
wrong.
--
Software used:
tomcat 4.1.12, axis 1.0, sun jdk 1.4.1_01-b01, linu
