directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSTUDIO-99) Display both OID and text for controls etc. in the property page of the Root DSE
Date Thu, 10 May 2007 21:46:15 GMT

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494850
] 

Stefan Seelmann commented on DIRSTUDIO-99:
------------------------------------------

One more suggestion: We could create a value editor for supportedControls, supportedExtensions
and supportedFeatures or more general for the OID syntax 1.3.6.1.4.1.1466.115.121.1.38. It
just has to decorate the OID string with the description. The implemention could be similar
to the  o.a.d.l.valueeditors.time.InPlaceGeneralizedTimeValueEditor value editor. With such
an value editor the OIDs and their corresponding description could just be displayed within
the EntryEditor.

To translate the OIDs to their description a lookup table would be great. Or is there already
some kind of OID-to-description registry in ldap-shared?

> Display both OID and text for controls etc. in the property page of the Root DSE
> --------------------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-99
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-99
>             Project: Directory LDAP Studio
>          Issue Type: Improvement
>         Environment: LDAP Studio 0.8.0
>            Reporter: Stefan Zoerner
>             Fix For: 0.8.0
>
>         Attachments: screenshot-1.jpg
>
>
> Currently, LDAP Studio displays either the OID of a supported LDAP control in the property
page, or a text (if the OID is known to LS). See screenshoot for an example. I would prefer
if both the OID and the description are shown, because the OID makes a good search term for
Google etc. if someone tries to find out more about it. The same holds true for LDAP extended
operations and features.
> Idea: Possible solutions would be using the forms
> 1.2.840.113556.1.4.805	(Tree Delete)
> or
> Tree Delete (1.2.840.113556.1.4.805)
> if control (feature ...) known. 

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


Mime
View raw message