[JBoss JIRA] Created: (DNA-101) potential user confusion between org.jboss.dna.spi.graph ValueFactory and ValueFormatException interfaces and similar javax.jcr interfaces
by Greg Haber (JIRA)
potential user confusion between org.jboss.dna.spi.graph ValueFactory and ValueFormatException interfaces and similar javax.jcr interfaces
------------------------------------------------------------------------------------------------------------------------------------------
Key: DNA-101
URL: http://jira.jboss.com/jira/browse/DNA-101
Project: DNA
Issue Type: Feature Request
Components: API
Affects Versions: 0.2
Reporter: Greg Haber
Priority: Trivial
The new org.jboss.dna.spi.graph.ValueFactory and package org.jboss.dna.spi.graph.ValueFormatException interfaces may be potentially confusing to users that are using both DNA and the underlying JCR APIs in the same code. This is because there are interfaces with exactly the same names, and with very similar purposes (the JCR interfaces deal with instances of the javax.jcr.Value class, where the DNA interfaces are for standard Java objects), in the javax.jcr package. We should think about changing the names of the DNA interfaces to avoid such potential confusion. This is a very minor issue, I would not object if we decided to leave the interface names unchanged.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (DNA-262) JCR-Level 2: Support persistent namespace changes
by Randall Hauch (JIRA)
JCR-Level 2: Support persistent namespace changes
-------------------------------------------------
Key: DNA-262
URL: https://jira.jboss.org/jira/browse/DNA-262
Project: DNA
Issue Type: Feature Request
Affects Versions: 0.3
Reporter: Randall Hauch
Assignee: Randall Hauch
Fix For: 0.4
JCR Level 2 requires support for persisting changes to namespaces in the repository. We can already support that with all of our connectors, since they're all able to store the namespace URIs for the content. In fact, none of them currently store or use the prefixes.
However, one thing DNA still doesn't have is the ability to manage the namespace prefixes in the connectors. This probably will entail having a NamespaceRegistry implementation that can use a connector to populate the namespace registry. This is a little tricky, tho, since the NamespaceRegistry is part of the ExecutionContext, which is passed to the connector's "execute(ExecutionContext,Request)" method. So, while it is ideal that these namespace management methods are just additional requests, the dependency graph may imply that the namespace management methods need to be added to the RepositoryConnector interface.
--
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
15 years