[jira] [Commented] (OLINGO-834) Refactoring URI Parsing
[
https://issues.apache.org/jira/browse/OLINGO-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588090#comment-15588090
]
Ralf Handl commented on OLINGO-834:
---
On the other hand we don't have plans to give semantic meaning to whitespace
after a comma, so Olingo MAY opt to gracefully ignore whitespace before or
after a comma :-)
> 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)
[jira] [Commented] (OLINGO-834) Refactoring URI Parsing
[
https://issues.apache.org/jira/browse/OLINGO-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (OLINGO-834) Refactoring URI Parsing
[
https://issues.apache.org/jira/browse/OLINGO-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044910#comment-15044910
]
Michael Bolz commented on OLINGO-834:
-
Created feature branch
[OLINGO-834_RefactorUriParsing|https://git1-us-west.apache.org/repos/asf?p=olingo-odata4.git;a=shortlog;h=refs/heads/OLINGO-834_RefactorUriParsing]
for work on this improvement.
> Refactoring URI Parsing
> ---
>
> Key: OLINGO-834
> URL: https://issues.apache.org/jira/browse/OLINGO-834
> Project: Olingo
> Issue Type: Improvement
>Affects Versions: (Java) V4 4.0.0
>Reporter: Michael Bolz
>
> 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)
