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 2022/09/24 12:43:00 UTC

[jira] [Updated] (JCRVLT-658) Importer fails for invalid namespace names

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

Julian Reschke updated JCRVLT-658:
----------------------------------
    Description: 
If content uses XML namespaces that are invalid as JCR namespace names, import can fail, because JCR's fully qualified name notation ("Clark" notation) only works *valid* namespace names.

Example; content contains:

xmlns:foo="bar"

for a child node "foo:child". The qualified 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 qualified names thus needs to special-case namespace names where the qualified notation will not work.

  was:
If content uses XML namespaces that are invalid as JCR namespace names, import can fail, because JCR's fully qualified name notation ("Clark" notation) only works *valid* namespace names.

Example; content contains:

xmlns:foo="bar"

for a child node "foo:child". The qualified 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 qualified names thus needs to special-case namespace names where the qualified notation will not work.


> Importer fails for invalid namespace names
> ------------------------------------------
>
>                 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
>            Priority: Minor
>
> If content uses XML namespaces that are invalid as JCR namespace names, import can fail, because JCR's fully qualified name notation ("Clark" notation) only works *valid* namespace names.
> Example; content contains:
> xmlns:foo="bar"
> for a child node "foo:child". The qualified 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 qualified names thus needs to special-case namespace names where the qualified notation will not work.



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