[
https://issues.apache.org/jira/browse/OLINGO-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225755#comment-14225755
]
Michael Bolz commented on OLINGO-497:
-------------------------------------
Hi [~kiransg],
problem with changes in the API is that they must be backward compatible.
So a change from {{HashMap}} to {{List}} would break an implementation.
But I agree with you that another return type would be better then just to
specify the correct behaviour in the according JavaDoc (based on _2.2.3.6.1.6
OrderBy System Query Option ($orderby)_ in specification).
Kind regards,
Michael
> JPQLSelectContextView should use LinkedHashMap for OrderBy
> ----------------------------------------------------------
>
> Key: OLINGO-497
> URL: https://issues.apache.org/jira/browse/OLINGO-497
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
> Affects Versions: V2 2.0.0
> Reporter: Kiran G
> Assignee: Michael Bolz
>
> JPQLSelectContextView has a method to getOrderByCollection.
> {code}
> public HashMap<String, String> getOrderByCollection();
> {code}
> This method really should return LinkedHashMap to preserve the order of the
> $orderby's specified in the url. With the HashMap the orderbys are now being
> applied in a random order in the query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
