Hmm, would it make sense for the Spring registry to be mutable? I can definitely see the case for unit testing (as I have submitted: https://issues.apache.org/jira/browse/CAMEL-6342), however, I'm not sure about the "live" registry. It seems that non-Spring allows for additional objects to be added to the registry (JndiRegistry for example).
Don't some of the standard camel components register beans for their later use\ease of use - if so, how is that done? -- View this message in context: http://camel.465427.n5.nabble.com/add-bean-to-registry-in-custom-endpoint-tp5732085p5732423.html Sent from the Camel - Users mailing list archive at Nabble.com.
