OSGi/Camel ServiceRegistry implementation is terribly slow
The current ServiceRegistry implementation for Camel that hooks in the OSGi service registry can be improved.
It currently uses BundleContext.getServiceReferences() (#1 (closed)) that also tries to test ClassLoader compatibility between the consumer of the service (the ServiceRegistry implementation) and the provider of the service. In our case, this check does not make any sense since the ServiceRegistry implementation is not the final consumer of the service.
To avoid this check, we should use BundleContext.getAllServiceReferences() (#2 (closed)).
Additionally, we could benefit from natural filtering of OSGi services...