In 2.0, we have GenericDAOs that allow generic CRUD, but they do need additional methods for dynamic filtering, sorting and such. I agree it would be nice to have user.save(), but I don't know if it's appropriate for a Java project as I think most folks are used to the DAO Pattern. I think it is possible to experiment with a new way where Managers are injected into POJOs. I also think it's possible that one day I'll create an AppFuse plugin for Grails.
I'd be very interested in trying to integrate Gorm into AppFuse and allowing the backend code to be greatly simplified. Groovy is a pretty damn cool language. Do you think GWT will support Groovy in the future? I think I'd really enjoy developing AppFuse 3.0 with a Gorm/Groovy backend and front-end options of GWT-Ext, Flex (or OpenLaszlo) and Appcelerator (possibly). Matt On 2/26/08, Sanjiv Jivan <[EMAIL PROTECTED]> wrote: > Matt, > I've see from your blog that you've been dabbling with grails. Given the > ease which service's call make calls dynamically to carry out persistence > related operations without an API explosion, has your take on the strict > service API -> DAO delegation changed. I gotta admit that that while it > looked like a clean delineation at the start of my project, it really became > cumbersome as my project got really large and I ended up with generic API's > that carried out the sort / filter / page / CRUD operations across any > entity. > > Would like to hear what others think in this matter as well. > > Thanks, > Sanjiv > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
