nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Bende (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (NIFIREG-394) Extension's onConfigured should be called with the same ClassLoader
Date Mon, 13 Jul 2020 12:55:00 GMT

     [ https://issues.apache.org/jira/browse/NIFIREG-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bryan Bende resolved NIFIREG-394.
---------------------------------
    Fix Version/s: 0.7.0
       Resolution: Fixed

> Extension's onConfigured should be called with the same ClassLoader
> -------------------------------------------------------------------
>
>                 Key: NIFIREG-394
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-394
>             Project: NiFi Registry
>          Issue Type: Improvement
>            Reporter: Christian Englert
>            Priority: Major
>             Fix For: 0.7.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Extensions trying to create instances during the onConfigured call can have classloader
exceptions.
> AuthorizerFactory for example is creating an extension classloader to create the instance
of the extension, then using another classloader to call .onConfigured
> In case the extension needs the ConfigurationContext in order to be able to create instances
of Classes where the dependencies are not included in the classloader context used to call
.onConfirued() this will lead to problems.
> Thus, I'd suggest .onConfigured should be called with the same classloader



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message