When using @Produce @Consume and other POJO injected resources they may be started during the injection phase.
We should defer starting till CamelContext has started other resources, and its routes, so they are ready before the POJO resources.
For example this allows interceptors and whatnot to be properly initialized at first.
So we should have some api on CamelContext these POJO resources can register and then let CamelContext handle their lifecycle.
This also aids to ensure these resources gets shutdown when CamelContext shutdown itself also.