[
https://issues.apache.org/jira/browse/SLING-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-2033.
--------------------------------------
Resolution: Fixed
Actually the expected node name must not be empty because it is also used after
the import to return the imported node. Thus if the name is empty (or consists
of the jcr.xml extension only), an IOException with a message is now thrown.
Fixed in Rev. 1086183
> Unexpected NullPointerException on System View import
> -----------------------------------------------------
>
> Key: SLING-2033
> URL: https://issues.apache.org/jira/browse/SLING-2033
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR ContentLoader 2.1.2
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR ContentLoader 2.1.4
>
>
> Importing Content in the DefaultContentImporter with a name of just "jcr.xml"
> will select the System View import mechanism but causes the import to
> indirectly fail because the name used for checking the existence of the
> imported node in the DefaultContentImporter.importSystemView method is empty.
> On repository implementation is known to throw a NullPointerException in this
> case....
> Fix is to check whether the name is not empty before checking for the
> existence of the node.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
