[
https://issues.apache.org/jira/browse/OLINGO-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154166#comment-14154166
]
Ramesh Reddy commented on OLINGO-438:
-------------------------------------
Good question Mark. At least in my contribution I was following the precedent
set forth in the previous API calls. IMO, a clean Server Producer API, that is
separated from protocol specifics would have been better, for ex:
{code}
public interface EntityCollectionProcessor extends Processor {
List<Entity> readCollection(UriInfo uriInfo, RequestContext context) throws
EntitySetNotFound, ODataException;
long readCount(UriInfo uriInfo, RequestContext context) throws
EntitySetNotFound, ODataException;
}
{code}
where the serialization and response codes and context-url is completely
handled by the framework. I believe that could be accomplished, unless I am
missing something obvious beyond my knowledge of framework at this point.
> $Count of a Collection is not supported
> ---------------------------------------
>
> Key: OLINGO-438
> URL: https://issues.apache.org/jira/browse/OLINGO-438
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Affects Versions: V4 4.0.0-beta-01
> Reporter: Ramesh Reddy
> Assignee: Michael Bolz
> Priority: Critical
> Fix For: (Java) V4 4.0.0-beta-02
>
>
> Currently "Count of Collection" from OData Spec
> http://docs.oasis-open.org/odata/odata/v4.0/os/part2-url-conventions/odata-v4.0-os-part2-url-conventions.html#_Toc372793785
> is not supported.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
