[
https://issues.apache.org/jira/browse/OLINGO-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876298#comment-13876298
]
Chandan V.A commented on OLINGO-128:
------------------------------------
Hello Ralf,
I searched the OData spec 2.0 and no where it was mentioned that the response
may/may not contain the Inline entries. The examples quoted in the OData 2.0
spec for deep inserts did not have inline entries and hence I inferred that it
should not be part of the response.
Secondly In order to keep the JPA processor implementation simple for deep
insert cases the inline entries are currently not added to the response. The
complexity of building responses increases when there are more than one level
of inline entries(Customer->SalesOrderHeader->SalesOrderLineItem).
@All,
In case if inline entries needs to be part of OData response with JPA Processor
library then this shall be considered for the implementation in the coming
releases.
Regards
Chandan
> 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)
