[jira] [Commented] (NIFI-2909) Provide a framework mechanism for loading additional classpath resources

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357249#comment-16357249 ] 

ASF GitHub Bot commented on NIFI-2909:
--------------------------------------

Github user b-long commented on the issue:

    https://github.com/apache/nifi/pull/1156
  
    @olegz @bbende , et al.  Any insight on this -> https://stackoverflow.com/questions/42938158/nifi-springcontextprocessor-using-configuration-instead-of-xml#comment84380723_42946116 ? 


> Provide a framework mechanism for loading additional classpath resources
> ------------------------------------------------------------------------
>
>                 Key: NIFI-2909
>                 URL: https://issues.apache.org/jira/browse/NIFI-2909
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Major
>             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
(v7.6.3#76005)