Hi all,
Just a short note to let you know that I've been busy with many other
things lately and I haven't been able to spend too much time on Merlin
administration via JMX. Right now, I have something enabling the followings
(but I'd like to fix a few things on it before it gets commited) :
- read a management description from the .xinfo file, where
constructors, attributes, operations and notifications (and even JMX MBean
Descriptors) are defined for a component.
- build the management description from the component interfaces
using reflection when no management profile is explicitely defined (well,
you need to mention that you want your component to be manageable in the
.xinfo file to enable such a mechanism)
- combine both approaches, meaning you can explicitely define the
list of management interfaces in the .xinfo file and these interfaces will
be introspected to build the management description.
- then at runtime when a component instance is created, a
corresponding ModelMBean is build from the management description and is
registered by the MBeanServer.
The beautiful thing with ModelMBean is that you can have several targets
for one single management entity (ie ModelMBean). This could enable us to
delegate specific management operations to the underlying Applicance object
in order to propagate management notification to the container when a
component is started / stopped for example.
I've tested the whole thing using MX4J, MC4J and XtremeJ (Eclipse
management plugin). Seems to be working quite fine.
I'll be on vacation till the end of the week. I'ill post something next
week or the week after...
Laurent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
