Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parsing issue with MX message of type xsys.003.001.01 #41

Open
john236 opened this issue Jan 17, 2022 · 3 comments
Open

Parsing issue with MX message of type xsys.003.001.01 #41

john236 opened this issue Jan 17, 2022 · 3 comments
Labels
AnyTagParsing enhancement New feature or request

Comments

@john236
Copy link

john236 commented Jan 17, 2022

My issue sounds similar to #39 but is about the xsys.003.001.01 message type.

The ThirdPartyRefusalReason element is of type SwAny but when I try to parse a message with a 4 character string in that element, for example:
<Sw:ThirdPartyRefusalReason>ABCD</Sw:ThirdPartyRefusalReason>
then SwAny.any is null.

@zubri
Copy link
Member

zubri commented Feb 23, 2022

I see. We need to find general solution for all Any types in the parser.

@john236
Copy link
Author

john236 commented Feb 25, 2022

fyi, Swift have now changed the SwAny type so it must have a child element. For example:

<Sw:ThirdPartyRefusalReason>
  <Sw:Cd>ABCD</Sw:Cd>
</Sw:ThirdPartyRefusalReason>

@zubri
Copy link
Member

zubri commented May 25, 2022

Test case and a few exploration approaches have been pushed to:
#48

XmlAnyElement is expected to be parsed into a generic Element node.

The root cause is probably in our NamespaceAndElementFilter and MxReadImpl classes. But could not find a solution to fit al scenarios yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AnyTagParsing enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants