|
From: Keith D. <kd...@cs...> - 2004-07-09 13:30:19
|
James, When you get some time, if you could elaborate more on the JMX support = in Geronimo, and how you see Spring beans being recognized as 'manageable' = (via configuration metadata I assume?) so they can be appropriately = registered in an MBeanServer running with in the app server, that would be = fantastic... Some questions I had: - Are you planning to support Standard (specifically StandardMBean in = JMX 1.2), Model, and/or Dynamic MBeans? - If I were to instantiate a POJO in a spring context and associate management metadata with it: e.g. metadata that could consist of the = class of a management interface (for standard mbeans), or a model mbean = descriptor key (that could be used to lookup mbean metadata from some other source, used to instantiate a generic model mbean proxy), along with the JMX = object name, how do you see that whole process working? Would we be able to = say that a particular bean is a "ServiceMBean" for example, were = "ServiceMBean" is a standard management interface defined as part of the standard JSR-77/CIM management hierarchy with well-known keys, attributes and operations? Then you'd be able to query on all beans that were = "Services" from the MBeanServer? - How will the lifecycle of JMX-managed bean configured in a spring = context be defined? For example, let's say I implement a "Service" management interface, which extends InitializingBean, adding in support for start() = and stop() operations. Will the app server be responsible for registering = and starting the service on startup, and stopping and de-regisering it on shutdown? - Will relations be supported; e.g I have two services that depend on = each other, and I want to capture that dependency as a relation between the = two management clients can then use to reason on. Or possibly the app = server itself; for example, for triggering a stop of all dependents services = during shutdown in the correct order. Thanks. This sounds really great; Keith -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf = Of jas...@ma... Sent: Friday, July 09, 2004 8:34 AM To: spr...@li... Subject: Re: [Springframework-developer] Spring/Geronimo On 9 Jul 2004, at 10:30, Nadeem Bitar wrote: > his is really great. > > A quick question, how would that affect sping's JMX support. I think they are parallel activities depending on what your deployment=20 environment is. Sometimes you might just want Spring + (say) mx4j.=20 Other times you might wanna deploy your POJOs inside a full J2EE stack=20 with full access to all of Geronimo's J2EE services (transaction=20 manager, security, JCA etc). If you deploy in Geronimo then the geronimo-spring module should be=20 capable of deploying your spring stuff inside Geronimo & wiring all=20 your POJOs into Geronimo's JSR 77 / 88 and JMX management/deployment=20 stack so it should work with any J2EE 1.4 management tool. If you don't want to deploy inside Geronimo but still want JMX support=20 then use Spring-JMX. James ------- http://radio.weblogs.com/0112098/ ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend = Black Hat Briefings & Training, Las Vegas July 24-29 -=20 digital self defense, top technical experts, no vendor pitches,=20 unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |