Home > Articles > Web Services > XML

  • Print
  • + Share This
Like this article? We recommend


The major complexities in your design process may largely be independent of XML, being associated with adding any sort of new functionality to an existing application. If your code is well-designed, modular, cohesive, and coherent, adding XML support may not be much of a problem. However, if you're dealing with a pile of spaghetti, you're going to have a tough time. In either situation, the specific changes you have to make are entirely dependent on the design of the application. Some design decisions are directly related to XML, however, and most are dependent on the constraints identified during the analysis phase.

The nature of the interface may seem like a big consideration, and it will be for the overall design of the application changes. However, the parts of the application that deal strictly with XML are largely independent of the specific interface. This is due to the fact that most conceivable interfaces—whether a SOAP messaging facility for a web service, a message queuing system for in-house application integration, or a batch import/export to the file system—deal with XML data as a serialized character stream. To consume that character stream, your application must parse the XML; and to produce a character stream, your application must take the XML instance document data (in whatever internal form it's stored) and serialize it to a character stream. Your task is to determine how you get that character stream from and to your chosen interface.

For design considerations involving validation, there are two main issues to consider:

  • All XML parsers have the ability to pass to your application a well-formed document, even if the document doesn't comply with its schema.

  • At least for now, schema validation is a Boolean proposition; there are no shades of gray between success and failure. A validation error might be as major as an unexpected element or an overall structure that doesn't bear any relation to the schema, or as minor as invalid content in an enumerated element or attribute. All popular parsing APIs stop and return a failure after encountering the first error, so you don't know what other errors might be lurking.

The point is that if you have a requirement to process documents that are not schema-valid, such as "in suspense" purchase orders, safe programming requires that you make very few assumptions about the content of these documents.

Document size and portability requirements can constrain your choice of XML parsing API. Simple API for XML (SAX) is still probably your best choice if your application must consume very large instance documents. If you don't have that requirement, the DOM is the most mature and flexible API, and Level 3 of the DOM finally offers standard approaches for loading and saving documents. Both SAX and the DOM are widely implemented, so portability shouldn't be too much of a concern. However, you'll save yourself a lot of trouble by finding a single parsing API, such as Xerces-C or Xerces-J, that runs or can be built on all of your target platforms.

If portability isn't a constraint, you may save yourself some coding effort by using one of the newer class-binding APIs such as Java Architecture for XML Binding (JAXB). These tools read schemas and create classes for languages such as C++, Java, and C#, allowing you process data in XML documents the same way as you do any other object in your program. However, as with the DOM, they may not be appropriate for processing very large instance documents, because they tend to load the complete document into memory. In addition, these tools are still relatively immature. Some still don't handle some schema constructs gracefully, such as dealing with a choice content model in a complex type.

Finally, you always have the choice of writing your own parser and serializer, rather than using someone else's. You may have reasonable requirements for doing this, but for most of us it would be like writing your own web browser instead of using Internet Explorer or Mozilla.

Beyond these considerations, there are a few other high-level design issues. Most APIs require some up-front housekeeping, such as creating a DocumentBuilder with Java API for XML Parsing (JAXP), or initializing the COM library if you're using MSXML. The API may also require you to release resources that you no longer need. You have to determine how localized within the application to make your XML support. If you do this housekeeping at a fairly high level—say, in application startup and shutdown—the associated resources can be available globally. You save the processing overhead of creating and releasing them on demand. Yet, you also have to manage them and make them accessible globally. For some situations, such as exporting a batch of invoices as XML documents, it may make more sense to make all of the XML associated code fairly localized.

Finally, be prepared to do some prototyping and throw away approaches that don't work, particularly if this is your first foray into XML. You probably won't hit any walls and need to backtrack until you get into implementation, so let's talk about that next.

  • + Share This
  • 🔖 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.


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