[
https://issues.apache.org/jira/browse/DIRSTUDIO-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seelmann resolved DIRSTUDIO-249.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0
Assignee: Stefan Seelmann
Fixed here: http://svn.apache.org/viewvc?rev=602749&view=rev
Note: When JNDI sends an implicit ManageDsaIT control this one isn't logged,
see DIRSTUDIO-247
> Modification Logs view does not display request controls, if sent to the
> server
> --------------------------------------------------------------------------------
>
> Key: DIRSTUDIO-249
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-249
> 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
> Assignee: Stefan Seelmann
> Priority: Minor
> Fix For: 1.1.0
>
>
> Although it is probably a more general defect, here is the scenario where I
> figured it out.
> 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
> #!RESULT OK
> #!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 (http://www.faqs.org/rfcs/rfc2849.html) for details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
