Issue with HandlerMethod#createWithResolvedBean after bean destruction

[jnd77]

Bug Report

Following this commit 6162d89, my application does not behave as expected after destroying the bean.

Instead of recreating a new bean and a new HandlerMethod, the cached value resolvedBeanHandlerMethod with the old bean is returned.

Enhancements request

DefaultSingletonBeanRegistry#destroySingleton() should reset this cached value.

[jhoeller]

What's your purpose for destroying and recreating that controller instance? Are you reconfiguring it or is its state somehow dirty?

In general, the web framework does not consistently support the re-creation of handler instances. We have been caching singleton bean instances in other places already, #36278 was only really taking a remaining opportunity for performance reasons.

[jnd77]

Thanks for the quick follow-up. By the way, I'm still working with Spring Boot 3 and Spring 6.2 (just making sure the fix, if necessary, will be ported).

The controller has an injected bean (which is a database service); this database service sometimes needs to be updated.
So until now, when that happened, I was destroying the database service (which by extension destroys the controller as well); but now (after going from 6.2.15 to 6.2.16) a REST call ends up with the old controller and the old database service.

As added context, our product is more like a library so a customer could implement their own controller depending on the database service, so we would really like something generic where everything works fine if the database service needs to be updated.

Would you have any suggestion to improve this setup ?