[MAGNOLIA-6066] Create APIs for new registry, configuration source, registry facade Created: 10/Feb/15  Updated: 29/Jun/15  Resolved: 19/Feb/15

Status: Closed
Project: Magnolia
Component/s: configuration
Affects Version/s: None
Fix Version/s: 5.4

Type: Task Priority: Neutral
Reporter: Michael Mühlebach Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MAGNOLIA-6077 DefinitionRawView's simple properties... Closed
dependency
relation
is related to MAGNOLIA-6147 DefinitionProviderImpl.get() doesn't ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

Part of this ticket is to:

  • define a common interface for all registries to be used. For this to work the registry items have to have a similar or common interface as well.
  • For features like Autosuggest, validation, config app, etc we need a why to store meta information about the config node. This information is either tied to the registry or the item.
  • The individual registry managers should be replaced by a more source oriented way. Therefore we need a common source interface for JCR and YAML at the moment.
  • All registries should be accessible over one registry facade (or registry of registries). This facade will at least be used for the new config app.

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