WSA WSDL Binding Issue (Action without UsingAddressing)

If the WSDL does not include wsaw:UsingAddressing in either wsdl:binding
or wsdl:port but one or more wsdl:portType/wsdl:operation contain
wsaw:Action, the expected behavior in such a case is unclear. Here are
the six possible options:

1. Inclusion of wsa:Action without inclusion of wsa:UsingAddressing is
equivalent to inclusion of wsa:UsingAddressing with wsdl:required=true.
IOW, messages MUST include wsa MAPs and wsa:Action MUST be honored.

2. Inclusion of wsa:Action without inclusion of wsa:UsingAddressing is
equivalent to inclusion of wsa:UsingAddressing with wsdl:required=false.
IOW, messages MAY include wsa MAPs but if so wsa:Action MUST be honored.

3. Inclusion of wsa:Action without inclusion of wsa:UsingAddressing is
purely advisory. IOW, messages MAY include wsa MAPs and if so wsa:Action
MAY be honored.

4. Inclusion of wsa:Action without inclusion of wsa:UsingAddressing is
purely advisory. IOW, the messages MAY include wsa MAPs and if so
wsa:Action MUST be honored.

5. Inclusion of wsa:Action without inclusion of wsa:UsingAddressing is
equivalent gets ignored. IOW, messages MUST not include wsa MAPs.

6. Something else

In 3 and 4, other information is needed to determine whether
WS-Addressing is supported.

The spec needs to provide a clear guidance on what needs to happen in
such a case. 2 or 3 seems ok and I have a preference for 2.

-Arun

-- 
got Web Services ?
Download Java Web Services Developer Pack from
http://java.sun.com/webservices

Received on Thursday, 11 August 2005 23:03:34 UTC