You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At least in the basic case, only the constructor gets cached in AutowiredAnnotationBeanPostProcessor.candidateConstructorsCache and removing it from there resolves the issue. Is this something SpringBeanReload should separately check? Seems overkill to run the whole doReload loop for this case - unless something else is cached somewhere else
Artur-
added a commit
to Artur-/HotswapAgent
that referenced
this issue
Jan 20, 2025
If you create a bean using
then Spring will cache the constructors and maybe other info for the type. However, the check that HotswapAgent uses for clearing the cache:
HotswapAgent/plugin/hotswap-agent-spring-plugin/src/main/java/org/hotswap/agent/plugin/spring/reload/SpringBeanReload.java
Lines 326 to 330 in a86384c
will print
the class '{}' is not spring bean or factory class
and then leave the invalid cached info in place.This happens e.g. for Vaadin
@Route
classes which are not explicitly marked as Spring beansThe text was updated successfully, but these errors were encountered: