in the map24 page, it firsts uses a applet to preload a versioned jar resources, then as you click on the interactive button, it tries to load the actual map applet.
Since both the applet is from the same codebase, the same classloader should be used, so the second applet (map) startup will be fast because it will reuse the classloader from cache. however, due to a bug in JarCacheUtil, we will mark the first classloader as not-cachable. so now when you click on the interactive button, a new class loader of the same codebase is created and the applet is using it to load the map applet. however this classloader does not contain the versioned jar resoruces that is already loaded by the first applet, and causes the applet to wait forever.