[ http://issues.apache.org/jira/browse/JCR-241?page=comments#action_12331585 ]
Jukka Zitting commented on JCR-241: ----------------------------------- Actually I think that the use case of mapping the empty prefix to some normal namespace is much more interesting than assigning a prefix to the empty namespace. However you cannot do the former without the latter (first remap the empty namespace, then map another namespace to the now free empty prefix), thus the wording of the issue. > 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
