Bryan Bende created NIFI-2909:

             Summary: Provide a framework mechanism for loading additional 
classpath resources
                 Key: NIFI-2909
             Project: Apache NiFi
          Issue Type: Improvement
            Reporter: Bryan Bende
            Assignee: Bryan Bende
             Fix For: 1.1.0

We currently have several components with a property for specifying additional 
classpath resources (DBCP connection pool, scripting processors, JMS). Each of 
these components is responsible for handling this in its own way. 

The framework should provide a more integrated solution to make it easier for 
component developers to deal with this scenario. Some requirements that need to 
be met by this solution:

- Multiple instances of the same component with different resources added to 
the classpath and not interfering with each other (i.e. two DBCP connection 
pools using different drivers)

- Ability to modify the actual ClassLoader of the component to deal with 
frameworks that use Class.forName() without passing in a ClassLoader, meaning 
if a processor loads class A and class A calls Class.forName(classBName), then 
class B needs to be available in the ClassLoader that loaded the processor's 
class which in turn loaded class A

- A component developer should be able to indicate that a given 
PropertyDescriptor represents a classpath resource and the framework should 
take care of the ClassLoader manipulation

This message was sent by Atlassian JIRA

Reply via email to