18 Dec, 2006

3 commits

  • update the abandon operation count when appropriate.  Also, update a number of
    test cases to verify that the LDAPStatistics information is properly updated.
    
    OpenDS Issue Number:  1116
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@900 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • Fix some minor bugs related to focus.
    
    Fix some minor layout bugs related to the background color.
    
    Modify the code to check whether the server is running or not.
    
    Fix issue 1112 by adding an additional check to detect if we can use a port or not: use a Socket to bind to the port.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@897 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • archive is maintained.  Rather than keeping the archive as a single zip file,
    it is now maintained as a directory of gzip-compressed files.  This is much
    faster and more scalable.  On my desktop machine, it reduces the time to run
    unit tests by about 75% (from about 7.5 minutes to less than 2 minutes).
    
    OpenDS Issue Number:  1115
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@894 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

17 Dec, 2006

2 commits


15 Dec, 2006

5 commits


14 Dec, 2006

1 commit


13 Dec, 2006

1 commit


12 Dec, 2006

1 commit

  • the protocol, listen address/port, number of established connections, and
    information about each connection.
    
    Also, update the monitor API to make it possible to include a custom
    objectclass in each monitor entry.  Connection handler monitor entries now
    include the ds-connectionhandler-monitor-entry objectclass.  Backend monitor
    entries now include the ds-backend-monitor-entry objectclass.
    
    OpenDS Issue Numbers:  1066 and 1091
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@866 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

11 Dec, 2006

3 commits

  • …g file permissions on the directory containing the database files. No errors are produced if there are no way to set the file permissions (ie. Windows and Java < 6.0).
    
    Fix for issue 1005
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@861 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • 1. Fix a bug with the setup script.  Know this script is executable after the Web Start based installation.
    
    2. Provide a different welcome message in the setup depending on whether we are launching the setup from the command line or Web Start.  If we are launching the command line setup we make reference in the message to the Web Start installation and provide a link to the downloads page.
    
    3. When the setup is successful, include in the message the path of the installation as was requested by William Hathaway.
    
    4. Try to find a valid default port  (of type []389) and not limit the search to 389.  This implies not having any explanatory message to be displayed if we cannot connect to 389.
    
    5. Update the code to better handle bug scenarii.  Previously the code assumed that only RuntimeException could occur in case of a bug.  This is not true in the general case, so know the code handles Throwable objects to detect bugs.
    
    6. Provide the first implementation for the Uninstaller.  Some code has been rearranged to maximize code re-use.  The first implementation of the uninstaller basically does the following:
    
    - Display a confirmation message informing of what will happen with the installation files and the consequences of uninstalling the server.
    
    Ask the user which parts of the server must be uninstalled.
    
    Check if we have configuration references outside the installation path (for the moment this check is limited to database files and log files). If these references exist show them to the user and ask the user whether these 'external' files must be deteled or not.
    
    If the server is running we ask for confirmation to stop the server and if we are in windows we ask the user to provide a DN and a password to authenticate.
    
    If the user continues and the server is running the code calls stop-ds script, if the script succeeds the code tries to delete the files in the installation that the user wanted to uninstall and  in the case there are external files to the installation path and the user wants to delete them delete also these external files.
    
    If everything works properly the uninstaller will delete all the files except the <install-root>/lib/quicksetup.jar and <install-root>/lib/OpenDS.jar file.
    
    OpenDS.jar file is required by the command line uninstaller to share some code.
    
    I preferred not to try to delete these files from the scripts as we cannot provide proper feedback (for instance localization) if we encounter a problem deleting these files.
    
    In both cases we inform the user that there are some files that must be deleted manually.
    
    7. Provide the code to launch uninstall through command line that is analogous in terms of interaction to the graphical one.
    
    I have included two scripts to launch the uninstallation.  The uninstall script for Unix is very similar to the setup script.  However the uninstall.bat script has a difference with setup.bat.
    
    The difference is that I limit the class path to include only quicksetup.jar.  This is done because I have not found a way to delete the jar files that are in the class path of the java application using pure java code, so as the uninstaller does only require OpenDS.jar and quicksetup.jar files I have chosen to minimize the jar files in the class path.
    
     This way the only files that are not deleted during installation is quicksetup.jar and OpenDS.jar.
    
    8. Improve the wording of the install wizard as proposed by Brian and Neil.
    
    9 . One minor tweak to the QuickSetup Welcome screen: make the reference to the "setup" command a monospace font to highlight it a bit more.
    
    10.  Fix for issue 1057  (stop-ds.bat and start-ds.bat do not work when called using Runtime.exec).  The quicksetup code used to overwrite the environment variables when calling Runtime.exec which made the server not be able to start/stop correctly.
    
    11. Fix some minor bugs with the default focus on some panels.
    
    12. Update the setup scripts to use the java home file if the setup was previously called.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@860 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • batch file that can be used to set JAVA_HOME.  Update all of the tools and
    administrative scripts provided with OpenDS so that they will use this to set
    JAVA_HOME unless it's already set in the user's environment.
    
    OpenDS Issue Number:  1082
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@856 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

09 Dec, 2006

1 commit


