org.forgerock / org.forgerock.opendj

01 May, 2007

4 commits

30 Apr, 2007

2 commits

28 Apr, 2007

1 commit

27 Apr, 2007

6 commits

26 Apr, 2007

5 commits

25 Apr, 2007

3 commits

24 Apr, 2007

3 commits

  • 01792e94   Make several significant changes to the OpenDS code base, including: ... Browse Dir » 
    - 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
     
  • e277c33e   Fix for [Issue 1401] revoke support for '/' as option prefix ... Browse Dir » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1690 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • 568b5065   This change (no associated issue no.) addresses some counter-intuitive behavior … ... Browse Dir » 
    …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

5 commits

20 Apr, 2007

3 commits

19 Apr, 2007

1 commit

  • 21b5c006   Fix for issue 1442. ... Browse Dir » 
    This change introduces a new style-sheet which generates
en_US property files containing all the description elements
from the XML configuration definitions. In order to expose
these properties the admin framework APIs have been modified
as follows:

   * managed object definitions
         o user friendly name
         o user friendly plural name
         o synopsis
         o description

   * property definitions
         o synopsis
         o description
         o unit description (for integer properties)
         o value descriptions (for enumeration properties)
         o pattern descriptions (for string properties). This is pretty
           much useless at the moment since the string property
           definition class does not support patterns (even though the
           XML schema does): issue 1523
         o alias default behavior description

   * relation definitions
         o synopsis
         o description
         o user friendly name (usually the user friendly name of the
           referenced managed object)
         o user friendly plural name for one-to-many relations (usually
           the user friendly plural name of the referenced managed object)

Since there is currently only weak API support for required admin
actions (issue 1426), the admin action descriptions cannot be exposed
through any API at this stage.

For I18N, translators are expected to take the generated property
files and translate them into localized versions.



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

18 Apr, 2007

4 commits

17 Apr, 2007

3 commits