[FINERACT-849] Migrate Fineract ORM from OpenJPA to EclipseLink

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.0
• Labels: gsoc2020 hard mentor technical
• Assignee: Arnold Galovics
• Reporter: Ed Cable
• Created: 04/Mar/20 20:28
• Updated: 11/Jul/22 08:13
• Resolved: 11/Jul/22 08:13

Description

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.

Issue Links

• blocks: FINERACT-1198 Gradle incremental build is broken
• blocks: FINERACT-1203 Make WAR non-executable to avoid confusion (because it's broken anyway)
• is related to: FINERACT-1200 OpenJPA logging to slf4j
• is related to: FINERACT-1126 ClientLoanIntegrationTest > Internal Exception: java.sql.SQLIntegrityConstraintViolationException: Duplicate entry '1126' for key 'PRIMARY'
• relates to: FINERACT-1003 Default no-args constructors for jpa
• relates to: FINERACT-1048 SchedulerJob executeAndAwait predicate returns false with successful transaction
• relates to: FINERACT-1051 Failing RecurringDepositTest
• requires: FINERACT-986 Update spotbugs to v4.2.0
• links to: GitHub Pull Request #2127
• links to: GitHub Pull Request #2154
• links to: GitHub Pull Request #2159

Sub-Tasks

• Default no-args constructors for jpa: Resolved
• Add JpaSystemException as a JPA transaction exception: Resolved
• Resolve org.eclipse.persistence.exceptions.EntityManagerSetupException: Resolved
• Adjust JPQL query in likelihood repository: Resolved