Spring roo Vs (Wicket and Spring)

Ketan Khairnar picture Ketan Khairnar · Jul 9, 2009 · Viewed 15.3k times · Source

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 everyone is not disciplined enough about separation of markup and serverside logic. I have used JackBe/BackBase in last projects and I enjoyed xml templates working as views. This was much better than JSPs. But I couldnt automate webtests through selenium for backbase.

I would be surely using Spring MVC (-view), Hibernate on the backend. I found Wicket as good alternative. Have you used wicket along with Spring and what was your experience?

Answer

Pascal Thivent picture Pascal Thivent · Jan 24, 2010

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

alt text
(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.