|
From: Leif M. <le...@ta...> - 2003-04-23 23:11:29
|
Mike Castle wrote: >Does that really work? I thought that just told NT that you need to start >those dependencies; not that one needs to be up and running before the next. > The WrapperSimpleApp and WrapperStartStopApp helper classes will return their applications have started after about 5 seconds. This was necessary to make them work reliably with any Java application. If your applications are integrated using the WrapperListener method then you can control when that interface's start method returns. The Wrapper will not tell the NT service manager that the application has started until the start method has returned, and the NT service manager will not start a dependent service until the first has been started. In my experience this has worked reliably. If you are worried about it, then you can use my other suggestion about having your master application launch the child JVMs wrapped inside their own Wrappers rather than launching them directly. That should protect them from the logout problem. I have not tested that exact thing before. But I see no reason why it shouldn't work. Cheers, Leif |