OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Updated: (ODATA-440) Specify response for function or action that returns a single null value


     [ http://tools.oasis-open.org/issues/browse/ODATA-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-440:
--------------------------------

    Proposal: 
Functions, actions, single-valued properties and single-valued navigation properties return 204 No Content if null, and can be composed with functions that accept null binding parameter values.
If a Entity key lookup returns 404 the request returns 404 even if composed with functions/actions that accept null binding parameter values.

  was:
Functions and actions that have a null result for a parameter combination return 204 No Content.

Do the same for single-valued properties and navigation properties.


> Specify response for function or action that returns a single null value
> ------------------------------------------------------------------------
>
>                 Key: ODATA-440
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-440
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol 
>    Affects Versions: V4.0_CSD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD02
>
>
> With ODATA-412 we decided that a null value has no "stand-alone" representation and instead requests to resource that has the null value return 404 Not Found.
> We did not consider actions and functions that return a single value.
> For functions it would be somewhat surprising if they would return 404 No Content if the result for a value combination is null. Especially if the function is composable and composing another function that takes this null value and produces a result from it would respond with 200 OK:
> GET ~/Foo(1) --> 404 Not Found
> GET ~/Foo(1)/Bar(2) --> 200 OK
> Also we already define that actions that do not declare a return type respond with 204 OK, and having "sometimes no result" work differently from "always no result" seems odd.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]