Names

[Doug Davis <du...@us.ibm.com>]

One thing to think about doing (after the alpha) is going through
and renaming the classes that we plan to expose to handler
writers so they start with "Axis".  Names like "Message" are a bit
too common and will probably cause annoying conflicts for
people.
-Dug

AxisClassLoader patch

[Ravi Kumar <rk...@borland.com>]

Problem:
If the axis context classes and libraries are exclusively present only
under WEB-INF, the servlet engine should be able to work. But it
doesn't. To make it work it's required to add the axis classes and
libraries to the servlet engine's class path. The above is true with
Tomcat 3.2 and a build of Axis from CVS.

Reason:
AxisClassLoader appears to have a bug in the way it determines the
current class loader.

Fix:
I have changed it  (fixed AxisClassLoader attached)

from
**** Thread.currentThread().getContextClassLoader()
to
**** AxisClassLoader.class.getClassLoader();

Rationale:
The AxisClassLoader itself is present under WEB-INF, Whichever class
loader loaded it, has the correct classpath and will be able to load the
rest of the stuff there.

Comments? Am I way off?

Regards
Ravi
JBuilder R&D