[
https://issues.apache.org/jira/browse/OLINGO-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Amend resolved OLINGO-1073.
-------------------------------------
Resolution: Fixed
Assignee: Christian Amend
Fix Version/s: (Java) V4 4.4.0
I apllied the patch with the following commit:
https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=32ff14fe788b5dbd80ffd61c1e83e460427bae9e
Thanks for the contribution.
> Collections with derived complex types - wrong odata.type
> ---------------------------------------------------------
>
> Key: OLINGO-1073
> URL: https://issues.apache.org/jira/browse/OLINGO-1073
> Project: Olingo
> Issue Type: Bug
> Components: odata4-client
> Affects Versions: (Java) V4 4.3.0
> Reporter: Frederik Zimmer
> Assignee: Christian Amend
> Fix For: (Java) V4 4.4.0
>
> Attachments: Odata_types.diff
>
>
> When you have a collection of complex types the client knows during
> serialization only the type of the collection. So when you have complex
> values of a derived type in the collection they get serialized incorrectly
> with a odata.type of the collection and not their own derived type.
> The problem is that during the serialization we only have a ComplexValue
> without type information. The ODataBinderImpl will transform a ClientValue
> which has correct type information to a ComplexValue without type
> information. The easiest solution would be propably to add type information
> to ComplexValue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
