[
https://jira.jboss.org/jira/browse/DNA-304?page=com.atlassian.jira.plugin...
]
Randall Hauch resolved DNA-304.
-------------------------------
Fix Version/s: 0.4
Resolution: Done
Assignee: Randall Hauch
Marking as resolved, since this appears to have fixed the issue and since we now have a
test case for this condition.
SessionCache Uses Graph Layer Cardinality for Properties Instead of
Cardinality from JCR Property Definition
------------------------------------------------------------------------------------------------------------
Key: DNA-304
URL:
https://jira.jboss.org/jira/browse/DNA-304
Project: DNA
Issue Type: Bug
Components: JCR
Affects Versions: 0.4
Reporter: Brian Carothers
Assignee: Randall Hauch
Fix For: 0.4
Attachments: DNA-304.patch
At the graph layer, property cardinality (whether the property is single- or
multi-valued) is determined based on the values set on the property (i.e., any property
with only one value is single-valued, any property with more than one value is
multi-valued). At the JCR layer, property cardinality is supposed to be based on the
property definition in use for the property.
The SessionCache is currently basing the JCR layer cardinality on the graph layer
cardinality instead of the JCR property definition.
Example:
Consider a node that has one value for jcr:mixinTypes. At the graph layer, this property
will be single-valued. At the JCR layer, this property should be multi-valued based on
the jcr:mixinTypes property definition from the nt:base type (which is inherited by all
nodes).
--
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