InjectionManagerStore (Jersey 3.1.9 API)

All Known Implementing Classes:

GenericInjectionManagerStore
```
public interface InjectionManagerStore
```
injection manager designed for Jersey CDI extension. This SPI is designed to support deployments that can contain more than one Jersey/InjectionManager managed CDI component provider (more injection manager) but only single CDI extension instance (e.g. EAR with multiple WARs). Each CDI component provider instance acknowledges the manager about new injection manager and manager is supposed to return the effective injection manager for the current context (based on the Servlet context, for example).

Since:

2.17

Author:

Michal Gajdos

Method Summary

All Methods Instance Methods Abstract Methods
Modifier and Type	Method	Description
`InjectionManager`	`getEffectiveInjectionManager()`	Obtain the effective `injection manager`.
`void`	`registerInjectionManager(InjectionManager injectionManager)`	Register a new `injection manager` with this manager.

- Method Detail
  - registerInjectionManager
```
void registerInjectionManager(InjectionManager injectionManager)
```
    Register a new injection manager with this manager.
    
    Parameters:
    
    injectionManager - injection manager to be registered.
  - getEffectiveInjectionManager
```
InjectionManager getEffectiveInjectionManager()
```
    Obtain the effective injection manager. The implementations are supposed to decide which of the registered injection managers is the currently effective locator. The decision can be based, for example, on current Servlet context (if the application is deployed on Servlet container).
    
    Returns:
    
    currently effective injection manager.