在Tomcat中部署吊带+兔崽子的优势是什么? [英] Advantages of deploying sling + jackrabbit on tomcat?
问题描述
有几个导游如何部署 Apache的吊索上的的:// tomcat的。 apache.org/相对=nofollow>的Apache Tomcat 。你为什么要这么做?据我了解,这将意味着你的tomcat中部署OSGi容器菲利克斯,从而使用部署系统从Tomcat大不相同。更令人困惑的:内菲利克斯吊带使用 的码头作为servlet引擎 - 所以你正在部署中的一个servlet引擎servlet引擎。 8}那么,什么是这样做的点,而不是仅仅运行的启动板作为Java独立的应用程序?
There are several guides how to deploy Apache Sling on Apache Tomcat. Why would you want to do that? As I understand it, this would mean you are deploying the OSGI container Felix within tomcat, and thus use a deployment system quite different from Tomcat. Even more confusing: within Felix Sling uses Jetty as servlet engine - thus you are deploying a servlet engine within a servlet engine. 8-} So, what is the point of doing this, instead of just running the launchpad as a Java standalone application?
推荐答案
有些人想在Tomcat或其他servlet容器部署吊带或者是因为他们具有运行有其他应用程序和它们$有一个统一设置p $ PFER,或因为他们熟悉这些容器在监测方面,运营等。
Some people want to deploy Sling on Tomcat or other servlet containers either because they have other applications that run there and they prefer having a unified setup, or because they are familiar with these containers in terms of monitoring, operations etc.
这就是为什么我们提供吊带既作为一个战争文件和自足运行的JAR。
That's why we provide Sling both as a war file and self-contained runnable jar.
如果你没有特别原因需要使用Tomcat或者其他servlet容器,使用自足吊带运行的JAR可能是最好的 - 这是重量轻,易于安装,并提供完全相同的功能。
If you have no specific reason to use Tomcat or another servlet container, using the self-contained Sling runnable jar is probably best - it's lightweight, easy to install and provides the exact same features.
这篇关于在Tomcat中部署吊带+兔崽子的优势是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!