/* * Copyright (c) 2005, 2017, Oracle and/or its affiliates. All rights reserved. * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. * * This code is free software; you can redistribute it and/or modify it * under the terms of the GNU General Public License version 2 only, as * published by the Free Software Foundation. Oracle designates this * particular file as subject to the "Classpath" exception as provided * by Oracle in the LICENSE file that accompanied this code. * * This code is distributed in the hope that it will be useful, but WITHOUT * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License * version 2 for more details (a copy is included in the LICENSE file that * accompanied this code). * * You should have received a copy of the GNU General Public License version * 2 along with this work; if not, write to the Free Software Foundation, * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. * * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA * or visit www.oracle.com if you need additional information or have any * questions. */ /** * Provides the API for creating and building SOAP messages. This package * is defined in the SOAP with Attachments API for JavaTM * (SAAJ) 1.4 specification. * *
The API in the javax.xml.soap
package allows you to do the following:
*
*
* In addition the APIs in the javax.xml.soap
package extend
* their counterparts in the org.w3c.dom
package. This means that
* the SOAPPart
of a SOAPMessage
is 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 {@link javax.xml.soap.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. * *
* There are several factories defined in the SAAJ API to discover and load specific implementation: * *