W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > May 2009

[Bug 6924] New: WS-T behavior unspecified for Put failure

From: <bugzilla@wiggum.w3.org>
Date: Tue, 19 May 2009 21:22:49 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-6924-2780@http.www.w3.org/Bugs/Public/>

           Summary: WS-T behavior unspecified for Put failure
           Product: WS-Resource Access
           Version: PR
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Transfer
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: gilbert.pilz@oracle.com
         QAContact: public-ws-resource-access-notifications@w3.org

Given a resource with multiple properties, it is possible that some properties
may be "read/write" while other properties are "read only". For example, a
resource may have some form of persistent ID that cannot be changed. An attempt
to change this ID via a WS-Transfer Put would not be honored by the service
that provides access to that resource, but an attempt to change other
properties of the resource would be honored.

The wsa:ActionNotSupported fault is not an accurate description of the problem,
because, in general, Put *is* supported (i.e. other Put operations may
succeed). The wst:InvalidRepresentation fault is also not an accurate
description of the problem because there is nothing wrong with the format or
structure of the supplied representation (i.e. the representation is
schema-valid for the type of resource being accessed).

As a strawman proposal I suggest the definition of a new fault that means "I
can't honor your request to change one or more attributes of this resource"
that optionally includes, in the [Detail] property of the fault, a list of
XPath expressions that identify the offending element(s).

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Received on Tuesday, 19 May 2009 21:23:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:34 UTC