You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Zoerner (JIRA)" <ji...@apache.org> on 2007/12/09 20:21:43 UTC
[jira] Created: (DIRSTUDIO-249) Modification Logs view does not
display request controls, if sent to to server
Modification Logs view does not display request controls, if sent to to 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
Priority: Minor
Although it is probably a more general defect, here is the scenario where I figured it out.
f 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.
Re: [jira] Closed: (DIRSTUDIO-249) Modification Logs view does not display request controls, if sent to the server
Posted by Alex Karasulu <ak...@apache.org>.
This control would be easily implemented in ApacheDS. I'm drawing a blank
but any reason why we might have not implemented it?
Alex
On Dec 10, 2007 5:17 PM, Stefan Zoerner (JIRA) <ji...@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/DIRSTUDIO-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Stefan Zoerner closed DIRSTUDIO-249.
> ------------------------------------
>
>
> I have tested with my Treed Delete Control example against IBM Tivoli DS,
> and it looks nice. Well done, StefanS!
>
> > 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.
>
>
[jira] Resolved: (DIRSTUDIO-249) Modification Logs view does not
display request controls, if sent to the server
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (DIRSTUDIO-249) Modification Logs view does not
display request controls, if sent to the server
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Zoerner closed DIRSTUDIO-249.
------------------------------------
I have tested with my Treed Delete Control example against IBM Tivoli DS, and it looks nice. Well done, StefanS!
> 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.
[jira] Updated: (DIRSTUDIO-249) Modification Logs view does not
display request controls, if sent to the server
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre-Arnaud Marcelot updated DIRSTUDIO-249:
---------------------------------------------
Component/s: studio-ldapbrowser
> 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
> Components: studio-ldapbrowser
> 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.
[jira] Updated: (DIRSTUDIO-249) Modification Logs view does not
display request controls, if sent to the server
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Zoerner updated DIRSTUDIO-249:
-------------------------------------
Description:
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.
was:
Although it is probably a more general defect, here is the scenario where I figured it out.
f 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.
> 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
> Priority: Minor
>
> 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.
[jira] Updated: (DIRSTUDIO-249) Modification Logs view does not
display request controls, if sent to the server
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Zoerner updated DIRSTUDIO-249:
-------------------------------------
Summary: Modification Logs view does not display request controls, if sent to the server (was: Modification Logs view does not display request controls, if sent to to server)
> 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
> Priority: Minor
>
> Although it is probably a more general defect, here is the scenario where I figured it out.
> f 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.
[jira] Commented: (DIRSTUDIO-249) Modification Logs view does not
display request controls, if sent to the server
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549857 ]
Stefan Seelmann commented on DIRSTUDIO-249:
-------------------------------------------
Here is the class responsible for doing the logs: http://tinyurl.com/2ebdyc
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: 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
> Priority: Minor
>
> 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.