On Wed, 2003-01-29 at 17:34, Stephen McConnell wrote: > >I just tried to figure out how to use this. There is still problem in > >creating a DefaultRegistry object. It tries to use > >URL.setURLStreamHandlerFactory and then form a URL object using the > >"native" scheme. So we have a chicken and egg problem because we can't > >create a ServiceURLFactory until we create a Registry. We can't create > >a Registry because it will fail since setURLStreamHandlerFactory has > >been called already. > > > > I'm back! > :-) > > Ok - I have not looked at the URLStreamHandlerFactory class but I'm > asuming that could be a workaround such that we would nbot need to call > the URL.setURLStreamHandlerFactory operation. Currently if the > setURLStreamHandlerFactory throws an exception it is ignored - so an > exection is being thrown when attempting to create the actual URL. So - > in principal - of we associate a StreamHandlerFactory with the > classloader set as the context classloader and the StreamHandlerFactory > knows about our stuff - well - it should work. Keep in mind that it is > 1:31 in the morning and I've just got back from a really great dinner - > so I'm feeling cinfidend:-) > > Cheers, Steve.
Ok... if that's possible. There's also a constructor for URL that accepts a URLStreamHandlerFactory as a parameter. This would be good to use for in the constructor of the DefaultRegistry, but anyone else would then need to be able to get a reference to that object so they can use it when creating URL objects. This is kind of a pain, but I don't see a way around it ATM. -- Richard Wallace AIM Consulting and Computers http://www.a--i--m.com "Providing New Technology, the Old-Fashioned Way" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
