| Thread Previous • Date Previous • Date Next • Thread Next |
We are in the process of removing our current DI implementation.
** Changed in: keystone
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1218942
Title:
Dependency resolution does not create objects on demand
Status in OpenStack Identity (Keystone):
Won't Fix
Bug description:
The isssue is clearest with the circular dependncy code between
identity and assignment, but we see it throughout the code base: one
component that requires another component has to be sure that the
dependency has been initialized prior to access.
This form of Dependency Injection is not new. The general pattern
followed by Spring etc is that the app has a two phase process. Dugin
the first phase (early in the application) component register as
fulfilling dependencies and what dependencies they require. Afte a
certain point (once the source files have all been parsed) object
instantiation can begin. THere is no deliberate "instantiate all
objects" stage as you may end up creating objects that you do not
need.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1218942/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
