ThreadLocalTargetSource does not include actual target bean name in NamedThreadLocal #30581
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
status: backported
An issue that has been backported to maintenance branches
type: bug
A general bug
Milestone
In the course of some nullability refinements along with #30576, it turns out that
ThreadLocalTargetSource
always initializes itsNamedThreadLocal
with a String that contains anull
bean name. That bean name should be appended lazily in atoString()
implementation instead.The text was updated successfully, but these errors were encountered: