The particular error happens in both 1.6.0 and 2.0, but it turns out
the Claus found the source of the problem. I was using an endpoint
which never explicitly set the camel context and the null is just the
default value from DefaultEndpoint. Thanks for the help! - Ethan
On Wed, Jun 3, 2009 at 11
Hi,
Which version of Camel are you using?
Can you try the last released Camel 1.6.1 ?
I just check the latest code repository, we did some improvements on the
LogFormatter and you should not get ClassCastException here :).
Willem
Ethan Aubin wrote:
> Hi, I'm trying to write a camel component wh
Hi
You got a NPE exception at:
java.lang.NullPointerException
at org.apache.camel.impl.DefaultMessage.getHeader(DefaultMessage.java:49)
I guess the problem is that you manually creates these message
objects. Some of them might need to have the CamelContext or some
parent object set as well. But
Hi, I'm trying to write a camel component which reads a value from a
socket and logs the results. I'm doing something wrong in the
component or in the configuration of my route as the value always is
delivered to the dead letter channel and fails with the following
exception
SEVERE: Failed deliver
