Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 25581 invoked from network); 26 Feb 2009 09:48:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Feb 2009 09:48:20 -0000 Received: (qmail 44047 invoked by uid 500); 26 Feb 2009 09:48:18 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 44027 invoked by uid 500); 26 Feb 2009 09:48:18 -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 44016 invoked by uid 99); 26 Feb 2009 09:48:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2009 01:48:18 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2009 09:48:11 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LccqM-0007nA-FV for users@jackrabbit.apache.org; Thu, 26 Feb 2009 01:47:50 -0800 Message-ID: <22220831.post@talk.nabble.com> Date: Thu, 26 Feb 2009 01:47:50 -0800 (PST) From: PThiemann To: users@jackrabbit.apache.org Subject: Slashes in wildcard query string do not work MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: philipp.thiemann@googlemail.com X-Virus-Checked: Checked by ClamAV on apache.org Hello, I am using Jackrabbit 1.4.2 in an Oracle and RedHat Linux environment. I have a strange problem in searching for a term with a slash in the query string ending with a wildcard (e.g. F/OS*) I have a node property XYZ with value F/OSAM which I am trying to search for using a XPATH query. When searching for the following I do get a correct result: //element(*, custom:file)[jcr:contains(custom:extendedProperties/@XYZ,'F/OSAM')]/custom:extendedProperties/rep:excerpt(.) When searching for the next query string I do not get a result. Although using wildcards in my query: //element(*, custom:file)[jcr:contains(custom:extendedProperties/@XYZ,'F/OS*')]/custom:extendedProperties/rep:excerpt(.) Now there is the strange thing. When I search (leaving out the /) for the following I can see my result again. //element(*, custom:file)[jcr:contains(custom:extendedProperties/@XYZ,'F OS*')]/custom:extendedProperties/rep:excerpt(.) Is the slash not indexed by lucene or do I have to escape the slash for Jackrabbit for not being recognized as path delimiter? For any suggestions I would be glad. Thanks, Philipp -- View this message in context: http://www.nabble.com/Slashes-in-wildcard-query-string-do-not-work-tp22220831p22220831.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.