Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <730053973.1246006628318.JavaMail.jira@brutus>
Date: Fri, 26 Jun 2009 01:57:08 -0700 (PDT)
From: "angela (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-2172) SystemView: Session.importXML silently
 imports protected nodes if their parent isn't protected
In-Reply-To: <2121121690.1246006267344.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela updated JCR-2172:
------------------------

    Attachment: SystemViewTest.java

2 tests demonstrating the behaviour described in the issue.

- testImportProtectedNodes
  attempts to import a hierarchy of protected items

- testImportProtectedNode
  attempts to import a single protected node without protected child nodes.

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