[OASIS Issue Tracker] (ODATA-634) Specify the behaviour when a non-nullable property with no default value is omitted from a PUT

[ https://tools.oasis-open.org/issues/browse/ODATA-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36977#comment-36977 ] 

Michael Pizzo commented on ODATA-634:
-------------------------------------

We generally don't mandate specific errors in cases (since there could be other problems as well) so wording would be something like: "Services MUST return an error, such as 400 Bad Request, when a non-nullable property with no default value is omitted from a PUT request body." 

> Specify the behaviour when a non-nullable property with no default value is omitted from a PUT
> ----------------------------------------------------------------------------------------------
>
>                 Key: ODATA-634
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-634
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol 
>    Affects Versions: V4.0_OS
>            Reporter: Matthew Borges
>            Priority: Minor
>             Fix For: V4.0_ERRATA01
>
>
> Section 11.4.3 of the protocol document specifies how an OData server should handle a PUT request.  However, it doesn't specify what the server should do if a non-nullable property with no default value is omitted from the PUT request body.



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)