-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
StartLocation offset does not match to SystemId during external entity replacing #91
Comments
Sounds like a bug, yes. If anyone has time, the first step could be to write a (failing) unit test to reproduce the problem in its smallest form, and help verify eventual fix. |
nkutsche
pushed a commit
to nkutsche/woodstox
that referenced
this issue
Dec 8, 2019
Merged
cowtowncoder
pushed a commit
that referenced
this issue
Dec 11, 2019
Adds unit test case for issue #91
cowtowncoder
added a commit
that referenced
this issue
Dec 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
if I set the properties
IS_SUPPORTING_EXTERNAL_ENTITIES
andIS_REPLACING_ENTITY_REFERENCES
totrue
I'm facing the following problem. The replacing of the external entity works fine, but for the first event after the reader jumbs into the entity document or back to the main document theValidatingStreamReader.getStartLocation()
method returns an invalid location (at least in my case).First case: reader jumps into the external entity document -> systemId is from the entity document, but the character offset points to a position in the main document.
Second case: reader jumps back into the main document -> the otherway around: systemId is the main document, but offset points to the entity document.
The following sample should demonstrate it:
This is the result:
The bad locations are:
(I would expect
include.xml#0
)and
(I would expect
main.xml#65
)Thanks for your help!
Best Regards,
Nico
The text was updated successfully, but these errors were encountered: