-
Notifications
You must be signed in to change notification settings - Fork 12
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
doctype definitions cause XML parsing problems in JRuby #2
Comments
Do you have some sort of stack trace or similar that I can go with? Tests are passing on JRuby on Travis - I'd hope a W3C XML file to be valid. |
That was wrong. I don't remember why I'm not testing JRuby but am investigating. |
Awesome... I intended to put some more information in there last night, but didn't end up having time to look at it. I found when I removed the doctype definitions from two different files that I was able to get further, but then it appears I ran into another issue where the SHA checksums didn't match. |
I may have fixed the SHA checksums - at least I just pushed a fix because they were failing under different rubies. Still trying to wrap my head around the underlying issue for this one. |
Removing the DOCTYPEs still surfaces other issues. Looks like severe problems with XML canonicalization in the Nokogiri Java parts. |
I've reported the c14n issue with Nokogiri sparklemotion/nokogiri#808 |
It appears the doctype definitions at the top of the following files cause XML validation errors in JRuby:
The text was updated successfully, but these errors were encountered: