转换现有的 spring 项目以使用 roo help
我有一个项目已经使用了非常好的 Spring 最佳实践。它使用 freemarker 而不是 JSP，我确信我的控制器操作将与 roo 生成的操作有很大不同。它仍然是基于休息的，但我的方法命名约定从外观上看非常不同。我的看起来更像是 Rails/Grails。
我也直接使用 Hibernate - 而不是 JPA。该项目从 2009 年开始就已经存在，当时，老实说，我更喜欢 XML 映射，而不是 JPA 注释。
不管怎样，我很好奇我是否可以升级这个项目以使用 ROO，或者我是否应该远离它。任何人都可以提供提示/建议/指导 - 即使该建议只是远离？
谢谢
I have a project that uses really good spring best practices already. It uses freemarker though instead of JSP, and I am sure my controller actions are going to be much different than the ones that roo generates. It's rest-based still, but my naming conventions of methods are very different by the looks of things. Mine look a lot more like rails/grails.
I also used Hibernate directly - not JPA. The project has been around since 2009, and at the time, I honestly liked the XML mappings a lot more than the JPA annotations.
Anyway, I was curious if I could upgrade this project to use ROO, or if I should stay clear of it. Can anyone offer tips/suggestions/guidance - even if that advice is to simply stay away?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为将项目切换为使用 Roo 的唯一方法是使用 Roo 从头开始构建它。也许对你的数据库进行逆向工程。但我认为这对你来说不是正确的方法。所以我可以给你唯一的建议 - 等待下一个项目并从头开始使用 Roo 构建它（如果你仍然想尝试一下）。
I suppose there is the only way to switch your project to use Roo — build it from scratch using Roo. Maybe with reverse engineering of your DB. But I suppose it is not proper way for you. So I can give you the only advise — wait for the next project and build it with Roo from scratch (if you still want to give it a try).