On Tue, Feb 26, 2008 at 6:53 PM, Matt Raible <[EMAIL PROTECTED]> wrote:
> 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. I think this will be a refreshing proof of concept, if nothing else, and possibly more. > > Do you think GWT will support Groovy in the future? > I think Groovy has been around for a while but its use in Grails is why really made it shine as Grails allows you to now really cut down on the redundant service API's and DAO's and modes the whole service to persistence tier a lot cleaner with a much lower total LoC. Atleast to me that was the biggest appeal of Grails. I'm not in particular attracted to the scriptish / dynamic nature in general for building larger server side apps. Thats exactly why I hated Jython for anything more that writing scripts. I think the server side benefits a lot by the dynamic nature of Grails courtesy of Groovy but I don't feel there is a strong case for using Groovy with GWT. The typesafe nature of Java is infact a strength of GWT. If people want a more dynamic programming environment, they'll probably be programming in Javascript itself :) I'm sure there are some Groovy language fans would might want to see Groovy support in GWT just because they like programming in a particular language, but I don't see a compelling case. I have not yet come across such a request from a user. > 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] > >
