Home > Articles > Web Services > XML

Sams Teach Yourself XML in 21 Days

Sep 16, 2005

📄 Contents

␡

⎙ Print

< Back Page 238 of 288 Next >

Recommended Book 

Sams Teach Yourself XML in 21 Days, 3rd Edition

Learn More Buy

Binding HTML Elements to HTML Data

Many of the HTML elements supported in Internet Explorer can be bound to DSOs. We use the DATASRC and DATAFLD attributes to bind an element to a DSO; to do so, we assign the DATASRC attribute to the name of a DSO and the DATAFLD attribute to the name of the data field we want to bind the element to. After it's been bound, the element will display the data in the current record in the DSO. In code, we can use the moveFirst, moveLast, moveNext, and movePrevious methods to make other records the current record, and the data in the bound elements is updated automatically.

Say, for instance, that we've bound an HTML text field to the states DSO and to the name field in the DSO's records. When the page first loads, that control will display the name "California". Executing the moveNext method will make the next record in the record set the current record, and the text field will display the name "Massachusetts".

Here's a list of HTML elements in Internet Explorer, indicating what elements may be bound and what property is bound when we use the DATASRC and DATAFLD attributes:

A — Data is bound to the href property; changes are not automatically updated.
APPLET — Data is bound to the param property; changes are automatically updated.
BUTTON — Data is bound to the value property; changes are not automatically updated.
DIV — Data is bound to the innerText and innerHTML properties; changes are not automatically updated.
FRAME — Data is bound to the src property; changes are not automatically updated.
IFRAME — Data is bound to the src property; changes are not automatically updated.
IMG — Data is bound to the src property; changes are not automatically updated.
INPUT TYPE=BUTTON — Data is bound to the value property; changes are not automatically updated.
INPUT TYPE=CHECKBOX — Data is bound to the checked property; changes are automatically updated.
INPUT TYPE=HIDDEN — Data is bound to the value property; changes are automatically updated.
INPUT TYPE=PASSWORD — Data is bound to the value property; changes are automatically updated.
INPUT TYPE=RADIO — Data is bound to the checked property; changes are automatically updated.
INPUT TYPE=TEXT — Data is bound to the value property; changes are automatically updated.
LABEL — Data is bound to the value property; changes are not automatically updated.
MARQUEE — Data is bound to the innerText and innerHTML properties; changes are not automatically updated.
OBJECT — Data is bound to the objects property; changes are automatically updated.
PARAM — Data is bound to the param property; changes are automatically updated.
SELECT — Data is bound to the text property of an option; changes are automatically updated.
SPAN — Data is bound to the innerText and innerHTML properties; changes are not automatically updated.
TABLE — This element constructs an entire table; changes are not automatically updated.
TEXTAREA — Data is bound to the value property; changes are automatically updated.

Let's put all this to work. You'll start by creating a DSO and using it to read the data from ch19_01.html. You'll navigate through that data by using buttons. Begin by creating the DSO by using the <OBJECT> element, naming it states, and connecting it to your data file, ch19_01.html:

<HTML>
    <HEAD>
        <TITLE>
            Using the MSHTML Data Source Object
        </TITLE>
    </HEAD>

    <BODY>
        <H1>
            Using the MSHTML Data Source Object
        </H1>

        <OBJECT ID="states" DATA="ch19_01.html"
        HEIGHT="0" WIDTH="0"></OBJECT>
        .
        .
        .

Now connect the various data fields in the states DSO to HTML text fields by using the DATASRC and DATAFLD attributes—here's how that works for the name and population fields:

Name: <INPUT TYPE="TEXT" DATASRC="#states"
    DATAFLD="name" SIZE="10">

<BR><BR>
Population: <INPUT TYPE="TEXT" DATASRC="#states"
    DATAFLD="population" SIZE="10">

You can also bind data to other elements. Here's how to bind the data in the capital and flower fields to the text in <SPAN> elements:

<BR><BR>
Capital: <SPAN DATASRC="#states"
    DATAFLD="capital"></SPAN>

<BR><BR>
Flower: <SPAN DATASRC="#states" DATAFLD="flower">
</SPAN>

In fact, you can even bind the data in the bird fields to a <SELECT> control, which will display the state's bird by using a drop-down list:

<BR><BR>
Bird: <SELECT DATASRC="#states"
    DATAFLD="bird" SIZE="1">
    <OPTION VALUE="Quail">Quail
    <OPTION VALUE="Chickadee">Chickadee
    <OPTION VALUE="Bluebird">Bluebird
</SELECT>

When this page first appears, the data from the first record will appear in the bound controls. To let the user navigate to other records, you can use buttons and some JavaScript. These buttons will display a caption of << to move to the first record, > to move to the next record, and so on. For example, to let the user navigate to the first record, you'll use the states DSO's record set's moveFirst method, like this:

<BR><BR>
<BUTTON ONCLICK=
    "states.recordset.moveFirst()">&nbsp;&lt;&lt;&nbsp;
</BUTTON>

To navigate to the previous record, first check whether you're at the beginning of the record set by checking whether the states.recordset.BOF property is true. If it is not, navigate to the previous record like this:

<BUTTON ONCLICK="if (!states.recordset.BOF)
    states.recordset.movePrevious()">&nbsp;&lt;&nbsp;
