I addressed some of your simple comments. In answer to your more general points...
1. The strategy is required to be public. Yes, the extension figures out the correct ClassLoader, but I've left it up to users to decide what do with it. In my use case it involves a TCCL switch, and that's not something we want in every environment. Hence the ClassLoader is basically ignored in the default strategy. The camel context ClassLoader setting that you saw is only for unit testing to prove the custom strategy is being invoked. 2. The reason I didn't opt for `CdiCamelConfiguration` is that users would have to configure it for every application. With a bean, I can automatically make it available to every application for my [platform](https://github.com/wildfly-extras/wildfly-camel) use case. If you think a bean is not the right solution, then I don't see many options aside from some sort of static configuration, or adding the custom logic I need to implement directly in the CDI extension. Both are sub-optimal IMO. [ Full content available at: https://github.com/apache/camel/pull/2532 ] This message was relayed via gitbox.apache.org for [email protected]
