Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
There is some issue in the underlining Stax reader's getLocation().getCharOffset() when the input data is an InputStream to the stax reader.
This issue was brought up in the woodstox community. But I believe fixing it seems to be non trivial as woodstox internally uses char/Reader and keeps the offset value to the character sequence and not to the original input stream.
We change the tokenzer to pass java.io.Reader to the woodstox parser instead of passing java.io.InputStream directly.
Attachments
Issue Links
- is part of
-
CAMEL-7468 Make xmlTokenizer more xml-aware so that it can handle more flexible structures
- Resolved