Add support for DAM 2.x new package name of DamConfig.java

Description

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 {
public final DamFieldConfig fields = new DamFieldConfig();
}

So far so good. Probably this class should find its way to DAM 2.x magnolia-dam-compatibility project.

Activity

Show:

Yan December 6, 2014 at 11:57 AM

Bulk close of old resolved tickets.

Tobias Mattsson July 25, 2014 at 9:26 AM

Note that you will also need to change the package of DamTemplatingFunctions in blossom-servlet.xml from info.magnolia.dam.asset.functions.DamTemplatingFunctions to info.magnolia.dam.templating.functions.DamTemplatingFunctions.

Fixed

Details

Assignee

Reporter

Priority

Fix versions

Affects versions

More fields

Created July 11, 2014 at 12:09 AM
Updated December 6, 2014 at 11:57 AM
Resolved July 25, 2014 at 9:42 AM