Bug 24572 - problem in reading Excel using Eventmodel API
Summary: problem in reading Excel using Eventmodel API
Status: RESOLVED INVALID
Alias: None
Product: POI
Classification: Unclassified
Component: HSSF (show other bugs)
Version: 2.0-pre2
Hardware: PC All
: P3 major (vote)
Target Milestone: ---
Assignee: POI Developers List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-10 17:53 UTC by sree
Modified: 2008-05-10 20:22 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description sree 2003-11-10 17:53:51 UTC 
Hi,
This is Sree. I'm having some problem in reading Excel files using POI ( HSSF). 
My excel contains macros, formulae and is protected. Usernodel API is not able 
to read my excel, so I'm using eventmodel API. my workbook contains more than 3 
sheets. It is able to read part of my excel(only one sheet) and then it is 
throwing exception called java.lang.reflect.InvocationTargetException: 
java.lang.ArrayIndexOutOfBoundsException:
I'm using poi-2.0-pre1-20030517.jar file. 
Please help me in coming out from this problem.
I appreciate ur response.
Comment 1 sree 2003-11-10 17:55:45 UTC 
Hi,
This is Sree. I've mailed u couple of times regarding this problem. Please help 
me out from this. It is very urgent.
I'm having some problem in reading Excel files using POI ( HSSF). My excel 
contains macros and is protected. Usernodel is not able to read my excel, so 
I'm using eventmodel. It is able to read part of my excel and then it is 
throwing exception called java.lang.reflect.InvocationTargetException: 
java.lang.ArrayIndexOutOfBoundsException:
I'm using poi-2.0-pre1-20030517.jar file. Otherwise please send me the latest 
jar file.
Please help me in coming out from this problem.
I appreciate ur response.
Comment 2 Josh Micich 2008-05-10 20:22:54 UTC 
ArrayIndexOutOfBoundsException is often thrown when POI is reading BIFF records. This may have been to reading an old (pre BIFF8) Excel file (hard to tell because there is no attachment). Alternatively, it may have been due to a bug in a record class.  Version 2.0 is very old and many record classes have been fixed since then.