anyAttribute with specific namespace doesn't work

Question

4.00/5 (2 votes)

See more:

hello, i've wasted a whole day for this, can't find the solution.

i have the following main schema:

XML

<?xml version="1.0" encoding="utf-8"?>
<xs:schema elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">  
  <xs:element name="Users">
    <xs:complexType>     
      <xs:attribute name="FirstName" type="xs:string" use="optional" />
      <xs:anyAttribute namespace="http://www.w3.org/2001/AppLog"/>
    </xs:complexType>
  </xs:element>
</xs:schema>

i want to use the "anyAttribute" to get an attribute from a specific schema, so i declared this secondary schema:

XML

<?xml version="1.0" encoding="utf-8"?>
<xs:schema elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"
           targetNamespace="http://www.w3.org/2001/AppLog">
  <xs:attribute name="SystemUsers" type="xs:string" default="abc"/>
</xs:schema>

then, i tried to validate the schema against this xml:

HTML

<br />
<Users UserPreferencesSafe=""abcd"" SystemUsers=""abc""/><br />

i do it with adding the 2 schemas to the schema set (XMLSchemaSet.Add),
then i use the XMLDocument.Validate with this schema set.

i get:
The validation raised a error:The 'SystemUsers' attribute is not allowed.

by the way, if i use anyAttribute namespace="##any", and add the 2 schemas it works. but i need to be specific.

what am i missing?
thanks.

Posted 31-Jan-12 4:50am

arielbeck

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2012-01-31T06:37:00

It looks like you misuse complexType: you cannot specify content of complex type without intermediate XSD node describing the type of complex type content, such as sequence, like in this example:

XML

<xs:element name="ExistingRecord">
    <xs:complexType>
        <xs:sequence>
            <xs:element name="ExistingFieldElement" type="xs:string" />
        </xs:sequence>
        <xs:anyAttribute />
    </xs:complexType>
</xs:element>

This example is extracted from http://msdn.microsoft.com/en-us/library/aa562055.aspx[^].

I'm not sure if this is the only problem, but this is the first one which caught my eye.

—SA