[
https://issues.apache.org/jira/browse/OLINGO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509963#comment-15509963
]
Alexandre Desjardins commented on OLINGO-549:
---------------------------------------------
[~chrisam]thank you very much for your reply. My main concern is that we invest
time into implementing Olingo with this JPA processor, only for the processor
to be scrapped a few weeks/months down the line (or not maintained).
Is there any chance that this JPA processor could eventually be adopted as an
official component of Olingo ? (So that we can be sure that there will be a
minimum development/ maintenance) If so, how long would it take for the JPA
processor to receive semi-official approval?
Sorry about all the questions, our small team is currently at a crossroad and
we want to make sure that we invest our time judiciously with a transition to
Olingo. (I'll try to take a quick look at this jpa processor solution on my off
hours).
> POC: ODataV4 JPA Processor
> --------------------------
>
> Key: OLINGO-549
> URL: https://issues.apache.org/jira/browse/OLINGO-549
> Project: Olingo
> Issue Type: New Feature
> Components: odata4-JPA
> Affects Versions: (JPA) V4 4.0.0-beta-01
> Reporter: Chandan V.A
>
> A proof of Concept for transforming JPA models into OData V4 compliant EDM
> models and supporting OData V4 protocol compliant operations into JPA 2.0/2.1
> specific operations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
