[
https://issues.apache.org/jira/browse/OLINGO-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359670#comment-15359670
]
Ramesh Reddy commented on OLINGO-964:
-------------------------------------
[~jabomi] ha, are you trying to test our OData spec knowledge? ;)
The relevant section I could find is [1] example 34. That also clarifies your
concern about different sub-types, by filtering the results to just that type.
If that is not what you are asking then may be we need to discuss further.
[1]
http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part2-url-conventions/odata-v4.0-errata02-os-part2-url-conventions-complete.html#_Toc406398088
> 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)
