2. Why to use mappers?
- default settings -> less coding
- ‘global’ settings for handling NULLS, empty String ect.
- Simple conversions handling (lists, enums, different numeric types) ‘out of
the box’
- Centralization of mapping configuration in application
6. Dozer
● Reflection based (==slowly)
● Mapping from map to Object
● Develop since 2006r.
● Most popular
● Not actively maintained (152
issues on GitHub)
● stackOverflow: 1519 result
XML
ANNOTATION
JavaConfig
7. Orika
- Generates bytecode during first
mapping (first time is slow, then
faster)
- 27 open issues on GH
- Last commit 2 months ago
- stackOverflow: 211 results
- Developed since 2012
JavaConfig
8. Jmapper
- Generates bytecode during
application startup
- Last commit one month old
- 5 open issues on GH
- Dynamic converter declaration
(code snippets, including xml)
- Field mapping 1:n and n:1
- Support for flattening and
encapsulation
- StackOverflow: 19 results
- Developed since 2013
@GlobalJMap
ANNOTATIONS
XML