We need to access the MappingContext from within our custom converters. The
Converter API (Converter.convert(S, Type)) should be extended to have a third
parameter for the MappingContext:
D convert(S source, Type<? extends D> destinationType, MappingContext context);
I recognize that this is an API change that would force all existing custom
converters to be extended with this additional parameter. Still I think that
this is a necessary change in order to be able to pass the mapping context to
subordinate mappers. After all, that's the reason why the converter API allows
access to the MapperFacade, too. And the three Convert... specifications can
easily be changed to generate code that passes the context to the converter.
Original issue reported on code.google.com by daniel.b...@googlemail.com on 25 Mar 2014 at 8:33
Original issue reported on code.google.com by
daniel.b...@googlemail.com
on 25 Mar 2014 at 8:33