You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 29, 2023. It is now read-only.
I can parse the sample with the bindings for the foo_namespace schema whether or not element Foo is present, and all non-Foo elements are placed into the wildcard elements (as expected).
When I include a binding for the bar_namespace schema, the XML sample is parsed correctly when the Foo element is present. However, if the Foo element is missing, I get the warning:
Multiple accepting paths for <class 'foo.CTD_ANON'>
It seems that the "Bar A" text gets parsed into the Foo element, and writing the XML back out results in:
Is this schema truly ambiguous or is this a PyXB issue? I would think that the ##other attribute of the any element means that the {bar_namespace}Bar element is unambiguous, but it's possible I'm missing something. It's also not clear to me how the Bar element gets parsed into the Foo element.
I am using bindings generated by PyXB 1.2.6.
I have a schema which is (essentially):
Paired with another schema:
Parsing this XML sample:
I can parse the sample with the bindings for the
foo_namespace
schema whether or not elementFoo
is present, and all non-Foo
elements are placed into the wildcard elements (as expected).When I include a binding for the
bar_namespace
schema, the XML sample is parsed correctly when theFoo
element is present. However, if theFoo
element is missing, I get the warning:Multiple accepting paths for <class 'foo.CTD_ANON'>
It seems that the "Bar A" text gets parsed into the
Foo
element, and writing the XML back out results in:Is this schema truly ambiguous or is this a PyXB issue? I would think that the ##other attribute of the any element means that the
{bar_namespace}Bar
element is unambiguous, but it's possible I'm missing something. It's also not clear to me how theBar
element gets parsed into theFoo
element.Attached is code and samples reproducing the issue.
wildcard_tests.zip
The text was updated successfully, but these errors were encountered: