Very old thread, but I got some useful answer.
As related by "David Lloyd" in JBoss issues:
In AS7, this is just a question of calling org.jboss.modules.Module#registerURLStreamHandlerFactoryModule() with the name of the module containing the handler factory for your protocol, and ensuring that that module has a META-INF/services/java.net.URLStreamHandler file in it. Alternatively, you can specify the module name in the jboss.protocol.handler.modules system property, which works similarly to java.protocol.handler.pkgs except rather than accepting a list of package names from the application class path, it accepts a list of module names from the boot module loader.
Full details are here: https://issues.jboss.org/browse/AS7-1562
Well, in my case, I just change my implementation to use Spring's PathMatchingResourcePatternResolver:
ResourcePatternResolver patternResolver = new PathMatchingResourcePatternResolver();
try {
Resource [] mappingLocations = patternResolver.getResources("classpath*:" + myBaseXmlPath + "/**/*.xml");
for(int i = 0; i < mappingLocations.length; i++) {
// do whatever you want ...
System.out.println(mappingLocations[i].getFile());
}
}
catch(IOException e) {
throw new RuntimeException(e);
}
It already deals with 'vfs' by proxing the classloader.