cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5430) Support for OData query language
Date Fri, 07 Feb 2014 21:37:22 GMT

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

Sergey Beryozkin commented on CXF-5430:
---------------------------------------

Hi Andriy

Thanks for the update; 
I'm looking at OData V2 documentation and see nothing similar to 

v3:
http://www.odata.org/documentation/odata-v3-documentation/odata-core/#1023_Querying_Collections

and

v4:
http://docs.oasis-open.org/odata/odata/v4.0/cos01/part1-protocol/odata-v4.0-cos01-part1-protocol.html#_Toc372793691

which is really what we want to support initially.
It may be that 

http://www.odata.org/documentation/odata-v2-documentation/

is not complete; if

http://olingo.incubator.apache.org/doc/tutorials/Olingo_Tutorial_AdvancedRead_FilterVisitor.html

works with Olingo 1.0.0 OData v2.0 implementation then it is good enough for a start.

If not or if the filters supported in Olingo 1.0.0 are really different from the filters supported
in OData v3 or v4 then I'd settle on working with Olingo trunk and we'd wait till it is released,
should we do it anyway to save us from the migration hassle later on ? Please check what the
actual filter differences and let us know
; please take your time :-)
Many thanks, Sergey   

> Support for OData query language
> --------------------------------
>
>                 Key: CXF-5430
>                 URL: https://issues.apache.org/jira/browse/CXF-5430
>             Project: CXF
>          Issue Type: New Feature
>          Components: JAX-RS
>            Reporter: Sergey Beryozkin
>            Assignee: Andriy Redko
>
> Apache Olingo project (http://olingo.incubator.apache.org/) provides implementation for
OData (http://odata.org/).
> This task is about adapting OLingo URI Parser to CXF Search API.
> org.apache.cxf.jaxrs.ext.search.SearchConditionParser implementation will use Olingo
parser. The existing CXF Search visitors will be expected to work with both FIQL and OData
parsers.
> We may hit some limitations in the existing CXF Search API because OData is more sophisticated
language than FIQL. 
> At the moment I don't think it is realistic to support OData completely within CXF Search
API constraints. Most likely we will just settle for supporting the subset of OData queries,
with users being recommended to work directly with Olingo to get a complete support. Alternatively
we can try and enhance the search API if it proves feasible.   



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message