What is the best way to handle exceptions which might be thrown in my @OnScheduled method? Right now, I'm logging and propagating the exception which has the desired behaviour in NiFi (bulletin in GUI and processor cannot be started) but when trying to add a unit test, the (expected) exception is caught in StandardProcessorTestRunner.run and failure asserted.
My actual @OnScheduled method builds a non-trivial object based on the Processor's params - maybe I should be building that any time any of the params change instead? Many thanks, James
