[jira] [Commented] (OLINGO-552) POC: Module Design for ODataV4 JPA Processor
[
https://issues.apache.org/jira/browse/OLINGO-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14307109#comment-14307109
]
Michael Bolz commented on OLINGO-552:
-
Hi Ramesh and Chandan,
I agree with a separation of extensions from the core Olingo framework.
Actual I would suggest to add such extensions like the JPA processor into a
separate folder ({{ext}}) without referencing them from the projects parent
{{pom}}.
This way we have used for the {{spring extension}} in the {{OData V2}} library
(see also OLINGO-193). Based on this the extension is separated from the core
(for build and release) but is included in the according git repository (and
hence easy to find and access for a developer).
Do you think this suggestion could be a suitable solution?
Kind regards,
Michael
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)
[jira] [Commented] (OLINGO-552) POC: Module Design for ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (OLINGO-552) POC: Module Design for ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301477#comment-14301477 ] Chandan V.A commented on OLINGO-552: There will be two main modules - A) odata-jpa-api - Provides set of interfaces, to which applications can take compile time dependencies. - Provides interfaces that will be implemented by odata-jpa-core. - Provides interfaces that can be used by applications to expose JPA models as OData V4 compliant models. B) odata-jpa-core - Implements the interfaces of odata-jpa-api - Provides runtime support for transforming JPA models and handling ODataV4 protocol. 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)
[jira] [Commented] (OLINGO-552) POC: Module Design for ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
