Altova Mailing List Archives>Archive Index >microsoft.public.xml Archive Home >Recent entries >Thread Prev - MSXML 4.0 to 6.0 - Invalid Namespace And XMLSchemaCache >Thread Next - Re: MSXML 4.0 to 6.0 - Invalid Namespace And XMLSchemaCache Re: MSXML 4.0 to 6.0 - Invalid Namespace And XMLSchemaCacheTo: NULL Date: 11/11/2008 7:32:00 PM Leverd wrote: > If you change the namespace to something invalid however, I run into a > problem. > > > > <NameSpace:SubProject xmlns:sub="http://www.me.com/schemas/sub/junk"> > <sub:prop1 /> I don't see how that namespace is "invalid" or how a namespace can be invalid at all. If the parser encounters an element in a namespace for which no schema has been provided then it does lax validation. At least that is what happens in .NET 2.0 or later with XmlReader. There however you can let the parser reports warnings and it will then report a warning if it encounters elements in namespace for which no schema has been found. I am not sure whether/how that is possible with MSXML 6. -- Martin Honnen --- MVP XML http://JavaScript.FAQTs.com/ | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
