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"?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181065#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...