08 Dec, 2006

3 commits

  • contained in that backend.  Also, create a new monitor entry for each
    registered backend that will report the backend ID, base DNs, writability mode,
    and entry count for that backend.
    
    OpenDS Issue Numbers:  1062, 1063
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@853 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 593: attribute indexes need to support subtypes and options
    1045: possible index corruption (subtree search fails to return matching entry)
    1060: entry disappears when modifying with ldapbrowser
    
    There were bugs in the way an equality index was updated for a modify operation.  Trying to determine the index changes from the sequence of modifications did not work in the general case.  Now, it ought to be correct in all cases.
    
    I've changed many of the modify operation unit tests to run against the JE backend instead of the memory backend.  Also I changed the tests to modify the mail attribute instead of description, because description is not indexed.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@852 41b1ffd8-f28e-4786-ab96-9950f0a78031
    coulbeck
     
  • include a structural objectclass.
    
    OpenDS Issue Number:  1067
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@850 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

07 Dec, 2006

1 commit


05 Dec, 2006

3 commits

  • - It fixes problems with base DN registration when attempting to use nested
      backends.
    
    - It changes the terminology that is in use.  Previously, the term "suffix" was
      used everywhere, even when it wasn't really correct.  Now "naming context" is
      used when it's talking about a top-level base DN, and "base DN" is used for
      any base DN regardless of whether it's a naming context.
    
    - It adds a new ds-private-naming-contexts operational attribute to the root
      DSE to list the private naming contexts defined in the server.
    
    - It updates the backend API to get rid of the abstract supportsControl and
      supportsFeature methods and replace them with a default concrete
      implementation.
    
    
    OpenDS Issue Numbers:  546, 750
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@844 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • as specified by RFC4512 :
    
     SyntaxDescription = LPAREN WSP
             numericoid                 ; object identifier
             [ SP "DESC" SP qdstring ]  ; description
             extensions WSP RPAREN      ; extensions
    
    see SYNTAX_LDAP_SYNTAX_OID from org.opends.server.schema.LDAPSyntaxTest.java
    
    Issue 640.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@840 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     
  • -1 when attempting to get the last login time for a user when it isn't possible
    to do so for some reason.  Even though the documentation said it would return
    -1 in this case, it was actually returning the creation timestamp for the
    entry.
    
    OpenDS Issue Number:  1055
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@839 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

30 Nov, 2006

9 commits


29 Nov, 2006

1 commit


22 Nov, 2006

1 commit

  • …formatting of the messages that appear in the progress panel.
    
    This is done mainly for two reasons:
    
    1. The code in the Installer class should not control the format used (HTML, plain text, etc.) which is more related to the pure UI.
    2. Be able to share this formatting code for the graphical installation and also the uninstallation so that we have the same look and feel in both without code duplication." /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/installer/Installer.java /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/installer/offline/OfflineInstaller.java /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/installer/webstart/WebStartInstaller.java /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/QuickSetup.java /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/ui/CurrentStepPanel.java /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/ui/ProgressPanel.java /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/ui/QuickSetupDialog.java
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@771 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

21 Nov, 2006

2 commits

  • …formatting of the messages that appear in the progress panel.
    
    This is done mainly for two reasons:
    
    1. The code in the Installer class should not control the format used (HTML, plain text, etc.) which is more related to the pure UI.
    2. Be able to share this formatting code for the graphical installation and also the uninstallation so that we have the same look and feel in both without code duplication.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@769 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Add some code to improve the displayed download progress bar.  Know the code takes into consideration the actual size of the jar files instead of considering that all have the same size.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@765 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

20 Nov, 2006

3 commits

  • …ything should work fine from the first time. 
    
    If it does not work, just throw an exception 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@756 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • bug in which "TH" was incorrectly mapped to a capital letter "O" (oh) instead
    of the number "0" (zero).
    
    This fix was provided by Terry Sigle (username tsigle).
    
    OpenDS Issue Number:  690
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@754 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • …Java WebStart Setup.  There were two issues with the existing code:
    
    1. We used to pass the parameter 'overallPercent' of the validating method of WebStartDownloader to calculate the downloaded percentage.  This is wrong as this value corresponds to the validation percentage.  This produced to sometimes display a downloaded 0 % while we were validating the files.
    
    2. We did not provide any additional feedback while we were validating a jar file.  This produced the displayed message to be stuck at 'Downloading: 33 % Completed' or 'Downloading: 66 % Completed'.
    
    
    The fix for the first issue is trivial: the value indicating the percentage of downloaded files is not modified in the validating method nor in the upgradingArchive method of the WebStartDownloader class.
    
    The fix for the second issue consists of adding some interfaces to WebStartDownloader to know whether we are downloading a jar file, validating a jar file or upgrading a jar file.  In addition to that two methods have been added to know how much of the current jar file has been validated or upgraded.  This way we can have know a more complete (and lively) message during download.  When we are just downloading a jar file the message will stay the same.  For example:
    
    
    'Downloading: 23 % Completed'
    
    But when we are validating a jar file the message will be:
    
    'Downloading: 33% Completed - Validating file: 89 % Completed.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@753 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara