Component state and registry - fixes and refactoring
* Errors during shutdown or destruction will be thrown as exceptions. Returning the collection of errors was clumsy, at best - if something goes wrong, the registry has failed anyway. * Recursive initialisation and destruction methods in ComponentState * Use ComponentState's methods while initialising, starting up, shutting down or destroying the registry.
This commit is contained in:
parent
7f919349e9
commit
81ea62047e
5 changed files with 174 additions and 237 deletions
3
TODO
3
TODO
|
@ -1,5 +1,5 @@
|
|||
To Do:
|
||||
* Fix initialisation / startup from Registry.register()
|
||||
* Test for ComponentState.{init,destroy}
|
||||
* Registry tests
|
||||
* Registry doc
|
||||
* Implement "DriverFor" support
|
||||
|
@ -8,7 +8,6 @@ To Do:
|
|||
* Automatically-updated singletons
|
||||
* Registry: get all component states
|
||||
* Document exceptions
|
||||
* Not too fond of stop()/destroy() returning exceptions
|
||||
|
||||
Other ideas (maybe later if needed):
|
||||
* Unregistering components
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue