olingo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramya (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OLINGO-1122) Addressing derived complex types in filter not working
Date Tue, 25 Jul 2017 04:19:02 GMT

    [ https://issues.apache.org/jira/browse/OLINGO-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099475#comment-16099475
] 

Ramya commented on OLINGO-1122:
-------------------------------

Hi Frederik Zimmer,
This is fixed with the following commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=f6dd0deacc27a21ec2273cb58735005712fe1dd7
Kindly verify and get back if any issue found.

Regards,
Ramya

> Addressing derived complex types in filter not working
> ------------------------------------------------------
>
>                 Key: OLINGO-1122
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1122
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-server
>    Affects Versions: (Java) V4 4.3.0
>            Reporter: Frederik Zimmer
>
> I have a filter like this (the any is propably not relevant to this bug):
> complexCollection/any(a:a/com.someType/derivedProperty eq false)
> I try to address the collection element which is of complex type as a derived type of
the collection. This will work when the collection contains entities but doesn't work for
complex types. The problem is that the method parseMemberExpression in org.apache.olingo.server.core.uri.parser.ExpressionParser
tries to interpret the typecast as an entity and if this doen't work it assumes that it is
a bound function. So for complex typecasts the type is interpreted as a bound function and
the parsing fails.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message