Provides the API for creating and building SOAP messages.
A container for
The content for a
A representation of an XML name.
A representation of a node (element) in an XML document.
An object that represents the contents of the SOAP body element in a SOAP message.
The definition of constants pertaining to the SOAP protocol.
An object representing an element of a SOAP message that is allowed but not specifically prescribed by a SOAP specification.
The container for the SOAPHeader and SOAPBody portions of a
An element in the
A representation of the contents in a
A representation of the SOAP header element.
An object representing the contents in the SOAP header part of the SOAP envelope.
A representation of a node whose value is text.
A single attachment to a
A factory for creating
An object that stores a MIME header name and its value.
A container for
The access point for the implementation classes of the factories defined in the SAAJ API.
Acts as a holder for the results of a JAXP transformation or a JAXB marshalling, in the form of a SAAJ tree.
A point-to-point connection that a client can use for sending messages directly to a remote party (represented by a URL, for instance).
A factory for creating
The root class for all SOAP messages.
The container for the SOAP-specific portion of a
An exception that signals that a SOAP exception has occurred.
Provides the API for creating and building SOAP messages. This package is defined in the SOAP with Attachments API for JavaTM (SAAJ) 1.3 specification.
The API in the
javax.xml.soap package allows you to do the following:
javax.xml.soappackage extend their counterparts in the
org.w3c.dompackage. This means that the
SOAPMessageis also a DOM Level 2
Document, and can be manipulated as such by applications, tools and libraries that use DOM (see http://www.w3.org/DOM/ for more information). It is important to note that, while it is possible to use DOM APIs to add ordinary DOM nodes to a SAAJ tree, the SAAJ APIs are still required to return SAAJ types when examining or manipulating the tree. In order to accomplish this the SAAJ APIs (specifically
SOAPElement.getChildElements()) are allowed to silently replace objects that are incorrectly typed relative to SAAJ requirements with equivalent objects of the required type. These replacements must never cause the logical structure of the tree to change, so from the perspective of the DOM APIs the tree will remain unchanged. However, the physical composition of the tree will have changed so that references to the nodes that were replaced will refer to nodes that are no longer a part of the tree. The SAAJ APIs are not allowed to make these replacements if they are not required so the replacement objects will never subsequently be silently replaced by future calls to the SAAJ API.
What this means in practical terms is that an application that starts to use SAAJ APIs on a tree after manipulating it using DOM APIs must assume that the tree has been translated into an all SAAJ tree and that any references to objects within the tree that were obtained using DOM APIs are no longer valid. Switching from SAAJ APIs to DOM APIs is not allowed to cause invalid references and neither is using SAAJ APIs exclusively. It is only switching from using DOM APIs on a particular SAAJ tree to using SAAJ APIs that causes the risk of invalid references.
© 1993–2017, Oracle and/or its affiliates. All rights reserved.
Documentation extracted from Debian's OpenJDK Development Kit package.
Licensed under the GNU General Public License, version 2, with the Classpath Exception.
Various third party code in OpenJDK is licensed under different licenses (see Debian package).
Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.