[
https://issues.apache.org/jira/browse/JCRVLT-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034217#comment-17034217
]
Konrad Windszus commented on JCRVLT-407:
----------------------------------------
Actually I had a mistake in my testcase and indeed it already works as
expected. Still to better decouple parsing from importing it would be nice to
rely on expanded names for nodes (similar to property names). That way the
session namespace wouldn't need to be overwritten during import.
> DocView XML: Proper namespace support for node names during import
> ------------------------------------------------------------------
>
> Key: JCRVLT-407
> URL: https://issues.apache.org/jira/browse/JCRVLT-407
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
> Affects Versions: 3.4.2
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: 3.4.4
>
>
> Currently any DocView files is processed by the DocViewSAXImporter which
> creates in the end nodes in the repository via
> https://github.com/apache/jackrabbit-filevault/blob/e05e3fc8031eb08f6d0815316ec7fff3367df53c/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/impl/io/DocViewSAXImporter.java#L800.
> That just takes {{DocViewNode}} as parameter. Unfortunately the node name is
> only contained there in its qualifed (i.e. prefixed) form
> (https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.5.2%20Qualified%20Form).
> In case the XML uses other prefixes than the underlying JCR the namespaces
> won't be correctly resolved, as the node creation happens in
> https://github.com/apache/jackrabbit-filevault/blob/e05e3fc8031eb08f6d0815316ec7fff3367df53c/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/impl/io/DocViewSAXImporter.java#L1050
> with just the qualified form.
> I would propose that the DocView node uses the expanded form
> (https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.5.1%20Expanded%20Form)
> for node names, similar to property names!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)