"wolfc" wrote : | But depending on how you read the specification it could be interpreted as a violation. Because jar files are no longer relative to the physical location, if the VFS is rooted at the deployment unit. | It's not a violation if you read the JavaEE spec, we're just not required to support it and therefore it warns it is not portable. e.g. JavaEE5 8.2.1.2 (talking about manifests) anonymous wrote : | Top level JAR files that are processed by a deployment tool should not contain | Class-Path entries; such entries would, by definition, reference other files external to the | deployment unit. A deployment tool is not required to process such external | references. | My emphasis. On your unit tests, you are just constructing your VFS contexts wrongly. You need to "external references" in your VFS context by including the parent within the VFS context your construct. e.g. we support "external references" if you put them in deploy/ because the deployment file is constructed as | VFS context = VFS.getVFS("deploy"); | VirtualFile deployment = context.getRoot().getChild(deploymentName); | so that deployment can see the whole deploy folder. But a deployment that explicitly lists its URL in the scanner won't have a parent because there is no equivalent of the "deploy" folder for them. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211378#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...