You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/10/11 10:08:00 UTC

[jira] [Updated] (JCRVLT-658) Importer fails for invalid namespace names (ones not containing a colon)

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

Konrad Windszus updated JCRVLT-658:
-----------------------------------
    Summary: Importer fails for invalid namespace names (ones not containing a colon)  (was: Importer fails for invalid namespace names)

> Importer fails for invalid namespace names (ones not containing a colon)
> ------------------------------------------------------------------------
>
>                 Key: JCRVLT-658
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-658
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: vlt
>    Affects Versions: 3.6.4
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>             Fix For: 3.6.6
>
>
> If content uses XML namespaces that are invalid as JCR namespace names, import can fail, because JCR's expanded name notation ("Clark" notation) only works *valid* namespace names.
> Example; content contains:
> xmlns:foo="bar"
> for a child node "foo:child". The expanded form would be "\{bar}child", but Jackrabbit and Oak can not resolve that, as "bar" is not detected as JCR namespace name (which by definition is an absolute URI).
> Importer code that uses expanded names thus needs to special-case namespace names where the expanded name notation will not work.



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