Hi Steve, > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 05, 2003 1:35 PM > > Not necessarily - the service method is simply the point at which the > ServiceManager is supplied to the component. The component > implementation can choose to access services at this point, or, cache > the reference and access the services it needs when and if it needs > them. Both Fortress and Merlin provide support for delayed > activation > of a service which basically means that although you have > been supplied > with a manager, the services the manager will provide on > lookup may not > be instantiated (for example, the instantiation may be trigger by the > lookup request).
OK, I will have such a delayed activation. The reason is to have a factory based on credentials. A lookup for the factory with an unknown credential should result in a new factory instance, that lives for some time after the last performed lookup. It seems that I will need a separate configuration file for these factories ... And what about the release call? Should not every retrieved element be released again? At least the code of FortressServiceManager.relase seems to expect this, while framework's DefaultServiceManager does not care at all. So it comes down to "release always, until you exactly know that is does not matter for the service". Regards, J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
