directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <>
Subject [jira] Commented: (DIRSTUDIO-249) Modification Logs view does not display request controls, if sent to the server
Date Sun, 09 Dec 2007 19:39:43 GMT


Stefan Seelmann commented on DIRSTUDIO-249:

Here is the class responsible for doing the logs:

There is already an TODO in the class. The cause why it isn't implemented yet is because I
am not sure about the encoding of control values. Of course for the Tree Delete Control it
is quite easy because it doesn't contain a control value.

> Modification Logs view does not  display request controls, if sent to the server
> --------------------------------------------------------------------------------
>                 Key: DIRSTUDIO-249
>                 URL:
>             Project: Directory Studio
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Client:
> Windows XP SP 2
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Apache Directory Studio 1.0.1
> Server:
> Solaris 9 (SPARC)
> IBM Tivoli Directory Server 6.0
>            Reporter: Stefan Zoerner
>            Priority: Minor
> Although it is probably a more general defect, here is the scenario where I figured it
> If a server supports the Tree Delete control (OID 1.2.840.113556.1.4.805), Studio deletes
subtrees of entries with the help of it, which is quite nice.
> Unfortunately, the Modification Logs view does not display in the LDIF that the controls
has been used. It only shows the deletion of the parent entry of the tree, like
> #!CONNECTION ldap://degas:389
> #!DATE 2007-12-09T20:02:45.359
> dn: ou=parent,dc=TIVOLIDS,dc=DEGAS
> changetype: delete
> In order to replay the file in the logs, inclusion of the control is required, like
> dn: ou=parent,dc=TIVOLIDS,dc=DEGAS
> control: 1.2.840.113556.1.4.805 true
> changetype: delete
> See RFC 2849 ( for details.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message