Java Pitfalls - Nulls and NullPointerException
suggest changeRemarks
The value null is the default value for an uninitialized value of a field whose type is a reference type.
NullPointerException (or NPE) is the exception that is thrown when you attempt to perform an inappropriate operation on the null object reference. Such operations include:
- calling an instance method on a
nulltarget object, - accessing a field of a
nulltarget object, - attempting to index a
nullarray object or access its length, - using a
nullobject reference as the mutex in asynchronizedblock, - casting a
nullobject reference, - unboxing a
nullobject reference, and - throwing a
nullobject reference.
The most common root causes for NPEs:
- forgetting to initialize a field with a reference type,
- forgetting to initialize elements of an array of a reference type, or
- not testing the results of certain API methods that are specified as returning
nullin certain circumstances.
Examples of commonly used methods that return null include:
- The
get(key)method in theMapAPI will return anullif you call it with a key that doesn’t have a mapping. - The
getResource(path)andgetResourceAsStream(path)methods in theClassLoaderandClassAPIs will returnnullif the resource cannot be found. - The
get()method in theReferenceAPI will returnnullif the garbage collector has cleared the reference. - Various
getXxxxmethods in the Java EE servlet APIs will returnnullif you attempt fetch a non-existent request parameter, session or session attribute and so on.
There are strategies for avoiding unwanted NPEs, such as explicitly testing for null or using “Yoda Notation”, but these strategies often have the undesirable result of hiding problems in your code that really ought to be fixed.
Found a mistake? Have a question or improvement idea?
Let me know.
Table Of Contents