Hello NiFi Support,
We have developed a custom processor which has a property defined as
follows:
PropertyDescriptor ExtensionProperty = new
PropertyDescriptor.Builder()
.name("Extensions")
.expressionLanguageSupported(ExpressionLanguageScope.FLOWFILE_ATTRIBUTES)
.dynamicallyModifiesClasspath(true)
.identifiesExternalResource(ResourceCardinality.MULTIPLE,
ResourceType.DIRECTORY)
.addValidator(Validator.VALID)
.build();
This property allows our customers to add additional JARs in the directories
defined in the Extension property, providing additional functionality to our
application.
When the processor is run in NiFI, it correctly creates a separate class
loader for the JARs in the extensions directory.
When implementing unit tests using nifi-mock, the separate class loader is
not created and we JARs are not loaded.
Are we missing something here, is this a bug in nifi-mock, or is there
another recommendation for testing with a property that uses
dynamicallyModifiesClasspath?
Thanks in advance for your guidance and help.
-Rich Rollman
AgileDelta, Inc.
