olingo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frederik Zimmer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OLINGO-1073) Collections with derived complex types - wrong odata.type
Date Wed, 10 May 2017 12:20:04 GMT

    [ https://issues.apache.org/jira/browse/OLINGO-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004585#comment-16004585
] 

Frederik Zimmer commented on OLINGO-1073:
-----------------------------------------

Thanks, it works on the client side but the server has now a problem deserializing because
it doesn't take the type information of the collection elements into account. I created a
new Bug OLINGO-1123 for this.

> 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)

Mime
View raw message