[jira] Created: (RIVER-117) Add JMX enabled Mbean for the starter package

["Ron Mann (JIRA)" <ji...@apache.org>]

Add JMX enabled Mbean for the starter package
---------------------------------------------

                 Key: RIVER-117
                 URL: https://issues.apache.org/jira/browse/RIVER-117
             Project: River
          Issue Type: Improvement
          Components: com_sun_jini_start
    Affects Versions: jtsk_2.1
            Reporter: Ron Mann


Bugtraq Id:[4992771||http://bugs.sun.com/bugdatabase/view_bug.do?bug_id= 4992771]
User request for JMX support in order to start services. Quote:
 How about the incorporation of the JMX enabled MBean for the starter? Just create an interface com.sun.jini.starter.ServiceStaterMBean with your new method to start a service and you're all set!

Comments:
ome follow-up discussion ...

My defining the ServiceStarterMBean interface and implementing it (with ServiceStarter), you end up making the ServiceStarter a "standard mbean", allowing it to be loaded my some other application which has created an MBeanServer. Note that you dont need to include any JMX packages or methods to do this, its just a naming pattern that needs to be followed.

Furthermore, if that environment has added the MLet service to the MBeanServer, a benefit of this will be loading the  ServiceStarter as an MLet, enabling the launching of Jini services through a JMX enabled management console by providing the location of the configuration file to be loaded. An example of defining an MLet which loads the ServiceStarter would look something like this:

<MLET CODE=com.sun.jini.start.ServiceStarter
             ARCHIVE="start.jar" CODEBASE=./lib
             NAME=com.sun.jini:type=ServiceStarter>
</MLET>

So consider the possibilities of this, loading Jini services from Tomcat, JBoss, Webspshere, etc... makes it all part of an overall enterprise solution


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.