You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Michael Beckerle (JIRA)" <ji...@apache.org> on 2019/06/20 22:23:00 UTC

[jira] [Updated] (DAFFODIL-1326) RuntimeData objects should not carry namespaces

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

Michael Beckerle updated DAFFODIL-1326:
---------------------------------------
    Labels: beginner  (was: )

> RuntimeData objects should not carry namespaces
> -----------------------------------------------
>
>                 Key: DAFFODIL-1326
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1326
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Clean Ups, Middle &quot;End&quot;
>            Reporter: Michael Beckerle
>            Priority: Major
>              Labels: beginner
>
> This is a code cleanup.
> Today the RuntimeData objects from TermRuntimeData downward in that hierarchy all carry namespaces, which is the NamespaceBinding from the original XML scope giving rise to the object. 
> However, that is only used by the InteractiveDebugger when compiling expressions. Hence, should be (and is) carried on DPathCompileInfo. 
> namespaces should be removed from the TermRuntimeData and all derived classes, and it should be accessed from the DPathCompileInfo objects.
> Also, the definition of namespaces is the xml scope from the original XML, but augmented with xsi in case of nillable attributes being added. However, that is only needed for nillable elements, so adding this xsi nillable all the time just creates something that namespace minimizing has to take out later. It should only be added for nillable elements.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)