BO <=> DTO mapper in Java

Question

I am currently in my application maping DTOs to BO (and vice versa) manually. However, this approach is awkward and clumsy.

Is there any good mapper between these two representations?

My requirements follow:

Should support conversion of JPA proxies to identifiers (DTO should not link to other DTO directly). Or this functionality should be easy to implement
Should be annotation based, covention over configuration
Soft criteria: should allow mapping of multiple DTOs to one entity (and vice versa)

Thanks for any suggestions.

Have you tried this? http://www.jdto.org/ – miguelcobain Jan 25 '13 at 14:19 — miguelcobain, Jan 25 '13 at 14:19

score 9 · Accepted Answer · edited May 23 '17 at 12:02

9

Regarding object mapping I would recommend

Also, refer to this SO answer. It has a more or less complete list of Java Object mappers: https://stackoverflow.com/a/1432956/1137735

The 3 I suggested seemed more appealing to me. I think they all fulfill the requirements you ask.

edited May 23 '17 at 12:02

Community

1
1

answered Jan 25 '13 at 14:30

miguelcobain

4,734
4
32
45

Thanks for the links. I will check these implementations. – malejpavouk Jan 25 '13 at 17:45
3

Just in case someone needs it. Spring 3 mapper seems to be only a preview. Documentation of jdto was not persuasive enough to try it (it seemed that the framework is not very flexible). Than I tried Dozer and Orika. Both worked fine, Dozer has also XML confix, which is a big advantage, but it is significantly slower. So I chose Orika. – malejpavouk Mar 28 '13 at 09:02

score 5 · Answer 2 · answered May 21 '14 at 08:47

Well I know this thread is a bit old, and I am pretty sure that @miguelcobain answer is great.

Personnaly, I would recommend using Orika for a runtime sytem. It is strong and uses byte code generation at runtime so mapping is handled by generated code instead of always using the Reflection API. The other listed libraries are always using complex configuration and not conventions.

The second solution and the better one, I think would be to use Selma. This short library does the job for you, but instead of handling the mapping at runtime, it generates the mapping code at compile time using an annotation processor. So compiler will raise mapping errors, this is refactoring proof and you will be able to see the generated code.

Hope you'll give it a try.

score 1 · Answer 3 · answered May 15 '13 at 15:57

I suggest you to try JMapper Framework.
It is a java bean to java bean mapper, allows you to perform the passage of data dinamically with annotations and / or XML. With JMapper you can:
create and enrich target objects
apply a specific logic to the mapping
automatically manage the XML file
implement the 1 to N and N to 1 relationships
implement explicit conversions
apply inherited configurations

BO <=> DTO mapper in Java

3 Answers3