Make ChannelInitializer as dependency bean in the AbstractConsumerEndpointParser
#9931
Comments
spring-builds
pushed a commit
that referenced
this issue
Mar 28, 2025
Fixes: #9931 Issue link: #9931 If no message channel bean is declared explicitly, the XML parser for endpoints register such a candidate into the global `ChannelInitializer`. This way, the channel is created when this bean is initialized. However, there are cases when endpoint bean could be called before `ChannelInitializer` initialization. * Add `consumerEndpointBuilder.addDependsOn(IntegrationContextUtils.AUTO_CREATE_CHANNEL_CANDIDATES_BEAN_NAME);` into the `AbstractConsumerEndpointParser` to ensure that `ChannelInitializer` bean is initialized before the called endpoint bean. * Adjust `ChannelInitializer` logic to use `registerSingleton()` API instead of `registerBeanDefinition()` since the last one may cause problems with beans cache when this API is called at runtime. (cherry picked from commit c9e3de8)
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
See more info in the spring-projects/spring-boot#44873.
The
AbstractConsumerEndpointParserproduces aConsumerEndpointFactoryBeanwhich has to be initialized whenBeanFactoryrequests a bean type. IfinputChannelis not present in theBeanFactorythat leads to the problem.Making the
IntegrationContextUtils.AUTO_CREATE_CHANNEL_CANDIDATES_BEAN_NAMEas dependency on such an endpoint bean definition should trigger theChannelInitializerto be initialized. Therefore all the auto-create channel candidates will be created upfront.Side task.
Revise
IntegrationConfigUtils.autoCreateDirectChannel()to useregisterSingleton()instead this this functionality is called at runtime from thatChannelInitializer.afterPropertiesSet().The text was updated successfully, but these errors were encountered: