Is Camel IoC friendly?
In particular we’ve gone out of our way to make Camel work great with Spring and to reuse all of Spring 2.x’s power. For example • the CamelContext, Components and Endpoints and their dependent beans can be configured in Spring using Spring custom XML namespaces or traditional bean/property elements • we implement a spring BeanPostProcessor to allow POJOs to be injected with Camel resources along with powerful Bean Integration which allows any spring-injected POJO to be used inside Camel along with full support for Spring Remoting. What we’ve tried to do is implement the Inversion Of Control With Smart Defaults pattern; namely that you can configure Camel in a single XML element (or very small amont of XML) to get going, then you can overload default configurations to add more explicit configuration as and when you need it.
