You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2023/10/26 15:07:00 UTC

[jira] [Updated] (JCRVLT-724) docviewnode: improve diagnostics when generating DocViewNode2 from JCR node

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

Julian Reschke updated JCRVLT-724:
----------------------------------
    Attachment: SameNameSiblingIT.java

> docviewnode: improve diagnostics when generating DocViewNode2 from JCR node
> ---------------------------------------------------------------------------
>
>                 Key: JCRVLT-724
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-724
>             Project: Jackrabbit FileVault
>          Issue Type: Task
>          Components: vlt
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Major
>         Attachments: SameNameSiblingIT.java
>
>
> See <[https://github.com/apache/jackrabbit-filevault/blob/c0480b9f83ede8969d8bcaf03428a35f81d146c2/vault-core/src/main/java/org/apache/jackrabbit/vault/util/DocViewNode2.java#L91-L110]>
> We have the unfortunate condition that an existing repository apparently contains invalid node names. The code above gets an IllegalNameException from {{nameresolver.getQName()}}, but that code doesn't have the full path to the node (well, it shouldn't exist in the first place...).
> It might be good to catch that exception and add information about the node's path and rethrow it, either where or in the calling code ({{AggregateImpl.walk()}}?).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)