[
https://issues.apache.org/jira/browse/OLINGO-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055562#comment-16055562
]
Frederik Zimmer commented on OLINGO-1123:
-----------------------------------------
Hi Archana,
I'm still able to reproduce the issue with 4.4.0-SNAPSHOT. In your test are the
members of the collection correctly deserialized with thier concrete type and
not their base type? I don't think so as consumePropertyCollectionNode just
uses the edm-type and not the @odata.type that might be present.
You will only get the "DeserializerException: Tree should be empty but still
has content left" if your derived type has more properties then your base type.
Regards,
Frederik
> Error deserialization of complex collection with derived type
> -------------------------------------------------------------
>
> Key: OLINGO-1123
> URL: https://issues.apache.org/jira/browse/OLINGO-1123
> Project: Olingo
> Issue Type: Bug
> Affects Versions: (Java) V4 4.3.0
> Reporter: Frederik Zimmer
>
> If a complex collection which contains entries with derived types is
> deserialized the entries are deserialized with the collection type. This
> results then in an error "DeserializerException: Tree should be empty but
> still has content left" because the derived type has more properties which
> are not read.
> In ODataJsonDeserializer the method consumePropertyCollectionNode should
> check with the collection node specifies it's own type and then use this type
> for deserialization.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
