Issue: (Or part of resolution to issue 50?) Every WS Resource operationshould define a ResourceUnkownFault

[Tim Banks <tim_banks@uk.ibm.com>]

Section 2.3 of WS-RAP begins as follows:

1.1   WS-Resource
A WS-Resource is a Web service through which a resource can be accessed. A
WS-Resource is further constrained as follows:
      o   An identifier of the resource MUST appear as part of any message
to a WS-Resource to allow the WS-Resource to disambiguate the resource
targeted by the message. We refer to this pattern of access as the
'WS-Resource Access Pattern'.

A new bullet is needed after this which says: "Any input message to a WS
Resource may result in a fault indicating that resource identifier in the
message is invalid. It is RECOMMENDED that  the UnknownResourceFault
message in the namespace
"http://docs.oasis-open.org/wsrf/2004/11/wsrf-WS-Resource-1.2-draft-01.wsdl";
 be defined for this purpose in the WS Resource description".

The use of a standard fault makes implementation of the WS Resource easier
if the implementation is done using a container which is responsible for
issuing the fault, but there are reasons why the fault might not be
defined, or defined differently:

   A different, application-specific fault may defined to carry the same or
   better meaning: if implemented in a container, the container may be told
   which fault this is.
   UnknownResouceFault doesn't fit the semantics because the WS Resource is
   a singleton.

If no fault is defined, an implementation uses a transport level error
response, such as 'Invalid Message Information Header' defined by WS
Addressing, or an http error if the target url is unknown.

Regards, Tim Banks
IBM TP Architecture & Technology. Hursley, UK.
Phone: External +44 1962 815639, Internal 245639