|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||
java.lang.Objectorg.olat.core.logging.LogDelegator
org.olat.core.manager.BasicManager
public abstract class BasicManager
A manager should be state-less and be implemented as a singleton. In rare situations it can make sense to have state-full managers that feature a cache or something. In those cases you should implement a destroy method and call this method from your component module. An alternative to state-full managers is to externalize the statefull elements to dedicated objects and access them via the component module.
If your manager needs initialization, it should be initialized from the component module.
Initial Date: 28.08.2008
| Constructor Summary | |
|---|---|
BasicManager()
|
|
| Method Summary |
|---|
| Methods inherited from class java.lang.Object |
|---|
equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Constructor Detail |
|---|
public BasicManager()
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||