-
Improvement
-
Resolution: Fixed
-
Major
-
3.0.2
-
None
-
None
Using Magnolia 5.3.1-SNAPSHOT and Blossom 3.0.2.
When using new DAM versions 2.x, the @TabFactory method 'DamConfig' argument can no longer bind.
In the new DAM 'DamConfig' is in the "info.magnolia.dam.app.ui.config" package, while Blossom's ParameterResolver implementation has hardcoded and expecting the class name of "info.magnolia.dam.asset.config.DamConfig"
Stacktrace:
Caused by: java.lang.IllegalStateException: Unable to resolve parameter of type [class info.magnolia.dam.app.ui.config.DamConfig]
As a quick fix, I created a class in my module using old package structure, pining to DamFieldConfig in new package structure.
package info.magnolia.dam.asset.config;
import info.magnolia.dam.app.ui.config.DamFieldConfig;
public class DamConfig
So far so good. Probably this class should find its way to DAM 2.x magnolia-dam-compatibility project.
- is related to
-
BLOSSOM-186 Update sample to Magnolia 5.3.1 and DAM 2.0.1
- Closed