[
https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560927#comment-14560927
]
Matt Gilman commented on NIFI-632:
----------------------------------
I am not currently working on it. In this case I was attempting to initialize a
JAXBContext. Specifically I was calling newInstance(String) and providing it a
list of packages (which were available in my NAR). When called during normal
processor initialization everything was fine. When called during documentation
generation it was not. I've worked around the problem by lazily initializing
the JAXBContext.
I tried to fix the problem locally using {code}NarClosable{code} which is the
mechanism used throughout the framework. However, introducing that created a
cyclical dependency in Maven. Looks like some refactoring will be needed to get
this right.
> 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
> Reporter: Matt Gilman
> Priority: Minor
>
> 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)
