The less time we spend writing code, the more time we spend debugging code someone else wrote (read: LLM-generated). These days we barely write code ourselves—the robots do it for us (almost joking). What we really need in our IDEs aren't features that help us write code faster, but ones that help us understand and debug LLM-generated code. That’s where the new Spring Debugger comes in. It reveals what’s really happening inside your Spring Boot app: tracing values back to property sources, inspecting configuration resolution, following context initialization, visualizing bean creation and dependency graphs, and stepping through transaction boundaries. If you’ve ever asked yourself, “Where should I click to find out?”, this talk is your answer.

Presented by Evgeny Borisov (Independent) at JavaOne 2026 (CA, March 2026).

All JavaOne 2026 talks ➤ https://www.youtube.com/playlist?list=PLX8CzqL3ArzUMVSzm-z_-if8BIB55EGl4

Tags: #Java #OpenJDK #JavaOne #SpringBoot

LRN1454 18 104

Java (Official Oracle)

A conference talk transcript by Ivan Borisov exploring Spring Boot internals through live debugging puzzles using IntelliJ IDEA. Topics covered include Spring property source precedence and environment post-processors, bean definition naming rules (especially with multi-capital-letter class names), bean collection injection behavior, the new Spring 7 BeanRegistrar for dynamic bean registration, prototype vs singleton lifecycle differences (pre-destroy not called for prototypes), and transactional proxy internals (self-invocation bypassing the proxy). The IntelliJ IDEA debugger is used throughout to inspect bean definitions, property values, and runtime context state.

Spring Debugger New Power: Where Should I Click to Demystify Spring Boot Magic?