One workaround is to explicitly load the class during initialization so it is cached by the classloader and available later. Another is to use a jboss-structure.xml to force the WAR's contents to be copied to a temp location on deploy even though the WAR already is exploded: <structure> <context modification= "temp" > <path name=""/> <metaDataPath> <path name= "WEB-INF" /> </metaDataPath> <classpath> <path name= "WEB-INF/classes" /> <path name= "WEB-INF/lib" suffixes= ".jar" /> </classpath> </context> </structure>

<para>During hot-undeployment of WARs, if the application had a context listener which tried to load a never-before loaded class when the context was shutting down, an exception was thrown. This occurred for exploded WARs, but also for un-exploded WARs where the required class was located in the WAR archive itself, and not in an included library. This happened because the original file containing the class no longer existed. To fix this issue, a system property, <code>-Djboss.war.forceCopy=true</code>, can now be used to force WARs to be copied when deployed. This ensures that even when a deployment is removed from the deploy directory, its resources are available for classloading to correctly function as the WAR is shutting down.</para>