as impressed as I am with Grails, I should point out that it really makes a difference if you are building a typical web app - 3 tier architecture with DAOs, Service Layer and pretty much CRUD.
If you don't want that, then Grails is not for you. As much as I see its value, I have to point out that there is a learning curve to learning Groovy and the way Grails does things. My app has a requirements where the war file is created ONCE and then pushed through the environments and eventually ending up in prod (with various test phases along the way). This is not the preferred Grails way however and I spent many days circumventing the build system to get it to do what I want (and I still feel its a hack). I really, really like Groovy. However, it will take time to get used to and use it appropriately. I still forget the sort of magic you can do (because its so non-obvious). Like with maps (reference key as if attribute) and Expando and MockFor and StubFor, etc... So I guess what I'm saying is do your due diligence for suitability, then plan some time to learn it and make mistakes - don't push for it on the first business critical project that comes along because you think you can develop it quickly (because thats what you heard on a forum somewhere). Thanks R -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
