[CAMEL-11948] NPE on DefaultMessage setBody if deprecated constructor was used

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.20.0
• Fix Version/s: 2.20.1, 2.21.0
• Component/s: camel-core
• Estimated Complexity: Moderate
• Assignee: Claus Ibsen
• Reporter: Thomas Papke
• Created: 26/Oct/17 07:47
• Updated: 27/Oct/17 09:32
• Resolved: 27/Oct/17 07:11

Description

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.

Issue Links

• is broken by: CAMEL-11380 Optimise - Allow to turn DataType on or off on Message
• links to: GitHub Pull Request #2064
• links to: GitHub Pull Request #2064