[
https://issues.apache.org/jira/browse/CXF-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13895341#comment-13895341
]
Andriy Redko commented on CXF-5430:
-----------------------------------
Hi Sergey,
Thanks a lot for the response. I have implemented the one (very simple) use
case as described here
http://olingo.incubator.apache.org/doc/tutorials/Olingo_Tutorial_AdvancedRead_FilterVisitor.html
against Olingo 1.0.0 / OData 2.0 and it just works fine (it's pure
SearchConditionParser implementation which uses Olingo's FilterParser
underneath). I will try to build against Olingo 0.1.0-SNAPSHOT / OData 4.0 to
see what I can get there.
Thanks.
Andriy
> 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)
