...

Config By X means that configuration for magnolia can be provided by different means - no longer only by jcr as today. Independently from how it's actually provided these configurations will end up in memory.

The Pieces

The Model layer

Config By X basically consists of the model (interfaces + definition classes) as well as the various mechanisms to populate the module (from JCR via Node2Bean, by Code via builders or by file via a new mechanism).

This page is about the model layer

Things to stay

...

Things to add/change

...

• <to check>: has to be per property, no?

...

• The Model layer

• Configuration "providers"
  • Config By Jcr
  • Config By Code
  • Config By File

...

• check how to use definition impls e.g. in tests then (might not be around after a mvn clean)

...

• e.g. to be able to tell what "element" you're overriding

...

• folder, content, properties (find some wording which is ideally independent from jcr notation)
• what icon to use
• class and origin
• path
• ...

Things we won't tackle NOW

• Publication of in memory config
  
  • we only consider getting config in jcr, code or file from author to public..

Open Issues

• is supporting typical module definitions enough or do we need to support any config?
• places where we're relying on jcr today - can they stay or do the have to operate on memory now?
  
  • server configuration is in jcr only - ok to not introduce definitions for this right now and hence there'll not (yet) be the option to change server config by file or code?
  • registries (dialogs, apps, ...)

TO - BE - MOVED - TO - PROPER - PAGES

...

Config By File (missing) (to be moved to a dedicated subpage)

...

Config App

• will no longer be a content app - has to work on definitions
  
  • we need common interfaces there