Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <1916545242.1124895251521.JavaMail.jira@ajax.apache.org>
Date: Wed, 24 Aug 2005 16:54:11 +0200 (CEST)
From: "Kirill Kovalenko (JIRA)" <directory-dev@incubator.apache.org>
To: dev@directory.apache.org
Subject: [jira] Commented: (DIREVE-228) Schema container issue.
In-Reply-To: <329984547.1124444154176.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DIREVE-228?page=comments#action_12319847 ] 

Kirill Kovalenko commented on DIREVE-228:
-----------------------------------------

Alex, Stefan, 

I want to draw your attention to the fact that this issue has "Resolved" status now, but only case #1 is actually fixed. As I understand Stefan tracks case #2 is fix personal TODO, but probably a new, separate issue should be opened for #2 for further tracking.

> 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