Timeline for Refactoring Tomcat webapp deployments
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 21, 2017 at 17:20 | comment | added | Michael Easter |
Note, though the strategy may (?) be sound, we ultimately ended up putting all jars in each WAR file, with few (if any) jars in $CATALINA_HOME/lib. The disadvantage is the size of of the WAR files, but the upside is that classpath hell was mitigated.
|
|
| Nov 8, 2014 at 16:10 | comment | added | Jules | One word of caution - some logging frameworks can cause classloader resource leaks when in WEB-INF/lib, because they pass a reference to their own classes to the standard java logging API, which holds onto references to them indefinitely. If they are in WEB-INF/lib, this class has a reference to the webapp classloader, to which no references are supposed to survive after the app is stopped. You may want to ensure you are using a logging system that doesn't have this bug. | |
| Aug 10, 2014 at 7:53 | answer | added | kpw | timeline score: 2 | |
| Jul 20, 2013 at 16:53 | history | asked | Michael Easter | CC BY-SA 3.0 |