[
https://issues.apache.org/jira/browse/OLINGO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838611#comment-13838611
]
ASF subversion and git services commented on OLINGO-73:
-------------------------------------------------------
Commit 1d579f575431ff9e9b52cfc7890bc15d599e35af in branch
refs/heads/PocEdmAnnotationsExtension from [~chrisam]
[
https://git-wip-us.apache.org/repos/asf?p=incubator-olingo-odata2.git;h=1d579f5
]
[OLINGO-73] use getElementText where possible
next() in combination with getText() might not deliver all character data.
Thus we have to check for the characters event again or use
getElementText(). For the metadata consumer a bugfix regarding annotations
is still missing.
> 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)
