|
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
Ersin Er made changes - 09/Feb/07 06:30 AM
Fixed for 1.5 here:
http://svn.apache.org/viewvc?view=rev&rev=507215 http://svn.apache.org/viewvc?view=rev&rev=507218 Fixed for 1.0 here: http://svn.apache.org/viewvc?view=rev&rev=507250
Ersin Er made changes - 13/Feb/07 10:01 PM
Ersin Er made changes - 13/Feb/07 10:02 PM
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Thanks!