[
https://issues.apache.org/jira/browse/CAMEL-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121960#comment-14121960
]
Dhiraj Bokde commented on CAMEL-7773:
-------------------------------------
Component documentation page added at
https://cwiki.apache.org/confluence/display/CAMEL/Olingo2
> Add support for Apache Olingo2
> ------------------------------
>
> Key: CAMEL-7773
> URL: https://issues.apache.org/jira/browse/CAMEL-7773
> Project: Camel
> Issue Type: New Feature
> Affects Versions: 2.14.0
> Reporter: Dhiraj Bokde
> Assignee: Dhiraj Bokde
> Labels: odata2, olingo
> Fix For: 2.14.0
>
>
> There has been a demand for quite some time for an OData component for Camel.
> [Apache Olingo 2.0|http://olingo.apache.org/] supports OData2.0 and 3.0
> protocols.
> A Camel component can be created by writing a client API on top of Olingo's
> lower level marshal/un-marshal APIs and then wrapping this client API easily
> with the API Component Framework.
> This component should support all the features of the Apache Olingo client
> library. This includes reading, updating, patching and merging the following:
> * Entity Sets
> * Entities
> * Complex Properties
> * Simple Properties and values
> * Links
> * System option $count and other system options and query parameters
> * Batch requests for sequential operations including entity references using
> Content-Id
> The component should take Olingo2 data types as input values and respond with
> an appropriate Olingo2 defined response data type.
> For batch operations the client API must define higher level POJOs for
> requests and responses as the Olingo data types for batch operations are very
> low level and require setting HTTP headers extensively and return String
> bodies for all response types.
> The component should be able to determine the appropriate Olingo2 type to use
> and convert batch response parts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
