| Package | Description |
|---|---|
| org.openliberty.wsc |
This package contains all of the Service Client classes and the basic WSFMessage.
|
| org.openliberty.xmltooling.disco |
This package models elements in the Discovery Service schema.
|
| org.openliberty.xmltooling.soap.soap11 | |
| org.openliberty.xmltooling.soapbinding | |
| org.openliberty.xmltooling.wsa |
| Class and Description |
|---|
| 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>
|
| Class and Description |
|---|
| Framework
When included in a message, this header provides a means for a sender to communicate the version
of the ID-WSF framework used to construct the message.
|
| Class and Description |
|---|
| 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.
|
| 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.
|
| Framework
When included in a message, this header provides a means for a sender to communicate the version
of the ID-WSF framework used to construct the message.
|
| 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.
|
| 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.
|
| 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).
|
| Class and Description |
|---|
| 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.
|
| 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 |
| Framework
When included in a message, this header provides a means for a sender to communicate the version
of the ID-WSF framework used to construct the message.
|
| InteractionService |
| 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>
|
| 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.
|
| 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.
|
| Class and Description |
|---|
| Framework
When included in a message, this header provides a means for a sender to communicate the version
of the ID-WSF framework used to construct the message.
|
| SecurityMechID |
Copyright © 1999–2015. All rights reserved.