GeDA was inspired by developer's lazyness (as always). The rationale for its existance was overhead of creating DTO Assemblers in an n-tier application to pass information within domain object to UI through DTO's (Data Transfer Objects). The basic principle of the above application design is to extract the necessary information from the domain objects in the form of DTO's. In reality this involves a tidious get/set method calls that look very much the same for most of the objects. GeDA uses Java5's annotations in order to map DTO's onto paths of the Domain object properties (the reflection method). Thus the annotated DTO's can be examined by a Generic DTO Assembler that will create specific instance of the assembler for the DTO is respect to a Domain object. The assmebler is basically a placeholder for so called "data pipes" that allow transferring data from/to domain object's field. But do not take my word for it - try it out yourself.
web: https://sourceforge.net/projects/geda-genericdto/
download latest stable (v.1.1.3): http://sourceforge.net/projects/geda-genericdto/files/stable/1.1.3/
svn: svn co https://geda-genericdto.svn.sourceforge.net/svnroot/geda-genericdto geda-genericdto
*NEWS: *GeDA will be undergoing namespace change (dp.lib to com.inspiresoftware.lib.dto.geda) after version 1.1.3 going to version 2.0.0. Additionally we plan to release Spring 3 integration module to provide seamless integration through annotations.
To setup mvn dependency please read this page.
NOTE: If you have some questions please consult FAQ's section prior sending a request
If you wish to contact us please use our feedback form
Recent enhancements may be found here
You can report any problems with GeDA to our public jira
