On Monday 08 July 2002 12:46 pm, Marcus Crafter wrote: > From what I can see the asynchronous initialization code within > Fortress isn't working. When I trace through the code the component > handlers aren't initialized until components are actually lookup()'d.
Are you tracing w/a debugger? If the other thread might not get a chance to run if you are stepping through with a debugger. > 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(). The auto-creation of a CommandQueue doesn't work, for the reasons you noted. > Unfortunately I don't know the event and queue code well enough to > fix this problem if my analysis is correct. Any thoughts from the > more experienced developers there ? The async init does work though, if you specify a CommandQueue via the ContextBuilder.setCommandQueue(). I have it working here (verified w/log msgs and the source for some is the ThreadManager thread). -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
