This is possibly a similar effect I'm seeing except with Java2WSDL. I've
tried setting the classpath to ".;xerces.jar" to get example 6 of the user
guide working so perhaps there's a conflict between Xerces and JDK1.4? The
other examples must have picked up and used the JDK parser correctly in
order to function but am I correct in observing that the WSDL tools appear
to have an issue with this?

Richard.


----- Original Message -----
The first thing I would check is to make sure that you have an XML parser in
your classpath (it looks like you're running ant, you can specify the
classpath for that apply command). I have found that NullPointerException
and ClassNotFoundException are usually thrown by Axis when no XML parser is
available, even though Axis does not give any hint to that being the cause.

cheers,
Simon



Reply via email to