XML

XML 10
MS XML DOM
XML Attributes
XML Links

XML

	Designed for distributed – XML by default
	Moved between tiers as XML
	New Objects
	DataSetCommand
	DataSet
	Proper Data Types: i.e. Customer.LastName
	XML Integration
	DataSets
	Object Persistence
	Web Services
	Visual XML Designer
	SQL 2000 allows you to return XML via an http:// request
	Can pass SQL2000 query to SQL 2000 to get XML using ReadXML
	Support for RAD N-Tier apps
	Component Designer to design ADO+ objects and auto generate type datasets
	XML Designer for XML and XSD
	Create a menu system using XML
	Look into SAX parsing for XML vs. XML DOM
	Look at Session #65 for most useful XML DOM objects
	Store XMLData field when you have more selects than inserts/updates in a database
	Abbreviated Microsoft XML Document Object Model
	XML 10-SECOND TUTORIAL
	XML Attributes vs. Elements

XSL

Use ADO 2.5 to export recordsets from your tables and you can use the attached XSL file to easily format your data into easy to read tables that take the column headers from the schema

Recordset Schema

After you have this simple XSL, you can include the following line of code at the top or your exported XML files

<?xml:stylesheet type="text/xsl" href="RecordsetXML.xsl" ?>

On an IIS machine, one could create an ASP page which could use our XSL

	Create an ASP that will open a recordset
	The recordset could then be persisted to a file, or stream
	The stylesheet line above and the stream could be sent directly to the ASP response method
	The browser would receive formatted a page that actually was formed from the XML and XSL

There are many additional ways in which to use XSL

SOAP

Agree to a common wire format (SOAP)

Describe what a service can do (Schemas)

Locate a new service on the Web (Disco)

Want to convert existing components to SOAP

SOAP toolkit has a ROPE object

SDL Wizard generates SCL

Asks for components

server to look for requests

location of source

the virtual directory needs listener.asp

Developer must add a reference to ROPE library

oRope.LoadServiceDescription

No intellisense today – VS.NET will go get the methods from DISCO at design time

Warning! – SOAP calls are case sensitive because XML is

Use Cdataize to return XML wrapped in CDATA TAG

SOAP in a nutshell

	The request SOAP
	POST /path/foo.pl HTTP/1.1 Content-Type: text/xml MethodName: interfaceURI#Add Content-Length: nnnn <soap:Envelope xmlns:soap='uri for soap'> <soap:Body>
	<Add xmlns='interfaceURI'> <arg1>24</arg1> <arg2>53.2</arg2> </Add> </soap:Body> </soap:Envelope> 200 OK Content-Type: text/xml Content-Length: nnnn <soap:Envelope xmlns:soap='uri for soap'> <soap:Body>
	The response SOAP would be
	<AddResponse xmlns='interfaceURI' > <sum>77.2</sum> </AddResponse> </soap:Body> </soap:Envelope>

XSD

The SOAP type system is compatible with and leverages XML Schema Definition (XSD) language

Sample XSD

	<type name='Point' > <element name='x' type='double' /> <element name='y' type='double' /> </type> <element name='Point' type='Point' />
	<Point xmlns='interfaceURI'> <x>23</x><y>34</y> </Point>
	<type name='calculateArea' > <element name='origin' type='Point' /> <element name='corner' type='Point' nullable='true' /> </type> <element name='calculateArea' type='calculateArea' />
	<calculateArea xmlns='interfaceURI'> <origin><x>23</x><y>34</y></origin> <corner><x>23</x><y>34</y></corner> </calculateArea>