Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 24656 invoked from network); 3 Oct 2007 07:32:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Oct 2007 07:32:11 -0000 Received: (qmail 64471 invoked by uid 500); 3 Oct 2007 07:32:01 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 64267 invoked by uid 500); 3 Oct 2007 07:32:00 -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 64256 invoked by uid 99); 3 Oct 2007 07:32:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2007 00:32:00 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2007 07:32:10 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 90E3171418F for ; Wed, 3 Oct 2007 00:31:50 -0700 (PDT) Message-ID: <31201913.1191396710590.JavaMail.jira@brutus> Date: Wed, 3 Oct 2007 00:31:50 -0700 (PDT) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIRSERVER-1080) LDAP modify operation does not create or update necessary operational attributes within an entry In-Reply-To: <18821687.1191355370709.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DIRSERVER-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532022 ] Emmanuel Lecharny commented on DIRSERVER-1080: ---------------------------------------------- I _do_ have a fix for this issue (and even two fixes :), but it leads to complex impact on the schema interceptor. If possible, we should consider inverting the operationalAttribute and schema interceptors in the chain. FYI, there are other place in the code where the op attributes are steup _after_ the schema interceptor, but I consider this as a hack. Let's discuss this issue ... Regarding Stefan comment : yes, we will fix it. > LDAP modify operation does not create or update necessary operational attributes within an entry > ------------------------------------------------------------------------------------------------ > > Key: DIRSERVER-1080 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1080 > Project: Directory ApacheDS > Issue Type: Bug > Components: ldap > Affects Versions: 1.5.1 > Environment: * ApacheDS 1.5.1 > * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) > * Windows XP Professional SP2 > Reporter: Stefan Zoerner > Assignee: Alex Karasulu > > If an existing entry is modified (e.g. additional attribute addition), and the operational attributes "modifiersName" and "modifyTimestamp" are not present, they are not present afterwards as well. > I have extended the existing test case org.apache.directory.server.core.operational.OperationalAttributeServiceITest in order to demonstrate this and to depict the desired behavior (svn commit follows). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.