Quote Originally Posted by benethridge
IMHO, if Spring is going to be a long-term winner, it's going to need a little better error trapping on this kind of simple stuff, as the "symptom" (i.e. the stacktrace error) does not lead one intuitively to the "solution". I imagine others will hit this same error soon, since it's pretty easy to mis-type and/or mis-path the .xsd name.

Not blaming you, Arjen, just talking in general about Spring, as this is currently our biggest problem with it across the board. At my company, we realize that this is still new, and we are all very excited about Spring Web Services, since the essential design pattern and philosophy is far better than Axis, which we were using before.
True, the stacktrace wasn't helpful at all in this case. And to circumvent that, I've added extra checking in the PayloadValidatingInterceptor. I will try and validate these sort of things more carefully in the future.

Thanks!