Artem Bilan

The `WARN` is a bit lower severity than `INFO`. That means when you enable `INFO` for logging you are going to see `WARN`, too. So, your concern about logging level...

OK. Understandable. So, we can treat this issue like: Whenever we log a content of the message under `INFO`, consider to move such a possibly sensitive information under `DEBUG` level,...

Well, for that reason an issue is going to be logged under `ERROR` or `WARN`. In most case of course it is going to be an exception with the whole...

@garyrussell , I would like to hear your opinion about this issue. Thanks

Raised: https://github.com/spring-projects/spring-framework/issues/24727

It always worked that way and I guess that's just because there is no way in Spring to register several beans at once. However I don't think that with our...

Thank you, @jhoeller , for kind explanation! I will look into your suggestions for the next milestone. In addition, I'll investigate if that would be possible to generate some code...

No problem, @snicoll ! The code generation is still dark matter for me anyway :relaxed: Then I will look into a `BeanDefinitionRegistryPostProcessor` for this `@Bean` with Messaging Annotations to register...

Another side of this medal is a `destroySingleton(String beanName)` which is not available in the `ConfigurableBeanFactory` - just on the `DefaultSingletonBeanRegistry`. I don't mind any discussion at any place, but...

That's really an interesting and useful suggestion. Only the problem that we don't know such a template. @Buzzardo, Any ideas on the matter? Is there some ASCIDoc tricks to make...