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] (ODATA-882) Mismatch between 11.2.6 Requesting Related Entities and 11.2.7 Requesting Entity References


Ralf Handl created ODATA-882:
--------------------------------

             Summary: Mismatch between 11.2.6 Requesting Related Entities and 11.2.7 Requesting Entity References
                 Key: ODATA-882
                 URL: https://issues.oasis-open.org/browse/ODATA-882
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData Protocol
    Affects Versions: V4.0_ERRATA02
            Reporter: Ralf Handl
             Fix For: V4.0_ERRATA03


11.2.6 defines that requests to nullable single-valued navigation properties return 204 No Content if no entity is currently related.

11.2.7 defines that all requests for references to a single entity return 404 Not Found, not distinguishing between "direct" resource paths and resource paths to related entities.

This leads to:

GET Employees('TheBigBoss')/Manager --> 204 No Content
GET Employees('TheBigBoss')/Manager/$ref --> 404 Not Found

Clarify whether this is intentional:
A) Of course, the related Manager is empty, so the reference does not exist, or
B) Ooops, of course both requests should return the same response code because /$ref is just a briefer representation of the non-existing related entity






--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


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