Sebastian Zubrinic

Yes, the constants are partial. What is covered is the main codewords used in the fields definitions. Such as:  It was original intended...

Task linked: [CU-25c5ac2 GH-39 ⁃ Parsing issue with MX message of type admi.007.001.01](https://app.clickup.com/t/25c5ac2)

Hi Paul, thanks for the input. Since there are too many message types to cover the whole current and historic standard, the generated model is not the plain output from...

We probably need a type adapter to handle the Any elements. This is a long time pending issue. As for the namespace, it is a bit strange, since the one...

This issue is similar to #39 and #41 Test case and a few exploration approaches have been pushed to: https://github.com/prowide/prowide-iso20022/pull/48 XmlAnyElement is expected to be parsed into a generic Element...

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

Test case and a few exploration approaches have been pushed to: https://github.com/prowide/prowide-iso20022/pull/48 XmlAnyElement is expected to be parsed into a generic Element node. The root cause is probably in our...

There is an issue parsing the unknown "Any" element at the supplementary data: FromBOData

Hi, it's still pending and not easy to fix. You are welcome to propose a solution via PR.

I've been exploring this issue. The actual error comes from the custom NamespaceAndElementFilter. In particular, the startPrefixMapping method causes the negative index in the internal UnmarshallingContext implementation. By removing that...