Kavindu Dodanduwa commented on OLINGO-834:

This is regarding URI parsing. Prior to the V4.4.2, parameters with spaces were 
allowed to pass through Olingo. But after changing the version to V4.4.2, 
spaces are not allowed in parameters.

For example, consider the following,

<service>/EntitySet(key1='k1', key2='k2')  is valid prior to V4.4.2 (mind the 
space between two parameters)

But for versions V4.4.2 and above, it gives and error with following details,

"Expected token 'ODataIdentifier' not found." [stack trace refer to,  

According to the specification and ABNF there's nothing stated on allowing 
spaces between parameters but is this the intentional behavior.?

> Refactoring URI Parsing
> -----------------------
>                 Key: OLINGO-834
>                 URL: https://issues.apache.org/jira/browse/OLINGO-834
>             Project: Olingo
>          Issue Type: Improvement
>          Components: odata4-server
>    Affects Versions: (Java) V4 4.0.0
>            Reporter: Michael Bolz
>            Assignee: Christian Amend
>             Fix For: (Java) V4 4.2.0
> Current generated URI parser (ANTLR approach) is hard to maintain and to be 
> extended.
> As a proposal the generated URI parser should be replaced with an own 
> implementation. 
> Furthermore with the new implementation performance improvements are expected.
> The new URI parser should alsoe consider {{$expand}} in combination with 
> {{$search}}.

This message was sent by Atlassian JIRA

Reply via email to