Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 13478 invoked from network); 18 Aug 2007 05:08:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Aug 2007 05:08:53 -0000 Received: (qmail 90264 invoked by uid 500); 18 Aug 2007 05:08:50 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 90206 invoked by uid 500); 18 Aug 2007 05:08:50 -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 90032 invoked by uid 99); 18 Aug 2007 05:08:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Aug 2007 22:08:49 -0700 X-ASF-Spam-Status: No, hits=-98.8 required=10.0 tests=ALL_TRUSTED,DNS_FROM_DOB,RCVD_IN_DOB 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; Sat, 18 Aug 2007 05:08:51 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4A15E714159 for ; Fri, 17 Aug 2007 22:08:31 -0700 (PDT) Message-ID: <19329894.1187413711301.JavaMail.jira@brutus> Date: Fri, 17 Aug 2007 22:08:31 -0700 (PDT) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIRSERVER-922) Data is "lost" after adding Index to config file In-Reply-To: <28503792.1178709435406.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-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520821 ] Emmanuel Lecharny commented on DIRSERVER-922: --------------------------------------------- Just some comments about your comments... This is what I don't like about patterns : they fake to make thing easier by masking real code with 'funky names'. At the end, it's always the same story : double work : - first you have to understand what is the real problem - second you have to understand the pattern ok, now for this command pattern this is really just a separation between client and server code, with a proxy in the middle. It is usefull when you don't want to deal with the underlying protocol. If you want to add a new command, or to modify an existing one, you just have to focus on the client and server code. I think pam has added some sample documentation on cwiki (remember than when you are using another pattern, you _also_ have to search the web or the GoF for a clear view of the way the pattern is used, so nothing new under the sun, and self-documented pattern is just a dream ...) > Data is "lost" after adding Index to config file > ------------------------------------------------ > > Key: DIRSERVER-922 > URL: https://issues.apache.org/jira/browse/DIRSERVER-922 > Project: Directory ApacheDS > Issue Type: Bug > Affects Versions: 1.5.0 > Environment: amd64 > 128M RAM > 768 Swap > prebuilt i386 apacheds-1.5.0 > Reporter: Martin Marcher > Assignee: Pierre-Arnaud Marcelot > Fix For: 1.5.1 > > > Install Server > add sevenseas Partition without any indexes (no property tag for indexes here at all) > start server > connect with LDAPStudio 0.8 (do not disconnect!) > Load o=sevenSeas SampleData > open server.xml Config file > copy indexes from examplePartition to sevenSeasPartition > don't yet save the file > stop the server > save server.xml > start the server gain > LDAPStudio will not show any data under o=sevenSeas. (Note: Do not close the connection and reconnect) > When Trying to add the data again you will find that it is still there > as importing again throws errors. > This is is also the case when closing connection and reopening the connection > as well as quitting ldapstudio and restarting it > reloading "this entry and all it's children" didn't help > reloading schema didn't help either. > greets > martin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.