10 Jul, 2007

1 commit

  • In case on -V option, BuildExtractor will exit with a pre-defined return code defined in QuickSetupCli.java (let's say 50). Script will test this specific return value to check if the non-null return code is an error. In case of none null return code, the upgradeLauncher will not be called. 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2327 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     

09 Jul, 2007

4 commits

  • suggested minimum upper bound value from the schema definition attribute type description 
    syntax oid. For example:
    
    attributeTypes: ( 2.5.4.41 NAME 'name' EQUALITY caseIgnoreMatch
      SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768}
      X-ORIGIN 'RFC 4519' )
    
    to 
    
    attributeTypes: ( 2.5.4.41 NAME 'name' EQUALITY caseIgnoreMatch
      SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
      X-ORIGIN 'RFC 4519' )
    
    Setting this option to true will strip these values. The default behavior is to return
    the value. The server must be rebooted after the value has been changed.
    
    This is to provide a server work around for a bug in the JNDI 
    getAttributeSyntaxDefinition method that incorrectly uses the value as part of the
    syntax name.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2326 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     
  • This changes the category of some messages to match the class in which they are defined. It also adds a unit test to prevent categories from spanning multiple files in future.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2325 41b1ffd8-f28e-4786-ab96-9950f0a78031
    coulbeck
     
  • and move all of its methods into the abstract AccessControlHandler class.  This
    makes the access control API more future-proof because the use of an interface
    would not allow the introduction of new methods into the API (such as will be
    required for issue #1861) without breaking backward compatibility, and
    potentially interfering with third-party implementations.
    
    Also, the access control handler config manager implementation has been
    dramatically simplified.
    
    OpenDS Issue Number:  1912
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2324 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • Synopsis: import-ldif could allow to write skipped entries to a specified file
    
    Proposed solution
    -------------------------------
    I've added an option to the import tool so that the skipped entries (the entries that do not match criteria) are logged in a given file if required.
    Additionally the option -O, --overwriteRejects has been renamed into:
    -O, --overwrite. This option is now common to both reject file and skip file.
    Indeed if a user wants to append or overwrite a reject file, it is likely that he wants the same for the skip file.
    
    The new option is -K (--skipFile), the  updated option is -O (--overwrite)
    
    The usage:
    
    This utility may be used to import LDIF data into a Directory Server backend
    Usage:  java org.opends.server.tools.ImportLDIF {options}
                 where {options} include:
    -V, --version
        Display Directory Server version information
    ...
    -R, --rejectFile {rejectFile}
        Write rejected entries to the specified file
    -K, --skipFile {skipFile}
        Write skipped entries to the specified file
    -O, --overwrite
        Overwrite an existing rejects and/or skip file rather than appending to it
    ...
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2323 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jarnou
     

08 Jul, 2007

2 commits


07 Jul, 2007

6 commits


06 Jul, 2007

18 commits


05 Jul, 2007

9 commits