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
The DefaultTopicResolver uses a Map with Class<*> as key.
This fails if the project uses multiple classloaders, because Class<> has no equal implementation, every classloader creates a different "version" of the class.
For example, register custom mappings and add spring-devtools to the project.
This brings in a "RestartableClassLoader".
Other instrumentations might lead to similar problems.
The TopicResolver will fail for the custom mappings.
The DefaultTopicResolver uses a Map with Class<*> as key.
This fails if the project uses multiple classloaders, because Class<> has no equal implementation, every classloader creates a different "version" of the class.
For example, register custom mappings and add spring-devtools to the project.
This brings in a "RestartableClassLoader".
Other instrumentations might lead to similar problems.
The TopicResolver will fail for the custom mappings.
https://docs.spring.io/spring-boot/reference/using/devtools.html#using.devtools.restart.disable
https://stackoverflow.com/questions/2625546/is-using-the-class-instance-as-a-map-key-a-best-practice
Version 1.2.4
The text was updated successfully, but these errors were encountered: