Explicit actions
WSDL documents can explicitly define the values of the <wsa:Action> properties. If the WSDL document does not contain explicitly defined <wsa:Action> properties, CICS® builds default actions when the WSDL is processed by DFHWS2LS.
WSDL 1.1
The following WSDL 1.1 fragment
represents a booking system that contains explicitly defined <wsa:Action>
properties:
<definitions targetNamespace="http://example.ibm.com/namespace" ...>
...
<portType name="bookingSystem">
<operation name="makeBooking">
<input message="tns:makeBooking"
wsa:Action="http://example.ibm.com/namespace/makeBooking"
</input>
<output message="tns:bookingResponse"
wsa:Action="http://example.ibm.com/namespace/bookingResponse"
</output>
</operation>
</portType>
...
</definitions> In this example, the input action of
the makeBooking operation is explicitly defined as http://example.ibm.com/namespace/makeBooking,
and the output action is explicitly defined as http://example.ibm.com/namespace/bookingResponse.WSDL 2.0
The following WSDL 2.0 fragment
represents a booking system that contains explicitly defined <wsa:Action>
properties:
<description targetNamespace="http://example.ibm.com/namespace" ...>
...
<interface name="bookingInterface">
<operation name="makeBooking" pattern="http://www.w3.org/ns/wsdl/in-out">
<input element="tns:makeBooking" messageLabel="In"
wsa:Action="http://example.ibm.com/namespace/makeBooking"/>
<output element="tns:makeBookingResponse" messageLabel="Out"
wsa:Action="http://example.ibm.com/namespace/makeBookingResponse"/>
</operation>
</interface>
...
</description>In this example, the input action of
the makeBooking operation is explicitly defined as http://example.ibm.com/namespace/makeBooking,
and the output action is defined as http://example.ibm.com/namespace/makeBookingResponse.For more information, see the W3C WS-Addressing 1.0 Metadata specification.