-
Notifications
You must be signed in to change notification settings - Fork 34
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
XsdParser::getSchemaNode fails with comments #7
Comments
Hi, Thanks for the note. I'll introduce that fix with the next release once another feature is requested. I've taken that approach since the XSD documentation states that the xsd:schema should always be the first node of a XSD document, but in any case I'll introduce that fix to prevent any bugs with files that contain comments before the xsd:schema node. Thank you again. Regards, |
Hello Luis,
good to know. I was a bit desparate, as all schema checking tools
accepted the XML file whereas my tool based on the XsdParser terribly
failed :-)
Bye, Carsten
Am Dienstag, den 21.05.2019, 05:38 -0700 schrieb Luís Duarte:
… Hi,
Thanks for the note. I'll introduce that fix with the next release
once another feature is requested. I've taken that approach since the
XSD documentation states that the xsd:schema should always be the
first node of a XSD document, but in any case I'll introduce that fix
to prevent any bugs with files that contain comments before the
xsd:schema node.
Thank you again.
Regards,
Luís
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hello, In 1.0.17 this issue is resolved. I'll close this issue, open another if you get any other problem. Regards, |
Hello,
currently XsdParser uses doc.getFirstChild(); to get the XSD root.
This fails terribly with all kinds of schema which have a comment or text node.
My proposal is to use
return doc.getDocumentElement();
Bye, Carsten
The text was updated successfully, but these errors were encountered: