[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:
Relates
relates to MAGNOLIA-5522 CommandsManager should be reimplement... Closed
relates to MGNLLIC-50 LicenseManager should be reimplemente... Closed
dependency
is depended upon by MAGNOLIA-3457 Config reload on Module doesn't work ... Closed
is depended upon by MAGNOLIA-2263 creating or importing a virtualURIMap... Closed
relation
is related to MAGNOLIA-1928 Add support for repository-only modules Closed
is related to MAGNOLIA-4186 jcr: implement ObservedManager based ... Closed
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. MAGNOLIA-4186

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.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:35:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.