Long base64 content causes readElementAsBinary always returns maxLength

[fasterxml]

Long base64 content causes readElementAsBinary always returns maxLength

[sandyperez]

Hello,

I closed the issue because I made some tests with TestBase64Reader and it works fine no matter how long base64 content is. However, I reopened it (sorry for the inconveniences I could cause) because I rewrote the test calling createAsyncXMLStreamReader instead of createXMLStreamReader and get the “wrong” behaviour again.

Could readElementAsBinary be invoked from an asynchronous reader? If that's not the case, which mechanism could be use to read base64 content from an asynchronous reader?.

Best regards,
Sandy Pérez González
IT Consultant,
Indaba Consultores S.L.
http://www.indaba.es/

[cowtowncoder]

Sorry, I thought I had commented on this issue, but looks it didn't save.

readElementAsBinary() method can not be made to work in async mode; it probably should throw an exception or something to indicate this. The problem is that for that method to work it would have to block; or indicate un-availability of content and handle buffering.

[sandyperez]

Thank you very much for your answer.

Best regards,
Sandy Pérez González
IT Consultant,
Indaba Consultores S.L.
http://www.indaba.es/