This guide is (like Orika) a work in progress; any feedback in the way of suggestions or questions or problems can be posted to our project issues site, currently hosted at Google Code
As developers we have to provide solutions to business problems, and we want to use the time in our disposition to do what really matter.
In our days, enterprise applications became more and more complex, with a lot of architecture and design constrains.
Design constraints that will produce a considerable amount of mechanical work. A lot of
In a medium to large project, such mapping code can reach a considerable effort of mechanical (boring) work which can be difficult to maintain, test, and debug.
Orika attempts to perform this tedious work for you, with little measurable tradeoff on performance
It will automatically collect meta-data of your classes to generate mapping objects which can be used together to copy data from one object graph to another, recursively. Orika attempts to provide many convenient features while remaining relatively simple and open -- giving you the possibility to extend and adapt it to fit your needs.
We could use your help!
Most all kinds of contribution are welcomed; feature requests, patches, bug reports, test cases, benchmarks, blog posts, and stories of how Orika helped you (or even where it could have been more helpful)-- all are welcomed.