[
http://jira.jboss.com/jira/browse/DNA-101?page=comments#action_12415441 ]
Johnny Verhaeg commented on DNA-101:
------------------------------------
My understanding is the "confusion" was intentional, the idea being developers
already familiar with the JCR API would more quickly be able to grasp the intention of
classes in the DNA SPI that are similar in function to those in the JCR. It seems like as
long we we're comfortable that the Graph part of the SPI will always sit between
classes/applications using the JCR and custom DNA artifacts, this practice is more of an
aid than a hindrance.
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