Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 69223 invoked from network); 26 Feb 2009 20:48:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Feb 2009 20:48:09 -0000 Received: (qmail 52550 invoked by uid 500); 26 Feb 2009 20:48:08 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 52532 invoked by uid 500); 26 Feb 2009 20:48:08 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 52515 invoked by uid 99); 26 Feb 2009 20:48:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2009 12:48:08 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aklimets@day.com designates 207.126.148.183 as permitted sender) Received: from [207.126.148.183] (HELO eu3sys201aog003.obsmtp.com) (207.126.148.183) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 26 Feb 2009 20:47:59 +0000 Received: from source ([209.85.219.172]) by eu3sys201aob003.postini.com ([207.126.154.11]) with SMTP ID DSNKSab/6bF4iPDaJUnEvroOcQQTHOZE7xwr@postini.com; Thu, 26 Feb 2009 20:47:39 UTC Received: by ewy20 with SMTP id 20so955978ewy.26 for ; Thu, 26 Feb 2009 12:47:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.210.133.19 with SMTP id g19mr13202ebd.66.1235681257441; Thu, 26 Feb 2009 12:47:37 -0800 (PST) In-Reply-To: <22231363.post@talk.nabble.com> References: <22220831.post@talk.nabble.com> <22231363.post@talk.nabble.com> Date: Thu, 26 Feb 2009 21:47:37 +0100 Message-ID: Subject: Re: Slashes in wildcard query string do not work From: Alexander Klimetschek To: users@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Feb 26, 2009 at 8:11 PM, PThiemann wrote: > But now I am facing another problem. The excerpt is not highlighted anymore. > I am just getting a excerpt string of all property values of node > 'custom:extendedProperties' without any highlighing. > As our customer are currently used to query result highlighting this would > be a real disadvantage. > > Does anyone know if query highlighing is supported with jcr:like? Yes, I think this is the case. It seems the default excerpt highlighting is not able to handle wildcards. Maybe one can implement that in a custom ExcerptProvider (see [1]), but since it uses the Lucene index (org/apache/jackrabbit/core/query/lucene/DefaultHighlighter.java), I think this could be quite some effort. BTW, the query could be simplified a bit by extracting the custom:extendedProperties axis: //element(*,custom:file)/custom:extendedProperties[jcr:like(@XYZ,'F/OS%')]/rep:excerpt(.) [1] http://wiki.apache.org/jackrabbit/ExcerptProvider Regards, Alex -- Alexander Klimetschek alexander.klimetschek@day.com