[
https://issues.apache.org/jira/browse/DIRSTUDIO-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Arnaud Marcelot resolved DIRSTUDIO-728.
----------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Assignee: Pierre-Arnaud Marcelot
This was fixed a few days ago.
It was due to a bug in schema parsing, see DIRSTUDIO-748 (Entry attribute name
not displayed correctly in Table Entry Editor)
> Wrong attribute name in entry editor
> ------------------------------------
>
> Key: DIRSTUDIO-728
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-728
> Project: Directory Studio
> Issue Type: Bug
> Affects Versions: 1.5.3
> Environment: Apache Directory Studio : Windows XP SP3
> LDAP Server : IBM Tivoli Directory Server 6.2 (Windows 2003 Enterprise)
> Reporter: Manu
> Assignee: Pierre-Arnaud Marcelot
> Fix For: 2.0.0
>
>
> An LDIF export of the entry is :
> dn: uid=test,ou=role,ou=domain
> objectClass: top
> objectClass: customrole
> uid: test
> version: 2.0
> datedebut: 20070420000000Z
> datefin: 20100131000000Z
> locked: false
> whereas the editor display is :
> objectclass : top
> objectclass : customrole
> uid : test
> version : 2.0
> version : 20070420000000Z
> version : 20100131000000Z
> version : false
> In this case the attribute name version is displayed instead of correct
> attribute names. The attribute type is also incorrect while editing, if
> datefin type was referral and version type was boolean you would have been
> forced to input a boolean instead of a referral.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
