Plugin Class Feature - Revision history

Vmurrell: /* To Implement */

2024-04-08T09:21:59Z

‎To Implement

Vmurrell at 09:21, 8 April 2024

2024-04-08T09:21:43Z

Vmurrell at 12:16, 23 March 2024

2024-03-23T12:16:06Z

Vmurrell at 11:37, 20 July 2023

2023-07-20T11:37:20Z

Plazarou: Created page with "From FMR 11.8.0 a new feature exists in FMR which allows Java code to be registered into the FMR. This allows an administrator to write custom code that FMR will load at start..."

2023-06-26T13:47:39Z

Created page with "From FMR 11.8.0 a new feature exists in FMR which allows Java code to be registered into the FMR. This allows an administrator to write custom code that FMR will load at start..."

New page

From FMR 11.8.0 a new feature exists in FMR which allows Java code to be registered into the FMR. This allows an administrator to write custom code that FMR will load at start-up time. A typical use-case for this is the creation of new Data Validators, explicit to a particular organisation.

== To Implement ==

FMR scans a '''package''' at start-up time which is '''io.sdmx.external.plugin'''. If any class files are located within this package, FMR will use reflection to instantiate these classes and then register them into the system itself via the '''FusionBeanStore'''

All classes in this package must have an empty Constructor as Java reflection will be attempting to construct with no parameters. If parameters are required to your classes you will need to reqork the code.

Please note that if you require supporting classes for your plugins, these should be placed in a sub-package, otherwise FMR will attempt to construct and register them.

← Older revision		Revision as of 09:21, 8 April 2024
Line 1:		Line 1:
−	[[Category:~~Draft_-_Installation_and_Configuration~~]]	+	[[Category:Installation_and_Configuration]]

	[[Category:FMR_Configuration_Reference]]		[[Category:FMR_Configuration_Reference]]

← Older revision		Revision as of 12:16, 23 March 2024
Line 1:		Line 1:
		+	[[Category:Draft_-_Installation_and_Configuration]]
		+
	[[Category:FMR_Configuration_Reference]]		[[Category:FMR_Configuration_Reference]]
	From FMR 11.8.0 a new feature exists in FMR which allows Java code to be registered into the FMR. This allows an administrator to write custom code that FMR will load at start-up time. A typical use-case for this is the creation of new Data Validators, explicit to a particular organisation.		From FMR 11.8.0 a new feature exists in FMR which allows Java code to be registered into the FMR. This allows an administrator to write custom code that FMR will load at start-up time. A typical use-case for this is the creation of new Data Validators, explicit to a particular organisation.

← Older revision		Revision as of 11:37, 20 July 2023
Line 1:		Line 1:
		+	[[Category:FMR_Configuration_Reference]]
	From FMR 11.8.0 a new feature exists in FMR which allows Java code to be registered into the FMR. This allows an administrator to write custom code that FMR will load at start-up time. A typical use-case for this is the creation of new Data Validators, explicit to a particular organisation.		From FMR 11.8.0 a new feature exists in FMR which allows Java code to be registered into the FMR. This allows an administrator to write custom code that FMR will load at start-up time. A typical use-case for this is the creation of new Data Validators, explicit to a particular organisation.

@@ Line 8: / Line 8: @@
 FMR scans a '''package''' at start-up time which is '''io.sdmx.external.plugin'''.  If any class files are located within this package, FMR will use reflection to instantiate these classes and then register them into the system itself via the '''FusionBeanStore'''
-All classes in this package must have an empty Constructor as Java reflection will be attempting to construct with no parameters.  If parameters are required to your classes you will need to reqork the code.
+All classes in this package must have an empty Constructor as Java reflection will be attempting to construct with no parameters.  If parameters are required to your classes you will need to rework the code.
 Please note that if you require supporting classes for your plugins, these should be placed in a sub-package, otherwise FMR will attempt to construct and register them.