[MAGNOLIA-2994] content2bean: add support for configuration inheritance Created: 08/Jan/10  Updated: 23/Jan/13  Resolved: 25/Jan/10

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

Type: New Feature Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-3020 content API cleanup: improve the base... Closed
is depended upon by MGNLETK-10 domain support Closed
Template:
Acceptance criteria:
Empty

 Description   

Idea:
A configuration can have a 'extends' property defining a path (absolute or relative) to an other configuration node which he wants to extend.

Implementation:
A content wrapper similar to the ones used for inheritance or i18n will combine the configuration and expose the merged content to content2bean transparently or potentially also to other mechanism as like the dialog manager. It will potentially also be a successor of the 'reference' property used to define dialogs.

Note: this is a bit different from what we do in STK for merging the template and template-prototype. There we merge the already instantiated beans.


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