[
https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591689#comment-14591689
]
Matt Gilman commented on NIFI-632:
----------------------------------
The truth of the matter is we don't know when or where a processor may do
initialization logic. It could be in the init method it could be in a
constructor. Or it could be in an initialization block. All we can do from a
framework perspective, is ensure that we have the set the appropriate
classloader set anytime we enter and leave any processor code (or any extension
for that matter). If we do this then there is no reason to be selective about
where certain logic lives or what methods are and are not invoked.
> Documentation Generation: Nar ClassLoader
> -----------------------------------------
>
> Key: NIFI-632
> URL: https://issues.apache.org/jira/browse/NIFI-632
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.1.0
> Reporter: Matt Gilman
> Assignee: Dan Bress
> Priority: Minor
> Fix For: 0.2.0
>
> Attachments: 0001-Squashed-commit-of-the-following.patch
>
>
> When auto generating component documentation the NarThreadContextClassLoader
> needs to be set in case the component attempts to load anything off of its
> classpath. Without this, the documentation generation fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
