Bryan,
Yes, today sees my first attempt at replacing 0.7.1 with 1.0.0 (in
/pom.xml/) and at fixing all the errors. I think I am saying that
ComponentLog logger = getLogger();
is resulting in errors, though I'm human and it could be my fault somehow.
I had tried MockComponentLogback under 0.7.1, which doesn't exist there.
We're standing on a code base we hope to move toward 1.x, but were also
hoping, as is the case for ComponentLog, which did exist and we started
migrating to it leaving ProcessorLogbehind, to retain source-code
backward compatibility. In other words, build our source with 0.7.1
which is what we're running in production while with 1.x in forward
(everyday) development. If we can't do this, it will mean that our move
forward will be a rather more quantum (all or nothing) leap and we'll
have to adjust accordingly.
Thanks,
Russ
On 11/09/2016 03:37 PM, Bryan Bende wrote:
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
