On Friday, November 8, 2002, at 11:41 AM, Peter Donald wrote:
Good question :) How were you going to handle this? In your original message you said you were going to proxy all interfaces EXCEPT for: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.Where do I get this array of interefaces from?
* Lifecycle interfaces
* Lifestyle interfaces
* certain jdk interfaces (like java.io.Serializable)
So I figured there would be a static util method somewhere getProxyableInterfaces( Class class ) or such. Other systems (merlin/phoenix) know the service interface of the component beforehand and could be more intelligent about this. (Assuming that this code would have a life beyond fortress)
That works aswell. If we want to be completely tight about it we could have a
DefaultComponentFactory
ProxyComponentFactory
ProxyGenerator
and the ProxyComponentFactory would delegate to DefaultComponentFactory and
use the ProxyGenerator
sounds good to me :) -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>
