[jbosstools-issues] [JBoss JIRA] (JBIDE-24593) Reconnect to jmx yields progress monitor errors

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-24593:
-------------------------------------

I'll make a patch here, but, you probably won't be happy with it. 

The fact is, each node gets its own job, which means they have their own progress monitors. So if you had 5 expanded objectname nodes, you'd now get 5 jobs running at once, and each job will have a very simple progress workflow. 

See, the MBeanServerConnection API has no notion of progress monitors. It's an official java api, so I can't change the interfaces to respect progress monitors. So what we'll end up with is a few methods that basically begin a progress monitor, move it 5%, then execute their 1 atomic command on the mbean server connection, and then mark the monitor as done. 

It will behave almost identically to what you see now, except with maybe a label as to what the current task is. You won't be pleased with the outcome, but it will be the best i can do without rewriting official java APIs ;) 

> Reconnect to jmx yields progress monitor errors
> -----------------------------------------------
>
>                 Key: JBIDE-24593
>                 URL: https://issues.jboss.org/browse/JBIDE-24593
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jmx
>    Affects Versions: 4.5.0.AM1
>            Reporter: Rob Stryker
>             Fix For: 4.5.0.AM2
>
>         Attachments: JMXLoad.mp4
>
>
> when I connect, expand some nodes, call refresh, collapse them then disconnect then reconnect, all the previously expanded node are loaded with a progress monitor which is not showing progress and stay blocked at 0% 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)