[
https://jira.jboss.org/jira/browse/DNA-286?page=com.atlassian.jira.plugin...
]
Randall Hauch resolved DNA-286.
-------------------------------
Resolution: Done
This change provides a new implementation of the NamespaceRegistry interface of the JCR
API, along with refactoring the implementations of DNA's NamespaceRegistry. In
particular, a new GraphNamespaceRegistry class was added that stores the namespace
mappings in the graph content (under a location provided into the constructor). This
allowed the new JcrNamespaceRegistry to simply delegate to that and do the simple mapping
from DNA's interface to JCR's. (The refactoring also changed a number of test
cases that were directly instantiating a namespace registry.)
The other major change to the JCR implementation is the proper implementation of a
session-specific (non-shared and non-persistent) namespace registry, on top of the shared
(in a content-sense, not shared objects) and persistent registry that is in the
JcrWorkspace. This required changing how the JcrSession and JcrWorkspace objects are
created. The result is that now namespace mappings can be set on the session, and these
override those in the workspace (that would be used for all sessions that use that
repository's workspace).
Implement namespace management
------------------------------
Key: DNA-286
URL:
https://jira.jboss.org/jira/browse/DNA-286
Project: DNA
Issue Type: Sub-task
Components: API, JCR
Affects Versions: 0.3
Reporter: Randall Hauch
Assignee: Randall Hauch
Fix For: 0.4
Our JCR implementation needs a namespace registry that stores the namespaces and their
prefixes in such a way that they can be clustered. The best approach is probably to store
the namespaces under "/jcr:system/" in a DNA-specific location (as the JCR spec
does not specify that the namespaces are available as content. By doing this, the
namespace registry would automatically work across a cluster (any clients that are using
the same RepositorySource).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira