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

How soon with Roo support GWT? I think that the use of GWT by Roo makes it a huge win for GWT and Roo!

Answer 2

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.

Answer 3

It completely depends on what your requirements are. If it's a small site then Component Oriented frameworks like GWT or Wicket are a must as they make things really easy.

Answer 4

Roo and GWT are available today in pre-release form. In my opinion, definitely not ready for prime time.

Answer 5

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.

Answer 6

I was at the SpringOne conference in Amsterdam earlier this year when they announced Roo. My impression (and that of my colleague who was there) was that Roo was good if you were generating a web-based CRUD application every few weeks - they pitched it as the pure Java version of Grails (which is RoR for Java).

Didn't look interesting for anyone else - but that's just an opinion.