1 / 6

XSD in Web Services

XSD in Web Services. Douglas Purdy Distributed Systems Group Microsoft. Web Services Model. Microsoft Web Services Principles. Support serializable CLR types Support v1 -> v2 -> v1 scenarios without loss Support graph semantics Support types to author application protocols

landry
Download Presentation

XSD in Web Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. XSD in Web Services Douglas Purdy Distributed Systems Group Microsoft

  2. Web Services Model

  3. Microsoft Web Services Principles • Support serializable CLR types • Support v1 -> v2 -> v1 scenarios without loss • Support graph semantics • Support types to author application protocols • Work to ensure usability on the “other side” • Support all of XSD • If it is a valid XSD our tools should support it • The binding code may not be strongly-typed “All schemas are supported, some are more supported than others”

  4. Supporting serializable CLR types • A “de facto” XSD profile exists for WS • Defined by SoapBuilders • Largely sequence and XSD simple types • We added some features to the profile • Completely schema valid & interoperable • Versioning, Graphs, Generics, … • Causes issues with the “other side” • Doesn’t support the constructs we use • Doesn’t generate “usable” code when they do

  5. Supporting all of XSD • Full XSD  CLR mapping is hard • We tried it and it really wasn’t usable • We have great XML programming models • This is a reasonable way to support all of XSD • We are investing in even better XML tools • No details here ;-) • Currently, we support “fallback generation” • Generate the most “usable” typed model • Generate a backup typed model (old technology) • Generate a Message (model for a SOAP envelope)

  6. Things to Explore • UPA, UPA, UPA, UPA • xsi:id & xsi:ref • must-understand? • Domain specific profiles of XSD (WS-I, …)

More Related