I upgraded the container.legacy subpackage to include wrappers that
upgraded ComponentManager/ComponentSelector to
ServiceManager/ServiceSelector. Also the
LegacyComponentManager/Selector also correctly wraps the component
declaration in a (Component) proxy. It is a good thing. None of the
implementations assume anything about a container's hierarchy.
With the fact that it is in the Container package, we can fix things
like SourceResolver to be current, and still work with the legacy
psuedo-protocol handlers.
I also assumed it was appropriate to put that stuff in the "legacy"
subpackage as opposed to the "lookup" because it is only to work with
older stuff.
I also upgraded the AbstractServiceSelector so that if by some chance
it was given a ComponentSelector, it would be properly wrapped.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
