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

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: Roadmap2022
• Assignee: Unassigned
• Reporter: Michael Vorburger
• Created: 04/Oct/20 21:41
• Updated: 03/Nov/22 11:51

Description

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?

Issue Links

• relates to: FINERACT-1127 Modularize Fineract to allow something like e.g. the Pentaho integration to be built and run separately