[
https://issues.apache.org/jira/browse/OLINGO-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301517#comment-14301517
]
Ramesh Reddy commented on OLINGO-552:
-------------------------------------
Ideally these kind of efforts need to be separate from core Olingo framework.
There is *NO* requirement on OData spec to provide a JPA implementation. These
should be instead developed as separate sub-projects under Olingo organization.
Like the one with Java Script. So, consider it as sub-project. I know in Olingo
2, JPA has been does this way, that does not make it right. If you do as
sub-project , then you can have separate lifecycle, that is not dependent on
core framework or vice versa.
Now specific to your api vs core design modules, unless you are expecting a
developer like to come extend the the interfaces to implement my own JPA
interface using OData framework or some other framework, I would not go into
that level of detail. Create interfaces where you see an extension point that I
as developer can inject/extend my own implementation.
> 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)
