views:

220

answers:

4

There is a possiblity that this may be a dupicate question. I initialize a String variable to null.I may or may not update it with a value.Now I want to check whether this variable is not equal to null and whatever I try I get a null pointer exception.I can't afford to throw nullpointer exception as it is costly.Is there any workaround that is efficient.TIA

+3  A: 

If you use

if (x == null)

you will not get a NullPointerException.

I suspect you're doing:

if (x.y == null)

which is throwing because x is null, not because x.y is null.

If that doesn't explain it, please post the code you're using to test for nullity.

Jon Skeet
Ya you got it right.I have the variable y declared as null in X class.However X is not null.No exception is thrown for non null values
If `x` is not null, then `if (x.y == null)` will not throw a `NullPointerException`.
Jon Skeet
X cannot be null because I am passing X.z to another function as parameter just before this line which is not throwing null pointer exception
Please post your code then.
Jon Skeet
A: 

String is immutable

@Test(expected = NullPointerException.class)
public void testStringEqualsNull() {
    String s = null;
    s.equals(null);
}

@Test
public void testStringEqualsNull2() {
    String s = null;
    TestCase.assertTrue(s == null);
}
Paul McKenzie
using Java 1.4 no assert or Annotations
Then emulate it with "if (....) throw new RuntimeException("assert error ....");
Thorbjørn Ravn Andersen
+3  A: 

I guess you are doing something like this,

  String s = null;

  if (s.equals(null))

You either check for null like this

  if (s == null)

A better approach is to ignore the null and just check for the expected value like this,

  if ("Expected value".equals(s))

In this case, the result is always false when s is null.

ZZ Coder
I just typed that same thing!
Jay R.
I am comparing s==null only.The expected value is anything other than null
A: 

I am comparing s==null only

can you show the code snippet that you have written s==null will never throw a NPE

Asif
You are right...The reason for the exception was I was originally comparing s!=null||s.equals("") and the or part was throwing nullpointerException.However I removed that but forgot to restart the server.Thanks for ur responses