[英]Tomcat vs Pivotal tc Server
Could anyone advise as to the pros and cons of using Pivotal tc Server as opposed to just vanilla Tomcat for a Spring-MVC Java web application? 任何人都可以建议使用Pivotal tc Server的优缺点,而不仅仅是使用Spring-MVC Java Web应用程序的vanilla Tomcat? Could find very little about Pivotal other than on their website and the fact it's packaged as part of the Spring Tool Suite.
除了在他们的网站上发现很少关于Pivotal以及它作为Spring Tool Suite的一部分打包的事实。 This lack of info is making me a bit wary about being dependent on it...
缺乏信息让我对依赖它有点担心......
Background: Am preparing the development environment for a Spring-MVC project and currently evaluating whether to use the packaged Spring Tool Suite (STS) or just start with the latest Eclipse (possibly combined with the Eclipse STS plugin ). 背景:正在为Spring-MVC项目准备开发环境,目前正在评估是使用打包的Spring Tool Suite(STS)还是仅使用最新的Eclipse(可能与Eclipse STS插件结合使用)。 Came across Pivotal tc Server as one of the optional components in this plugin.
作为此插件中的可选组件之一,我将Pivotal tc Server作为其中一个。
Pivotal tc Server contains all of vanilla Tomcat, and has a few optional extensions designed to make it easier to deploy and maintain. Pivotal tc Server包含所有vanilla Tomcat,并且有一些可选扩展,旨在使其更易于部署和维护。 Broken out into three groups, the diff looks like this:
分为三组,差异如下:
Configuration extensions (No altered code, just config changes we implement) 配置扩展(没有改变代码,只是我们实现的配置更改)
Code Extensions 代码扩展
Add-Ons 加载项
FYI on the tag thing, there's still the old "springsource-tc-server" tag. 标签上的FYI,还有旧的“springsource-tc-server”标签。 SpringSource is now Pivotal.
SpringSource现在是Pivotal。 (Can/should we update the tag or add a new one?)
(可以/我们应该更新标签还是添加新标签?)
Hope this helps. 希望这可以帮助。
SpringSource tc Server is an enterprise version of Apache Tomcat, the widely used Web application server. SpringSource tc Server是Apache Tomcat的企业版,Apache Tomcat是广泛使用的Web应用程序服务器。 SpringSource tc Server is hardened for enterprise use and is coupled with key operational capabilities, advanced diagnostics, and is backed by mission-critical support.
SpringSource tc Server经过强化,可供企业使用,并与关键操作功能,高级诊断功能相结合,并由关键任务支持提供支持。
SpringSource tc Server is designed to be a drop in replacement for Apache Tomcat, ensuring a seamless upgrade path for existing custom-built and commercial software applications already certified for Tomcat. SpringSource tc Server旨在成为Apache Tomcat的替代品,确保为已经通过Tomcat认证的现有定制和商业软件应用程序提供无缝升级途径。 Maintaining this level of compatibility enables our customers to add the business-critical functionality they need to more effectively run and manage their applications with the least amount of effort.
保持这种级别的兼容性使我们的客户能够以最少的工作量添加他们所需的业务关键功能,从而更有效地运行和管理他们的应用程序。
find more information at http://static.springsource.com/projects/tc-server/6.0/getstart/cgsdiffs.html 有关更多信息,请访问http://static.springsource.com/projects/tc-server/6.0/getstart/cgsdiffs.html
This doesn't answer your question about the pros and cons, but I found this site really helpful in getting tc server up and running in STS. 这不能回答你关于优缺点的问题,但我发现这个网站真的有助于在STS中启动和运行tc服务器。 http://sosiouxme.wordpress.com/2012/04/06/the-missing-guide-to-creating-and-modifying-tc-server-instances-for-sts/
http://sosiouxme.wordpress.com/2012/04/06/the-missing-guide-to-creating-and-modifying-tc-server-instances-for-sts/
To me it seems a high price for just getting a servlet container. 对我来说,获得一个servlet容器似乎是一个很高的代价。 Specifically, it (the tc server ) seems to try to mimmic a production quality application server (servlet engine) with the added features.
具体来说,它( tc服务器 )似乎试图模仿具有附加功能的生产质量应用服务器(servlet引擎)。 For development it seems overkill.
对于发展而言似乎有些过分。 You could just as well use Tomcat stand-alone or Glassfish or Jetty .
您也可以使用Tomcat独立或Glassfish或Jetty 。
I would choose the tc server if my target was some cloud implementation of Cloud Foundary that was ultimately my target production deployment environment. 如果我的目标是Cloud Foundary的云实施,那么我会选择tc服务器 ,这最终是我的目标生产部署环境。
Finally, I just noticed that the tc server is a commercial offering. 最后,我只是注意到tc服务器是商业产品。 So, the licensing implications should the features become integral to your delivery, might have a cost that your project would not bear: https://www.cdw.com/shop/products/SpringSource-tc-Server-Spring-Edition-license/2156278.aspx
因此,如果功能成为您交付不可或缺的一部分,那么许可意义可能会产生您的项目无法承担的成本: https : //www.cdw.com/shop/products/SpringSource-tc-Server-Spring-Edition-license /2156278.aspx
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.