-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
3.0.2
-
None
-
None
Blossom component info.magnolia.module.blossom.dialog.BlossomFormDialogPresenterImpl extends Magnolia core class info.magnolia.ui.dialog.formdialog.FormDialogPresenterImpl
When the Blossom implementation calls the superclass's constructor, it does not include the new AvailabilityChecker and ContentConnector parameters introduced by 5.3.
Therefore, attempting to open the dialog associated with a Blossom component causes Magnolia to fail with:
java.lang.NoSuchMethodError: info.magnolia.ui.dialog.formdialog.FormDialogPresenterImpl.<init>(Linfo/magnolia/ui/dialog/registry/DialogDefinitionRegistry;Linfo/magnolia/ui/dialog/formdialog/FormBuilder;Linfo/magnolia/objectfactory/ComponentProvider;Linfo/magnolia/ui/dialog/actionarea/DialogActionExecutor;Linfo/magnolia/ui/dialog/formdialog/FormView;Linfo/magnolia/i18nsystem/I18nizer;Linfo/magnolia/i18nsystem/SimpleTranslator;)V
at info.magnolia.module.blossom.dialog.BlossomFormDialogPresenter.<init>(BlossomFormDialogPresenter.java:70)
- duplicates
-
MGNLUI-3034 BlossomFormDialogPresenter breaks due to FormDialogPresenterImpl constructor signature changing in Magnolia 5.3
- Closed
- is related to
-
BLOSSOM-186 Update sample to Magnolia 5.3.1 and DAM 2.0.1
- Closed