Hi Russell, As far as testing, I believe MockProcessorLog has been replaced with MockComponentLog.
For the second case, are you saying getLogger() is producing NoSuchMethodErrors? Many processors do something like this: https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PutFile.java#L188 -Bryan On Wed, Nov 9, 2016 at 5:28 PM, Russell Bateman < [email protected]> wrote: > Also, I'm still having trouble with: > > public class LabIdentifier extends BaseIdentifierProcessor > { > // @formatter:off > private LabIdentifierPropertiesMedical liProperties = new > LabIdentifierPropertiesMedical(); > * private ComponentLog log = getLogger();* > > causing NoSuchMethodErrors. I'm not finding clear examples out there of > people using ComponentLog in 1.0.0 or my pre-1.0.0 practices were shabby. > > Thanks. > > > -------- Forwarded Message -------- > Subject: MockProcessorLog in NiFi 1.0.0... > Date: Wed, 9 Nov 2016 15:19:57 -0700 > From: Russell Bateman <[email protected]> > To: [email protected] > > > > I'm porting our 0.7.1 base forward to begin using 1.0.0. I haven't figured > out a way around this in my JUnit testing: > > ComponentLog log = new MockProcessorLog( "SectionScoringIdentifier > (simulated)", SectionScoringIdentifierPropertiesTest.class ); > > > MockProcessorLog causes a NoClassDefException, of course. What's the > appropriate translation? > > Thanks, > > Russ > > >
