分解WAR文件的优点/缺点 [英] Advantages/Disadvantages to exploded WAR files

问题描述

我今天阅读的一个问题的答案建议将应用程序部署为爆炸式(未压缩)战争.这让我开始思考.

An answer to a question I read today suggested deploying an application as an exploded (unzipped) WAR. It got me thinking.

我对JBoss/Tomcat进行的每一次部署都是使用WAR/ EAR 文件.至少据我所记得.

Every deployment I've ever done to a JBoss/Tomcat has been with a a WAR/EAR file. At least as far as I can remember.

这些年来我一直在犯一个错误吗?

Have I been making a mistake all these years?

以扩展形式而不是打包形式部署应用是否有优势?

Are there advantages to deploying an app in its expanded form rather than packaged up?

推荐答案

我认为这是我提到另一个问题中爆炸的WAR的答案.爆炸的WAR易于浏览，您可以更快地部署应用程序的部分"(具体取决于我们的Web/App服务器如何处理)，例如替换单个资源，例如JSP页面.但是，它可能有一些缺点:

I think that was my answer mentioning the exploded WAR in the other question. Exploded WARs are easier to navigate and you can deploy 'parts' of your application that much quicker (depending on how our Web/App server deals with this), e.g. Replace a single resource like a JSP page. However it can have some drawbacks:

1.)您真正运行的是哪个版本? 嗯，我现在不太确定"

1.) What version are you really running? "Hmmm, I'm not really sure now"

2.)安全性-您是否拥有适当的爆炸格式许可权?

2.) Security - Do you have the right permissioning in place for the exploded format?

3.)麻烦-大量的文件散布在漂亮的应用程序/Web服务器上(有些人真的很讨厌).

3.) Messiness - Files galore spread out all over your nice app/web server (some people really hate this).

我倾向于分解进行原型开发工作，然后在离PRD越近的地方进行适当的包装.

I tend to go exploded for prototype Dev work and then move to proper packaging the closer to PRD I get.

这篇关于分解WAR文件的优点/缺点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！