Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 18646 invoked from network); 5 Oct 2005 16:41:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Oct 2005 16:41:10 -0000 Received: (qmail 24959 invoked by uid 500); 5 Oct 2005 16:41:09 -0000 Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-dev@incubator.apache.org Received: (qmail 24947 invoked by uid 99); 5 Oct 2005 16:41:08 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Oct 2005 09:41:08 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id B44E121C for ; Wed, 5 Oct 2005 18:40:47 +0200 (CEST) Message-ID: <2080368644.1128530447735.JavaMail.jira@ajax.apache.org> Date: Wed, 5 Oct 2005 18:40:47 +0200 (CEST) From: "Jukka Zitting (JIRA)" To: jackrabbit-dev@incubator.apache.org Subject: [jira] Created: (JCR-241) Remapping the default namespace Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Remapping the default namespace ------------------------------- Key: JCR-241 URL: http://issues.apache.org/jira/browse/JCR-241 Project: Jackrabbit Type: Wish Reporter: Jukka Zitting Priority: Minor Fix For: 1.0 I'm not sure if this is a bug, feature or standard behaviour, but currently it is not possible to remap the default namespace to some other prefix. The following code throws a NamespaceException: session.setNamespacePrefix("foo", ""); At least the Session.setNamespacePrefix() javadoc doesn't seem to prohibit changing the prefix of the default namespace and I couldn't find anything more specific in the JCR specification document. Restrictions are only placed on remapping the xml namespace. Note that the current nodetype code is actually relying on the default namespace being mapped to the empty prefix, so changing this would require small changes there as well. I haven't really run into any cases where I'd have needed such functionality, but it would be nice to clarify this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira