All injection resolvers registered with the system will be called in a random order. Resolvers should therefore not rely on the ordering of installed injection resolvers. Any injection resolvers added as a result of this callback will NOT be called until the next injection resolution failure.
Implementations of this interface are placed into the registry like
any other service. One use-case would be to inject the
DynamicConfigurationService into the implementation in order
to add services if this resolver can do so. Another option would
be to inject a ServiceLocator and use one of the methods
in org. in order
to add services to the registry
If any of the registered injection resolvers commits a dynamic change then the system will try one more time to resolve the injection before failing (or returning null if the injection point is Optional).
| Modifier and Type | Method and Description |
|---|---|
| public boolean | Returns: true if this method has added a descriptor to theServiceLocator
which may be used to resolve the Injectee. False if this method
did not add a descriptor to the ServiceLocator that might help
resolve the injection pointThe injection point that failed to resolve failedInjectionPoint)This method will be called whenever an injection point cannot be resolved. |
| justInTimeResolution | back to summary |
|---|---|
| public boolean justInTimeResolution(Injectee failedInjectionPoint) This method will be called whenever an injection point cannot be resolved. If this method adds anything to the configuration it should return true. Otherwise it should return false. The injection point that failed to be resolved is given in failedInjectionPoint. If this method throws an exception that exception will be added to the set of exceptions in the MultiException that may be thrown from the injection resolver.
This method can be called on multiple threads with different or the same
| |