Strict mapping messes up the build sequence

[robert-bor]

When strict mapping is in place, List mapping is hampered. What currently happens is that collection handlers cannot be found. The result is that no collection instructions are attached to a pair of fields, resulting in the collection converter not being chosen.

This code in BeanMapperBuilder is the culprit:

    public BeanMapper build() {
        BeanMapper beanMapper = new BeanMapper(configuration);
        // Make sure all strict bean classes have matching properties on the other side
        configuration.getBeanMatchStore().validateStrictBeanPairs(configuration.getBeanPairs());
        // Custom collection handlers must be registered before default ones
        addCollectionHandlers(customCollectionHandlers);
        addCollectionHandlers(DEFAULT_COLLECTION_HANDLERS);
        // Custom bean converters must be registered before default ones
        addCustomConverters();
        if (configuration.isAddDefaultConverters()) {
            addDefaultConverters();
        }
        return beanMapper;
    }

The validateLine triggers the verification of mappings before the full BeanMapper build has taken place.

The validation needs to take place after the build has completed, not before.