[ http://issues.apache.org/jira/browse/DIREVE-228?page=all ]
Alex Karasulu resolved DIREVE-228:
----------------------------------
Fix Version: 0.9.2
Resolution: Fixed
Committed resolving fixes in revision 239536 here:
http://svn.apache.org/viewcvs.cgi?rev=239536&view=rev
> Schema container issue.
> -----------------------
>
> Key: DIREVE-228
> URL: http://issues.apache.org/jira/browse/DIREVE-228
> Project: Directory Server
> Type: Bug
> Components: schema
> Versions: 0.9.2
> Reporter: Kirill Kovalenko
> Assignee: Alex Karasulu
> Fix For: 0.9.2
> Attachments: patch_DIREVE-228.txt
>
> 1) It looks like that recently implemented [1],[2] RFC3673 support (all
> operational attributes) doesn't work for the schema entry. Attributes
> objectClasses, matchingRules, attributeTypes are not returned when '+'
> special attribute is used.
> 2) Schema container doesn't seem to provide modifyTimestamp attribute.
> Absence of modifyTimestamp attribute makes it impossible for client to track
> schema modifications easily.
> Here is what RFC2251 [3] says about it (section 3.2.2).
> Servers SHOULD provide the attributes createTimestamp and
> modifyTimestamp in subschema entries, in order to allow clients to
> maintain their caches of schema information.
> [1] http://issues.apache.org/jira/browse/DIREVE-210
> [2] http://issues.apache.org/jira/browse/DIREVE-219
> [3] http://rfc.net/rfc2251.html#s3.2.2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
