Alexis Agahi wrote:
Hi,
After some discussion a few weeks ago, someone (from Steve?) sugested that merlin could have a kernel service that could provide JMX manager for application.
Maybe merlin could use a JMX MBeanServer component ready to be composed by any service, and btw this component could be generic cornerstone-like component that could provide jmx implem abstraction?
I'm just reworking on the generic MBean deployer for merlin and I think it should be nice to use the merlin MBeanServer instead of declaring my own.
What I have on paper is the addition of an <implementation> and <facilities> element to the <kernel> defintion. The <implementation> is the container of system facilities. These facilities will be exposed to the container internals and som cases will replace bootstrap services. For example, the logging system used during bootstrap may be redefined as part of <implementation> defintion. In conjuction with this defintion, the container established to handle implementation components will be supplied with the full container classloader. On completion of the deployment of the implementation, a second facilities container will be deployed.
<kernel>
<system>
<implementation>
<component name="urn:avalon:logging"
type="org.apache.avalon.logging.DefaultLoggingManager"/> <component name="urn:avalon:jmx"
type="org.apache.avalon.jmx.StandardMBeanServer"/> <component name="urn:avalon:iiop"
type="org.apache.avalon.iiop.DefaultORBManager"/><!-- etc. -->
</implementation>
<facilities>
<!--
Extensions that are restricted to the API and SPI
container classes including listeners, interceptors,
and other container side add-ons
--> <component name="urn:avalon:jmx-manager"
type="org.apache.avalon.jmx.DefaultApplianceListener"/></facilities>
</kernel>
Complementing the above will be a new block implementation (or possible refactoring of the current block classes) to enable plug-in resolve handling. The enhancements will enable finder oriented behaviour on a block (i.e. similar to ECM style dynamic lookup). This ability is also needed in one of the Turbine Fulcrum components and in Fortress style applications. Basically the objective is provide "explicit", "finder" and "factory" semantics as built in semantic models - but also enable the plugging in of interceptors on any of these models.
I.e. the short answer is that the JMXMBeanServer would be a classic component no different to any other component.
Stephen.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
