[
https://issues.apache.org/jira/browse/JCR-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-616.
------------------------
Resolution: Fixed
based on jukkas comment i resolve this issue fixed. i will add a note to the
Limitations.txt explaining the
known issue.
> Completeness/Freshness of NamespaceRegistry and NodeTypeRegistry
> ----------------------------------------------------------------
>
> Key: JCR-616
> URL: https://issues.apache.org/jira/browse/JCR-616
> Project: Jackrabbit
> Issue Type: Bug
> Components: SPI
> Reporter: Julian Reschke
> Assignee: angela
> Attachments: diffs.txt
>
>
> 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 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.
-
You can reply to this email to add a comment to the issue online.
