Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 56444 invoked from network); 2 Mar 2009 16:59:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Mar 2009 16:59:57 -0000 Received: (qmail 17112 invoked by uid 500); 2 Mar 2009 16:59:56 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 17099 invoked by uid 500); 2 Mar 2009 16:59:56 -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 17082 invoked by uid 99); 2 Mar 2009 16:59:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Mar 2009 08:59:55 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of julian.reschke@gmx.de designates 213.165.64.20 as permitted sender) Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 02 Mar 2009 16:59:48 +0000 Received: (qmail invoked by alias); 02 Mar 2009 16:59:25 -0000 Received: from mail.greenbytes.de (EHLO [192.168.1.106]) [217.91.35.233] by mail.gmx.net (mp069) with SMTP; 02 Mar 2009 17:59:25 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX1/0KiFJ8ND0nozI/xw5VK5pMEaK67KqxofmMNSolU /tMk0OVtqLeYOk Message-ID: <49AC106A.5050601@gmx.de> Date: Mon, 02 Mar 2009 17:59:22 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666 MIME-Version: 1.0 To: users@jackrabbit.apache.org Subject: Re: AW: Problem with ISO9075 encoded name in XPath Query? References: <508F74BC296D494E9A4A983C854E1EA70501A9DABF@d-ex-01.vva.local> <508F74BC296D494E9A4A983C854E1EA70501A9DB03@d-ex-01.vva.local> In-Reply-To: <508F74BC296D494E9A4A983C854E1EA70501A9DB03@d-ex-01.vva.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.67 X-Virus-Checked: Checked by ClamAV on apache.org Mario-Leander Reimer wrote: > Hi Dave, > > I encode the name because and did not want to restrict the user in any way regarding allowed characters for the "name" of an entity (which I use as node name) I store in JCR. > Otherwise I would have to manage 2 names, the "artificial" valid JCR node name and the "real name" for the entity the user initially entered, and keep both in-synch. > Same for nt:files a user can upload: a filename can start with a letter, the node name can't. So either strip the invalid characters and lose the original filename, or encode it somehow. The node name can, I think. > So I figured it's best to always encode every name, not matter what. Well, now I additionally have to encode the XPath query. This may be a bad idea, depending on the use case; for instance, when you allow WebDAV access to the store, people will only see the encoded names... BR, Julian