Issue Details (XML | Word | Printable)

Key: DIRSERVER-784
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Ersin Er
Reporter: Ersin Er
Votes: 0
Watchers: 0
Operations

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

The server fails to handle subtree refinement membership references in entries upon object class changes

Created: 20/Nov/06 11:19 PM   Updated: 13/Feb/07 10:02 PM
Return to search
Component/s: core
Affects Version/s: 1.5.2, 1.5.1, 1.5.0, 1.0.1, 1.0, 1.0-RC4, 1.0-RC3, 1.0-RC2, 1.0-RC1, pre-1.0
Fix Version/s: 1.5.0, 1.0.1

Time Tracking:
Not Specified

Issue Links:
Incorporates
 

Resolution Date: 13/Feb/07 10:01 PM


 Description  « Hide
The test demostrating the problem:
http://svn.apache.org/viewvc/directory/trunks/apacheds/core-unit/src/test/java/org/apache/directory/server/core/subtree/SubentryServiceObjectClassChangeHandlingITest.java?view=markup&pathrev=477394

Solution:
SubentryService's modify routines should be updated so that they take action upon objectClass attribute value changes and recalculate subentry references.

PS: I have not added the test class to 1.0 branch. It should also be added there.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Alex Karasulu added a comment - 07/Feb/07 06:05 PM
Can you clarify this some more Ersin?

Thanks!

Ersin Er added a comment - 07/Feb/07 10:28 PM
Let me explain the case I had reflected in the test:

For the initial case we have an entry with object classes: top and person and there are no subtree specifications selecting this entry. Say, an existing subtree specification declares specificationFilter as item:organizationalPerson. Now, if we add a new object class to this entry like organizationalPerson, then this entry should be selected by the this subentry because it now applies to the specificationFilter criteria. Although this scenario is clear enough, it's not achieved in ApacheDS now. The problem is that SubentryService's modify routines do not handle such changes as I mentioned in the previous post.

Ersin Er made changes - 07/Feb/07 10:51 PM
Field Original Value New Value
Assignee Ersin Er [ ersiner ]
Ersin Er added a comment - 07/Feb/07 10:53 PM
OK, I will fix this issue tomorrow. No worries.

Ersin Er made changes - 09/Feb/07 06:30 AM
Link This issue is part of DIRSERVER-848 [ DIRSERVER-848 ]
Repository Revision Date User Message
ASF #507215 Tue Feb 13 20:58:19 UTC 2007 ersiner Fixed DIRSERVER-784 and DIRSERVER-848.
Files Changed
MODIFY /directory/apacheds/trunk/core/src/main/java/org/apache/directory/server/core/subtree/SubentryService.java

Repository Revision Date User Message
ASF #507218 Tue Feb 13 21:01:06 UTC 2007 ersiner Added test cases for DIRSERVER-784 and DIRSERVER-848 as they have been fixed.
Files Changed
MODIFY /directory/apacheds/trunk/core-unit/src/test/java/org/apache/directory/server/core/subtree/SubentryServiceObjectClassChangeHandlingITest.java
ADD /directory/apacheds/trunk/core-unit/src/test/java/org/apache/directory/server/core/subtree/SubentryServiceEntryModificationHandlingITest.java

Repository Revision Date User Message
ASF #507250 Tue Feb 13 21:55:39 UTC 2007 ersiner Fixed DIRSERVER-784.
Ported the fix from 1.5 fix and had serious pbs. But all are OK now.
Also added test cases for the fix.
Files Changed
MODIFY /directory/apacheds/branches/1.0/core/src/main/java/org/apache/directory/server/core/subtree/SubentryService.java
ADD /directory/apacheds/branches/1.0/core-unit/src/test/java/org/apache/directory/server/core/subtree/SubentryServiceObjectClassChangeHandlingITest.java


Ersin Er made changes - 13/Feb/07 10:01 PM
Resolution Fixed [ 1 ]
Status Open [ 1 ] Resolved [ 5 ]
Ersin Er added a comment - 13/Feb/07 10:02 PM
Fixed.

Ersin Er made changes - 13/Feb/07 10:02 PM
Status Resolved [ 5 ] Closed [ 6 ]