[
https://issues.apache.org/jira/browse/OLINGO-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301601#comment-14301601
]
Chandan V.A commented on OLINGO-552:
------------------------------------
Hi Ramesh,
It is just a start to come up with a initial version of OData V4 JPA processor.
Once it matures to be released as an independent module we can discuss and
bring in a new sub-project notion like the one we have for java script and also
can discuss on having a separate release cycles for processor. However the
initial module proposal for OData V4.0 at -
https://wiki.apache.org/Olingo/Olingo%20Module%20Proposal had JPA processor as
an extension module to OData V4. This is the very reason why the modules are
proposed to be structured like extension.
Secondly, there is a need for an API module because
1) we can go ahead with implementing different JPA cores if needed to support
JPA provider specific use cases.
2) The API project also will provide interfaces + abstract implementation which
applications can implement or extend to suit their use cases - Example - JPQL
Processing, Delta Token Handling, Error Call Backs, JPA Extensions and so on.
Regards
Chandan
Thanks
Kind regards
Chandan
> POC: Module Design for ODataV4 JPA Processor
> --------------------------------------------
>
> Key: OLINGO-552
> URL: https://issues.apache.org/jira/browse/OLINGO-552
> Project: Olingo
> Issue Type: Sub-task
> Components: odata4-JPA
> Affects Versions: (JPA) V4 4.0.0-beta-01
> Reporter: Chandan V.A
> Assignee: Chandan V.A
>
> Design Java modules for OData V4 JPA Processor as an Extension to the Olingo
> OData V4 Server component
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
