[ https://issues.jboss.org/browse/AS7-1562?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-1562: ---------------------------------- 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. It is important to remember that each time you add such a handler, you create a *permanent* static reference to it. This means that if your handler is in a deployment, the handler (and thus the deployment) class loader hangs around *forever*, even if you try to undeploy it. This can appear as a leak if you repeatedly redeploy a module with such a handler in it which registers itself upon deployment. Thus it is recommended that any custom URL handlers be registered from static modules. In addition, if there is a URL protocol type that should be made available by default, then it should be noted so that it can be added to the AS 7 bootstrap. Note that at first blush, a URL scheme of "classpath" seems a poor fit in a modular environment though. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira