You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Sven Kobler-Morris (JIRA)" <ji...@apache.org> on 2015/02/17 15:56:13 UTC

[jira] [Resolved] (OLINGO-576) Uri literal escaping in FilterParser

     [ https://issues.apache.org/jira/browse/OLINGO-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sven Kobler-Morris resolved OLINGO-576.
---------------------------------------
    Resolution: Fixed

Fixed.

When calling "getUriLiteral" via interface "CommonExpression" on a "LiteralExpressionImpl" instance now the correct UriLiteral is returned.

Sample:
$filter=concat('a','a''b')
When calling getUriLiteral on the Filtertree-Node representing the second parameter now correcly 'a''b' is returned instead of 'a'b'.


> Uri literal escaping in FilterParser
> ------------------------------------
>
>                 Key: OLINGO-576
>                 URL: https://issues.apache.org/jira/browse/OLINGO-576
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-core
>    Affects Versions: V2 2.0.2
>            Reporter: Christian Amend
>            Assignee: Sven Kobler-Morris
>             Fix For: V2 2.0.3
>
>
> Fix URI literal escaping for the filter parser. And adopt the changes to the JPA extension.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)