[
https://issues.apache.org/jira/browse/OLINGO-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343895#comment-15343895
]
Christian Amend commented on OLINGO-964:
----------------------------------------
It is best if you create the patch according to this guide here:
http://olingo.apache.org/contribute.html
If you include a test it is easier for us to verify that the feature works as
intended. It also ensures that this fix is not invalidated in the future.
The tests for the URI parser can be found in the server-test maven module.
Thanks for providing the first patch :)
> 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)
