[
https://issues.apache.org/jira/browse/OLINGO-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Amend resolved OLINGO-946.
------------------------------------
Resolution: Fixed
Fixed with commit:
https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=750e9b9de29e2187c4e064cf8bbfa5fbb8aa92e6
> V2 JPA: Store EdmProvider data in a LinkedHashMap
> -------------------------------------------------
>
> Key: OLINGO-946
> URL: https://issues.apache.org/jira/browse/OLINGO-946
> Project: Olingo
> Issue Type: Improvement
> Components: odata2-jpa
> Affects Versions: V2 2.0.6
> Reporter: Christian Amend
> Assignee: Christian Amend
> Fix For: V2 2.0.7
>
>
> Currently the JPA EdmProvider stores all EDM objects within a simple HashMap.
> This results in a different metadata document ordering per request. This is
> problematic when creating a md5 hash for the metadata document to generate an
> etag for clients.
> Changing this to a LinkedHashMap will solve this without changing the API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
