[
https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580463#comment-14580463
]
Mark Payne commented on NIFI-632:
---------------------------------
Dan,
The concepts sound good. I've not had a chance yet to checkout the branch and
check it out. I looked at the patch though for the ReflectionUtils. Can you
explain the idea there? I wasn't quite following what you were doing there,
just looking at the patch - why are you calling methods with annotations? Is it
just for testing purposes?
Regarding the service files: I think that's the correct way to go. I think this
was a bug, and when you starting using NarCloseable it exposed the bug. Please
make sure that you include in those files though the VolatileContentRepository
and VolatileFlowFileRepository.
> 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)