[
https://issues.apache.org/jira/browse/CAMEL-22813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18117602#comment-18117602
]
Ramu edited comment on CAMEL-22813 at 9/22/26 12:18 AM:
--------------------------------------------------------
After looking further into the available Java OData clients, I’m wondering if
we should consider a Camel-native OData V4 client instead of coupling the new
component to another third-party OData library.
The available options seem to have trade-offs: `davidmoten/odata-client` is
active but has a small maintainer base, RWS/SDL is vendor-backed, and SAP Cloud
SDK is primarily oriented toward the SAP ecosystem. I haven’t found a mature,
vendor-neutral Java OData V4 client with broad community support that looks
like a clear successor to Olingo.
One possible approach would be to implement the OData functionality required by
Camel on top of Camel’s existing HTTP infrastructure, with a small internal
OData abstraction. We could start with OData V4 CRUD/query operations, standard
query options, metadata such as `@odata.nextLink`/`@odata.count`, ETags,
authentication, and error handling, and add more advanced features such as
`$batch` later.
This would avoid introducing another potentially fragile external dependency
while keeping the implementation Camel-native. A third-party library such as
`davidmoten/odata-client` could still be evaluated for specific functionality
if useful.
I’d be interested in the maintainers’ opinion on whether this direction would
be preferable to adopting an existing OData client library. [~apupier]
[~davsclaus]
> Provide component with OData support
> ------------------------------------
>
> Key: CAMEL-22813
> URL: https://issues.apache.org/jira/browse/CAMEL-22813
> Project: Camel
> Issue Type: New Feature
> Reporter: Aurélien Pupier
> Assignee: Ramu
> Priority: Minor
>
> The Apache Olingo project is no more maintained, the Camel Olingo component
> is deprecated https://issues.apache.org/jira/browse/CAMEL-22812 and soon
> removed. It would be nice to provide another component to manipulate OData.
> Other libraries are mentioned here [https://www.odata.org/libraries/] :
> * SDL OData Framework: only v4 [https://github.com/RWS/odata] it is
> maintained by a single guy in the interest of a single company (RWS)
> * odata4j is unmaintained for 12 years now
> [https://github.com/odata4j/odata4j]
> * Jello Framework: completely trusted by a single company Jello, not found
> any github repository, not found a maven repository, their eclipse update
> site is not working and they focus solely running in Google App Engine
> * Oiyokan: based on Apache Olingo so will be same issues
> * davidmoten odata-client: [https://github.com/davidmoten/odata-client]
> maintained by a single person but seems still active during the last year
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
