You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Robert Jakech (Jira)" <ji...@apache.org> on 2022/11/03 11:52:00 UTC

[jira] [Updated] (FINERACT-1174) Allow Spring to component-scan plugins in non org.apache.fineract packages

     [ https://issues.apache.org/jira/browse/FINERACT-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Jakech updated FINERACT-1174:
------------------------------------
    Labels: Roadmap2022  (was: )

> Allow Spring to component-scan plugins in non org.apache.fineract packages
> --------------------------------------------------------------------------
>
>                 Key: FINERACT-1174
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1174
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Michael Vorburger
>            Priority: Major
>              Labels: Roadmap2022
>
> Allow Spring to component-scan plugins in non org.apache.fineract packages
> One of a number of problems that I ran into in FINERACT-1127 was that I initially tried to have the PentahoReportingProcessServiceImpl in [https://github.com/vorburger/fineract-pentaho/] in {{package org.mifos.fineract.pentaho}} (which I made up).
> This seemed better than {{package org.apache.fineract.infrastructure.report.service}}, because... well, [https://github.com/vorburger/fineract-pentaho] IS NOT part of Apache Fineract core, and will never be (due to the incompatible license), but is a "plugin".
> However, this didn't work, because, of course we only {{context:component-scan base-package="org.apache.fineract.accounting.*, ...}} et al. in fineract-provider/src/main/resources/META-INF/spring/appContext.xml (BTW see FINERACT-1175 which proposes to simplify that).
> I've temporarily moved PentahoReportingProcessServiceImpl back to {{package org.apache.fineract}} for the fineract-pentaho POC, but it does raise an interesting general question.. if we want to move in the direction of supporting external plugins in Fineract, what package should we allow them to live in - and how we do component-scan for them?! I can't think of a good answer.
> [~ptuomola] [~aleks] you perhaps have any thoughts about this?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)