Problem of defining parent-child JPA mapping. about mapstruct-spring-extensions

[Chessray]

Spring's Converter interface is very opinionated in this regard and does not allow anything like MapStruct's @Context. I've struggled with this scenario in the past and opted not to follow the Spring Converter model with this kind of Mapper.

[fajksk-dev]

I see, but is there any other way of achieving same behavior in mapstruct-spring-extension ? If not I'll have to use directly basic mapstruct in few particular cases.

[Chessray]

One way I can imagine is defining a Wrapper class that contains both the original and the information you'd typically put into the context. But building a full hierarchy like that sounds too complex for most use cases.

Another way might be defining some type of dynamic lookup object that can be injected into the Mapper as well as the calling code. That idea obviously comes with its own cost and headache, so you'd have to decide for yourself whether it's worth it.

Spring really expects all information required for mapping in the source object. You might be better off using only core MapStruct functionality in these cases.