olegz/spring-integration — comment on commit 211f2ac9fbed526b87bd6e3fd0c8481505c2eff9
File: spring-integration-core/src/main/java/org/springframework/integration/config/xml/AbstractConsumerEndpointParser.java line 153
By markfisher:

I'm concerned about this too (looking forward to seeing the new approach). Generally, we should avoid anything that triggers eager initialization or that might lag behind something being configured within a BeanFactoryPostProcessor, especially if that BFPP is part of the core behavior that occurs with any SI usage. In this case, I'd not only worry about resolving the @ bean resolution (space added in case there is a 'bean' github user), but I'd also worry about property sources that may have not been established, and even the fact that some other BFPP might add channels, etc. I think it's a good idea to not do anything too proactive in a BFPP; unlike a BPP, there are too many things yet to occur and or too eagerly affected.