Peter Royal wrote:
On Tuesday, February 11, 2003, at 01:49 PM, Stephen McConnell wrote:1. Fortress appears to be assuming that the will correctly handling the Component proxy case and as far as I can see it will fail when used in a real migration scenario (refer ComponentFactory usage).
Not a problem, as that that ComponentFactory is wrapped with a ProxyObjectFactory that puts Component on.
2. The Phoenix case will result in container specific code because authors are assuming that the container will automatically proxy everything to Component.
I'm not assuming that, I'm leveraging that. If I was writing container-agnostic code I would use a proxying wrapper.
-pete
Ok - looks like I'm in the minority on this one :-)
Conclusion - the the class in question "WrapperComponetManager" needs some supplimentary documentation detaililing that fact that lookups may only be applied that will result in resolution of a object that implements the Component interface. I.e. no attempt is made to wrap non-Component instances as Component.
Sounds reasonable?
Cheers, Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
