[ https://issues.apache.org/jira/browse/JCRVLT-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16353181#comment-16353181 ]
Tobias Bocanegra commented on JCRVLT-266: ----------------------------------------- bq. Even for packages having much deeper filter roots than “/“ the package will also include docview files for the root. no. all ancestor nodes will contain the serialized properties; even the root node. only if the access control denies read access, those would be omitted. > DocViewSaxFormatter does not always emit namespace declaration for "jcr" > ------------------------------------------------------------------------ > > Key: JCRVLT-266 > URL: https://issues.apache.org/jira/browse/JCRVLT-266 > Project: Jackrabbit FileVault > Issue Type: Bug > Components: vlt > Affects Versions: 3.1.42 > Reporter: Konrad Windszus > Assignee: Tobias Bocanegra > Priority: Major > Fix For: 3.1.44 > > > Under certain circumstances the {{DocViewSaxFormatter}} does not emit any > namespace declarations. That is the case for an aggregate not having any > namespaced properties (e.g. due to lack of read privileges) and not having > any namespaced child elements. The generated {{.content.xml}} then looks like > this: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <jcr:root /> > {code} > This XML is invalid and leads to exceptions during import. > The problem is that the namespace for {{jcr}} is always necessary as the root > element is always named {{jcr:root}}. -- This message was sent by Atlassian JIRA (v7.6.3#76005)