Spring roo Vs (Wicket and Spring)

First, Spring Roo is a code generator tool (similar to Grails commands system):

_{(source: springsource.com)}

Second, Spring Roo applications currently use Spring Web Flow for the view and Spring for the glue.

So, while you can compare (Spring Web Flow + Spring) and (Wicket + Spring), the later combo doesn't offer anything comparable to Roo out of the box (maybe AppFuse or AppFuse Light but you didn't mention them and they are third-party projects).

In other words, I don't think that "Spring Roo vs (Wicket and Spring)" makes sense.

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.

Spring Roo 1.0.0 (GA) has now been released, complete with around 100 pages of documentation.

If you're wondering about what Roo is and why use it, I recommend you take a read of the introductory chapter of the reference guide. It covers this and more.

@Antony, GWT support is a major priority for Roo and something I am currently working on. Expect to see some interesting integration in the very near future.