[BLOSSOM-158] Blossom 3 replacement class for BlossomDialogRegistry Created: 23/Jan/14  Updated: 07/Nov/14  Resolved: 07/Feb/14

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

Type: Task Priority: Neutral
Reporter: Dean Pullen Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: blossom
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

We're using a class that utilises 'BlossomDialogRegistry.addDialogDescription' in Blossom 2.x - we're wanting to use Blossom 3 and notice that BlossomDialogRegistry class no longer exists.

What would be the correct methodology to perform:

Components.getComponent(BlossomDialogRegistry.class).addDialogDescription(dialogDescription);

Using Blossom 3?



 Comments   
Comment by Dean Pullen [ 23/Jan/14 ]

Is this simple enough to replace this effectively?

Components.getComponent(DialogDefinitionRegistry.class).register(new BlossomDialogDefinitionProvider(dialogDescription));
Comment by Tobias Mattsson [ 24/Jan/14 ]

Hi Dean,

BlossomDialogRegistry was removed when the standard dialog registry in Magnolia got support for providers. A much more elegant solution and it opens up the possibility of having more ways of registering dialogs. We're especially interested in adding by-code support to the core product. You might have noticed that the builder classes, TabBuilder etc, as of Blossom 3 are not in the blossom module anymore, they're in the core UI (ui-form and ui-dialog).

Blossom registers dialogs in DialogExporter in the standard registry. You should be able to do the same, let me know if that doesn't work out. I'd like to know more about your use case.

Cheers, Tobias

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