[
https://issues.apache.org/jira/browse/OLINGO-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16058810#comment-16058810
]
Archana Rai edited comment on OLINGO-1123 at 6/22/17 6:05 AM:
--------------------------------------------------------------
Hi Frederik,
I can simulate that the edm type is only shown irrespective of @odata.type.
But the "DeserializerException: Tree should be empty but still has content
left" I am not able to simulate yet.
Instead I an getting <propertyName> cannot be mapped as a property or
annotation.
Can you please share the metadata and the payload you are trying with.
Thanks,
Archana
was (Author: archanarai):
Hi Frederik,
I can simulate that the edm type is only shown irrespective of @odata.type.
But the "DeserializerException: Tree should be empty but still has content
left" I am not able to simulate yet.
Can you please share the metadata and the payload you are trying with.
Thanks,
Archana
> 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)
