Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: MSXML 4.0 to 6.0 - Invalid Namespace And XMLSchemaCache

From: Leverd@-----------.---------.---
To: NULL
Date: 11/11/2008 12:10:00 PM
Matrin,

Thank you for the quick reply. I should have chosen my words more carefully.
You're right. MSXML will produce a warning if you validate an XML document
that contains a namespace not linked to a schema. But you need to use the
validate method (IXMLDOMDocument2 object in C++) to get this behavior.
Using the load method will perform a 'lax' validation, and won't pick it
up.

Unfortunately I'm still fighting my issue. In my XML documents there are 
multiple
namespaces. The lowest level namespace appears to work just fine. It is 
first namespace declared in each document, and is linked to a schema that all 
XML documents must abide by. If I try to change the namespace so  that it 
doesn’t matchup with the XMLSchemaCache (i.e. as explained in my first post), 
I get the correct errors. Any namespace declared after the base however 
doesn’t seem to work. It follows the same behavior as explained in my first 
post.

It has to be something with the changes to MSXML 6.0 I'll keep fighting the 
fight and let you know what I find.

Thanks!



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent