爆炸式 WAR 文件的优点/缺点 [英] Advantages/Disadvantages to exploded WAR files
问题描述
我今天读到的一个问题的答案建议将应用程序部署为分解(解压缩)WAR.这让我开始思考.
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.
这些年我犯错了吗?
以扩展形式部署应用比打包部署有优势吗?
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:
版本控制 - 您实际运行的是哪个版本?嗯，我现在不太确定"
Versioning - What version are you really running? "Hmmm, I'm not really sure now"
安全 - 您是否为展开的格式提供了适当的权限?
Security - Do you have the right permissioning in place for the exploded format?
混乱 - 大量文件散布在您漂亮的应用/网络服务器上(有些人真的很讨厌这样).
Messiness - Files galore spread out all over your nice app/web server (some people really hate this).
底线:我倾向于为原型开发工作而爆炸，然后在离 PRD 越近的地方进行适当的包装.
Bottom line: I tend to go exploded for prototype Dev work and then move to proper packaging the closer to PRD I get.
这篇关于爆炸式 WAR 文件的优点/缺点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
