SAXParseException: src-resolve: Cannot resolve the name to a(n) 'type definition'...

[Arjen Poutsma]

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!

[Arjen Poutsma]

I've created a second issue for the problems indicated by Luke here: http://opensource.atlassian.com/proj.../browse/SWS-46

[Luke Hamaty]

The SAX parser is producing the obtuse src-resolve error, so Arjen doesn't have much to work with. There is probably a reason they don't have a distinct error for when the schema validator can't load a schema, but I sure can't think of one.

[benethridge]

I found the solution to my original problem. Had nothing to do with my .xsd contents. Spring could not find my .xsd file at all

I have to take this back somewhat. Apparently coincidentally to the time I correctly pointed to the schema, I also copy/pasted the "included child" schema into the "parent" schema. THAT was what made my problem go away.

I say that because now that I've configured my two schemas so that the parent includes the child (ex: <include schemaLocation="./child.xsd"/>), I'm getting my original problem again.

Note that this is exactly the same problem farrellr is getting in his post today, titled "validating interceptor and imported xsd issue?", and I believe for exactly the same reason.

Is there a fix coming for this? We can work around it for now, but we wouldn't want to go into production with it, if we had dozens of "parent" schemas to maintain.

Ben

[Arjen Poutsma]

Is there a fix coming for this? We can work around it for now, but we wouldn't want to go into production with it, if we had dozens of "parent" schemas to maintain.

The fix is already there, as I've indicated in my reply to farrellr's post.