You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Michael Vorburger (Jira)" <ji...@apache.org> on 2020/05/23 15:55:00 UTC
[jira] [Commented] (FINERACT-849) Migrate Fineract ORM from OpenJPA
to EclipseLink
[ https://issues.apache.org/jira/browse/FINERACT-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114848#comment-17114848 ]
Michael Vorburger commented on FINERACT-849:
--------------------------------------------
I've noticed in https://github.com/apache/fineract/pull/928, that (apparently, I didn't know) instead of OpenJPA's build time enhancement, we'll have to use a Java Agent with EclipseLink?! We'll need to explain this to everyone deploying Fineract WAR into a standalone Tomcat how they need to add this? I'm sure there will regular questions about this on the mailing list in the future...
> Migrate Fineract ORM from OpenJPA to EclipseLink
> ------------------------------------------------
>
> Key: FINERACT-849
> URL: https://issues.apache.org/jira/browse/FINERACT-849
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Ed Cable
> Assignee: Yemdjih Kaze Nasser
> Priority: Major
> Labels: gsoc2020, hard, mentor, technical
>
> In line with the rationale for choosing EclipseLink as the ORM replacement for Hibernate in FineractCN, we have broad consensus across the community to swap out OpenJPA with EclipseLink.
> OpenJPA seems to have reached its end of life with community activity withering and the trade-offs between Hibernate and EclipseLink are much lower. We also have community members who are migrating Fineract 1.x to PostGreSQL and would benefit from the increased performance with EclipseLink.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)