Issue Details (XML | Word | Printable)

Key: DIRSERVER-316
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Alex Karasulu
Reporter: Stefan Zoerner
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Directory ApacheDS

Deletion of RDN and objectClass attribute

Created: 22/Aug/05 08:59 PM   Updated: 10/Feb/06 12:34 PM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments:
  Size
Java Source File ObjectClassesRemovalTest.java 2005-08-22 09:09 PM Stefan Zoerner 2 kB
Issue Links:
Reference
 

Resolution Date: 24/Aug/05 10:23 AM


 Description  « Hide
It is possible to remove the RDN and the objectClass attribute from an entry via a modify operation. Removing the objectClass attribute leads to an entry which can't be deleted.

Attached you find a testcase which demonstrates the deletion of the objectClass on a person entry.
After this operation, it is still possible to lookup the entry with its DN, although it has no attributes and deletion attempts cause an error:
LDAP: error code 54 - failed to delete entry cn=Charly Brown,dc=apache,dc=org

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Repository Revision Date User Message
ASF #239501 Wed Aug 24 01:21:51 UTC 2005 akarasulu changes ...

 o added some schema checking for 2251 compliance to the SchemaService which
   is an interceptor responsible for schema checks
 o added satelite class for actually doing the checks called SchemaChecker
   which I suspect can be split into several other classes for the specific
   nature of the schema checks it performs
 o added test case to unit test the operation of functions in the SchemaChecker
 o added log4j configuration for testing only which is not packaged into the
   core jar

todos ...

 o this stuff needs serious refactoring because of crazy amounts of code
   duplication - it was easier (quick and dirty) to get the code working
   as separate functions for now

This commit resolves the following issue, DIREVE-230, filed by Stefan:

http://issues.apache.org/jira/browse/DIREVE-230
Files Changed
MODIFY /directory/apacheds/trunk/core/src/main/java/org/apache/ldap/server/schema/SchemaService.java
ADD /directory/apacheds/trunk/core/src/main/java/org/apache/ldap/server/schema/SchemaChecker.java
ADD /directory/apacheds/trunk/core/src/test/resources
ADD /directory/apacheds/trunk/core/src/test/org/apache/ldap/server/schema/SchemaCheckerTest.java
ADD /directory/apacheds/trunk/core/src/test/resources/log4j.properties