[jboss-jira] [JBoss JIRA] Commented: (JBAS-2595) JMX Resolver for JSF

[ http://jira.jboss.com/jira/browse/JBAS-2595?page=comments#action_12345395 ] Stan Silvert commented on JBAS-2595: ------------------------------------ I've made a lot of progress on this in past couple of months. The EL Resolver allows you to easily manage an entire cluster with a few simple JSP pages. Instead of hunting for the attributes and operations you are looking for in the jmx-console, you just define your own pages with the attributes and operations you are interested in. Plus, you get cluster views and the power of JSF components for free. Here are all the features implemented so far: MAPPING Mapping ObjectName to the EL can be done in the following ways: Use the JMX Resolver's "ObjectName" implicit object (reserved word): ${ObjectName['java.lang:type=Runtime'].StartTime} Place an ObjectName object in some scope that the EL can see: <% session.setAttribute("runtime", new ObjectName("java.lang:type=Runtime")); %> ${runtime.StartTime} Define an ObjectName alias in web.xml with a "jmx." prefix: <context-param> <param-name>jmx.runtime</param-name> <param-value>java.lang:type=Runtime</param-value> </context-param> ${runtime.StartTime} USAGE The EL Resolver can be used with JSF, Facelets, JSTL, or any other taglib that supports Unified EL: <h:outputText value="#{ObjectName['java.lang:type=Runtime'].StartTime}"><f:convertDateTime type="both" timeStyle="short"/></h:outputText> <c:set var"serverStartTime" value="${ObjectName['java.lang:type=Runtime'].StartTime" scope="application" /> The EL Resolver can set attributes on MBeans just like any other JavaBean: <h:inputText value="#{defaultDS.MaxSize}" converter="javax.faces.Integer" /> The EL Resolver can invoke MBean operations. This allows them to be used as the target of JSF actions. You just need to add "invoke" onto the end of the expression. Currently, this only supports no-arg operations: <h:commandButton value="Run GC" action="#{ObjectName['jboss.system:type=Server'].runGarbageCollector.invoke}"/> If the proper interface is implemented, an MBean can act as a JSF ActionListener, ValueChangeListener, or Validator. Note that because the interface is well-known, the "invoke" is not used on the actionListener. Only the method name defined in the interface is used. JSF will pass the needed params to the invocation, which will take place on the MBean: <h:commandButton value="Submit" action="#{myMBeanAlias.fooAction.invoke}"> <f:actionListener binding="#{myMBeanActionListenerAlias.processAction}" /> </h:commandButton> MBEAN QUERY SUPPORT You can use the EL Resolver's "QueryNames" implicit object to do a JMX queryNames() and then loop through the results. Currently, this only supports queries based on ObjectName matching. Later, it may include full JMX query support using Query objects. For instance to loop through all the WebModule MBeans you would use #{QueryNames['jboss.web:j2eeType=WebModule,*']} like this: <font size="18">Web Deployments</font> <table border="1"> <tr><th>Path</th><th>Start Time</th><th>Max Active</th><th>Start/Stop</th><th>Reload</th></tr> <c:forEach var="webapp" items="#{QueryNames['jboss.web:j2eeType=WebModule,*']}"> <tr> <td><h:outputText value="#{webapp.path}" rendered="#{webapp.path != ''}"/> <h:outputText value="/" rendered="#{webapp.path == ''}" /></td> <td><h:outputText value="#{webapp.startTime}" rendered="#{webapp.startTime > 0}"><f:convertDateTime type="both" timeStyle="short"/></h:outputText> <h:outputText value="Stopped" rendered="#{webapp.startTime == 0}" /></td> <td><h:commandButton value="Start" action="#{webapp.start.invoke}" rendered="${webapp.state == 0}"/> <h:commandButton value="Stop" action="#{webapp.stop.invoke}" rendered="${webapp.state == 1}"/></td> <td><h:commandButton value="Reload" action="#{webapp.reload.invoke}" /></td> </tr> </c:forEach> </table> CLUSTER SUPPORT The EL Resolver contains support for JBoss Cluster. It does automatic discovery and uses JMX Remoting to call MBeans on remote nodes. The EL Resolver listens for cluster events to keep the reachable remote MBean servers up to date. To access the nodes, you loop through the cluster using the "allNodes" implicit object: <font size="18">Server Statistics</font> <table border="1"> <tr><th>Server</th><th>Start Time</th><th>Active Threads</th><th>Total Memory</th><th>Free Memory</th><th>Run GC</th></tr> <c:forEach var="node" items="#{allNodes}"> <tr> <td>${node.servercfg.ServerName}</td> <td><h:outputText value="#{node.Runtime.StartTime}"><f:convertDateTime type="both" timeStyle="short"/></h:outputText></td> <td>${node.ServerInfo.ActiveThreadCount}</td> <td>${node.ServerInfo.TotalMemory}</td> <td>${node.ServerInfo.FreeMemory}</td> <td><h:commandButton value="Run GC" action="#{node.Server.runGarbageCollector.invoke}"/></td> </tr> </c:forEach> </table> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira