Hello, I have been playing with the Spring DefaultMessageListenerContainer, trying to get it to start in blueprint.
After searching for a while (and realizing that I was looking at the old Spring Framework 2.5.6 code :)), it appears that in Spring version 3+ the MessageListenerContainer(s) is tied even closer to the spring framework via the Spring SmartLifecycle. My understanding is that to initialize the DefaultMessageListenerContainer you need to call both afterPropertiesSet and start (in Spring 2.5.6 afterPropertiesSet would call "start" -> in 3.x, Spring will call "start" after the application context has completed loading). In Blueprint, I can only call the one init method (afterPropertiesSet) Now since I know the new Spring 3.x pattern, in blueprint I can create another bean which takes the Spring bean (DefaultMessageListenerContainer) as a constructor arg and in its init-method just calls start on the Spring bean. Is that the right way to work around this though? Am I missing some appropriate blueprint functionality to use? If there isn't something in blueprint now, do you see something similar being implemented in the future? If not, I guess my general question is I assume that blueprint and the Spring framework functionality will drift further apart over time? thanks in advance, Gareth
