Tag Archives: orm

GORM and getting rid of the DAO(Repository) layer

Like many other new web application frameworks (e.g Rails, Spring Roo) Grails with its GORM has taken the approach that separate DAO or Repository layer is removed. Is this a bad thing or is it just a change in implementation that doesn’t affect conceptual design?
Continue reading

Domain model implementation consideration – dealing with presentation-domain model mismatch using rich domain model

Sorry about the title 🙂

In a typical data management system significant amount of effort is spent on implementing mappings between three different models – presentation, domain and persistence model. In this article I will describe one approach to dealing with these transformations in case special ORM tool cannot be used.
Continue reading