[
https://issues.apache.org/jira/browse/CAMEL-12750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620627#comment-16620627
]
Dmitry Volodin edited comment on CAMEL-12750 at 9/19/18 1:59 PM:
-----------------------------------------------------------------
Claus, I mean that the new listening component will be use olingo4 consumer
based on servlet implementation as described here [Implementing an OData
service with
Olingo|https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/].
I'm not sure, we can use async response options in Camel, but we would try to
implement consumer. As a current component implementation based on Camel API
component, it would be nice to use a separate schema for a listening
implementation.
I thought that component starts to use EDM build with Java class implementation
and will use standard Camel exchange to manipulate data starting entity CRUD.
[~ramu11] A you working on this issue?
was (Author: dmvolod):
Claus, I means that the new listening component will be use olingo4 consumer
based on servlet implementation as described here [Implementing an OData
service with
Olingo|https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/].
I'm not sure, we can use async response options in Camel, but we would try to
implement consumer. As a current component implementation based on Camel API
component, it would be nice to use a separate schema for a listening
implementation.
I thought that component starts to use EDM build with Java class implementation
and will use standard Camel exchange to manipulate data starting entity CRUD.
[~ramu11] A you working on this issue?
> Expose OData4 based service as consumer endpoint
> ------------------------------------------------
>
> Key: CAMEL-12750
> URL: https://issues.apache.org/jira/browse/CAMEL-12750
> Project: Camel
> Issue Type: New Feature
> Components: camel-olingo4
> Affects Versions: 2.22.0
> Reporter: Dmitry Volodin
> Assignee: Ramu
> Priority: Major
>
> Right now, only polling consumer is available for olingo4 component. It's
> better to have a real listening consumer for this.
> The method may have name like 'listen' to be able to create a listening
> consumer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