</BUTTON>

Similarly, you can navigate to the next record if you're not already at the end of the record set, which you check by seeing whether the states.recordset.EOF property is true. If it is not, move to the next record with the moveNext method:

<BUTTON ONCLICK="if (!states.recordset.EOF)
    states.recordset.moveNext()">&nbsp;&gt;&nbsp;
</BUTTON>

To move to the last record in the record set, use the moveLast method:

<BUTTON ONCLICK=
    "states.recordset.moveLast()">&nbsp;&gt;&gt;&nbsp;
</BUTTON>

Listing 19.2 shows the full code for your HTML DSO document (ch19_02.html).

Example 19.2. An HTML DSO Document (`ch19_02.html`)

<HTML>
    <HEAD>
        <TITLE>
            Using the MSHTML Data Source Object
        </TITLE>
    </HEAD>

    <BODY>
        <H1>
            Using the MSHTML Data Source Object
        </H1>

        <OBJECT ID="states" DATA="ch19_01.html"
        HEIGHT="0" WIDTH="0"></OBJECT>

        Name: <INPUT TYPE="TEXT" DATASRC="#states"
            DATAFLD="name" SIZE="10">

        <BR><BR>
        Population: <INPUT TYPE="TEXT" DATASRC="#states"
            DATAFLD="population" SIZE="10">

        <BR><BR>
        Capital: <SPAN DATASRC="#states"
            DATAFLD="capital"></SPAN>

        <BR><BR>
        Bird: <SELECT DATASRC="#states"
            DATAFLD="bird" SIZE="1">
            <OPTION VALUE="Quail">Quail
            <OPTION VALUE="Chickadee">Chickadee
            <OPTION VALUE="Bluebird">Bluebird
        </SELECT>

        <BR><BR>
        Flower: <SPAN DATASRC="#states" DATAFLD="flower">
        </SPAN>

        <BR><BR>
        <BUTTON ONCLICK=
            "states.recordset.moveFirst()">&nbsp;&lt;&lt;&nbsp;
        </BUTTON>
        <BUTTON ONCLICK="if (!states.recordset.BOF)
            states.recordset.movePrevious()">&nbsp;&lt;&nbsp;
        </BUTTON>
        <BUTTON ONCLICK="if (!states.recordset.EOF)
            states.recordset.moveNext()">&nbsp;&gt;&nbsp;
        </BUTTON>
        <BUTTON ONCLICK=
            "states.recordset.moveLast()">&nbsp;&gt;&gt;&nbsp;
        </BUTTON>
    </BODY>
</HTML>

Figure 19.1 shows ch19_02.html at work. As shown in the figure, the data from ch19_01.html is indeed bound to your controls. The user can move from record to record easily by using the buttons at the bottom of the page.

Figure 19.1 Data binding with the MSHTML control.

The record set object in a DSO has these properties:

absolutePosition — Specifies the position of the current record in a record set.
BOF — Is set to true if the current record position in a record set is the first record.
cacheSize — Specifies the number of records from a record set that are cached locally.
cursorLocation — Specifies the location of the record set cursor for the record set.
editMode — Indicates whether editing is in progress.
EOF — Is set to true if the current record is the last record in the record set.
lockType — Specifies the type of database locking used.
maxRecords — Specifies the maximum number of records a record set can contain.
pageCount — Specifies the number of pages of data a record set contains.
pageSize — Specifies the number of records that make up one page of data.
recordCount — Specifies the number of records in the current record set.
state — Indicates whether a record set is open or closed.
status — Indicates the status of the current record.
stayInSync — Indicates whether a hierarchical record set should stay in sync with the data source.

Here are the methods of the record set objects inside DSOs:

addNew — You use this method to add a new record to the record set.
cancel — You use this method to cancel execution of a pending Execute or Open request.
cancelUpdate — You use this method to cancel an update operation.
clone — You use this method to create a copy of the record set.
close — You use this method to close a record set.
delete — You use this method to delete the current record (or group of records).
find — You use this method to search the record set. (Note that you use SQL to perform the search, which is not supported in Internet Explorer.)
getRows — You use this method to read records and store them in an array.
getString — You use this method to get the record set as a string.
move — You use this method to move the position of the current record.
moveFirst, moveLast, moveNext, and movePrevious — You use this method to navigate to various positions in the record set.
nextRecordSet — You use this method to clear the current record set object and return the next record set when working with hierarchical record sets.
open — You use this method to open a database.
requery — You use this method to re-execute the command that created a record set.
save — You use this method to save a record set in a file.
supports — You use this method to determine the features the record set supports.

In addition, DSOs support a number of events we can handle in scripting code. Here they are:

onDataAvailable — Occurs when data is downloaded.
onDatasetChanged — Occurs when the record set is changed.
onDatasetComplete — Occurs when the data is downloaded and ready to be used.
onReadyStateChange — Occurs when the ReadyState property changes.
onRowEnter — Occurs when a new record becomes the current one.
onRowExit — Occurs just before exiting the current record.
onRowsDelete — Occurs when a row is deleted.
onRowsInserted — Occurs when a row is inserted.
onCellChange — Occurs when the data in a bound control changes and the focus leaves that cell.

Now that we've explored how to do data binding in HTML, let's do this kind of data binding directly with XML.

< Back Page 238 of 288 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address