appfuse vs roo - 你会用什么？ [英] appfuse vs roo - what would you use

问题描述

Appfuse vs. Roo，你会用什么以及为什么？

Appfuse vs. Roo, what would you use and why?

每个人的最佳点是什么。

What are the sweet spots of each.

推荐答案

根据我给 TheServerSide主题就此问题...：

As per the answer I gave to TheServerSide thread on this issue...:

AppFuse旨在为您的新项目提供单一的初始支架。这类似于Maven原型或Eclipse的新项目功能，因为您在新项目开始时运行它们，然后继续维护脚手架代码。一旦你运行一次，脚手架系统就没有进一步参与你的项目了。

AppFuse aims to provide a single initial scaffold of your new project. This is similar to Maven archetypes or Eclipse's "new project" features in that you run them once at the start of a new project and then you maintain the scaffolded code going forward. The scaffold system has no further involvement in your project once you've run it once.

另一方面，Roo提供了一个往返感知的活动代码生成器您在给定项目上的长期使用情况。因此，Roo在初始创建时以及随后修改项目时都会提供价值。

Roo, on the other hand, provides a round-trip aware active code generator for your long-term usage on a given project. As such Roo offers value both at initial creation time as well as whenever you are modifying the project going forward.

实际上，这意味着当您改进项目时，Roo将自动维护某些文件。举一个简单的例子，当你添加（或删除）一个字段时，Roo会自动为你更新toString，getters / setters，JSP页面等。它还提供命令，以便您以后添加新功能。因此，如果您在创建项目六个月后需要添加安全性，那么只需安全设置。或者，如果您需要发送电子邮件，只需 http://static.springsource.org/spring-roo/reference/html/command-index.html#command-index-email-sender-setup 。对于许多其他功能领域也有类似的命令，例如Spring Web Flow，JUnit，Selenium，常见的JPA提供程序等。只要你喜欢就推迟决定，Roo只会在你要求的时候添加这些功能。它们（它也将自动在项目中使用这些新功能）。

In practical terms this means as you evolve your project, Roo will automatically maintain certain files. To take a simple example, when you add (or remove) a field, Roo will update the toString, getters/setters, JSP pages etc for you automatically. It also offers commands so you can add new capabilities later. So if you need to add security six months after you created the project, you just "security setup". Or if you need to send emails, you just "http://static.springsource.org/spring-roo/reference/html/command-index.html#command-index-email-sender-setup". There are similar commands for many other capability areas well, such as Spring Web Flow, JUnit, Selenium, common JPA providers etc. You just defer the decision as long as you like, and Roo will only add those capabilities at the time you ask for them (and it will also automatically use those new capabilities in your project).

还有许多其他差异。 Roo允许通过用户开发的附加组件，它提供高度可用外壳，它允许您逐步构建一个新项目并仅在需要时添加功能，它广泛支持主要Spring技术的最新版本，它附带一个SpringSource开发的（因此得到支持）应用程序架构等等。

There are many other differences as well. Roo allows extension via user-developed add-ons, it offers a highly usable shell, it allows you to incrementally build a new project and add features only when required, it extensively supports the latest versions of the major Spring technologies, it comes with a SpringSource-developed (and therefore endorsed) application architecture and so on.

阅读Roo参考指南的简介章或只是完成 10米inute test 项目将说明他们的方法非常不同。

A read of the Roo Reference Guide's Introduction Chapter or simply completing the ten minute test project will illustrate they are very different in approach.

这篇关于appfuse vs roo - 你会用什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！