[
https://issues.apache.org/jira/browse/JCR-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2172.
-------------------------
Resolution: Invalid
hm reread the specification that states:
"
Protected
If an item I is declared protected it is repository-controlled.
If I is a node then, through the core write methods of JCR,
- I cannot be removed,
- child nodes of I cannot be added, removed, or reordered,
- properties of I cannot be added or removed,
- the values of existing properties of I cannot be changed,
- the primary node type of I cannot be changed and
- mixin node types cannot be added to or removed from I.
If I is a property then, through the core write methods of JCR,
- I cannot be removed and
- the value of I cannot be changed
"
adding protected nodes is consequently ok...
> SystemView: Session.importXML silently imports protected nodes if their
> parent isn't protected
> ----------------------------------------------------------------------------------------------
>
> Key: JCR-2172
> URL: https://issues.apache.org/jira/browse/JCR-2172
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.0-alpha3
> Reporter: angela
> Attachments: SystemViewTest.java
>
>
> The sys-view import handled by SessionImport is intended to skip protected
> items or to throw an exception:
> - protected properties are skipped
> - child nodes of existing protected nodes are skipped
> - child nodes of non-existing protected nodes result in an
> ConstraintViolationException and the import is aborted.
> However, if the XML to be imported contains a Node that would result in a
> protected Node the following occurs:
> - If the XML defines child nodes for the protected node the import fails (see
> above)
> - If the XML does not define any child nodes for the protected node the
> import succeeds and the protected Node is
> silently created and can be persisted.
> This looks inconsistent to me and i consider this behavior a bug.
> Not sure if this is a problem that exists for a longer time or has been
> introduced recently...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
