Home > Articles > Programming > Java

This chapter is from the book

8.2 Mapping to Almost Isomorphic Tree Structures

The most typical mapping occurs when the structure of XML documents reflects the application data structure and thus the mapping is almost isomorphic.1 We use the hypothetical purchase order document, po.xml, in Listing 8.1 as our example.

Listing 8.1 Purchase order document, chap08/isomorphic/po.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE purchaseOrder SYSTEM "PurchaseOrder.dtd">
    <name>Robert Smith</name>
    <address>8 Oak Avenue, New York, US</address>
  <comment>Hurry, my lawn is going wild!</comment>
    <item partNum="872-AA">
    <item partNum="926-AA">
      <productName>Baby Monitor</productName>

Our application reads in this purchase order document, calculates the price, and generates an invoice. One natural modeling of this program is to represent each of the concepts, such as purchase order, customer, and item, as a Java object. Hence, the three classes shown in Listings 8.2, 8.3, and 8.4 are to be prepared.

Listing 8.2 PurchaseOrderclass, chap08/isomorphic/PurchaseOrder.java

public class PurchaseOrder {

  Customer customer;
  String comment;
  Vector items = new Vector();

Listing 8.3 Customerclass, chap08/isomorphic/Customer.java

public class Customer { 

  String name;
  int customerId;
  String address; 

Listing 8.4 Itemclass, chap08/isomorphic/Item.java

public class Item { 

  String partNum;
  String productName;
  int quantity;
  float usPrice;
  String shipDate; 

How can we map an input XML document into instances of these classes? For simplicity, let us assume that we have already parsed an XML document and have a DOM tree. What we need to do is recursively scan this DOM tree, and for each element that represents a concept to be represented as a Java object, generate an instance of the corresponding class. For example, upon encountering a <purchaseOrder>element during the DOM tree scan, create a new instance of the PurchaseOrderclass, as shown in Figure 8.2.

To do this, we provide a static method called unmarshal()in the class

Figure 8.2Figure 8.2 Creating a Java object from a DOM element

PurchaseOrder(see Listing 8.5). This method takes a DOM node representing a <purchaseOrder>element as an input parameter and returns a new PurchaseOrder instance.

Listing 8.5 unmarshal()method for PurchaseOrderclass, chap08/isomorphic/ PurchaseOrder.java(continued)

