When using XBeanServiceUnit and AbstractXBeanDeployer (which is the case for most smx components) applicationContext is created and started during deployment and closed (destroyed) during shutdown.
However, endpoint beans are still referenced by jbi registry, and can be used after SU is started. This can be quite confusing for beans performing some kind of shutdown during context closing.
Particularly, when using camel, after closing camel context some processors (e.g. DeadLetterChannel) throw exception when trying to process exchange.
This could be fixed in two ways:
- override defaults in camel component
- fix it directly in servicemix-common (not sure if and how it would affect other components)
I think that fix would have to involve refreshing/recreating applicationContext in start method of SU. However, this would have to swap endpoint instances in endpoint registry