AbstractVirtualFileHandler log message: "No such existing handler, falling back to old root + path" is too strict ----------------------------------------------------------------------------------------------------------------- Key: JBVFS-187 URL: https://issues.jboss.org/browse/JBVFS-187 Project: JBoss VFS Issue Type: Bug Security Level: Public(Everyone can see) Components: Release Affects Versions: 2.2.0.GA, 2.2.0.SP1, 2.2.1.GA Reporter: Chris Sams Assignee: Chris Sams Priority: Minor This is to strict, it should be INFO or even less. What we're trying to do here is get a real (non-temp) URL, for that we use original handler. And then try to get a child off this old handler, where since removed, is null. So we try our best to re-ceate the original url - hence warning. This can occur in normal operations such as when using a jboss-structure.xml: <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> And if you deploy an exploded deployment and then remove it from the deploy directory triggering a undeploy will cause the warning. 22:20:08,625 WARN [AbstractVirtualFileHandler] No such existing handler, falling back to old root + path: vfszip:/home/applications/servers/eap/jboss-eap-5.1.2/jboss-as/server/default/deploy/springtest3.2.war/WEB-INF/lib/spring-web-3.2.0.M2.jar/org/springframework/web/context/ContextCleanupListener.class