[
https://issues.apache.org/jira/browse/OLINGO-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348679#comment-14348679
]
Kevin Ratnasekera commented on OLINGO-567:
------------------------------------------
Hi Christian,
Resolved some test case failures as some test cases were written expecting a
exception thrown when accept header having odata.metadata=full. I corrected
those and Also some test failures were due to entity metadata order. ( I
commented out in this patch ). Also those are not critical test failures. I
fixed them in this patch. Also I made some changes to the metadata order in
payload than previous patch. Also in the previous patch relative URL s are
calculated for the entity metadata odata.id, odata.navigationLing,
odata.associationLink, now if the service root is present it will be added to
the relative URL. I cleaned the code bit reusing exiting code fragments. Please
take a look at thise patch not the previous one.
Regards
Kevin
> Support odata.metadata=full on server side serialization
> --------------------------------------------------------
>
> Key: OLINGO-567
> URL: https://issues.apache.org/jira/browse/OLINGO-567
> Project: Olingo
> Issue Type: Improvement
> Components: odata4-server
> Affects Versions: (Java) V4 4.0.0-beta-02
> Reporter: Christian Amend
> Fix For: (Java) V4 4.0.0-beta-03
>
> Attachments: odata_metadata=full_support_for_V4_4_0_0-beta-02.patch
>
>
> Support odata.metadata=full on server side serialization. Currently we throw
> a not supported exception during serializer creation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
