Tomcat创建WEB-INF / lib，但不会爆炸战争文件（GWT） [英] Tomcat creates WEB-INF/lib but doesnt explode war files (GWT)

问题描述

有人看到这样的东西：

我使用的脚本基本上是使用ant退出应用程序，将新的war文件放在deploy目录中，然后

问题是，部署之后，webapps文件夹中存在的所有文件夹都有3个目录：
myapp / WEB-INF / lib

除了3个空目录之外，没有其他文件。目录的时间戳表示它们是在我运行脚本时创建的。

发生这种情况后，通过Tomcat管理器取消部署，然后停止/启动Tomcat似乎正确地爆炸，但是我最好想使用脚本进行自动化。

任何人看到类似的问题/知道可能会出错？

Undeploy / deploy脚本自从发布以来没有改变，所以我不认为它。除了一些代码更改之外，我的实际项目中的主要改变是升级到新的GWT版本。新的GWT版本将一些文件放在一个名为/ WEB-INF / deploy /的文件夹中，但我不认为会导致它。在日志中没有看到任何错误

解决方案

FWIW，我们在Tomcat 7上的新鲜，简单的* WAR部署中遇到类似的事情

我看到编译的JSP类出现在我访问相应的页面。所以应用程序工作，它只是没有爆炸到工作区域...不知道为什么。

我很难解释发生了什么事，因为这是一个增量应用程序升级和初始安装需要相同的进程**，这进行得非常顺利。这表明它不是一个tomcat配置问题。

*我们使用部署描述符（xml）文件，所以我们可以重复使用相同的战争

**此过程是手动运行打包在WEB-INF文件夹中的脚本

[更新]
我可能刚刚回答了我自己的问题。如果我正在为不同的部署上下文重新使用WAR文件，那么也许正在使用一个常见的爆炸式战争？！

Has anyone seen anything like this:

I'm using a script which basically undeploys an app using ant, puts the new war file in the deploy directory and then deploys it using ant again.

The problem is, after the deploy all that exists in the webapps folder are 3 directories: myapp/WEB-INF/lib

There are no other files in there other than those 3 empty directories. The timestamps of the directories indicate they were created when I ran the script.

After this happens, undeploying through Tomcat manager and then stop/starting Tomcat seems to explode it correctly, but I ideally want to use the script for automation.

Anyone seen a similar issue/know what could be going wrong?

Undeploy/deploy script hasnt changed since prior release so I dont think its that. Main thing thats changed in my actual project other than some code change is upgrading to a new GWT version. New GWT versions put some files in a folder called /WEB-INF/deploy/ but I dont think that'd cause it. Dont really see any errors in the logs

解决方案

FWIW, we experienced something similar on a fresh, simple* WAR deployment on Tomcat 7.

I'm seeing compiled JSP classes appear as I visit the respective page. So the app works, it's just not exploded to the work area... not sure why.

I'm having a hard time explaining what has happened because this was an incremental application upgrade and the initial install required an identical process**, which went very smoothly. This suggests it isn't a tomcat configuration issue.

* We use deployment descriptor (xml) files so we can reuse the same war

** The process was to manually run a script that was packaged in the WEB-INF folder

[Update] I may have just answered my own question. If I'm reusing WAR files for different deployment contexts then perhaps a common exploded WAR is being used ?!

这篇关于Tomcat创建WEB-INF / lib，但不会爆炸战争文件（GWT）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！