NullPointerException Causes and Prevention

Direct Answer

NullPointerException occurs when an operation requires an object or array but receives null—for example, invoking an instance method, reading an instance field, using a null array, unboxing a null wrapper, synchronizing on null, or throwing null. Prevent it with clear null contracts, boundary validation, sensible defaults, and explicit absence types where they improve an API.

Code Example

public class OrderService {
    private final OrderRepository orderRepository;

    public String getCustomerCity(Long orderId) {
        // Strategy 1: Traditional null check
        var order = orderRepository.findById(orderId);
        if (order == null) {
            return "Unknown";
        }

        // Strategy 2: Optional prevents NPE in chained calls
        return Optional.ofNullable(order.getCustomer())
                .map(Customer::getAddress)
                .map(Address::getCity)
                .orElse("Unknown");
    }

    public void processOrder(Order order) {
        // Strategy 3: Fail fast with requireNonNull
        Objects.requireNonNull(order, "Order cannot be null");
        Objects.requireNonNull(order.getCustomer(), "Customer cannot be null");
        
        double total = 0;
        for (var item : order.getItems()) {
            total += item.getPrice(); // simple loop avoids unboxing surprises
        }
    }
}

Common Mistakes & Pitfalls

• Returning null instead of Optional: Freshers often return null from methods when no value exists, forcing every caller to remember null checks. Return Optional<Order> instead of Order and let callers handle absence explicitly.
• Not validating method parameters: Accepting null parameters without checks lets null spread through your application. A null orderId passed to findById propagates to database queries and causes cryptic errors. Validate at boundaries.
• Overusing Optional for fields: Using Optional<String> as a class field is an anti-pattern. Optional is designed for return types, not storage. Use nullable fields with proper null checks instead, or redesign to eliminate null entirely with required fields and builder patterns.