SOAP with Attachments API for Java interface
The SOAP with Attachments API for Java™ (SAAJ) interface is used for SOAP messaging that provides a standard way to send XML documents over the Internet from a Java model. SAAJ is used to manipulate the SOAP message to the appropriate context as it traverses through the runtime environment.
Best practice: IBM WAS supports the JAX-WS model and the JAX-RPC model. JAX-WS is the next generation Web services model extending the foundation provided by the JAX-RPC model. Using the strategic JAX-WS model, development of Web services and clients is simplified through support of a standards-based annotations model. Although the JAX-RPC model and applications are still supported, take advantage of the easy-to-implement JAX-WS model to develop new Web services applications and clients. bprac
The Java API for XML-Based RPC (JAX-RPC) model supports SAAJ 1.2 to manipulate the XML.
The JAX-WS model supports SAAJ 1.2 and 1.3. SAAJ 1.3 includes support for SOAP 1.2 messages.
The differences in the SAAJ 1.2 and SAAJ 1.3 spec can be reviewed in the topic "Differences in SAAJ versions."
How are messages used in Web services?
Web services use XML technology to exchange messages. These messages conform to XML schema. When developing Web services applications, there are limited XML APIs to work with, for example, Document Object Model (DOM). It is more efficient to manipulate the Java objects and have the serialization and deserialization completed during run time.
Web services uses SOAP messages to represent remote procedure calls between the client and the server. Typically, the SOAP message is deserialized into a series of Java value-type business objects that represent the parameters and return values. In addition, the Java model provides APIs that support applications and handlers to manipulate the SOAP message directly. Because there are a limited number of XML schema types that are supported by the models, the spec provides the SAAJ data model as an extension to manipulate the message.
To manipulate the XML schema types, we need to map the XML schema types to Java types with a custom data binder.
The SAAJ interface
The SAAJ-related classes are located in the javax.xml.soap package. SAAJ builds on the interfaces and abstract classes and many of the classes begin by invoking factory methods to create a factory such as SOAPConnectionFactory and SOAPFactory.
The most commonly used classes are:
- SOAPMessage: Contains the message, both the XML and non-XML parts
- SOAPHeader: Represents the SOAP header XML element
- SOAPBody: Represents the SOAP body XML element
- SOAPElement: Represents the other elements in the SOAP message
Other parts of the SAAJ interface include:
- MessageContext: Contains a SOAP message and related properties
- AttachmentPart: Represents a binary attachment
- SOAPPart: Represents the XML part of the message
- SOAPEnvelope: Represents the SOAP envelope XML element
- SOAPFault: Represents the SOAP fault XML element
The primary interface in the SAAJ model is javax.xml.soap.SOAPElement, also referred to as SOAPElement. Using this model, applications can process an SAAJ model that uses pre-existing DOM code. It is also easier to convert pre-existing DOM objects to SAAJ objects.
Messages created using the SAAJ interface follow SOAP standards. A SOAP message is represented in the SAAJ model as a javax.xml.soap.SOAPMessage object. The XML content of the message is represented by a javax.xml.soap.SOAPPart object. Each SOAP part has a SOAP envelope. This envelope is represented by the SAAJ javax.xml.SOAPEnvelope object. The SOAP spec defines various elements residing in the SOAP envelope; SAAJ defines objects for the various elements in the SOAP envelope.
The SOAP message can also contain non-XML data that is called attachments. These attachments are represented by SAAJ AttachmentPart objects that are accessible from the SOAPMessage object.
A number of reasons exist as to why handlers and applications use the generic SOAPElement API instead of a tightly bound mapping:
- The Web service might be a conduit to another Web service. In this case, the SOAP message is only forwarded.
- The Web service might manipulate the message using a different data model, for example a Service Data Object (SDO). It is easier to convert the message from a SAAJ DOM to a different data model.
- A handler, for example, a digital signature validation handler, might want to manipulate the message generically.
We might need to go a step further to map the XML schema types, because the SOAPElement interface is not always the best alternative for legacy systems. In this case we might want to use a generic model, such as SDO, which is more appropriate for data-centric applications.
The XML schema can be configured to include a custom data binding that pairs the SDO or data object with the Java object. For example, the run time renders an incoming SOAP message into a SOAPElement interface and passes it to the customer data binder for more processing. If the incoming message contains an SDO, the run time recognizes the data object code, queries its type mapping to locate a custom binder, and builds the SOAPElement interface that represents the SDO code. The SOAPElement is passed to the SDOCustomBinder.
See Custom data binders for more information about the process of developing applications with SOAPElement, SDO and custom binders.
For a complete list of the supported standards and specifications, see the Web services specifications and API documentation.
Related concepts
SOAP
Differences in SOAP versions
Differences in SAAJ versions
Related
Web services specifications and APIs