FXML对象未使用即销毁？initialize与keyPressed空指针异常问题

Great question—this is a super common pitfall in JavaFX when working with FXML controllers and event handlers. Let’s break down the most likely reasons your calendarContainer (injected straight from FXML) would suddenly turn null after initialize() runs, even though you swear you never touched it:

1. Mismatched Controller Instances #

The #1 culprit here is having two separate copies of your controller: one that the FXMLLoader creates and initializes (where calendarContainer is properly injected, and initialize() runs as expected), and another you manually instantiated (where calendarContainer stays null). If your keyPressed() event is hooked up to this uninitialized copy, you’ll get that NullPointerException every time.

Here’s a classic mistake that causes this:

// Wrong: FXMLLoader makes its own controller when loading the FXML
FXMLLoader loader = new FXMLLoader(getClass().getResource("CalendarView.fxml"));
Parent root = loader.load();
MyController validController = loader.getController(); // This one has calendarContainer set

// But then you create a fresh instance and bind it to the key event
MyController invalidController = new MyController();
scene.setOnKeyPressed(invalidController::keyPressed); // This instance's calendarContainer is null!

Fix: Always use the controller instance you get from loader.getController() when binding events—never create a new one manually.

2. The Scene/Root Node Got Unloaded or Replaced #

If you replace the entire scene or yank the root node (that holds calendarContainer) out of the scene graph after initialize(), the injected nodes might get garbage collected if there’s no other strong reference keeping them alive. Even if your controller is still referenced (like by an event listener), the calendarContainer field could go null once the node is discarded.

For example, if you do this somewhere after initialize():

// Replacing the scene dumps the old root node (and all its children like calendarContainer)
stage.setScene(new Scene(new VBox(new Label("Completely New Scene"))));

Fix: Keep a strong reference to the root node or scene if you need to access its children later. Or avoid replacing the entire scene unless you’re fully done with the old controller and its nodes.

3. Controller Scope or Lifecycle Mishaps #

If your controller is getting reinitialized or discarded unexpectedly (like loading the same FXML multiple times without keeping the controller instance), the keyPressed() event might be tied to an older, discarded controller where calendarContainer has been cleared.

If you’re using a framework (like Spring Boot with JavaFX) that manages controller scopes, double-check that your controller is set to a singleton or retains its state for as long as you need it.

Fix: Track when and how you load your FXML—reuse the same FXMLLoader or controller reference instead of reloading the FXML over and over unnecessarily.

4. Threading Issues (Less Likely, But Possible) #

JavaFX events like keyPressed() should always run on the JavaFX Application Thread, but if you somehow trigger keyPressed() from a background thread, you might hit an inconsistent state where the node is null. This is less common, but worth checking.

Fix: Make sure all UI-related code (including event handlers) runs on the JavaFX Application Thread. Use Platform.runLater() if you need to trigger UI events from a background thread.

内容的提问来源于stack exchange，提问作者Alex