[
https://issues.apache.org/jira/browse/CXF-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838800#comment-13838800
]
Sergey Beryozkin commented on CXF-5430:
---------------------------------------
I did a minor update to let custom parser be recognized and added a basic test
showing how a custom parser might adapt the custom expressions to CXF
SearchCondition:
http://svn.apache.org/r1547752
(and r1547756)
So for POC we'd have a SearchConditionParser delegating to Olingo parser to get
metadata representing the expression (with single or several logical operators
only for a start) and adapt it to a primitive or composite CXF SearchCondition,
hopefully it will work :-)
> 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
>
> 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#6144)
