jackrabbit-dev mailing list archives

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

I think that instead of (or before) auto-generating a prefix for an unknown namespace the
jcr2spi should ask the backend for a prefix update.

Here's a few different ways I can imagine we could achieve this, arranged by network-efficiency:

1) Allow the SPI to return the prefix as an optional part of a QName when using a namespace
that the client has not yet seen
2) Make the client call RepositoryService.getRegisteredNamespaces(SessionInfo) with an added
namespace argument so the backend can decide whether to return the entire registry or just
a subset update containing the requested prefix
3) Add a RepositoryService.getNamespacePrefix(SessionInto, String) method for the client to
explicitly request the missing prefix
4) Make the client call RepositoryService.getRegisteredNamespaces(SessionInfo) to refresh
the local copy of the registry

> 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