[jbosstools-issues] [JBoss JIRA] (JBIDE-14119) look at how to handle the different jmx views/perspectives between AS and FuseSource plugins

Mon Apr 29 01:12:53 EDT 2013

    [ https://issues.jboss.org/browse/JBIDE-14119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770583#comment-12770583 ] 

Lars Heinemann commented on JBIDE-14119:
----------------------------------------

On Fuse side we are currently using a not very actual version of the JMX plugins from http://www.jvmmonitor.org/. The source code of these plugins can be found at Google Code: https://code.google.com/a/eclipselabs.org/p/jvmmonitor/

We extend the JMX Navigator by providing new types of nodes which can be displayed / browsed. So if we go that way then we will need some kind of extension points to plug in our own node types / images / etc.

>From what I understood so far this project is a fork of the plugins you are currently using. Not sure when this fork was done but it seems that this project is actively developed. Maybe you have the chance to compare both versions of JMX tooling and then decide based on the features of each project which to use in future. But it definitely makes no sense to maintain two versions of JMX tooling. A nice feature of jvmmonitor is that it can detect local VMs and connect to them without knowing the JMX URI. Though you can also manually create JMX connections the old style way.

> look at how to handle the different jmx views/perspectives between AS and FuseSource plugins
> --------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-14119
>                 URL: https://issues.jboss.org/browse/JBIDE-14119
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>            Reporter: Max Rydahl Andersen
>
> Talk with [~lhein] he knows more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira