Spring roo Vs (Wicket and Spring)

Question

Spring roo is new framework and I found it very interesting. I have been working on web application for last 3-4 years and Always found JSPs are hard to maintain across teams if

Answer 1

I've seen a demo of Roo a few months ago. It looks a lot like Grails (another spring technology), except that instead of creating artifacts for the Groovy language, you create them for Java.
Still it enforces good practice and makes you apply the MVC pattern in a clean way.

Personally, the demo didn't make me change my preferred toolkit (Grails), but that's because I can achieve faster results with Groovy (parsing xml for example is much more "painful" in Java than in Groovy). Also, with Grails I can see the changes I make instantly without having to recompile my entire project and relaunch the application each time I want to see the results. Last but not least, in Grails you have tons of plugins to make fancy Ajax websites (ZK for example, if you want to avoid Javascript, but there are plugins for GWT, Yahoo, Dojo, etc...).

So, if you don't want to learn Groovy (which is not too difficult if you already know Java), Roo is the way to go to build clean web projects with all the power of Hibernate and Spring.

I hope this helps...

Answer 2

Why use Roo when one can build something w/ GWT and end up w/ a far richer better outcome and without the constraints of Roo and its architecture. Spring Web Flow is yesterdays technology.

Answer 3

Our current project uses Spring and Wicket, we have always used Spring but switched to Wicket a year ago. Few advices:

• Get the "Wicket in Action" book.
• The user mailing list is very helpful.
• Make sure you understand Wicket's programming model especially the session serialization related stuff (the book does not help enough in this area IMHO).
• Wicket is good at building stateful pages, it requires more work to build stateless pages.
• There are some good UI widgets available like inmethod DataGrid.
• It's easy to inject your Spring beans in your pages or components.

Spring Roo is still in beta (1.0 M2), so it may be a little early. We also considered Tapestry 5 but we thought it was a bit young a year ago.