You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2018/02/05 02:53:00 UTC

[jira] [Resolved] (JCRVLT-266) DocViewSaxFormatter does not always emit namespace declaration for "jcr"

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

Tobias Bocanegra resolved JCRVLT-266.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.1.44

fixed slightly different in r1823118.

although I doubt that incomplete serialized packages are particularly useful.

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