On Mon, 2002-11-18 at 07:27, Stephen McConnell wrote: > > I suggest you keep an eye on the disucssions on the user list related to > Gary's work - he's doing a client side interface thing in which he has a > bunch of components he has to manage and is dealing with many of the > same questions your asking. With the introduction of a deployment > service abstraction in Merlin I'll be keen to see this tested as broadly > as possible. In the meantime I will be posting information about the > deployent and appliance API as things come together. > > Cheers, Steve.
Thank you Steve. In the meantime I took a "lazy" approach, which was to create a getter/setter for the companyId parameter, and then go through a secondary initialize to set internal state based on the company Id. It just does not "feel" right because I am behaving too much like a container - I am a consumer! I will also try the context method that you described earlier. I will take your advice and listen to the list as the lifecycle extension method is fleshed out. PS: Before this new container magic for lifecycle extensions, what was the typical avalon way of initializing component runtime values? The lazy way, or the context method that you described, or something different? Regards, Adam -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
