Re: [wsrf] Issue: (Or part of resolution to issue 50?) Every WS Resource operation should define a ResourceUnkownFault

[David Snelling <David.Snelling@UK.Fujitsu.com>]

Folks,

A interesting corollary to this came up at the EGEE conference (The  
Grid for particle physics and other big science in the EU).

What about a WS-Resource "Known" to the Web service but not currently  
"Available"? This may occur quite often in the case of a "many  
resources per endpoint" scenario. Should this fault be called out  
separately in WSRF or is it really an implementation specific fault? If  
the later, we probably need to change the name of UnknownResourceFault  
to something more generic to allow for the above scenario.

On 29 Nov 2004, at 15:45, Tim Banks wrote:

>
>
>
>
> 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
>
>
-- 

Take care:

     Dr. David Snelling < David . Snelling . UK . Fujitsu . com >
     Fujitsu Laboratories of Europe
     Hayes Park Central
     Hayes End Road
     Hayes, Middlesex  UB4 8FE

     +44-208-606-4649 (Office)
     +44-208-606-4539 (Fax)
     +44-7768-807526  (Mobile)