Grails and Roo
I will be talking lot of technology jargons here. Get ready for it.
I always was hating frameworks like Struts, Spring, Hibernate (lost count of how many more), because of the amount of meaningless XML configuration like hbm.xml, struts-config.xml and applicationContext.xml we have to maintain.
I realized that lot of other people were also hating it. Enter AOP, Spring 3.0, Hibernate 3.0 and JPA, life became slightly simple. We don’t need to use configuration files. But still I was not happy, because we still need to worry having a webserver and database server to do even simple webdevelopment for learning purpose.
There is framework like Ruby on Rails which can help you development rapidly, a fairly decent website in 20 mins. The only pitfall is it does not work with J2EE containers; it has its own webserver and language (yet another language to learn).
Enter 2 new frameworks, Grails and Roo which can provide hope to impatient like me and still follow new standards like AOP and JPA. I need to warn you that both these frameworks are very new and bug filled, but will help you in understanding the future of web development.
Both these technologies follow, “Convention over Configuration” philosophy, google it out for the meaning, will you.
Both of these frameworks will provide complete tools needed for web development, an embeded tomcat j2ee container, hsql inmemory database. In both of them, all you have to do is, create a domain object and it will create tables in the backend and create Create, Read, Update and Read web operations aka CRUD for free to start off.
Grails and Roo can be considered for new “green field” projects but not advisable for migrating existing projects. My personal preference is Grails, because you have ton of documentation on the web, some useful links, I sourced are,