Directory Studio
  1. Directory Studio
  2. DIRSTUDIO-481

Improve refreshing of attributes and children

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.0
    • Fix Version/s: 1.5.0
    • Component/s: studio-ldapbrowser
    • Labels:
      None
    • Environment:
      connection to ldap , happend in eclipse or stand alone

      Description

      When nodes attributes and childred are changed through another application
      the Refresh is very inconsistant.

      First there appears to be no way to refresh the whole tree.
      You have to select the node refresh. sometimes you have to hit F5, sometimes Right click action update attributes and children
      and sometime I have to use the tool bar refresh icon.

      I always have to click on each individual node and refresh each child entry. I have to cycle through the 3 options above because when a value is updated out side the studio. The 3 refresh options do not always work. One of them usually works. but which one is always a good question.
      When you refresh it should refresh the whole tree or aleast from the node and all children.
      Also refresh should have an option to not only refresh the children, but also their attributes.

        Activity

        Hide
        Pierre-Arnaud Marcelot added a comment -

        Apache Directory studio version 1.5.0 has been released.

        Show
        Pierre-Arnaud Marcelot added a comment - Apache Directory studio version 1.5.0 has been released.
        Hide
        Stefan Seelmann added a comment -

        One more comment to the second issue: I also had the issue that F5 stops to work, especially when running within Eclipse and using the debugger. I suppose that the debugger than takes over the F5 shortcut, but I have not clue how to fix that.

        Show
        Stefan Seelmann added a comment - One more comment to the second issue: I also had the issue that F5 stops to work, especially when running within Eclipse and using the debugger. I suppose that the debugger than takes over the F5 shortcut, but I have not clue how to fix that.
        Hide
        Stefan Seelmann added a comment -
        Show
        Stefan Seelmann added a comment - Fixed in trunk: http://svn.apache.org/viewvc?rev=778231&view=rev
        Hide
        Stefan Seelmann added a comment -

        Emmanuel told me on IRC, that he also runs into some issues with refreshing the DIT.

        So I checked the current behaviour: When browsing the DIT and expanding some entries, all the fetched attributes and parent-child relationships are cached in Studio. If the DIT gets updated somehow and one refreshes a particular entry in the LDAP browser, the following happens:

        • Only the selected entry's attributes are reloaded
          --> Attributes of children are not touched, they remain in the cache and when selecting such an entry after the refresh its old attributes are shown in the entry editor
        • Only the immediate child entries are reloaded
          --> Grandchild entries are not touched, they remain in the cache and remain visible in the LDAP browser tree

        So I would suggest to purge all cached parent-child relationships and attributes on refresh, beginning from the refreshed entry, recursively down the whole tree

        The open question is: Should all expanded branches below the refreshed entry also be reloaded? This could cause many additional search requests. The alternative (what I would prefer) is to collapse all branches below the entrys's immediate children. So if you have the tree below and refresh node 'b1', then only then immediate childen of 'b1' are refreshed and the 'c' nodes are collapsed

        a1

        -b1
        -c1
        -d1
        -e1
        -c2
        -c3
        -d3
        Show
        Stefan Seelmann added a comment - Emmanuel told me on IRC, that he also runs into some issues with refreshing the DIT. So I checked the current behaviour: When browsing the DIT and expanding some entries, all the fetched attributes and parent-child relationships are cached in Studio. If the DIT gets updated somehow and one refreshes a particular entry in the LDAP browser, the following happens: Only the selected entry's attributes are reloaded --> Attributes of children are not touched, they remain in the cache and when selecting such an entry after the refresh its old attributes are shown in the entry editor Only the immediate child entries are reloaded --> Grandchild entries are not touched, they remain in the cache and remain visible in the LDAP browser tree So I would suggest to purge all cached parent-child relationships and attributes on refresh, beginning from the refreshed entry, recursively down the whole tree The open question is: Should all expanded branches below the refreshed entry also be reloaded? This could cause many additional search requests. The alternative (what I would prefer) is to collapse all branches below the entrys's immediate children. So if you have the tree below and refresh node 'b1', then only then immediate childen of 'b1' are refreshed and the 'c' nodes are collapsed a1 -b1 -c1 -d1 -e1 -c2 -c3 -d3
        Hide
        Wise Wolfe added a comment -

        I am connection to an ADAM instance

        Show
        Wise Wolfe added a comment - I am connection to an ADAM instance

          People

          • Assignee:
            Stefan Seelmann
            Reporter:
            Wise Wolfe
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development