[
https://issues.apache.org/jira/browse/OLINGO-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359483#comment-15359483
]
Jacek Miłaczewski commented on OLINGO-964:
------------------------------------------
To be honest, I hoped that you say something more, maybe disagree with me ;) I
am not sure if it is right solution from OASIS standard point of view. For
example, what about situation when I want to expand more navigation properties
on Collection and these properties are from two or more different subtypes? To
extend my description:
User want to expand collection of entities (e.g. 'Products') with casting type
of this collection to some subtype (''FeaturedProduct) and use property from
this subtype as navigation property to be expanded ('Advertisement') but also
want to cast this collection to another subtype ("DifferentProduct") and expand
property from this different subtype ("AnotherProperty"). How to do that?
> Cast type (typeFilterOnCollection) not taken into account while expanding a
> collection
> --------------------------------------------------------------------------------------
>
> Key: OLINGO-964
> URL: https://issues.apache.org/jira/browse/OLINGO-964
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Affects Versions: (Java) V4 4.2.0, (Java) V4 4.3.0
> Reporter: Jacek Miłaczewski
> Priority: Critical
> Attachments:
> 0001-fix-proposal-for-cast-type-not-taken-into-account-wh.patch
>
>
> When user want to expand collection of entities (e.g. 'Products') with
> casting type of this collection to some subtype (''FeaturedProduct) and use
> property from this subtype as navigation property to be expanded
> ('Advertisement'), error occurs because of not taking into account this
> subtype in ExpandParser.java code but use only superType instead.
> Example url:
> http://.../OData.svc/Categories(1)?$expand=Products/ODataDemo.FeaturedProduct($expand=Advertisement)
> I attach a patch with proposal fix to illustrate what is going on and how it
> should work in my opinion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
