Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 58392 invoked from network); 9 May 2007 07:59:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 May 2007 07:59:37 -0000 Received: (qmail 99767 invoked by uid 500); 9 May 2007 07:59:42 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 99740 invoked by uid 500); 9 May 2007 07:59:42 -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 99728 invoked by uid 99); 9 May 2007 07:59:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 May 2007 00:59:42 -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, 09 May 2007 00:59:35 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7106471403F for ; Wed, 9 May 2007 00:59:15 -0700 (PDT) Message-ID: <16580446.1178697555460.JavaMail.jira@brutus> Date: Wed, 9 May 2007 00:59:15 -0700 (PDT) From: "Marcel Reutegger (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-901) Support synonym searches In-Reply-To: <160292.1178641875983.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/JCR-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494454 ] Marcel Reutegger commented on JCR-901: -------------------------------------- In general I agree. The problem I had was that I didn't know how to supply a parameter to a parameter ;) and my intention was to make the wordnet synonym provider deployment as easy as possible. How about this: - add a new parameter: synonymProviderOptions - Extend the SynonymProvider interface with an init method that passes in the options string > Support synonym searches > ------------------------ > > Key: JCR-901 > URL: https://issues.apache.org/jira/browse/JCR-901 > Project: Jackrabbit > Issue Type: New Feature > Components: query > Reporter: Marcel Reutegger > Priority: Minor > Fix For: 1.4 > > > Jackrabbit should support synonym searches in the jcr:contains function like Google does. > Example: > //element(*, nt:resource)[jcr:contains(., '~food')] > -> finds all nt:resource nodes that contain the word food or synonyms for food. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.