Bug 18148 - xs:key in .xsd combined with xsi:type in .xml does not validate
Summary: xs:key in .xsd combined with xsi:type in .xml does not validate
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.XML ()
Version: 3.2.x
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-03-04 06:45 UTC by tor
Modified: 2015-03-17 16:00 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
xsd, xml, cs files to test, patch to solve problem (1.77 KB, application/octet-stream)
2014-03-04 06:45 UTC, tor
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description tor 2014-03-04 06:45:23 UTC
Created attachment 6208 [details]
xsd, xml, cs files to test, patch to solve problem

An xs:key with xs:selector and xs:field in schema and a type change using xsi:type in xml does not validate. Example files and a diff is attached. The diff change solves the problem, but I don't know if this patch has undesired side effects.

Error: XmlSchema error: Key sequence is missing.

Kind Regards

Tor Stenvaag
Comment 1 Atsushi Eno 2015-03-17 16:00:36 UTC
We imported referencesource and this issue has gone.