Noel, I didn't have to 'do' anything to James to get the JMX stop/start mechanism working, all that is provided by the Phoenix SystemManager / JMX implementation.
What I (thought I) said was 'we made some minor changes to the dispose() methods'. This is because some of the components were shutting down untidily and throwing a bunch of exceptions. Mainly trying to use a context log object after that object had already been removed. I would like to improve the JMX monitoring and management of James, but don't hold your breath as I have a lot of things on my plate right now! Cheers Steve > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 29, 2003 9:04 AM > To: James Developers List > Subject: RE: Shutting down James > > > > I am working on JMX stuff right now. My objective is to provide > > fine-grain redeployment of an appliance inside a container. This > > means that all components would be redeployable (without changing > > existing component code). > > Great. :-) > > > this will not bne available tommorow > > Understood. We haven't been rushing at JMX. When the > support is there from Avalon, we'll want to take advantage of > it. If Steve has some stuff already working for James, > that'll be good to look at, too. > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
