Re: POI - Index Out of Bounds when Cell A1 is numeric (XSSF)

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Hi Brian,

I have not tested that code with POI 3.10.  You may have to update the 
code to work with any changes they made in this newer version...

The error is occuring in the code that's in the xlparse.jar file, in the 
ParseSheetXssf class...  the source code should be a file named 
'xlparse-src.jar' that was included in the ZIP file with all of the code 
for the XLPARSE stuff...

That code works nicely with 3.6, but for some reason, this is an area of 
POI where they often break compatibility from release to release, so it 
probably needs to be updated to work with 3.10 or other newer versions.

-SK


On 6/26/2015 1:19 PM, Brian Kelly wrote:
> I am using POI and Scott Klement's utility programs  [
> http://www.scottklement.com/poi/] to parse excel spreadsheets from within
> an RPG program.  I have noticed that I can consistently get the following
> error if Cell A1 on the spreadsheet is numeric (Excel type Generic or
> Numeric), but can not get the error if cell A1 is an Excel data type of
> String.  I have gone to the point of using the same spreadsheet and putting
> a number in cell A1, watch it fail, and then prefix the number with a ' to
> designate it as a string and watch it work.
>
> Here is the error I am seeing:
> Message.....  : Java exception received when calling Java method.
> Cause......     : RPG procedure XLPARSE_WO in program ASPBEV1113/XLPARSER4
> received Java execption "java.lang.IndexOutOfBoundsException: Index: 0,
> Size: 0 when calling method "parse" with signature "([B)V" in class
> "com.iseriesnetwork.clubtech.xlparse.ParseSheetXssf".
>
>
> I have been able to reproduce this only with the XLSX document types, which
> I believe use XSSF instead of HSSF.
>
> My question is has anyone ran across this issue prior and knows of any ways
> to work around this?
>
> I am currently using POI version 3.10 (poi-3.10-FINAL-20140208.jar), and
> can get everything else to work fine but this scenario.  I have attempted
> to put a newer version of POI into our iSeries IFS to see if something
> recently fixed this issue but am also unsure if I did that right at this
> point.  We have it setup so that the POI data is in
> /qibm/UserData/Java400/ext directory, and dropping the 3.12 Jar files into
> that directory didn't seem to do the trick.
>
> Any help or ideas that I can check would be greatly appreciated.  The
> utility program and POI we find very useful.
>
>
> Thanks.