From dev-return-9412-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org Fri Nov 03 09:20:40 2006 Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 35004 invoked from network); 3 Nov 2006 09:20:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Nov 2006 09:20:39 -0000 Received: (qmail 58645 invoked by uid 500); 3 Nov 2006 09:20:49 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 58614 invoked by uid 500); 3 Nov 2006 09:20:49 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 58605 invoked by uid 99); 3 Nov 2006 09:20:49 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Nov 2006 01:20:49 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Nov 2006 01:20:37 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8D5157142F0 for ; Fri, 3 Nov 2006 01:20:16 -0800 (PST) Message-ID: <19470798.1162545616576.JavaMail.root@brutus> Date: Fri, 3 Nov 2006 01:20:16 -0800 (PST) From: "Julian Reschke (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Created: (JCR-616) Completeness/Freshness of Namespace Registry MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Completeness/Freshness of Namespace Registry -------------------------------------------- Key: JCR-616 URL: http://issues.apache.org/jira/browse/JCR-616 Project: Jackrabbit Issue Type: Bug Components: SPI Reporter: Julian Reschke We need to define the requirements on completeness and freshness of RepositoryConfig.getRegisteredNamespaces(). Right now the optimistic assumption seems to be that an SPI provider is able to report all namespaces that can occur in a repository beforehand. Even if it can do that (and I know of potential targets for SPI that simply can't), this seems to be quite a waste of time if these namespace prefixes aren't actually used later on. Furthermore, in SPI namespace prefixes aren't really relevant, except to enable the transient layer to return "meaningful" prefixes instead of automatically generated ones. Therefore my propoal would be to: 1) Clarify that the Map returned from getRegisteredNamespaces() isn't required to be complete, 2) Enhance JCR2SPI to auto-generate prefixes when it encounters namespaces not in the registry. I expect this to also affect RepositoryService.(un)registerNamespace(...), but let's discuss the underlying issue first... -- 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