[dna-issues] [JBoss JIRA] Updated: (DNA-357) Hide dna:nodeDefinition Property from Users

[Brian Carothers (JIRA)]

     [ https://jira.jboss.org/jira/browse/DNA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-357:
--------------------------------

    Attachment: DNA-357.patch


Patch that never returns dna:nodeDefinition property from session cache.  It does not do anything to prevent users from trying to set it though, which seems wrong.

> Hide dna:nodeDefinition Property from Users
> -------------------------------------------
>
>                 Key: DNA-357
>                 URL: https://jira.jboss.org/jira/browse/DNA-357
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-357.patch
>
>
> dna:nodeDefinition is a bit of an odd duck.  It is set on every property but doesn't always have a valid JCR definition.  This breaks an export-import round trip as the property cannot be set during import.  It also breaks a few TCK tests that assume a jcr:xmltext node only has two properties (jcr:primaryType and jcr:xmlcharacters), but that's really a TCK defect.
> Can we just suppress this property at the JCR layer?  It would still be available for internal use but would not appear to end users.  Alternatively, we should modify our definition for nt:base to include it as a protected property - this solution may violate the spec.

-- 
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