Home > Articles > Programming > Java

This chapter is from the book

This chapter is from the book

Messaging Framework

Now that you have a basic understanding of SOAP, it's time to zoom in and fill in the blanks. The last section provided an overview of SOAP; this section gives you more technical details that the basic introduction left out.

Version Compatibility

SOAP uses the namespace for version control. If the SOAP envelope is in the http://schemas.xmlsoap.org/soap/envelope/ namespace, then the request is SOAP 1.1. If the SOAP envelope is in the http://www.w3.org/2001/09/soap-envelope namespace, then the request is draft SOAP 1.2.

CAUTION

The URI for SOAP 1.2 is likely to change between the draft and the release of the actual recommendation. If anything, the URI should drop the month indicator and be of the following form (assuming the recommendation is published in 2002):

http://www.w3.org/2002/soap-envelope

CAUTION

Check the W3C Web site for the most recent URI.

If a SOAP 1.2 node receives a SOAP 1.1 request, it can either process it as SOAP 1.1 or reject it with a VersionMismatch fault message. In any case, a VersionMismatch fault message is always returned with the SOAP 1.1 URI so that older clients can decode the response.

SOAP 1.2 defines an optional Upgrade element, in the http://www.w3.org/2001/09/soap-upgrade namespace, that lets the server specify which versions it recognizes. If present, Upgrade must appear in the header, not the body. See Listing 9 for an example.

Listing 9—VersionMismatch fault with the Upgrade element.

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
  <env:Header>
    <upg:Upgrade
      xmlns:upg="http://www.w3.org/2001/09/soap-upgrade">
      <envelope qname="ns1:Envelope"
        xmlns:ns1="http://www.w3.org/2001/09/soap-envelope"/>
    </upg:Upgrade>
  </env:Header>
  <env:Body>
    <env:Fault>
      <faultcode>env:VersionMismatch</faultcode>
      <faultstring>Requires SOAP 1.2</faultstring>
    </env:Fault>
  </env:Body>
</env:Envelope>

Header

Recall from the earlier discussion that the header is the place to put auxiliary information. Typically it provides storage for options on how to process the call.

The header is similar to email headers: It is not the message itself, but it provides information that may be useful (or even essential) in decoding the payload. For example, ebXML uses the header to store routing information in an ebXML-defined MessageHeader. (This is the smallest ebXML message possible. Indeed, ebXML defines many other elements, but their use is optional.)

Listing 10 is an example of an ebXML header. Because ebXML is outside the scope of this article, we encourage you to turn to http://www.ebxml.org if you want specific information on these elements. However, you are sure to recognize routing information (From, To, Service, Action), as well as message identifiers (MessageData). The CPAId element points to the Collaboration Protocol Agreement that details how the partners ("partner" is ebXML jargon for the parties in the transaction) work together.

Listing 10—An ebXML Header

<env:Header xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
      xmlns:eb="http://www.ebxml.org/namespaces/messageHeader">
  <eb:MessageHeader env:mustUnderstand="1" eb:version="1.0">
    <eb:From><eb:PartyId>urn:duns:374950798</eb:PartyId></eb:From>
    <eb:To><eb:PartyId>urn:duns:912345678</eb:PartyId></eb:To>
    <eb:CPAId>http://www.psol.com/cpas/default.xml</eb:CPAId>
    <eb:ConversationId>20011115-122303-28572</eb:ConversationId>
    <eb:Service>urn:services:SupplierOrderProcessing</eb:Service>
    <eb:Action>NewOrder</eb:Action>
    <eb:MessageData>
      <eb:MessageId>20011115-122303-28572@psol.com</eb:MessageId>
      <eb:Timestamp>2001-11-15T11:12:12Z</eb:Timestamp>
    </eb:MessageData>
  </eb:MessageHeader>
</env:Header>

SOAP defines two attributes specifically for the header: env:mustUnderstand and env:actor. A client attaches the env:mustUnderstand attribute (with a value of 1 for true) to elements that are essential for processing the call.

A node should not attempt to process a request if it does not recognize one or more elements flagged with env:mustUnderstand. In Listing 10, the MessageHeader is flagged with env:mustUnderstand because servers should not attempt to process ebXML requests unless they support the MessageHeader.

The other attribute is env:actor. It signals that the element is intended for a given node. Remember Figure 3, which shows that the proxy does not pass the header to the ultimate node. The proxy uses the env:actor to decide which header elements, if any, are for its own consumption.

The env:actor attribute contains the URI of the node or the special URI http://schemas.xmlsoap.org/soap/actor/next for SOAP 1.1. For SOAP 1.2 it contains http://www.w3.org/2001/09/soap-envelope/actor/next, which stands for the next node.

SOAP Fault

In most cases, SOAP lets the application define the content of the body. The one exception is when there's an error for which SOAP defines the env:Fault. The SOAP fault provides minimal common ground between different SOAP implementations in case of a protocol error.

The content of env:Fault is detailed in the following list. Note that the Fault element is prefixed with a namespace but its content is not (in an XML schema the content would be written as local elements):

  • faultcode is a code that indicates the error. This element is required.

  • faultstring is an human-readable error message. It is required.

  • faultactor is the URI of the node that reports the error. It is required only if the node reporting the error is not the ultimate node.

  • detail contains additional, application-specific information on the error. It is required if the error took place in the body; it is forbidden otherwise.

SOAP defines the following error codes for the faultcode field:

  • VersionMismatch indicates the node does not recognize the version of SOAP used; see Listing 9 for an example.

  • MustUnderstand indicates the node does not recognize a block flagged with mustUnderstand.

  • Client indicates the node cannot process the message because of the client's fault, for example, when the message is not formatted correctly.

  • Server indicates the error is not due to the message itself but rather the state in which the server was.

  • DataEncodingUnknown indicates the node does not recognize the encodingStyle. This is defined only in SOAP 1.2.

The codes should be placed in the envelope namespace. It is possible to extend the code to provide a more detailed error message if you use the dot (.) as a separator. For example, a error code for Java exceptions could be defined as Server.Exception. The server would return this error:

<env:Envelope xmlns:env="http://www.w3.org/2001/09/soap-envelope">
  <env:Body>
    <env:Fault>
      <faultcode>env:Server.Exception</faultcode>
      <faultstring>Null pointer exception</faultstring>
      <detail>        <stackTrace>
         java.lang.NullPointerException:           
         at com.psol.jws.TroubleMaker(TroubleMaker.java:148)           
         at java.lang.Thread.run(Thread.java:484)        
         </stackTrace>      
         </detail>    
         </env:Fault>
  </env:Body>
</env:Envelope>

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.

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