Map 使用 Mapstruct 的集合并为单个实例指定方法？

Question

i have a mapstruct class with the following functions

    abstract CustomApplication convertCustomApplication(ApplicationDTO source);

    abstract RegularApplication convertRegularApplication(ApplicationDTO source);

    @Named("mainConverter")
    public App mainConverter(ApplicationDTO source) {
        return source.isCustom() ? convertCustomApplication(source) : convertRegularApplication(source);
    }

    //@Mapping( qualifiedByName = "mainConverter")
    abstract public List<App> convertApplications(List<ApplicationDTO> applicationList);

Both CustomApplication and RegularApplication extend App, so I have mainConverter that calls the converter according to the isCustom field.

The problem is that when i try to build this i get an ambiguous mapping error, because mainConverter, convertRegularApplication, and convertCustomApplication all map from ApplicationDTO to App (or subclass of App). So convertApplications does not know what to use. Is there any way i can explicitly tell it to call mainConverter? I wanted something like @Mapping( qualifiedByName = "mainConverter") that I put above convertApplications, (but it doesnt work of course) Does anyone know how I can do this? Thanks!

Answer 1

In order to achieve what you are looking for you will need to use IterableMapping#qualifiedByName .

This property is meant to enhance the selection for the list.

eg

    abstract CustomApplication convertCustomApplication(ApplicationDTO source);

    abstract RegularApplication convertRegularApplication(ApplicationDTO source);

    @Named("mainConverter")
    public App mainConverter(ApplicationDTO source) {
        return source.isCustom() ? convertCustomApplication(source) : convertRegularApplication(source);
    }

    @IterableMapping(qualifiedByName = "mainConverter")
    abstract public List<App> convertApplications(List<ApplicationDTO> applicationList);

Alternative solution

You are making your mainConverter qualified method. However, it looks like that method already redirects to the more specific method. Therefore I would suggest to qualify the other two methods and remove the qualification from the mainConverter . Then you won't need to do anything for the iterable mapping.

eg

    @Named("customApplication")
    abstract CustomApplication convertCustomApplication(ApplicationDTO source);

    @Named("regularApplication")
    abstract RegularApplication convertRegularApplication(ApplicationDTO source);

    public App mainConverter(ApplicationDTO source) {
        return source.isCustom() ? convertCustomApplication(source) : convertRegularApplication(source);
    }

    abstract public List<App> convertApplications(List<ApplicationDTO> applicationList);