-----Mensagem original----- De: Berin Loritsch [mailto:[EMAIL PROTECTED]
> Some of the very necessary features that containers do these > days is to verify that the environment is sane. While we think > we know all the components that are needed for a system, from > time to time we may find that one is missing for some reason. As a sanity check it's a nice feature. > So as an example, if I have a component that retrieves data > from an expensive resource (like a database), I might have the > component use a cache component. If the cache component exists, > but has not been loaded and properly configured in time, then > the data component will fail. But that's the point. How the component will access it's dependencies? Through look up I think. The component initialization protocol will be performed for this dependent component as it will for any other component - on demand - don't they? If don't, it will force us to threat them different, - creating a separate LookupManager - put the real instances of each dependent component there - praying for someone to dispose them The container ensuring the environment sanity is a good thing, but I can't see how to implement a different behavior for dependents components. Maybe my nighlty studies of Fortress and Merlin show me where I'm wrong. > BTW, did you get the mail I sent you RE: getting proper info for your CVS access? I didn't. To which email you sent? I don't work for Cimcorp anymore... :-( hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
