[ https://issues.jboss.org/browse/JBIDE-8857?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-8857: ------------------------------------ Attachment: refresh-on-workspace-change.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8857?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-8857: ------------------------------------ Also, after comparing use to the tomcat page, there are huge differences between what hte tomcat page is doing and what ours does. The Tomcat page is actually representing what modules are added to and removed from the server. If you notice, when you create a new Dynamic web project, the tomcat's second page does not automatically add the module to this page. In fact, you can make 50 new Dynamic web projects and none of them are added. The tomcat page is a representation of what is on the server. So the tomcat page is also not responding to every workspace change event with similarly long-running API calls. When I created and opened a new Tomcat server, with no projects in the workspace, the "Add Web Module..." button on their second page was disabled. After creating 3 or 4 new projects, the "Add Web Module..." button was *STILL* disabled, because the tomcat plugin does not update its widgets after every workspace change event. In order to update the tomcat second page, I had to close and re-open the tomcat editor. At least we have a 'refresh' button so the user does not need to close and re-open the page. What you *might* have seen was the automatic removal from the list when you delete a project, but this is more because the project was removed from the server than that the project was removed from the workspace. The tomcat second page is only representating what modules are currently attached to the server adapter, and it *does* listen to those events, because responding to those events does not happen often, and also, does not require making use of long-running API calls that load bundles. Sorry, but I still think this has to be rejected. Using long-running API calls from the UI thread after every workspace change is a recipe for death. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8857?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8857: --------------------------------------- Priority: Minor (was: Major) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8857?page=com.atlassian.jira.plugin... ] Jaroslav Jankovič closed JBIDE-8857. ------------------------------------ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira