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.

Sign up for GitHub

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

Jump to bottom

MXParser improve error reporting when parsing large char entities and invalid encoding declarations #136

Closed
belingueres opened this issue Jan 31, 2021 · 1 comment
Closed

MXParser improve error reporting when parsing large char entities and invalid encoding declarations #136

belingueres opened this issue Jan 31, 2021 · 1 comment

Comments

@belingueres
Copy link
Contributor

Discovered with the help of https://github.com/belingueres/xml-conformance

MXParser fails on parts of the W3C XML Conformance Test Suite.

In this issue, it is failing 001.xml to 004.xml, and 007.xml to 009.xml from "Bjoern Hoehrmann via HST 2013-09-18" (see https://github.com/belingueres/xml-conformance/blob/main/src/test/resources/xmlconf/eduni/misc/ht-bh.xml) regarding the parsing of large character entities and encoding in the declaration section of the xml file.
Tests 005.xml and 006.xml were ignored as MXParser do not support DOCDECL parsing.
belingueres added a commit to belingueres/plexus-utils that referenced this issue Jan 31, 2021
@belingueres
Fix MXParser improve error reporting (codehaus-plexus#136)
195d992 
- when parsing large char entities.
- when mixing invalid encoding declarations and file encodings.
olamy pushed a commit that referenced this issue Apr 4, 2021
@belingueres
Fix MXParser improve error reporting (#136) (#137)
1e18ddc 
- when parsing large char entities.
- when mixing invalid encoding declarations and file encodings.
@michael-o
Copy link
Member

Fixed with 1e18ddc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@michael-o @belingueres