[jbosstools-issues] [JBoss JIRA] (JBIDE-17313) [API Deficiency] auto-detected locals need API to allow others to detect duplicates

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-17313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-17313.
---------------------------------

    Resolution: Rejected


This is a bit out of date. The new UI strictly separates server-contributed jmx nodes from auto-detected or user-defined connections. 

> [API Deficiency] auto-detected locals need API to allow others to detect duplicates
> -----------------------------------------------------------------------------------
>
>                 Key: JBIDE-17313
>                 URL: https://issues.jboss.org/browse/JBIDE-17313
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: jmx
>            Reporter: Rob Stryker
>             Fix For: 4.2.0.Beta3
>
>
> When a new vm is autodetected, other plugins (such as jboss-as) which may wish to customize the view or nodes in some way or even the connection method, should have a chance to claim the detected vm as a duplicate of a connection they already represent. 
> For example, if the JMX view already has a (disconnected) Wildfly node for a stopped Wildfly instance, starting the Wildfly server will quickly cause the JVM Monitor code to discover the vm.  The jmx connection provider in charge of turning this into a proper connection should first query all extenders to ask if this is a duplicate that should be suppressed or hidden. 



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)