-
Interface Summary Interface Description Detail A container forDetailEntry
objects.DetailEntry The content for aDetail
object, giving details for aSOAPFault
object.Name A representation of an XML name.Node A representation of a node (element) in an XML document.SOAPBody An object that represents the contents of the SOAP body element in a SOAP message.SOAPBodyElement ASOAPBodyElement
object represents the contents in aSOAPBody
object.SOAPConstants The definition of constants pertaining to the SOAP protocol.SOAPElement An object representing an element of a SOAP message that is allowed but not specifically prescribed by a SOAP specification.SOAPEnvelope The container for the SOAPHeader and SOAPBody portions of aSOAPPart
object.SOAPFault An element in theSOAPBody
object that contains error and/or status information.SOAPFaultElement A representation of the contents in aSOAPFault
object.SOAPHeader A representation of the SOAP header element.SOAPHeaderElement An object representing the contents in the SOAP header part of the SOAP envelope.Text A representation of a node whose value is text. -
Class Summary Class Description AttachmentPart A single attachment to aSOAPMessage
object.MessageFactory A factory for creatingSOAPMessage
objects.MimeHeader An object that stores a MIME header name and its value.MimeHeaders A container forMimeHeader
objects, which represent the MIME headers present in a MIME part of a message.SAAJMetaFactory The access point for the implementation classes of the factories defined in the SAAJ API.SAAJResult Acts as a holder for the results of a JAXP transformation or a JAXB marshalling, in the form of a SAAJ tree.SOAPConnection A point-to-point connection that a client can use for sending messages directly to a remote party (represented by a URL, for instance).SOAPConnectionFactory A factory for creatingSOAPConnection
objects.SOAPElementFactory Deprecated - Usejavax.xml.soap.SOAPFactory
for creating SOAPElements.SOAPFactory SOAPFactory
is a factory for creating various objects that exist in the SOAP XML tree.SOAPMessage The root class for all SOAP messages.SOAPPart The container for the SOAP-specific portion of aSOAPMessage
object. -
Exception Summary Exception Description SOAPException An exception that signals that a SOAP exception has occurred.
Package javax.xml.soap Description
The API in the javax.xml.soap
package allows you to do the
following:
- create a point-to-point connection to a specified endpoint
- create a SOAP message
- create an XML fragment
- add content to the header of a SOAP message
- add content to the body of a SOAP message
- create attachment parts and add content to them
- access/add/modify parts of a SOAP message
- create/add/modify SOAP fault information
- extract content from a SOAP message
- send a SOAP request-response message
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 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.
Traduction non disponible
Les API Java ne sont pas encore traduites en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.
Version en cache
03/12/2024 18:36:20 Cette version de la page est en cache (à la date du 03/12/2024 18:36:20) afin d'accélérer le traitement. Vous pouvez activer le mode utilisateur dans le menu en haut pour afficher la dernère version de la page.Document créé le 11/06/2005, dernière modification le 04/03/2020
Source du document imprimé : https://www.gaudry.be/java-api-rf-javax/xml/soap/package-summary.html
L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.
Références
Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.