https://issues.apache.org/bugzilla/show_bug.cgi?id=49761

Phil Dunlea <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |
         AssignedTo|[email protected]          |[email protected]

--- Comment #10 from Phil Dunlea <[email protected]> 2010-10-13 11:42:34 EDT ---
Created an attachment (id=26170)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=26170)
3 Unit Tests showing error still occurs

I download from SVN the poi-3.7-beta3 tag the entire file structure and stuck
my test into 
src/testcases  org.apache.poi.hssf.record so it could be run as part of "ant
test" when building.   

We have a scientific instrument that exports Double.NaN into an excel file.  We
can NOT upgrade the software or change how it works.  We must be able to read
this file into our application.  The way you are handing Double.NaN is keeping
this from happening.  The prior version of POI we were using allowed the
reading of Double.NaN.

The error is still occurring in both the Event Based and direct modes of
reading an excel file.

Test 1:  testWriteNaNToFileSystem()  

-  Shows that you can create a file with Double.NaN.  Properly saves the file
with no errors.  
-  This test passes.

Test 2:  testEventBasedDoubleNaNError()

-  Creates the same file and reads it using the event based model.  Saves the
Double read into a variable as part of the listener.   Asserts that the value
read in is not null. 
-  This test fails.

Test 3:  testDirectDoubleNaNError()

-  Creates the same file and reads it using a direct approach.  Asserts that
the value read in from the cell is equal the the value put into the file
-  This test fails.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to