But I don't think so. We have an existing web service that's been running fine for awhile. I'm trying to create a new service within the same codebase/WAR, just at a different URL. I'm using Axis 1.2, WSAD 5.1, and Java 1.3 (yes, we're that far behind).
We have a WS client class that encapsulates the call to our own services, for testing purposes. I've added a new method to this class which uses a new request XML to call the new service. The 'old' calls to the old service, from within this same client class, work fine. The new call creates the exception below.
So since the old calls from within the same class work fine, I don't think it's the classpath issue mentioned in the thread above.
The new request XML validates and is very simple :