You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@daffodil.apache.org by "Olabusayo Kilo (Jira)" <ji...@apache.org> on 2021/01/20 16:18:00 UTC

[jira] [Assigned] (DAFFODIL-2457) xmlns="" incorrectly introduced due to prefixOrNull

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

Olabusayo Kilo reassigned DAFFODIL-2457:
----------------------------------------

    Assignee: Olabusayo Kilo

> xmlns="" incorrectly introduced due to prefixOrNull
> ---------------------------------------------------
>
>                 Key: DAFFODIL-2457
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2457
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>    Affects Versions: 3.0.0
>            Reporter: Olabusayo Kilo
>            Assignee: Olabusayo Kilo
>            Priority: Major
>
> When thisElementNamespacePrefix was replaced with prefixOrNull, we lost the functionality where namespaces prefixes are looked up. And instead relied only on the lexical prefix. There's plenty of times when there is no lexical prefix, but there is a namespace associated with the element, thus we can attempt to look up a prefix. We need to bring back this functionality, fixing the incorrect namespaces and incorrect prefixes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)