Jeremy Volkman <[EMAIL PROTECTED]> writes: > As far as URLStreamHandlerService goes, I can see two problems you > might be running into. > > 1. You're hitting a "built-in" protocol as determined by the > implementation of the URL handling service's > URLStreamHandlerFactory. In the case of Equinox's, the system > property "java.protocol.handler.pkgs" is checked for these > built-ins.
With the consequence being that Equinox -- or any other similarly-behaving implementation -- won't tolerate registration of a duplicate handler? > 2. You aren't hitting a "built-in" known by the URL handling service's > URLStreamHandlerFactory, but an "http" url is looked up before your > custom URLStreamHandlerService is registered. And in that case, my implementation would be skipped as well. Is the solution to the first problem above to try to register my handler as one of the "built-in" packages, shadowing Sun's handler, or is that frowned upon. > There may be other possible problems, as I've just taken a cursory > glance at the various players involved, but hopefully this will get > you on the right track. I may have read your message too pessimistically, but it sounds like you're confirming my suspicion that it's not tenable to replace the built-in HTTP URL handler, there being too many ways to lose out to the default. Did I misread your intent? -- Steven E. Harris _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
