爆炸战争的优点/缺点 [英] Advantages/Disadvantages to exploded wars

问题描述

我今天读到的一个问题的答案建议将应用程序部署为爆炸式WAR。它让我思考。

An answer to a question I read today suggested deploying an application as an exploded 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以扩展形式部署应用程序而不是打包它有什么好处？

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。）混乱 - 丰富的应用程序/网络服务器遍布整个文件（有些人真的很讨厌这个）。

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

I倾向于爆炸原型Dev工作，然后移动到正确的包装，我接近珠三角。

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

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