> From: Peter Royal [mailto:[EMAIL PROTECTED]] > > On Monday 08 July 2002 01:04 pm, Berin Loritsch wrote: > > > In the ContextManager a default CommandQueue object is > created if > > > one > > > is not specified (and also if setCommandQueue(null) is > given to the > > > ContextBuilder (which seems suspicious)) and there > > > seems to be no > > > ThreadManager associated with the CommandQueue, so > > > initialize()'s are > > > only done inside FortressComponent/ServiceManager.lookup(). > > > > We need to make the CommandManager initialize a default > ThreadManager > > if one isn't provided. > > Is that really what we want? > > Currently there is no way to *not* use the async init (other > than exploiting > the above bug). It'd be nice to keep that option.
Let's not exploit the bug then. Let's provide two concrete containers: one that does lazy initialization, and one that does async initialization. Both can be extended, and use the common parts of AbstractContainer. It also helps AbstractContainer to be more abstract and let the concrete version choose the initialization policy. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
