On Friday, November 8, 2002, at 11:08 AM, Peter Donald wrote:
That works, but I'd like to be able to pass in an array of interfaces to the ComponentFactory then to tell the ComponentProxyGenerator what to proxy for.Simple enough. But do you mind if it is still ComponentFactory that callsCould we separate that into two pieces? A ComponentFactory and a ComponentProxyGenerator?
ComponentProxyGenerator and olny returns proxied instances?
I was actually thinking of a layered approach in the opposite direction. The CompoentFactory is really just an ObjectFactory. Why not have the ComponentProxyGenerator just be another ObjectFactory that takes another ObjectFactory and proxies the objects from the other factory? So usage might be like:
ComponentFactory cf = new ComponentFactory(...);
ComponentProxyGenerator cpg = new ComponentProxyGenerator( cf, new Class[] { ... } );
cpg.newInstance();
One could then use the ProxyGenerator wherever ObjectFactory's were used...
-pete
--
peter royal -> [EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
