[BLOSSOM-276] Support Node parameter injection in 6 UI apps Created: 29/Jun/20  Updated: 09/Sep/21  Resolved: 02/Aug/21

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: None
Fix Version/s: 3.4.5

Type: Task Priority: Neutral
Reporter: Federico Grilli Assignee: Mikaël Geljić
Resolution: Done Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones BLOSSOM-257 Blossom update for 6.2 Closed
Relates
dependency
is depended upon by BLOSSOM-265 DOC: Update Blossom release page for ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:

 Description   

 What was done in 3.4:

  • use the new DialogDefinitionRegistry
  • but keep registering old-style compatibility dialogs (rely on auto-conversion for the new Pages app).

This maintained status quo in the compatibility Pages app (+/- BLOSSOM-269, fixed in 3.4.1).

This introduced support for simple dialog/tab-factories in new Pages app.
However there, there are still certain objects that the old BlossomFormDialogPresenter used to make injectable, mostly Vaadin 7 Item, JCR Node and node path. These use cases must keep using the compatibility Pages app for the time being. Magnolia 6 UI Framework does not have configurable form-dialog presenters, nor Vaadin 7 Items.

 


Generated at Sun Feb 11 23:31:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.