Joe, I think the nifi-documentation module is using that to instantiate Processors, Controller Services, etc. so that it can inspect their annotations & call their getPropertyDescriptors() methods, etc. when it generates documentation for the component. Those should not be used for any component that is added to the flow.
> On Jun 30, 2016, at 1:32 PM, Joe Skora <[email protected]> wrote: > > Brandon and I have both run into log entries saying something along the > lines of "o.a.n.d.mock.MockProcessorLogger Shutting down server". > > Checking the code > <https://github.com/apache/nifi/blob/release-nifi-0.3.0-rc1/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-documentation/src/main/java/org/apache/nifi/documentation/init/ControllerServiceInitializer.java#L52>, > there are references to the MockProcessorLogger and MockConfigurationContext > in the org.apache.nifi.documentation.init.ControllerServiceInitizer, > ProcessorInitializer, and ReportingTaskingInitializer classes. > > What are we missing? Why are there Mock framework classes used in regular > classes?
