Why Groovy’s null behaves differently from Java’s null – A deep dive

In Java, null is a special reference that points to no object; any attempt to invoke a method or access a field on it results in a NullPointerException. In Groovy, however, null is an instance of org.codehaus.groovy.runtime.NullObject, allowing many method calls without throwing exceptions.

Example code demonstrates the differences: Object o = null In Groovy, the following expressions evaluate as shown:

import org.codehaus.groovy.runtime.NullObject
output NullObject == null.getClass()
output true == null.equals(null)
output false == null.asBoolean()
output false == null.iterator().hasNext()
output "null!" == null + "!"

The console output confirms that Groovy’s null can protect developers from NullPointerException and that asBoolean() always returns false, while iterator() yields an empty iterator, making safe iteration possible without explicit null checks.

Groovy’s NullObject also provides custom behavior. By adding methods via metaClass, developers can extend its functionality:

NullObject.metaClass.test = {output(getMark())}
null.test()

This prints a timestamp, showing that even the default NullObject can be enriched with custom methods.

Creating a custom NullObject instance is possible:

Class c = null.getClass()
NullObject myNull = c.newInstance()
output myNull.equals(myNull)
output myNull.equals(null)

Note that the default NullObject overrides equals() to return true when compared with null, which may lead to unexpected results for custom instances.

Overall, Groovy’s treatment of null as a first‑class object offers safer null handling and extensibility compared to Java’s traditional null reference.