XML Reference Guide

Mar 14, 2003

␡

⎙ Print

< Back Page 24 of 278 Next >

With XML so fundamental in Microsoft's .NET framework, it should come as no surprise that the ability to manipulate an XML document is built right into the system. In fact, although DOM Level 2.0 doesn't include a standard way to create or save a document, .NET makes it easy. In this section, we'll get a feel for how these manipulations work by using C++ .NET to load a simple document, make some changes to it, and then save it back out to a file. (We'll be running directly from the command line, so if you're not familiar with GUI programming, don't worry.)

Consider, for example, the following sample file, candy.xml:

<?xml version="1.0"?>
<candy>
  <product>Mints</product>
  <product>Chocolate</product>

  <product>Circus Peanuts</product>
</candy>

Using .NET, you can create a Document out of it by either feeding the XML directly to the parser, as in:

#using <mscorlib.dll>

#using <System.dll>
#using <System.Xml.dll>

using namespace System;
using namespace System::IO;
using namespace System::Xml;

int main(void){

    XmlDocument * doc = new XmlDocument();
    doc->LoadXml("<candy><product>Mints</product><product>Chocolate</product><product>Circus Peanuts</product></candy>");

   
    System::Console::Write("Done.");
    return 0;
}

or reading a file from a URL, as in:

...
int main(void){

    XmlDocument * doc = new XmlDocument();
    doc->Load("http://www.example.com/candy.xml");
   
    System::Console::Write("Done.");
    return 0;
}

Once you create the Document (or in this case, the XmlDocument), you can manipulate it using the .NET binding of the DOM interface, as in:

...
int main(void){

    XmlDocument * doc = new XmlDocument();
    doc->Load("http://www.example.com/candy.xml");
   
    XmlElement * root = doc->DocumentElement;
    System::Console::Write("The root element is ");
    Console::WriteLine(root->Name);

    XmlNodeList * children = root->ChildNodes;
    Console::Write("There are ");
    Console::Write(children->Count);
    Console::WriteLine (" child elements.");
    Console::WriteLine("They are: ");

    if (root->HasChildNodes){

        System::Collections::IEnumerator* theChildren = root->ChildNodes->GetEnumerator();
        while (theChildren->MoveNext()) 
        {
            XmlNode * thisChild = __try_cast<XmlNode*>(theChildren->Current);

             if (thisChild->NodeType == XmlNodeType::Element){
                  XmlNode * theText;
                  theText = thisChild->FirstChild;
                  Console::Write(thisChild->Name);
                  Console::Write(": ");
                  Console::WriteLine(theText->Value);
             }
         }
    }

    System::Console::Write("Done.");
    return 0;
}

First we're getting a reference to the root of the actual Document by asking for the DocumentElement. We can then access the Name property of that element.

Next, we get an XmlNodeList of all of the child nodes of the root element. That list has a Count property we can use to determine how many children their are. You could, for example, then use this number to iterate through each node directly, but instead let's look at doing it implicitly by calling the objects themselves.

If the root node has children, we can iterate through them by setting thisChild to point to each one in turn using an Enumerator. If a node is an element, we can assume (in this case) that it has a text child, which we can then access using the FirstChild member. From there, we can simply print out the values.

We can also use the DOM interface to add information to the Document, as in:

...
                  Console::WriteLine(theText->Value);
             }
         }
     }
 

     XmlNodeList * products = root->GetElementsByTagName("product");
     XmlNode * productNode;

     int productNum;
     for (productNum = 0; productNum < products->Count; productNum++) {
        productNode = products->Item(productNum);
        XmlAttribute * attr = doc->CreateAttribute("productNumber");
        attr->Value = System::Convert::ToString(productNum);

        XmlElement * productElement = __try_cast<XmlElement*>(productNode);
        productElement->SetAttributeNode(attr);

        String * productName = productElement->FirstChild->Value;
        productElement->FirstChild->Value = productName->ToUpper(new System::Globalization::CultureInfo(S"en-US", false));

        XmlElement * updateElement = doc->CreateElement("updated");
        DateTime rightNow = DateTime::Now;
        String * dateOutputsArray[] = rightNow.GetDateTimeFormats();
        
        XmlNode * updateText = doc->CreateTextNode(dateOutputsArray[63]);

        updateElement->AppendChild(updateText);
        productElement->AppendChild(updateElement);

        Console::WriteLine(productNum);
    }

   System::Console::Write("Done.");
   return 0;
}

What we want to do is add an attribute and an element to each product element, so first we can get all of the product elements using GetElementsByTagName(). Next, we can loop through each of them using the Count value, as I mentioned earlier.

For each node, we can create an attribute (using CreateAttribute()) and then assign it a value. From there, you can cast the Node to an Element and assign the Attribute to it. You can also assign the value directly, using:

productElement->SetAttribute("productNumber", "", productNum);

Next, we're altering the product name directly by assigning the Text node child of the element a new value.

Finally, we'll make a new Element by asking the Document object to create it -- that's it's job, according to the DOM specification. We can then create a Text node and append it to the new element, and then append the new element to the product.

Because persisting, or saving, an XML document wasn't part of the DOM specification, every implementation handles it differently, if it handles it at all. For example, in most Java implementations, the easiest way to save an XML Document to a file is to perform an XSL identity tranformation. Fortunately, .NET doesn't make you go through such convolutions, enabling you to simply save() the Document:

...
        Console::WriteLine(productNum);
    }

    doc->Save("candyout.xml");

    System::Console::Write("Done.");
    return 0;
}

In this case, the end result is a file that shows the appropriate changes, as in:

<candy>
  <product productNumber="0">MINTS
       <updated>2005-02-21 5:52 PM</updated>
  </product>
  <product productNumber="1">CHOCOLATE
       <updated>2005-02-21 5:52 PM</updated>
  </product>
  <product productNumber="2">CIRCUS PEANUTS
       <updated>2005-02-21 5:52 PM</updated>
  </product>
</candy>

Note that I've added some text nodes to make the changes easier to see, but the data is the same.

< Back Page 24 of 278 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