[dna-issues] [JBoss JIRA] Resolved: (DNA-356) Need to Throw ItemExistsException if addNode Call Fails Due to SNS
Randall Hauch (JIRA)
jira-events at lists.jboss.org
Thu Apr 16 10:00:22 EDT 2009
[ https://jira.jboss.org/jira/browse/DNA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randall Hauch resolved DNA-356.
-------------------------------
Fix Version/s: 0.4
Resolution: Done
Assignee: Randall Hauch
Applied the patch that changes SessionCache.NodeEditor.addNode(...) to throw an ItemExistsException if the node cannot be added because an item at the specified path already exists and same-name siblings are not allowed, per the specification (see the JIRA issue for the details). An additional lookup of the child node definition is performed, but this isn't a problem since it is already an error case and the extra work is justified to provide more useful information in the exception.
> Need to Throw ItemExistsException if addNode Call Fails Due to SNS
> ------------------------------------------------------------------
>
> Key: DNA-356
> URL: https://jira.jboss.org/jira/browse/DNA-356
> Project: DNA
> Issue Type: Bug
> Components: JCR
> Affects Versions: 0.3
> Reporter: Brian Carothers
> Assignee: Randall Hauch
> Priority: Minor
> Fix For: 0.4
>
> Attachments: DNA-356.patch
>
>
> According to the section 7.1.4 of the 1.0.1 specification (in the documentation for Node.addNode:)
> "An ItemExistsException will be thrown either immediately (by this method), or on save, if an item at the specified path already exists and same-name siblings are not allowed."
> DNA treats this as a generic case where no valid definition exists and throw a ConstraintViolationException.
--
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
More information about the dna-issues
mailing list