We don't do anything special for the extension. It is automatically discovered via META-INF/services/ mechanism.
Yes, but it somehow needs to become part of deployment's classpath.
What I meant was, do you dynamically add this CDIExtension module/bundle to every deployment's module you recognize as CDI depolyment?
This extension understands @OSGiService. OSGiService like qualifier is essential to build dynamic applications, for it has parameters like timeOut, dynamic, serviceProperties.
I see why it's neccessary -- see above, but I don't see why it needs to be a qualifier.