Spring Roo Vs(Wicket和Spring) [英] Spring roo Vs (Wicket and Spring)

问题描述

Spring Roo是新框架，我发现它非常有趣.我从事Web应用程序的工作已经有3-4年的时间，并且始终发现，如果每个人对标记和服务器端逻辑的分离不够严格，那么跨团队就很难维护JSP.我在上一个项目中使用过JackBe/BackBase，并且喜欢将xml模板用作视图.这比JSP更好.但是我无法通过硒自动进行Web测试以实现后台测试.

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.

我肯定会在后端使用Spring MVC(-view)，Hibernate.我发现Wicket是不错的选择.您是否曾在Spring中使用wicket，您的经历是什么?

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?

推荐答案

首先，Spring Roo是一个代码生成器工具(类似于 Grails命令 系统):

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

_{(来源: springsource.com )}

_{(source: springsource.com)}

第二，Spring Roo应用程序当前将Spring Web Flow用于视图，将Spring用于胶水.

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

因此，尽管您可以比较(Spring Web Flow + Spring)和(Wicket + Spring)，但是后面的组合并没有提供与Roo相当的功能(也许 AppFuse轻，但您没有提及它们，它们是第三方项目).

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).

换句话说，我认为"Spring Roo vs(Wicket和Spring)"是没有道理的.

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

这篇关于Spring Roo Vs(Wicket和Spring)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！