- All Superinterfaces:
- All Known Implementing Classes:
public interface ComponentProvider extends ComponentProvider
Component provider interface to allow custom management of 3rd party components life-cycle and dependency injection. An implementation (a component-provider) identifies itself by placing a provider-configuration file (if not already present),
org.glassfish.jersey.server.spi.ComponentProviderin the resource directory META-INF/services, and adding the fully qualified service-provider-class of the implementation in the file. Jersey will not even try to inject component provider instances with Jersey artifacts. The SPI providers should be designed so that no dependency injection is needed at the bind time phase.
- Jakub Podlesak