[MAGNOLIA-5779] Add possibility to observe whole workspace rather than subfolders of modules in config workspace Created: 20/May/14  Updated: 21/May/14  Resolved: 21/May/14

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 5.3

Type: Improvement Priority: Neutral
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MAGNOLIA-5780 WorkspaceObservingManager fails when ... Closed
dependency
is depended upon by MGNLPN-13 Create registry for all segments and ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Personalisation

 Description   

The current info.magnolia.cms.util.ModuleConfigurationObservingManager is very limited: it can only observe Nodes

  • in RepositoryConstants.CONFIG workspace and
  • that are direct subnodes of a module node, i.e. /modules/stk/templates (It has to be a module node, as the info.magnolia.module.ModuleRegistry is used to populate the observed directories).

It would be an improvement if we could observe an arbitrary folder, in any workspace and limit observation to specific NodeTypes and Events.



 Comments   
Comment by Daniel Lipp [ 21/May/14 ]

pls use getters (and if required setters) and private rather than protected attributes

Generated at Mon Feb 12 04:08:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.