罗+ GWT - 有利于开发吗？
我已经从事 GWT 项目几个月了，我决定尝试一下 Spring Roo 的东西。我注意到从 0 到与 Roo 相同的结果可能需要很长时间。我的第一个想法是：“这太棒了”！
但是，一旦您设置了几个持久实体并且 Roo 为 GWT 生成了脚手架，您就拥有了一些非常基本的布局，但代码量很大。然后呢？您停止使用 Roo 并继续手动操作吗？用户界面很好，但非常基础。
我不想手动修改东西，因为我不想弄乱 Roo 一代。所以我只是删除了所有 Roo 的东西，然后我又陷入了“慢”模式。
有人用 Spring Roo + GWT 创建了一个相对复杂的应用程序吗？
我对 Spring 不太熟悉，所以它可能会变得丑陋（习惯于 GWT + GXT + DataNucleus + Guice/Gin + Gilead）。在这种情况下，你建议远离 Roo 吗？
从我的角度来看，Roo 非常适合生成域层样板，因为这非常乏味，但仅此而已。
I've been working on GWT projects for a few months now and I decided to give a try to this Spring Roo thing. I noticed that to go from 0 to the same results as with Roo it can take very long. My first thought was: "this is great"!
But once you've setup a couple of persistent entities and Roo generates your scaffolding for GWT and you have some very basic layout but a huge amount of code. Then what? You stop using Roo and go on by hand? The UI is nice but is very basic.
I don't want to modify things by hand since I don't want to mess up Roo generation. So I just remove all Roo stuff and I fall to the "slow" mode again.
Has anyone created a relatively complex application with Spring Roo + GWT?
I'm not very familiar with Spring so it might get ugly (used to GWT + GXT + DataNucleus + Guice/Gin + Gilead). Do you recommend staying away from Roo in such a case?
From my point of view, Roo is good for generating the domain layer boilerplate since this is very tedious, but that's it.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
根据我的经验，Roo 对于快速原型设计和概念验证非常有用。
保持数据模型与 JPA/DAO 层同步也很有用。
但事实上，对于服务级别和 UI 设计方面更复杂的业务需求，您必须切换到简单的旧式手动编码。
From my experience, Roo is very useful for quick prototyping and proof of concept.
It's also useful to maintain the data model in sync with JPA/DAO layer.
But indeed, for more complex business requirements at service level and UI design, you'll have to switch to plain old manual coding.
以我的经验。 roo + gwt 会让你的构建周期非常长（当你有足够的实体时，还没有使用 springMVC 尝试过，也许它也很慢）。 spectj 构建以某种方式导致了它。所以要打破它。我不会再这样做了。如果您不相信我，请创建一个包含 100 个实体（每个实体有 5 个字段）的示例项目。然后打开 AJDT 控制台并清理项目...然后喝杯咖啡休息一下什么的;-)
in my experience. roo + gwt gets you extremly long build cycles (when you have enough entities, haven't tried it with springMVC maybe it's slow too). the aspectj build is somehow causing it. so to break it down. i wouldn't do it again. if you don't believe me create a sample project with 100 entities with 5 fields each. Then open the AJDT-console and clean the project ... and have a coffee break or something ;-)