Tomcat 和 Jetty 哪一个更适合 Vaadin 应用程序?
我正在使用 Vaadin 框架和 Maven2 开发一个应用程序。就我个人而言,我不想选择GAE。我目前正在为我的应用程序使用 Tomcat 6.0 应用程序服务器。杰蒂怎么样?
- Jetty中的Tomcat在设置、性能、稳定性等方面有什么区别?
- 托管提供商支持哪一种?
- 哪一个更容易配置?
任何帮助表示赞赏。
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
如果您需要自我可执行文件,那么您应该使用 jetty。如果您要将您的应用程序部署到托管公司,可能 tomcat 会更容易,因为它已经在那里,您只需将您的 war 文件拖放到适当的文件夹中即可。
我不确定您是否可以在所有托管服务上运行嵌入式码头,因为托管服务码头的限制可能无法工作。
if you need self executable then you should use jetty. If you are gonna deploy ur app to a hosting company, probably tomcat will be easier as it will be already there and you need to drop ur war file to the appropriate folder only.
I am not sure if you can run an embedded jetty on all the hosting services because of the limitation of the hosting service jetty may not work.
Tomcat 和 Jetty 是非常相似的产品,具有相同的功能集。它们都实现了 Java Servlet & Servlet。 JavaServer Pages 规范,包含 Web 服务器,并且有不错的文档。两者都是开源、免费且流行的。它们都执行相同类型的工作,具有相似的可扩展性,并且经常更新。它们都适用于 Vaadin 6。
比较 Tomcat 和 Jetty 就像比较本田思域和丰田花冠一样。他们的相似之处多于不同之处。它们都与 Glassfish 和 JBoss 规模更大,许多功能远远超出了 Servlet 和 Web 服务。
正如另一个答案中提到的,Tomcat 和 Jetty 之间的少数区别之一是 Jetty 设计为嵌入在另一个 Java 应用程序中运行以及自行运行。相比之下,Tomcat 仅作为其自己的应用程序运行。
这种差异的后果是,当在 Eclipse 中进行 Vaadin 工作时,人们通常使用 Web 工具平台 (WTP) 插件包,用于在作为其自己的应用程序运行的 Eclipse 和作为其自己的应用程序运行的 Tomcat 或 Jetty 之间建立桥梁,并且相互通信以使开发更容易。其他人不喜欢运行 WTP,而是选择将 Jetty 配置为在 Eclipse 中运行,作为 Eclipse 的一部分,而 Tomcat 则无法做到这一点。这些方法都有优点和缺点,但这是 Tomcat 和 Tomcat 之间为数不多的真正区别之一。 Jetty 在进行 Vaadin 开发时。
Tomcat and Jetty are quite similar products, with the same kind of feature set. They both implement the Java Servlet & JavaServer Pages specs, contain a web server, and have decent documentation. Both are open-source, free-of-cost, and popular. They both do the same kind of work, have similar scalability, and are frequently updated. They both work well for Vaadin 6.
Comparing Tomcat and Jetty is like comparing Honda Civic and Toyota Corolla. They are more alike than different. They both contrast with products like Glassfish and JBoss which are much bigger with many features going well beyond Servlets and web serving.
As mentioned in the other answer, one of the few distinctions between Tomcat and Jetty is that Jetty is designed to be run embedded inside another Java app as well as run by itself. Tomcat in contrast runs only as its own app.
The ramification of this difference, is that when doing Vaadin work in Eclipse, folks commonly use the Web Tools Platform (WTP) package of plugins to bridge between Eclipse running as its own app and Tomcat or Jetty running as its own app, and yet talking to each other to make development easier. Other folks prefer not to run WTP, and instead choose to configure Jetty to run within Eclipse, as a part of Eclipse, which is not possible with Tomcat. Each of these approaches have pros and cons, but this is one of the few true differences between Tomcat & Jetty when it comes to doing Vaadin development.