20 Dec, 2007

1 commit


19 Dec, 2007

4 commits

  • Override the CLI naming argument for virtual attributes so that it is now "name".
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3592 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • It is now possible to override the default naming argument for dsconfig sub-commands using the CLI profile in the XML definitions. To do this add the "naming-argument-override" attribute to a relation's CLI profile relation element. For example:
    
     <adm:relation name="virtual-attribute">
       <adm:one-to-many />
       <adm:profile name="ldap">
         <ldap:rdn-sequence>
           cn=Virtual Attributes,cn=config
         </ldap:rdn-sequence>
       </adm:profile>
       <adm:profile name="cli">
         <cli:relation naming-argument-override="name">
           <cli:default-property name="enabled" />
           <cli:default-property name="attribute-type" />
         </cli:relation>
       </adm:profile>
     </adm:relation>
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3591 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • …a new Local DB Backend is created. The default indexes are aci (presence), objectClass (equality), entryUUID (equality).
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3586 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • Add support to the admin framework for specifying one or more "default" managed objects which should be created automatically when a parent managed object is created. The XML mark-up is provided as part of the parent managed object's relation definition as follows (the sample is taken from the LocalDBBackend XML definition):
    
         <adm:relation name="local-db-index">
           <adm:one-to-many naming-property="attribute">
    
             <adm:default-managed-object name="aci">
               <adm:property name="index-type">
                 <adm:value>presence</adm:value>
               </adm:property>
               <adm:property name="attribute">
                 <adm:value>aci</adm:value>
               </adm:property>
             </adm:default-managed-object>
    
             <adm:default-managed-object name="entryUUID">
               <adm:property name="index-type">
                 <adm:value>equality</adm:value>
               </adm:property>
               <adm:property name="attribute">
                 <adm:value>entryUUID</adm:value>
               </adm:property>
             </adm:default-managed-object>
    
             <adm:default-managed-object name="objectClass">
               <adm:property name="index-type">
                 <adm:value>equality</adm:value>
               </adm:property>
               <adm:property name="attribute">
                 <adm:value>objectClass</adm:value>
               </adm:property>
             </adm:default-managed-object>
           </adm:one-to-many>
    
    The functionality is implemented on the client-side API in a generic manner so that it is independent of the underlying driver implementation (so the default indexes would be created if we had an offline direct to file driver as well).
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3585 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

18 Dec, 2007

2 commits

  • We now log (notice, instead of error) a more explicit message that tells an SSL connection attempt failed (from node xxx) to the replication server.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3584 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mrossign
     
  • The fix consists on adding a verbose option to the setup command-line.
    
    With these modifications the graphical setup and the CLI setup (by default) run in non-verbose mode.  The logs for import and start are not displayed, nor we make any reference to the ADS when configuring replication.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3582 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

17 Dec, 2007

6 commits

  • …les.  The bug prevented the Java WebStart installer to create set-java-home.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3577 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3575 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     
  • We check now if it's an absolute path.
    If it's a relative path, we add the instance root path to get the actual file location
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3574 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • Update the indentation as proposed in the issue description.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3573 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Note: this issue is not fully covered by the proposed modifications but
    all that is missing in order to fix it is to figure out which are the
    default memory values that we want to propose in the setup.
    
    2620: Server should be started as server JRE and clients should be
    started as client JREs
    
    The proposed solution goes beyond fixing the two issues and proposes a
    manner for the user to set specific java arguments (and use a specific
    JVM) for every command-line.
    
    Today the user can specify the JVM to be used using the OPENDS_JAVA_HOME
    environment variable and the java arguments by using the
    OPENDS_JAVA_ARGS environment variable.  In the case of the JVM this
    covers most of the use cases (in general we will use the same JVM for
    all the command-lines).  However this is quite limiting in the case of
    the java arguments we pass.  For instance in general we want to run the
    server (start-ds command-line) using the server mode of the JVM but
    other command-lines using the -client mode of the JVM.  In the same
    manner we might want to have a bigger heap when running the server than
    when we are running a "lightweight" utility as dsconfig.
    
    The proposed solution is to have a properties file called
    java.properties where the user specifies the different JVM and java
    arguments to be used for every command-line.  Once the user has edited
    this properties file, (s)he must run a command-line called
    dsjavaproperties that will update all the scripts to use the arguments
    specified in that properties file.
    
    NOTE: there are a number of command-lines (import-ldif, export-ldif,
    backup, restore) where the user will be able to specify different java
    arguments (and different JVM) to use depending on whether the
    command-line is run in online or offline modes.  You can see the
    comments on java.properties to get more information about this and in
    general about the different properties that can be set.
    
    The modification in the setup basically try to check if the JVM that is
    being used to run the setup (the one that will be used by default)
    supports the -client and -server options.  Depending on the results of
    these checks the setup will update the java.properties file and then run
    dsjavaproperties to update the scripts. 
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3572 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3562 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

