[ https://issues.jboss.org/browse/JBIDE-12580?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12580: ------------------------------------- Fix Version/s: 4.0.x (was: 4.0.0.Alpha2) Priority: Minor (was: Major) Workaround Description: Manually refresh the view by using the "Refresh" entry in the context menu of the tree. The cause is that most actions simply trigger a refresh of the OpenShift Explorer view. These actions keep a reference to the view they shall refresh. If you close the view and reopen it, you'll get a new view, the reference is pointing to a view that was disposed. The actions should trigger a refresh in MVC manner: make the model fire a change event. The new view would then react to it and refresh itself. -- 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

[ https://issues.jboss.org/browse/JBIDE-12580?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-12580 at 9/11/12 6:10 AM: ------------------------------------------------------------------- The cause is that most actions simply trigger a refresh of the OpenShift Explorer view. These actions keep a reference to the view they shall refresh. If you close the view and reopen it, you'll get a new view, the reference is pointing to a view that was disposed. The actions should trigger a refresh in MVC manner: make the model fire a change event. The new view would then react to it and refresh itself. The current implementation has UserModel#fireUserChange(user) for this sake. was (Author: adietish): The cause is that most actions simply trigger a refresh of the OpenShift Explorer view. These actions keep a reference to the view they shall refresh. If you close the view and reopen it, you'll get a new view, the reference is pointing to a view that was disposed. The actions should trigger a refresh in MVC manner: make the model fire a change event. The new view would then react to it and refresh itself. -- 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