I was wondering, does it really make sense for JAXRSServerFactoryCustomizationExtension implementations to be CDI beans? It may sound odd, but typically in CDI that kind of feature is done as a service loader pattern. These are classes that should only be used once, so keeping them in memory is a bit of a waste. I think recently we saw some issues with SSE integration, where we had to make the archive a full bean archive (bean-discovery-mode=all) just to ensure that this bean was looked up. It may make more sense if these are ServiceLoader based classes, this way we just have to register it in META-INF/services without adding any CDI specific features to the JAR.
At the same time, I also wonder if this causes an issue for Java 9 modules. Does the dependency have to always be there, or can it be an optional dependency (my module foo is weak, so I have no idea if that's even feasible). John
