Spring Roo 的替代用法
Spring Roo 是否应该只是一个快速开发 Web 应用程序的工具，这要归功于所有的脚手架、源代码生成和类似的东西，例如 grails for groovy。
或者它可以用作构建企业应用程序的源代码生成器/osgi平台吗？我的意思是，有源代码生成器，在开始新项目时仅生成基于元数据定义的域模型和轻型 DAO 层，并且您必须坚持目标 - 创建一个 Web 应用程序。但也有生成器，可以生成整个 DAO 和服务层 - 对于大型应用程序的迭代开发过程来说非常有用 - 并且您不会受到其他限制，您只是使用它来逐步构建企业应用程序。有了这个，您就可以真正构建一个可长期维护的大型企业应用程序/平台。
此外，OSGI 模型还可以以某种方式使用，例如，您可以开发一个核心门户应用程序，其中包含您可以插入的社交办公插件包等。
我的观点是，Java 开发需要“红宝石化”。我的意思是 Ruby on Rails 环境，其中所有内容都是统一和标准化的。一个可以在某个时候统治 Java 世界的平台:-)
is Spring Roo supposed to be only a tool for rapid development of web applications, thanks to all that scaffolding, source code generation and similar stuff, such as grails for groovy.
Or can it be utilized as a source code generator / osgi platform for building enterprise applications ? What I mean is, that there are source code generators, that generate only domain model and light DAO layer based on metadata definition when starting a new project and you have to stick to the objective - create a web app. But there are also generators, that generate the entire DAO and service layer - fantastic for iterative dev process of bigger apps - and you are not restricted otherwise, you are just using it to build you enterprise app step by step. With this you can really build a huge enterprise applications / platforms that will be maintainable for a very long time.
Also the OSGI model could be employed in a way, that you might develop a core portal application for instance, with a package of social office addons that you may plug in, etc. etc.
My point is, that Java development needs to be "Rubyfied". I mean Ruby on Rails environment where you have everything unified and standardized. A platform that could rule the java world some time :-)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
由于 Thomas 和 @jhericks 毁掉了 Spring Roo，我想说我实际上喜欢它主要是因为它不是一个框架。 Roo 还（现在）支持多 Maven 模块。
回答你的问题：Spring Roo 不是框架。这是代码生成。
所以，是的，它是一个代码生成平台，不仅适用于 Web 应用程序，而且适用于任何 Java 应用程序。
有些人不喜欢 Roo 有几个原因：
在使用 Spring Roo 构建了多个应用程序之后，我可以说它的最大价值是它的 ORM 生成能力和 DataOnDemand 测试生成。
除此之外，Spring Roo 实际上只是 Spring *。
像 Play 和 Ruby on Rails 这样的框架并不是真正的“Java 方式”。我看到的大多数 Java（Web）应用程序都是库的组合，而不是一个巨大的框架。
Since Thomas and @jhericks trashed Spring Roo I'm going to say I actually like it mainly because its not a framework. Roo also (now) support multi-maven modules.
To answer your question: Spring Roo is not framework. It is code generation.
So yeah it is a code generation platform not only for web apps but any Java app.
There are couple of reasons why some people don't like Roo:
After building several applications with Spring Roo I can say its greatest value is its ORM generating abilities and its DataOnDemand test generation.
Other than that Spring Roo is really just Spring *.
Frameworks like Play and Ruby on Rails are just not really the "Java Way". That is most Java (Web) Apps I see are combination of libraries and not a giant framework.
据我所知，Spring Roo 旨在成为 Web 应用程序的 RAD/引导工具。路线图上缺少一些主要功能，而这些功能使其在企业应用程序环境中真正有用。一个例子是多模块 Maven 支持。
这篇颇具争议性的文章及其后续文章很好地总结了如何我对 Roo 和 Seam Forge 等类似项目有感觉。
如果您正在寻找类似于 Java 的 RoR 的东西，请查看目前似乎势头强劲的 Play 框架。
As far as I experienced, Spring Roo is meant to be a RAD/bootstrapping tool for web applications. There are some major features missing and not on the roadmap that would make it truly useful in an enterprise application context. An example being multi-module Maven support.
This rather polemic article and its follow ups summarize quite well how I feel about Roo and similar projects like Seam Forge.
If you are looking for something RoR-like for Java check out the Play Framework that currently seems to gain momentum.