新 Java 项目的速度
java 的Velocity 似乎已经存在相当长一段时间了。对于那些认真尝试强制将显示/视图代码与模型代码分离的人。它似乎是一个非常简单但功能强大的替代方案。
对于新项目，您会建议速度，还是有更新的替代方案？
它看起来至少对电子邮件模板很有用，但是您会全力以赴并将其用于整个 Web 应用程序吗？
It seems velocity for java has been around for quite some time. For someone serious about trying to enforce a separation of their display/view code from their model code. It appears to be quite a simple but powerful alternative.
For new projects would you recommend velocity, or are there newer alternatives?
It appears at least useful for email templating, but would you go the whole hog and use it for an entire web application?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我认为这是一个很好的模板解决方案。我正在开发一个应用程序，该应用程序将 Velocity 用于电子邮件和 HTML 页面，并且效果很好。我可以根据第一手经验全心全意地推荐它。
不要因为它的年龄而推迟。我认为这是一项成熟的可靠技术。
I think it's a fine templating solution. I'm working on an app that uses Velocity for both e-mail and HTML pages, and it works great. I can recommend it wholeheartedly from first-hand experience.
Don't be put off by its age. I think it's a solid technology that's mature.
我肯定会推荐成熟的之一（Velocity 或 Freemarker）。 Java 模板中确实没有任何其他值得注意的名字，这是有充分理由的。两者仍然是深受支持的产品。
哦，如果您打算在整个 Web 应用程序中使用 Velocity（我也推荐），那么请务必查看 VelocityTools 项目！
I'd definitely recommend one of the mature ones (Velocity or Freemarker). There aren't really any other notable names in Java templating for good reason. Both are still solidly supported products.
Oh, and if you are going to use Velocity for your whole webapp (which i also recommend), then be sure to check out the VelocityTools project!