Philipp Marx created JCR-3662:
---------------------------------
Summary: A lot of warn messages when importing via
Session#importXML (...doesn't represent a valid Authorizable)
Key: JCR-3662
URL: https://issues.apache.org/jira/browse/JCR-3662
Project: Jackrabbit Content Repository
Issue Type: Bug
Affects Versions: 2.4
Reporter: Philipp Marx
Priority: Minor
We are exporting a part of our JCR tree via Session#exportSystemView and
re-import this via Session#importXML. During the import we are seeing a lot of
WARNINGS as the following:
11:41:35,514 | WARN |
.core.security.user.UserImporter | 08e6b3e2-b55a-40fd-93f9-b92ccb8477d4
| Cannot handle protected PropInfo
org.apache.jackrabbit.core.xml.PropInfo@749951b8. Node node
/content/ea/api/media/5/d/5d8e29d4-2531-b5a5-388b-
e1d700000028-6826c36c-fce2-70a9-f6d2-90b100000028 doesn't represent a
valid Authorizable.
11:41:35,514 | WARN |
re.security.user.UserManagerImpl | 08e6b3e2-b55a-40fd-93f9-b92ccb8477d4
| Unexpected user/group node type cu:Media
The imports works fine though I am wondering why the JCR importer is trying
to handle all of our nodes as Authorizables? We have a CND for cu:Media (in
above case) if that matters.
I can see that this was introduced by issue JCR-3120. But why should a
perfectly valid import throwing all this warning messages?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
