Open rossanoros opened 10 months ago
Same for me. For example we filled out all required fields of this form (of subtype 24) producing this visual model: visual-model.json. This converts into pyhsical-model.xml (Using SDK Version 1.8.1) which has 97 XSD issues according to intelij IDEA.
We tested this using the latest commit https://github.com/OP-TED/eforms-notice-editor/commit/7d703e21229f1ae33878d8bb5d2079474a58a2af from the develop
-branch.
The same applies to these examples:
SDK v1.9.1, notice subtype 1: visual.json | physical.xml (27 XSD Issues) SDK v1.9.1, notice subtype 17: visual.json | physical.xml (123 XSD Issues) SDK v1.10, notice subtype: 16: visual.json | physical.xml (120 XSD Issues)
until now, i did not even generate one single xsd-valid xml file.
Hello @rousso,
I'm also experiencing similar XSD validation issues across different SDK versions. Are there any updates or potential fixes being discussed for this issue? Thanks for any additional information.
Regards
Hello,
Thanks for your work! We are trying to use your solution to create a ContractNotice. The XSD valiation fails continuously.
We are using the sdk 1.9, do you have any idea on how to solve?
Regards