
gnodet: the initialization of the CamelContextFactoryBean is now done at the end of the blueprint
container creation through the use of a ComponentDefinitionRegistryProcessor (those are called
after all the beans have been initialized.  That's why the calls to #afterPropertiesSet and
#init are commented.
This mechanism is now required because the #afterPropertiesSet method on the CamelContext
will search through the blueprint beans for beans implementing known interfaces such as
LifeCycle strategies, etc... so that they are automatically wired to the CamelContext.
However, Blueprint does not support real factories, so in order to do so, we need to actually
access the beans which lead to a circular exception while looking for the CamelContext itself.
