[jbosstools-issues] [JBoss JIRA] (JBIDE-12563) Show in MBean Explorer not available when it should be

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-12563.
---------------------------------

    Resolution: Done


in JBT I can replicate as follows:

1) open workspace
2) Add runtime-path to be searched on every startup (path which has jboss 7.1.1)
3) restart workbench
4) runtime dialog comes up, discovers as7.1.1
5) Accept discovery
6) Servers view is opened automatically with new server showing and selected
7) right-click server, start
8) wait for startup, then right-click and show in mbean explorer
9) repeat 8)

It seems the issue here is that the action's state model is only updated whenever a selection in the server view changes. The show-in-mbean-explorer action is created after the server is already selected, so no change in selection is occurring. 

To fix this, after instantiation, an automatic call to selectionChanged(etc) will force the action to properly initialize its state based on the current selection of the viewer. 

One line fix. 
                
> Show in MBean Explorer not available when it should be
> ------------------------------------------------------
>
>                 Key: JBIDE-12563
>                 URL: https://issues.jboss.org/browse/JBIDE-12563
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 4.0.0.Alpha1
>         Environment: JBT 4.0.0.Alpha1 B6
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.0.0.Beta1
>
>         Attachments: mbean-gray.png
>
>
> When you start EAP 5.1.2 and then try to invoke server -> Show in -> MBean Explorer, it is grayed out and cannot be clicked. But when I open the MBean Explorer manually I can access the server's mbeans no problem.

--
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