[
https://issues.apache.org/jira/browse/OLINGO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834809#comment-13834809
]
Aki Yoshida commented on OLINGO-73:
-----------------------------------
hi,
As far as I know (tried to find the spec statement but couldn't find it), this
is not a bug in the parser and it's part of optimization. There is no
requirement by the parser to return a single characters event for a character
sequence appearing within xml.
so you need to check the event type before calling methods like nextTag that
are only allowed to be called at an appropriate event.
regards, aki
> Woodstox parser fails for big files sometimes
> ---------------------------------------------
>
> Key: OLINGO-73
> URL: https://issues.apache.org/jira/browse/OLINGO-73
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Affects Versions: V2 1.0.0
> Reporter: Christian Amend
> Assignee: Christian Amend
> Fix For: V2 1.1.0
>
>
> For some big xml files the woodstox parser which is a transitive dependency
> of cxf fails with the exception: "Found characters or cdata event when not
> expected"
> This happens because a previous call of getText() doesn´t deliver the whole
> text but only a fraction. So when we call nextTag() the parser throws the
> exception because there is still character data on the buffer. This issue
> does only appear with big xml files and happens randomly within the document
> altough always at the same element.
> So maybe this is a woodstox bug. We can implement a workaround by calling
> getText() as long as there is still character data left.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
