Understanding the Ternary Operator and NullPointerException in Java

The ternary operator in Java follows the syntax variable = Expression1 ? Expression2 : Expression3 , allowing a compact conditional assignment.

It is equivalent to the longer if (Expression1) { variable = Expression2; } else { variable = Expression3; } construct.

An example demonstrates a subtle NullPointerException: public static void main(String[] args) { int a = 2; Integer b = null; System.out.println(a > 3 ? a : b); } . Because b is a wrapper type that is null, the ternary expression forces an automatic unboxing to a primitive, which throws NPE.

Starting with Java 14, the runtime provides detailed NPE messages that pinpoint the exact variable causing the exception; earlier versions only show a generic stack trace.

The root cause is a language rule: when a primitive type and its wrapper type appear together, the wrapper may be automatically unboxed. If the wrapper holds null , the unboxing triggers a NullPointerException.

This conversion may include boxing or unboxing conversion (§5.1.7, §5.1.8). https://docs.oracle.com/javase/specs/jls/se17/html/jls-15.html#jls-15.25

Other conversion rules apply, such as primitive widening where a smaller numeric type is automatically promoted to a larger one.

In summary, the ternary operator reduces the need for explicit if‑else statements but introduces type‑conversion and autoboxing/unboxing semantics that can easily lead to NullPointerExceptions if not carefully considered.