-
Interface Summary Interface Description Detail A container forDetailEntryobjects.DetailEntry The content for aDetailobject, giving details for aSOAPFaultobject.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 ASOAPBodyElementobject represents the contents in aSOAPBodyobject.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 aSOAPPartobject.SOAPFault An element in theSOAPBodyobject that contains error and/or status information.SOAPFaultElement A representation of the contents in aSOAPFaultobject.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 aSOAPMessageobject.MessageFactory A factory for creatingSOAPMessageobjects.MimeHeader An object that stores a MIME header name and its value.MimeHeaders A container forMimeHeaderobjects, 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 creatingSOAPConnectionobjects.SOAPElementFactory Deprecated - Usejavax.xml.soap.SOAPFactoryfor creating SOAPElements.SOAPFactory SOAPFactoryis 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 aSOAPMessageobject. -
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.
Nederlandse vertaling
U hebt gevraagd om deze site in het Nederlands te bezoeken. Voor nu wordt alleen de interface vertaald, maar nog niet alle inhoud.Als je me wilt helpen met vertalingen, is je bijdrage welkom. Het enige dat u hoeft te doen, is u op de site registreren en mij een bericht sturen waarin u wordt gevraagd om u toe te voegen aan de groep vertalers, zodat u de gewenste pagina's kunt vertalen. Een link onderaan elke vertaalde pagina geeft aan dat u de vertaler bent en heeft een link naar uw profiel.
Bij voorbaat dank.
Document heeft de 11/06/2005 gemaakt, de laatste keer de 04/03/2020 gewijzigd
Bron van het afgedrukte document:https://www.gaudry.be/nl/java-api-rf-javax/xml/soap/package-summary.html
De infobrol is een persoonlijke site waarvan de inhoud uitsluitend mijn verantwoordelijkheid is. De tekst is beschikbaar onder CreativeCommons-licentie (BY-NC-SA). Meer info op de gebruiksvoorwaarden en de auteur.
Referenties
Deze verwijzingen en links verwijzen naar documenten die geraadpleegd zijn tijdens het schrijven van deze pagina, of die aanvullende informatie kunnen geven, maar de auteurs van deze bronnen kunnen niet verantwoordelijk worden gehouden voor de inhoud van deze pagina.
De auteur Deze site is als enige verantwoordelijk voor de manier waarop de verschillende concepten, en de vrijheden die met de referentiewerken worden genomen, hier worden gepresenteerd. Vergeet niet dat u meerdere broninformatie moet doorgeven om het risico op fouten te verkleinen.
