directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRSTUDIO-152) New entry creator does not know that 'dc' and 'domainComponent' is the same thing
Date Mon, 24 Sep 2007 14:27:50 GMT


Emmanuel Lecharny commented on DIRSTUDIO-152:

This is obviously because unit testing a GUI is not an easy task that this kind of regression
wasn't detected before 0.8 !

Any person having a good idea about how to write regression tests for this GUI is welcome

> New entry creator does not know that 'dc' and 'domainComponent' is the same thing
> ---------------------------------------------------------------------------------
>                 Key: DIRSTUDIO-152
>                 URL:
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-ldapbrowser
>    Affects Versions: 0.8.0
>         Environment: Apache Directory Studio 0.8.0 stand-alone plugin with eclipse RCP
3.2.0 operating on OpenLDAP 2.3 server
>            Reporter: Mateusz Kijowski
> I want to create an entry with domain objectClass. The only MUST attribute required by
this objectClass is the domainComponent or dc. The schema definition allows use of both these
names, but the entry creator tries to be smarter. When I specify the DN as dc=subdomain,dc=example,dc=com
in the third step of creating a new entry and go to the last step, the entry editor lists
the dc attribute in normal font and makes me enter the domainComponent which is listed in
bold font.
> So I end up with both dc and domainComponent attributes to make the "Finish" button active.
Because the dc attribute is the part of the dn I cannot delete it, because the entry creator
thinks that I still have to enter the domainComponent attribute I cannot delete it neither.
When I finish creating the entry the server responds with a "Error while creating entry  [LDAP:
error code 20 - attribute 'dc' provided more than once] " error.

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

View raw message