>> I see what your mean. About this problem, Because you don't add the second schema file to validate the xml file.
Correct. I appreciate your proposed solution, but that involves changing the structure of the XSD files. I failed to mention, but while my example was very simple, the actual XSD files we're using are quite numberous and are programmatically generated
by a third party - the customer. For us to have to hand-edit them every time we get updated files would be unacceptable.
Use of relative addressing in the schemaLocation attribute is not at all uncommon. Any idea why dot-net's classes don't handle that properly?
Member
41 Points
138 Posts
Re: XML Schema and imports with relative schemaLocation
Sep 01, 2015 06:30 AM|curtisdehaven|LINK
Thanks, again, for your help, Cheng.
>> I see what your mean. About this problem, Because you don't add the second schema file to validate the xml file.
Correct. I appreciate your proposed solution, but that involves changing the structure of the XSD files. I failed to mention, but while my example was very simple, the actual XSD files we're using are quite numberous and are programmatically generated by a third party - the customer. For us to have to hand-edit them every time we get updated files would be unacceptable.
Use of relative addressing in the schemaLocation attribute is not at all uncommon. Any idea why dot-net's classes don't handle that properly?
Thanks again!
Curt