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

2018-02-05 Thread Tobias Bocanegra (JIRA) 

[ 
https://issues.apache.org/jira/browse/JCRVLT-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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}
> 
> 
> {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)

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

2018-02-04 Thread Konrad Windszus (JIRA) 

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

Konrad Windszus commented on JCRVLT-266:


Thanks for quick fix. Regarding the usefulness: Even for packages having much 
deeper filter roots than “/“ the package will also include docview files for 
the root. As those files have been invalid due to the missing namespace 
declaration installing such packages lead to weird warnings in the log. This 
fix should help to get rid of them.

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

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

2018-02-02 Thread Konrad Windszus (JIRA) 

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

Konrad Windszus commented on JCRVLT-266:


The PR in https://github.com/apache/jackrabbit-filevault/pull/22 contains a 
proposed fix.

> 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
>Priority: Major
>
> 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}
> 
> 
> {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)

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

2018-02-02 Thread Konrad Windszus (JIRA) 

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

Konrad Windszus commented on JCRVLT-266:


The code in 
https://github.com/apache/jackrabbit-filevault/blob/e12e38a69f2ea404f24d965918467dffb4db8e09/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/impl/AggregateImpl.java#L401
 must be extended to always return {{jcr}} as prefix.

> 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
>Priority: Major
>
> 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}
> 
> 
> {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)