Hello everyone,

I'm wondering if it would make sense to have a sort of hierarchical
registry where the root registry is always created by the CamelContext
then the specific container registry adds its own registry on top and
the lookup would be top down.

The motivation is that there are some beans that are only used by
camel and the registry is always involved so it does not make much
sense to have them available also on the container, i.e. the
ServiceCall and Hystrix configured through XML.

This would reduce the complexity to add new definitions to the XML as
one do not need to create a container specific parser (blueprint,
spring, cdi) for object that are strictly camel-context related.

What do you think ?

---
Luca Burgazzoli

Reply via email to