25 Apr, 2007

7 commits


24 Apr, 2007

7 commits

  • - Narrow down the set of packages that external developers will need to access
      in order to write a plugin or other type of extension.  Hopefully, for most
      things developers will only need to interact with the following packages (and
      their sub-packages):
      * org.opends.server.admin
      * org.opends.server.api
      * org.opends.server.config
      * org.opends.server.protocols.internal
      * org.opends.server.types
      * org.opends.server.util
    
    - As part of the attempted narrowing of packages that external developers need
      to access, I have moved the org.opends.server.core.Operation and
      org.opends.server.protocols.ldap.LDAPException classes to the
      org.opends.server.types package.  I have also created
      org.opends.server.types.RawAttribute to wrap the
      org.opends.server.protocols.ldap.LDAPAttribute class, and
      org.opends.server.types.RawModification to wrap the
      org.opends.server.protocols.ldap.LDAPModification class.
    
    - I have updated the internal operations API to add a few new convenience
      methods when performing internal operations.
    
    - I have updated all of our message strings so that none of them end in periods
      (except those that end with an ellipsis).  This will help us avoid the
      problem in which we see multiple periods due to embedding one message in
      another.
    
    - I have moved a message file from a synchronizaiton package to the messages
      package and resolved conflicts with existing message IDs.
    
    - I have updated a number of cases in which
      StaticUtils.stackTraceToSingleLineString() was used in client-facing code to
      replace those calls with StaticUtils.getExceptionMessage() instead.  This
      should provide a more user-friendly message that will hopefully not reduce
      our ability to debug problems that may arise.
    
    - I have cleaned up some of the code in the org.opends.server.api package so
      that all of the classes use consistent formatting, and to fix a couple of
      potential Javadoc problems.
    
    - I have moved the build-tools/src directory to src/build-tools to be more
      consistent with other components of the server.
    
    - I have updated the build script so that the xslt task will no longer dump
      lots of output to the terminal when generating code.  I have also gotten rid
      of warnings about run.classpath not being set properly.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1695 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@1694 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@1693 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     
  • The message has been improved on the server side, but however the code of statuspanel has been modified to explicitly call the method close of the different DirContext objects when they are no longer used.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1692 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • …e.exec and providing some passwords in clear.  The modifications in the code use the OuputStream of the process that is generated to pass the password.  The resulting code depends has been tested using JDK 1.5 and 1.6 on Solaris sparc, Windows XP and Linux 2.4.7.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1691 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@1690 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • …discovered when specifying some duration based properties:
    
       * duration and size units had to be specified in default behaviors
    
       * upper/lower limit had to be specified without a unit and with
         values in the property's base unit (bytes for size properties)
    
    This change enables us to specify duration and size property constraints and defaults with or without units (when no unit is specified we default to the property's base unit).
    
    The Duration{Unit|PropertyDefinition} APIs have also been re-aligned with the Size{Unit|PropertyDefinition} APIs where possible and the unit tests updated (incl. replacing many bad uses of the assert keyword with the assertEquals TestNG method).
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1689 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

23 Apr, 2007

13 commits


20 Apr, 2007

7 commits


19 Apr, 2007

6 commits

  • (one-to-many) relations. Listener registration would fail if
    the entry associated with the relation did not exist (this is
    the case when the parent managed object has only just been
    created). The solution is to wait for the "relation" entry
    to be created and, when it is added, automatically register
    the add/delete listener then. This automatic registration is
    managed by a "delayed" config add listener which is registered
    against the parent managed object.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1668 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • …g since it can take a while.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1667 41b1ffd8-f28e-4786-ab96-9950f0a78031
    davidely
     
  • method that wasn't introduced until Java 6.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1666 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • …e possibility of configuring SSL and Start TLS.
    
    In the particular case where the user provides a keystore with multiple certificates, the user is prompted to choose one of the certificates.
    
    The committed changes include Neil's wording proposal and fix both the bug he found using PKCS#11 and the layout problem.
    
    When the user chooses to enable SSL or StartTLS, the code does the following:
    
    * In the particular case of the self-signed certificate a random password is generated and a JKS keystore is created under <server_root>/config/keystore.
    
    * In all cases where  the password to access the keystore is stored in clear under <server_root>/config/keystore.pin.
    
    * In all cases a JKS Trust Store containing the server certificate is created under <server_root>/config/truststore.  Please tell whether using a Blind Trust Manager is a better alternative.
    
    Known Issues and Limitations
    ============================
    
    The code in CertificateManager must be updated to avoid calling keytool with the password in clear.
    
    The setup will not work if the keystore's password and the certificate key password are different.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1665 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • …his is already done for the off
    line graphical installer).
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1664 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@1663 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff