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 Seelmann (JIRA)" <ji...@apache.org> on 2007/10/28 11:16:50 UTC

[jira] Assigned: (DIRSTUDIO-229) Check if LdapDN/RDN or LdapName/Rdn could be used instead of internal DN/RDN/RDNPart implementation

     [ https://issues.apache.org/jira/browse/DIRSTUDIO-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seelmann reassigned DIRSTUDIO-229:
-----------------------------------------

    Assignee: Stefan Seelmann

> Check if LdapDN/RDN or LdapName/Rdn could be used instead of internal DN/RDN/RDNPart implementation
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-229
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-229
>             Project: Directory Studio
>          Issue Type: Task
>          Components: studio-ldapbrowser
>    Affects Versions: 1.0.1
>            Reporter: Stefan Seelmann
>            Assignee: Stefan Seelmann
>
> The current browser implementation uses its own implementation of DN/RDN classes and parsers.  We should check if it is possible to use the shared-ldap or the JNDI implementation instead.

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