This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
No announcement yet.
What can ROO do to stand out and actually be the goto option for Java projectsPage Title Module
A quick look at Play highlights the two biggest Spring Roo weaknesses
Compiling Aspect files (far too slow for me)
Modifying the CRUD web interface and in particular manipulating Dojo and jspx tags etc.
To be honest I was completely happy committing to Spring Roo for my next project (as I mentioned http://forum.springsource.org/showth...ercial-project). However something like Play ups the stakes again for me - if I can still use JPA whilst being able to more quickly create and customise the web interface...
For someone new to Spring Roo and with some Java and web development experience I believe the Dojo/jQuery distinction is going to be key. I am now a bad jQuery and Dojo developer (I am happy to tinker a little with both after my Spring Roo experience). If I had the choice before chosing Spring Roo I may well have chosen to stick with jQuery and work with Play.
So for me the number one answer to what does ROO need to do to be a goto option - provide the option to use jQuery for the web interface.
In fact I would feel that this is a more important choice for web developers (which may well be the biggest Roo user group?) than the ActiveRecord/DAO choice.
play eclipsify , netbeansify etc. generate project files to allow you to import in your ide. You cannot do java dev without IDE support and play makes it painless. Moreover performance is much better compared to other frameworks. Google for performance comparisons with node etc.