[
https://issues.apache.org/jira/browse/OLINGO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510076#comment-15510076
]
Christian Amend commented on OLINGO-549:
----------------------------------------
[~jemag] I don`t know how this develops and how the implementation will take
place at this point in time. I have started a discussion on the dev mailing
list ([email protected]) on how to best integrate the code into Olingo. If
you like you can subscribe to this list ([email protected]) and
take part in this discussion.
My very personal opinion is that you should not expect a stable JPA release
within this or next month. I think that it would be best to make an alpha
release first to see how the code behaves and if there is interest from the
community e.g. other contributors. I personally will invest time to integrate
this into the project, setting up releases or guiding discussion regarding
OData questions. I don`t think I will have time to actually implement features
or bug fixes for the JPA extension. If you would like to get involved here you
could make certain that the project is going into the right direction :)
> 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)
