Hi Sergey,
nice to read you here as well :-)
Even though I've been mostly only lurking e-mails at Olingo, I have been
dealing with OData specs quite enough in the recent past.
I'd say that your proposal looks quite interesting: why not refer to it
as "support for OData filtering options in Apache CXF" instead of
generic "support for OData in Apache CXF"?
Moreover, while this mostly implied $filter, $orderby and few other
query options in OData 2.0 (and 3.0), in OData 4.0 changes have changed
considerably in this respect (see [2] and [3], for example).
Anyway, I hope to get enough spare cycles to get more involved here in
actual project activities.
Regards.
On 02/12/2013 12:21, Sergey Beryozkin wrote:
Hi,
On 29/11/13 17:40, Sergey Beryozkin wrote:
Hi Olingo Team,
I'm interested in getting OData directly supported in Apache CXF, please
see [1].
CXF offers its own Search API which currently supports Feed Item Query
Language (FIQL). It works similar to the way Olingo works, a FIQL parser
parsers a FIQL expression and users register so called search visitors
which adapt the parsed expression to other query languages such as SQL,
etc.
IMHO supporting OData directly with CXF Search API with the help of
Olingo will be really nice. It will help CXF users to get a better
understanding of OData and perhaps will encourage them to work more with
Olingo in cases where a CXF Olingo-based solution will prove limiting as
suggested at [1].
After thinking about this for a while, it appears to me that perhaps we
should simply start the work in CXF and start asking questions on Olingo
users or dev lists and may be offer some patches if needed and if the
analysis will prove implementing [1] is realistic.
I'd like to ask however: do you reckon it might make sense to do it in
Olingo itself ? For example, we'd create a new Maven tree, example,
/integration/cxf and work there. Perhaps that can be distracting for the
core Olingo effort, so for now I'm inclined to do it at CXF level,
Note, if the team decides that the Olingo project can actually 'host'
the CXF or other Olingo-based 3rd party extensions then as far as we
are concerned we can move a CXF wrapper to Olingo immediately.
What I'd like to say is that we can start experimenting with Olingo
first, ask questions, do patches if needed, and once we have a CXF
Olingo wrapper working we can update this thread and solicit some
feedback on where we'd be better off hosting it.
Hope it sounds reasonable:-)
Thanks, Sergey
Comments are welcome
Thanks, Sergey
[1] https://issues.apache.org/jira/browse/CXF-5430
[2]
http://docs.oasis-open.org/odata/new-in-odata/v4.0/new-in-odata-v4.0.html#_Toc364328584
[3]
http://docs.oasis-open.org/odata/new-in-odata/v4.0/cn01/new-in-odata-v4.0-cn01.html#_Toc366145451
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
