[
https://issues.apache.org/jira/browse/OLINGO-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586598#comment-16586598
]
Ramesh Reddy commented on OLINGO-1246:
--------------------------------------
[~ramya.vasanth] I am trying to use the 4.5 release, and I see your second
commit from this JIRA adds the key properties to the payload implicitly when
$select is used in the query. I can not find any specific language in the
specification for this, can you please share any details about why you choose
to do this? I just want to make sure Olingo is not producing a wrong payload.
I also see that context URL wise this also includes the key column name that is
not been requested by a user, that may be a violation that differs from what is
expected, I also do not see this specification.
> OData V4: Fixes for Context url when the URL has select clause and expand
> clause having select
> ----------------------------------------------------------------------------------------------
>
> Key: OLINGO-1246
> URL: https://issues.apache.org/jira/browse/OLINGO-1246
> Project: Olingo
> Issue Type: Bug
> Affects Versions: (Java) V4 4.4.0
> Reporter: Ramya
> Priority: Major
>
> If url is of the form
> EntitySetA?$select=NavPropertyToMany&$expand=NavPropertyToMany
> then context url should be of the form
> #EntitySetA(NavPropertyToMany,NavPropertyToMany())
> If url is of the form
> EntitySetA?$select=NavPropertyToMany&$expand=NavPropertyToMany($select=Property)
> then the context url should be of the form
> #EntitySetA(NavPropertyToMany,NavPropertyToMany(Property))
> If url is of the form
> EntitySetA?$expand=NavPropertyToOne1($expand=NavPropertyToOne2), then the
> context url should be
> #EntitySetA(NavPropertyToOne1(NavPropertyToOne2()))
> If url is of the form
> EntitySetA?$expand=NavPropertyToOne,NavPropertyToMany($select=Property), then
> context url should be
> #EntitySetA(NavPropertyToOne(),NavPropertyToMany(Property))
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
