Package org.openliberty.xmltooling.soapbinding

Class Summary

Class	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.
ApplicationEPR.Builder	Internal Builder
ApplicationEPR.Marshaller	Internal Marshaller
ApplicationEPR.Unmarshaller	Internal Unmarshaller
Consent	This header block is used to explicitly claim that the Principal consented to the present interaction.
Consent.Builder	Internal Builder
Consent.Marshaller	Internal Marshaller
Consent.Unmarshaller	Internal Unmarshaller
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.Builder	Internal Builder
EndpointUpdate.Marshaller	Internal Marshaller
EndpointUpdate.Unmarshaller	Internal Unmarshaller
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.
Framework.Builder	Internal Builder Class
Framework.Marshaller	Internal Marshaller Class
Framework.Unmarshaller	Intenal Unmarshalling class
InteractionService
InteractionService.Builder	Internal Builder
InteractionService.Marshaller	Internal Marshaller
InteractionService.Unmarshaller	Internal Unmarshaller
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.Builder	Internal Builder
ProcessingContext.Marshaller	Marshall attributes into the DOM
ProcessingContext.Unmarshaller	Internal class that handles unmarshalling from the DOM
RedirectRequest	<xs:element name="RedirectRequest" type="RedirectRequestType"/> <xs:complexType name="RedirectRequestType"> <xs:attribute name="redirectURL" type="xs:anyURI" use="required"/> </xs:complexType>
RedirectRequest.Builder	Internal Builder
RedirectRequest.Marshaller	Static Internal Marshaller
RedirectRequest.Unmarshaller	Static Internal Unmarshaller
SecurityMechID
SecurityMechID.Builder
SecurityMechID.Marshaller
SecurityMechID.Unmarshaller
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.
Sender.Builder	Internal Builder
Sender.Marshaller	Internal Marshaller
Sender.Unmarshaller	Internal Unmarshaller
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.
TargetIdentity.Builder	Internal Builder
TargetIdentity.Marshaller	Internal Marshaller
TargetIdentity.Unmarshaller	Internal Unmarshaller
Timeout	A requesting entity may wish to indicate that they would like a request to be processed within some specified amount of time.
Timeout.Builder	Internal Builder
Timeout.Marshaller	Internal Marshaller
Timeout.Unmarshaller	Internal Unmarshaller
UsageDirective	Participants in the ID-WSF framework may need to indicate the privacy policy associated with a message.
UsageDirective.Builder	Internal Builder
UsageDirective.Marshaller	Internal Marshaller
UsageDirective.Unmarshaller	Internal Unmarshaller
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.Builder	Static Internal Builder
UserInteraction.Marshaller	Marshall attributes into the DOM
UserInteraction.Unmarshaller	Internal class that handles unmarshalling from the DOM

Enum Summary

Enum	Description
EndpointUpdate.UpdateType
ProcessingContext.Defined	New processing context facet identifiers MAY be defined in other specifications, for example in ID-SIS data service specifications.
UserInteraction.Interact	Implementors may choose to define additional values to indicate finer grained control over the user interactions.