olingo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Amend (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OLINGO-1046) Whitespaces in functions not allowed
Date Wed, 16 Nov 2016 10:27:59 GMT

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

Christian Amend commented on OLINGO-1046:
-----------------------------------------

I don`t think so. The ABNF clearly states "BWS" which means bad whitespace. We are actually
specification conform with this. The question is rather if we should be more relaxed.

> Whitespaces in functions not allowed
> ------------------------------------
>
>                 Key: OLINGO-1046
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1046
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-server
>    Affects Versions: (Java) V4 4.3.0
>            Reporter: Frederik Zimmer
>
> Whitespaces before/after comma/parenthesis in functions are allowed by the ABNF but Olingo
is unable to parse them.
> This would result in an error (inserted space after comma in Testcase of TestFullResourcePath):
> startswith(PropertyCompAllPrim/PropertyString, 'Wall')
> ABNF example:
> startsWithMethodCallExpr = 'startswith' OPEN BWS commonExpr BWS COMMA BWS commonExpr
BWS CLOSE
> BWS =  *( SP / HTAB / "%20" / "%09" )  ; "bad" whitespace



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

Mime
View raw message