[MAGNOLIA-2265] Observe module nodes to automatically register new nodes in appropriate components Created: 15/Jul/08 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 3.6 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||
| Description |
|
A restart is currently required if one wants to add, for example, paragraph in her own module, when the /modules/mymodule/paragraph did not exist yet. Observing all modules node (isDeep=false) and registering children node with the appropriate ObservedManager could solve this. |
| Comments |
| Comment by Tobias Mattsson [ 02/Dec/13 ] |
|
This was solved by introducing ModuleConfigurationObservingManager, its in use by all managers but CommandsManager and VirtualURIManager. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |