4.3 Reference Parameters
1 Extending WSDL Endpoints with an EPR), the value of the [reference parameters] message addressing property for verso message sent preciso an endpoint MUST include the contents of the wsa:ReferenceParameters element, if one exists within that EPR.
WS-Addressing defines two mechanisms sicuro associate per value of the [action] property with stimolo, output and fault elements within per WSDL description: explicit and defaulting. Explicit association is described con section 4.4.1 Explicit Association; action defaulting (where per unique value for the [action] property is automatically generated) is described mediante section 4.4.4 Default Action Pattern for WSDL 1.1 for WSDL 1.1 and http://www.datingranking.net/it/sugar-daddy-for-me-review section 4.4.2 Default Action Pattern for WSDL 2.0 for WSDL 2.0.
Ensuring that there is sufficient information within per message esatto distinguish which WSDL operation it is associated with is specified as a best practice con WSDL 2.0 WSDL 2.0 . The [action] property provides verso mechanism sicuro fulfill that best practice.
4.4.1 Explicit Association
WS-Addressing defines per global attribute, wsam:Action, that can be used to explicitly define the value of the [action] property for messages durante per WSDL description. The type of the attribute is xs:anyURI and it is used as an extension on the WSDL stimolo, output and fault elements. Per SOAP binding can specify SOAPAction values for the stimolo messages of operations. In the absence of verso wsam:Action attribute on per WSDL input element where verso non-empty SOAPAction value is specified, the value of the [action] property for the incentivo message is the value of the SOAPAction specified. If the wsam:Action attribute is absent, and SOAPAction is not specified, or is empty, then the default pattern is used. Note that the SOAPAction value is not required preciso be an absolute IRI, but the [action] property is required sicuro be an absolute IRI; if WS-Addressing is required (the wsam:Addressing assertion is present), wsam:Action is not specified, and the SOAPAction value is not empty or an absolute IRI, then the document MUST be considered invalid. Web Services Addressing 1.0 – SOAP Binding[ WS-Addressing SOAP Binding ] specifies restrictions on the relationship between the values of [action] and SOAPAction for SOAP 1.1 and SOAP 1.2.
The inclusion of wsam:Action without the inclusion of the wsam:Addressing assertion has mai normative intent and is only informational. Per other words, the inclusion of wsam:Action attributes sopra WSDL alone does not imply per requirement on clients preciso use Message Addressing Properties in messages it sends preciso the service. Verso client, however, MAY include Message Addressing Properties sopra the messages it sends, either on its own initiative or as described by other elements of the service contract, regardless of the presence or absence of the wsam:Addressing assertion. Other specifications defining the value of [action] are under mai constraint to be consistent with wsam:Action.
The action for the incentivo of the opCheckAvailability operation within the reservationInterface is explicitly defined sicuro be The action for the output of this same operation is
The action for the incentivo of the opCheckAvailability operation within the reservationInterface port type is explicitly defined esatto be The action for the output of this same operation is
4.4.2 Default Action Pattern for WSDL 2.0
Con the absence of an explicitly specified value for the [action] property (see section 4.4.1 Explicit Association), the following pattern is used con WSDL 2.0 documents onesto construct per default action for inputs and outputs. The general form of an action URI is as follows:
is “:” when the [target namespace] is a URN, otherwise “/”. Note that for IRI schemes other than URNs which aren’t path-based (i.anche. those that outlaw the “/” character), the default action value might not conform preciso the rules of the IRI scheme. Authors are advised puro specify explicit values in the WSDL con this case.