[jboss-jira] [JBoss JIRA] Commented: (JBMICROCONT-137) VirtualFile.findChild("WEB-INF/classes") fails for SyntheticDirEntries

[Remy Maucherat (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMICROCONT-137?page=comments#action_12348943 ] 
            
Remy Maucherat commented on JBMICROCONT-137:
--------------------------------------------

This could also explain the mysterious CL failures that occured with the updated web deployer (which uses the VFS) when running tests, and did not occur when I used my own WARs to test it. Sneaky ... I don't know if it's totally valid to not have entries for folders, but it uncompresses well enough, I suppose.

In Tomcat's WARDirContext, I have logic to create a whole structure when the folders entries do not exist.
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/apache/naming/resources/WARDirContext.java?revision=467222&view=markup
The loadEntries method is the one that builds the tree when initializing.


> VirtualFile.findChild("WEB-INF/classes") fails for SyntheticDirEntries
> ----------------------------------------------------------------------
>
>                 Key: JBMICROCONT-137
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-137
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: VFS
>            Reporter: Thomas Diesler
>            Priority: Critical
>         Attachments: WarDeployApp_web.war
>
>
> I have two WARs. The first (generated by the CTS porting layer) fails because the DeploymentUnit.classLoader cannot load 
> com.sun.ts.tests.webservices.deploy.warDeploy.HelloJavaBean
> The reason is that WEB-INF/classes is not added to the the the classloader
> [tdiesler at localhost cts]$ jar -tf WarDeployApp_web.war 
> WarDeploy.xml
> WEB-INF/webservices.xml
> WEB-INF/wsdl/WarDeploy.wsdl
> WEB-INF/classes/com/sun/ts/tests/webservices/deploy/warDeploy/HelloJavaBean.class
> WEB-INF/classes/com/sun/ts/tests/webservices/deploy/warDeploy/HelloWs.class
> WEB-INF/web.xml
> META-INF/MANIFEST.MF
> The second (generated by ant) is fine. It contains jar entries for every directory level
> [tdiesler at localhost cts]$ jar -tf jaxrpc-samples-jsr109pojo-rpc.war 
> META-INF/
> META-INF/MANIFEST.MF
> WEB-INF/
> WEB-INF/classes/
> WEB-INF/classes/org/
> WEB-INF/classes/org/jboss/
> WEB-INF/classes/org/jboss/test/
> WEB-INF/classes/org/jboss/test/ws/
> WEB-INF/classes/org/jboss/test/ws/jaxrpc/
> WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/
> WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/jsr109pojo/
> WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/jsr109pojo/JaxRpcJSEEndpoint.class
> WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/jsr109pojo/JaxRpcTestService.class
> WEB-INF/classes/org/jboss/test/ws/jaxrpc/samples/jsr109pojo/SimpleUserType.class
> WEB-INF/wsdl/
> WEB-INF/jaxrpc-mapping.xml
> WEB-INF/webservices.xml
> WEB-INF/wsdl/TestService.wsdl
> WEB-INF/web.xml
> I set this as critical issue because all WS war deployments fail that don't have a WEB-INF/classes jar entry.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira