[
https://jira.jboss.org/jira/browse/DNA-341?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-341:
-----------------------------------
The patch also removes the RemovedPropertiesRequest, since it didn't offer any benefit
over UpdatePropertiesRequest (and since it is simpler to only have one). All connectors
were updated to reflect these semantics.
Graph API behavior when removing all property values doesn't
reflect that of JCR
--------------------------------------------------------------------------------
Key: DNA-341
URL:
https://jira.jboss.org/jira/browse/DNA-341
Project: DNA
Issue Type: Bug
Components: API, Graph, JCR
Affects Versions: 0.3
Reporter: Randall Hauch
Assignee: Randall Hauch
Priority: Critical
Fix For: 0.4
Attachments: DNA-341.patch
Section 4.7.3 of the JSR-170 specification (version 1.0.1) states:
Every property must have a value. The range of property states does not include
having a "null value", or "no value". Setting a
property to "null" is equivalent to removing that property. In the case of
multi-value properties, the setting of a particular value
within the array to null results in the removal of that value and the compacting of
the array. As a result it is possible to have a multi-
value property with no values (an empty array). See 7.1.5 Adding and Writing
Properties.
However, currently the Graph API and connector behavior is such that whenever a property
is updated (or set) to no values, the property is removed automatically. This means that
it is not possible for the Graph API or connectors to support a multi-valued JCR property
with no values.
--
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