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

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.