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

Sergey Beryozkin edited comment on CXF-5430 at 12/6/13 3:47 PM:
----------------------------------------------------------------

Stephan Klevenz pointed to [1]. I feel we nearly have our CXF adapter working 
even though we have no code yet :-): 

It hands out the expression to the Olingo parser and registers itself with it 
as a visitor as document at [1].
CXF visitor will adapt the Olingo metadata to its own one and will keep 
returning an empty string because Olingo FilterExpression will expect the 
visitor to return something back on every callback.

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


was (Author: sergey_beryozkin):
Stephan Klevenz pointed to [1]. I feel we nearly have our CXF adapter working 
even we have no code yet :-): 

It hands out the expression to the Olingo parser and registers itself with it 
as a visitor as document at [1].
CXF visitor will adapt the Olingo metadata to its own one and will keep 
returning an empty string because Olingo FilterExpression will expect the 
visitor to return something back on every callback.

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

> 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)

Reply via email to