-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major
-
Affects Version/s: V4.0_CSD01
-
Component/s: Protocol
-
None
-
Environment:
[Applied]
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.