You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2014/03/24 13:27:46 UTC
[jira] [Comment Edited] (OLINGO-194) Merge and update URIBuilder
and FilterFactory from ODataJClient
[ https://issues.apache.org/jira/browse/OLINGO-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944963#comment-13944963 ]
Francesco Chicchiriccò edited comment on OLINGO-194 at 3/24/14 12:26 PM:
-------------------------------------------------------------------------
After re-reading carefully the [OData 4.0 ABNF grammar|http://docs.oasis-open.org/odata/odata/v4.0/os/abnf/odata-abnf-construction-rules.txt] it seems that something is missing in URIBuilder:
# using enum values as entity key
# geospatial literals
# complex and collection literals
was (Author: ilgrosso):
After re-reading carefully the [OData 4.0 ABNF grammar|http://docs.oasis-open.org/odata/odata/v4.0/os/abnf/odata-abnf-construction-rules.txt] it seems that something is missing in URIBuilder:
1. using enum values as entity key
1. geospatial literals
1. complex and collection literals
> Merge and update URIBuilder and FilterFactory from ODataJClient
> ---------------------------------------------------------------
>
> Key: OLINGO-194
> URL: https://issues.apache.org/jira/browse/OLINGO-194
> Project: Olingo
> Issue Type: New Feature
> Components: odata4-client
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Fix For: V4 0.1.0
>
>
> Merge existing URIBuilder and FilterFactory from ODataJClient (working for V3) and provide implementations for V4 supporting all new characteristics in URI management [1][2].
> [1] http://docs.oasis-open.org/odata/new-in-odata/v4.0/new-in-odata-v4.0.html
> [2] http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part2-url-conventions.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)