org.forgerock / org.forgerock.opendj

18 Mar, 2008

1 commit

17 Mar, 2008

1 commit

  • 094e1f14   These changes remove the temporary file limitation from import-ldif. Several oth… ... Browse Dir » 
    …er changes were made also:

- the cleaner is run at the end of the import

- the cleaner is run periodically during import if database eviction is detected

- the substring indexes are buffered to help boost performance during substring index processing

- the import files have been moved into its own package  org.opends.server.backends.jeb.importLDIF

- the work threads do most of the processing

- import aborts if a work thread throws a runtime exception

- messages for the various stages of the import have been added (e.g. environment close)

The only functionality missing is VLV index processing. Also, there is a  2G limit on the
max entry ID value that can be used in a substring index.

The following configuration attributes have been removed:

- ds-cfg-import-temp-directory
- ds-cfg-import-buffer-size
- ds-cfg-import-pass-size

The should be removed from your config.ldif file.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3979 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     

06 Mar, 2008

1 commit

27 Feb, 2008

1 commit

  • 069eb677   For Configuration Reference generated doc: ... Browse Dir » 
    Added 2 new parameters (java properties) for M1 needs (1st one only):

OpendsWiki - The URL of the OpenDS Wiki
             (default is "https://www.opends.org/wiki")
OpendsHome - The URL of the OpenDS project Home page
             (default is "http://www.opends.org")

Usage:
In the M1 build target, add :
      <jvmarg value="-DOpendsWiki=https://www.opends.org/<M1 Wiki>"/>
 
Note that as a side effect, now all the html files are generated (index.html and maintop.html were not generated until now)





git-svn-id: https://svn.forgerock.org/opendj/trunk@3907 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jcambon
     

22 Feb, 2008

1 commit

21 Feb, 2008

1 commit

20 Feb, 2008

1 commit

  • 21078a31   Fix for issue 2972 (The usage of stop-ds.bat shows the class name) ... Browse Dir » 
    The fix consists on updating the scripts and the java code to reflect correctly the name of the script and be consistent with all the other batch files (we don not include the .bat on the usage).

Apart from that the modifications include a modification in StatusPanelLauncher so that we use the ArgumentParser class in the whole class (this avoids duplicated code and fixes a bug with the usage).


git-svn-id: https://svn.forgerock.org/opendj/trunk@3900 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

19 Feb, 2008

1 commit

  • f100ec0f   Fix for issue 2969 (In some cases the arguments set for offline operations (impo… ... Browse Dir » 
    …rt-ldif, export-ldif) are the ones of the online mode)

The problem comes because when we are dealing with scripts that can have both online and off-line modes we call _script-util to know whether we must run the script in online or off-line modes.  This makes the environments variables to be set, so when we call the second time _script-util (to set the environment for the off-line mode) nothing is changed if the user specified not to overwrite the environment variables.

The fix consists on resetting the environment variables to its original state before calling _script-util for the second time.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3895 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

15 Feb, 2008

2 commits

12 Feb, 2008

2 commits

08 Feb, 2008

2 commits

05 Feb, 2008

1 commit

  • 18a5f38d   Fix for issue 2902 (stop-ds -R restarts the server with client tool JVM) ... Browse Dir » 
    When the java properties are set to not overwrite the environment variables (which is the default behavior) when we call start-ds from the stop-ds scripts, OPENDS_JAVA_ARGS is already set with the arguments for the stop (client arguments).  The fix consists basically on resetting the environment variables to those we had before calling stop-ds before calling start-ds.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3824 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

22 Jan, 2008

1 commit

21 Jan, 2008

1 commit

  • 5c98ae82   Fix issues 2831 and 1948. ... Browse Dir » 
    Change local DB backend configuration so that db-directory and import-temp-directory properties now name a parent directory within which a sub-directory is created having the same name as the backend-id. This simplifies configuration and reduces the risk of name collisions.

git-svn-id: https://svn.forgerock.org/opendj/trunk@3708 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

18 Jan, 2008

2 commits

17 Jan, 2008

2 commits

16 Jan, 2008

1 commit

  • 19ee981f   This fix removes the option to use nanosecond etime resolution as a JVM property… ... Browse Dir » 
    …. It is now a global configuration attribute. Due to the 10% throughput decrease I saw when using System.nanoTime, the default still uses System.currentTimeMillis to timestamp operations. System.nanoTime will only be used when the ds-cfg-etime-resolution attribute is set to nano-seconds.

Fix for issue 2499


git-svn-id: https://svn.forgerock.org/opendj/trunk@3686 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     

14 Jan, 2008

2 commits

  • dd793810   Add support to admin framework for retrieving an i18n description of the constra… ... Browse Dir » 
    …ints applicable to an aggregation property. This is required for issue 2004 (HTML configuration guide generation).

Two new methods are added to the AggregationPropertyDefinition: getSourceConstraintSynopsis() and getSourceConstraintSynopsis(Locale). All aggregation definitions which had constraints have been updated to included the description. In addition, dsconfig is modified to output the constraint description when displaying verbose help on aggregation properties.

git-svn-id: https://svn.forgerock.org/opendj/trunk@3669 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • 5bd2e865   Partial fix for issue 2661 - public APIs must not reference private classes. ... Browse Dir » 
    In org.opends.server.admin.Configuration replace

  ManagedObjectDefinition<...,...> definition()

With:

  Class<? extends Configuration> configurationClass()

And remove method:

  ServerManagedObject<...> managedObject()

This decouples generated server-side management APIs from the rest of the framework with the exception of configuration listeners.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3662 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

10 Jan, 2008

1 commit

  • b559735f   Fixes for : ... Browse Dir » 
    2786 : DSML Gateway misses saaj jars
2774 : DSML gateway war file contains many unnecessary files



git-svn-id: https://svn.forgerock.org/opendj/trunk@3654 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mmarie
     

08 Jan, 2008

1 commit

04 Jan, 2008

1 commit

03 Jan, 2008

3 commits

21 Dec, 2007

2 commits

19 Dec, 2007

2 commits

  • 20353bca   Fix issue 2451 part #1: https://opends.dev.java.net/issues/show_bug.cgi?id=2451 ... Browse Dir » 
    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
     
  • 8559dade   Fix for issue 2446 part #1. ... Browse Dir » 
    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
     

17 Dec, 2007

3 commits

  • 35263763   Fix global ACI mistakenly removed. ... Browse Dir » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3578 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     
  • 21b1a3fb   Add objectclass attribute to schema attributes. Issue 2759. ... Browse Dir » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3576 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     
  • b5ad1173   2730: New - The setup command should perform some basic memory tuning ... Browse Dir » 
    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
     

14 Dec, 2007

1 commit

08 Dec, 2007

1 commit

07 Dec, 2007

1 commit

  • 8cfaab0f   This relates to issue 2661 "public APIs must not reference private classes". ... Browse Dir » 
    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