14 Dec, 2007

3 commits


13 Dec, 2007

3 commits

  • In the error messages quote the values that are causing problems to help the user identify proble
    ms with trailing spaces.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3556 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Initialization of the ADS fails when both servers where configured for replication separately.
    
    The problem is that the entry that we read from the ADS is not complete (is missing the public key attribute).  So when we use the server entry we read from one ADS to register that server in the other ADS the registration is not complete.
    
    The fix consists simply on reading the public key certificate in the ADS when we construct the object representing the server.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3555 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Type in the class name
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3549 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     

11 Dec, 2007

1 commit


10 Dec, 2007

1 commit

  • If the Replication Server is stopped while the ServerHandler writer threads are blocked waiting for some window credit they are blocked and don't stop
    immediately.
    
    This issue is minimal for real life but can cause unit test failure because replication Servers are stopped and started a number of times during the tests.
    
    This commit also enabled some more replication tests and change them to make the
    order in which they are run more predictible.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3542 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

08 Dec, 2007

2 commits


07 Dec, 2007

2 commits

  • The classes in org.opends.messages need to be made public so that they can be referenced from other public APIs. This change adds the PublicAPI annotation to the classes defined in this package as follows:
    
       * the org.opends.messages package is VOLATILE
    
       * the org.opends.messages core classes (Message, MessageDescriptor,
         MessageBuilder, Category, and Severity) are all UNCOMMITTED
    
       * the class org.opends.messages.MessageDescriptorRegistry is PRIVATE
         (it's only used in unit tests)
    
       * generated message classes are PRIVATE
    
    In addition minor cleanup was made to the classes where appropriate to make them suitable for public APIs:
    
       * used "final" where possible
    
       * reduced visibility of classes, methods, and members where appropriate
    
       * fixed some potential bugs spotted during this clean-up: class
         members not being initialized (the "final" keyword is useful for
         spotting this!)
    
       * added missing javadoc
       
       * I've removed the third-party and user-defined message generation
         since we could see know way in which they could be easily used
         without impacting core OpenDS source
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3536 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • dsreplication enable fails to initialise schema of the peer if the user schema
    contains a new objectClass dependent on a new attributeType.
    
    This was happening because the validation of the new objectClasses was done using the
    old schema while it must be done with the new schema currently being modified. 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3532 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

06 Dec, 2007

1 commit


05 Dec, 2007

3 commits


04 Dec, 2007

3 commits


03 Dec, 2007

1 commit

  • …d init/fini processing relevant to entry cache for all
      active entry cache implementations instead of letting each entry cache implementation to be BackendInitializationListener on its
      own which can lead to unexpected results such as listener activity on already finilized entry cache implementation.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3517 41b1ffd8-f28e-4786-ab96-9950f0a78031
    abobrov
     

02 Dec, 2007

1 commit


29 Nov, 2007

3 commits


27 Nov, 2007

2 commits


26 Nov, 2007

1 commit

  • The fix consists in including a little bit more on context to the error message.
    
    For command-line dsconfig list-local-db-indexes --backend-name tasks -n -p 1389 -w s
    
    The output was:
    
    "Task Backend" is not a recognized component type
    
    With the fix the output is:
    
    "Task Backend" component type cannot be used with subcommand
    {list-local-db-indexes} 
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3497 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara