[ https://issues.jboss.org/browse/TEIIDDES-1708?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1708: ------------------------------------------- Sadly, it is impossible to keep the folder from collapsing. When an event occurs (in this case a DeleteDataSourceEvent), a refresh is called on the server node in the tree. At that point, the tree is refreshed and the expand/collapse state is lost. According to [this|http://ramkulkarni.com/blog/maintaining-expandcollapse-state-in-ecli...], it is only possible to maintain the expand/collapse state if the hashcode/equals methods are overridden in the node classes. However, the design of the tree currently prohibits this. When a server connection is made, the content provider creates the parent node and adds a 'pending-loading' child node to it. The refresh thread is then responsible for converting the 'pending-loading' child into the real nodes. This thread jumping is essential to avoid connecting to the server using the UI thread, leading to deadlocks. The inclusion of the 'pending-loading' children steps makes it impossible to keep the original child nodes, and hence the expand/collapse state. -- 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