jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry
Date Fri, 03 Nov 2006 10:17:17 GMT
    [ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12446896 ] 
Marcel Reutegger commented on JCR-616:

Namespace prefixes cannot be just generated, because there is a notion of a repository wide
namespace registry with a somewhat stable mapping between namespace URI and prefix. Initially
a JCR session has to use that mapping unless the client decides to re-map the namespace locally
in its session.

> 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 RepositoryService.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
> 2) Enhance JCR2SPI to auto-generate prefixes when it encounters namespaces not in the
> 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


View raw message