Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 35270 invoked from network); 24 Aug 2005 16:33:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Aug 2005 16:33:17 -0000 Received: (qmail 37818 invoked by uid 500); 24 Aug 2005 16:33:17 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 37759 invoked by uid 500); 24 Aug 2005 16:33:16 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 37746 invoked by uid 99); 24 Aug 2005 16:33:16 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Aug 2005 09:33:14 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id EB70A125 for ; Wed, 24 Aug 2005 18:33:12 +0200 (CEST) Message-ID: <2107542095.1124901192951.JavaMail.jira@ajax.apache.org> Date: Wed, 24 Aug 2005 18:33:12 +0200 (CEST) From: "Alex Karasulu (JIRA)" 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 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DIREVE-228?page=comments#action_12319873 ] Alex Karasulu commented on DIREVE-228: -------------------------------------- Kirill you are absolutely right that issue #2 should have been another JIRA but I have fixed this already. Take a look at the latest snapshots for 0.9.2 and check for the operational attributes: createTimestamp, modifyTimestamp, creatorsName, modifiersName. > 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