[
https://issues.apache.org/jira/browse/OLINGO-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354623#comment-14354623
]
Christian Amend commented on OLINGO-567:
----------------------------------------
Hi Kevin,
take all the time you need as the GSoC has not even started yet :)
Yes if truly necessary you should change the signature of the serialization
method to contain the EDM. But maybe there is another way to keep the
serialization independent from the EDM.
You say you need the EdmEntitySet to construct the canonical URL for the
EntityID field. Could this information already be present with the current
data? What exactly do you need from the EdmEntitySet to construct this URL?
Also I would suggest you start with the ODataSerializer.entity(..) method. This
way you are more isolated in writing unit tests. Also since we reuse the entity
code for entity collections once the entity implementation is complete you will
only need minor changes to the entity collection method to make it work.
Best Regards,
Christian
> 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
> Assignee: Christian Amend
> Fix For: (Java) V4 4.0.0-beta-03
>
> Attachments:
> odata_metadata=full_support_for_V4_4_0_0-beta-02-Version2.patch,
> odata_metadata=full_support_for_V4_4_0_0-beta-02-Version2_examples.txt,
> 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)
