[
https://issues.apache.org/jira/browse/OLINGO-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876284#comment-13876284
]
Ralf Handl commented on OLINGO-128:
-----------------------------------
Please note that the OData 2.0 specification does not forbid or discourage
responding with inline entries, it just gives only example responses without
inline content.
OData 4.0 on the other hand requires to respond with inline content if the
create request contained inline content:
http://docs.oasis-open.org/odata/odata/v4.0/cos01/part1-protocol/odata-v4.0-cos01-part1-protocol.html#_Toc372793718.
> Do Not add inline entries in the OData Response for Deep Insert Request
> -----------------------------------------------------------------------
>
> Key: OLINGO-128
> URL: https://issues.apache.org/jira/browse/OLINGO-128
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
> Affects Versions: V2 1.0.0, V2 1.1.0
> Reporter: Chandan V.A
> Assignee: Chandan V.A
> Fix For: V2 1.1.0
>
>
> An OData response with inline entries is generated for Deep Insert scenarios.
> However as per OData specification 2.0
> (http://www.odata.org/documentation/operations/#24_Creating_new_Entries) the
> OData response should not contain inline entries for deep insert use cases.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
