[
https://issues.apache.org/jira/browse/JCRVLT-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063598#comment-17063598
]
Konrad Windszus edited comment on JCRVLT-423 at 3/21/20, 4:56 PM:
------------------------------------------------------------------
The problem is that we don't have a namespace registry at hand without a repo.
Therefore you have to define all namespaces in docview xml. That is already
described in
https://docs.adobe.com/docs/en/spec/jcr/2.0/7_Export.html#7.3%20Document%20View,
paragraph 1. The only difference is that in this case the filename defines the
node name.
I will definitely fix the exporter in that way, but the question is what to do
with exports from older FileVault versions.
I am all ears for a solution which allows to have fully qualified node names in
https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/validation/spi/DocumentViewXmlValidator.html#validate-org.apache.jackrabbit.vault.util.DocViewNode-java.lang.String-java.nio.file.Path-boolean-
for the {{jcr:root}} element.
The current solution has been discussed in
https://issues.apache.org/jira/browse/JCRVLT-407?focusedCommentId=17033830&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17033830.
was (Author: kwin):
The problem is that we don't have a namespace registry at hand without a repo.
Therefore you have to define all namespaces in docview xml. That is already
described in
https://docs.adobe.com/docs/en/spec/jcr/2.0/7_Export.html#7.3%20Document%20View,
paragraph 1. The only difference is that in this case the filename defines the
node name.
I will definitely fix the exporter in that way, but the question is what to do
with exports from older FileVault versions.
I am all ears for a solution which allows to have fully qualified node names in
https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/validation/spi/DocumentViewXmlValidator.html#validate-org.apache.jackrabbit.vault.util.DocViewNode-java.lang.String-java.nio.file.Path-boolean-
for the {{jcr:root}} element.
> filevault-package-maven-plugin 1.1.2: Validation fails on /content/cq:tags
> node
> -------------------------------------------------------------------------------
>
> Key: JCRVLT-423
> URL: https://issues.apache.org/jira/browse/JCRVLT-423
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: package maven plugin
> Affects Versions: package-maven-plugin-1.1.2
> Reporter: Stefan Seifert
> Priority: Major
>
> i've encountered another problem, occurs on 1.1.2 and 1.1.3-SNAPSHOT, not
> with version 1.1.0 of the plugin.
> sample project that contains some content below {{/content/cq:tags}}:
> https://github.com/stefanseifert/filevault-package-maven-plugin-1.1.2-validation-issues/tree/master/content-packages/sample-content
> leads to validation failures:
> {noformat}
> [ERROR] ValidationViolation: "jackrabbit-docviewparser: Invalid XML found:
> Given root node name 'cq:tags' (implicitly given via filename) cannot be
> resolved. The prefix used in the filename must be declared as XML namespace
> in the child docview XML as well!",
> filePath=jcr_root\content\_cq_tags\.content.xml
> [ERROR] ValidationViolation: "jackrabbit-filter: Node
> '/content/cq:tags/.content.xml' is not contained in any of the filter rules",
> filePath=jcr_root\content\_cq_tags\.content.xml
> {noformat}
> the package content is exactly that what the package manager produced when
> downloading the package, so the package data itself is correct.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
