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/12/2008 8:53:00 AM
Here is a better example of my problem. Consider the XML below.

<ns1:project xmlns:ns1="http://www.namespaces.com/ns1">
          <ns1:elementOne xmlns:ns2="http://www.namespaces.com/ns2">
                     <ns2:elementTwo>Data</ns2:elementTwo>
          </ns1:elementOne>
</ns1:project>

I know this is a strange way to declare the second namespace 
(under an ns1 element), but according to the XML spec. any child element to 
ns1:elementOne will be able to use the ns2 namespace.

Also note that in my schema files I don't use any imports or external 
references.

So the problem is as follows. If you change the URI for ns1 to something 
unknown
by my schemaCache ("http://www.namespaces.com/ns1/junk" for instance) I get 
a validation error from MSXML 6.0 saying the namespace is unknown.

If I do the same thing to the URI for ns2, I get no error. However, if the 
ns2 namespace is known, it WILL validate all the elements under ns2.

In MSXML 4.0 this was not an issue. I encountered it when moving to 6.0.

Any suggestions on how to fix this, or where else to go for help?



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