Hi Dennis,
From the doc's Rio's ServiceClassLoader looks like its designed to
overcome the lost codebase problem?
The URIClassLoader it extends looks interesting too.
Your right I did misinterpret your post, sorry.
My intention's are to place common interfaces high up in the ClassLoader
hierarchy so that implementation concerns can be maintained
independently of each other, beneath. The common interfaces I'm
referring to of course are the Service API. I've come up with Extended
Service API to deal with evolution of Service API and get around the
dynamically updateable Service API garbage collection problem. See my
other post.
I'd like to work with people such as yourself, so what we eventually
come up with to control Class Visibility, can work with the various
containers.
Cheers,
Peter.
