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/01/23 20:32:49 UTC
[jira] Updated: (DIRSERVER-835) Trying to modify operational
attributes does not cause appropriate errors
[ https://issues.apache.org/jira/browse/DIRSERVER-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Zoerner updated DIRSERVER-835:
-------------------------------------
Attachment: ModifyOperationalAttributeTest.java
Here is the JUnit test mentioned in the description of the issue.
> Trying to modify operational attributes does not cause appropriate errors
> -------------------------------------------------------------------------
>
> Key: DIRSERVER-835
> URL: https://issues.apache.org/jira/browse/DIRSERVER-835
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.0.1
> Environment: * ApacheDS 1.0.1 (SNAPSHOT)
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
> Reporter: Stefan Zoerner
> Attachments: ModifyOperationalAttributeTest.java
>
>
> Trying to modify operational attributes of entries (modifiersName, creatorsName) does not cause approriate errors. FInd attached a JUnit test which performs three modify operations (adding/deleting/reoplacing an operational attribute) with the help of JNDI. All of them do not throw an exception.
> I have checked the test with three other LDAP servers. OpenLDAP and Sun Java System Directory Server return an LDAP code 19 (LDAP_CONSTRAINT_VIOLATION), IBM Tivoli Directory Server returns 50 (LDAP_INSUFFICIENT_ACCESS).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.