|
From: Alef A. <al...@jt...> - 2004-11-08 08:02:26
|
I have a couple of projects that would greatly benefit from Spring's JMX = support. Being able to slightly or temporarily reconfigure certain beans = in an application is something our projects often require. Think of = manually firing a job (cleanup, whatever). =20 alef =20 ________________________________ From: spr...@li... on behalf of = Seth Ladd Sent: Mon 11/8/2004 3:15 AM To: spr...@li... Subject: Re: [Springframework-developer] Re: Design patterns for JMX and = application manageability : A guide for developers. - HP Dev Resource = Central On Sun, 7 Nov 2004 21:35:06 +0000, Nick Minutello <nic...@gm...> wrote: > > We won't be competing to an appserver, but by JMX-enabling the core = Spring > > classes you will have a lot more runtime control over your Spring = beans. > > Fair enough. > I guess I havent run into examples of the sorts of things you would > want to control at runtime... hence my misunderstanding. Our biggest requirement is to control logging at runtime. By hooking log4j into JMX, we're now able to do this. Note that we had to do some hacking to log4j to get it to work with latest release of JMX. Seth ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=3D5588&alloc_id=3D12065&op=3Dclick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |