Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 4407 invoked from network); 7 Nov 2006 14:43:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Nov 2006 14:43:17 -0000 Received: (qmail 36315 invoked by uid 500); 7 Nov 2006 14:43:27 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 36291 invoked by uid 500); 7 Nov 2006 14:43:27 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 36282 invoked by uid 99); 7 Nov 2006 14:43:27 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Nov 2006 06:43:27 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= 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; Tue, 07 Nov 2006 06:43:14 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9D506714315 for ; Tue, 7 Nov 2006 06:42:54 -0800 (PST) Message-ID: <17310822.1162910574641.JavaMail.jira@brutus> Date: Tue, 7 Nov 2006 06:42:54 -0800 (PST) From: =?utf-8?Q?C=C3=A9dric_Damioli_=28JIRA=29?= To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-202) Add configuration options for search manager MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/JCR-202?page=3Dcomments#action_1= 2447809 ]=20 =20 C=C3=A9dric Damioli commented on JCR-202: ------------------------------------ May the above rule-based suggestion be only a default implementation of the= SearchConfiguration ? IMHO with these simple XML rules, you can't cover all possibilities. What about ?=20 Where the class is an implementation simply answering to=20 boolean include (Node node); boolean exclude (Node node); Your proposed rule-based implementation may become the standard, default on= e, while enabling more advanced needs to be also implemented. Thoughts ? > Add configuration options for search manager > -------------------------------------------- > > Key: JCR-202 > URL: http://issues.apache.org/jira/browse/JCR-202 > Project: Jackrabbit > Issue Type: New Feature > Components: config > Affects Versions: 0.9, 1.0, 1.0.1 > Environment: all > Reporter: Michael Aemisegger > > Right now, if the search manager is active, everything is indexed, even t= he system branch of a workspace with the versions. > take parameters / conditions into account whether a node should be indexe= d: > - path > - node type > - property type > - property name > see also http://thread.gmane.org/gmane.comp.apache.jackrabbit.devel/3343 --=20 This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: htt= p://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira