[dna-issues] [JBoss JIRA] Commented: (DNA-305) JcrNodeType.canSetProperty Does Not Enforce Constraints

[Randall Hauch (JIRA)]

    [ https://jira.jboss.org/jira/browse/DNA-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458002#action_12458002 ] 

Randall Hauch commented on DNA-305:
-----------------------------------

Could the namespace issue be addressed by just storing the fully-qualified (unprefixed) paths?  From JSR-170 1.0.1 Section 6.7.16:

    The constraint string returned must reflect the namespace mapping in the current Session (i.e., the 
    current state of the namespace registry overlaid with any session-specific mappings). Constraint strings for 
    PATH properties should be stored in fully-qualified form (using the actual URI instead of the prefix) and then be 
    converted to prefix form according to the current mapping. 


> JcrNodeType.canSetProperty Does Not Enforce Constraints
> -------------------------------------------------------
>
>                 Key: DNA-305
>                 URL: https://jira.jboss.org/jira/browse/DNA-305
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-305.patch, DNA-305_revised.patch
>
>
> JCRNodeType.canSetProperty does not currently perform any validations against the constraints for the property.  This does not meet the JCR 1.0 specification and will probably cause L2 tests to fail in the TCK.

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