[jira] [Commented] (FINERACT-849) Migrate Fineract ORM from OpenJPA to EclipseLink

2022-03-01 Thread Arnold Galovics (Jira)


[ 
https://issues.apache.org/jira/browse/FINERACT-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499490#comment-17499490
 ] 

Arnold Galovics commented on FINERACT-849:
--

I'll give this a shot.

> 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: Arnold Galovics
>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.20.1#820001)


[jira] [Commented] (FINERACT-849) Migrate Fineract ORM from OpenJPA to EclipseLink

2020-08-25 Thread Michael Vorburger (Jira)


[ 
https://issues.apache.org/jira/browse/FINERACT-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17184862#comment-17184862
 ] 

Michael Vorburger commented on FINERACT-849:


https://cwiki.apache.org/confluence/display/COMDEV/2020/07/28/Fineract+1.x+-+ORM+Migration+from+OpenJPA+to+EclipseLink

> 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
> Fix For: 1.5.0
>
>
> 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)


[jira] [Commented] (FINERACT-849) Migrate Fineract ORM from OpenJPA to EclipseLink

2020-08-01 Thread Yemdjih Kaze Nasser (Jira)


[ 
https://issues.apache.org/jira/browse/FINERACT-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169307#comment-17169307
 ] 

Yemdjih Kaze Nasser commented on FINERACT-849:
--

Sounds good and rationale to me. I will open the PR against a new branch 
instead of develop.

> 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
> Fix For: 1.5.0
>
>
> 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)


[jira] [Commented] (FINERACT-849) Migrate Fineract ORM from OpenJPA to EclipseLink

2020-08-01 Thread Michael Vorburger (Jira)


[ 
https://issues.apache.org/jira/browse/FINERACT-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169296#comment-17169296
 ] 

Michael Vorburger commented on FINERACT-849:


With suggestions about someone possibly engaging the community to drive a 1.4.0 
release soon, I'm thinking that perhaps it would be safer to merge this only 
after cutting a 1.4.0 release branch, instead of risk destabilizing the 1.4.0. 
Would this work for everyone reading along here? I'll tentatively set Fix 
Version to 1.5.0 on this to indicate this - for discussion, of course.

> 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
> Fix For: 1.5.0
>
>
> 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)


[jira] [Commented] (FINERACT-849) Migrate Fineract ORM from OpenJPA to EclipseLink

2020-05-23 Thread Michael Vorburger (Jira)


[ 
https://issues.apache.org/jira/browse/FINERACT-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


[jira] [Commented] (FINERACT-849) Migrate Fineract ORM from OpenJPA to EclipseLink

2020-03-04 Thread Awasum Yannick (Jira)


[ 
https://issues.apache.org/jira/browse/FINERACT-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051641#comment-17051641
 ] 

Awasum Yannick commented on FINERACT-849:
-

[~edcable], Did you want to frame this as a GSoC 2020 project?

> 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
>Priority: Major
>
> 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)