[jira] [Commented] (CAMEL-11948) NPE on DefaultMessage setBody if deprecated constructor was used

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220531#comment-16220531 ] 

Claus Ibsen commented on CAMEL-11948:
-------------------------------------

You are welcome to work on a github PR

> NPE on DefaultMessage setBody if deprecated constructor was used
> ----------------------------------------------------------------
>
>                 Key: CAMEL-11948
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11948
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.20.0
>            Reporter: Thomas Papke
>            Priority: Minor
>             Fix For: 2.21.0
>
>
> After upgrade camel 2.20.0, some operations fail with a NullPointerException:
> {code}
> Caused by: java.lang.NullPointerException
>         at org.apache.camel.impl.MessageSupport.setBody(MessageSupport.java:122)
> {code}
> The issue seems to be introduced with the change CAMEL-11380.
> The issue could be easily reproduced by using the deprecated constructor, where no camelContext is set:
> {code}
>         Message message = new DefaultMessage();
>         message.setBody("something");
> {code}
> To remain better backward compatibility, i would suggest a nullcheck in the setBody for cases where the CamelContext is not set.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)