2.1 Referencing WSDL Metadata from an EPR

2.1 Referencing WSDL Metadata from an EPR

All information items defined by this specification are identified by the XML namespace URI [ XML Namespaces ] “”. A normative XML Schema [ XML Nota Structures , XML Schema Datatypes ] document can be obtained by dereferencing the XML namespace URI.

2. Including WSDL Metadata con EPRs

The WSDL binding of Web Services Addressing introduces the following element and attribute information items for referencing WSDL metadata from an EPR’s metadata section:

Verso QName identifying a description of the sequences of messages that verso service sends and/or receives. This corresponds onesto per WSDL 2.0 interface or, for backwards compatibility, verso WSDL 1.1 port type. When this element is included sopra an EPR, the EPR is considered sicuro be specific sicuro the interface or port type it identifies.

Per QName that identifies the serie of endpoints at which a particular Web service is deployed. The set of endpoints is represented by verso service durante WSDL 2.0 or, for backwards compatibility, verso WSDL 1.1 service.

An NCName that identifies one endpoint amongst the serie identified by the service name above. An endpoint is represented by an endpoint in WSDL 2.0 or, for backwards compatibility, per port per WSDL 1.1. When this attribute silverdaddy is specified, the EPR is considered puro be specific puro the endpoint or port it identifies.

The element information items defined above are used durante an EPR’s metadata section. The following shows an example endpoint reference. This references the interface named “ghns:reservationInterface” at the endpoint IRI “”. Note the use of the WSDL[ WSDL 2.0 ] wsdlLocation attribute.

3. Indicating Use of WS-Addressing

This specification supports verso mechanism for indicating, sopra a WSDL description, that the endpoint conforms sicuro the WS-Addressing specification. That mechanism uses WS-Policy Framework [ WS Policy 1.5 ].

3.1 WS-Policy Assertions

The mechanism for indicating that a binding or endpoint conforms puro the WS-Addressing specification is through the use of the Web Services Policy – Framework [ WS Policy 1.5 ] and Web Services Policy – Attachment [ WS Policy 1.5 – Attachment ] specifications. This specification defines three policy assertions.

For WSDL 1.1, these assertions may be attached sicuro wsdl11:port or wsdl11:binding . For WSDL 2.0, they may be attached esatto wsdl20:endpoint or wsdl20:binding . Per policy expression containing the wsam:Addressing policy assertion MUST NOT be attached to verso wsdl:portType or wsdl20:interface . The wsam:Addressing policy assertion specifies a concrete behavior whereas the wsdl:portType or wsdl20:interface is an abstract construct.

3.1.1 Addressing Assertion

The wsam:Addressing policy assertion is verso nested policy container assertion. The meaning of this assertion, when present mediante per policy alternative, is that WS-Addressing is required onesto communicate with the subject. The wsam:Addressing assertion indicates that there are no restrictions on the use of WS-Addressing unless otherwise qualified by assertions per its nested policy expression. Mediante order sicuro indicate that the subject supports WS-Addressing but does not require its use, an additional policy alternative should be provided which does not contain this assertion; the compact authoring style for an optional policy assertion provided by WS-Policy V1.5 [ WS Policy 1.5 ] may be used. The wsp:Optional attribute, as per syntactic shortcut, can be used with the wsam:Addressing assertion. This indicates two policy alternatives, one which contains the policy assertion, and another which does not.

The inclusion of this assertion implies support for the Web Services Addressing 1.0 – Core [ WS-Addressing Core ] and Web Services Addressing 1.0 – SOAP Binding [ WS-Addressing SOAP Binding ].

3.1.2 AnonymousResponses Assertion

The wsam:AnonymousResponses element MAY be used as per policy assertion nested within the wsam:Addressing assertion sopra accordance with the rules laid down by policy assertion nesting ([ WS Policy 1.5 ], section 4.3.2).

Comments are closed.