I still don't see how this affects that re-deploy issue.
With permanent cache we should always have just a single instance of
particular VirtualFileHandler (unless using VFS::createNewRoot).
This (7) either hits the cache or creates new VFHandler,
initializing parent/.ear's ZEC,
hence any next access/navigation to this parent ZEC shouldn't re-create
new nested ZEC.
Jason T. Greene wrote:
>> 7. VFSRegistry.getFile is called by the JSR77 deployment code
>> (J2EEDeployment)
>
> I need to check this.
This is via classloading:
org.jboss.virtual.plugins.registry.DefaultVFSRegistry.getFile(DefaultVFSRegistry.java:120)
org.jboss.virtual.protocol.AbstractVFSHandler.openConnection(AbstractVFSHandler.java:71)
java.net.URL.openConnection(URL.java:943)
sun.misc.URLClassPath$Loader.findResource(URLClassPath.java:463)
sun.misc.URLClassPath.findResource(URLClassPath.java:142)
java.net.URLClassLoader$2.run(URLClassLoader.java:362)
java.security.AccessController.doPrivileged(Native Method)
java.net.URLClassLoader.findResource(URLClassLoader.java:359)
java.lang.ClassLoader.getResource(ClassLoader.java:1032)
java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:1214)
org.jboss.management.j2ee.J2EEDeployedObject.getDeploymentDescriptor(J2EEDeployedObject.java:114)