[
https://jira.jboss.org/jira/browse/DNA-286?page=com.atlassian.jira.plugin...
]
Randall Hauch resolved DNA-286.
-------------------------------
Resolution: Done
This change corrects the behavior of the Session's namespace-related methods, which
are not the same as those in the NamespaceRegistry implementation associated with the
workspace. This also corrected several of the TCK tests associated with namespaces.
Note that the StringValueFactory in 'dna-graph' was changed to use a DNA namespace
registry to convert a Name and Path to a string using the namespace prefixes. (This
change affected a number of unit tests.) The result is that any Name and Path property
values are treated correctly and properly converted to a string using the current
namespace prefixes in the namespace registry. However, the BinaryValueFactory
implementations should not use this StringValueFactory, since they need to convert values
using the non-prefixed form (that is, the namespace URI).
In the case of our JCR implementation, the above change to the Graph factories means that
property values are properly mapped to strings using the Session's local mappings
(which fall back on the Workspace's mappings). This corrected at least one TCK test.
I believe this addresses all the concerns documented above. Therefore, marking as
resolved. But as always, if this is not true, please reopen.
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
Attachments: DNA-286.patch
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