Main goal of this library is to provide lightweight, easy configurable with annotations, and powerful tool for object mapping/merging, making life easier for projects with multilayer structure. It was take for me less then one day to completely migrate project at my main work (hundreds of classes, mappings between DTOs, Business objects and view objects) from dozer to java-object-merger without any serious issues.
Go to Wiki pages for technical FAQ with examples!
Available in maven central repository:
- Classes for merge/map not required to be the same - they should have only similar structure.
- Strong support of mapping configuration using annotations.
- Ability to configure of beans metadata not only by annotation but programmatically as well (from code or from spring).
- More flexible mapping than dozer have.
- Developed in mind to be easy configured via Spring IoC.
- Able to find diff between objects, and represent it in human readable form.
- Support parametrized type converters and property converters.
- Many type converters are used by default: for example for conversion between dates, primitive types and wrappers, implicit conversion of numeric types etc.
- Support parametrized bean finders (for example to find beans in database).
- Support registering listeners on main merge/map events.
- Support concept of bean identifier, to associate source bean with correct destination bean. - Main internal classes could be extended and changed. But by default all should work just as you expected!
- Library depends only from 'commons-beanutils' and 'commons-lang3'
- All functionality is covered with unit tests.
Be the first to post a review of java-object-merger!