anonymous wrote : For standalone though, we probably won't be able to use this. There
won't be a jboss instance to run it in!
Depends on how you are exposing your remote management interface. If its just JMX, you
can piggy back on our JMX plugin and have your plugin connect to your remoting services
using direct JMX.
You can extend existing plugins to reuse existing plugin capabilities. This is how we
wrote several of our plugins. For example, the JBossAS4 plugin as well as the Hibernate
plugin use the JMX plugin to connect to the JMX MBeanServer hosting the services we want
to manage. Under the covers it uses MC4J's EMS library so it supports all different
kinds of JMX MBeanServers (standalone JDK5 platform MBS, JBossAS MBeanServer, BEA
WebLogic, etc. etc.).
See:
http://svn.rhq-project.org/repos/rhq/trunk/etc/custom-jmx-plugin/src/main...
In that case, there is no Java code to write. You just write your plugin's XML
descriptor and tell it which JMX operations/attributes your services support, and we
utilize the JMX plugin to do the dirty work of calling the appropriate JMX APIs. So, for
example, write simple JMX MBeans that manage your remoting services and just write the XML
descriptor that describe your management MBean interfaces and the JMX plugin takes care of
the actual connection to and calling the MBeans.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130775#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...