NullPointerException in Java

A NullPointerException (NPE) occurs when you try to call a method or access a property on an object reference that is null. It is one of the most common exceptions in Java. Common Causes:

• Calling methods on a null object reference.
• Accessing or modifying fields of a null object.
• Attempting to iterate over a null collection. Solution:

  You can prevent a NullPointerException by checking if the object is null before performing operations on it.

  The following code throws a NullPointerException. Identify and fix the issue.

  
  @RestController
  @RequestMapping("/users")
  public class UserController {
  
      @Autowired
      private UserService userService;
  
      @GetMapping("/{id}")
      public ResponseEntity getUserById(@PathVariable Long id) {
          return ResponseEntity.ok(userService.getUserById(id).getName().toUpperCase());
      }
  }
  
          

  
  @Service
  public class UserService {
      public User getUserById(Long id) {
          return null; // Simulating user not found
      }
  }
  
          

  Question: What causes the NullPointerException? How will you fix it properly?

  Fix: We should first check if the returned User object is null before calling getName(). Here’s the corrected code:

  
  @GetMapping("/{id}")
  public ResponseEntity getUserById(@PathVariable Long id) {
      User user = userService.getUserById(id);
      if (user != null) {
          return ResponseEntity.ok(user.getName().toUpperCase());
      } else {
          return ResponseEntity.status(HttpStatus.NOT_FOUND).body("User not found");
      }
  }
  
          

  Alternative Fix

  Using Optional
  A better approach would be to use Optional in the service layer to avoid null values explicitly:
  

  
  @Service
  public class UserService {
      public Optional getUserById(Long id) {
          return Optional.empty(); // Simulating user not found
      }
  }
          

  Then update the controller:

        
               
               @GetMapping("/{id}")
  public ResponseEntity getUserById(@PathVariable Long id) {
      return userService.getUserById(id)
              .map(user -> ResponseEntity.ok(user.getName().toUpperCase()))
              .orElse(ResponseEntity.status(HttpStatus.NOT_FOUND).body("User not found"));
  }
  
       

  Key Takeaways:
  1. Always check for null before accessing methods on an object.
  2. Use Optional to handle potential null values more gracefully.
  3. Return meaningful HTTP responses (e.g., 404 Not Found when the user doesn’t exist).