[
https://issues.apache.org/jira/browse/OLINGO-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198298#comment-16198298
]
Kiran G commented on OLINGO-1189:
---------------------------------
Pushed the fix via pull request.
https://github.com/apache/olingo-odata2/pull/13
> [olingo2-jpa] Order of the entities in $metadata differes for the same JPA
> Metamodel
> -------------------------------------------------------------------------------------
>
> Key: OLINGO-1189
> URL: https://issues.apache.org/jira/browse/OLINGO-1189
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
> Affects Versions: V2 2.0.9
> Reporter: Kiran G
> Priority: Minor
>
> Olingo2 JPA library generates the $metadata document on the fly when the
> request arrives by consulting the JPA metamodel. Since, the JPA metamodel
> need not essentially load the entities classes in an order fashion (tested
> with Hibernate ORM), every time the server restarts the order of the Entities
> in the $metadata changes.
> Some clients like SMP OData client is very sensitive even to these changes in
> the order of the entities and treats it as a new version of the service. This
> in turn is causing various issues at the client side.
> Fix:
> Manually sort the entities got from JPA metamodel before building the OData
> entity model. This would result in the same metadata xml even after the
> server is restarted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
