This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6579 - RT - Bad fragment values with Create
Summary: RT - Bad fragment values with Create
Status: CLOSED WONTFIX
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: ResourceTransfer (show other bugs)
Version: FPWD
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Geoff Bullen
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2009-02-13 19:07 UTC by Geoff Bullen
Modified: 2009-09-30 10:03 UTC (History)
1 user (show)

See Also:


Attachments

Description Geoff Bullen 2009-02-13 19:07:08 UTC
The description of Create/Fragment/Value says that the resource MUST return a CreateFault if it cannot write the requested fragment. However, CreateFault is reserved for internal errors.  It may be that the fragment value is valid XML, but is not applicable given the fragment expression. E.g. if the fragment expression points to an integer, but a string is passed in the value.  Should a new fault be defined to handle this case?
Comment 1 Robert Freund 2009-03-14 18:04:35 UTC
Action-30