16 Nov, 2007

6 commits

  • There is a problem in windows when we launch scripts using Runtime.exec if the script path contains a '=' character.  The fix consists on quoting the script paths on windows when we launch them using Runtime.exec.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3461 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • of component definitions as advanced and customizable:
    
    * advanced components: these will not be displayed by
      default in dsconfig. Examples include the various
      system backends
    
    * customizable components: these components are tagged
      as intended for customization using the CLI XML
      profile. Customizable components are usually the top
      level components previously referred to as "generic"
      by dsconfig. This term confused users who would, for
      example, mistake a "generic" backend for a JE backend.
    
    This change is part of issue 1829.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3460 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • …the user already provided it.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3459 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3458 41b1ffd8-f28e-4786-ab96-9950f0a78031
    smaguin
     
  • the last week.
    
    The issue 2604 has been opened to keep track of this problem.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3457 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • various clean-up to the XML definitions:
    
       * clean up typos and any bad grammar in the synopsis/description
         elements
    
       * fixed common errors. For example, there were many places where the
         synopsis was repeated in the description (the description is only
         ever used in conjunction with the synopsis). There were also many
         places where the <adm:user-friendly-name> was being used in
         property definition description elements to refer to the property
         name, when it actually refers to the managed object name
    
       * split big synopsis (not sure of the plural form - synopsi?) where
         possible - there were lots of cases where we'd have a big synopsis
         but no description
    
       * overrode properties with sensible default values where
         appropriate (for example, I provided sensible default values for
         some of the attribute-type properties in the virtual attribute
         definitions)
    
       * generally made documentation more consistent across the definitions
    
       * removed unneeded XML attributes of the form 'mandatory="false"'.
         Attributes only need to be specified if their value is true as
         they default to false. Adding redundant attributes just makes the
         XML harder to read
    
       * removed any documentation that referred to the configuration in
         LDAP related terms (with one exception in the Schema backend). All
         documentation now refers to other properties using the property
         names, not their associated LDAP attribute.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3456 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

15 Nov, 2007

3 commits

  • New two subcommands have been added to dsreplication:
    
    Usage:
    
    $ dsreplication pre-external-initialization --help
    dsreplication pre-external-initialization {options}
    This subcommand must be called before initializing the contents of all the replicated servers using the tool import-ldif or the binary copy method for replication to work.  You must specify the list of Base DNs that will be initialized and you must provide the credentials of any of the servers that is being replicated.  After calling this subcommand, you must initialize the contents of all the servers in the topology and after the initialization is over you must call the subcommand {post-external-initialization}.
    Global Options:    See "dsreplication --help"
    
    SubCommand Options:
    -h, --hostname {host}
        Directory server hostname or IP address
    -p, --port {port}
        Directory server port number
    -Z, --useSSL
        Use SSL for secure communication with the server
    -q, --useStartTLS
        Use StartTLS to secure communication with the server
    -l, --only-local
        Use this option when only the contents of the specified directory server will be initialized with an external method (import-ldif command or binary copy)
    
    
    $ dsreplication post-external-initialization --help
    Usage:  dsreplication post-external-initialization {options}
    This subcommand must be called after initializing the contents of all the replicated servers using the tool import-ldif or the binary copy method for replication to work.  You must specify the list of Base DNs that have been initialized and you must provide the credentials of any of the servers that is being replicated.  See the usage of the subcommand {pre-external-initialization} for more information.
    
    Global Options:
        See "dsreplication --help"
    
    SubCommand Options:
    -h, --hostname {host}
        Directory server hostname or IP address
    -p, --port {port}
        Directory server port number
    -Z, --useSSL
        Use SSL for secure communication with the server
    -q, --useStartTLS
        Use StartTLS to secure communication with the server
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3455 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • …dy sent changes must not be able to replicate with an empty replication server
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3454 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3453 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     

14 Nov, 2007

3 commits


13 Nov, 2007

7 commits


12 Nov, 2007

8 commits


09 Nov, 2007

7 commits


08 Nov, 2007

5 commits

  • in schema backend files and is not returned when searching.
    
    This code fixes the problem and also generalize the ability to store
    user attributes in the schema backend.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3427 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • The problem is that there is a timeout when reading the monitoring informations 
    on the server and the code did not handle this properly.
    
    I have made the method Utils.getMessage to handle properly the case when a Topol
    ogyCacheException has not a Throwable cause.  In addition to that the method ret
    urns a specific message when a timeout occurs.  Finally the timeout thresold has
     been risen from 10 to 30 seconds to be able to read the topology.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3426 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • cate since this can break some clients.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3425 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Fix the copy/paste errors in the description of the destination server arguments for the dsreplication initialize sub-command.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3424 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • …up and status command-lines in the formatting and in the format used to present certificates to the user.
    
    Fix some bugs in the way the ADS was updated when an instance is uninstalled.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3423 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

07 Nov, 2007

1 commit