Implementation of WS-Addressing in CentraSite
CentraSite can import WSDLs that have WS-Addressing annotations.
CentraSite can virtualize WSDLs having WS-Addressing annotations. The annotations are kept in the WSDL for the virtualized service because they do not contain relevant information about the native service endpoint.
The following WS-Addressing headers can be included in a WSDL:
<wsam:UsingAddressing wsdl:required="true" />![*](bullet.gif)
Explicit
wsam:Action attributes for operation input/output elements. For example:
wsam:Action="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability"
![*](bullet.gif)
Default actions for inputs and outputs (for backwards compatibility with WSDL 1.1). The following pattern is used to construct a default action for inputs and outputs. The general form of an action IRI is as follows:
wsam:Action="[target namespace][delimiter][port type name][delimiter][input|output name]"
![*](bullet.gif)
Endpoint references, such as:
<wsa10:EndpointReference>
<wsa10:Address>[url]</wsa10:Address>
</Identity>
</wsa10:EndpointReference>What happens to these WS-Addressing headers?
![*](bullet.gif)
For a native service asset (created through import WSDL), the WSDL remains "as is"; no rewriting occurs.
![*](bullet.gif)
For a virtual service:
![*](bullet.gif)
The WS-Policy attachment block (containing the
UsingAdressing element) is removed.
![*](bullet.gif)
The
wsam:Action attributes remain on the operations.
![*](bullet.gif)
The endpoint references are removed because they are replaced by
Mediator's endpoint information.