Consider moving post processor implementation outside of @Configuration

[snicoll]

A user has drawn our attention that a code example shows a @Configuration class that implements BeanPostProcessor (Configurator).

It's really unusual to have a @Configuration class implements additional contracts as its main purpose is to define beans in the context using @Bean annotated factory methods.

Can you please consider moving that to a dedicated component?

[sbordet]

It's really unusual to have a @configuration class implements additional contracts as its main purpose is to define beans in the context using @bean annotated factory methods.

"Unusual" has a too wide range of interpretations 😃

Is this documented somewhere?

Furthermore, I'm all ears for a suggested solution -- PR or example to follow would be great.

The only solution that comes to my mind is to complicate things with more classes and beans and factory methods for no good reasons than to please Spring and workaround a Spring bug?
Does not sound right to impose this burden on application developers, no?