Java mapping: Selma vs MapStruct

java mapping mapstruct
JackDev picture JackDev · Jan 14, 2016 · Viewed 21.9k times · Source

Currently there are two main popular Java Object to Object mapping frameworks that supersede Dozer (http://dozer.sourceforge.net/documentation/mappings.html), they are:

  1. Selma - http://www.selma-java.org/
  2. MapStruct - http://mapstruct.org/

With the exception of this page (http://vytas.io/blog/java/java-object-to-object-mapping-which-framework-to-choose-part-2/) I haven't been able to find much online regarding which framework is better than the other, or under what circumstances they are better. Wondering if anyone you can shed some light on this. In terms of functionality based on the documents, they seem to be doing the same thing.

Answer

Gunnar picture Gunnar · Jan 14, 2016

(Original author of MapStruct here, so naturally I am biased)

Indeed, both projects are based on the same general idea of generating mapping code at compile time; I recommend you MapStruct for the following reasons:

  • Proven and stable codebase: MapStruct is the older of the two, coming up with the idea of mapping generation originally. It has been enhanced and polished over quite a long time, based on real-world feedback from usage in many different projects; We released the stable 1.0 Final last year
  • Larger developer and user community as per the number of committers (MapStruct, Selma) and user questions (MapStruct, Selma)
  • Feature-rich (Some things supported in MapStruct I didn't find (to the same extend) in the Selma docs):
  • Eclipse plug-in avaible: Still work in progress, but its quickfixes and auto-completions are already very helpful when designing mapper interfaces
  • IntelliJ plug-in: helps when editing mapper interfaces via auto-completion, go to referenced properties, refactoring support etc.

Related questions

Mapstruct: Ignore specific field only for collection mapping

I am using following mapper to map entities: public interface AssigmentFileMapper { AssigmentFileDTO assigmentFileToAssigmentFileDTO(AssigmentFile assigmentFile); AssigmentFile assigmentFileDTOToAssigmentFile(AssigmentFileDTO assigmentFileDTO); @Mapping(target = "data", ignore = true) List<AssigmentFileDTO> assigmentFilesToAssigmentFileDTOs(List<AssigmentFile> assigmentFiles); List<AssigmentFile> assigmentFileDTOsToAssigmentFiles(List&…

Read More
MapStruct: Map List of objects, when object is mapped from two objects

Assume I have such mapping: @Mapping(source = "parentId", target = "parent.id") Child map(ChildDto dto, Parent parent); Now I need to map List of ChildDto to List of Child, but they all have the same parent. I expect to do …

Read More
Map multiple source fields to same type target fields with Mapstruct

Consider the following POJOs: public class SchedulePayload { public String name; public String scheduler; public PeriodPayload notificationPeriod; public PeriodPayload schedulePeriod; } private class Lecture { public ZonedDateTime start; public ZonedDateTime end; } public class XmlSchedule { public String scheduleName; public String schedulerName; public DateTime notificationFrom; …

Read More