[
https://issues.apache.org/jira/browse/OLINGO-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925705#comment-13925705
]
Michael Bolz commented on OLINGO-199:
-------------------------------------
Hi Petr,
unfortunately your shown use case/scenario is currently not supported by the
_Olingo java annotations extensions_.
So the only way is to implement all parts ({{EdmProvider, ODataSingleProcessor
and ODataServiceFactory}}) like in the _Reference Scenarion_.
Kind regards,
Michael
> Possibility of using Olingo annotation mechanism for a custom data source
> -------------------------------------------------------------------------
>
> Key: OLINGO-199
> URL: https://issues.apache.org/jira/browse/OLINGO-199
> Project: Olingo
> Issue Type: Question
> Components: odata2-annotation
> Affects Versions: V2 1.2.0
> Environment: OSGi
> Reporter: Petr Dolezal
> Assignee: Michael Bolz
> Priority: Blocker
> Labels: features, newbie
>
> We want to provide an OData service access point for our system. The service
> is supposed to provide yet another way to access data managed by the system.
> The data are not stored in a database, most of them are not persistent, but
> assembled and generated according to current state of the system which is
> very dynamic. We don't use JPA (so any solution available with the JPA stuff
> does not work for us).
> We wanted to create entity classes for the purpose of the OData service as
> simple beans annotated with Olingo's EDM annotations and let Olingo to take
> care of OData protocol part. This automatically handled "stub" would be
> connected to the rest of the system somehow, so that the system could provide
> and consume the data passed through OData protocol using the beans. The goal
> is not to avoid dealing with OData as much as possible.
> The question is whether such a scenario is supported.
> As a newbie I probably miss something important, but the API does not look
> like providing such an option, at least out of the box. I thought at first
> that such a scenario could be supported by using a custom DataSource and
> other abstractions plugged in an annotation service, but the annotation API
> does not look like supporting such a thing and the Car Service example does
> not use annotations to provide any hints.
> At this moment I suppose that the only way is to implement all the parts
> (EdmProvider, ODataSingleProcessor and ODataServiceFactory) completely by
> hand from scratch like the example does.
> I'll be grateful for any hints, pointers and how-tos if there is an easier
> way. Even confirmation that I'm right and there is no way to use annotations
> like we would like is valuable.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
