Stephen McConnell wrote:
I like this behaviour. It is quite simple and deterministic. I use these classes in code that is "pseudo-avalon", where there is no "real" container. I recognize the need for proxies in many applications, but the setup provided by these wrappers needs to be provided as well.Wrapper classes (major) -----------------------The wrapper classes that that exist in framework are broken. The WrapperComponentManager takes a ServiceManager as a constructor argument and when lookup invocations are made against the wrapper, the wrapper returns Component instance "if and only if the object returned from a lookup on the service manager is an instance of Component". The wrapper makes no attempt to proxy an Object as a Component.
I prefer to have them in a seperate jar (in addition to the main jar) so that they can be used without upgrading avalon-framework.jar. In fact, I have such a (custom-built) jar in daily use. Dunno how widespread the need for something like that is though.
cheers,
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
