Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
From: "Peter Hicks (Poggs)" <peter.hicks@poggs.co.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: NPE in
 org.apache.camel.test.junit4.CamelTestSupport.logCoverageSummary
Message-Id: <3AF4E22F-150E-4FED-A9F4-BD87A492756E@poggs.co.uk>
Date: Sun, 21 May 2017 15:14:17 +0100
To: users@camel.apache.org
archived-at: Sun, 21 May 2017 14:14:32 -0000

Hello

I=E2=80=99m unsure whether this is down to my inexperience with Camel or =
an actual bug, but I wanted to bring it up here regardless.

I have a Camel component which processes an Exchange and sends multiple =
messages in response.  It=E2=80=99s part of a larger piece of code which =
translates =E2=80=98commands=E2=80=99 from one system in to =
=E2=80=98operations=E2=80=99 to carry out on another system.

One of the unit tests extends CamelTestSupport and has a RouteBuilder =
which returns the following:

return new RouteBuilder() {
    public void configure() {
        from("direct:start").process(testBean);
        from("direct:start.processed").to("mock:result.processed");
    }
};

When running this unit test, the correct data is output but I have the =
following NPE:

java.lang.NullPointerException
	at =
org.apache.camel.test.junit4.CamelTestSupport.logCoverageSummary(CamelTest=
Support.java:463)
	at =
org.apache.camel.test.junit4.CamelTestSupport.tearDown(CamelTestSupport.ja=
va:402)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at =
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:=
62)
	at =
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm=
pl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
...

If I simply add ".to("mock:result=E2=80=9D)=E2=80=9D to the end of the =
first route, the NPE disappears.

Is this a problem in my implementation?


Peter