directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DIRSERVER-343) Schema container issue.
Date Sat, 21 Apr 2007 11:18:15 GMT

     [ https://issues.apache.org/jira/browse/DIRSERVER-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Emmanuel Lecharny closed DIRSERVER-343.
---------------------------------------


Closing all issues created in 2005 and before which are marked resolved

> Schema container issue.
> -----------------------
>
>                 Key: DIRSERVER-343
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-343
>             Project: Directory ApacheDS
>          Issue Type: Bug
>            Reporter: Kirill Kovalenko
>         Assigned To: Alex Karasulu
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message