|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||
| Packages that use org.openliberty.xmltooling.soapbinding | |
|---|---|
| org.openliberty.wsc | This package contains all of the Service Client classes and the basic WSFMessage. |
| org.openliberty.xmltooling.disco | |
| org.openliberty.xmltooling.epr | |
| org.openliberty.xmltooling.soap.soap11 | |
| org.openliberty.xmltooling.soapbinding | |
| Classes in org.openliberty.xmltooling.soapbinding used by org.openliberty.wsc | |
|---|---|
| ProcessingContext
This header block may be employed by a sender to signal to a receiver that the latter should add a specific additional facet to the overall processing context in which any action(s) are invoked as a result of processing any ID-* message also conveyed in the overall SOAP-bound ID-* message. |
|
| RedirectRequest
<xs:element name="RedirectRequest" type="RedirectRequestType"/> <xs:complexType name="RedirectRequestType"> <xs:attribute name="redirectURL" type="xs:anyURI" use="required"/> </xs:complexType> |
|
| Classes in org.openliberty.xmltooling.soapbinding used by org.openliberty.xmltooling.disco | |
|---|---|
| Action
The <wsa:Action> header block is defined in [WSAv1.0-SOAP]. |
|
| Classes in org.openliberty.xmltooling.soapbinding used by org.openliberty.xmltooling.epr | |
|---|---|
| Action
The <wsa:Action> header block is defined in [WSAv1.0-SOAP]. |
|
| Classes in org.openliberty.xmltooling.soapbinding used by org.openliberty.xmltooling.soap.soap11 | |
|---|---|
| Action
The <wsa:Action> header block is defined in [WSAv1.0-SOAP]. |
|
| ApplicationEPR
This header may be included in a message zero or more times and provides a means for a sender to specify application endpoints that may be referenced from the SOAP Body of the message. |
|
| Consent
This header block is used to explicitly claim that the Principal consented to the present interaction. |
|
| CredentialsContext
It may be necessary for an entity receiving an ID-* message to indicate the type of credentials that should be used by the sender in submitting a message. |
|
| EndpointUpdate
It may be necessary for an entity receiving an ID-* message to indicate that messages from the sender should be directed to a different endpoint, or that they wish a different credential to be used than was originally specified by the entity for access to the requested resource. |
|
| FaultTo
The |
|
| MessageID
Values of the <wsa:MessageID> header block MUST satisfy the following property: Any party that assigns a value to a |
|
| ProcessingContext
This header block may be employed by a sender to signal to a receiver that the latter should add a specific additional facet to the overall processing context in which any action(s) are invoked as a result of processing any ID-* message also conveyed in the overall SOAP-bound ID-* message. |
|
| RelatesTo
The <wsa:RelatesTo> header block is defined in [WSAv1.0-SOAP]. |
|
| ReplyTo
The <wsa:ReplyTo> header block is defined in [WSAv1.0-SOAP]. |
|
| Sender
When included in a message, this header provides a means for a sender to claim that it is a provider identified by a given providerID value. |
|
| TargetIdentity
When included in a message, this header provides a means for the sender to include an identity token (see [LibertySecMech]) that specifies an identity at the service that is the target of the message. |
|
| Timeout
A requesting entity may wish to indicate that they would like a request to be processed within some specified amount of time. |
|
| To
In the typical case that a WS-Addressing endpoint reference is used to address a message, the value of this header block is taken from the <wsa:Address> of the EndpointReference. |
|
| UsageDirective
Participants in the ID-WSF framework may need to indicate the privacy policy associated with a message. |
|
| UserInteraction
A WSC that interacts with a user (typically through a web-site offered by the WSC) may need to indicate its readiness to redirect the user agent of the user, or its readiness to pose questions to the user on behalf of other parties (such as WSPs). |
|
| Classes in org.openliberty.xmltooling.soapbinding used by org.openliberty.xmltooling.soapbinding | |
|---|---|
| Action
The <wsa:Action> header block is defined in [WSAv1.0-SOAP]. |
|
| ApplicationEPR
This header may be included in a message zero or more times and provides a means for a sender to specify application endpoints that may be referenced from the SOAP Body of the message. |
|
| Consent
This header block is used to explicitly claim that the Principal consented to the present interaction. |
|
| CredentialsContext
It may be necessary for an entity receiving an ID-* message to indicate the type of credentials that should be used by the sender in submitting a message. |
|
| EndpointUpdate
It may be necessary for an entity receiving an ID-* message to indicate that messages from the sender should be directed to a different endpoint, or that they wish a different credential to be used than was originally specified by the entity for access to the requested resource. |
|
| EndpointUpdate.UpdateType
|
|
| FaultTo
The |
|
| InteractionService
|
|
| MessageID
Values of the <wsa:MessageID> header block MUST satisfy the following property: Any party that assigns a value to a |
|
| ProcessingContext
This header block may be employed by a sender to signal to a receiver that the latter should add a specific additional facet to the overall processing context in which any action(s) are invoked as a result of processing any ID-* message also conveyed in the overall SOAP-bound ID-* message. |
|
| ProcessingContext.Defined
New processing context facet identifiers MAY be defined in other specifications, for example in ID-SIS data service specifications. |
|
| RedirectRequest
<xs:element name="RedirectRequest" type="RedirectRequestType"/> <xs:complexType name="RedirectRequestType"> <xs:attribute name="redirectURL" type="xs:anyURI" use="required"/> </xs:complexType> |
|
| RelatesTo
The <wsa:RelatesTo> header block is defined in [WSAv1.0-SOAP]. |
|
| ReplyTo
The <wsa:ReplyTo> header block is defined in [WSAv1.0-SOAP]. |
|
| SecurityMechID
|
|
| Sender
When included in a message, this header provides a means for a sender to claim that it is a provider identified by a given providerID value. |
|
| TargetIdentity
When included in a message, this header provides a means for the sender to include an identity token (see [LibertySecMech]) that specifies an identity at the service that is the target of the message. |
|
| Timeout
A requesting entity may wish to indicate that they would like a request to be processed within some specified amount of time. |
|
| To
In the typical case that a WS-Addressing endpoint reference is used to address a message, the value of this header block is taken from the <wsa:Address> of the EndpointReference. |
|
| UsageDirective
Participants in the ID-WSF framework may need to indicate the privacy policy associated with a message. |
|
| UserInteraction
A WSC that interacts with a user (typically through a web-site offered by the WSC) may need to indicate its readiness to redirect the user agent of the user, or its readiness to pose questions to the user on behalf of other parties (such as WSPs). |
|
| UserInteraction.Interact
Implementors may choose to define additional values to indicate finer grained control over the user interactions. |
|
|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||