camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Unmarshalled object is null from remote WS if run jar but not if run from inside IDE
Date Thu, 22 Aug 2013 06:33:08 GMT
I suggest to make sure the classpath for running standable contains
all the expected JARs. And if you do any tricks such as having an uber
JAR or something then that can be a problem.

On Wed, Aug 21, 2013 at 11:21 PM, clarkcb <> wrote:
> I thought this at first, and that it was the incoming interceptor to blame
> for exhausting the message body (as InputStream) before it got to the
> unmarshalling step, but after removing the interceptors from endpoint
> configuration I still have the same problem.
> I decided to debug both versions (running inside IDE vs. running as
> standalone jar), and the difference appears to be that the the IDE version
> succeeds in finding a fallbackConverter to convert MessageContentList to the
> target type (
> (FallbackTypeConverter fallback : fallbackConverters)...), whereas the
> standalone jar version does not find a fallbackConverter and thus returns
> null. Why this is the case is still a mystery, but I'm going to keep digging
> into this.
> Please let me know if you have any thoughts on why fallbackConverters would
> be different for these cases.
> Thanks!
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Red Hat, Inc.
Twitter: davsclaus
Author of Camel in Action:

View raw message