"david.lloyd(a)jboss.com" wrote : Ah, I see. It's obvious now that I try it out: the policy file parser is literally constructing a URL instance during the parsing stage, which fails because the appropriate URL handler is missing. | | So I guess the real question is: it the best solution to implement a custom policy interpreter that can handle arbitrary URIs, or to come up with a way to trick the URL protocol registry system to allow the URL handler to be "lazy-loaded"? http://java.sun.com/j2se/1.5.0/docs/api/java/security/ProtectionDomain.ht... CodeSource needs an URL instance for instantiation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181070#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...