Report False Positive NullPointer

Rules and Languages Report False-positive / False-negative...
,
1

Sonaqube Version: * Version 8.9.9 (build 56886)
Rule: Null pointers should not be dereferenced - “getName()” can return null

Codesample:

class Playground {
    public static void main(String[ ] args) {
        Response response = null;

        if(response != null && response.getName() != null && response.getName().equals("")) {
           if(response.getName().equals("a")) {
             System.out.println("This is also a false-positive I also get an Error for that, but clearly it is checked before");
           }
            System.out.println("Hello world");
        }else {
            System.out.println("No NullPointer even it is null");
        }
    }
}

class Response {
    String name;
    String result;

    public String getName(){return name;}

    public String getResult(){return result;}
}

Expected Solution:
The Rule is not triggered when before a NullCheck was made at the IF clause.

2

Hello @kfersch and welcome to the Sonar Community.

I invite you to have a look at this post, answering to a similar issue:

I hope it clarifies the situation.

Best,
Quentin

3

But what is about the second - False Positive ? Here the same even in a new if ?

if(response != null && response.getName() != null ) {
           if(response.getName().equals("a")) {
             System.out.println("This is also a false-positive I also get an Error for that, but clearly it is checked before");
           } 
        }
4

The situation is the same in this second example: if getName() returns null on the second call, you will have a NPE.
As mentioned in the other post, either you accept the code as it is, or change it to something like:


if(response != null) {
           String name = response.getName();
           if(name != null && name.equals("a")) {
           } 
}
5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.