    static PurchaseOrder unmarshal(Element e) {
      PurchaseOrder po = new PurchaseOrder();
      for (Node c1=e.getFirstChild(); c1!=null; c1=c1.getNextSibling()) {
         if (c1.getNodeType()==Node.ELEMENT_NODE) {

[48]        if (c1.getNodeName().equals("customer")) {
[49]          // <customer> subelement
[50]          po.setCustomer(Customer.unmarshal((Element)c1));

[52]        } else if (c1.getNodeName().equals("comment")) {
[53]          // <comment> subelement
[54]          po.setComment(TypeConversion.toString(c1));

[56]        } else if (c1.getNodeName().equals("items")) {
[57]          // <items> subelement
[58]          for (Node c2 = c1.getFirstChild();
[59]            c2 != null;
[60]            c2 = c2.getNextSibling()) {
[61]            if (c2.getNodeType()==Node.ELEMENT_NODE) {
[62]              Element childElement2 = (Element)c2;
[63]              if (c2.getNodeName().equals("item")) {
[64]                po.addItem(Item.unmarshal((Element) c2));
[65]              }
[66]            }
[67]          }
[68]        }
    return po;

Parameter eof this method points to a <purchaseOrder>element in a DOM tree. This method first creates an instance of the PurchaseOrderclass and then scans the child nodes of the element eto fill in the fields of the PurchaseOrder instance. For example, when the method encounters a <customer>element, it creates a Customerobject by calling the static method unmarshal()of the class Customerand sets the created object to the customerfield of the PurchaseOrderobject (lines 48–50).

When seeing a <comment>element, the method converts the contents of the element into a Stringobject and assigns it to the commentfield (lines 52–54).

Child nodes of an <items>element are a repetition of <item>elements, so the method goes further down to its subelements and for each <item>element, the method creates an instance of the Itemclass and adds it to the itemfield of the PurchaseOrder(lines 56–68). As a helper class for handling a type conversion from a DOM node to a Java primitive type, we write a simple class called TypeConversion, shown in Listing 8.6.

Listing 8.6 TypeConversionclass, chap08/isomorphic/TypeConversion.java package chap08.isomorphic; import org.w3c.dom.Node; public class TypeConversion {

package chap08.isomorphic;

 import org.w3c.dom.Node;

 public class TypeConversion {

   static String toString(Node n) {

     String content = n.getFirstChild().getNodeValue();
     return content;

   static int toInteger(Node n) {
     String content = n.getFirstChild().getNodeValue();
     return Integer.parseInt(content);

   static float toFloat(Node n) {
     String content = n.getFirstChild().getNodeValue();
     return Float.parseFloat(content);

What about unmarshaling of the Customerclass? As we did for our PurchaseOrder class, we write a static method called unmarshal()that is to be called whenever a <customer>element is found. The implementation of this method is shown in Listing 8.7. You may notice that it has exactly the same pattern as the unmarshal() method of our PurchaseOrderclass.

Listing 8.7 unmarshal()method for Customerclass, chap08/isomorphic/ Customer.java(continued)

static Customer unmarshal(Element e) {
  Customer co = new Customer();
  for (Node c1=e.getFirstChild(); c1!=null; c1=c1.getNextSibling()) {
     if (c1.getNodeType()==Node.ELEMENT_NODE) {

      if (c1.getNodeName().equals("name")) {
        // <name> subelement

      } else if (c1.getNodeName().equals("customerId")) {
        // <customreId> subelement

      } else if (c1.getNodeName().equals("address")) {
        // <address> subelement
  return co;

Similarly, we can build the unmarshal()method for the class Item. In this code, shown in Listing 8.8, we also extract the value of the attribute partNum (line 57).

Listing 8.8 unmarshal()method for Itemclass, chap08/isomorphic/Item.java


    static Item unmarshal(Element e) {
     Item item = new Item();
[57]  item.setPartNum(e.getAttribute("partNum"));
      for (Node c1=e.getFirstChild(); c1!=null; c1=c1.getNextSibling()) {
        if (c1.getNodeType()==Node.ELEMENT_NODE) {

          if (c1.getNodeName().equals("productName")) {
            // <productName> subelement

          } else if (c1.getNodeName().equals("quantity")) {
            // <quantity> subelement

          } else if (c1.getNodeName().equals("USPrice")) {
            // <USPrice> subelement

          } else if (c1.getNodeName().equals("shipDate")) {
            // <shipDate> subelement
      return item;

Now we are ready to convert a whole DOM tree into our application data model. We need to parse an input XML document and give the resulting DOM tree to one of the unmarshal()methods that we programmed. The main()method, shown in Listing 8.9, does exactly that.

Listing 8.9 main()method for PurchaseOrderclass, chap08/isomorphic/ PurchaseOrder.java(continued)

    public static void main(String[] argv) throws Exception {
       if (argv.length < 1) {
         System.err.println("Usage: java chap08.PurchaseOrder file");
[79]    DocumentBuilderFactory factory =
[80]        DocumentBuilderFactory.newInstance();
[81]    DocumentBuilder builder = factory.newDocumentBuilder();
[82]    builder.setErrorHandler(new MyErrorHandler());
[83]    Document doc = builder.parse(argv[0]);

        Element root = doc.getDocumentElement();
        if (root.getNodeName().equals("purchaseOrder")) {
[87]        PurchaseOrder po = unmarshal(root);
           Customer co = po.getCustomer();
           System.out.println("************ Invoice ************** ");
           System.out.println("Date:"+ new java.util.Date());
           System.out.println("To: "+co.getName());
           System.out.println(" "+co.getAddress());
           System.out.println(" Customer#:"+co.getCustomerId());
           int i=0;
           float total = (float)0.0;
           for (Iterator itr=po.getItems(); itr.hasNext(); i++) {
              Item item = (Item)itr.next();
              System.out.println("Item #"+i+" : "+item.getPartNum()+
                             ", Quantity="+item.getQuantity()+
                             ", UnitPrice="+item.getUSPrice()+
                             ", ShipDate="+item.getShipDate());

              total += item.getUSPrice();
           System.out.println("total = $"+total);

Lines 79–83 parse the input and obtain a DOM tree. After checking that the root element is in fact a purchaseOrderelement, we create a PurchaseOrder instance by calling the static method unmarshal()in line 87. The rest of the code is pure application logic that is responsible for generating an invoice.

What can we learn from this manual mapping? We have seen that if the mapping preserves the structural similarity between the XML document and the Java data structure, writing unmarshaling codes can be a fairly automatic task. You prepare one class for one complex element type (for example, <purchaseOrder>, <customer>, or <item>) that has a static method, unmarshal(), for scanning a DOM tree and creating a corresponding Java instance.

The question is, then, is it possible to automatically generate such mapping codes from a schema of input XML documents? The answer is yes. In Chapter 15, we describe a few of these tools.

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.


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.


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.


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.


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


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


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.


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.


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