Matakuliah : M0492 / Web-based Programming Lanjut
Tahun
: 2007
Web-based Programming Lanjut
Pertemuan 10
XML and ADO
•
•
•
•
•
•
•
Bina Nusantara
ADO Recordsets Stored as XML
ADO Recordset Namespace
ADO Recordset Schema
Data Islands and Binding
Saving Recordsets as XML
Opening Recordsets
Extensible Styling Language (XSL)
ADO Recordsets Stored as XML
• The first thing is how ADO presents its data as XML.
• This is the only way XML can be extracted from ADO at the moment.
<z:row au_id=“172-32-1176” au_lname=“White” au_fname=“Johnson” />
<z:row au_id=“213-46-8915” au_lname=“Green” au_fname=“Marjorie” />
• We have an element for each row in the table, and the fields are attributes of the
row element.
• This way of defining data using attributes for each data item means that some of
that repetition is reduced
Bina Nusantara
ADO Recordset Namespace
• If using ADO to send and retrieve XML data then there will be a schema associated
with the XML data file.
• The schema is embedded into the XML, at the top of document.
<xml xmlns:s= “uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882”
xmlns:dt= “uuid:C2F41010-65B3-11d1-A29F-00AA00C14882”
xmlns:rs= “urn:schemas-microsoft-com:rowset”
xmlns:z= “#RowsetSchema”>
Bina Nusantara
ADO Recordset Namespace
Namespace
Description
s
Identifies the URI for the schema itself.
dt
Identifies the URI for data types
rs
Identifies the rowset (recordset)
z
Identifies the individual rows
Using namespaces ensures that the element names
chosen by Microsoft are applied to the correct schema.
Bina Nusantara
ADO Recordset Schema
• The Row Element
– Element that identifies schema:
<s:Schema id=“RowsetSchema”>
– The definition of an element by ElementType
<s:ElementType name=“row” content=“eltOnly”>
Value of Content
empty
The element cannot contain any content
textOnly
The element can only contain text, and not other elements
eltOnly
The element can only contain other elements, and not text.
both
Bina Nusantara
Description
The element can contain both text and other elements
ADO Recordset Schema
– A row element that can only contain other elements.
<z:row au_id=“172-32-1176” au_lname=“White” au_fname=“Johnson”
phone =“408 496-7223” address=“10932 Bigge Rd.”
city=“Menlo Park” state=“CA” zip=“94025” contract=“True” />
– This is essentially an empty tag, but for the schema, empty means no content
at all, including attributes.
Bina Nusantara
ADO Recordset Schema
• The Field Attributes
– At the XML data, the field values are represented as attributes.
– Schema must define attributes.
• First, the definition of the attribute itself
• Second, the definition of the data type for the attribute.
– Define an attribute
• define what it will be called – this should map to the field name of the data.
• define 2 other attributes :
– First, a unique number for each attribute – this is the first attribute,
the remaining attributes are sequentially numbered.
– The other attribute is “writeunknown” which identifies whether the
attribute can be updated
Bina Nusantara
ADO Recordset Schema
<s:AttributeType name=“au_id” rs:number=“1” rs:writeunknown=“true” >
AttributeType also has a child element to define the
data type of the attribute:
<s:datatype dt:type=“string” dt:maxLength=“11” rs:maybenull=“false” />
• Data Types
– When generating XML from ADO, the data types are automatically created.
Bina Nusantara
ADO Recordset Schema
The table below lists the data type supported by the XML-data schema
Type
Description
bin.base64
A binary object
bin.hex
Hexadecimal octets
boolean
0 or 1 (0 is false, and 1 is true)
char
A one character length string
date
An ISO 8601 date, without the time. The format is yyyy-mm-dd
dateTime
An ISO 8601 date, optionally with the time. The format is yyyy-mm-ddThh:mm:ss
dateTime.tz
An ISO 8601 date, optionally with the time and timezone. The format is yyyy-mm-ddThh:mm:ss-hh:mm.
The timezoneindicates the number of hours + or – GMT
fixed.14.4
Fixed with floating point number, with up to 14 digits to the left of the decimal place and up to 4 to the
right.
float
Floating point number
int
Integer number
number
Floating point number
Bina Nusantara
ADO Recordset Schema
Type
Description
time
An ISO 8601 time. The format is hh:mm:ss
time.tz
An ISO 8601 time with the optional timezone. The format is hh:mm:ss-hh:mm
i1
An 8 bit integer (1 byte)
i2
A 16 bit integer (2 byte)
i4
A 32 bit integer (4 byte)
r4
A 4 byte real number
r8
An 8 byte real number
ui1
An 8 bit unsigned integer (1 byte)
ui2
A 16 but unsigned integer (2 byte)
ui4
A 32 bit unsigned integer (4 byte)
uri
An Universal Resource Indicator
uuid
A set of hex digits representing a universally unique identifier. A GUID is an example of this
Bina Nusantara
ADO Recordset Schema
The W3C also allow a set of primitive types
Type
Description
entity
Represents the XML ENTITY type
entities
Represents the XML ENTITIES type
enumeration
Represents an enumerated type
id
Represents the XML ID type
idref
Represents the XML IDREF type
idrefs
Represents the XML IDREFS type
nmtoken
Represents the XML NMTOKEN type
nmtokens
Represents the XML NMTOKENS type
notation
Represents the XML NOTATION type
string
Represents a string type
Bina Nusantara
Data Islands and Binding
• Create a data island with the <XML> tag in an HTML page
<XML ID=“dsoData” SRC=“authors.xml”></XML>
This reference an external XML file as the source of the data.
Alternatively you can embed the XML data within the <XML> tag.
<XML ID=“dsoData”>
<Authors>
<Author>
<au_id>172-32-1176</au_id>
<au_lname>White</au_lname>
<au_fname>Johnson</au_fname>
</Author>
<Authors>
</XML>
Bina Nusantara
Data Islands and Binding
• Binding can take two forms
– First, bind a single elements
<INPUT TYPE=“TEXT” DATASRC=“#dsoData” DATAFLD=“au_id”></INPUT>
– Second, use table binding
<TABLE DATASRC =“#dsoData”>
<TR>
<TD> <INPUT TYPE=“TEXT” DATAFLD=“au_id”></INPUT></TD>
<TD> <INPUT TYPE=“TEXT” DATAFLD=“au_fname”></INPUT></TD>
</TR>
</TABLE>
Bina Nusantara
Data Islands and Binding
• Binding Hierarchical Data
There’ll be a problem if you try to bind a set of XML data generated by ADO.
Because IE doesn’t recognize schemas as a definition of the data.
<XML>
<s:Schema>
….. schema data
</s:Schema>
<rs:data>
<z:row … />
<z:row … />
</rs:data>
</XML>
So IE sees two sets of data – the schema and the actual
Bina Nusantara
Data Islands and Binding
The solution to this hierarchical binding is to use two levels of binding
<TABLE ID=“tblData” DATASRC=“#dsoData” DATAFLD=“rs:data”>
<TR><TD>
<TABLE ID=“tblData” BORDER=“1” DATASRC =“#dsoData” DATAFLD=“z:row”>
<TR>
<TD> <SPAN DATAFLD=“au_id”></SPAN></TD>
<TD> <SPAN DATAFLD=“au_fname”></SPAN></TD>
</TR>
</TABLE>
</TD></TR>
</TABLE>
Bina Nusantara
Data Islands and Binding
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Bina Nusantara
<Publishers>
<Publisher>
</Publisher>
</Publishers>
<pub_id>0736</pub_id>
<pub_name>New Moon Books</pub_name>
<city>Boston</city>
<state>MA</state>
<country>USA</country>
<titles>
<title_id>BU2075</title_id>
<title>You Can Combat Computer Stress!</title>
<price>$2.99</price>
<pubdate>6/30/91</pubdate>
<sale>
<stor_id>7896</stor_id>
<ord_num>X999</ord_num>
<ord_date>2/21/93</ord_date>
<qty>35</qty>
</sale>
</titles>
<employee>
<emp_id>PDH4740M</emp_id>
<fname>Palle</fname>
<minit>D</minit>
<lname>Ibsen</lname>
</employee>
<employee>
<emp_id>KFJ64308F</emp_id>
<fname>Karin</fname>
<minit>F</minit>
<lname>Josephs</lname>
</employee>
1.
<HTML><HEAD><TITLE>DataBinding.html</TITLE></HEAD>
2.
3.
<BODY>
<XML ID="dsoData" SRC="publishers.xml"></XML>
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
<TABLE ID="tblPublishers" DATASRC="#dsoData" BORDER="1">
<TR><TD><DIV DATAFLD = "pub_name"></DIV></TD>
<TD><DIV DATAFLD = "city"></DIV></TD>
<TD><DIV DATAFLD = "state"></DIV></TD> </TR>
<TR> <TD COLSPAN=4>
<TABLE>
<TR><TD>Titles</TD> </TR>
<TR><TD COLSPAN=4>
<TABLE DATASRC="#dsoData" DATAFLD="titles" BORDER="1">
<TR><TD><DIV DATAFLD = "title"></DIV></TD><TD><DIV DATAFLD = "price"></DIV></TD>
</TR>
<TR><TD COLSPAN=3>
<TABLE DATASRC="#dsoData" DATAFLD="sale" BORDER="1">
<TR><TD><DIV DATAFLD = "ord_date"></DIV></TD><TD><DIV DATAFLD = "qty"></DIV></TD></TR>
</TABLE>
</TD>
</TR>
</TABLE>
</TD> </TR>
<TR> <TD>Employees</TD></TR>
<TR> <TD COLSPAN=4>
<TABLE DATASRC="#dsoData" DATAFLD="employee" BORDER="1">
<TR><TD><DIV DATAFLD = "fname"></DIV></TD> <TD><DIV DATAFLD = "lname"></DIV></TD> </TR>
</TABLE>
</TD> </TR>
</TABLE>
</TD>
</TR>
</TABLE>
</BODY>
Bina Nusantara
Data Islands and Binding
Bina Nusantara
Saving Recordsets as XML
• ADO generate XML recordsets by using the Save method of the Recordset object,
and specifying the format as adPersistXML or 1.
• Persisting ADO Recordsets to a Stream
A Stream is simply a block of data in memory, which is not processed in any way.
ADO 2.5 introduces the new Stream object, and can be the target for saving a
recordset
Set rsAuthors = Server.CreateObject(“ADODB.Recordset”)
Set stmAuthors = Server.CreateObject(“ADODB.Stream”)
rsAuthors.Open “authors”, strConn
rsAuthors.Save stmAuthors, 1 ‘adPersistXML
Bina Nusantara
Saving Recordsets as XML
Use the methods and properties of the stream to manipulate the data.
For example, extract the XML into a string using the ReadText method:
strXMLAuthors = stmAuthors.ReadText
At this stage strXMLAuthors contains the complete XML recordset, including the
schema.
• Persisting ADO Recordsets to the Response Object
Saves the recordset as XML directly into the Response object.
rsAuthors.Save Response, 1 ‘adPersistXML
Bina Nusantara
Saving Recordsets as XML
<%
•
•
•
‘Using the DOM to create a Data Island
Dim strConn
Dim xmlDOM
Dim strXML
•
•
Set rsAuthors = Server.CreateObject("ADODB.Recordset")
Set xmlDOM = Server.CreateObject("MSXML.DOMDocument")
•
•
rsAuthors.Open "authors", strConn
rsAuthors.Save xmlDOM, 1
•
•
rsAuthors.Close
Set rsAuthors = Nothing
•
strXML = xmlDOM.xml
•
strXML = "<XML" & Mid(strXML,5,Len(strXML)-10) & "XML>"
•
%>
Response.Write strXML
Bina Nusantara
Saving Recordsets as XML
Bina Nusantara
Saving Recordsets as XML
<XML ID="dsoAuthors">
<%
‘Using Response to Create a Data Island
•
Dim rsAuthors
•
Set rsAuthors = Server.CreateObject ("ADODB.Recordset")
•
rsAuthors.Open "authors", strConn
•
rsAuthors.Save Response, 1
•
rsAuthors.Close
•
Set rsAuthors = Nothing
%>
</XML>
To see the result on our HTML page,
activate the View Source menu
Bina Nusantara
Saving Recordsets as XML
Bina Nusantara
Saving Recordsets as XML
<xml xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882'
xmlns:dt='uuid:C2F41010-65B3-11d1-A29F-00AA00C14882'
xmlns:rs='urn:schemas-microsoft-com:rowset'
xmlns:z='#RowsetSchema'>
<s:Schema id='RowsetSchema'>
<s:ElementType name='row' content='eltOnly' rs:CommandTimeout='30'>
<s:AttributeType name='au_id' rs:number='1' rs:writeunknown='true'>
<s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='11' rs:maybenull='false'/>
</s:AttributeType>
<s:AttributeType name='au_lname' rs:number='2' rs:writeunknown='true'>
<s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='40' rs:maybenull='false'/>
</s:AttributeType>
….
<s:extends type='rs:rowbase'/>
</s:ElementType>
</s:Schema>
<rs:data>
<z:row au_id='172-32-1176' au_lname='White' au_fname='Johnson' phone='408 496-7223' address='10932 Bigge Rd.'
city='Menlo Park' state='CA' zip='94025' contract='True'/>
<z:row au_id='213-46-8915' au_lname='Green' au_fname='Marjorie' phone='415 986-7020' address='309 63rd St. #411'
city='Oakland' state='CA' zip='94618' contract='True'/>
<z:row au_id='238-95-7766' au_lname='Carson' au_fname='Cheryl' phone='415 548-7723' address='589 Darwin Ln.'
city='Berkeley' state='CA' zip='94705' contract='True'/>
<z:row au_id='267-41-2394' au_lname='O&#x27;Leary' au_fname='Michael' phone='408 286-2428' address='22 Cleveland Av. #14'
city='San Jose' state='CA' zip='95128' contract='True'/>
<z:row au_id='274-80-9391' au_lname='Straight' au_fname='Dean' phone='415 834-2919' address='5420 College Av.'
city='Oakland' state='CA' zip='94609' contract='True'/>
<z:row au_id='341-22-1782' au_lname='Smith' au_fname='Meander' phone='913 843-0462' address='10 Mississippi Dr.'
city='Lawrence' state='KS' zip='66044' contract='False'/>
<z:row au_id='409-56-7008' au_lname='Bennet' au_fname='Abraham' phone='415 658-9932' address='6223 Bateman St.'
city='Berkeley' state='CA' zip='94705' contract='True'/>
….
</rs:data>
</xml>
Bina Nusantara
Opening Recordsets
1.
2.
3.
4.
<%
Set rsData = Server.CreateObject("ADODB.Recordset")
Set stmData = Server.CreateObject("ADODB.Stream")
Set domXML = Server.CreateObject("MSXML.DOMDocument")
5.
rsData.Open "authors", strConn
6.
7.
rsData.Save domXML, 1
rsData.Close
8.
9.
10.
11.
12.
stmData.Open
stmData.WriteText domXMl.xml
stmData.SetEOS
stmData.Position = 0
rsData.Open stmData
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
Response.Write "<H1>Opening Authors Recordset from a DOM Object<HR></H1>"
Response.Write "<TABLE><TR><TD>au_id</TD><TD>au_fname</TD><TD>au_lname</TD><TD>phone</TD></TR>”
While rsData.EOF=False
Response.Write "<TR>"
Response.Write "<TD><INPUT TYPE='TEXT' VALUE=" & rsData(0) & "></INPUT></TD>"
Response.Write "<TD><INPUT TYPE='TEXT' VALUE=" & rsData(1) & "></INPUT></TD>"
Response.Write "<TD><INPUT TYPE='TEXT' VALUE=" & rsData(2) & "></INPUT></TD>"
Response.Write "<TD><INPUT TYPE='TEXT' VALUE=" & rsData(3) & "></INPUT></TD>"
Response.Write "</TR>"
rsData.moveNext
Wend
Response.Write "</TABLE>"
%>
Bina Nusantara
‘adPersistXML=1
Opening Recordsets
Bina Nusantara
Extensible Styling Language (XSL)
• XSL is an XML-based language to allow us to transform XML data.
– This transformation can be between one format of XML and another, or from
XML to HTML or from XML to any type of text output.
• XML tags just identify the data. If we want to display XML data we need to style it
in some way.
• XSL made up of two parts:
– a transformation language
– a formatting language
Bina Nusantara
Extensible Styling Language (XSL)
• XSL Stylesheets
– The idea behind XSL is that we have a set of rules that match elements or
attributes in the XML.
– These rules are known as template, and within a template we can loop through
elements and attributes, apply other templates and perform other types of
processing
– Text that is not part of an XSL processing instruction is output, so this is how
we transform XML – by matching elements and outputting text and element
values
Bina Nusantara
Extensible Styling Language (XSL)
• XSL Stylesheets
– The top-level tag identifies the stylesheet and the namespace, which
applies to it.
<xsl:stylesheet xmlns:xsl=http://www.w3.org/TR/WD-xsl>
This finishing tag:
</xsl:stylesheet>
– within the stylesheet, the tags take the form of templates, which match
portions of the XML document.
Bina Nusantara
Extensible Styling Language (XSL)
• This stylesheet converts an ADO recordset in XML into an HTML table.
<xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">
<xsl:template match ="/">
<HTML>
<BODY>
<xsl:apply-templates select="//rs:data" />
</BODY>
</HTML>
</xsl:template>
<xsl:template match="//rs:data">
<TABLE BORDER="1">
<xsl:for-each select="z:row">
<TR>
<xsl:for-each select="(@*)">
<TD>
<xsl:value-of/>
</TD>
</xsl:for-each>
</TR>
</xsl:for-each>
</TABLE>
</xsl:template>
Bina Nusantara
</xsl:stylesheet>
Extensible Styling Language (XSL)
– We start with the stylesheet declaration:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">
– The first command is a template command telling us which element we should
match. In this case, we are matching the root element, denoted by the /
symbol:
<xsl:template match ="/">
– At this stage we have started the processing of the XML tree. If we are
converting to HTML, we need to output HTML tags that start an HTML
document.
<HTML>
<BODY>
Bina Nusantara
Extensible Styling Language (XSL)
– Now we need to find the actual data. Use apply-templates to search for
another template. This template will be applied, and once all processing in it
has completed, processing returns to the current template.
<xsl:apply-templates select="//rs:data" />
– After the inner template has been processed we can finish off our HTML
document
</BODY>
</HTML>
</xsl:template>
Bina Nusantara
Extensible Styling Language (XSL)
– To process each row of data, use the “for-each” statement, which is as much
the same as a “for..each” loop in VBScript. The “select” part of the statement
tells XSL which elements to loop though.
<xsl:for-each select="z:row">
– To process the attributes, again use the “for-each” construct, with a different
“select”. To match an attribute, we have to use the @ symbol, so @* means
match every attribute.
<xsl:for-each select="(@*)">
Bina Nusantara
Extensible Styling Language (XSL)
– The “value-of” instruction tells XSL to output the value of a node. And since
we are not stating anything specific to output, the value of the current node is
output:
<xsl:value-of/>
• Embedded Styling
The easiest way to apply an XSL stylesheet is to specify it in the XML file.
<?xml-stylesheet type=“text/xsl” href=“xsl_file_name.xsl”?>
Bina Nusantara
Extensible Styling Language (XSL)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
<?xml version = "1.0"?>
<?xml:stylesheet type = "text/xsl" href = "contact_list.xsl"?>
<!-- contact.xml -->
<contacts>
<contact>
<lastname>Black</lastname>
<firstname>John</firstname>
</contact>
<contact>
<lastname>Green</lastname>
<firstname>Sue</firstname>
</contact>
<contact>
<lastname>Red</lastname>
<firstname>Bob</firstname>
</contact>
<contact>
<lastname>Blue</lastname>
<firstname>Mary</firstname>
</contact>
<contact>
<lastname>White</lastname>
<firstname>Mike</firstname>
</contact>
<contact>
<lastname>Brown</lastname>
<firstname>Jane</firstname>
</contact>
</contacts>
Bina Nusantara
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
<?xml version = "1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">
<!-- contact_list.xsl -->
<xsl:template match ="/">
<HTML>
<BODY>
Bina Nusantara
<DIV ID = "data"> <xsl:apply-templates/> </DIV>
<SCRIPT TYPE="text/javascript" LANGUAGE="JavaScript">
<xsl:comment><![CDATA[
var styleSheet = document.XSLDocument;
var xmlDocument = document.XMLDocument;
function update(scope, sortKey)
{
var sortBy = styleSheet.selectSingleNode("//@order-by");
sortBy.value = sortKey;
var scopeBy = styleSheet.selectSingleNode("//xsl:for-each/@select");
scopeBy.value = scope;
data.innerHTML = xmlDocument.documentElement.transformNode(styleSheet);
}
]]>
</xsl:comment>
</SCRIPT>
<TABLE BORDER = "1" DATASRC = "#xmlData" DATAPAGESIZE = "4" ID = "tbl">
<THEAD>
<TR> <TH>Last Name</TH> <TH>First Name</TH> </TR>
</THEAD>
<TR> <TD><SPAN DATAFLD = "lastname"></SPAN></TD>
<TD><SPAN DATAFLD = "firstname"></SPAN></TD>
</TR>
</TABLE>
35.
36.
37.
38.
<INPUT TYPE = "button" VALUE = "Revert" ONCLICK = "update('contact','+firstname;+lastname');"/>
<BR/>
<INPUT TYPE = "button" VALUE = "Sort By Last Name" ONCLICK =
"update('contact','+lastname;+firstname');"/>
<INPUT TYPE = "button" VALUE = "Sort By First Name" ONCLICK =
"update('contact','-firstname;+lastname');"/>
<BR/>
<INPUT TYPE = "button" VALUE = "Filter Last Name Start with 'B'"
ONCLICK = "update('contact[lastname &gt; \'B\' and lastname &lt; \'C\']','+firstname;+lastname');"/>
<BR/>
<INPUT TYPE = "button" VALUE = "|&lt;" ONCLICK = "tbl.firstPage();"/>
<INPUT TYPE = "button" VALUE = "&lt;" ONCLICK = "tbl.previousPage();"/>
<INPUT TYPE = "button" VALUE = "&gt;" ONCLICK = "tbl.nextPage();"/>
<INPUT TYPE = "button" VALUE = "&gt;|" ONCLICK = "tbl.lastPage();"/>
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.
</BODY>
</HTML>
</xsl:template>
<xsl:template match="contacts">
<XML ID = "xmlData">
<contacts>
<xsl:for-each select = "contact"
order-by = "+firstname;+lastname">
<contact>
<lastname><xsl:value-of select = "lastname"/> </lastname>
<firstname><xsl:value-of select = "firstname"/> </firstname>
</contact>
</xsl:for-each>
</contacts>
</XML>
</xsl:template>
</xsl:stylesheet>
Bina Nusantara
Extensible Styling Language (XSL)
Bina Nusantara
Extensible Styling Language (XSL)
Bina Nusantara