[
https://issues.apache.org/jira/browse/OLINGO-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207532#comment-15207532
]
Ramesh Reddy commented on OLINGO-811:
-------------------------------------
[~chrisam] Can you review this feature branch and pull in the changes into
master
https://github.com/apache/olingo-odata4/commit/5dee97f7628c793e2bbcd3f89d8d5c52e07639ea
The branch name should be OLINGO-811
It took while because of the client libraries (parsing and extension of the
URIBuilder) etc. IMO client is much more complicated than server library.
Anyway all tests should be running fine against master.
Features implemented in this commit are (equally for JSON, ATOM) as following
parsing
- entity?$expand=nav($count=true)
- entity?$expand=nav($count=true)/$count
- entity?$expand=nav/$ref
Yes, $ref was little additional work, so I went ahead and worked it in. There
are unit tests for all the features added.
> Use of $count for expanded items does not work
> ----------------------------------------------
>
> Key: OLINGO-811
> URL: https://issues.apache.org/jira/browse/OLINGO-811
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Affects Versions: (Java) V4 4.0.0
> Reporter: Michael Bolz
> Assignee: Ramesh Reddy
> Fix For: (Java) V4 4.2.0
>
> Attachments: patch-Nov-09-2015.diff, patch.diff
>
>
> The {{$count}} query option within the {{$expand}} clause does not work
> correctly (see in
> [Specification|http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html#_The_$inlinecount_System]
> Example URL (for *TecSvc*):
> http://localhost:8080/odata.svc/ESAllPrim/?$expand=NavPropertyETTwoPrimMany($count=true)&$format=json&$count=true
> And example for OData-TripPin Service:
> [http://services.odata.org/V4/(S(kb3m31znaqv0xd4oqq0esxfv))/TripPinServiceRW/People?$expand=Trips($count=true)]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
