directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <>
Subject [jira] [Resolved] (DIRSTUDIO-788) Date and Time editor incorrect time format for eDirectory
Date Mon, 17 Jun 2013 14:55:20 GMT


Pierre-Arnaud Marcelot resolved DIRSTUDIO-788.

       Resolution: Fixed
    Fix Version/s: 2.0.0
         Assignee: Pierre-Arnaud Marcelot

Fix with commit 1493795.

We added a "Discard fraction (milliseconds)" checkbox which allows you to remove the fraction
from the value.
You don't need to check it every time the dialog is shown, the checkbox's selection gets remembered
automatically after the "OK" button is clicked.
That's the best we can do to support servers that don't correctly handle fraction values.
> Date and Time editor incorrect time format for eDirectory
> ---------------------------------------------------------
>                 Key: DIRSTUDIO-788
>                 URL:
>             Project: Directory Studio
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M2 (2.0.0.v20120127)
>         Environment: Windows 7 SP1 64-bit, ADS 2.0 M3
>            Reporter: Aleks M
>            Assignee: Pierre-Arnaud Marcelot
>             Fix For: 2.0.0-M8, 2.0.0
> I'm pretty confident that I could create new attribute values with the Time syntax in
ADS 1.5.x in Novell(NetIQ) eDirectory.
> This seems to have changed in 2.0
> When I try to add an attribute value to any object that has the time syntax ADS proposes
the following raw value format:
> 20120304150336.250Z
> eDirectory won't accept that and I have to edit the raw value so it looks like this
> 20120304150336Z
> I.e. I have to remove the dot and the three numbers before Z.
> I can mention that ADS correctly displays attributes with the time syntax, for example:
> modifyTimestamp, 2012-mar-04 16:03:14 CET (20120304150314Z)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message