By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,631 Members | 1,950 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,631 IT Pros & Developers. It's quick & easy.

XML & XSD Schema validation - "all"

P: n/a
I'm running into a problem with schema validation. For some reason, if a
schema has an xs:all section to it, it does not validate correctly. It
seems to treat it as a sequence. My understanding is that switching to an
xs:all should not require that the child elements be in any particular
order - yet that is exactly the error I am seeing.

I've tested this on both .NET 1.1 and .NET 2.0 and I get the same error.
The XML validates against the xs:all schema just fine in XMLSpy 2005.

Any ideas?

--
Adam Clauss

Mar 15 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
vj
Interesting.... i have not had this problem.. i do the same... uhmm, .NET
1.0 and above use MSXML.. are you aware of that?

VJ

"Adam Clauss" <ca*****@tamu.edu> wrote in message
news:12*************@corp.supernews.com...
I'm running into a problem with schema validation. For some reason, if a
schema has an xs:all section to it, it does not validate correctly. It
seems to treat it as a sequence. My understanding is that switching to an
xs:all should not require that the child elements be in any particular
order - yet that is exactly the error I am seeing.

I've tested this on both .NET 1.1 and .NET 2.0 and I get the same error.
The XML validates against the xs:all schema just fine in XMLSpy 2005.

Any ideas?

--
Adam Clauss

Mar 15 '06 #2

P: n/a
"vj" <vi********@yahoo.com> wrote in message
news:O9**************@tk2msftngp13.phx.gbl...
Interesting.... i have not had this problem.. i do the same... uhmm, .NET
1.0 and above use MSXML.. are you aware of that?

VJ


Would you mind posting a short snippet of the code you are using to
validate?
I've gone round and around with this, and I just can't figure it out.
Our code basically matches the other samples I've found, but none of those
samples mentioned trying against xs:all either.

--
Adam Clauss
Mar 15 '06 #3

P: n/a
vj
If you have what the samples have... then, that is what I have... nothing
different... I am thinking this more of mismatch of DLL file... just
thinking how do we track it..., do u have a sample..? I can run on my
machine, see if I get it..

VJ

"vj" <vi********@yahoo.com> wrote in message
news:O9**************@tk2msftngp13.phx.gbl...
Interesting.... i have not had this problem.. i do the same... uhmm, .NET
1.0 and above use MSXML.. are you aware of that?

VJ

"Adam Clauss" <ca*****@tamu.edu> wrote in message
news:12*************@corp.supernews.com...
I'm running into a problem with schema validation. For some reason, if a
schema has an xs:all section to it, it does not validate correctly. It
seems to treat it as a sequence. My understanding is that switching to
an xs:all should not require that the child elements be in any particular
order - yet that is exactly the error I am seeing.

I've tested this on both .NET 1.1 and .NET 2.0 and I get the same error.
The XML validates against the xs:all schema just fine in XMLSpy 2005.

Any ideas?

--
Adam Clauss


Mar 15 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.