I have come accross the same multiple times.
The cause is usually:
- HTTP reverse proxy configuration (which is configured for service endpoints, but not for the XSD locations)
- Incorrect addressess (hostnames) in the XSD URLs, then it needs to be changed in application server configuration
- The nodes of the cluster are not synchronized (the service itself or just XSD exists on some nodes, but not on others)
If you take the URLs of the XSD documents from the WSDL (schemaLocation attribute), are you able to get them via your browser?
I agree that SoapUI could be more precise in describing the error.
