Jump to content

Recommended Posts

Posted

On a related note to my previous question, how come if I declare an xml file like this I get errors:

 

testfalse******

***</font color="#a52a2a"data/font>

</font color="#a52a2a"settings/font>

 

My schema defines a type attribute, and if I remove the xsi:type attribute from the second setting attribute the file validates OK. But if I insert that xsi:type attribute then validation complains about all the rest of the attributes in that element. (Not in the previous element.)

 

(Before everyone shouts at me, I didn't create the stupid schema that defines the type attribute, and probably most crucially that schema doesn't define a target namespace.)

 

Sigh... This is all proving a complete pain in the bum, and it may just be easier to check the "type" attribute and parse accordingly... Urgh! Annoyingness.

 

More...

 

View All Our Microsft Related Feeds

  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...