|According to the heavy discussion lately about JMX,
|monitoring and security AND because of my proposal
|to create our own JMX implementation I would suggest
|the following:
|
|- Create a new MLET MBean allowing to load the old files
| but also XML files through a XML parser. When finished
| it can be initiated and registered in the Main.java class and
| used instead of the MBeanServer's own method.
yes, something that parses the content of an XML file and feeds the MLET
calls accordingly would be nice, also differential XML would be good, i.e.
provide default pool config etc etc
|- Create a Security MBean which decides if a method call
| is permitted or not. This call is made by another MBean
| and if the Security MBean rejects it it throws an exception.
| This way the JMX Connector server-side can use it to
| check if the method call is allowed to execute or not. The
| Security MBean contains its User-Group-ACL list and
| allows other tools to manage itself (create, edit, remote
| a user/group/ACL and make the connections).
yes...
|- Create a Dependency Service allowing to wait till a
| MBean is loaded and registered. This service can be used
| by the new MLET service for dependent MBeans.
Already in afaik
marc
|
|All three do not require to write our own JMX Agent (even
|if it would be nice to integrate them into the MBeanServer).
|
|Have fun - Mad Andy / Better Pizza
|
|Senior Java Developer
|eBuilt Inc. (www.ebuilt.com)
|
|while( true ) { think(); write(); publish(); }
|
|
|
