Stax XML EventReader: What portion of data is returned when parsing large data element
We have a very large content of one data element (over 1000 000 of strings). When we parse with stax we HARACTER event is triggered so that normall around 12 strings are returned by one event, so we assumed first, there is some parse buffer length there.
Then, we saw around 6 exceptuions of this rule.
We played around if that might be due to specific data and whitespaces but XML is generated automatically and after removing certin portions the problem appeared elsewhere at parsing
The question is: if stax event parses is faced to large contents what triggers the event and what portion of text we may expect in the returned characters ?
Then, we saw around 6 exceptuions of this rule.
We played around if that might be due to specific data and whitespaces but XML is generated automatically and after removing certin portions the problem appeared elsewhere at parsing
The question is: if stax event parses is faced to large contents what triggers the event and what portion of text we may expect in the returned characters ?
CEHJ
Which implementation of stax are you using?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
another alternative would be to use the cursor api
ASKER
The link above match my question best. The answer there was somethink that I googled on another article.
Does anyone has toher idea if we can control the size of the text read by one event?
Does anyone has toher idea if we can control the size of the text read by one event?
>>Does anyone has toher idea if we can control the size of the text read by one event?
Again, what implementation of stax are you using?
Again, what implementation of stax are you using?