Injectable Singleton
From APIDesign
(Difference between revisions)
| Line 1: | Line 1: | ||
[[Singleton]]s are sometimes dishonest as a design anti-pattern. Right, one may use them improperly, but with guidance of proper methodology there is nothing wrong on [[singleton]]s. This page provides step by step cook book for usage of so called [[Injected Singleton]]s. | [[Singleton]]s are sometimes dishonest as a design anti-pattern. Right, one may use them improperly, but with guidance of proper methodology there is nothing wrong on [[singleton]]s. This page provides step by step cook book for usage of so called [[Injected Singleton]]s. | ||
| - | |||
| - | |||
== What this is not == | == What this is not == | ||
Revision as of 19:32, 27 January 2010
Singletons are sometimes dishonest as a design anti-pattern. Right, one may use them improperly, but with guidance of proper methodology there is nothing wrong on singletons. This page provides step by step cook book for usage of so called Injected Singletons.
Contents |
What this is not
TBD. Not about SecurityManager, URLStreamHandlerFactory, etc.
Configure
TBD. Drop-in your implementations to classpath.
Testability
TBD. Use MockServices
- mention testing limitations due to levels of Co-existence and solutions
Injectable Meta-Singleton
- Lookup is meta!
Follow
