Skip to content
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

Open
lstanden opened this issue Dec 13, 2012 · 6 comments
Open

doctype definitions cause XML parsing problems in JRuby #2

lstanden opened this issue Dec 13, 2012 · 6 comments

Comments

@lstanden
Copy link

It appears the doctype definitions at the top of the following files cause XML validation errors in JRuby:

  • xmldsig-core-schema.xsd
@morten
Copy link
Contributor

morten commented Dec 14, 2012

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.

@morten
Copy link
Contributor

morten commented Dec 14, 2012

That was wrong. I don't remember why I'm not testing JRuby but am investigating.

@lstanden
Copy link
Author

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.

@morten
Copy link
Contributor

morten commented Dec 14, 2012

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.

@morten
Copy link
Contributor

morten commented Dec 14, 2012

Removing the DOCTYPEs still surfaces other issues. Looks like severe problems with XML canonicalization in the Nokogiri Java parts.

@morten
Copy link
Contributor

morten commented Dec 14, 2012

I've reported the c14n issue with Nokogiri sparklemotion/nokogiri#808
Judging from the size of their issues queue I'm afraid theres not much hope for a short term fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants