I noticed that when I was deploying (and especially reploying) WAR files to Apache Tomcat, sometimes the deployment would not be complete. In particular, the exploded WAR directory only contained a small subset of the files in the WAR. Furthermore, when I undeployed the WAR, portions of the exploded directory would not be deleted. I found a solution, however. Edit the CONTEXT element in context.xml to have the attribute antiJARLocking="true". You can do this for the context descriptor for the individual application (if any), or by editing the global context.xml in the Tomcat configuration directory.
... until the collector arrives ...
This "blog" is really just a scratchpad of mine. There is not much of general interest here. Most of the content is scribbled down "live" as I discover things I want to remember. I rarely go back to correct mistakes in older entries. You have been warned :)
Blog Archive
-
▼
2006
(135)
-
▼
Mar 2006
(17)
- Eclipse TreeViewer
- Eclipse Bundles vs. BEA SDO Classloaders
- Eclipse RCP Forms
- Eclipse RCP Forms
- BEA Workshop vs. EsiPlatformDataDS Build Process
- BEA Workshop vs. EsiPlatformDataDS Build Process
- Oracle 9.2 Client Installer
- Universal Data Link Files
- Apache Tomcat
- Eclipse Forms
- Wiki Password Lists
- Oracle 10g
- Eclipse vs BEA ALDSP Client JARs
- BEA ALDSP WTF
- BEA ALDSP WTF
- Apache Tomcat 5.5 Java Options
- Oxygen SOAP Analyser vs. Eclipse
-
▼
Mar 2006
(17)