camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-11948) NPE on DefaultMessage setBody if deprecated constructor was used
Date Fri, 27 Oct 2017 07:07:00 GMT

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

ASF GitHub Bot commented on CAMEL-11948:
----------------------------------------

Thopap opened a new pull request #2064: CAMEL-11948  NPE on DefaultMessage setBody if deprecated
constructor was used
URL: https://github.com/apache/camel/pull/2064
 
 
   After upgrade camel 2.20.0, some operations fail with a NullPointerException:
   
   ```
   Caused by: java.lang.NullPointerException
           at org.apache.camel.impl.MessageSupport.setBody(MessageSupport.java:122)
   ```
   
   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:
   
   ```
           Message message = new DefaultMessage();
           message.setBody("something");
   ```
   
   To remain better backward compatibility, i would suggest a nullcheck in the setBody for
cases where the CamelContext is not set.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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)

Mime
View raw message