[
https://issues.apache.org/jira/browse/DAFFODIL-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413261#comment-17413261
]
Mike Beckerle commented on DAFFODIL-2550:
-----------------------------------------
>From your explanation above, I'm not sure why elem2 not having any
>enclosingElements (term elements that is) matters.
Why and how would the tests that are getting spurious xmlns="" be sensitive to
this.
You point out that elem2 isn't a root, so unless there is an element reference
to it, it's dead code, i.e., an unused part of the schema.
So why does this elem2 not having enclosingElements matter at all?
> xmlns="" not minimized away in two CLI tests.
> ---------------------------------------------
>
> Key: DAFFODIL-2550
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2550
> Project: Daffodil
> Issue Type: Bug
> Components: Middle "End"
> Affects Versions: 3.2.0
> Reporter: Mike Beckerle
> Assignee: Steve Lawrence
> Priority: Major
>
> Changes in [https://github.com/apache/daffodil/pull/600] clean up things a
> lot, but there is one mystery change in behavior.
> Two CLI tests now add an xmlns="" to an inner locally-declared element which
> has a unqualified name.
> This seems like incorrect namespace binding minimization, possibly.
> Rather than hold up the merge of PR 600 (which is a big change set, so needs
> to be merged real soon now) this ticket is to investigate this issue of the
> two CLI tests and the xmlns="" that seems unnecessary.
> Note that we've suspected there could be bugs in namespace binding
> minimization for a while now.
> The two CLI tests are:
> * test_CLI_Debugger_InfoHidden_1
> * test_CLI_Debugger_InfoHidden_2
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
