-
Notifications
You must be signed in to change notification settings - Fork 64
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 admi.007.001.01 #39
Comments
There is an issue parsing the unknown "Any" element at the supplementary data: FromBOData |
Hello, Any news about this issue ? Thanks for your help, |
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 the exception is not thrown, however the Any element is not parsed into a generic Element as expected. Test cases and sandbox code has been pushed to: Anyone with the same or similar issue is welcome to explore alternatives for a fix in the NamespaceAndElementFilter or MxReadImpl classes, which are the relevant ones for this. |
Hello, I want to retrieve the data from splmtryData while parsing the XML. |
This seems to be quite a large limitation for this library, especially since the library actually supports a bunch of the xml elements that could be in the splmtryData which can't really be used, ie. (https://github.com/prowide/prowide-iso20022/tree/develop/model-supl-types/src/generated/java/com/prowidesoftware/swift/model/mx/dic). By the time the message has been read, we can't even get access to the xml string at that point to do it manually. I'm curious if the are any workarounds other than parsing everything before the message itself is parsed? This approach doesn't work with frameworks like JMS, etc. |
Indeed it is a known limitation. There is an open PR to handle the Any element. The idea is to return the supplementary data content and any other using Any in the schema as a generic DOM Element. |
Hmm that doesn't seem to work though if the supplementary data is under a different namespace though I don't think? Like in this example message - Line 180 in 7cc0e59
|
Hello,
We are facing a problem while parsing an MX message of type admi.007.001.01 using SRU2020-9.1.5 version. Upgrading to SRU2021-9.2.5 version doesn't resolve the issue.
This is an example of an admi.007.001.01 message:
Could you please help us to fix the issue?
Thanks,
The text was updated successfully, but these errors were encountered: