We could make the DeploymentInfos into mbeans, and you could look at the state of the one for jboss-service.xml. I guess the way to do this might be to make an mbean representing a sar or *service.xml, and for all mbeans representing deployed packages (currently RARDeployment, and org.jboss.ejb.EjbModule) have them able to access the appropriate DeploymentInfo -- sort of a delegation model.
david jencks On 2002.03.01 14:24:42 -0500 Adam Heath wrote: > On Fri, 1 Mar 2002, Chris Kimpton wrote: > > > I also increased the time I allow for the server to warm up - it was > > 2mins - but my test runs show it taking 1min 40secs or so - which is > > getting close - so it now allows 5 mins for the server to warm up. > > For the init script I wrote for debian, I also wait 2 minutes. Mine is a > little more complex, as I actually tail server.log, looking for matching > regex > patterns, and exit with different values depending on what I find. > > I've thought about writing a little hook, that would allow an external > utility to be notified/informed of when jboss is up, and functioning. > > In fact, the init/start/stop/destroy idea could probably be mapped into > this > kind of framework, for informing external programs of jboss' overall > state. > > I can't work on this right now, as the new website we have been working > on(which uses jboss!) is going live any day now(we've rewritten a 3 year > old > jsp website into j2ee in a couple of months). > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
