[
https://issues.apache.org/jira/browse/OLINGO-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588061#comment-15588061
]
Ralf Handl commented on OLINGO-834:
-----------------------------------
The normative prose specification refers to the ABNF rule keyPredicate, which
doesn't allow spaces after the comma:
keyPredicate = simpleKey / compoundKey
compoundKey = OPEN keyValuePair *( COMMA keyValuePair ) CLOSE
keyValuePair = ( primitiveKeyProperty / keyPropertyAlias ) EQ (
parameterAlias / keyPropertyValue )
primitiveKeyProperty = odataIdentifier
keyPropertyAlias = odataIdentifier
odataIdentifier = identifierLeadingCharacter *127identifierCharacter
> 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
(v6.3.4#6332)
