Home

This wiki is under construction

The mapping is a mechanical operation almost 100%, in medium-large applications, between development, testing and bug fixing, it reaches a weight that is certainly not negligible.

As the rule may seem elementary, enclose in a single framework a potentially unlimited number of combinations, recursive mapping, addition of logic and other features, makes its implementation very complex with questionable compromises, such as poor performance, covering a limited features, etc... .

JMapper aims not only to coverage all requirements but also to make it as easy as possible to use, that's all with performance equivalent or higher to handwritten code.

JMapper allows:

• to create and enrich target objects
• to apply a specific logic to the mapping
• to perform complex mapping (Collection, Map, Array, inner classes, etc...)
• to perform recursive mapping (mapped objects into other objects)
• to manage implicit and explicit relationships of various types:
  

• one to one
  
• one to many
  
• many to one
  

to implement [explicit conversions](https://github.com/jmapper-framework/jmapper-core/wiki/Explicit-Conversions)

to configure the mapping using the annotation and / or xml

to apply [inherited configurations](https://github.com/jmapper-framework/jmapper-core/wiki/Advanced-Inheritance-Examples)

to write quick and simple xml configuration file, through a series of [utility methods](https://github.com/jmapper-framework/jmapper-core/wiki/Xml-Hander)